
From nsb@guppylake.com  Mon Aug  1 05:48:24 2011
Return-Path: <nsb@guppylake.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC5811E83ED for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 05:48:24 -0700 (PDT)
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_15=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zx7Iq7u+22qy for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 05:48:23 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 5507311E83F9 for <ietf@ietf.org>; Mon,  1 Aug 2011 05:48:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=uYUYReeAk4SyFw6KI3weilEgSNWx2R9hwYrRHaEYzjTvu7zUZ5CO+5CVaiwyTllwo0Ipz9vNWrEq+STcXc0+bNk0PHYCZ8t8pHw4Al8qrAD26iVjUvFJkqXgydwLH83F;
Received: from 70-9-10-51.pools.spcsdns.net ([70.9.10.51] helo=[192.168.0.197]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1Qnrui-00022L-KE; Mon, 01 Aug 2011 08:48:09 -0400
Subject: Re: DKIM Signatures now being applied to IETF Email
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <4E352A74.6080703@isdg.net>
Date: Mon, 1 Aug 2011 08:48:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>	<CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>	<00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net> <F5833273385BB34F99288B3648C4F06F13512DF4CE@EXCH-C2.corp.cloudmark.com> <4E352A74.6080703@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 12:48:24 -0000

I find it amazing how many different ways there are to criticize DKIM =
for not doing something it was never intended to do.  DKIM is a small =
building block that enables new functionality, but such functionality is =
beyond the scope of DKIM.

DKIM does one thing, and one thing only:  It uses a cryptographic =
signature to associate a domain with a message.  By doing so, it creates =
strong evidence that the message passed through that domain at some =
point and has not been significantly modified since.

Whether that domain is good guys or bad guys, senders or resenders, Coke =
or Pepsi, is completely irrelevant.  It is a small nugget of evidence to =
provide an anchor point for forensics stronger than what have come =
before.  It tells us that the named domain considered the message =
reasonable to send or resend, for its own reasons -- its own forensic =
evidence, its nefarious intent, or the phase of the moon.  With such an =
anchor, we can begin to build stronger and more robust systems for =
analyzing the desirability of messages, as we are now trying to do in =
the REPUTE work, because it allows us to push our forensic analysis =
upstream a bit.  It does not relieve downstream software of the need to =
decide how to feel about the signing domain, whether it's a spammer, a =
copy-cat, or anyone else.

If, for example, the IETF mailing list software only allows posting by =
list members, but itself trusts the sender's header fields, then an IETF =
DKIM signature tells me only that the IETF servers think a message =
passed that test.  That's obviously not perfect, but it's slightly =
stronger than what came before -- it is still possible to forge a =
message before sending it to the list, but much harder to forge a =
message to look as if it came from the list exploder.  That is progress =
-- very very small, slow, progress.  If, at some point, the list =
exploder starts only passing through messages that themselves have valid =
DKIM signatures, it will be significantly more progress, but it won't do =
anything to stop a spammer from subscribing to the IETF list and =
DKIM-authenticating himself.  For that we'll need reputation information =
-- another small step, which we're trying to initiate with REPUTE.

We've had a long history of grand plans for user authentication on the =
Internet.  Those plans have largely failed.  I think an incremental =
approach like DKIM has a better chance, but it is obviously vulnerable =
to being dismissed by those who see a small improvement as not worth =
bothering with.  The best is the enemy of the good.  -- Nathaniel


On Jul 31, 2011, at 6:12 AM, Hector Santos wrote:

> You continue to not comprehend (or rather ignore) what continues to =
plaque DKIM - the lack of fault detection. Its why it continues to have =
a hard time and have people who actually believe in this promising =
protocol "bitch" about it.  If these "big email" providers (or anyone =
for that matter) begin to make assertions about what is good about their =
mail then they better be ready for the violations of such assertions to =
be rejected.  You can't have it just one way and mandate this is the =
only way to process this overhead - looking for good mail only and =
ignoring all the violations and illogically treating it like it was =
never signed or compromised or attempted to be compromised.
>=20
> The overall difficulty is that originality is lost - the original =
author or dkim signer has lost or lacks any protocol guidance to tell =
resigners that the mail they are about the process might be bad - =
according to the original author domain.
>=20
> If the resigner is going to intentionally and neglectfully ignore all =
original claims about the original domain signing practice, then how do =
you expect the anonymous "copy-cat" abuse to be controlled?
>=20
>=20
> Murray S. Kucherawy wrote:
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of t.petch
>>> Sent: Saturday, July 30, 2011 3:26 AM
>>> To: Barry Leiba
>>> Cc: ietf
>>> Subject: Re: DKIM Signatures now being applied to IETF Email
>>>=20
>>> Sadly, I do not see it being used in the mailing lists where an
>>> organisation is sending me directly data I would like to be able to =
rely on
>>> - which I think fits the applicability well - and instead, I see it
>>> being used on a mailing list such as those in the IETF where I
>>> believe that the costs outweigh the benefits - and I have no choice
>>> about that:-(.
>> There has been some post-DKIM talk recently about the idea of =
"transient trust", wherein (to use this example) ietf.org would verify =
the signature on an arriving list submission, attach an RFC5451 header =
field that indicates the results of that verification, then send the =
message out to the list with that added field and a new ietf.org =
signature that "covered" it.  Then, if you decide to believe ietf.org's =
claims about the original signature, you know more than you would =
otherwise.
>> This hasn't been widely deployed yet, but some big email providers =
are currently playing with the idea.
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> --=20
> Hector Santos, CTO
> http://www.santronics.com
> http://santronics.blogspot.com
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From tnadeau@lucidvision.com  Mon Aug  1 06:12:57 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C2B11E8077 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 06:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t15CsB2I74BS for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 06:12:57 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id A3D9A5E800E for <ietf@ietf.org>; Mon,  1 Aug 2011 06:12:38 -0700 (PDT)
Received: from [192.168.1.133] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id C7B841D42F9E; Mon,  1 Aug 2011 09:12:24 -0400 (EDT)
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com>
Date: Mon, 1 Aug 2011 09:12:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com>
To: Eric Burger <eburger-l@standardstrack.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 13:12:58 -0000

	I'd actually vote for NO meetings on Fridays. %90 of attendees =
fly home on Friday if at all possible, especially since most of us have =
flown in on Sunday.  Unless you are local to the meeting, it is a major =
hassle leaving after the meetings on Friday, especially if you are =
international, since you are unlikely to make your flight and then are =
forced to stay another night.  This adds to the expenses of the trip, =
which most companies are now very sensitive to. This added day is =
especially evident if you are in some relatively obscure location as was =
last summer's meeting or the last one in Japan, that had no easy direct =
access to a major airport other than several hours of train/travel.  =
Blowing nearly 2 weekends in a row for each IETF meeting is not the way =
forward if you ask me. 8)

	--Tom


On Jul 31, 2011, at 11:48 AM, Eric Burger wrote:

> I don't think I have seen a proposal like this before.  I really like =
it, as there are a bunch of post-IETF stuff, some of which starts in the =
afternoon and thus conflicts with the IETF. This fixes that problem, =
enables us to have the same amount of meeting time, and potentially lets =
people get home a day early.
>=20
> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
>=20
>> Howdy,
>> First I'd like to thank the organizers for IETF-81 for another =
well-run meeting.  The logistics and coordination for such an event must =
be daunting, and I know we (the attendees) tend to focus on the =
negatives rather than the positives... but we really are thankful for =
all the time and effort put into it.  Thank you!
>>=20
>> I would also like to propose a small change for future meetings.  On =
Friday, instead of having a 2.5 hour WG meeting, followed by a 1.5 hour =
lunch break, followed by 2 hours of WG meetings... perhaps we could just =
have 4.5 hours of WG meetings straight and also start a bit earlier? =20
>>=20
>> Something like this:
>> 8:30-11:00 Session I
>> 11:15-12:15 Session II
>> 12:30-13:30 Session III
>> End
>>=20
>> That way the people who need to get to an airport get more time, or =
fewer of them have to miss WG meetings, etc.  And it would help reduce =
costs for attendees if they can avoid staying Friday night at the hotel. =
 And lunch at 13:30 doesn't seem unreasonable (to me).
>>=20
>> I apologize if this has been brought up before.  I tried to find it =
from an old email thread for the "Experiment" at IETF-73 which added the =
Friday afternoon sessions, but did not see this proposal being =
suggested.
>>=20
>> -hadriel
>>=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 john@jlc.net  Mon Aug  1 06:39:32 2011
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13AB011E8089 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 06:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.28
X-Spam-Level: 
X-Spam-Status: No, score=-106.28 tagged_above=-999 required=5 tests=[AWL=-0.281, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEgKoTMjHw7s for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 06:39:31 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1544721F8BAA for <ietf@ietf.org>; Mon,  1 Aug 2011 06:39:31 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id CAD5933C21; Mon,  1 Aug 2011 09:39:35 -0400 (EDT)
Date: Mon, 1 Aug 2011 09:39:35 -0400
From: John Leslie <john@jlc.net>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: A modest proposal for Friday meeting schedule
Message-ID: <20110801133935.GC89723@verdi>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com>
User-Agent: Mutt/1.4.1i
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 13:39:32 -0000

Thomas Nadeau <tnadeau@lucidvision.com> wrote:
> On Jul 31, 2011, at 11:48 AM, Eric Burger wrote:
>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
>> 
>>> Something like this:
>>> 8:30-11:00 Session I
>>> 11:15-12:15 Session II
>>> 12:30-13:30 Session III
>> 
>> I really like it, as there are a bunch of post-IETF stuff, some of
>> which starts in the afternoon and thus conflicts with the IETF.
> 
> I'd actually vote for NO meetings on Fridays...

   We have been trying to treat Friday as a "real" day for a year or so,
and it's only partly working.

   For IETF81, I'd have to rate the Friday TSVWG and V6OPS an a success
(though I was barely functional by then). Squeezing them into the
Monday-Thursday schedule would have made for serious conflicts.

   We need some improved paradigms...

   For one, I suggest we take remote-participation _seriously_ for the
Friday meetings. Many of us are waiting-for-Godot at airports on Friday,
and could certainly wear a headphone/mike and watch our laptop screens.
Meetecho seemed ready to manage that sort of thing. :^)

--
John Leslie <john@jlc.net>

From dimitri.papadimitriou@alcatel-lucent.com  Mon Aug  1 06:41:12 2011
Return-Path: <dimitri.papadimitriou@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA1611E80AD for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 06:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xPSEZSFp7Ja6 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 06:41:11 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 6290F11E8089 for <ietf@ietf.org>; Mon,  1 Aug 2011 06:41:11 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p71Db9kg030692 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 1 Aug 2011 15:37:10 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Mon, 1 Aug 2011 15:37:09 +0200
From: "Papadimitriou, Dimitri (Dimitri)" <dimitri.papadimitriou@alcatel-lucent.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, IETF-Discussion list <ietf@ietf.org>
Date: Mon, 1 Aug 2011 15:37:09 +0200
Subject: RE: A modest proposal for Friday meeting schedule
Thread-Topic: A modest proposal for Friday meeting schedule
Thread-Index: AcxPmBpixpbwtezNTTGCAyx7fK66JgAtdD9A
Message-ID: <EFDB2B5417263843B5077E12666D8C10187C5FA4@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>
In-Reply-To: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.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-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 13:41:12 -0000

Interesting proposal. It could be as proposed with 3 sessions or with 2 ses=
sions and 1/2 hour break between Session I and II depending on the needs (b=
oth would still give 4h30 of meeting):
08:30-11:00 Session I
11:30-13:30 Session II

Thanks,
-dimitri.

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
> Behalf Of Hadriel Kaplan
> Sent: Sunday, July 31, 2011 5:40 PM
> To: IETF-Discussion list
> Subject: A modest proposal for Friday meeting schedule
>=20
> Howdy,
> First I'd like to thank the organizers for IETF-81 for=20
> another well-run meeting.  The logistics and coordination for=20
> such an event must be daunting, and I know we (the attendees)=20
> tend to focus on the negatives rather than the positives...=20
> but we really are thankful for all the time and effort put=20
> into it.  Thank you!
>=20
> I would also like to propose a small change for future=20
> meetings.  On Friday, instead of having a 2.5 hour WG=20
> meeting, followed by a 1.5 hour lunch break, followed by 2=20
> hours of WG meetings... perhaps we could just have 4.5 hours=20
> of WG meetings straight and also start a bit earlier? =20
>=20
> Something like this:
> 8:30-11:00 Session I
> 11:15-12:15 Session II
> 12:30-13:30 Session III
> End
>=20
> That way the people who need to get to an airport get more=20
> time, or fewer of them have to miss WG meetings, etc.  And it=20
> would help reduce costs for attendees if they can avoid=20
> staying Friday night at the hotel.  And lunch at 13:30=20
> doesn't seem unreasonable (to me).
>=20
> I apologize if this has been brought up before.  I tried to=20
> find it from an old email thread for the "Experiment" at=20
> IETF-73 which added the Friday afternoon sessions, but did=20
> not see this proposal being suggested.
>=20
> -hadriel
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> =

From tnadeau@lucidvision.com  Mon Aug  1 07:14:25 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8934721F8D77 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.241
X-Spam-Level: 
X-Spam-Status: No, score=-2.241 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUP6MbSo6Igi for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:14:25 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id D439A21F8CDB for <ietf@ietf.org>; Mon,  1 Aug 2011 07:14:24 -0700 (PDT)
Received: from [192.168.1.133] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 00AB01D447CA; Mon,  1 Aug 2011 10:14:27 -0400 (EDT)
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <20110801133935.GC89723@verdi>
Date: Mon, 1 Aug 2011 10:14:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <34247C00-9293-40CC-879A-50D5BFC1669E@lucidvision.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1244.3)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 14:14:25 -0000

On Aug 1, 2011, at 9:39 AM, John Leslie wrote:

> Thomas Nadeau <tnadeau@lucidvision.com> wrote:
>> On Jul 31, 2011, at 11:48 AM, Eric Burger wrote:
>>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
>>>=20
>>>> Something like this:
>>>> 8:30-11:00 Session I
>>>> 11:15-12:15 Session II
>>>> 12:30-13:30 Session III
>>>=20
>>> I really like it, as there are a bunch of post-IETF stuff, some of
>>> which starts in the afternoon and thus conflicts with the IETF.
>>=20
>> I'd actually vote for NO meetings on Fridays...
>=20
>   We have been trying to treat Friday as a "real" day for a year or =
so,
> and it's only partly working.
>=20
>   For IETF81, I'd have to rate the Friday TSVWG and V6OPS an a success
> (though I was barely functional by then). Squeezing them into the
> Monday-Thursday schedule would have made for serious conflicts.
>=20
>   We need some improved paradigms...
>=20
>   For one, I suggest we take remote-participation _seriously_ for the
> Friday meetings. Many of us are waiting-for-Godot at airports on =
Friday,
> and could certainly wear a headphone/mike and watch our laptop =
screens.
> Meetecho seemed ready to manage that sort of thing. :^)

	That may work, but it does require that someone be at the =
meeting venue while the rest sit in the airport.

	--Tom


>=20
> --
> John Leslie <john@jlc.net>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From moore@network-heretics.com  Mon Aug  1 07:14:50 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 057FD21F8D7C for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.984
X-Spam-Level: 
X-Spam-Status: No, score=-2.984 tagged_above=-999 required=5 tests=[AWL=-0.385, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id se55EVMuVo-i for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:14:49 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 7B13F21F8D80 for <ietf@ietf.org>; Mon,  1 Aug 2011 07:14:49 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1QntGh-0008Gx-Qh; Mon, 01 Aug 2011 10:14:55 -0400
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110801133935.GC89723@verdi>
Date: Mon, 1 Aug 2011 10:14:53 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <4A474B96-C6E2-4F54-B9C9-83A40C6AF543@network-heretics.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da9409ee86cc8dfd8ba0b415e20781622d5c4350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 14:14:50 -0000

On Aug 1, 2011, at 9:39 AM, John Leslie wrote:

>   For one, I suggest we take remote-participation _seriously_ for the
> Friday meetings. Many of us are waiting-for-Godot at airports on Friday,
> and could certainly wear a headphone/mike and watch our laptop screens.

Interesting idea...though would the airport WiFi have the capacity for that?

Keith




From moore@network-heretics.com  Mon Aug  1 07:19:56 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96F9D21F8DC2 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.979
X-Spam-Level: 
X-Spam-Status: No, score=-2.979 tagged_above=-999 required=5 tests=[AWL=-0.380, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o5xipewmS+Zd for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:19:56 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3D021F8C53 for <ietf@ietf.org>; Mon,  1 Aug 2011 07:19:56 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1QntLb-0003l7-KT; Mon, 01 Aug 2011 10:19:59 -0400
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <34247C00-9293-40CC-879A-50D5BFC1669E@lucidvision.com>
Date: Mon, 1 Aug 2011 10:19:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <627B3195-F41B-40B3-B030-3F90DC225AA9@network-heretics.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi> <34247C00-9293-40CC-879A-50D5BFC1669E@lucidvision.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940659c7646fb6a1eeef9e5bd8596ee7847350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
Cc: John Leslie <john@jlc.net>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 14:19:56 -0000

On Aug 1, 2011, at 10:14 AM, Thomas Nadeau wrote:
>=20
> 	That may work, but it does require that someone be at the =
meeting venue while the rest sit in the airport.

Or we could all just meet at the airport.  :) =20

I suspect that one of the many problems with trying to depend on remote =
participation from the airport is that our travel schedules will vary =
considerably.  So some of us will be in taxis headed to the airport, =
others will already be on airplanes (but could participate from the next =
airport), etc.

We might be better off trying to schedule remote follow-up meetings the =
following week.  But by then, of course, the Real World will have =
intruded.

Keith


From peter@denic.de  Mon Aug  1 07:22:15 2011
Return-Path: <peter@denic.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BFA21F8DBF for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:22:15 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2EiVBYWZVAi for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:22:14 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id 5C18121F8C53 for <ietf@ietf.org>; Mon,  1 Aug 2011 07:22:14 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QntNr-0007pd-Vr; Mon, 01 Aug 2011 16:22:20 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QntNr-0008MT-Rz; Mon, 01 Aug 2011 16:22:19 +0200
Date: Mon, 1 Aug 2011 16:22:19 +0200
From: Peter Koch <pk@ISOC.DE>
To: ietf@ietf.org
Subject: Re: RFC 6302: "Internet-Facing Server Logging": No Word about Privacy?
Message-ID: <20110801142219.GQ2998@x27.adm.denic.de>
References: <A7A1E90D-AE24-401C-8B29-A3DA7252401A@gmx.net> <069601cc4c8a$18c9d4e0$4a5d7ea0$@com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <069601cc4c8a$18c9d4e0$4a5d7ea0$@com>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 14:22:15 -0000

On Wed, Jul 27, 2011 at 02:22:08PM -0400, Dan Wing wrote:

> It's trying to say that today, servers routinely log:
> 
>   * timestamp
>   * source IPv4 address
>   * resource accessed
> 
> and that servers, compliant with RFC6302, need to additionally log:
> 
>   * source port

at least the abstract says:

   In the wake of IPv4 exhaustion and deployment of IP address sharing
   techniques, this document recommends that Internet-facing servers log
   port number and accurate timestamps in addition to the incoming IP
   address.

I'd understand when people regard this as encouraging logging.

Also in the later text it is hard to identify the precondition that
address logging was in place for whatever reason and only then the
address sharing considerations come into play.  Maybe instead of
making rcommendations on the providing side it would have been better
to address the - no longer justified - assumptions that the consuming
side may have.

-Peter

From jeroen@unfix.org  Mon Aug  1 05:11:12 2011
Return-Path: <jeroen@unfix.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F9B21F8CEF; Mon,  1 Aug 2011 05:10:41 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AY1H3AHQ4BDT; Mon,  1 Aug 2011 05:10:32 -0700 (PDT)
Received: from icaras.de.unfix.org (icaras.de.unfix.org [IPv6:2a01:4f8:130:74c1:5054:ff:fec4:f7d4]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC3921F8D39; Mon,  1 Aug 2011 05:10:32 -0700 (PDT)
Received: from yomi.ch.unfix.org (yomi.ch.unfix.org [IPv6:2001:41e0:ff42:99:ca2a:14ff:fe1f:2b7b]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by icaras.de.unfix.org (Postfix) with ESMTPSA id 8A048801C2BF; Mon,  1 Aug 2011 14:10:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unfix.org; s=DKIM2009; t=1312200632; bh=MXlCJQLBZHU46Sg4UGG3nkqOp6egFAsSJg2L+to3zts=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=MKjYcL4sGPF+j5a0mFlNLSqt3NDjU2jLi1+t2tgLS1uDBTlPQvfd3C5d3b4KT7r3Z kfPO6zb9YRGyrYSVNqnmW0gszFP/Qw6TsWW3yjJo5i1BoGpWSs4salyKcBjkuEQkZS NwPaNTkkCygDXXH3U+a9XS1ND9en3TD0H8pHRlKWGs7iJaG5ThTgEGhHP1UcJY161Y bwU9hejvH8Up5WOOzW7O3alc9UEAzKKhNH62TaqCZyL6gW0jdGYbxI4I68rx/PDtxO 1kn4njFTkrP//5HKN00orY0jF4/CKxOFHh1Vat3FNLDO84kKgNIjYfxop+Sq7WjAAd uEQR32cau/Qxw==
Message-ID: <4E3697B8.1010603@unfix.org>
Date: Mon, 01 Aug 2011 14:10:32 +0200
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net> <4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com> <13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net> <4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com> <20110727023833.5C72D1232958@drugs.dv.isc.org> <968F0B1C-D082-4A59-8213-FD58C74AF89D@nominum.com> <20110727151517.CF9371235D70@drugs.dv.isc.org> <D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <EMEW3|fcf145b5033ff99790b7c34003f47686n6QGZC03tjc|ecs.soton.ac.uk|D0D20EB6-78C9-415D-9493-3AA08FAACEEF@ecs.soton.ac.uk> <999C3229-649D-4242-BB0F-2BB494EDF1D9@network-heretics.com> <4E305E3E.2040607@unfix.org> <20110727233634.406021238970@drugs.dv.isc.org> <4E3127F1.2030708@unfix.org> <20110730010626.05D3212542D0@drugs.dv.isc.org>
In-Reply-To: <20110730010626.05D3212542D0@drugs.dv.isc.org>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 01 Aug 2011 07:34:26 -0700
Cc: IPv6 Operations <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 12:11:13 -0000

On 2011-07-30 03:06 , Mark Andrews wrote:
> In message <4E3127F1.2030708@unfix.org>, Jeroen Massar writes:
>> On 2011-07-28 01:36 , Mark Andrews wrote:
>> [..]
>>> Is there *one* tunnel management protocol that they all support or
>>> does a cpe vendor have to implement multiple ones to reach them
>>> all?  I'm pretty sure I know the answer to this question but I'd
>>> love to be proved wrong.
>>
>> There is no 'one' solution to the problems that they are solving.
>>
>> As such there tend to be a combo of:
>>  - static proto-41 tunnel
>>  - 6to4
>>  - 6rd
>>  - TSP => dynamic NATted addresses
>>  - proto-41 + heartbeat + TIC => dynamic public addresses
>>  - AYIYA + TIC => dynamic NATted addresses
> 
> I was more thinking about commonality with tunnel brokers.

These all are implemented by "tunnelbrokers", be they tunnel brokers
where you can just fill in the details yourself (6to4) or the others
where the parameters are provided by the entity you want to connect to.

> 6rd is not a replacement for 6to4 as it requires ISP involment or
> someone to create a registry of 3rd party 6rd providers along with
> associated parameters sets similar non anycast 6to4.

6rd is then also intended for a per ISP deployment.

> static proto-41
> tunnel is also not a viable replacement as it doesn't handle address
> reassignment at the CPE end.

See the "proto-41 + heartbeat" option, that is standard proto-41 but
with a side-channel which beats where the endpoint currently is.

But why are you trying to replace 6to4? What are the requirements that
you have that are not satisfied by any of the above methods?

Greets,
 Jeroen

From john@jlc.net  Mon Aug  1 07:48:48 2011
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E56B21F8CE2 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.569
X-Spam-Level: 
X-Spam-Status: No, score=-106.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fKrZDRMqgVcu for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:48:48 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 19A3221F8CDE for <ietf@ietf.org>; Mon,  1 Aug 2011 07:48:47 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 476D133C25; Mon,  1 Aug 2011 10:48:54 -0400 (EDT)
Date: Mon, 1 Aug 2011 10:48:54 -0400
From: John Leslie <john@jlc.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: A modest proposal for Friday meeting schedule
Message-ID: <20110801144854.GD89723@verdi>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi> <4A474B96-C6E2-4F54-B9C9-83A40C6AF543@network-heretics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A474B96-C6E2-4F54-B9C9-83A40C6AF543@network-heretics.com>
User-Agent: Mutt/1.4.1i
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 14:48:48 -0000

Keith Moore <moore@network-heretics.com> wrote:
> On Aug 1, 2011, at 9:39 AM, John Leslie wrote:
> 
> >   For one, I suggest we take remote-participation _seriously_ for the
> > Friday meetings. Many of us are waiting-for-Godot at airports on Friday,
> > and could certainly wear a headphone/mike and watch our laptop screens.
> 
> Interesting idea...though would the airport WiFi have the capacity for
> that?

   They _should_... ;^)

   Actually, I would expect airports to be better equipped for this than
hotels, and we've made substantial progress training hotels. ;^)

   If it's _only_ the WiFi that's an issue, I'm _quite_ sure we could
show them how to fix that!

--
John Leslie <john@jlc.net>

From ynir@checkpoint.com  Mon Aug  1 07:49:04 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12A2321F8CF0 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.487
X-Spam-Level: 
X-Spam-Status: No, score=-10.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSFkocjNtJ2R for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 07:49:03 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id B862721F8CEF for <ietf@ietf.org>; Mon,  1 Aug 2011 07:49:02 -0700 (PDT)
X-CheckPoint: {4E36CA6C-4-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p71En6Ys029559;  Mon, 1 Aug 2011 17:49:07 +0300
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 1 Aug 2011 17:49:06 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Mon, 1 Aug 2011 17:49:06 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Keith Moore <moore@network-heretics.com>, John Leslie <john@jlc.net>
Date: Mon, 1 Aug 2011 17:49:13 +0300
Subject: Re: A modest proposal for Friday meeting schedule
Thread-Topic: A modest proposal for Friday meeting schedule
Thread-Index: AcxQWikLlqnry7nETJyGUksZju4dyw==
Message-ID: <CA5C972C.497C%ynir@checkpoint.com>
In-Reply-To: <4A474B96-C6E2-4F54-B9C9-83A40C6AF543@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.12.0.110505
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 14:49:04 -0000

On 8/1/11 5:14 PM, "Keith Moore" <moore@network-heretics.com> wrote:

>On Aug 1, 2011, at 9:39 AM, John Leslie wrote:
>
>>   For one, I suggest we take remote-participation _seriously_ for the
>> Friday meetings. Many of us are waiting-for-Godot at airports on Friday,
>> and could certainly wear a headphone/mike and watch our laptop screens.
>
>Interesting idea...though would the airport WiFi have the capacity for
>that?

One data point: On Friday, the DHCP server was not responding at Quebec
air port from 11:45 to 12:15. Then it suddenly came back.  Guess all those
IETFers (there were 10 of us) were taxing it to its limits.


From housley@vigilsec.com  Mon Aug  1 08:10:19 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74E5321F8B0A for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 08:10:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.7
X-Spam-Level: 
X-Spam-Status: No, score=-102.7 tagged_above=-999 required=5 tests=[AWL=-0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6hM1QtkbzHI for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 08:10:18 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id C92D721F8B06 for <ietf@ietf.org>; Mon,  1 Aug 2011 08:10:18 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5638CF24131 for <ietf@ietf.org>; Mon,  1 Aug 2011 11:10:25 -0400 (EDT)
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 zDv7ucMPDh2t for <ietf@ietf.org>; Mon,  1 Aug 2011 11:10:11 -0400 (EDT)
Received: from [192.168.2.100] (pool-71-178-218-214.washdc.fios.verizon.net [71.178.218.214]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 851E9F24127 for <ietf@ietf.org>; Mon,  1 Aug 2011 11:11:05 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: A modest proposal for Friday meeting schedule
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20110801133935.GC89723@verdi>
Date: Mon, 1 Aug 2011 11:10:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 15:10:19 -0000

I am discussing the possibility with the Secretariat and the IESG.  I =
will report back to the community as soon as possible.

Russ


>>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
>>>=20
>>>> Something like this:
>>>> 8:30-11:00 Session I
>>>> 11:15-12:15 Session II
>>>> 12:30-13:30 Session III
>>>=20
>>> I really like it, as there are a bunch of post-IETF stuff, some of
>>> which starts in the afternoon and thus conflicts with the IETF.


From stpeter@stpeter.im  Mon Aug  1 08:18:56 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B93111E80A4 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 08:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Upeyn8AMgU8 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 08:18:55 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 75F4611E809C for <ietf@ietf.org>; Mon,  1 Aug 2011 08:18:55 -0700 (PDT)
Received: from squire.local (unknown [216.17.251.72]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0EE9A41309; Mon,  1 Aug 2011 09:20:16 -0600 (MDT)
Message-ID: <4E36C3E3.6050500@stpeter.im>
Date: Mon, 01 Aug 2011 09:18:59 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>	<12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E343791.7040401@qualcomm.com> <4E3439CE.4030509@joelhalpern.com>
In-Reply-To: <4E3439CE.4030509@joelhalpern.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 15:18:56 -0000

On 7/30/11 11:05 AM, Joel M. Halpern wrote:
> It seems to me that this does two things, both small but useful.
> 1) It makes a minor change in the advancement procedures so that they
> are more reasonable.  They may still not be sufficiently reasonable to
> be used, but it improves them, and thereby improves the odds.
> 2) It is coupled to an intent to actually behave according to what the
> document says.  Such an intent is obviously not feasible without some
> change.  It is useful to have our behavior and our documented
> description of how we work match because the mismatch causes confusion,
> at least for new participants, and sometimes even for experienced
> participants.
> 
> It might be the case that it will improve the advancement percentage. It
> might not.  I can not imagine that it will make that even worse.

I'm with Joel here. Let's clean up our documentation so that it more
closely matches our current practice. We might even encourage more folks
to progress their work along the standards track, although I think that
failing is more cultural than procedural.

> So, it seems to me that this matches the description that Eric, Brian,
> and others have used of a baby step that is not harmful and may be helpful.

The "baby step" description is a metaphor. If we can't make even this
small change, how can we expect to complete more significant reforms?

BTW, the latest version more clearly describes the problem it is trying
to solve, so I think that my DISCUSS has been addressed. I'm clearing
the DISCUSS and now approve of publishing this I-D as an RFC.

Peter

--
Peter Saint-Andre
https://stpeter.im/


From scott@kitterman.com  Mon Aug  1 08:41:29 2011
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF2011E80C9 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 08:41:29 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWMiWaHdkM7v for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 08:41:28 -0700 (PDT)
Received: from mailout00.controlledmail.com (mailout00.controlledmail.com [72.81.252.19]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0F411E80A6 for <ietf@ietf.org>; Mon,  1 Aug 2011 08:41:28 -0700 (PDT)
Received: from mailout00.controlledmail.com (localhost [127.0.0.1]) by mailout00.controlledmail.com (Postfix) with ESMTP id DCFD838C12F; Mon,  1 Aug 2011 11:41:32 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1312213293; bh=OlF3h5Bx0pt0BxMWeVUg7ffn243rB5smoRaoHUrS5+w=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=aBmUC2NtzS1HaiVjBUpaYLsSvZodPxGX8KZOwkwSkrBpPHdLMx+JNnlJCrNL3c65e VwBmBQ5m7P9dcHCbXryhOyehmGLKV/P+1t6Dk95SX12+mcYUbL0T6/XlY1rElM+ZKu DzpLsph6s2f3A9wiVg+1lM7DQzuaZNOo2cJ3Z+3g=
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
Date: Mon, 1 Aug 2011 11:41:29 -0400
User-Agent: KMail/1.13.6 (Linux/2.6.38-10-generic-pae; KDE/4.6.2; i686; ; )
References: <20110725171748.GA13506@amsl.com> <4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>
In-Reply-To: <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201108011141.30549.scott@kitterman.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 15:41:29 -0000

On Monday, August 01, 2011 08:48:04 AM Nathaniel Borenstein wrote:
> I find it amazing how many different ways there are to criticize DKIM for
> not doing something it was never intended to do.  DKIM is a small building
> block that enables new functionality, but such functionality is beyond the
> scope of DKIM.
> 
> DKIM does one thing, and one thing only:  It uses a cryptographic signature
> to associate a domain with a message.  By doing so, it creates strong
> evidence that the message passed through that domain at some point and has
> not been significantly m

...

In fairness to Hector, the functionality that he is complaining is missing was 
part of the original working group charter.  I think it's unfortunate (and I 
said so at the time) that the group chose to define a core DKIM protocol first 
and then attempt to bolt a policy mechanism on afterwards.  It's rather not 
suprising it didn't work out well (ADSP).

So you are correct, it does one thing and one thing only, but that's because 
the WG decided to build it that way, not because the WG was limited to that.  

Of course, now, it is what it is and there's no changing that, but I also 
think it's reasonable to think it could have been done better.

Scott K

P.S. It's possible I may mis-remember WG versus pre-WG discussions here, but 
either way it was a poor (IMO) way to attempt to tackle the work.

From mrw@lilacglade.org  Mon Aug  1 09:46:32 2011
Return-Path: <mrw@lilacglade.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AF211E8077 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 09:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.335
X-Spam-Level: 
X-Spam-Status: No, score=-101.335 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iaaIR85vxhCr for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 09:46:31 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 9CDA621F8D42 for <ietf@ietf.org>; Mon,  1 Aug 2011 09:46:31 -0700 (PDT)
Received: from [10.36.0.36] (pool-108-7-232-64.bstnma.fios.verizon.net [108.7.232.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 24546202B2 for <ietf@ietf.org>; Mon,  1 Aug 2011 12:49:02 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: A modest proposal...
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>
Date: Mon, 1 Aug 2011 12:45:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 16:46:32 -0000

Hi All,

Within the IETF, it has become common to use the term a "A Modest =
Proposal..." as a title for actual proposals for process change within =
the IETF.  This causes some cultural dissonance for me, personally, and  =
I want to make sure that people are aware of the origin of this term, =
and the potential for misinterpretation of proposals that are titled =
this way.

It is not my intention to criticize Hadriel, or anyone else who has used =
this phrase.  I am sure that no one who has used this term has intended =
to be offensive to me or to anyone else.  I am not personally offended, =
and I am not looking for an apology.   I just want to make sure that =
people understand how the use of this term resonates with  me, =
personally, and potentially with others.=20

The original article by Jonathan Swift, titled, "A Modest Proposal...",  =
was a satirical suggestion that widespread famine and poverty in Ireland =
could be addressed by the Irish selling their children to the wealthy as =
a source of food (http://art-bin.com/art/omodest.html).  This was a very =
loaded article that made an outrageous proposal, clearly not one that =
was meant to be taken seriously.  This article has been interpreted in =
many different ways, though.  Despite the fact that the article may have =
been intended to be supportive of the Irish cause (by satirizing =
England's indifference to Irish poverty and famine), the article was, =
nonetheless, highly offensive to many Irish people for a number of =
reasons.  Although i can't personally see it, I have also been assured =
that the article is uproariously funny.  Whether you find the article =
offensive or humorous, though, "A Modest Proposal..." is a culturally =
charged  reminder of a very difficult time in Irish/English history, and =
the term is likely to evoke complex feelings in people who are still =
culturally sensitive about that topic.

So, if you are making a satirical, uproariously funny suggestion that =
you do not intend to be taken seriously, but that might be =
misinterpreted as incredibly offensive to all parties involved, then "A =
Modest Proposal.." might be just the right title...  (Although you might =
want to think twice before you hit "send" :-)).

But, if you are making a serious proposal for how to improve things in =
the IETF, I would personally feel more comfortable, and therefore better =
disposed toward your suggestion, if you would not use the term "A Modest =
Proposal.." to describe it.

You are, of course, free to use any title you wish for your own =
proposals...  My only purpose in sending this mail is to educate people =
who might not be aware of the history of this particular phrase, so that =
they might have a better basis for deciding whether or not to use "A =
Modest Proposal..." in the titles of their own proposals.

Thank you for listening,
Margaret


From hartmans@mit.edu  Mon Aug  1 09:51:09 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A365D21F8ED0; Mon,  1 Aug 2011 09:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.126
X-Spam-Level: 
X-Spam-Status: No, score=-104.126 tagged_above=-999 required=5 tests=[AWL=-1.861, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VH7KF+vc6MiK; Mon,  1 Aug 2011 09:51:09 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 35A5521F8ECC; Mon,  1 Aug 2011 09:51:09 -0700 (PDT)
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 5CE6A202B2; Mon,  1 Aug 2011 12:54:00 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2A3E3422B; Mon,  1 Aug 2011 12:51:11 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org,secdir@ietf.org
Subject: secdir review of draft-ietf-msec-gdoi-update
Date: Mon, 01 Aug 2011 12:51:11 -0400
Message-ID: <tsl8vrd2hz4.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: draft-ietf-msec-gdoi-update@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 16:51:09 -0000

This update to the GDOI specification significantly improves clarity and
readability.
However, there is one issue that I think should be addressed prior to
publication:


At the top of page 11, the spec claims that a seq payload protects
against group members responding to groupkey-pull messages sent prior to
joining the group.
I'm reasonably sure that should be groupkey-push messages; I believe the
nonce payloads provide replay protection for the pull exchange.

Actually, it's more complicated than that.  Section 3.3 also seems to
believe the sequence number is about pull exchanges. However it says
that  a GM should always expect the push message sequence number to be
reset to 1.
Why is that reasonable? If a group is ongoing, don't we want to tell new
members what the sequence number currently is rather than having them
assume it is 1? The push message is multicast, so we cannot maintain a
separate sequence number for each member.

I think either there is some sort of error with the description of the
replay mechanisms or it requires significantly more explanation.

From framefritti@gmail.com  Mon Aug  1 10:04:46 2011
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A2C111E80D5 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 10:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.533
X-Spam-Level: 
X-Spam-Status: No, score=-3.533 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQhyOPIHNHU3 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 10:04:45 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 320C711E80AB for <ietf@ietf.org>; Mon,  1 Aug 2011 10:04:45 -0700 (PDT)
Received: by qwc23 with SMTP id 23so3810406qwc.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 10:04:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ga39zICPCLp0WxcgQP4ng4Rd0SpL2NT7OpBi/Vk8pNQ=; b=Y9Pm9hwQ+XwiLvYTP3l+m6o5qcF+bWNkY1DXz/odP5bL7Qkeqn3JsmflTmjNId9CuP VZdxtE1qp5bB2j7+EYua10f/TkQHF537hlDNqkj0FycXBn9TGfK8A+5C5obBor4HHLgz ZuuKfTIa/iB9nCelPM4O6W8LHrYiXxiz9Dz98=
MIME-Version: 1.0
Received: by 10.229.21.194 with SMTP id k2mr3405809qcb.235.1312218287183; Mon, 01 Aug 2011 10:04:47 -0700 (PDT)
Received: by 10.229.84.208 with HTTP; Mon, 1 Aug 2011 10:04:47 -0700 (PDT)
In-Reply-To: <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org>
Date: Mon, 1 Aug 2011 19:04:47 +0200
Message-ID: <CABSMSPUvDbVki4FALbtJtg+mWWF6_fEX7FDmrzJuVsP2_MOZOg@mail.gmail.com>
Subject: Re: A modest proposal...
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=0016368322f0e016c004a974a041
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 17:04:46 -0000

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

Well, Margaret, thank you for the information (I am serious, not ironical).
I (and, I guess, many other IETFers) was not aware about this "historical"
usage of "A Modest proposal..." Although I did not make any proposal so far,
I would have used it out of modesty.  You know, to say "Listen, I have this
cute idea, maybe it is just a silly thing, but..."

I'll try to remember it, whenever I'll have something to propose.


Riccardo

2011/8/1 Margaret Wasserman <mrw@lilacglade.org>

>
> Hi All,
>
> Within the IETF, it has become common to use the term a "A Modest
> Proposal..." as a title for actual proposals for process change within the
> IETF.  This causes some cultural dissonance for me, personally, and  I want
> to make sure that people are aware of the origin of this term, and the
> potential for misinterpretation of proposals that are titled this way.
>
> It is not my intention to criticize Hadriel, or anyone else who has used
> this phrase.  I am sure that no one who has used this term has intended to
> be offensive to me or to anyone else.  I am not personally offended, and I
> am not looking for an apology.   I just want to make sure that people
> understand how the use of this term resonates with  me, personally, and
> potentially with others.
>
> The original article by Jonathan Swift, titled, "A Modest Proposal...",
>  was a satirical suggestion that widespread famine and poverty in Ireland
> could be addressed by the Irish selling their children to the wealthy as a
> source of food (http://art-bin.com/art/omodest.html).  This was a very
> loaded article that made an outrageous proposal, clearly not one that was
> meant to be taken seriously.  This article has been interpreted in many
> different ways, though.  Despite the fact that the article may have been
> intended to be supportive of the Irish cause (by satirizing England's
> indifference to Irish poverty and famine), the article was, nonetheless,
> highly offensive to many Irish people for a number of reasons.  Although i
> can't personally see it, I have also been assured that the article is
> uproariously funny.  Whether you find the article offensive or humorous,
> though, "A Modest Proposal..." is a culturally charged  reminder of a very
> difficult time in Irish/English history, an
>  d the term is likely to evoke complex feelings in people who are still
> culturally sensitive about that topic.
>
> So, if you are making a satirical, uproariously funny suggestion that you
> do not intend to be taken seriously, but that might be misinterpreted as
> incredibly offensive to all parties involved, then "A Modest Proposal.."
> might be just the right title...  (Although you might want to think twice
> before you hit "send" :-)).
>
> But, if you are making a serious proposal for how to improve things in the
> IETF, I would personally feel more comfortable, and therefore better
> disposed toward your suggestion, if you would not use the term "A Modest
> Proposal.." to describe it.
>
> You are, of course, free to use any title you wish for your own
> proposals...  My only purpose in sending this mail is to educate people who
> might not be aware of the history of this particular phrase, so that they
> might have a better basis for deciding whether or not to use "A Modest
> Proposal..." in the titles of their own proposals.
>
> Thank you for listening,
> Margaret
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Well, Margaret, thank you for the information (I am serious, not ironical).=
 I (and, I guess, many other IETFers) was not aware about this &quot;histor=
ical&quot; usage of &quot;A Modest proposal...&quot; Although I did not mak=
e any proposal so far, I would have used it out of modesty. =A0You know, to=
 say &quot;Listen, I have this cute idea, maybe it is just a silly thing, b=
ut...&quot;<div>
<br></div><div>I&#39;ll try to remember it, whenever I&#39;ll have somethin=
g to propose.=A0</div><div><br></div><div><br></div><div>Riccardo<br><br><d=
iv class=3D"gmail_quote">2011/8/1 Margaret Wasserman <span dir=3D"ltr">&lt;=
<a href=3D"mailto:mrw@lilacglade.org">mrw@lilacglade.org</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><br>
Hi All,<br>
<br>
Within the IETF, it has become common to use the term a &quot;A Modest Prop=
osal...&quot; as a title for actual proposals for process change within the=
 IETF. =A0This causes some cultural dissonance for me, personally, and =A0I=
 want to make sure that people are aware of the origin of this term, and th=
e potential for misinterpretation of proposals that are titled this way.<br=
>

<br>
It is not my intention to criticize Hadriel, or anyone else who has used th=
is phrase. =A0I am sure that no one who has used this term has intended to =
be offensive to me or to anyone else. =A0I am not personally offended, and =
I am not looking for an apology. =A0 I just want to make sure that people u=
nderstand how the use of this term resonates with =A0me, personally, and po=
tentially with others.<br>

<br>
The original article by Jonathan Swift, titled, &quot;A Modest Proposal...&=
quot;, =A0was a satirical suggestion that widespread famine and poverty in =
Ireland could be addressed by the Irish selling their children to the wealt=
hy as a source of food (<a href=3D"http://art-bin.com/art/omodest.html" tar=
get=3D"_blank">http://art-bin.com/art/omodest.html</a>). =A0This was a very=
 loaded article that made an outrageous proposal, clearly not one that was =
meant to be taken seriously. =A0This article has been interpreted in many d=
ifferent ways, though. =A0Despite the fact that the article may have been i=
ntended to be supportive of the Irish cause (by satirizing England&#39;s in=
difference to Irish poverty and famine), the article was, nonetheless, high=
ly offensive to many Irish people for a number of reasons. =A0Although i ca=
n&#39;t personally see it, I have also been assured that the article is upr=
oariously funny. =A0Whether you find the article offensive or humorous, tho=
ugh, &quot;A Modest Proposal...&quot; is a culturally charged =A0reminder o=
f a very difficult time in Irish/English history, an<br>

=A0d the term is likely to evoke complex feelings in people who are still c=
ulturally sensitive about that topic.<br>
<br>
So, if you are making a satirical, uproariously funny suggestion that you d=
o not intend to be taken seriously, but that might be misinterpreted as inc=
redibly offensive to all parties involved, then &quot;A Modest Proposal..&q=
uot; might be just the right title... =A0(Although you might want to think =
twice before you hit &quot;send&quot; :-)).<br>

<br>
But, if you are making a serious proposal for how to improve things in the =
IETF, I would personally feel more comfortable, and therefore better dispos=
ed toward your suggestion, if you would not use the term &quot;A Modest Pro=
posal..&quot; to describe it.<br>

<br>
You are, of course, free to use any title you wish for your own proposals..=
. =A0My only purpose in sending this mail is to educate people who might no=
t be aware of the history of this particular phrase, so that they might hav=
e a better basis for deciding whether or not to use &quot;A Modest Proposal=
...&quot; in the titles of their own proposals.<br>

<br>
Thank you for listening,<br>
Margaret<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></div>

--0016368322f0e016c004a974a041--

From marshall.eubanks@gmail.com  Mon Aug  1 10:06:18 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A6211E80E4 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 10:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.437
X-Spam-Level: 
X-Spam-Status: No, score=-103.437 tagged_above=-999 required=5 tests=[AWL=0.161, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7914HkUVIwR for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 10:06:17 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4760711E8077 for <ietf@ietf.org>; Mon,  1 Aug 2011 10:06:17 -0700 (PDT)
Received: by gxk19 with SMTP id 19so4276983gxk.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 10:06:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=g8rmvQSJlS3AKLxLJj5BbsP/3eqIf6qJyfcWZWRy7Ik=; b=f+FIPfGTZrjZs2//QxCjNv1A1U+b/3nnzJclavVNtCZ+bD+tNSI5Jkf3LcdRYgntSw 3SGbbESwVdvGiJEkWERAxtlJkBuhHpV82ruQRiAzVIxeoOCFk/QhdBpAkJrORHVSxT7t IQJGkee8v1tn10fcgjHsBc3/kQQO+rDlgKEqw=
MIME-Version: 1.0
Received: by 10.150.55.31 with SMTP id d31mr1039343yba.24.1312218383622; Mon, 01 Aug 2011 10:06:23 -0700 (PDT)
Received: by 10.151.98.21 with HTTP; Mon, 1 Aug 2011 10:06:23 -0700 (PDT)
In-Reply-To: <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org>
Date: Mon, 1 Aug 2011 13:06:23 -0400
Message-ID: <CAJNg7V+-6mzbP0ZNpaB=546obPRB6F0DnZdJkpbyCOfS=iBoTA@mail.gmail.com>
Subject: Re: A modest proposal...
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Margaret Wasserman <mrw@lilacglade.org>
Content-Type: multipart/alternative; boundary=000e0cd722669fa0d104a974a699
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 17:06:18 -0000

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

On Mon, Aug 1, 2011 at 12:45 PM, Margaret Wasserman <mrw@lilacglade.org>wrote:

>
> Hi All,
>
> Within the IETF, it has become common to use the term a "A Modest
> Proposal..." as a title for actual proposals for process change within the
> IETF.  This causes some cultural dissonance for me, personally, and  I want
> to make sure that people are aware of the origin of this term, and the
> potential for misinterpretation of proposals that are titled this way.
>
> It is not my intention to criticize Hadriel, or anyone else who has used
> this phrase.  I am sure that no one who has used this term has intended to
> be offensive to me or to anyone else.  I am not personally offended, and I
> am not looking for an apology.   I just want to make sure that people
> understand how the use of this term resonates with  me, personally, and
> potentially with others.
>
> The original article by Jonathan Swift, titled, "A Modest Proposal...",
>  was a satirical suggestion that widespread famine and poverty in


Note that he did have the sense to publish it anonymously.

Marshall


> Ireland could be addressed by the Irish selling their children to the
> wealthy as a source of food (http://art-bin.com/art/omodest.html).  This
> was a very loaded article that made an outrageous proposal, clearly not one
> that was meant to be taken seriously.  This article has been interpreted in
> many different ways, though.  Despite the fact that the article may have
> been intended to be supportive of the Irish cause (by satirizing England's
> indifference to Irish poverty and famine), the article was, nonetheless,
> highly offensive to many Irish people for a number of reasons.  Although i
> can't personally see it, I have also been assured that the article is
> uproariously funny.  Whether you find the article offensive or humorous,
> though, "A Modest Proposal..." is a culturally charged  reminder of a very
> difficult time in Irish/English history, an
>  d the term is likely to evoke complex feelings in people who are still
> culturally sensitive about that topic.
>
> So, if you are making a satirical, uproariously funny suggestion that you
> do not intend to be taken seriously, but that might be misinterpreted as
> incredibly offensive to all parties involved, then "A Modest Proposal.."
> might be just the right title...  (Although you might want to think twice
> before you hit "send" :-)).
>
> But, if you are making a serious proposal for how to improve things in the
> IETF, I would personally feel more comfortable, and therefore better
> disposed toward your suggestion, if you would not use the term "A Modest
> Proposal.." to describe it.
>
> You are, of course, free to use any title you wish for your own
> proposals...  My only purpose in sending this mail is to educate people who
> might not be aware of the history of this particular phrase, so that they
> might have a better basis for deciding whether or not to use "A Modest
> Proposal..." in the titles of their own proposals.
>
> Thank you for listening,
> Margaret
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

<br><br><div class=3D"gmail_quote">On Mon, Aug 1, 2011 at 12:45 PM, Margare=
t Wasserman <span dir=3D"ltr">&lt;<a href=3D"mailto:mrw@lilacglade.org">mrw=
@lilacglade.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hi All,<br>
<br>
Within the IETF, it has become common to use the term a &quot;A Modest Prop=
osal...&quot; as a title for actual proposals for process change within the=
 IETF. =A0This causes some cultural dissonance for me, personally, and =A0I=
 want to make sure that people are aware of the origin of this term, and th=
e potential for misinterpretation of proposals that are titled this way.<br=
>

<br>
It is not my intention to criticize Hadriel, or anyone else who has used th=
is phrase. =A0I am sure that no one who has used this term has intended to =
be offensive to me or to anyone else. =A0I am not personally offended, and =
I am not looking for an apology. =A0 I just want to make sure that people u=
nderstand how the use of this term resonates with =A0me, personally, and po=
tentially with others.<br>

<br>
The original article by Jonathan Swift, titled, &quot;A Modest Proposal...&=
quot;, =A0was a satirical suggestion that widespread famine and poverty in =
</blockquote><div><br></div><div>Note that he did have the sense to publish=
 it anonymously.=A0</div>
<div><br></div><div>Marshall</div><div>=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">Ireland could be addressed by the Irish selling their children to the =
wealthy as a source of food (<a href=3D"http://art-bin.com/art/omodest.html=
" target=3D"_blank">http://art-bin.com/art/omodest.html</a>). =A0This was a=
 very loaded article that made an outrageous proposal, clearly not one that=
 was meant to be taken seriously. =A0This article has been interpreted in m=
any different ways, though. =A0Despite the fact that the article may have b=
een intended to be supportive of the Irish cause (by satirizing England&#39=
;s indifference to Irish poverty and famine), the article was, nonetheless,=
 highly offensive to many Irish people for a number of reasons. =A0Although=
 i can&#39;t personally see it, I have also been assured that the article i=
s uproariously funny. =A0Whether you find the article offensive or humorous=
, though, &quot;A Modest Proposal...&quot; is a culturally charged =A0remin=
der of a very difficult time in Irish/English history, an<br>

=A0d the term is likely to evoke complex feelings in people who are still c=
ulturally sensitive about that topic.<br>
<br>
So, if you are making a satirical, uproariously funny suggestion that you d=
o not intend to be taken seriously, but that might be misinterpreted as inc=
redibly offensive to all parties involved, then &quot;A Modest Proposal..&q=
uot; might be just the right title... =A0(Although you might want to think =
twice before you hit &quot;send&quot; :-)).<br>

<br>
But, if you are making a serious proposal for how to improve things in the =
IETF, I would personally feel more comfortable, and therefore better dispos=
ed toward your suggestion, if you would not use the term &quot;A Modest Pro=
posal..&quot; to describe it.<br>

<br>
You are, of course, free to use any title you wish for your own proposals..=
. =A0My only purpose in sending this mail is to educate people who might no=
t be aware of the history of this particular phrase, so that they might hav=
e a better basis for deciding whether or not to use &quot;A Modest Proposal=
...&quot; in the titles of their own proposals.<br>

<br>
Thank you for listening,<br>
Margaret<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>

--000e0cd722669fa0d104a974a699--

From HKaplan@acmepacket.com  Mon Aug  1 10:08:37 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 526C111E812C for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 10:08:37 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtt8npDzGh3K for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 10:08:32 -0700 (PDT)
Received: from ETMail2.acmepacket.com (etmail2.acmepacket.com [216.41.24.9]) by ietfa.amsl.com (Postfix) with ESMTP id 8E70E11E8115 for <ietf@ietf.org>; Mon,  1 Aug 2011 10:08:32 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by ETMail2.acmepacket.com (216.41.24.9) with Microsoft SMTP Server (TLS) id 8.1.240.5; Mon, 1 Aug 2011 13:07:33 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Mon, 1 Aug 2011 13:08:38 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Margaret Wasserman <mrw@lilacglade.org>
Date: Mon, 1 Aug 2011 13:08:37 -0400
Subject: Re: A modest proposal...
Thread-Topic: A modest proposal...
Thread-Index: AcxQbacZ86dJ+64rR1yfAUIDm7ZsHQ==
Message-ID: <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org>
In-Reply-To: <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAUA=
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 17:08:37 -0000

Fascinating.  I had no idea that there even *was* such a phrase in common u=
sage, let alone that there was known etymology for it.  One learns somethin=
g new every day. =20
But I meant it quite literally: a moderate/humble/etc. proposal for Friday =
meeting schedule.=20

-hadriel


On Aug 1, 2011, at 12:45 PM, Margaret Wasserman wrote:

>=20
> Hi All,
>=20
> Within the IETF, it has become common to use the term a "A Modest Proposa=
l..." as a title for actual proposals for process change within the IETF.  =
This causes some cultural dissonance for me, personally, and  I want to mak=
e sure that people are aware of the origin of this term, and the potential =
for misinterpretation of proposals that are titled this way.
>=20
> It is not my intention to criticize Hadriel, or anyone else who has used =
this phrase.  I am sure that no one who has used this term has intended to =
be offensive to me or to anyone else.  I am not personally offended, and I =
am not looking for an apology.   I just want to make sure that people under=
stand how the use of this term resonates with  me, personally, and potentia=
lly with others.=20
>=20
> The original article by Jonathan Swift, titled, "A Modest Proposal...",  =
was a satirical suggestion that widespread famine and poverty in Ireland co=
uld be addressed by the Irish selling their children to the wealthy as a so=
urce of food (http://art-bin.com/art/omodest.html).  This was a very loaded=
 article that made an outrageous proposal, clearly not one that was meant t=
o be taken seriously.  This article has been interpreted in many different =
ways, though.  Despite the fact that the article may have been intended to =
be supportive of the Irish cause (by satirizing England's indifference to I=
rish poverty and famine), the article was, nonetheless, highly offensive to=
 many Irish people for a number of reasons.  Although i can't personally se=
e it, I have also been assured that the article is uproariously funny.  Whe=
ther you find the article offensive or humorous, though, "A Modest Proposal=
..." is a culturally charged  reminder of a very difficult time in Irish/En=
glish history, an
> d the term is likely to evoke complex feelings in people who are still cu=
lturally sensitive about that topic.
>=20
> So, if you are making a satirical, uproariously funny suggestion that you=
 do not intend to be taken seriously, but that might be misinterpreted as i=
ncredibly offensive to all parties involved, then "A Modest Proposal.." mig=
ht be just the right title...  (Although you might want to think twice befo=
re you hit "send" :-)).
>=20
> But, if you are making a serious proposal for how to improve things in th=
e IETF, I would personally feel more comfortable, and therefore better disp=
osed toward your suggestion, if you would not use the term "A Modest Propos=
al.." to describe it.
>=20
> You are, of course, free to use any title you wish for your own proposals=
...  My only purpose in sending this mail is to educate people who might no=
t be aware of the history of this particular phrase, so that they might hav=
e a better basis for deciding whether or not to use "A Modest Proposal..." =
in the titles of their own proposals.
>=20
> Thank you for listening,
> Margaret
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From msk@cloudmark.com  Mon Aug  1 11:29:47 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 982E211E811E for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.205
X-Spam-Level: 
X-Spam-Status: No, score=-103.205 tagged_above=-999 required=5 tests=[AWL=-0.606, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4M2-lFuX2eM for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:29:47 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 2A89B11E8077 for <ietf@ietf.org>; Mon,  1 Aug 2011 11:29:47 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Mon, 1 Aug 2011 11:29:48 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: 'IETF Discussion' <ietf@ietf.org>
Date: Mon, 1 Aug 2011 11:29:47 -0700
Subject: RE: Review of:   draft-ietf-iab-draft-iab-dns-applications-02
Thread-Topic: Review of:   draft-ietf-iab-draft-iab-dns-applications-02
Thread-Index: AcxHkqqb6bhdsVniQwWR+k0iku3P4wDgeQxQAVh/AgA=
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF4D7@EXCH-C2.corp.cloudmark.com>
References: <4E280223.8030309@dcrocker.net> <010301cc4b9e$ee296cf0$ca7c46d0$@us>
In-Reply-To: <010301cc4b9e$ee296cf0$ca7c46d0$@us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 18:29:47 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of R=
ichard Shockey
> Sent: Tuesday, July 26, 2011 7:19 AM
> To: 'IETF Discussion'
> Subject: RE: Review of: draft-ietf-iab-draft-iab-dns-applications-02
>=20
> I would like to add my support here to Dave Crocker's very thoughtful and
> IMHO accurate description of this revised draft. I share his views that t=
he
> substantive criticisms have not been addressed.

+1.

In particular, I'm missing what important message this draft presents that =
is not already discussed in RFC5507. =20

> If there are issues with new uses of the DNS, DNSEXT or DNSOPS are fully
> chartered to provide community review and do not need any "fuzzy" guidanc=
e
> on what is and is not acceptable.  This entire draft could beeasily
> simplified byt a one sentence statement.
>=20
> "If you need to do database look ups in the future we would prefer that y=
ou
> think of using protocols other than the DNS."

Right, and it's not clear to me we need a full IAB document stating that.  =
And, there are plenty of people on the DNS Directorate as well as others sc=
attered throughout the IETF that make this point on a regular basis already=
.


From hallam@gmail.com  Mon Aug  1 11:31:08 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C69711E811E for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.476
X-Spam-Level: 
X-Spam-Status: No, score=-3.476 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f++Wj+onWPFI for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:31:07 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6018411E8077 for <ietf@ietf.org>; Mon,  1 Aug 2011 11:31:07 -0700 (PDT)
Received: by gwb20 with SMTP id 20so4475537gwb.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 11:31:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=xMN9NugJ5wl/4SCDHE1hzTs8Q77pk196bgCgwblkJAk=; b=SBm6Gz0LWURtbPnWrOVyIX/Cs5ZIy7RukU+QIhx6gUyKp3fKSWqLH+V8Aq4uhnpzkb 1uysb45345uSF4IF6wmxh2IoFY4ujfU9dc5HWIccTd3XLjNSpbiKfJT4fmxnItDryZlN PP4qjJHIZb7wgDeIt89TLwo1zSOmMAOGlyHJk=
MIME-Version: 1.0
Received: by 10.101.190.6 with SMTP id s6mr471001anp.50.1312223473919; Mon, 01 Aug 2011 11:31:13 -0700 (PDT)
Received: by 10.100.34.3 with HTTP; Mon, 1 Aug 2011 11:31:13 -0700 (PDT)
Date: Mon, 1 Aug 2011 14:31:13 -0400
Message-ID: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>
Subject: Drafts Submissions cut-off
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=00163691fc2d07668c04a975d6fe
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 18:31:08 -0000

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

Over the weekend I attempted to determine the rules for discussion of drafts
at IETF meetings and was surprised to discover that they are not actually
written down anywhere (other than on the meetings page). As a result we
appear to have an anomalous situation in which an author who misses the
cut-off date for ID submissions is in fact entitled to sit on the draft for
two weeks and then submit when the ID queue re-opens.

I suggest that this is a sub-optimal state of affairs. I see two solutions:

1) Codify the requirement that materials to be discussed at the meeting must
be submitted before the cut-off and that submissions made during meetings
are strictly limited to revisions occurring after and between WG sessions.
[Except in exceptional circumstances with AD approval]

2) Eliminate the 2 week cut off completely.


My strong preference is the first. I cannot see any point in suspending what
is now an automated system in advance of meetings if it means that instead
of having the materials available a week before the meeting they are only
available after the meeting has started.

I am pretty sure that I remember this discussion in a plenary at the time
that publication of drafts was automated and publication during meetings was
no longer an exceptional circumstance.




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

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

Over the weekend I attempted to determine the rules for discussion of draft=
s at IETF meetings and was surprised to discover that they are not actually=
 written down anywhere (other than on the meetings page). As a result we ap=
pear to have an anomalous situation in which an author who misses the cut-o=
ff date for ID submissions is in fact entitled to sit on the draft for two =
weeks and then submit when the ID queue re-opens.<div>
<br></div><div>I suggest that this is a sub-optimal state of affairs. I see=
 two solutions:</div><div><br></div><div>1) Codify the requirement that mat=
erials to be discussed at the meeting must be submitted before the cut-off =
and that submissions made during meetings are strictly limited to revisions=
=A0occurring=A0after and between WG sessions. [Except in exceptional circum=
stances with AD approval]</div>
<div><br></div><div>2) Eliminate the 2 week cut off completely.</div><div><=
br></div><div><br></div><div>My strong preference is the first. I cannot se=
e any point in suspending what is now an automated system in advance of mee=
tings if it means that instead of having the materials available a week bef=
ore the meeting they are only available after the meeting has started.</div=
>
<div><br></div><div>I am pretty sure that I remember this discussion in a p=
lenary at the time that publication of drafts was automated and publication=
 during meetings was no longer an exceptional circumstance.</div><div><br c=
lear=3D"all">
<br></div><div><br></div><div><br>-- <br>Website: <a href=3D"http://hallamb=
aker.com/">http://hallambaker.com/</a><br><br>
</div>

--00163691fc2d07668c04a975d6fe--

From msk@cloudmark.com  Mon Aug  1 11:50:21 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D32BE11E8077 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.199
X-Spam-Level: 
X-Spam-Status: No, score=-103.199 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQv-1Canr1wa for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:50:21 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 6E90E11E8135 for <ietf@ietf.org>; Mon,  1 Aug 2011 11:50:21 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Mon, 1 Aug 2011 11:50:28 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 1 Aug 2011 11:50:27 -0700
Subject: RE: DKIM Signatures now being applied to IETF Email
Thread-Topic: DKIM Signatures now being applied to IETF Email
Thread-Index: AcxQYYpBeKD2lGDeRC2hbrWQVJnWiAAF8cPQ
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com>
References: <20110725171748.GA13506@amsl.com> <4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com> <201108011141.30549.scott@kitterman.com>
In-Reply-To: <201108011141.30549.scott@kitterman.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 18:50:21 -0000

My own recollection is that the working group originally had policy ideas i=
n its charter, but as we went through the work it became evident that doing=
 DKIM policy was increasingly hard to get right without creating something =
unreliable or even damaging to the current infrastructure.  Thus, I think t=
he separation in scope became necessary as the base protocol developed and =
matured.

Unfortunately, there are a those who cling tenaciously to the original view=
 and scope, and thus assert that anything less than the original goal set m=
eans DKIM is a failure.  But, also unfortunately, no workable solution has =
yet to be presented.

Nathaniel's statement is right on the money: DKIM, in its current form, is =
an important development enabling some important new functionality.  Rather=
 than harping on the cruft that was cut away from DKIM along its path, we s=
hould be focusing on the new stuff, as that's what we really need, and that=
's what stands the greatest chance of success going forward.


From ajs@anvilwalrusden.com  Mon Aug  1 11:55:41 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD30B11E814C for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:55:41 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwRn1tloa6+r for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:55:41 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE7211E8147 for <ietf@ietf.org>; Mon,  1 Aug 2011 11:55:41 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id DE3421ECB41C for <ietf@ietf.org>; Mon,  1 Aug 2011 18:55:47 +0000 (UTC)
Date: Mon, 1 Aug 2011 14:55:45 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Drafts Submissions cut-off
Message-ID: <20110801185545.GG22542@shinkuro.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 18:55:41 -0000

On Mon, Aug 01, 2011 at 02:31:13PM -0400, Phillip Hallam-Baker wrote:
> 
> I suggest that this is a sub-optimal state of affairs. I see two solutions:
> 
> 1) Codify the requirement that materials to be discussed at the meeting must
> be submitted before the cut-off and that submissions made during meetings
> are strictly limited to revisions occurring after and between WG sessions.
> [Except in exceptional circumstances with AD approval]
> 
> 2) Eliminate the 2 week cut off completely.

Speaking as a WG chair but only for myself, I am opposed to either of
these two options.

(1) makes it impossible for Chairs to say, "We had a really good
discussion between the cut-off and the queue re-opening.  The editors
think they got it; please check the new text against the discussion
and be prepared to nail this down in the meeting."  It's not optimal,
but sometimes (should be rarely) qthings get done this way, and I
don't want Even More Process Police Rules to get in the way.  I
especially don't want anything more gated on the AD during IETF week.
Chairs have to ensure this rule isn't abused, and if it is then the
right thing to do is complain about WG management, not invent more
rules.

(2) means that nothing will be published in time for people to be
prepared.

I'm sensitive to the problem that is being raised here, but I think
these two options are both bad ways to solve that.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From moore@network-heretics.com  Mon Aug  1 11:59:38 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6B821F8C2E for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.975
X-Spam-Level: 
X-Spam-Status: No, score=-2.975 tagged_above=-999 required=5 tests=[AWL=-0.376, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQBm8WzpJc+O for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 11:59:37 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id D302021F8C2F for <ietf@ietf.org>; Mon,  1 Aug 2011 11:59:37 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1QnxiI-0001A8-Bo; Mon, 01 Aug 2011 14:59:42 -0400
Subject: Re: DKIM Signatures now being applied to IETF Email
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com>
Date: Mon, 1 Aug 2011 14:59:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C4ACC39-F9CC-429B-B6E6-CE0202C2C1BE@network-heretics.com>
References: <20110725171748.GA13506@amsl.com> <4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com> <201108011141.30549.scott@kitterman.com> <F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940c53454f9e98092e39e54a75b80491ca0350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 18:59:38 -0000

On Aug 1, 2011, at 2:50 PM, Murray S. Kucherawy wrote:

> My own recollection is that the working group originally had policy =
ideas in its charter, but as we went through the work it became evident =
that doing DKIM policy was increasingly hard to get right without =
creating something unreliable or even damaging to the current =
infrastructure.  Thus, I think the separation in scope became necessary =
as the base protocol developed and matured.
>=20
> Unfortunately, there are a those who cling tenaciously to the original =
view and scope, and thus assert that anything less than the original =
goal set means DKIM is a failure.  But, also unfortunately, no workable =
solution has yet to be presented.
>=20
> Nathaniel's statement is right on the money: DKIM, in its current =
form, is an important development enabling some important new =
functionality.  Rather than harping on the cruft that was cut away from =
DKIM along its path, we should be focusing on the new stuff, as that's =
what we really need, and that's what stands the greatest chance of =
success going forward.

Perhaps.  But it's difficult to escape the impression that this is =
another example of IETF failing to solve an important problem by =
focusing on a portion of the problem that's easy to solve, and ruling =
the difficult part out of scope for the time being.  Repeat as needed; =
you can always partition the remaining part of the problem again.

Keith


From scott@kitterman.com  Mon Aug  1 12:02:57 2011
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06C3321F8B6C for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:02:57 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSauILNythvc for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:02:56 -0700 (PDT)
Received: from mailout00.controlledmail.com (mailout00.controlledmail.com [72.81.252.19]) by ietfa.amsl.com (Postfix) with ESMTP id 7223421F8C4F for <ietf@ietf.org>; Mon,  1 Aug 2011 12:02:35 -0700 (PDT)
Received: from mailout00.controlledmail.com (localhost [127.0.0.1]) by mailout00.controlledmail.com (Postfix) with ESMTP id 8D0AB38C12F; Mon,  1 Aug 2011 15:02:41 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1312225361; bh=fuqu7W0ZxigcimK6bon8eHjORd2WbCiFe2MqVdeKik0=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=QnKSZJrwb2gZyZxGbCF0ARjUuH5M5DvLP/7TtFIH6uJyxPmCtY30Zr7SsP1S2n1nF zwLOmWJaMJNC0/ex00tI9VOqxVbDRleuFLuYNC18zmnYqrb39fANlBTp6M7S7Lp/k2 vTmeik72mzzyEQlimpwJXyiQERd13fsMEQx4dciI=
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
Date: Mon, 1 Aug 2011 15:02:39 -0400
User-Agent: KMail/1.13.6 (Linux/2.6.38-10-generic-pae; KDE/4.6.2; i686; ; )
References: <20110725171748.GA13506@amsl.com> <201108011141.30549.scott@kitterman.com> <F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201108011502.40061.scott@kitterman.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 19:02:57 -0000

On Monday, August 01, 2011 02:50:27 PM Murray S. Kucherawy wrote:
> My own recollection is that the working group originally had policy ideas
> in its charter, but as we went through the work it became evident that
> doing DKIM policy was increasingly hard to get right without creating
> something unreliable or even damaging to the current infrastructure. 
> Thus, I think the separation in scope became necessary as the base
> protocol developed and matured.
> 
> Unfortunately, there are a those who cling tenaciously to the original view
> and scope, and thus assert that anything less than the original goal set
> means DKIM is a failure.  But, also unfortunately, no workable solution
> has yet to be presented.
> 
> Nathaniel's statement is right on the money: DKIM, in its current form, is
> an important development enabling some important new functionality. 
> Rather than harping on the cruft that was cut away from DKIM along its
> path, we should be focusing on the new stuff, as that's what we really
> need, and that's what stands the greatest chance of success going forward.

I agree.  The one thing I don't agree with in his statement is the never part 
of "... criticize DKIM for not doing something it was never intended to do."  
It is what it is, for better or worse and we need to move forward, but I don't 
think historical revisionism is appropriate (DomainKeys, which is the 
antecedent to DKIM, had a policy component, so expecting that to have been 
included in DKIM is not at all unreasonable).

We should move forward with what we have, but not forget how we got here.

Scott K

From barryleiba.mailing.lists@gmail.com  Mon Aug  1 12:43:01 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61C8A11E812C for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.058
X-Spam-Level: 
X-Spam-Status: No, score=-103.058 tagged_above=-999 required=5 tests=[AWL=-0.081, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRZctlKrysJS for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:43:00 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id C7C2611E8077 for <ietf@ietf.org>; Mon,  1 Aug 2011 12:43:00 -0700 (PDT)
Received: by yie30 with SMTP id 30so4391699yie.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 12:43:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=dW3i1pK+iG7PxOjfO48m8u1LNEss5QXPEcG3b6OZKbM=; b=J0cLCWaMjU4K91REmP+MBRnNSHstb0aBotp0NCfuqrR6AXQ02qWJQoali43PPbhjFI l21PyJGWlC823BaZBcKm/zFRTm4CNaNKK0ljXZ8v9TGjcbc8kOIKdbbHLGt3cL9Fnyiv wvfclNQ76L7emgqCfcN6BWwgytVu8Hs5vWGJY=
MIME-Version: 1.0
Received: by 10.236.144.200 with SMTP id n48mr1853432yhj.348.1312227787690; Mon, 01 Aug 2011 12:43:07 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.38.7 with HTTP; Mon, 1 Aug 2011 12:43:06 -0700 (PDT)
In-Reply-To: <20110801185545.GG22542@shinkuro.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com>
Date: Mon, 1 Aug 2011 15:43:06 -0400
X-Google-Sender-Auth: dJhArtG5pLNWQPfU9DFUp2aiRoE
Message-ID: <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com>
Subject: Re: Drafts Submissions cut-off
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 19:43:01 -0000

On Mon, Aug 01, 2011 at 02:31:13PM -0400, Phillip Hallam-Baker wrote:
> I suggest that this is a sub-optimal state of affairs. I see two solutions:
>
> 1) Codify the requirement that materials to be discussed at the meeting must
> be submitted before the cut-off and that submissions made during meetings
> are strictly limited to revisions occurring after and between WG sessions.
> [Except in exceptional circumstances with AD approval]
>
> 2) Eliminate the 2 week cut off completely.

When I first read this, I thought that (1) could make sense.  When I
started to read Andrew's response, I disagreed with it.  After all,
the AD can override the block on submissions.

Then I got to this:

On Mon, Aug 1, 2011 at 2:55 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> I
> especially don't want anything more gated on the AD during IETF week.
> Chairs have to ensure this rule isn't abused, and if it is then the
> right thing to do is complain about WG management, not invent more
> rules.

...and I switched.  Andrew's right: we aren't well served by a
situation that requires AD intervention in this, and we do have to
trust the chairs to manage their working groups, including managing
the time and content of the sessions.

I understand the situation that prompted Phill to suggest this, but I
think it's something that needs to be taken up with the chairs.  And,
yes, that is what happened, in a sense -- it was taken up with the
chairs -- and also in a sense, the chairs acknowledged that they
allowed something that in this case might have been problematic.

I think that's the way to deal with it, albeit with somewhat more
circumspection than happened.  I'd rather not put rules in place that
restrict how the chairs can manage the discussions in their working
groups.  Most of the time, these late updates are helpful, not
harmful.  The chairs need to be able to put their judgment to work
here.

Barry

From john-ietf@jck.com  Mon Aug  1 12:47:06 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89B9A11E8077 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.633
X-Spam-Level: 
X-Spam-Status: No, score=-102.633 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AupHxk9xhPJt for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:47:06 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id A742C11E8132 for <ietf@ietf.org>; Mon,  1 Aug 2011 12:47:05 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QnySB-000IOy-SG; Mon, 01 Aug 2011 15:47:08 -0400
Date: Mon, 01 Aug 2011 15:47:07 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
Subject: Re: Drafts Submissions cut-off
Message-ID: <7EB2BF41472FEC1438355A0B@PST.JCK.COM>
In-Reply-To: <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 19:47:06 -0000

+1

More flexibility, more chair accountability for the decisions
they make about that flexibility, fewer rules and fewer things
that require AD involvement except on appeal and other types of
high-level discussions about whether particular WGs are being
managed properly.

   john


--On Monday, August 01, 2011 15:43 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

> On Mon, Aug 01, 2011 at 02:31:13PM -0400, Phillip Hallam-Baker
> wrote:
>> I suggest that this is a sub-optimal state of affairs. I see
>> two solutions:
>> 
>> 1) Codify the requirement that materials to be discussed at
>> the meeting must be submitted before the cut-off and that
>> submissions made during meetings are strictly limited to
>> revisions occurring after and between WG sessions. [Except in
>> exceptional circumstances with AD approval]
>> 
>> 2) Eliminate the 2 week cut off completely.
> 
> When I first read this, I thought that (1) could make sense.
> When I started to read Andrew's response, I disagreed with it.
> After all, the AD can override the block on submissions.
> 
> Then I got to this:
> 
> On Mon, Aug 1, 2011 at 2:55 PM, Andrew Sullivan
> <ajs@anvilwalrusden.com> wrote:
>> I
>> especially don't want anything more gated on the AD during
>> IETF week. Chairs have to ensure this rule isn't abused, and
>> if it is then the right thing to do is complain about WG
>> management, not invent more rules.
> 
> ...and I switched.  Andrew's right: we aren't well served by a
> situation that requires AD intervention in this, and we do
> have to trust the chairs to manage their working groups,
> including managing the time and content of the sessions.
> 
> I understand the situation that prompted Phill to suggest
> this, but I think it's something that needs to be taken up
> with the chairs.  And, yes, that is what happened, in a sense
> -- it was taken up with the chairs -- and also in a sense, the
> chairs acknowledged that they allowed something that in this
> case might have been problematic.
> 
> I think that's the way to deal with it, albeit with somewhat
> more circumspection than happened.  I'd rather not put rules
> in place that restrict how the chairs can manage the
> discussions in their working groups.  Most of the time, these
> late updates are helpful, not harmful.  The chairs need to be
> able to put their judgment to work here.
> 
> Barry
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf





From mra@pobox.com  Mon Aug  1 12:57:55 2011
Return-Path: <mra@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D740A21F8C5B for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:57:55 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwtHW097E9Q4 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:57:55 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 66C2A21F8BBE for <ietf@ietf.org>; Mon,  1 Aug 2011 12:57:47 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 9B24344DB for <ietf@ietf.org>; Mon,  1 Aug 2011 15:57:53 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type:content-transfer-encoding; s=sasl; bh=0ZUNMGuzptwg pRvHaS9VVL91Dy4=; b=m5/3VzQo4xswC+D8bEKBMBHmm14hx5Iv+rKiDKsxArFW PDShaJLdDiID9Q3tz2710zX2YeM/yeVi8QBpwV89HUMxkTOLfC+F2MZtyclvcdw1 M8cTyaWf+dFnVnZbXKnS0cHjXSkQ2x1KaZ/1ubXFdv7QRS/ZeHXfSa708bqf8LE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type:content-transfer-encoding; q=dns; s=sasl; b=gKO+GE IogPTwCau7Zart+lQcLeef9yu2v+cwqXM94Mjl2jdHvnBC4+1NIZcPgJiPNzhzSQ PLtnV1IcipGF2He8XkkTrmYmPZpNlMqZuE5Cf+Z0RZkpTsAUV+wXDaWMzUAEN2NB FdQbgv7up6c3RMqiJ/x//9TNfWz74EaRmvM/0=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 9018C44DA for <ietf@ietf.org>; Mon,  1 Aug 2011 15:57:53 -0400 (EDT)
Received: from mail-vx0-f172.google.com (unknown [209.85.220.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by b-sasl-quonix.pobox.com (Postfix) with ESMTPSA id 53BEE44D7 for <ietf@ietf.org>; Mon,  1 Aug 2011 15:57:53 -0400 (EDT)
Received: by vxi40 with SMTP id 40so5695537vxi.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 12:57:53 -0700 (PDT)
Received: by 10.52.107.102 with SMTP id hb6mr4749877vdb.419.1312228673136; Mon, 01 Aug 2011 12:57:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.168.170 with HTTP; Mon, 1 Aug 2011 12:57:33 -0700 (PDT)
In-Reply-To: <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org> <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com>
From: Mark Atwood <mra@pobox.com>
Date: Mon, 1 Aug 2011 12:57:33 -0700
Message-ID: <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@mail.gmail.com>
Subject: Re: A modest proposal...
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Pobox-Relay-ID: 8AE8599E-BC78-11E0-9D10-1DC62E706CDE-82717895!b-pb-sasl-quonix.pobox.com
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 19:57:56 -0000

On Mon, Aug 1, 2011 at 10:08 AM, Hadriel Kaplan <HKaplan@acmepacket.com> wr=
ote:
>
> Fascinating. =C2=A0I had no idea that there even *was* such a phrase in c=
ommon usage, let alone that there was known etymology for it. =C2=A0One lea=
rns something new every day.
> But I meant it quite literally: a moderate/humble/etc. proposal for Frida=
y meeting schedule.

English is funny that way, and it's one of the things that make it
such a difficult language to learn.  A great deal of the meaning is
not in the literal meaning of a given chain of words, but is also
contained in the historical and literary allusions that given phrases
may have, which often have the direct opposite or at least very
different meaning than the literal words.

..m

From hartmans@mit.edu  Mon Aug  1 12:59:33 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8160211E8137 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.035
X-Spam-Level: 
X-Spam-Status: No, score=-104.035 tagged_above=-999 required=5 tests=[AWL=-1.770, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZO4SWKqpX4gu for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 12:59:33 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 177AC11E8077 for <ietf@ietf.org>; Mon,  1 Aug 2011 12:59:32 -0700 (PDT)
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 09BBD20289; Mon,  1 Aug 2011 16:02:24 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A97B1422B; Mon,  1 Aug 2011 15:59:34 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Drafts Submissions cut-off
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com> <7EB2BF41472FEC1438355A0B@PST.JCK.COM>
Date: Mon, 01 Aug 2011 15:59:34 -0400
In-Reply-To: <7EB2BF41472FEC1438355A0B@PST.JCK.COM> (John C. Klensin's message of "Mon, 01 Aug 2011 15:47:07 -0400")
Message-ID: <tslwrew2995.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: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 19:59:33 -0000

I think removing the cutoff is the right approach here.

I'd prefer that some date remain on the list of important meeting dates
to remind ourselves that revisions should be in in time for people to
read them.

From housley@vigilsec.com  Mon Aug  1 13:47:53 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D6621F8C17 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 13:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8yFSHWzZuvZS for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 13:47:53 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2611021F8C0A for <ietf@ietf.org>; Mon,  1 Aug 2011 13:47:41 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 3EFF9F24165 for <ietf@ietf.org>; Mon,  1 Aug 2011 16:48:10 -0400 (EDT)
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 9ZCzS5zKgu+H for <ietf@ietf.org>; Mon,  1 Aug 2011 16:47:37 -0400 (EDT)
Received: from [192.168.2.101] (pool-96-241-176-45.washdc.fios.verizon.net [96.241.176.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 94EA8F24131 for <ietf@ietf.org>; Mon,  1 Aug 2011 16:48:09 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Minutes for IETF 81 Administrative Plenary
Date: Mon, 1 Aug 2011 16:47:47 -0400
Message-Id: <54493EFB-471A-4527-94D8-03EF25FA9122@vigilsec.com>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 20:47:53 -0000

I just posted the draft minutes for the Administrative Plenary:
http://www.ietf.org/proceedings/81/minutes/plenaryw.txt

Many thanks to Dean Willis for taking notes.

Please notify me of any errors that need correcting.

Russ


From david.kessens@nsn.com  Mon Aug  1 13:49:04 2011
Return-Path: <david.kessens@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F17421F8D02 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 13:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.483
X-Spam-Level: 
X-Spam-Status: No, score=-6.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dUGJ4cDbB6+I for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 13:49:04 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id AC76021F8D01 for <ietf@ietf.org>; Mon,  1 Aug 2011 13:49:03 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p71Kn6ZB009559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 1 Aug 2011 22:49:06 +0200
Received: from localhost.localdomain ([10.138.51.235]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p71Kn5f1031558; Mon, 1 Aug 2011 22:49:06 +0200
Received: from localhost.localdomain (X1 [127.0.0.1]) by localhost.localdomain (8.14.4/8.14.4) with ESMTP id p71Kn5Wn029320;  Mon, 1 Aug 2011 13:49:05 -0700
Received: (from david@localhost) by localhost.localdomain (8.14.4/8.14.4/Submit) id p71Kn3jL029318; Mon, 1 Aug 2011 13:49:03 -0700
X-Authentication-Warning: localhost.localdomain: david set sender to david.kessens@nsn.com using -f
Date: Mon, 1 Aug 2011 13:49:03 -0700
From: David Kessens <david.kessens@nsn.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: A modest proposal for Friday meeting schedule
Message-ID: <20110801204903.GG25922@nsn.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi> <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 20:49:04 -0000

Russ,

On Mon, Aug 01, 2011 at 11:10:24AM -0400, Russ Housley wrote:
> I am discussing the possibility with the Secretariat and the IESG.  I will report back to the community as soon as possible.

I don't think this proposal should be pursued. The breaks fulfil an
important function and there is nothing wrong with a starting time of 9am.

The friday meetings are always going to be tough at the end of a week long
meeting but trying to compress the friday schedule would only make it
harder.

David Kessens
---

> >>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
> >>> 
> >>>> Something like this:
> >>>> 8:30-11:00 Session I
> >>>> 11:15-12:15 Session II
> >>>> 12:30-13:30 Session III
> >>> 
> >>> I really like it, as there are a bunch of post-IETF stuff, some of
> >>> which starts in the afternoon and thus conflicts with the IETF.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

David Kessens
---

From moore@network-heretics.com  Mon Aug  1 14:34:31 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C04B821F8CD7 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.959
X-Spam-Level: 
X-Spam-Status: No, score=-2.959 tagged_above=-999 required=5 tests=[AWL=-0.360, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1ht5wz2TSmI for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:34:31 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 48ABB21F8CD6 for <ietf@ietf.org>; Mon,  1 Aug 2011 14:34:31 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1Qo08A-0001kh-FV; Mon, 01 Aug 2011 17:34:34 -0400
Subject: Re: A modest proposal...
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@mail.gmail.com>
Date: Mon, 1 Aug 2011 17:34:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1842EBEA-0D0F-43FB-9090-BC984D87A2A2@network-heretics.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org> <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com> <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@mail.gmail.com>
To: Mark Atwood <mra@pobox.com>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940621ecc6f34d0a8eb590157c04ff77f8b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:34:31 -0000

On Aug 1, 2011, at 3:57 PM, Mark Atwood wrote:

> On Mon, Aug 1, 2011 at 10:08 AM, Hadriel Kaplan =
<HKaplan@acmepacket.com> wrote:
>>=20
>> Fascinating.  I had no idea that there even *was* such a phrase in =
common usage, let alone that there was known etymology for it.  One =
learns something new every day.
>> But I meant it quite literally: a moderate/humble/etc. proposal for =
Friday meeting schedule.
>=20
> English is funny that way, and it's one of the things that make it
> such a difficult language to learn.  A great deal of the meaning is
> not in the literal meaning of a given chain of words, but is also
> contained in the historical and literary allusions that given phrases
> may have, which often have the direct opposite or at least very
> different meaning than the literal words.

I believe that "problem" exists in other languages also.

I also don't think that Swift forever changed the meaning of "modest =
proposal" by writing that article.  Those with a familiarity of English =
literature might see another potential meaning in those words, but the =
"normal" meaning still applies.

Keith


From moore@network-heretics.com  Mon Aug  1 14:36:42 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD4B21F8CF3 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:36:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.955
X-Spam-Level: 
X-Spam-Status: No, score=-2.955 tagged_above=-999 required=5 tests=[AWL=-0.356, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ut8tjjRAX3uc for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:36:42 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB1E21F8CE9 for <ietf@ietf.org>; Mon,  1 Aug 2011 14:36:42 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1Qo0AJ-00083t-Aj; Mon, 01 Aug 2011 17:36:47 -0400
Subject: Re: Drafts Submissions cut-off
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <tslwrew2995.fsf@mit.edu>
Date: Mon, 1 Aug 2011 17:36:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com> <7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940d7873c4d224b74430aedfb9c42d2ed32350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
Cc: John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:36:42 -0000

On Aug 1, 2011, at 3:59 PM, Sam Hartman wrote:

> I think removing the cutoff is the right approach here.
>=20
> I'd prefer that some date remain on the list of important meeting =
dates
> to remind ourselves that revisions should be in in time for people to
> read them.

If memory serves, the original purpose of the cutoff was to avoid =
overtaxing the resources of the Secretariat in the period immediately =
prior to IETF meetings.   But it has also come in handy for ADs and =
others who feel the need to keep up with large numbers of documents from =
a variety of working groups.   I wouldn't blame any AD or WG chair for =
imposing a "no drafts submitted after the cutoff can be discussed at the =
meeting" rule.

Keith



From adam@nostrum.com  Mon Aug  1 14:38:21 2011
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 197DE1F0C3B for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.327
X-Spam-Level: 
X-Spam-Status: No, score=-102.327 tagged_above=-999 required=5 tests=[AWL=0.274, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4rckzbOF5Mk for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:38:20 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 50C781F0C39 for <ietf@ietf.org>; Mon,  1 Aug 2011 14:38:20 -0700 (PDT)
Received: from dn3-110.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 p71LcOEh076014 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 1 Aug 2011 16:38:26 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4E371CD0.9010501@nostrum.com>
Date: Mon, 01 Aug 2011 16:38:24 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: A modest proposal for Friday meeting schedule
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi> <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com>
In-Reply-To: <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:38:21 -0000

I'd like to join the sparse voices in speaking out against this plan. By 
Friday, I'm pretty well on a local meal schedule. Pushing lunch back by 
2 hours would pretty well on guarantee that I'd be sugar-crashed and 
less coherent than normal by the end of Session II.

/a

On 8/1/11 10:10 AM, Russ Housley wrote:
> I am discussing the possibility with the Secretariat and the IESG.  I will report back to the community as soon as possible.
>
> Russ
>
>
>>>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
>>>>
>>>>> Something like this:
>>>>> 8:30-11:00 Session I
>>>>> 11:15-12:15 Session II
>>>>> 12:30-13:30 Session III
>>>> I really like it, as there are a bunch of post-IETF stuff, some of
>>>> which starts in the afternoon and thus conflicts with the IETF.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From ole@cisco.com  Mon Aug  1 14:42:56 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFAE21F8B71 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.825
X-Spam-Level: 
X-Spam-Status: No, score=-102.825 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSBLmoIlqcpM for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:42:56 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id E19BC21F8B6E for <ietf@ietf.org>; Mon,  1 Aug 2011 14:42:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1086; q=dns/txt; s=iport; t=1312234983; x=1313444583; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=bFWfxeBR/tWKxAW+h+jt1SnxeKJ351XWpFOLju2H6dE=; b=icr9RBr+i3rmDz6RvLL/BPtErmRdAn6MqYixod+QloYnSkNOEnqlDayY +YU9q+GwF4zQotDySZ7L4ID466Uw+JMCQ1sWDzkrSd5wUbFF9N/8o2PP7 KI8QTxDdtlhMqA9/TfJaGE4hSA5eJe9iE75Q5qHX6ao2sCsW3+jMbbfKu Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAK0cN06rRDoI/2dsb2JhbAAsEwOZP44gd4FAAQEBAQIBEgECASQ/EAsOHRtXBhMih0qiCwGDGg8Bm0WDHCKDBASHWpAohGWHGA
X-IronPort-AV: E=Sophos;i="4.67,302,1309737600";  d="scan'208";a="8583108"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-5.cisco.com with ESMTP; 01 Aug 2011 21:43:02 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p71Lh2V5024944; Mon, 1 Aug 2011 21:43:02 GMT
Date: Mon, 1 Aug 2011 14:43:02 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mark Atwood <mra@pobox.com>
Subject: Re: A modest proposal...
In-Reply-To: <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1108011439010.20499@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org> <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com> <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@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: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:42:56 -0000

Not to mention the strange grammatical "usage" that you hear in 
Britain:

"I am stood in front of the office."

"We were sat on the runway for 20 minutes"

(Something you say about chess pieces I suppose...)

or:

"The Bank of England have announced an increase in interest rates"

No wonder us foreigners have such a hard time, particularly as we have 
to pay attention to the American variants.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Mon, 1 Aug 2011, Mark Atwood wrote:

> 
> English is funny that way, and it's one of the things that make it
> such a difficult language to learn.  A great deal of the meaning is
> not in the literal meaning of a given chain of words, but is also
> contained in the historical and literary allusions that given phrases
> may have, which often have the direct opposite or at least very
> different meaning than the literal words.
> 
> ..m

From brian.e.carpenter@gmail.com  Mon Aug  1 14:47:23 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 228491F0C49 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:47:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyNunY+cowu0 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:47:22 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9A94321F8D8A for <ietf@ietf.org>; Mon,  1 Aug 2011 14:47:22 -0700 (PDT)
Received: by gyd5 with SMTP id 5so4450965gyd.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 14:47:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=X7YHdxsH2pPuqLh9FerRfj9ixeR0x/Cva7shZMRRvNg=; b=Yan61AXuJiE/02fL1nE9EpB7eFf8fHuiADpM81dzcAAIFgJVQp1fSpgXdT2vmRRTVb l/DoE+tfHROYGOcLjZgTS60kvpwzFeEAa+AVYMdUekL9et71vjMYpujLRRmUxN5ilxXH DmxiTRI71amG5y1bbMWyK24dUID/8/h6M9kD0=
Received: by 10.68.39.39 with SMTP id m7mr9467168pbk.54.1312235249326; Mon, 01 Aug 2011 14:47:29 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id v1sm5968573pbg.31.2011.08.01.14.47.27 (version=SSLv3 cipher=OTHER); Mon, 01 Aug 2011 14:47:28 -0700 (PDT)
Message-ID: <4E371EEC.1050602@gmail.com>
Date: Tue, 02 Aug 2011 09:47:24 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Drafts Submissions cut-off
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>	<20110801185545.GG22542@shinkuro.com>	<CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com>	<7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu> <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com>
In-Reply-To: <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:47:23 -0000

Speaking for myself, I *highly* value the existing twin cutoff dates.
It makes it possible to perform triage on the drafts before the meeting,
and to read a reasonable number of them that seem important with some care.

Allowing drafts to be posted right up to the start of the meeting would
make any kind of systematic triage impossible, so I would end up reading
drafts at random - or more likely, sitting back and waiting to be spoon-fed
the PowerPoint.

Bad idea, which would detract from the effectiveness of WG sessions.

   Brian

From aallen@rim.com  Mon Aug  1 14:50:25 2011
Return-Path: <aallen@rim.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3981F0C4F for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.195
X-Spam-Level: 
X-Spam-Status: No, score=-5.195 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGC3gIpL84mC for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:50:24 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3D31F0C49 for <ietf@ietf.org>; Mon,  1 Aug 2011 14:50:24 -0700 (PDT)
X-AuditID: 0a41282f-b7b8cae00000068f-12-4e371f993cc0
Received: from XHT109CNC.rim.net (xht109cnc.rim.net [10.65.12.218]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mhs060cnc.rim.net (SBG) with SMTP id 9E.38.01679.99F173E4; Mon,  1 Aug 2011 21:50:18 +0000 (GMT)
Received: from XCT105ADS.rim.net (10.67.111.46) by XHT109CNC.rim.net (10.65.12.218) with Microsoft SMTP Server (TLS) id 8.3.159.2; Mon, 1 Aug 2011 17:50:29 -0400
Received: from XMB105ADS.rim.net ([fe80::c47b:e609:558:1b44]) by XCT105ADS.rim.net ([fe80::2d01:2041:eea3:819b%22]) with mapi id 14.01.0289.001; Mon, 1 Aug 2011 16:50:28 -0500
From: Andrew Allen <aallen@rim.com>
To: "adam@nostrum.com" <adam@nostrum.com>, "housley@vigilsec.com" <housley@vigilsec.com>
Subject: Re: A modest proposal for Friday meeting schedule
Thread-Topic: A modest proposal for Friday meeting schedule
Thread-Index: AcxPmBpixpbwtezNTTGCAyx7fK66JgAKw5+AACzZywAAAPMKgAADK/cAAA2M/QAACg6FDw==
Date: Mon, 1 Aug 2011 21:50:27 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2301B689@XMB105ADS.rim.net>
In-Reply-To: <4E371CD0.9010501@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.110.251]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrAKsWRmVeSWpSXmKPExsXC5chzS3eWvLmfwfMF7BZ7/i5it3j14ia7 xbON81kcmD2WLPnJ5DFr5xMWj1V3vrAGMEc1MNok5uXllySWpCqkpBYn2yr5pKYn5igEFGWW JSZXKrhkFifnJGbmphYpKWSm2CqZKCkU5CQmp+am5pXYKiUWFKTmpSjZcSlgABugssw8hdS8 5PyUzLx0WyXPYH9dCwtTS11DJTtdJJDwjztj/Zf1TAUbuSpWt35jamA8xNHFyMkhIWAisai3 mx3CFpO4cG89WxcjF4eQQC+TxLI3/xkhnKWMErfeTmSCcDYzSnR032IFaWETUJZY/nsGUBUH h4hAlMST3hSQMDNQ+OmmOUwgtrCAlUTDvqVgtoiAtcSBb+uh7DCJDw/vsYDYLAIqEpt7p7KB 2LwCbhKdO36DXcQpoC2x4EcfmM0IdN33U2uYIOaLS9x6Mp8J4moBiSV7zjND2KISLx//Y4Ww FSWeNG5mgajXk7gxdQobhK0tsWzha2aIXYISJ2c+AasREpCW2HFyDeMERvFZSFbMQtI+C0n7 LCTtCxhZVjEK5mYUG5gZJOcl6xVl5urlpZZsYgQnFQ39HYx9e7UOMQpwMCrx8MbLmPsJsSaW FVfmHmKU4GBWEuGdNcvMT4g3JbGyKrUoP76oNCe1+BCjBTBUJjJLcSfnAxNeXkm8sYEBCkdJ nDdY2sBPSCAdmKqyU1MLUotgWpk4OKUaGIV/b18as+u1ct7J1FuXlU4q1E1vT/NbPvEdV+r8 U9PUb7Oc85JQWyJW/arrotUSM+9dFZ82pTD8FGn4Uj5/7V/9U1z/5h2SXXLQVOHbE0Em7g/z bm6vEX76/R+viFUTf90d3SfdZ7fbbgpvs1uziC/5P6ukuYxi5WRtr/mWJ0++nMHt/P/PvztK LMUZiYZazEXFiQCe02kIQwMAAA==
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:50:25 -0000

+1 with Adam


----- Original Message -----
From: Adam Roach [mailto:adam@nostrum.com]
Sent: Monday, August 01, 2011 04:38 PM=0A=
To: Russ Housley <housley@vigilsec.com>
Cc: IETF <ietf@ietf.org>
Subject: Re: A modest proposal for Friday meeting schedule

I'd like to join the sparse voices in speaking out against this plan. By 
Friday, I'm pretty well on a local meal schedule. Pushing lunch back by 
2 hours would pretty well on guarantee that I'd be sugar-crashed and 
less coherent than normal by the end of Session II.

/a

On 8/1/11 10:10 AM, Russ Housley wrote:
> I am discussing the possibility with the Secretariat and the IESG.  I will=
 report back to the community as soon as possible.
>
> Russ
>
>
>>>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
>>>>
>>>>> Something like this:
>>>>> 8:30-11:00 Session I
>>>>> 11:15-12:15 Session II
>>>>> 12:30-13:30 Session III
>>>> I really like it, as there are a bunch of post-IETF stuff, some of
>>>> which starts in the afternoon and thus conflicts with the IETF.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From scott.brim@gmail.com  Mon Aug  1 14:53:37 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87F331F0C4E for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:53:37 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkieI9naC15l for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:53:36 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEAE1F0C49 for <ietf@ietf.org>; Mon,  1 Aug 2011 14:53:36 -0700 (PDT)
Received: by iye7 with SMTP id 7so8718581iye.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 14:53:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:from:date:message-id:subject:to :cc:content-type; bh=dcb+otuHXa/2w9c1sz9h8Q1Kf1swGIZx2/7fBIjzQRM=; b=Yy+iZu5qa1jvZ7UY5mNkjPnB7OcKKbBAaQTb8+Hmmw/ivRXWDn6AxdV2A4aDWL1+jx ZYS7frasgDs6nP0HCPcINQSJZ2ZFHNANyWnc9G4q+zVBqJeDYIVojARyjU/GlZTrb6Rb YRn9eWU7kS3NjeVR8rfzFYLvn2+hU1bafnTJk=
Received: by 10.231.83.193 with SMTP id g1mr2776595ibl.74.1312235620727; Mon, 01 Aug 2011 14:53:40 -0700 (PDT)
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com> <7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu> <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com> <4E371EEC.1050602@gmail.com>
In-Reply-To: <4E371EEC.1050602@gmail.com>
Mime-Version: 1.0 (iPad Mail 8L1)
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 1 Aug 2011 17:54:16 -0400
Message-ID: <6489201734580959064@unknownmsgid>
Subject: Re: Drafts Submissions cut-off
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:53:37 -0000

I invoke the end to end argument.  The working groups know best
whether they will consider late contributions.  Working groups already
go around the deadlines when they want to anyway, and some publish
even stronger deadlines, or exclude drafts for other reasons. The
draft process level cutoff does a partial job that sometimes gets in
the way - a classic e2e situation. Let the draft process be nice and
simple and straightforward, without unnecessary bling.

Scott


On Aug 1, 2011, at 17:47, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> Speaking for myself, I *highly* value the existing twin cutoff dates.
> It makes it possible to perform triage on the drafts before the meeting,
> and to read a reasonable number of them that seem important with some care.
>
> Allowing drafts to be posted right up to the start of the meeting would
> make any kind of systematic triage impossible, so I would end up reading
> drafts at random - or more likely, sitting back and waiting to be spoon-fed
> the PowerPoint.
>
> Bad idea, which would detract from the effectiveness of WG sessions.
>
>   Brian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From joelja@bogus.com  Mon Aug  1 15:13:07 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379BC21F8E33 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.659
X-Spam-Level: 
X-Spam-Status: No, score=-102.659 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWoHtb9sdojG for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:13:06 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1271A21F8E31 for <ietf@ietf.org>; Mon,  1 Aug 2011 15:13:05 -0700 (PDT)
Received: from [10.101.144.52] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p71MD9DV006392 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 1 Aug 2011 22:13:09 GMT (envelope-from joelja@bogus.com)
Subject: Re: Drafts Submissions cut-off
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com>
Date: Mon, 1 Aug 2011 15:13:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1251DC7A-587D-47C2-AFD2-56CB5C50CDD7@bogus.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com> <7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu> <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 01 Aug 2011 22:13:10 +0000 (UTC)
Cc: John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 22:13:07 -0000

On Aug 1, 2011, at 2:36 PM, Keith Moore wrote:

> On Aug 1, 2011, at 3:59 PM, Sam Hartman wrote:
>=20
>> I think removing the cutoff is the right approach here.
>>=20
>> I'd prefer that some date remain on the list of important meeting =
dates
>> to remind ourselves that revisions should be in in time for people to
>> read them.
>=20
> If memory serves, the original purpose of the cutoff was to avoid =
overtaxing the resources of the Secretariat in the period immediately =
prior to IETF meetings.   But it has also come in handy for ADs and =
others who feel the need to keep up with large numbers of documents from =
a variety of working groups.   I wouldn't blame any AD or WG chair for =
imposing a "no drafts submitted after the cutoff can be discussed at the =
meeting" rule.

It's one of the tools that assists with the volume. Not discussing =
documents which have not been socialized even if they did make the =
deadline is another.=20

While I'm sure consistency is the hobgoblin of small minds, having =
global default deadlines is of great assistance while pursuing work =
across multiple groups and areas.

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


From touch@isi.edu  Mon Aug  1 15:17:30 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 605001F0C4D for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.376
X-Spam-Level: 
X-Spam-Status: No, score=-103.376 tagged_above=-999 required=5 tests=[AWL=-0.777, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jK722+xyafGH for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:17:28 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id CE4F71F0C49 for <ietf@ietf.org>; Mon,  1 Aug 2011 15:17:28 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p71MHMlh027077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Aug 2011 15:17:23 -0700 (PDT)
Message-ID: <4E3725F2.5050903@isi.edu>
Date: Mon, 01 Aug 2011 15:17:22 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Drafts Submissions cut-off
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com> <7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu> <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com> <4E371EEC.1050602@gmail.com> <6489201734580959064@unknownmsgid>
In-Reply-To: <6489201734580959064@unknownmsgid>
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 22:17:30 -0000

Not all IDs are discussed at the upcoming IETF. It is inconvenient to 
need to delay an update or new submission simply because there's an IETF 
coming up.

And all I've seen the deadline accomplish is that people post non-posted 
updates on local websites for discussion anyway.

Unless there's a load issue, IMO there ought not be a blackout period.

Joe

From tony@att.com  Mon Aug  1 15:22:17 2011
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F4321F0C4C for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vAaCKSI9Codg for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:22:16 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEE31F0C49 for <ietf@ietf.org>; Mon,  1 Aug 2011 15:22:16 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-5.tower-120.messagelabs.com!1312237341!30717932!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 22574 invoked from network); 1 Aug 2011 22:22:22 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-5.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 Aug 2011 22:22:22 -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 p71MMljK024075 for <ietf@ietf.org>; Mon, 1 Aug 2011 18:22:47 -0400
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 p71MMgGJ023999 for <ietf@ietf.org>; Mon, 1 Aug 2011 18:22:44 -0400
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 p71MMGZi013508 for <ietf@ietf.org>; Mon, 1 Aug 2011 18:22:16 -0400
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p71MM9gm013336 for <ietf@ietf.org>; Mon, 1 Aug 2011 18:22:09 -0400
Received: from [10.0.2.15] (ds135-91-110-234.dhcps.ugn.att.com[135.91.110.234]) by maillennium.att.com (mailgw1) with ESMTP id <20110801222209gw100e4lpfe> (Authid: tony); Mon, 1 Aug 2011 22:22:09 +0000
X-Originating-IP: [135.91.110.234]
Message-ID: <4E372712.2080508@att.com>
Date: Mon, 01 Aug 2011 18:22:10 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: A modest proposal for Friday meeting schedule
References: <BBF5DDFE515C3946BC18D733B20DAD2301B689@XMB105ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2301B689@XMB105ADS.rim.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 22:22:17 -0000

Do I hear a call for a morning cookie break?

     Tony hansen

On 8/1/2011 5:50 PM, Andrew Allen wrote:
> +1 with Adam
>
>
> ----- Original Message -----
> From: Adam Roach [mailto:adam@nostrum.com]
> Sent: Monday, August 01, 2011 04:38 PM
> To: Russ Housley<housley@vigilsec.com>
> Cc: IETF<ietf@ietf.org>
> Subject: Re: A modest proposal for Friday meeting schedule
>
> I'd like to join the sparse voices in speaking out against this plan. By
> Friday, I'm pretty well on a local meal schedule. Pushing lunch back by
> 2 hours would pretty well on guarantee that I'd be sugar-crashed and
> less coherent than normal by the end of Session II.
>
> /a
>
> On 8/1/11 10:10 AM, Russ Housley wrote:
>> I am discussing the possibility with the Secretariat and the IESG.  I will report back to the community as soon as possible.
>>
>> Russ
>>
>>
>>>>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
>>>>>
>>>>>> Something like this:
>>>>>> 8:30-11:00 Session I
>>>>>> 11:15-12:15 Session II
>>>>>> 12:30-13:30 Session III
>>>>> I really like it, as there are a bunch of post-IETF stuff, some of
>>>>> which starts in the afternoon and thus conflicts with the IETF.
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From moore@network-heretics.com  Mon Aug  1 15:36:36 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46AE81F0C54 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.936
X-Spam-Level: 
X-Spam-Status: No, score=-2.936 tagged_above=-999 required=5 tests=[AWL=-0.337, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QL3H9lLeEukS for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:36:35 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 83F8C1F0C53 for <ietf@ietf.org>; Mon,  1 Aug 2011 15:36:35 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1Qo16I-0008Es-Qf; Mon, 01 Aug 2011 18:36:43 -0400
Subject: Re: Drafts Submissions cut-off
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E3725F2.5050903@isi.edu>
Date: Mon, 1 Aug 2011 18:36:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C05EDE54-6789-479D-9796-CBBA336C8692@network-heretics.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com> <7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu> <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com> <4E371EEC.1050602@gmail.com> <6489201734580959064@unknownmsgid> <4E3725F2.5050903@isi.edu>
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da94039cd7aaf63dc35912dea8ca4a01ad684350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 22:36:36 -0000

On Aug 1, 2011, at 6:17 PM, Joe Touch wrote:

> Not all IDs are discussed at the upcoming IETF. It is inconvenient to =
need to delay an update or new submission simply because there's an IETF =
coming up.
>=20
> And all I've seen the deadline accomplish is that people post =
non-posted updates on local websites for discussion anyway.
>=20
> Unless there's a load issue, IMO there ought not be a blackout period.

Based on response time from the internet-drafts@ietf.org during that =
period, and also on delays in getting the I-Ds out the door, I believe =
there is a load issue.   (no complaints about the actual response or =
service, but they did seem quite busy)

Keith


From johnl@iecc.com  Mon Aug  1 15:58:14 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 372FD1F0C4E for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.39
X-Spam-Level: 
X-Spam-Status: No, score=-110.39 tagged_above=-999 required=5 tests=[AWL=0.809, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2dZtP-dEO0XK for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 15:58:13 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 62A711F0C49 for <ietf@ietf.org>; Mon,  1 Aug 2011 15:58:13 -0700 (PDT)
Received: (qmail 26531 invoked from network); 1 Aug 2011 22:58:20 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 1 Aug 2011 22:58:20 -0000
Received: (qmail 61763 invoked from network); 1 Aug 2011 22:58:19 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 1 Aug 2011 22:58:19 -0000
Date: 1 Aug 2011 22:57:57 -0000
Message-ID: <20110801225757.8527.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
In-Reply-To: <4C4ACC39-F9CC-429B-B6E6-CE0202C2C1BE@network-heretics.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: moore@network-heretics.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 22:58:14 -0000

>Perhaps.  But it's difficult to escape the impression that this is
>another example of IETF failing to solve an important problem by
>focusing on a portion of the problem that's easy to solve, and ruling
>the difficult part out of scope for the time being. 

It's definitely a case of the best being the enemy of the good.

There are some basic problems with any system of policy assertions:
the people making the assertions may be mistaken or lying (something
we've seen with ADSP), and there are precious few assertions that I
can make that are of any use to you in deciding how to deal with my
traffic.  Since you have no reason to believe my assertions unless you
already know me, you need mechanisms for third parties that can opine
about the credibility of self-assertions.  Inventing the mechanism is
only medium hard (see RFC 5518) but spinning up vouching services that
provide a usefully large amount of information is very hard.

R's,
John

From moore@network-heretics.com  Mon Aug  1 16:00:21 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CB45E8010 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.933
X-Spam-Level: 
X-Spam-Status: No, score=-2.933 tagged_above=-999 required=5 tests=[AWL=-0.334, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGJupFODseuY for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:00:21 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id DD6071F0C4E for <ietf@ietf.org>; Mon,  1 Aug 2011 16:00:20 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1Qo1TD-0001Uf-Tz; Mon, 01 Aug 2011 19:00:24 -0400
Subject: Re: DKIM Signatures now being applied to IETF Email
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110801225757.8527.qmail@joyce.lan>
Date: Mon, 1 Aug 2011 19:00:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com>
References: <20110801225757.8527.qmail@joyce.lan>
To: John Levine <johnl@iecc.com>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940f2ed6950cccc68c96c45b7ba221f6e68350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 23:00:21 -0000

On Aug 1, 2011, at 6:57 PM, John Levine wrote:

>> Perhaps.  But it's difficult to escape the impression that this is
>> another example of IETF failing to solve an important problem by
>> focusing on a portion of the problem that's easy to solve, and ruling
>> the difficult part out of scope for the time being.=20
>=20
> It's definitely a case of the best being the enemy of the good.
>=20
> There are some basic problems with any system of policy assertions:
> the people making the assertions may be mistaken or lying (something
> we've seen with ADSP), and there are precious few assertions that I
> can make that are of any use to you in deciding how to deal with my
> traffic.  Since you have no reason to believe my assertions unless you
> already know me, you need mechanisms for third parties that can opine
> about the credibility of self-assertions.  Inventing the mechanism is
> only medium hard (see RFC 5518) but spinning up vouching services that
> provide a usefully large amount of information is very hard.

I buy all of the above.

Does it follow, then, that the Right Thing to do is to avoid building =
any other parts of the system (even, say, the reputation service query =
protocol) until the easiest part is finished?

Keith


From mrw@lilacglade.org  Mon Aug  1 16:02:17 2011
Return-Path: <mrw@lilacglade.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE1D5E8013 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.955
X-Spam-Level: 
X-Spam-Status: No, score=-101.955 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nc9DuwsSVXUm for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:02:17 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 011715E8010 for <ietf@ietf.org>; Mon,  1 Aug 2011 16:02:16 -0700 (PDT)
Received: from [10.36.0.36] (pool-108-7-232-64.bstnma.fios.verizon.net [108.7.232.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.suchdamage.org (Postfix) with ESMTPSA id 409DD20289; Mon,  1 Aug 2011 19:05:08 -0400 (EDT)
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>
Date: Mon, 1 Aug 2011 19:02:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 23:02:17 -0000

I greatly prefer the current meeting schedule to one that packs meetings =
in to a shorter time period on Friday. As another poster mentioned, I =
too am tired by Friday, and I'm unlikely to stay focused through 5 =
straight hours of meetings, especially if I'm expected to keep going two =
hours past when I ate lunch on the previous four days.=20

If we don't want to hold meetings on Friday afternoons due to conflicts, =
I'd much rather see us eliminate one of the plenaries and hold meetings =
during that time slot.

Margaret

On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:

> Howdy,
> First I'd like to thank the organizers for IETF-81 for another =
well-run meeting.  The logistics and coordination for such an event must =
be daunting, and I know we (the attendees) tend to focus on the =
negatives rather than the positives... but we really are thankful for =
all the time and effort put into it.  Thank you!
>=20
> I would also like to propose a small change for future meetings.  On =
Friday, instead of having a 2.5 hour WG meeting, followed by a 1.5 hour =
lunch break, followed by 2 hours of WG meetings... perhaps we could just =
have 4.5 hours of WG meetings straight and also start a bit earlier? =20
>=20
> Something like this:
> 8:30-11:00 Session I
> 11:15-12:15 Session II
> 12:30-13:30 Session III
> End
>=20
> That way the people who need to get to an airport get more time, or =
fewer of them have to miss WG meetings, etc.  And it would help reduce =
costs for attendees if they can avoid staying Friday night at the hotel. =
 And lunch at 13:30 doesn't seem unreasonable (to me).
>=20
> I apologize if this has been brought up before.  I tried to find it =
from an old email thread for the "Experiment" at IETF-73 which added the =
Friday afternoon sessions, but did not see this proposal being =
suggested.
>=20
> -hadriel
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From moore@network-heretics.com  Mon Aug  1 16:27:40 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B4C11E8154 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.929
X-Spam-Level: 
X-Spam-Status: No, score=-2.929 tagged_above=-999 required=5 tests=[AWL=-0.330, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7h-KWz09WC+E for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:27:40 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 18F8B21F8C58 for <ietf@ietf.org>; Mon,  1 Aug 2011 16:27:40 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1Qo1th-0000Bj-AB; Mon, 01 Aug 2011 19:27:45 -0400
Subject: is IETF trying to do too much?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>
Date: Mon, 1 Aug 2011 19:27:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D992EEF2-5DAE-4884-951E-8B8CD370657C@network-heretics.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940909118a066a0e21d89f5c114162384ec350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 23:27:41 -0000

I have a different idea than trying to cram more meeting time into a =
busy week.

Is it possible that there are too many IETF working groups, or that IETF =
working groups are taking on too much work?

I keep going to working group meetings that have overflowing agendas of =
mostly presentations, with little time for discussion.

I also keep going to working group meetings where much of the time is =
devoted to someone doing a presentation of a new idea (with associated =
draft), after which the chair asks for a show of hands indicating =
whether the group should take on the draft as a work item. =20

I don't want to discourage people from bringing new work to working =
groups, but it seems to me that (a) working groups should devote plenty =
of time to discussing drafts that are already work items, and (b) making =
progress on old work should generally take precedence over considering =
new work. =20

It also seems to me that working groups, when considering whether to =
take on new work, should consider not only whether the work is within =
their charters and whether there are enough hands to take on new work, =
but also whether the new work will strain the group in any of several =
ways.  e.g. Will the adoption of new work make it more difficult for the =
working group to devote adequate time to reviewing and commenting on =
work already in progress?   Will adoption of the new work cause the =
working group's schedule to slip?    etc.

I understand very well that when technical people get immersed in a =
problem space, they see more and more problems that need to be solved.   =
But the trick that IETF needs to learn, I suspect, is making sure that =
the core problems are well solved, and that (when feasible) the =
solutions are sufficiently general that they can apply to a wide =
variation in problem spaces.    And sometimes, the trick is to walk away =
after the core problems are solved and avoid the temptation to try to =
nail down everything.

Another impression that I have is that IETF has a management structure =
that evolved when IETF was trying to accommodate 3,000+ participants at =
a meeting, and now we have around 1200.   And yet the rate of RFC =
production seems to have increased drastically, though perhaps that's =
just my imagination.   Are we putting out more documents of lower =
quality or relevance?

Keith


From paul.hoffman@vpnc.org  Mon Aug  1 16:27:51 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 864B511E8163 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:27:51 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pyr0Uy+JnYAm for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:27:50 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5AED611E813E for <ietf@ietf.org>; Mon,  1 Aug 2011 16:27:50 -0700 (PDT)
Received: from sn87.proper.com (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p71NRcUb078825 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 1 Aug 2011 16:27:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: Drafts Submissions cut-off
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>
Date: Mon, 1 Aug 2011 16:27:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C22E1819-CB43-4E39-8F78-070BCFA3A474@vpnc.org>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 23:27:51 -0000

On Aug 1, 2011, at 11:31 AM, Phillip Hallam-Baker wrote:

> Over the weekend I attempted to determine the rules for discussion of =
drafts at IETF meetings and was surprised to discover that they are not =
actually written down anywhere (other than on the meetings page). As a =
result we appear to have an anomalous situation in which an author who =
misses the cut-off date for ID submissions is in fact entitled to sit on =
the draft for two weeks and then submit when the ID queue re-opens.

Another situation, one which happened at this meeting, is that the =
authors turn in drafts before the cutoff, in the two weeks of no =
submissions there are criticisms of the document that the authors agree =
to fix, and the authors turn in the revised draft as soon as the window =
opens, before the WG actually meets.

> I suggest that this is a sub-optimal state of affairs. I see two =
solutions:
>=20
> 1) Codify the requirement that materials to be discussed at the =
meeting must be submitted before the cut-off and that submissions made =
during meetings are strictly limited to revisions occurring after and =
between WG sessions. [Except in exceptional circumstances with AD =
approval]
>=20
> 2) Eliminate the 2 week cut off completely.

Or, (3), specify somewhere that the submission window opens at the =
beginning of the meeting and allow WG chairs to decide what they want to =
do about new drafts. In the case last week, the draft was turned in and =
posted to the mailing list on Monday ahead of the meeting on Friday; the =
chairs seemed to like that.

--Paul Hoffman


From david.kessens@nsn.com  Mon Aug  1 16:36:02 2011
Return-Path: <david.kessens@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D0CB11E8163 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.425
X-Spam-Level: 
X-Spam-Status: No, score=-6.425 tagged_above=-999 required=5 tests=[AWL=0.174,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cY8xAITy6x3O for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:36:01 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 9F52211E8077 for <ietf@ietf.org>; Mon,  1 Aug 2011 16:36:00 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p71NZsTF030405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Aug 2011 01:35:54 +0200
Received: from localhost.localdomain ([10.138.49.170]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p71NZrOU022969; Tue, 2 Aug 2011 01:35:53 +0200
Received: from localhost.localdomain (X1 [127.0.0.1]) by localhost.localdomain (8.14.4/8.14.4) with ESMTP id p71NZpGI031334;  Mon, 1 Aug 2011 16:35:51 -0700
Received: (from david@localhost) by localhost.localdomain (8.14.4/8.14.4/Submit) id p71NZmEW031332; Mon, 1 Aug 2011 16:35:48 -0700
X-Authentication-Warning: localhost.localdomain: david set sender to david.kessens@nsn.com using -f
Date: Mon, 1 Aug 2011 16:35:48 -0700
From: David Kessens <david.kessens@nsn.com>
To: Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: A modest proposal for Friday meeting schedule
Message-ID: <20110801233548.GL25922@nsn.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 23:36:02 -0000

Margaret,

On Mon, Aug 01, 2011 at 07:02:22PM -0400, Margaret Wasserman wrote:
> 
> If we don't want to hold meetings on Friday afternoons due to conflicts,
> I'd much rather see us eliminate one of the plenaries and hold meetings
> during that time slot.

I was already planning to bring this up again in the IAB, but now that you
mention it here, I fully agree!

David Kessens
---

From hartmans@mit.edu  Mon Aug  1 16:39:10 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 623CE21F8CD7 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.993
X-Spam-Level: 
X-Spam-Status: No, score=-103.993 tagged_above=-999 required=5 tests=[AWL=-1.728, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7aEDnfNWTqI for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:39:09 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id BE80F21F8CA3 for <ietf@ietf.org>; Mon,  1 Aug 2011 16:39:08 -0700 (PDT)
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 118DA202C9; Mon,  1 Aug 2011 19:42:00 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 9B4F5422B; Mon,  1 Aug 2011 19:39:10 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Drafts Submissions cut-off
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com> <7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu> <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com>
Date: Mon, 01 Aug 2011 19:39:10 -0400
In-Reply-To: <3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com> (Keith Moore's message of "Mon, 1 Aug 2011 17:36:45 -0400")
Message-ID: <tsloc081z35.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: John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@MIT.EDU>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 23:39:10 -0000

>>>>> "Keith" == Keith Moore <moore@network-heretics.com> writes:

    Keith> On Aug 1, 2011, at 3:59 PM, Sam Hartman wrote:
    >> I think removing the cutoff is the right approach here.
    >> 
    >> I'd prefer that some date remain on the list of important meeting
    >> dates to remind ourselves that revisions should be in in time for
    >> people to read them.

    Keith> If memory serves, the original purpose of the cutoff was to
    Keith> avoid overtaxing the resources of the Secretariat in the
    Keith> period immediately prior to IETF meetings.  But it has also
    Keith> come in handy for ADs and others who feel the need to keep up
    Keith> with large numbers of documents from a variety of working
    Keith> groups.  I wouldn't blame any AD or WG chair for imposing a
    Keith> "no drafts submitted after the cutoff can be discussed at the
    Keith> meeting" rule.

Right.  I'd expect chairs to do something along these lines, moderated
for their group.
Having something on the important meeting dates as a general reminder
seems like a good idea to me.

From brian.e.carpenter@gmail.com  Mon Aug  1 16:52:44 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B40D65E8010 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XI1PP8uxOJ3 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 16:52:44 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id E217221F8BFB for <ietf@ietf.org>; Mon,  1 Aug 2011 16:52:43 -0700 (PDT)
Received: by iye7 with SMTP id 7so8821957iye.31 for <ietf@ietf.org>; Mon, 01 Aug 2011 16:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=I6NHsEPRsN5XS5NWOfVS35CrfzusHkLi8H60MmE7Nv0=; b=XAAPODlZm1lzMp72iZ2TjC8sCk+Th4Qonh6qb1VN+mSLS2R+L2SZyIPa8JOz6qSxfE Kc/0BhbmzDXpmhcI5Is1w36Nsz2DP6CV1bTC8qgPhWtlRpuHRYnyon7csRyaWyMEBei2 PXblJQMLYvwT5dGT+Ks/zlqAdie0kubW6j+us=
Received: by 10.42.167.138 with SMTP id s10mr1126497icy.165.1312242771236; Mon, 01 Aug 2011 16:52:51 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id h6sm7343507icw.19.2011.08.01.16.52.49 (version=SSLv3 cipher=OTHER); Mon, 01 Aug 2011 16:52:50 -0700 (PDT)
Message-ID: <4E373C50.9010402@gmail.com>
Date: Tue, 02 Aug 2011 11:52:48 +1200
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: David Kessens <david.kessens@nsn.com>
Subject: "technical" plenary [was: A modest proposal for Friday meeting schedule]
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>	<E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <20110801233548.GL25922@nsn.com>
In-Reply-To: <20110801233548.GL25922@nsn.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 23:52:44 -0000

On 2011-08-02 11:35, David Kessens wrote:
> Margaret,
> 
> On Mon, Aug 01, 2011 at 07:02:22PM -0400, Margaret Wasserman wrote:
>> If we don't want to hold meetings on Friday afternoons due to conflicts,
>> I'd much rather see us eliminate one of the plenaries and hold meetings
>> during that time slot.
> 
> I was already planning to bring this up again in the IAB, but now that you
> mention it here, I fully agree!

iirc, the second plenary was invented (partly be me, I suspect) because there
was no other session where cross-area architectural topics could be discussed
Parallel sessions for such topics are unsuitable, because of clashes
for almost everybody.

The situation now seems to be that we have such a plenary session automatically,
and if there isn't an important architectural topic, we invent one to fill
the time.

That seems backwards. Maybe the IAB and the IRTF should bid for a plenary slot
only when they have an important cross-area topic to propose, and if there isn't
a topic, there isn't a plenary. That would be more like a plenary BOF.

In any case, the IRTF Report, IAB Report and RSOC Report could certainly be
made in the other plenary.

   Brian


From johnl@iecc.com  Mon Aug  1 17:41:02 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA6FB1F0C3C for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 17:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.427
X-Spam-Level: 
X-Spam-Status: No, score=-110.427 tagged_above=-999 required=5 tests=[AWL=0.772, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lftE7hbi0B07 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 17:41:02 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 4FE4B1F0C3E for <ietf@ietf.org>; Mon,  1 Aug 2011 17:41:01 -0700 (PDT)
Received: (qmail 27665 invoked from network); 2 Aug 2011 00:41:08 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 2 Aug 2011 00:41:08 -0000
Received: (qmail 90292 invoked from network); 2 Aug 2011 00:41:08 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Aug 2011 00:41:08 -0000
Date: 2 Aug 2011 00:40:46 -0000
Message-ID: <20110802004046.33505.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
In-Reply-To: <C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: moore@network-heretics.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 00:41:03 -0000

> Does it follow, then, that the Right Thing to do is to avoid
> building any other parts of the system (even, say, the reputation
> service query protocol) until the easiest part is finished?

If we knew what to build, we'd build it.

We published RFC 5518 for VBR, a reputation system that sits on top of
DKIM, two years ago.  At this point I know of only one small VBR
provider, which I manage.

Also, even without general reputation systems, there are special cases
that are worth doing, e.g., there's a handful of large heavily phished
domains that sign all their mail, notably paypal.com and its ccTLD
variants.  For a medium or large mail system, it's worth adjusting the
spam filters to throw away mail purporting to be from Paypal that
doesn't have a signature.

R's,
John

From john-ietf@jck.com  Mon Aug  1 19:32:45 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C5521F86C3 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 19:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level: 
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtoOK+zRl4Fo for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 19:32:41 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3E321F86BC for <ietf@ietf.org>; Mon,  1 Aug 2011 19:32:40 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qo4mO-000M8T-Rs; Mon, 01 Aug 2011 22:32:25 -0400
Date: Mon, 01 Aug 2011 22:32:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Margaret Wasserman <mrw@lilacglade.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: A modest proposal for Friday meeting schedule
Message-ID: <88B2C4FA7EDF445D5E9292B0@PST.JCK.COM>
In-Reply-To: <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 02:32:46 -0000

--On Monday, August 01, 2011 19:02 -0400 Margaret Wasserman
<mrw@lilacglade.org> wrote:

>...
> If we don't want to hold meetings on Friday afternoons due to
> conflicts, I'd much rather see us eliminate one of the
> plenaries and hold meetings during that time slot.

Margaret,

FWIW, I personally think the plenaries have enough value, if
only as potential checks on the leadership, that I'd hate to see
one or both go.  I even think their substantive content is
occasionally helpful.

However, my main purpose in responding to the above is to advise
that you Be careful what you wish for.   I suggest that, until
we start pushing back aggressively on requests for meeting slots
(or, if necessary, on new WG requests), the number of slots that
are asked for will always expand to fill (or nearly fill) the
number of slots available.  The IESG has concluded that it is ok
to have three meeting slots on Fridays.  If we eliminate a
plenary to open up one or two more slots and use those slots to
stop using the Friday afternoon ones, I suggest that it will be
only a matter of time before we have enough demand for slots
that we expand back into the Friday afternoon times, retaining
the slots that eliminate the plenary.

If we really want to eliminate the Friday afternoon slots, then
we should eliminate those slots, ratcheting up the criteria for
getting meeting time to the point that we don't need them.
Whether or not we need two plenaries (or one or zero or three)
is almost independent of thet, even though we could get some
short-term relief.  Given the amount of burnout I often see by
Friday, simply dropping the afternoon sessions is my personal
favored solution.

If we want to keep the Friday afternoon slots, or keep the
number of slots that Friday afternoon gives us, then compressing
the day make sense to me.  Doing that compression according to
the suggestion has disadvantages --both those you cite and
others.  But maybe modifying the proposal to include a short
beverage and cookie break around 11:30 would make sense.  Maybe
there are other ideas too.  But I think the trends are very
clear and that, in the long run, eliminating a plenary would
"buy" an extra slot or two (and another very long and exhausting
day) but would not improve the Friday situation.

     john




From tobias.gondrom@gondrom.org  Mon Aug  1 19:50:48 2011
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6360711E8157 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 19:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.761
X-Spam-Level: 
X-Spam-Status: No, score=-94.761 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, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P3a3daK4Y-QU for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 19:50:47 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (lvps83-169-7-107.dedicated.hosteurope.de [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id 50FAC11E8152 for <ietf@ietf.org>; Mon,  1 Aug 2011 19:50:46 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=uieixYzsKwwSYum7uVEjGjEq6ESa+VliL0hR9JwVtMUuPn8pYGx9wNvB97NwTBQhWm4F2VzxHFDN8nTNaBLljV6toPs5ZuBrJULCeuXviloM4+LJcS6c/AVm2YeRO6t4; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type;
Received: (qmail 7641 invoked from network); 2 Aug 2011 04:50:45 +0200
Received: from ip-64-119-211-105.static.fibrenoire.ca (HELO ?172.16.52.23?) (64.119.211.105) by lvps83-169-7-107.dedicated.hosteurope.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Aug 2011 04:50:44 +0200
Message-ID: <4E376603.8090009@gondrom.org>
Date: Tue, 02 Aug 2011 03:50:43 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110627 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org, secdir@ietf.org, iesg@ietf.org,  draft-doria-genart-experience.all@tools.ietf.org, gen-art@ietf.org
Subject: Secdir review of draft-doria-genart-experience-04
Content-Type: multipart/alternative; boundary="------------070603010908060305070700"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 02:50:48 -0000

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

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.

This document is informational and covers the experiences of the General 
Area Review Team.
The Security Considerations of the draft are sufficient.

The following three comments:
1. minor editorial in section 4.3Form of Review
=> maybe replace the word "stole" with "derived" or any other word.
"Rather than invent new guidelines, the Gen-ART requirements for the 
form of a review stole liberally from" / "Rather than invent new 
guidelines, the Gen-ART requirements for the form of a review derived 
liberally from"

2. Section 12:
is it beneficial to list all current members of the Gen-ART per name in 
the draft?
- first are there any privacy issues with that?
- when adding or removing people from the team,the list in the I-D might 
become outdated and give false information on the current status. Would 
it be more appropriate/easier to update the draft to reference the 
current list of reviewers (e.g. on a tools web page) instead of listing 
them in the I-D?

3. Section 10 Security Considerations:  is ok so far.
On a personal comment/addition:
But maybe worth considering is that availability and integrity of sent 
reviews is also important:
I noticed that recently some emails to mail-aliases did not get 
delivered to the respective lists and therefore reviews and/or answers 
to reviews might not be received by the individuals on these lists.
Unfortunately this happens in some random fashion (for the same sender 
email and ietf tools aliases within a short time frame, some times it 
happens some times it doesn't), without a timely warning (but usually 
with a failure message 3-5 days after the email message has been 
posted). First investigations may suggest that this could be due to some 
spam filter or mail server configuration issues, however other reasons 
might also apply.
This can obviously impair the quality of the public review process if 
individual comments and reviews will not be delivered.

Kind regards, Tobias





--------------070603010908060305070700
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Arial">I have reviewed this document as part of the
      security directorate's <br>
      ongoing effort to review all IETF documents being processed by the
      <br>
      IESG.&nbsp; These comments were written primarily for the benefit of
      the <br>
      security area directors.&nbsp; Document editors and WG chairs should
      treat <br>
      these comments just like any other last call comments.<br>
      <br>
      This document is informational and covers the experiences of the
      General Area Review Team. <br>
      The Security Considerations of the draft are sufficient. <br>
      <br>
      The following three comments: <br>
      1. minor editorial in section 4.3</font><font face="Arial"> Form
      of Review<br>
    </font><font face="Arial">=&gt; maybe replace the word "stole" with
      "derived" or any other word.<br>
      "Rather than invent new guidelines, the Gen-ART requirements for
      the form of a review stole liberally from" / </font><font
      face="Arial">"Rather than invent new guidelines, the Gen-ART
      requirements for the form of a review derived liberally from"<br>
    </font><br>
    <font face="Arial">2. Section 12: <br>
      is it beneficial to list all current members of the Gen-ART per
      name in the draft? <br>
      - first are there any privacy issues with that? <br>
      - when adding or removing people from the team,</font><font
      face="Arial"> the list in the I-D might become outdated and give
      false information on the current status. </font><font
      face="Arial"> Would it be more appropriate/easier to update the
      draft to reference the current list </font><font face="Arial"> </font><font
      face="Arial">of reviewers </font><font face="Arial">(e.g. on a
      tools web page) </font><font face="Arial">instead of listing them
      in the I-D? <br>
      <br>
      3. Section 10 Security Considerations:&nbsp; is ok so far. <br>
      On a personal comment/addition: <br>
      But maybe worth considering is that availability and integrity of
      sent reviews is also important: <br>
      I noticed that recently some emails to mail-aliases did not get
      delivered to the respective lists and therefore reviews and/or
      answers to reviews might not be received by the individuals on
      these lists. <br>
      Unfortunately this happens in some random fashion (for the same
      sender email and ietf tools aliases within a short time frame,
      some times it happens some times it doesn't), without a timely
      warning (but usually with a failure message 3-5 days after the
      email message has been posted). First investigations may suggest
      that this could be due to some spam filter or mail server
      configuration issues, however other reasons might also apply. <br>
      This can obviously impair the quality of the public review process
      if individual comments and reviews will not be delivered. <br>
      <br>
      Kind regards, Tobias<br>
      <br>
      <br>
      <br>
      <br>
    </font>
  </body>
</html>

--------------070603010908060305070700--

From hsantos@isdg.net  Mon Aug  1 21:51:14 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E9921F8C22 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 21:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.792
X-Spam-Level: 
X-Spam-Status: No, score=-3.792 tagged_above=-999 required=5 tests=[AWL=-1.193, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvhmqnuuP4r8 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 21:51:13 -0700 (PDT)
Received: from pop3.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5E86521F8C21 for <ietf@ietf.org>; Mon,  1 Aug 2011 21:51:12 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2761; t=1312260678; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=LWI+Nb0Mgvo1KdcPLHct+JcR6VM=; b=gJBMBa81fnDxmS8Fs6zd ZhjAeIKIAkvDV3Ce7wqtgJN25vxdwd2hIxIEKTAnYWfhZV+SF5578YLlPNp4482H fqLtxlXrUEPAGfHGD32/kaVzqj4htJzS10oxbRU8AJem416QoufQ/AvE4PaSTeHN Gta/zZEfQ1odN6Z++96Q/c4=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 02 Aug 2011 00:51:18 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer); 
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 716164309.31802.4064; Tue, 02 Aug 2011 00:51:17 -0400
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312260407; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=41mvLyb+5hFqhqk2uy oZiviZ92tnoMFyBBL6VTBw7MY=; b=YFa80DnVEdrqd5bTUapcOZHZXM6EGIvoXo QYENUts9shHSR9OcFO1JNpgjU4TFup7xGlKUqta1kwNIIkU65+viem4+6JdUDsgB 2aplaF/BQVraWW2SDxB1pste+sfH01q8v0T8FJNQGlvc6Ygpl2+rL9+q788u98WK 5lswwe7Cc=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 02 Aug 2011 00:46:47 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1687445940.3711.6940; Tue, 02 Aug 2011 00:46:46 -0400
Message-ID: <4E378273.1050407@isdg.net>
Date: Tue, 02 Aug 2011 00:52:03 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E352A74.6080703@isdg.net>	<773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>	<201108011141.30549.scott@kitterman.com>	<F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com> <4C4ACC39-F9CC-429B-B6E6-CE0202C2C1BE@network-heretics.com>
In-Reply-To: <4C4ACC39-F9CC-429B-B6E6-CE0202C2C1BE@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 04:51:14 -0000

Keith Moore wrote:

> Perhaps.  But it's difficult to escape the impression that this is 
> another example of IETF failing to solve an important problem by focusing 
> on a portion of the problem that's easy to solve, and ruling the difficult 
> part out of scope for the time being.  Repeat as needed; you can always 
> partition the remaining part of the problem again.

It was not a difficult problem.  The issues were well understood long 
before Murray took over the DKIM specification. The WG security and 
requirements RFC productions clearly laid it out:

   RFC4686  Analysis of Threats Motivating DKIM
   RFC5016  Requirements for a DKIM Signing Practices Protocol

The remaining technical problem was how to scale the authorization of 
3rd party signer.   The proposals

   ASL  Allowed Signer List (good for small systems, does not scale)
   TPA  Third Party Authorization (appear to scale, but complex)
   ATPS Authorized Third Party Signer (easier version of TPA)

But there was a fundamental mindset and marketing conflict.  It was a 
conflict of 3rd party resigner market right to exist uncontrolled, 
unrestricted regardless of originating DKIM message claims.

The WG could not continue to complete RF5017 ADSP when the then out of 
scope Trust ideas took over and promoted a market of unrestricted 
resigners.  If ADSP became a standard then these resigners would be in 
violation of a security standard, and it would be a serious problem if 
they intentionally and neglected a security protocol when they 
resigned mail potentially distributing harmful mail

The easy solution is to toss out ADSP, like it never existed. No one 
should follow original domain policy declarations.

But this only shifted to the problem to the resigner who has no sort 
of policy wrappers.  What happens with resigners resign resigned mail? 
  Who will protect them?

Without based line protocol consistent controls and guidelines to 
follow, I'm afraid DKIM signing is fast becoming is rabid hop to hop 
message signature stamping broadcasting concept where the only 
remaining benefit is to make sense of the last signer which is never a 
problem in the authorized and known mail world.  Its a problem with 
the anonymous world and a DKIM-signature has no value here when the 
signer is unknown. Since DKIM-signature requires the 5322.From address 
to be hash bound to the signature, the lost of policy allowed the 
anonymous abuse of these domains to continue.

The issue is straight forward, either resigners support signing 
controls or not. Obviously the latter was the easy way for THEM but it 
didn't solve the problem.  No matter way a policy concept is required.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From randy@qualcomm.com  Mon Aug  1 22:15:05 2011
Return-Path: <randy@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A368221F8B60 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 22:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f+U3xZQyeh8z for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 22:15:04 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id C918D21F8B5E for <ietf@ietf.org>; Mon,  1 Aug 2011 22:15:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1312262113; x=1343798113; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p0624061fca5d361f8806@dhcp-44e5.meeting.i etf.org>|In-Reply-To:=20<88B2C4FA7EDF445D5E9292B0@PST.JCK .COM>|References:=20<F9F155A0-142F-4D48-8A89-690BC22CECB1 @acmepacket.com>=0D=0A=20<E9E015CE-912E-4509-988C-53047CF D923B@lilacglade.org>=0D=0A=20<88B2C4FA7EDF445D5E9292B0@P ST.JCK.COM>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date: =20Mon,=201=20Aug=202011=2022:09:08=20-0700|To:=20John=20 C=20Klensin=20<john-ietf@jck.com>,=20Margaret=20Wasserman =0D=0A=09<mrw@lilacglade.org>,=20Hadriel=20Kaplan=20<HKap lan@acmepacket.com>|From:=20Randall=20Gellens=20<randy@qu alcomm.com>|Subject:=20Re:=20A=20modest=20proposal=20for =20Friday=20meeting=20schedule|CC:=20IETF-Discussion=20li st=20<ietf@ietf.org>|MIME-Version:=201.0|Content-Type:=20 text/plain=3B=20charset=3D"us-ascii"=3B=20format=3Dflowed |X-Random-Sig-Tag:=201.0b28|X-Originating-IP:=20[172.30.3 9.5]; bh=L1ZZzXfvfJaFhqGGsETe6qCdXx0a2NNPiQcoka0aAhg=; b=BS+k6VbeICcpSBppATX7swmBG2muiI7Vgck7DvmNsr/27UTqblheeAh2 p4BHw/tZ4zs5jCms3htCfeAKmneC+VeQ/tDSGpUiVJrYoRLHL//0lxgfu WGV11pWY7DdXRAqA9FL38c8ZFRroz8AKEwzkOvygYOEm/vQG2h8ChSV8L 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6425"; a="107460304"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine01.qualcomm.com with ESMTP; 01 Aug 2011 22:15:12 -0700
X-IronPort-AV: E=Sophos;i="4.67,304,1309762800"; d="scan'208";a="118438939"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 01 Aug 2011 22:15:12 -0700
Received: from dhcp-44e5.meeting.ietf.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.323.0; Mon, 1 Aug 2011 22:15:10 -0700
Message-ID: <p0624061fca5d361f8806@dhcp-44e5.meeting.ietf.org>
In-Reply-To: <88B2C4FA7EDF445D5E9292B0@PST.JCK.COM>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <88B2C4FA7EDF445D5E9292B0@PST.JCK.COM>
X-Mailer: Eudora for Mac OS X
Date: Mon, 1 Aug 2011 22:09:08 -0700
To: John C Klensin <john-ietf@jck.com>, Margaret Wasserman <mrw@lilacglade.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: A modest proposal for Friday meeting schedule
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 05:15:05 -0000

I'd like to add my voice to those who wouldn't like the proposed 
compressed Friday schedule.

However, I do think there are things we could try to tweak the 
schedule.  For example, perhaps on one or two days, we could split 
the morning slot into two slots of 1:10 with a ten-minute break. 
Many WGs don't need 2.5 hours.

Also, a few years back at the Paris IETF, if I recall correctly, we 
had a one hour morning slot followed by a two-hour slot, then a 
later-than-usual lunch break.  Personally, I think that worked pretty 
well.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Implementation is the sincerest form of flattery.

From hsantos@isdg.net  Mon Aug  1 23:06:14 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2287211E8090 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 23:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.745
X-Spam-Level: 
X-Spam-Status: No, score=-3.745 tagged_above=-999 required=5 tests=[AWL=-1.146, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bq7xM5dhf1E6 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 23:06:12 -0700 (PDT)
Received: from winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6B23C11E8091 for <ietf@ietf.org>; Mon,  1 Aug 2011 23:06:12 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6560; t=1312265179; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=CcCVWjjNrB+Y0KrNnoBtIEfuk9c=; b=B1SuZ1TTOUeN3oSNRljF HNeQAN/60DF6t4lF5p2+gdNx2AubcslNPus6aSkDcRskjo2TIpIfPfCZzQGeGVbo WGkMKuXm4gSR4/ayeLe7FUrlUeJ7gKfDkkeDqRivbphkefZl3tHsvoN7HvPzi90j r+FwwfzyJjxJ+HZ527B95CM=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 02 Aug 2011 02:06:19 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer); 
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 720664547.31856.4220; Tue, 02 Aug 2011 02:06:18 -0400
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312264907; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=zuyMHRYXKWDstmyJXI jAH+9LSkDdsKpgamA07vf6zNg=; b=Dy7JZ9ryNrdB0UUXPqCj9HiTQcqzpODS8y 50aoWKeP9LGo9gJc0VtXanDq0kQDWU5kzvHat0nIoD3wi49VkpJeCGN4NsOh1tIh BEVY/IMr79tbtyWQU5w1ijY/yYnu87hCt3y+0aQeWUNSLtG+FK2WgzS5nVu7YMoI HVIB3Urnk=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 02 Aug 2011 02:01:47 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1691945752.3717.5712; Tue, 02 Aug 2011 02:01:46 -0400
Message-ID: <4E379408.4050008@isdg.net>
Date: Tue, 02 Aug 2011 02:07:04 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf <ietf@ietf.org>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>	<CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>	<00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net> <F5833273385BB34F99288B3648C4F06F13512DF4CE@EXCH-C2.corp.cloudmark.com> <4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>
In-Reply-To: <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 06:06:14 -0000

Nathaniel Borenstein wrote:
> I find it amazing how many different ways there are to criticize DKIM 
> for not doing something it was never intended to do.  DKIM is a small 
> building block that enables new functionality, but such functionality 
> is beyond the scope of DKIM.

Note: We have an advanced implementation of DKIM as a product line so 
my concerns are not outsider views.  My input is 100% based on 
implementation and field experiences.

Policy was very fundamental to the understanding of DKIM, it was part 
of the original DomainKeys and DKIM expanded this powerful concept 
with a wider range of Author Domain policies.

I never disputed the out of scope 3rd party trust policy model but it 
addressed a different problem - trust, if any, of a valid signature 
after the violations are filtered by author domain policies, if any. 
  Two different layers and this was outlined in my 2006 DKIM Signer 
Authorization Protocol (DSAP) I-D.

The problem was a conflict in different market ideas - an unrestricted 
resigner DKIM mail market which 1st party security controls would 
conflict with.  They  simply did not want the 1st party to override 
any 3rd party signers.  This conflict was highlighted in the SSP 
requirements with the last minute addition in RFC5016:

        "Requirements for a DKIM Signing Practices Protocol"

when item #10 was added in section 5.3 to appease the opponents of 1st 
party SSP polices:

    10. SSP MUST NOT provide a mechanism that impugns the existence of
        non-first party signatures in a message.  A corollary of this
        requirement is that the protocol MUST NOT link practices of first
        party signers with the practices of third party signers.

          INFORMATIVE NOTE: the main thrust of this requirement is that
          practices should only be published for that which the publisher
          has control, and should not meddle in what is ultimately the
          local policy of the receiver.

          Refs: Deployment Consideration, Section 4.3.

This was unfortunate. On the one hand it suggest we should not meddle 
in how local receivers will behave yet it imposes a MUST NOT mandate 
in allowing the 1st party policy to override a 3rd party signature 
trust policy.

> DKIM does one thing, and one thing only:  It uses a cryptographic signature 
> to associate a domain with a message.  

It does more than that.  DKIM has a fundamental requirement to hash 
bound the 5322.From field to the signature.  Its the only header that 
MUST be signed. All others are optional.  This 5322.FROM bind provide 
the only anchor possible that can be repudiated.

So there are two principal domains associated with a signature:

    Signer        d= value in signature
    5322.From     DKIM requirement

> By doing so, it creates strong evidence that the message passed 
> through that domain at some point and has not been significantly 
> modified since.

I don't see this. The resigner can be totally opaque with no 
association with the original domain.  The signer::author association 
begins with the original signature creation by the author domain 
selecting a signer and/or prearranged with an outsource signing service.

Now, what people are looking for as well, is when there is 
resigner::author association when the author is participating in a 
resigner network.  Currently we call this a 3rd party Authorization.

> With such an anchor, we can begin to build stronger and more robust 
> systems for analyzing the desirability of messages, as we are now trying 
> to do in the REPUTE work, because it allows us to push our forensic 
> analysis upstream a bit.  

Heuristic wrappers are interesting but its a different problem. It 
doesn't adequately address what a deterministic solution can do for you.

> If, for example, the IETF mailing list software only allows posting 
> by list members, but itself trusts the sender's header fields, then 
> an IETF DKIM signature tells me only that the IETF servers think a 
> message passed that test.  

There you go, you made an POLICY STATEMENT - translate it into a 
protocol for everyone to follow and check.

> That's obviously not perfect, but it's slightly stronger than what came 
> before -- it is still possible to forge a message before sending it to the 
> list, but much harder to forge a message to look as if it came from 
> the list exploder.  

This is all besides the point. Its all about detection what YOU think 
is a violation of a protocol logic.  Whatever you produce in REPUTE, 
you are producing a idea for people to follow consistency based on 
some baseline rules established.

> We've had a long history of grand plans for user authentication on 
> the Internet.  Those plans have largely failed.  

There are plenty of authentication protocols that works very well, and 
fundamental to our current network.

The issue here is a DKIM signer market run wild uncontrolled and if we 
don't get our act together soon to put a security wrapper around it, 
it risk becoming yet another wasted header with little to no value and 
perhaps limited to exclusive communications in private communications 
networks.

> I think an incremental approach like DKIM has a better chance, 
> but it is obviously vulnerable to being dismissed by those who 
> see a small improvement as not worth bothering with.  The best is 
> the enemy of the good.  -- Nathaniel

I have invested dearly in dollars, time and energy and we have 
produced an advanced DKIM implementation into our product line with a 
high degree of mail component integration - its a commercial product, 
not just for our own use.

My concerns are 100% sincere as I believe that it might not be too 
late for DKIM to correct what has occurred - the deemphasis of the 
single DKIM requirement to hash bind the 5322.FROM author to the 
signature means.

This is an association you can not ignore because the entire mail 
infrastructure relies on the 5322.From as a fundamental header across 
all mail networks, all mail devices, etc, etc. etc.   This is a not a 
question that can be separated which unfortunately the DKIM 
specification Abstract states as a goal of DKIM:

    DKIM separates the question of the identity of the signer of the
    message from the purported author of the message.

What question is that? Is the question this?

    Do author domains have any say on who signs for them
    and who/what is considered unauthorized signatures
    versus authorized resigning?

Anyway, thanks for your comments.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From jaap@bartok.nlnetlabs.nl  Mon Aug  1 23:24:04 2011
Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E797C11E80A0 for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 23:24:04 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKMCBuSCXiGu for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 23:24:04 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by ietfa.amsl.com (Postfix) with ESMTP id DC99011E808E for <ietf@ietf.org>; Mon,  1 Aug 2011 23:24:03 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.5/8.14.5) with ESMTP id p726O90d094048 for <ietf@ietf.org>; Tue, 2 Aug 2011 08:24:09 +0200 (CEST) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201108020624.p726O90d094048@bartok.nlnetlabs.nl>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: A modest proposal for Friday meeting schedule
In-reply-to: <20110801233548.GL25922@nsn.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <20110801233548.GL25922@nsn.com>
Comments: In-reply-to David Kessens <david.kessens@nsn.com> message dated "Mon, 01 Aug 2011 16:35:48 -0700."
Date: Tue, 02 Aug 2011 08:24:09 +0200
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (bartok.nlnetlabs.nl [127.0.0.1]); Tue, 02 Aug 2011 08:24:09 +0200 (CEST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 06:24:05 -0000

    
    > 
    > If we don't want to hold meetings on Friday afternoons due to conflicts,
    > I'd much rather see us eliminate one of the plenaries and hold meetings
    > during that time slot.
    
    I was already planning to bring this up again in the IAB, but now that you
    mention it here, I fully agree!
    
Before we start to fiddle with time slots, why don't we wait before the
results of the traditional survey-on-last-meeting has been published.

	jaap

From gwz@net-zen.net  Tue Aug  2 01:17:47 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B8A21F8A69 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 01:17:47 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ivrTJ46dUB8b for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 01:17:46 -0700 (PDT)
Received: from p3plsmtpa07-08.prod.phx3.secureserver.net (p3plsmtpa07-08.prod.phx3.secureserver.net [173.201.192.237]) by ietfa.amsl.com (Postfix) with SMTP id 8D58521F8A30 for <ietf@ietf.org>; Tue,  2 Aug 2011 01:17:45 -0700 (PDT)
Received: (qmail 11078 invoked from network); 2 Aug 2011 08:16:22 -0000
Received: from unknown (124.120.79.57) by p3plsmtpa07-08.prod.phx3.secureserver.net (173.201.192.237) with ESMTP; 02 Aug 2011 08:16:22 -0000
Message-ID: <4E37B24E.7020104@net-zen.net>
Date: Tue, 02 Aug 2011 15:16:14 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: David Kessens <david.kessens@nsn.com>
Subject: Re: A modest proposal for Friday meeting schedule
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <20110801233548.GL25922@nsn.com>
In-Reply-To: <20110801233548.GL25922@nsn.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------080005040707030307040608"
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 08:17:47 -0000

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

On 8/2/2011 6:35 AM, David Kessens wrote:
> 
> Margaret,
> 
> On Mon, Aug 01, 2011 at 07:02:22PM -0400, Margaret Wasserman wrote:
>> 
>> If we don't want to hold meetings on Friday afternoons due to
>> conflicts, I'd much rather see us eliminate one of the plenaries
>> and hold meetings during that time slot.
> 
> I was already planning to bring this up again in the IAB, but now
> that you mention it here, I fully agree!

Actually, I'd like to see both plenaries moved to Friday & the resulting
time be delegated to more useful things.  People having a deep need to
attend them can stay over Friday night while others can go home.

--------------080005040707030307040608
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------080005040707030307040608--

From daedulus@btconnect.com  Tue Aug  2 01:30:47 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A63CF21F8CA5 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 01:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.17
X-Spam-Level: 
X-Spam-Status: No, score=-2.17 tagged_above=-999 required=5 tests=[AWL=-0.190,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ya4tiG6+qQG9 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 01:30:47 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr11.btconnect.com [213.123.26.189]) by ietfa.amsl.com (Postfix) with ESMTP id D68A921F8EE5 for <ietf@ietf.org>; Tue,  2 Aug 2011 01:30:46 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.ncs.ibs-infra.bt.com [10.87.14.166]) by c2beaomr11.btconnect.com (MOS 3.10.10a-GA) with ESMTP id ADT11719; Tue, 2 Aug 2011 09:30:09 +0100 (BST)
Received: (from localhost [127.0.0.1]) by c2beaomr06.btconnect.com (MOS 4.2.2-FCS) id EBF69578; Tue,  2 Aug 2011 09:30:09 +0100 (BST)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr06.btconnect.com with SMTP id EBF69498; Tue, 02 Aug 2011 09:30:05 +0100 (BST)
Message-ID: <004f01cc50e5$8ec04580$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "David Kessens" <david.kessens@nsn.com>, "Russ Housley" <housley@vigilsec.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com><B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com><60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com><20110801133935.GC89723@verdi><2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com> <20110801204903.GG25922@nsn.com>
Subject: Re: A modest proposal for Friday meeting schedule
Date: Tue, 2 Aug 2011 09:26:47 +0200
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.4E37B58C.00E9, actions=TAG
X-Junkmail-Status: score=50/50, host=c2beaomr06.btconnect.com
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 08:30:47 -0000

---- Original Message -----
From: "David Kessens" <david.kessens@nsn.com>
To: "Russ Housley" <housley@vigilsec.com>
Cc: "IETF" <ietf@ietf.org>
Sent: Monday, August 01, 2011 10:49 PM
>
> Russ,
>
> On Mon, Aug 01, 2011 at 11:10:24AM -0400, Russ Housley wrote:
> > I am discussing the possibility with the Secretariat and the IESG.  I will
report back to the community as soon as possible.
>
> I don't think this proposal should be pursued. The breaks fulfil an
> important function and there is nothing wrong with a starting time of 9am.
>
> The friday meetings are always going to be tough at the end of a week long
> meeting but trying to compress the friday schedule would only make it
> harder.

Yes, and has been said, Friday is travel time; with a 17:30 flight, a time to
dip into those sessions I never normally attend, with an 09:30 flight, I'm gone.
Anything that matters needs to be Monday to Thursday, and that includes
Plenaries. They may be boring, but that in itself is an important reflection of
the various I***s.

Tom Petch
>
> David Kessens
> ---
>
> > >>> On Jul 31, 2011, at 11:40 AM, Hadriel Kaplan wrote:
> > >>>
> > >>>> Something like this:
> > >>>> 8:30-11:00 Session I
> > >>>> 11:15-12:15 Session II
> > >>>> 12:30-13:30 Session III
> > >>>
> > >>> I really like it, as there are a bunch of post-IETF stuff, some of
> > >>> which starts in the afternoon and thus conflicts with the IETF.
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>
> David Kessens
> ---
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From daedulus@btconnect.com  Tue Aug  2 02:08:34 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59AD321F8EA2 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 02:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.138
X-Spam-Level: 
X-Spam-Status: No, score=-2.138 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZIEao2HEunW for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 02:08:33 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr11.btconnect.com [213.123.26.189]) by ietfa.amsl.com (Postfix) with ESMTP id 8D4BE21F8D97 for <ietf@ietf.org>; Tue,  2 Aug 2011 02:08:32 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr07.ncs.ibs-infra.bt.com [10.87.14.167]) by c2beaomr11.btconnect.com (MOS 3.10.10a-GA) with ESMTP id ADT12323; Tue, 2 Aug 2011 10:03:39 +0100 (BST)
Received: (from localhost [127.0.0.1]) by c2beaomr07.btconnect.com (MOS 4.2.2-FCS) id DWF67117; Tue,  2 Aug 2011 10:03:39 +0100 (BST)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr07.btconnect.com with SMTP id DWF67023; Tue, 02 Aug 2011 10:03:34 +0100 (BST)
Message-ID: <013a01cc50ea$3c4f48a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Keith Moore" <moore@network-heretics.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com><20110801185545.GG22542@shinkuro.com><CAC4RtVD5U9d-08STjR_BNbFyQ=PuaF4dbY-uaBmW7tTnmw3=Qg@mail.gmail.com><7EB2BF41472FEC1438355A0B@PST.JCK.COM> <tslwrew2995.fsf@mit.edu><3A4B3EAE-35EE-4798-B46E-528DED4420AC@network-heretics.com><4E371EEC.1050602@gmail.com> <6489201734580959064@unknownmsgid><4E3725F2.5050903@isi.edu> <C05EDE54-6789-479D-9796-CBBA336C8692@network-heretics.com>
Subject: Re: Drafts Submissions cut-off
Date: Tue, 2 Aug 2011 10:00:20 +0200
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.4E37BD66.006A, actions=tag
X-Junkmail-Status: score=50/50, host=c2beaomr07.btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 09:08:34 -0000

----- Original Message -----
From: "Keith Moore" <moore@network-heretics.com>
To: "Joe Touch" <touch@ISI.EDU>
Cc: <ietf@ietf.org>
Sent: Tuesday, August 02, 2011 12:36 AM

> On Aug 1, 2011, at 6:17 PM, Joe Touch wrote:
>
> > Not all IDs are discussed at the upcoming IETF. It is inconvenient to need
to delay an update or new submission simply because there's an IETF coming up.
> >
> > And all I've seen the deadline accomplish is that people post non-posted
updates on local websites for discussion anyway.
> >
> > Unless there's a load issue, IMO there ought not be a blackout period.
>
> Based on response time from the internet-drafts@ietf.org during that period,
and also on delays in getting the I-Ds out the door, I believe there is a load
issue.   (no complaints about the actual response or service, but they did seem
quite busy)

Yes, except that I do see complaints, of I-Ds appearing after a cutoff, with the
explanation being that there has been a delay of some days from submission to
announcement, so the I-Ds were submitted before the cutoff but appeared after.
Which suggests that the system gets overloaded

And this is a minor problem.  As suggested in another post, the cutoff is a good
time
to do a trawl, especially of unadopted I-Ds which may not have been mentioned
on the list, of all announced I-Ds to catch any that I have missed.

On balance, the cutoff is a good thing.

Tom Petch

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


From daedulus@btconnect.com  Tue Aug  2 02:26:41 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFC721F8EEF for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 02:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.125
X-Spam-Level: 
X-Spam-Status: No, score=-2.125 tagged_above=-999 required=5 tests=[AWL=-0.126, BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfK8c7hbL1QP for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 02:26:40 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id 2004321F8EC3 for <ietf@ietf.org>; Tue,  2 Aug 2011 02:26:39 -0700 (PDT)
Received: from host109-153-78-164.range109-153.btcentralplus.com (HELO pc6) ([109.153.78.164]) by c2beaomr06.btconnect.com with SMTP id EBG40163; Tue, 02 Aug 2011 10:25:32 +0100 (BST)
Message-ID: <018601cc50ed$4d6f1ae0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Nathaniel Borenstein" <nsb@guppylake.com>
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>	<CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>	<00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net><F5833273385BB34F99288B3648C4F06F13512DF4CE@EXCH-C2.corp.cloudmark.com><4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
Date: Tue, 2 Aug 2011 10:11:40 +0200
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.4E37C28B.0023, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.2.82714:17:7.944, ip=109.153.78.164, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __KNOWN_FREEWEB_URI1[http://santronics.blogspot.com [blogspot.com] [blogspot.com]], __ANY_URI, BLOGSPOT_URI, __URI_NO_PATH, __CP_URI_IN_BODY, BODY_SIZE_6000_6999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, KNOWN_FREEWEB_URI, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4E37C28D.00A5,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 09:26:41 -0000

----- Original Message -----
From: "Nathaniel Borenstein" <nsb@guppylake.com>
To: "Hector Santos" <hsantos@isdg.net>
Cc: "ietf" <ietf@ietf.org>
Sent: Monday, August 01, 2011 2:48 PM
Subject: Re: DKIM Signatures now being applied to IETF Email


> I find it amazing how many different ways there are to criticize DKIM for not
doing something it was never intended to do.  DKIM is a small building block
that enables new functionality, but such functionality is beyond the scope of
DKIM.

I agree that DKIM does exactly what it sets out to do, but am not amazed that it
attracts criticism.  When people have a need, and want a technical solution, and
then find that what at first sight appeared to be a solution is not one, then
they
may be disappointed, and be critical.  That is human nature.

When that happens is a time to reflect, to look at the requirements that were
not met.  If they  were captured and rejected, at least for the time being, then
noone has any
cause to be upset.  But if the requirements were not captured, then perhaps
it is a time to contemplate that, how were they missed, what else might have
been
missed and whether or not that should be acted upon in future.

And, as I said before, my criticism is of those who have imposed this technology
on the IETF lists, not of the technology itself.

Tom Petch
>
> DKIM does one thing, and one thing only:  It uses a cryptographic signature to
associate a domain with a message.  By doing so, it creates strong evidence that
the message passed through that domain at some point and has not been
significantly modified since.
>
> Whether that domain is good guys or bad guys, senders or resenders, Coke or
Pepsi, is completely irrelevant.  It is a small nugget of evidence to provide an
anchor point for forensics stronger than what have come before.  It tells us
that the named domain considered the message reasonable to send or resend, for
its own reasons -- its own forensic evidence, its nefarious intent, or the phase
of the moon.  With such an anchor, we can begin to build stronger and more
robust systems for analyzing the desirability of messages, as we are now trying
to do in the REPUTE work, because it allows us to push our forensic analysis
upstream a bit.  It does not relieve downstream software of the need to decide
how to feel about the signing domain, whether it's a spammer, a copy-cat, or
anyone else.
>
> If, for example, the IETF mailing list software only allows posting by list
members, but itself trusts the sender's header fields, then an IETF DKIM
signature tells me only that the IETF servers think a message passed that test.
That's obviously not perfect, but it's slightly stronger than what came
before -- it is still possible to forge a message before sending it to the list,
but much harder to forge a message to look as if it came from the list exploder.
That is progress -- very very small, slow, progress.  If, at some point, the
list exploder starts only passing through messages that themselves have valid
DKIM signatures, it will be significantly more progress, but it won't do
anything to stop a spammer from subscribing to the IETF list and
DKIM-authenticating himself.  For that we'll need reputation information --
another small step, which we're trying to initiate with REPUTE.
>
> We've had a long history of grand plans for user authentication on the
Internet.  Those plans have largely failed.  I think an incremental approach
like DKIM has a better chance, but it is obviously vulnerable to being dismissed
by those who see a small improvement as not worth bothering with.  The best is
the enemy of the good.  -- Nathaniel
>
>
> On Jul 31, 2011, at 6:12 AM, Hector Santos wrote:
>
> > You continue to not comprehend (or rather ignore) what continues to plaque
DKIM - the lack of fault detection. Its why it continues to have a hard time and
have people who actually believe in this promising protocol "bitch" about it.
If these "big email" providers (or anyone for that matter) begin to make
assertions about what is good about their mail then they better be ready for the
violations of such assertions to be rejected.  You can't have it just one way
and mandate this is the only way to process this overhead - looking for good
mail only and ignoring all the violations and illogically treating it like it
was never signed or compromised or attempted to be compromised.
> >
> > The overall difficulty is that originality is lost - the original author or
dkim signer has lost or lacks any protocol guidance to tell resigners that the
mail they are about the process might be bad - according to the original author
domain.
> >
> > If the resigner is going to intentionally and neglectfully ignore all
original claims about the original domain signing practice, then how do you
expect the anonymous "copy-cat" abuse to be controlled?
> >
> >
> > Murray S. Kucherawy wrote:
> >>> -----Original Message-----
> >>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
t.petch
> >>> Sent: Saturday, July 30, 2011 3:26 AM
> >>> To: Barry Leiba
> >>> Cc: ietf
> >>> Subject: Re: DKIM Signatures now being applied to IETF Email
> >>>
> >>> Sadly, I do not see it being used in the mailing lists where an
> >>> organisation is sending me directly data I would like to be able to rely
on
> >>> - which I think fits the applicability well - and instead, I see it
> >>> being used on a mailing list such as those in the IETF where I
> >>> believe that the costs outweigh the benefits - and I have no choice
> >>> about that:-(.
> >> There has been some post-DKIM talk recently about the idea of "transient
trust", wherein (to use this example) ietf.org would verify the signature on an
arriving list submission, attach an RFC5451 header field that indicates the
results of that verification, then send the message out to the list with that
added field and a new ietf.org signature that "covered" it.  Then, if you decide
to believe ietf.org's claims about the original signature, you know more than
you would otherwise.
> >> This hasn't been widely deployed yet, but some big email providers are
currently playing with the idea.
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >
> > --
> > Hector Santos, CTO
> > http://www.santronics.com
> > http://santronics.blogspot.com
> >
> >
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From eburger-l@standardstrack.com  Tue Aug  2 04:23:43 2011
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57DE721F8DC3 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 04:23:43 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M0VBQ+E1Ssqm for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 04:23:42 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 6806A21F8D63 for <ietf@ietf.org>; Tue,  2 Aug 2011 04:23:42 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=xU3QekMsMCGCxUOB0Qa+DijlcU1rmSQzmp2hSUQtAIBX0CdLUEwcdGE74QkiqZJaE7frz4CPbR5O062FhHM+4K3ptGEoemDTthN8kh9GvS+Z8eAuwxMtGZdKtEno55Vj;
Received: from cpe-72-226-11-112.nycap.res.rr.com ([72.226.11.112] helo=[192.168.1.6]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QoD4g-0003tP-0X for ietf@ietf.org; Tue, 02 Aug 2011 04:23:50 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: A modest proposal for Friday meeting schedule
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <88B2C4FA7EDF445D5E9292B0@PST.JCK.COM>
Date: Tue, 2 Aug 2011 07:23:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <85F40D8B-0BBF-4F87-BD00-6A44FAA9EBD9@standardstrack.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <88B2C4FA7EDF445D5E9292B0@PST.JCK.COM>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 11:23:43 -0000

I think John has the issue nailed.  I think it would be easy to try to =
eliminate the plenaries and then end up with a full Friday, anyway.  I =
would offer that it would be very difficult, however, to take a =
compressed Friday and later add an afternoon to it.  Thus, I am much =
more in favor of a compressed Friday, perhaps with some of the mentioned =
tweaks (a cookie break or a graham cracker and milk break for those who =
know the Montessori routine), than either leaving Friday as is or =
eliminating the Plenaries.

BTW, has anyone noticed the trend of doing more and more on the Sunday =
and Saturday *before* IETF week?

On Aug 1, 2011, at 10:32 PM, John C Klensin wrote:

>=20
>=20
> --On Monday, August 01, 2011 19:02 -0400 Margaret Wasserman
> <mrw@lilacglade.org> wrote:
>=20
>> ...
>> If we don't want to hold meetings on Friday afternoons due to
>> conflicts, I'd much rather see us eliminate one of the
>> plenaries and hold meetings during that time slot.
>=20
> Margaret,
>=20
> FWIW, I personally think the plenaries have enough value, if
> only as potential checks on the leadership, that I'd hate to see
> one or both go.  I even think their substantive content is
> occasionally helpful.
>=20
> However, my main purpose in responding to the above is to advise
> that you Be careful what you wish for.   I suggest that, until
> we start pushing back aggressively on requests for meeting slots
> (or, if necessary, on new WG requests), the number of slots that
> are asked for will always expand to fill (or nearly fill) the
> number of slots available.  The IESG has concluded that it is ok
> to have three meeting slots on Fridays.  If we eliminate a
> plenary to open up one or two more slots and use those slots to
> stop using the Friday afternoon ones, I suggest that it will be
> only a matter of time before we have enough demand for slots
> that we expand back into the Friday afternoon times, retaining
> the slots that eliminate the plenary.
>=20
> If we really want to eliminate the Friday afternoon slots, then
> we should eliminate those slots, ratcheting up the criteria for
> getting meeting time to the point that we don't need them.
> Whether or not we need two plenaries (or one or zero or three)
> is almost independent of thet, even though we could get some
> short-term relief.  Given the amount of burnout I often see by
> Friday, simply dropping the afternoon sessions is my personal
> favored solution.
>=20
> If we want to keep the Friday afternoon slots, or keep the
> number of slots that Friday afternoon gives us, then compressing
> the day make sense to me.  Doing that compression according to
> the suggestion has disadvantages --both those you cite and
> others.  But maybe modifying the proposal to include a short
> beverage and cookie break around 11:30 would make sense.  Maybe
> there are other ideas too.  But I think the trends are very
> clear and that, in the long run, eliminating a plenary would
> "buy" an extra slot or two (and another very long and exhausting
> day) but would not improve the Friday situation.
>=20
>     john
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From adrian@olddog.co.uk  Tue Aug  2 04:48:18 2011
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D1421F8D85 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 04:48:18 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SovFEqtrJ1HA for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 04:48:17 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD8A21F8D84 for <ietf@ietf.org>; Tue,  2 Aug 2011 04:48:17 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id p72BhZio001392;  Tue, 2 Aug 2011 12:43:35 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id p72BhWd4001358 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 2 Aug 2011 12:43:33 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Eric Burger'" <eburger-l@standardstrack.com>, "'IETF-Discussion list'" <ietf@ietf.org>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>	<E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>	<88B2C4FA7EDF445D5E9292B0@PST.JCK.COM> <85F40D8B-0BBF-4F87-BD00-6A44FAA9EBD9@standardstrack.com>
In-Reply-To: <85F40D8B-0BBF-4F87-BD00-6A44FAA9EBD9@standardstrack.com>
Subject: RE: A modest proposal for Friday meeting schedule
Date: Tue, 2 Aug 2011 12:48:17 +0100
Message-ID: <03d501cc510a$14ff9a00$3efece00$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHOVos3KyRIJgFJt8silL1mpq2phAHk951aAVSoLmUCBh2cHpTbZoKg
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 11:48:18 -0000

> BTW, has anyone noticed the trend of doing more and more on the Sunday and
> Saturday *before* IETF week?

Very much so. 
Workshops, joint meetings, design teams...
In Prague, a good number of people started in Friday.

Nothing wrong with that, but it does put paid to the idea that the IETF is 4.5
day meeting, and that squeezing it at one end will restrain it. Toothpaste-like,
squeezing the closing Friday will only cause more spillage on the opening
Sunday.

OTOH, I have good reason to think that the application of more focus by WGs
during their meetings *could* reduce the pressure on the whole schedule. Thus,
the perennial thread on not presenting drafts at WG meetings would surely bear
fruit.

Adrian



From tnadeau@lucidvision.com  Tue Aug  2 05:05:30 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA5621F8EB6 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 05:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9iT5X778mTr for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 05:05:29 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 8365621F8EB1 for <ietf@ietf.org>; Tue,  2 Aug 2011 05:05:29 -0700 (PDT)
Received: from [192.168.1.133] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 5248B1D48F94; Tue,  2 Aug 2011 08:05:38 -0400 (EDT)
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <03d501cc510a$14ff9a00$3efece00$@olddog.co.uk>
Date: Tue, 2 Aug 2011 08:05:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <02B53035-51FA-453A-BA7D-EF518FB9F436@lucidvision.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>	<E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>	<88B2C4FA7EDF445D5E9292B0@PST.JCK.COM> <85F40D8B-0BBF-4F87-BD00-6A44FAA9EBD9@standardstrack.com> <03d501cc510a$14ff9a00$3efece00$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1244.3)
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 12:05:30 -0000

On Aug 2, 2011, at 7:48 AM, Adrian Farrel wrote:

>> BTW, has anyone noticed the trend of doing more and more on the =
Sunday and
>> Saturday *before* IETF week?
>=20
> Very much so.=20
> Workshops, joint meetings, design teams...
> In Prague, a good number of people started in Friday.
>=20
> Nothing wrong with that, but it does put paid to the idea that the =
IETF is 4.5
> day meeting, and that squeezing it at one end will restrain it. =
Toothpaste-like,
> squeezing the closing Friday will only cause more spillage on the =
opening
> Sunday.
>=20
> OTOH, I have good reason to think that the application of more focus =
by WGs
> during their meetings *could* reduce the pressure on the whole =
schedule. Thus,
> the perennial thread on not presenting drafts at WG meetings would =
surely bear
> fruit.

	Indeed. A few people were discussing this during one of the =
meetings last week where the agenda was packed to the gills, and the WG =
chairs were cutting off discussion after just 1 or 2 people at the mic.  =
We were all wondering why we spent any time allowing for the =
presentation and instead should have allowed the full 5/10 minute slot =
for discussions/debate.  Even better, what if we spent a whole 15 =
minutes discussing or debating?!

	--Tom



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


From scott.brim@gmail.com  Tue Aug  2 05:33:53 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9AEE21F8C0C for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 05:33:53 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rs1hGplbGbF for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 05:33:53 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 10F4521F8C0B for <ietf@ietf.org>; Tue,  2 Aug 2011 05:33:53 -0700 (PDT)
Received: by iye7 with SMTP id 7so9581987iye.31 for <ietf@ietf.org>; Tue, 02 Aug 2011 05:34:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=U+ZSZ2FYOnDP0JPh3nFxPJpF0okxCl6/KVcV0VOpYkQ=; b=YA5FuQOZJsXlFaQxHSpXPwuF1JkHQNcg0GLsbhGuW0xSqGB6PoJvKnfq9UW8jPLBz3 cWN7RJuh4nciJXZyFPtcut4yf2SFfIWX6c26r4Pawm0FNmGqTlmZ+Hf1UqkaBaFtBgKh J832G0z04ugQbmsDib/ivm/Ud4+1Xr9H7MTiY=
Received: by 10.42.176.67 with SMTP id bd3mr1352066icb.488.1312288441920; Tue, 02 Aug 2011 05:34:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.10.140 with HTTP; Tue, 2 Aug 2011 05:33:41 -0700 (PDT)
In-Reply-To: <02B53035-51FA-453A-BA7D-EF518FB9F436@lucidvision.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <88B2C4FA7EDF445D5E9292B0@PST.JCK.COM> <85F40D8B-0BBF-4F87-BD00-6A44FAA9EBD9@standardstrack.com> <03d501cc510a$14ff9a00$3efece00$@olddog.co.uk> <02B53035-51FA-453A-BA7D-EF518FB9F436@lucidvision.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 2 Aug 2011 08:33:41 -0400
Message-ID: <CAPv4CP83R7QwOADu4xY0U7Jc7vQ0Ni+6JCWA_+cjWkireaw11Q@mail.gmail.com>
Subject: Re: A modest proposal for Friday meeting schedule
To: Thomas Nadeau <tnadeau@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: adrian@olddog.co.uk, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 12:33:53 -0000

On Tue, Aug 2, 2011 at 08:05, Thomas Nadeau <tnadeau@lucidvision.com> wrote=
:
>> OTOH, I have good reason to think that the application of more focus by =
WGs
>> during their meetings *could* reduce the pressure on the whole schedule.=
 Thus,
>> the perennial thread on not presenting drafts at WG meetings would surel=
y bear
>> fruit.
>
> =A0 =A0 =A0 =A0Indeed. A few people were discussing this during one of th=
e meetings last week where the agenda was packed to the gills, and the WG c=
hairs were cutting off discussion after just 1 or 2 people at the mic. =A0W=
e were all wondering why we spent any time allowing for the presentation an=
d instead should have allowed the full 5/10 minute slot for discussions/deb=
ate. =A0Even better, what if we spent a whole 15 minutes discussing or deba=
ting?!

See http://trac.tools.ietf.org/wg/intarea/trac/wiki/MeetingTimePrioritizati=
on
for what we came up with.

From vesely@tana.it  Tue Aug  2 06:27:50 2011
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0C9621F881C for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 06:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level: 
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[AWL=0.018,  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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lwjp4Ruv672j for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 06:27:50 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id A417A21F861A for <ietf@ietf.org>; Tue,  2 Aug 2011 06:27:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1312291678; bh=hG6eGCmLf/eQTVhm9Hkvs3HpVC8ehueBNavCEAs36rM=; l=1113; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=im9mTL6u+00BZXpovHrwnoViMe6/iqWvdXKC2mMsPa7IJbc/jXj1tv0+vKD2NmaWM mch721L4Ha57F/q680pfNr/y3NGUI1764qqNUj7RLLWo71H1fAkhfB7pCSr3dcdnLa sXiDfZnDBNGROGIJTCw1QqhJWWhmS31yqXMx8m3o=
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, 02 Aug 2011 15:27:58 +0200 id 00000000005DC03F.000000004E37FB5E.000030D1
Message-ID: <4E37FB5D.4070309@tana.it>
Date: Tue, 02 Aug 2011 15:27:57 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com>	<4E352A74.6080703@isdg.net>	<773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>	<201108011141.30549.scott@kitterman.com>	<F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com>	<4C4ACC39-F9CC-429B-B6E6-CE0202C2C1BE@network-heretics.com> <4E378273.1050407@isdg.net>
In-Reply-To: <4E378273.1050407@isdg.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 13:27:50 -0000

On 02/Aug/11 06:52, Hector Santos wrote:
> Keith Moore wrote:
> 
>> Repeat as needed; you can always partition the remaining part of
>> the problem again.
> 
> It was not a difficult problem.  [...] how to scale the
> authorization of 3rd party signer. [...] But there was a
> fundamental mindset and marketing conflict.  It was a conflict of
> 3rd party resigner market right to exist uncontrolled, unrestricted
> regardless of originating DKIM message claims.

Marketing pressure on IETF protocols may be business as usual, but
DKIM managed to come out pretty cleanly neutral in this respect,
AFAICS[*].

IMHO, a scenario with a few big re-signers would pose more problems
than it can ever solve.  I wish they... resign.  However, managing
reputation without having recourse to a big brother of some sort is no
easy problem.  Since even governments are being blamed for pursuing
personal interests rather than people's needs, solving that will be a
major achievement in democracy.

-- 
[*] Let's draw a veil over that somewhat confused patent disclosure
https://datatracker.ietf.org/ipr/1547/

From wjhns1@hardakers.net  Tue Aug  2 07:02:20 2011
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 910D421F87AF for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 07:02:20 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z98Y7bmZOSV7 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 07:02:20 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id C26BC21F8784 for <ietf@ietf.org>; Tue,  2 Aug 2011 07:02:19 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 515B65BF; Tue,  2 Aug 2011 07:01:57 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Drafts Submissions cut-off
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <C22E1819-CB43-4E39-8F78-070BCFA3A474@vpnc.org>
Date: Tue, 02 Aug 2011 07:01:57 -0700
In-Reply-To: <C22E1819-CB43-4E39-8F78-070BCFA3A474@vpnc.org> (Paul Hoffman's message of "Mon, 1 Aug 2011 16:27:55 -0700")
Message-ID: <sd8vrbx67e.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 14:02:20 -0000

>>>>> On Mon, 1 Aug 2011 16:27:55 -0700, Paul Hoffman <paul.hoffman@vpnc.org> said:

PH> Or, (3), specify somewhere that the submission window opens at the
PH> beginning of the meeting and allow WG chairs to decide what they
PH> want to do about new drafts. In the case last week, the draft was
PH> turned in and posted to the mailing list on Monday ahead of the
PH> meeting on Friday; the chairs seemed to like that.

It all comes down to "how to best get information to those that need
it (as fast as possible)".  I too, read the older version of the draft
that being discussed and didn't realize there was a new one because I
rarely get to *all* of my mail during IETF weeks (I'm too busy talking
in the hallways to read email).  That being said, I think forward
progress on drafts are most likely to happen *during* IETF meetings in
hallways and thus it's impossible to enter a WG meeting and assume that
no thinking has changed in the 3 weeks since the last draft was
published.

IE, this has nothing to do with the drafts themselves.  It has to do
with communication of changebars.  In the case where significant changes
have taken place in thinking (documented or not) because of
conversations or work that has commenced since the cut-off date, it
should be the responsibility of the authors to give a quick summary
early in the meeting about recent progress, as it's indeed unfair to
assume everyone in the audience hasn't printed and read everything only
an hour before the meeting and were present in every conversation that
occurred over the cookie table (regardless of whether there were
actually cookies or just crumbs there).  It should also be up to the
chairs to bug the authors about making sure that any recent changes are,
in fact, at least listed or presented in detail depending on what's best
for the meeting.

You can't hold a discussion half the participants have only half the
information.  It doesn't matter who's fault it was.  It only matters
that it's a problem.

-- 
Wes Hardaker
SPARTA, Inc.

From msk@cloudmark.com  Tue Aug  2 10:10:35 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 886AB21F86E0 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 10:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.679
X-Spam-Level: 
X-Spam-Status: No, score=-103.679 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdhoP5LbBP97 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 10:10:35 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 1104F21F8726 for <ietf@ietf.org>; Tue,  2 Aug 2011 10:10:35 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Tue, 2 Aug 2011 10:10:44 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 2 Aug 2011 10:10:43 -0700
Subject: RE: DKIM Signatures now being applied to IETF Email
Thread-Topic: DKIM Signatures now being applied to IETF Email
Thread-Index: AcxRGB5DStQ4SdlrSECXRjf4JKc55wAHmMPA
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF4EE@EXCH-C2.corp.cloudmark.com>
References: <20110725171748.GA13506@amsl.com>	<4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com> <201108011141.30549.scott@kitterman.com> <F5833273385BB34F99288B3648C4F06F13512DF4D8@EXCH-C2.corp.cloudmark.com> <4C4ACC39-F9CC-429B-B6E6-CE0202C2C1BE@network-heretics.com> <4E378273.1050407@isdg.net> <4E37FB5D.4070309@tana.it>
In-Reply-To: <4E37FB5D.4070309@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 17:10:35 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of A=
lessandro Vesely
> Sent: Tuesday, August 02, 2011 6:28 AM
> To: ietf@ietf.org
> Subject: Re: DKIM Signatures now being applied to IETF Email
>=20
> > It was not a difficult problem.  [...] how to scale the
> > authorization of 3rd party signer. [...] But there was a
> > fundamental mindset and marketing conflict.  It was a conflict of
> > 3rd party resigner market right to exist uncontrolled, unrestricted
> > regardless of originating DKIM message claims.
>=20
> Marketing pressure on IETF protocols may be business as usual, but
> DKIM managed to come out pretty cleanly neutral in this respect,
> AFAICS[*].

I think the claim that marketing somehow entered into the guidance of DKIM'=
s evolution is specious, and that's being polite.  I've yet to see any evid=
ence at all, short of unfounded assertions about the unspoken agendas of th=
e participants, to back it up.


From john@jck.com  Mon Aug  1 14:51:00 2011
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42DB41F0C4B for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.678
X-Spam-Level: 
X-Spam-Status: No, score=-102.678 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqQsFm0ThT1d for <ietf@ietfa.amsl.com>; Mon,  1 Aug 2011 14:50:59 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 920931F0C49 for <ietf@ietf.org>; Mon,  1 Aug 2011 14:50:59 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qo0Nj-000JQU-Pm; Mon, 01 Aug 2011 17:50:39 -0400
Date: Mon, 01 Aug 2011 17:50:38 -0400
From: John C Klensin <john@jck.com>
To: Adam Roach <adam@nostrum.com>, Russ Housley <housley@vigilsec.com>
Subject: Re: A modest proposal for Friday meeting schedule
Message-ID: <535D447870130147BCE840BA@PST.JCK.COM>
In-Reply-To: <4E371CD0.9010501@nostrum.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi> <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com> <4E371CD0.9010501@nostrum.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: Tue, 02 Aug 2011 10:28:10 -0700
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2011 21:51:00 -0000

--On Monday, August 01, 2011 16:38 -0500 Adam Roach
<adam@nostrum.com> wrote:

> I'd like to join the sparse voices in speaking out against
> this plan. By Friday, I'm pretty well on a local meal
> schedule. Pushing lunch back by 2 hours would pretty well on
> guarantee that I'd be sugar-crashed and less coherent than
> normal by the end of Session II.

Adam,

I've noticed that lots of people (myself often included) are
often sufficiently wasted by Friday morning to be largely
disfunctional (certainly "less coherent than normal").   I'm
prepared to believe that pushing back lunch would make it even
worse for some people, but it may be that the best solution to
that problem is a better breakfast or snacks that can be brought
into the meeting rooms (or eaten during a _very_ short break as
distinct from 90 minutes of lunch break).

With at least some facilities, getting finished earlier would
also reduce costs; I assume I'm not the only one who would like
to see that go straight to the registration fees.

So I think this is a good idea if it is feasible... even though
my preference would be to go back to ending at noon (or 11:30 or
earlier) on Friday by getting more efficient about how we use
time earlier in the week and more selective about who and what
gets time at all.

 best,
   john




From lars.eggert@nokia.com  Tue Aug  2 06:27:20 2011
Return-Path: <lars.eggert@nokia.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2922421F8906 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 06:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.658
X-Spam-Level: 
X-Spam-Status: No, score=-103.658 tagged_above=-999 required=5 tests=[AWL=0.830, BAYES_00=-2.599, GB_I_INVITATION=-2, SARE_NETPROD=0.111, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XETVmX9c6B2K for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 06:27:19 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 26B7121F881C for <ietf@ietf.org>; Tue,  2 Aug 2011 06:27:19 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p72DRQQ4004641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 2 Aug 2011 16:27:27 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97.2 at fit.nokia.com
Content-Type: multipart/signed; boundary="Apple-Mail=_4A77544F-47A3-44F2-B851-62CCD255F552"; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Call for Nominations: Applied Networking Research Prize (ANRP) for IETF-82
Date: Tue, 2 Aug 2011 16:27:23 +0300
Message-Id: <FF36C9A0-9178-45E5-B9A1-D450DB68CC8D@nokia.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.fit.nokia.com); Tue, 02 Aug 2011 16:27:23 +0300 (EEST)
X-Nokia-AV: Clean
X-Mailman-Approved-At: Tue, 02 Aug 2011 10:28:32 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: anrp@isoc.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 13:27:20 -0000

--Apple-Mail=_4A77544F-47A3-44F2-B851-62CCD255F552
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252



               CALL FOR NOMINATIONS:

      APPLIED NETWORKING RESEARCH PRIZE (ANRP)
     =20
               http://irtf.org/anrp


*** Submit nominations until August 28 for the ANRP for IETF-82,
*** November 13-18, 2011 in Taipei, Taiwan:
*** http://fit.nokia.com/anrp/82/

The Applied Networking Research Prize (ANRP) is awarded for
recent results in applied networking research that are relevant
for transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recently
published results are encouraged to apply for this prize, which
will offer them the opportunity to present and discuss their work
with the engineers, network operators, policy makers and
scientists that participate in the Internet Engineering Task
Force (IETF) and its research arm, the Internet Research Task
Force (IRTF). Third-party nominations for this prize are also
encouraged. The goal of the Applied Networking Research Prize
(ANRP) is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they
would not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

* cash prize of $500 (USD)

* invited talk at the IRTF Open Meeting

* travel grant to attend the week-long IETF meeting
  (airfare, hotel, registration, stipend)

* recognition at the IETF plenary

* invitation to related social activities

* potential for additional travel grants to future IETF
  meetings, based on community feedback


HOW TO APPLY

Only a single person can be nominated based on a peer-reviewed,
recently-published, original journal, conference or workshop paper
they authored. The nominee must be one of the main authors of the
nominated paper. Both self nominations (nominating one=92s own paper)
and third-party nominations (nominating someone else=92s paper) are
encouraged.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF experimentation,
analyze the behavior of Internet protocols in operational
deployments or realistic testbeds, make an important contribution
to the understanding of Internet scalability, performance,
reliability, security or capability, or otherwise be of relevance
to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates
to these goals, and are encouraged to describe how presentation
of these research results will foster their transition into new
IETF engineering or IRTF experimentation, or otherwise seed new
activities that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to
foster the transitioning of research results into real-world
benefits for the Internet. Therefore, applicants must indicate
that they (or the nominee, in case of third-party nominations)
are available to attend the respective IETF meeting in person and
in its entirety.

Nominations must include:

* the name and email address of the nominee

* a reference to the published nominated paper

* a PDF copy of the nominated paper

* a statement that describes how the nominated paper
  fulfills the goals of the award

* a statement that the nominee is available to attend the
  respective IETF meeting in person and in its entirety

* a brief biography or CV of the nominee

* optionally, any other supporting information (link to
  nominee's web site, etc.)

*** Nominations are submitted via the submission site:
*** http://fit.nokia.com/anrp/82/


SELECTION PROCESS

A small selection committee comprised of individuals
knowledgeable about the IRTF, IETF and the broader networking
research community will evaluate the submissions against these
selection criteria. The goal is to select 1-2 submissions for the
Applied Networking Research Prize (ANRP) during each nomination
period. All nominees will be notified by email.


IMPORTANT DATES

Applications open:  August 1, 2011
Applications close: August 28, 2011
Notifications:      September 20, 2011
IETF-82 Meeting:    November 13-18, 2011 in Taipei, Taiwan=20


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).=

--Apple-Mail=_4A77544F-47A3-44F2-B851-62CCD255F552
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDgwMjEzMjcyNFowIwYJKoZIhvcNAQkE
MRYEFLG+NfUytUvQjRBiP9XmDWgPc50jMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AKYS9w1XuPwWoMtVO5IVWVEpOi5SCmAGcbndRAH3PqzLAquZ4oxDpCzG3keVnYN6dq02CCa1d5GH
qTvMUgHOF/l1oi9zqlPl87DtTg9IM05jSP4dLlKrcxRhyPXWm/I/xZlVzZBudEWzuXsMVUpqpbTv
dYT1Pr7MthnBBFtXSJ25Z27dcflKxXVanid3vAZNTY8ofgb1jmyaERuohIERVojmCvJJykpNlrml
wONqoJVFlAKhEPPvZPejRuiz12g3DaRnZm5RKh065AcLbbHfNSx4yDdaNh1FpT/3yptst5jcOoBz
pNb5H5BCavYSZ+O5otq4lu5TpBU5ALfOz1alniUAAAAAAAA=

--Apple-Mail=_4A77544F-47A3-44F2-B851-62CCD255F552--

From stpeter@stpeter.im  Tue Aug  2 10:36:49 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6371711E8080 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 10:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.701
X-Spam-Level: 
X-Spam-Status: No, score=-102.701 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GnktsbJ8ielG for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 10:36:49 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 0573111E807F for <ietf@ietf.org>; Tue,  2 Aug 2011 10:36:49 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9F3E441309; Tue,  2 Aug 2011 11:38:16 -0600 (MDT)
Message-ID: <4E3835B9.60503@stpeter.im>
Date: Tue, 02 Aug 2011 11:36:57 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: John C Klensin <john@jck.com>
Subject: Re: A modest proposal for Friday meeting schedule
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi> <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com> <4E371CD0.9010501@nostrum.com> <535D447870130147BCE840BA@PST.JCK.COM>
In-Reply-To: <535D447870130147BCE840BA@PST.JCK.COM>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 17:36:49 -0000

On 8/1/11 3:50 PM, John C Klensin wrote:

> So I think this is a good idea if it is feasible... even though
> my preference would be to go back to ending at noon (or 11:30 or
> earlier) on Friday by getting more efficient about how we use
> time earlier in the week and more selective about who and what
> gets time at all.

+1 to that. Work will expand to fill the time allotted.

A side benefit is that the IESG/IAB could have a lunch meeting on Friday
(as opposed to the current breakfast meeting) and cover all the hot
topics from the week (not the week minus Friday).

/psa

From mnot@mnot.net  Tue Aug  2 10:45:48 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEE7311E80AA for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 10:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.292
X-Spam-Level: 
X-Spam-Status: No, score=-104.292 tagged_above=-999 required=5 tests=[AWL=-1.693, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Dwf8uEIfy5N for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 10:45:48 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 241FC11E8098 for <ietf@ietf.org>; Tue,  2 Aug 2011 10:45:48 -0700 (PDT)
Received: from [10.10.1.118] (unknown [67.111.52.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B597B22E253; Tue,  2 Aug 2011 13:45:55 -0400 (EDT)
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <535D447870130147BCE840BA@PST.JCK.COM>
Date: Tue, 2 Aug 2011 10:45:52 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <075B1870-7D4C-4766-9D7F-279182275FBE@mnot.net>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com> <60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com> <20110801133935.GC89723@verdi> <2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com> <4E371CD0.9010501@nostrum.com> <535D447870130147BCE840BA@PST.JCK.COM>
To: John C Klensin <john@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 17:45:48 -0000

On 01/08/2011, at 2:50 PM, John C Klensin wrote:
> 
> I've noticed that lots of people (myself often included) are
> often sufficiently wasted by Friday morning to be largely
> disfunctional (certainly "less coherent than normal").   I'm
> prepared to believe that pushing back lunch would make it even
> worse for some people, but it may be that the best solution to
> that problem is a better breakfast or snacks that can be brought
> into the meeting rooms (or eaten during a _very_ short break as
> distinct from 90 minutes of lunch break).

This is better. Some people will still doubtless complain.

> 
> With at least some facilities, getting finished earlier would
> also reduce costs; I assume I'm not the only one who would like
> to see that go straight to the registration fees.

+1

> So I think this is a good idea if it is feasible... even though
> my preference would be to go back to ending at noon (or 11:30 or
> earlier) on Friday by getting more efficient about how we use
> time earlier in the week and more selective about who and what
> gets time at all.

+1


--
Mark Nottingham   http://www.mnot.net/




From spencer@wonderhamster.org  Tue Aug  2 11:10:49 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 920A221F859C for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 11:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.701
X-Spam-Level: 
X-Spam-Status: No, score=-101.701 tagged_above=-999 required=5 tests=[AWL=0.896, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJT5eqLvtTtU for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 11:10:49 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id EF90621F8574 for <ietf@ietf.org>; Tue,  2 Aug 2011 11:10:48 -0700 (PDT)
Received: from S73602b ([206.47.36.50]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0M6icu-1Rbzfl2REK-00xMKE; Tue, 02 Aug 2011 14:10:57 -0400
Message-ID: <FBFC03EF62E7437BB9051CB99EA1FED4@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Peter Saint-Andre" <stpeter@stpeter.im>, "John C Klensin" <john@jck.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com><B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com><60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com><20110801133935.GC89723@verdi><2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com><4E371CD0.9010501@nostrum.com><535D447870130147BCE840BA@PST.JCK.COM> <4E3835B9.60503@stpeter.im>
Subject: Re: A modest proposal for Friday meeting schedule
Date: Tue, 2 Aug 2011 13:10:52 -0500
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.6109
X-Provags-ID: V02:K0:C7Wyg5BqrHLdsVRyxAG1c9pCnxkBjQrc68g0RyIYj7T XTWSdYXHVHdlitmD3yh7hq+o4N2CbE6lLq5RVkk3Yz//c4lHuc kO+6fRR1yTqXHXzXK84XQ99myUq3NKwjcMzCcZ4oOeVISHChrk IhPd9EebHkApL1zZxaYa91aUv5gyW4ClLVCOMvZmObWe9RVSvd YXE5gHb9ot+SHT2q25zWfC/aBnY6hsYXCB4P7hA29c=
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 18:10:49 -0000

Peter,

> A side benefit is that the IESG/IAB could have a lunch meeting on Friday
> (as opposed to the current breakfast meeting) and cover all the hot
> topics from the week (not the week minus Friday).
>
> /psa

I agree with your point here, and add that the joint IAB/IESG Friday session 
isn't only a BOF report session, it's "hot spots, however defined" - we've 
usually at least SEEN all the BOFs by Friday breakfast, but that doesn't 
mean we've seen all the hot spots ;-)

Spencer 


From sm@resistor.net  Tue Aug  2 11:28:48 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 319A511E80B8 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 11:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.094
X-Spam-Level: 
X-Spam-Status: No, score=-102.094 tagged_above=-999 required=5 tests=[AWL=-0.487, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kt18oJs4+7Lu for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 11:28:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A318D21F8669 for <ietf@ietf.org>; Tue,  2 Aug 2011 11:28:45 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p72ISf22001076;  Tue, 2 Aug 2011 11:28:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1312309726; bh=vFf0IAm2mLeFGmWzJ8BoVfdYxIpgXXueje1P+rXs9QY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=aGGKXSuaS0MddBBAOQ2TGNreAv1DsxB8Nyv6Sw3GK/ckRkZDbLkiB1SllysDKYEWW /n42PkIUh5L87rJkwbyYjkVK8hkiovfcA7cWAct9Ef5/Bk9FIoOxUaltM3GkfpCzfn yTytIC1YERKdV2FE3Te6eFwy/T9zJYCwGFG0VGHU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1312309726; bh=vFf0IAm2mLeFGmWzJ8BoVfdYxIpgXXueje1P+rXs9QY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=FpL6KB7teS/AacgQEZi8SgyzhxRvxPF5ZtyXcfCh8SaU556K4oE263s6hCodSbrPo Mi8X1y6iPuo6roP8RgIn+CaE6Vi3uMdK4kj7J3dBw0mupd80YsF7rJYD3Qk3bNtDQo 0jUmPk7ECTEvRnOSFt/NcYwnSVrHiuWtHeT/ZsxM=
Message-Id: <6.2.5.6.2.20110801172353.0696f868@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 01 Aug 2011 17:46:49 -0700
To: Phillip Hallam-Baker <hallam@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Drafts Submissions cut-off
In-Reply-To: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.g mail.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 18:28:48 -0000

Hi Phillip,
At 11:31 AM 8/1/2011, Phillip Hallam-Baker wrote:
>Over the weekend I attempted to determine the rules for discussion 
>of drafts at IETF meetings and was surprised to discover that they 
>are not actually written down anywhere (other than on the meetings 
>page). As a result we appear to have an anomalous situation in which 
>an author who misses the cut-off date for ID submissions is in fact 
>entitled to sit on the draft for two weeks and then submit when the 
>ID queue re-opens.
>
>I suggest that this is a sub-optimal state of affairs. I see two solutions:
>
>1) Codify the requirement that materials to be discussed at the 
>meeting must be submitted before the cut-off and that submissions 
>made during meetings are strictly limited to revisions occurring 
>after and between WG sessions. [Except in exceptional circumstances 
>with AD approval]
>
>2) Eliminate the 2 week cut off completely.

I'll start by quoting Scott Brim [1]:

   "One generation's rule of thumb becomes the next generation's dogma.
    The IETF should sit up and really think when someone suggests that
    a process has become dogma."

Quoting Ned [2]:

   "I'd much rather breach the sanctity of the rules by getting rid of
    some of them entirely."

Quoting Russ [3]:

   "When all of the Internet-Drafts were processed by Secretariat staff,
    there was a huge workload concern.  Now that the Internet-Draft
    Submission Tool (IDST) is taking the bulk of the load, there are
    resources to deal with these exceptions, as was just demonstrated."

Which was in response to John Klensin who said [4]:

   "The original reason for those cutoffs -- even more important
    than giving people time to read drafts -- was that the
    submissions were overwhelming the Secretariat.  Not only did
    they have other things to do in the weeks before the meeting, it
    was becoming unpredictable whether a draft submitted in advance
    of the meeting would be posted early enough for the relevant WG
    to look at it.  The split between "new" and "revised" drafts was
    another attempt to protect the Secretariat -- notions of having
    to formally approve WG drafts came later."

And Dave said [5]:

   "It would seem that the right thing is to remove the cutoff and let
     each working group decide on what drafts will be worked on."

Spencer Dawkins [6] quoted Section 7.1 of RFC 2418.

Pete Resnick was of the opinion [7] that:

   "The cutoff is an arbitrary procedure to try (poorly IMO) to enforce
    the 2418 rule."

I suggest that WG chairs stop asking the working group whether they 
have read the draft as it is silly.  It is an impossible task to keep 
up with the flood of I-D that are submitted on Meeting Monday.

Regards,
-sm

1. msg-id: 48821469.4050907@employees.org
2. msg-id: 01MXC0962CLI00007A@mauve.mrochek.com
3. msg-id: 20080719191556.567F03A6A32@core3.amsl.com
4. msg-id: 2E1B2AB9703690B8E1EEBE90@p3.JCK.COM
5. msg-id: 48826DC0.8000307@dcrocker.net
6. msg-id: 013501c8ea6a$271e28a0$6501a8c0@china.huawei.com
7. msg-id: p06250100c4a9226eac87@[75.145.176.242] 


From maurice@tehcorner.com  Tue Aug  2 12:10:32 2011
Return-Path: <maurice@tehcorner.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3558221F8511 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 12:10:32 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJFQDBWkj7WX for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 12:10:31 -0700 (PDT)
Received: from mail.tehcorner.info (mail.tehcorner.info [76.74.171.246]) by ietfa.amsl.com (Postfix) with ESMTP id 67B2F21F850C for <ietf@ietf.org>; Tue,  2 Aug 2011 12:10:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.tehcorner.info (Postfix) with ESMTP id C16C7E082D4 for <ietf@ietf.org>; Tue,  2 Aug 2011 12:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mail.tehcorner.info
Received: from mail.tehcorner.info ([127.0.0.1]) by localhost (mail.tehcorner.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6wxKUn5opT1 for <ietf@ietf.org>; Tue,  2 Aug 2011 12:37:31 -0700 (PDT)
Received: from localhost (me10436d0.tmodns.net [208.54.4.225]) by mail.tehcorner.info (Postfix) with ESMTPSA id E3F4CE080A6 for <ietf@ietf.org>; Tue,  2 Aug 2011 12:37:30 -0700 (PDT)
Date: Tue, 02 Aug 2011 12:10:21 -0700
Subject: Re: Ietf Digest, Vol 39, Issue 13
Message-ID: <js51sa1qpv9np3epc6oii11t.1312312214604@email.android.com>
From: Maurice Zenarosa <maurice@tehcorner.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 19:10:32 -0000

CgpNYXVyaWNlIFplbmFyb3NhClRlY2hub2xvZ3kgRGVwYXJ0bWVudApMeW53b29kIFVuaWZpZWQg
U2Nob29sIERpc3RyaWN0CgoKaWV0Zi1yZXF1ZXN0QGlldGYub3JnIHdyb3RlOgoKPklmIHlvdSBo
YXZlIHJlY2VpdmVkIHRoaXMgZGlnZXN0IHdpdGhvdXQgYWxsIHRoZSBpbmRpdmlkdWFsIG1lc3Nh
Z2UKPmF0dGFjaG1lbnRzIHlvdSB3aWxsIG5lZWQgdG8gdXBkYXRlIHlvdXIgZGlnZXN0IG9wdGlv
bnMgaW4geW91ciBsaXN0Cj5zdWJzY3JpcHRpb24uICBUbyBkbyBzbywgZ28gdG8gCj4KPmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zgo+Cj5DbGljayB0aGUgJ1Vuc3Vi
c2NyaWJlIG9yIGVkaXQgb3B0aW9ucycgYnV0dG9uLCBsb2cgaW4sIGFuZCBzZXQgIkdldAo+TUlN
RSBvciBQbGFpbiBUZXh0IERpZ2VzdHM/IiB0byBNSU1FLiAgWW91IGNhbiBzZXQgdGhpcyBvcHRp
b24KPmdsb2JhbGx5IGZvciBhbGwgdGhlIGxpc3QgZGlnZXN0cyB5b3UgcmVjZWl2ZSBhdCB0aGlz
IHBvaW50Lgo+Cj4KPgo+U2VuZCBJZXRmIG1haWxpbmcgbGlzdCBzdWJtaXNzaW9ucyB0bwo+CWll
dGZAaWV0Zi5vcmcKPgo+VG8gc3Vic2NyaWJlIG9yIHVuc3Vic2NyaWJlIHZpYSB0aGUgV29ybGQg
V2lkZSBXZWIsIHZpc2l0Cj4JaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9p
ZXRmCj5vciwgdmlhIGVtYWlsLCBzZW5kIGEgbWVzc2FnZSB3aXRoIHN1YmplY3Qgb3IgYm9keSAn
aGVscCcgdG8KPglpZXRmLXJlcXVlc3RAaWV0Zi5vcmcKPgo+WW91IGNhbiByZWFjaCB0aGUgcGVy
c29uIG1hbmFnaW5nIHRoZSBsaXN0IGF0Cj4JaWV0Zi1vd25lckBpZXRmLm9yZwo+Cj5XaGVuIHJl
cGx5aW5nLCBwbGVhc2UgZWRpdCB5b3VyIFN1YmplY3QgbGluZSBzbyBpdCBpcyBtb3JlIHNwZWNp
ZmljCj50aGFuICJSZTogQ29udGVudHMgb2YgSWV0ZiBkaWdlc3QuLi4iCj4KPgo+VG9kYXkncyBU
b3BpY3M6Cj4KPiAgIDEuIFJlOiBBIG1vZGVzdCBwcm9wb3NhbCBmb3IgRnJpZGF5IG1lZXRpbmcg
c2NoZWR1bGUKPiAgICAgIChTcGVuY2VyIERhd2tpbnMpCj4gICAyLiBSZTogRHJhZnRzIFN1Ym1p
c3Npb25zIGN1dC1vZmYgKFNNKQo+Cj4KPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPgo+TWVzc2FnZTogMQo+RGF0
ZTogVHVlLCAyIEF1ZyAyMDExIDEzOjEwOjUyIC0wNTAwCj5Gcm9tOiAiU3BlbmNlciBEYXdraW5z
IiA8c3BlbmNlckB3b25kZXJoYW1zdGVyLm9yZz4KPlRvOiAiUGV0ZXIgU2FpbnQtQW5kcmUiIDxz
dHBldGVyQHN0cGV0ZXIuaW0+LCAiSm9obiBDIEtsZW5zaW4iCj4JPGpvaG5AamNrLmNvbT4KPkNj
OiBJRVRGIDxpZXRmQGlldGYub3JnPgo+U3ViamVjdDogUmU6IEEgbW9kZXN0IHByb3Bvc2FsIGZv
ciBGcmlkYXkgbWVldGluZyBzY2hlZHVsZQo+TWVzc2FnZS1JRDogPEZCRkMwM0VGNjJFNzQzN0JC
OTA1MUNCOTlFQTFGRUQ0QGNoaW5hLmh1YXdlaS5jb20+Cj5Db250ZW50LVR5cGU6IHRleHQvcGxh
aW47IGZvcm1hdD1mbG93ZWQ7IGNoYXJzZXQ9Imlzby04ODU5LTEiOwo+CXJlcGx5LXR5cGU9b3Jp
Z2luYWwKPgo+UGV0ZXIsCj4KPj4gQSBzaWRlIGJlbmVmaXQgaXMgdGhhdCB0aGUgSUVTRy9JQUIg
Y291bGQgaGF2ZSBhIGx1bmNoIG1lZXRpbmcgb24gRnJpZGF5Cj4+IChhcyBvcHBvc2VkIHRvIHRo
ZSBjdXJyZW50IGJyZWFrZmFzdCBtZWV0aW5nKSBhbmQgY292ZXIgYWxsIHRoZSBob3QKPj4gdG9w
aWNzIGZyb20gdGhlIHdlZWsgKG5vdCB0aGUgd2VlayBtaW51cyBGcmlkYXkpLgo+Pgo+PiAvcHNh
Cj4KPkkgYWdyZWUgd2l0aCB5b3VyIHBvaW50IGhlcmUsIGFuZCBhZGQgdGhhdCB0aGUgam9pbnQg
SUFCL0lFU0cgRnJpZGF5IHNlc3Npb24gCj5pc24ndCBvbmx5IGEgQk9GIHJlcG9ydCBzZXNzaW9u
LCBpdCdzICJob3Qgc3BvdHMsIGhvd2V2ZXIgZGVmaW5lZCIgLSB3ZSd2ZSAKPnVzdWFsbHkgYXQg
bGVhc3QgU0VFTiBhbGwgdGhlIEJPRnMgYnkgRnJpZGF5IGJyZWFrZmFzdCwgYnV0IHRoYXQgZG9l
c24ndCAKPm1lYW4gd2UndmUgc2VlbiBhbGwgdGhlIGhvdCBzcG90cyA7LSkKPgo+U3BlbmNlciAK
Pgo+Cj4KPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+Cj5NZXNzYWdlOiAyCj5EYXRl
OiBNb24sIDAxIEF1ZyAyMDExIDE3OjQ2OjQ5IC0wNzAwCj5Gcm9tOiBTTSA8c21AcmVzaXN0b3Iu
bmV0Pgo+VG86IFBoaWxsaXAgSGFsbGFtLUJha2VyIDxoYWxsYW1AZ21haWwuY29tPgo+Q2M6IElF
VEYgRGlzY3Vzc2lvbiBNYWlsaW5nIExpc3QgPGlldGZAaWV0Zi5vcmc+Cj5TdWJqZWN0OiBSZTog
RHJhZnRzIFN1Ym1pc3Npb25zIGN1dC1vZmYKPk1lc3NhZ2UtSUQ6IDw2LjIuNS42LjIuMjAxMTA4
MDExNzIzNTMuMDY5NmY4NjhAcmVzaXN0b3IubmV0Pgo+Q29udGVudC1UeXBlOiB0ZXh0L3BsYWlu
OyBjaGFyc2V0PSJ1cy1hc2NpaSI7IGZvcm1hdD1mbG93ZWQKPgo+SGkgUGhpbGxpcCwKPkF0IDEx
OjMxIEFNIDgvMS8yMDExLCBQaGlsbGlwIEhhbGxhbS1CYWtlciB3cm90ZToKPj5PdmVyIHRoZSB3
ZWVrZW5kIEkgYXR0ZW1wdGVkIHRvIGRldGVybWluZSB0aGUgcnVsZXMgZm9yIGRpc2N1c3Npb24g
Cj4+b2YgZHJhZnRzIGF0IElFVEYgbWVldGluZ3MgYW5kIHdhcyBzdXJwcmlzZWQgdG8gZGlzY292
ZXIgdGhhdCB0aGV5IAo+PmFyZSBub3QgYWN0dWFsbHkgd3JpdHRlbiBkb3duIGFueXdoZXJlIChv
dGhlciB0aGFuIG9uIHRoZSBtZWV0aW5ncyAKPj5wYWdlKS4gQXMgYSByZXN1bHQgd2UgYXBwZWFy
IHRvIGhhdmUgYW4gYW5vbWFsb3VzIHNpdHVhdGlvbiBpbiB3aGljaCAKPj5hbiBhdXRob3Igd2hv
IG1pc3NlcyB0aGUgY3V0LW9mZiBkYXRlIGZvciBJRCBzdWJtaXNzaW9ucyBpcyBpbiBmYWN0IAo+
PmVudGl0bGVkIHRvIHNpdCBvbiB0aGUgZHJhZnQgZm9yIHR3byB3ZWVrcyBhbmQgdGhlbiBzdWJt
aXQgd2hlbiB0aGUgCj4+SUQgcXVldWUgcmUtb3BlbnMuCj4+Cj4+SSBzdWdnZXN0IHRoYXQgdGhp
cyBpcyBhIHN1Yi1vcHRpbWFsIHN0YXRlIG9mIGFmZmFpcnMuIEkgc2VlIHR3byBzb2x1dGlvbnM6
Cj4+Cj4+MSkgQ29kaWZ5IHRoZSByZXF1aXJlbWVudCB0aGF0IG1hdGVyaWFscyB0byBiZSBkaXNj
dXNzZWQgYXQgdGhlIAo+Pm1lZXRpbmcgbXVzdCBiZSBzdWJtaXR0ZWQgYmVmb3JlIHRoZSBjdXQt
b2ZmIGFuZCB0aGF0IHN1Ym1pc3Npb25zIAo+Pm1hZGUgZHVyaW5nIG1lZXRpbmdzIGFyZSBzdHJp
Y3RseSBsaW1pdGVkIHRvIHJldmlzaW9ucyBvY2N1cnJpbmcgCj4+YWZ0ZXIgYW5kIGJldHdlZW4g
V0cgc2Vzc2lvbnMuIFtFeGNlcHQgaW4gZXhjZXB0aW9uYWwgY2lyY3Vtc3RhbmNlcyAKPj53aXRo
IEFEIGFwcHJvdmFsXQo+Pgo+PjIpIEVsaW1pbmF0ZSB0aGUgMiB3ZWVrIGN1dCBvZmYgY29tcGxl
dGVseS4KPgo+SSdsbCBzdGFydCBieSBxdW90aW5nIFNjb3R0IEJyaW0gWzFdOgo+Cj4gICAiT25l
IGdlbmVyYXRpb24ncyBydWxlIG9mIHRodW1iIGJlY29tZXMgdGhlIG5leHQgZ2VuZXJhdGlvbidz
IGRvZ21hLgo+ICAgIFRoZSBJRVRGIHNob3VsZCBzaXQgdXAgYW5kIHJlYWxseSB0aGluayB3aGVu
IHNvbWVvbmUgc3VnZ2VzdHMgdGhhdAo+ICAgIGEgcHJvY2VzcyBoYXMgYmVjb21lIGRvZ21hLiIK
Pgo+UXVvdGluZyBOZWQgWzJdOgo+Cj4gICAiSSdkIG11Y2ggcmF0aGVyIGJyZWFjaCB0aGUgc2Fu
Y3RpdHkgb2YgdGhlIHJ1bGVzIGJ5IGdldHRpbmcgcmlkIG9mCj4gICAgc29tZSBvZiB0aGVtIGVu
dGlyZWx5LiIKPgo+UXVvdGluZyBSdXNzIFszXToKPgo+ICAgIldoZW4gYWxsIG9mIHRoZSBJbnRl
cm5ldC1EcmFmdHMgd2VyZSBwcm9jZXNzZWQgYnkgU2VjcmV0YXJpYXQgc3RhZmYsCj4gICAgdGhl
cmUgd2FzIGEgaHVnZSB3b3JrbG9hZCBjb25jZXJuLiAgTm93IHRoYXQgdGhlIEludGVybmV0LURy
YWZ0Cj4gICAgU3VibWlzc2lvbiBUb29sIChJRFNUKSBpcyB0YWtpbmcgdGhlIGJ1bGsgb2YgdGhl
IGxvYWQsIHRoZXJlIGFyZQo+ICAgIHJlc291cmNlcyB0byBkZWFsIHdpdGggdGhlc2UgZXhjZXB0
aW9ucywgYXMgd2FzIGp1c3QgZGVtb25zdHJhdGVkLiIKPgo+V2hpY2ggd2FzIGluIHJlc3BvbnNl
IHRvIEpvaG4gS2xlbnNpbiB3aG8gc2FpZCBbNF06Cj4KPiAgICJUaGUgb3JpZ2luYWwgcmVhc29u
IGZvciB0aG9zZSBjdXRvZmZzIC0tIGV2ZW4gbW9yZSBpbXBvcnRhbnQKPiAgICB0aGFuIGdpdmlu
ZyBwZW9wbGUgdGltZSB0byByZWFkIGRyYWZ0cyAtLSB3YXMgdGhhdCB0aGUKPiAgICBzdWJtaXNz
aW9ucyB3ZXJlIG92ZXJ3aGVsbWluZyB0aGUgU2VjcmV0YXJpYXQuICBOb3Qgb25seSBkaWQKPiAg
ICB0aGV5IGhhdmUgb3RoZXIgdGhpbmdzIHRvIGRvIGluIHRoZSB3ZWVrcyBiZWZvcmUgdGhlIG1l
ZXRpbmcsIGl0Cj4gICAgd2FzIGJlY29taW5nIHVucHJlZGljdGFibGUgd2hldGhlciBhIGRyYWZ0
IHN1Ym1pdHRlZCBpbiBhZHZhbmNlCj4gICAgb2YgdGhlIG1lZXRpbmcgd291bGQgYmUgcG9zdGVk
IGVhcmx5IGVub3VnaCBmb3IgdGhlIHJlbGV2YW50IFdHCj4gICAgdG8gbG9vayBhdCBpdC4gIFRo
ZSBzcGxpdCBiZXR3ZWVuICJuZXciIGFuZCAicmV2aXNlZCIgZHJhZnRzIHdhcwo+ICAgIGFub3Ro
ZXIgYXR0ZW1wdCB0byBwcm90ZWN0IHRoZSBTZWNyZXRhcmlhdCAtLSBub3Rpb25zIG9mIGhhdmlu
Zwo+ICAgIHRvIGZvcm1hbGx5IGFwcHJvdmUgV0cgZHJhZnRzIGNhbWUgbGF0ZXIuIgo+Cj5BbmQg
RGF2ZSBzYWlkIFs1XToKPgo+ICAgIkl0IHdvdWxkIHNlZW0gdGhhdCB0aGUgcmlnaHQgdGhpbmcg
aXMgdG8gcmVtb3ZlIHRoZSBjdXRvZmYgYW5kIGxldAo+ICAgICBlYWNoIHdvcmtpbmcgZ3JvdXAg
ZGVjaWRlIG9uIHdoYXQgZHJhZnRzIHdpbGwgYmUgd29ya2VkIG9uLiIKPgo+U3BlbmNlciBEYXdr
aW5zIFs2XSBxdW90ZWQgU2VjdGlvbiA3LjEgb2YgUkZDIDI0MTguCj4KPlBldGUgUmVzbmljayB3
YXMgb2YgdGhlIG9waW5pb24gWzddIHRoYXQ6Cj4KPiAgICJUaGUgY3V0b2ZmIGlzIGFuIGFyYml0
cmFyeSBwcm9jZWR1cmUgdG8gdHJ5IChwb29ybHkgSU1PKSB0byBlbmZvcmNlCj4gICAgdGhlIDI0
MTggcnVsZS4iCj4KPkkgc3VnZ2VzdCB0aGF0IFdHIGNoYWlycyBzdG9wIGFza2luZyB0aGUgd29y
a2luZyBncm91cCB3aGV0aGVyIHRoZXkgCj5oYXZlIHJlYWQgdGhlIGRyYWZ0IGFzIGl0IGlzIHNp
bGx5LiAgSXQgaXMgYW4gaW1wb3NzaWJsZSB0YXNrIHRvIGtlZXAgCj51cCB3aXRoIHRoZSBmbG9v
ZCBvZiBJLUQgdGhhdCBhcmUgc3VibWl0dGVkIG9uIE1lZXRpbmcgTW9uZGF5Lgo+Cj5SZWdhcmRz
LAo+LXNtCj4KPjEuIG1zZy1pZDogNDg4MjE0NjkuNDA1MDkwN0BlbXBsb3llZXMub3JnCj4yLiBt
c2ctaWQ6IDAxTVhDMDk2MkNMSTAwMDA3QUBtYXV2ZS5tcm9jaGVrLmNvbQo+My4gbXNnLWlkOiAy
MDA4MDcxOTE5MTU1Ni41NjdGMDNBNkEzMkBjb3JlMy5hbXNsLmNvbQo+NC4gbXNnLWlkOiAyRTFC
MkFCOTcwMzY5MEI4RTFFRUJFOTBAcDMuSkNLLkNPTQo+NS4gbXNnLWlkOiA0ODgyNkRDMC44MDAw
MzA3QGRjcm9ja2VyLm5ldAo+Ni4gbXNnLWlkOiAwMTM1MDFjOGVhNmEkMjcxZTI4YTAkNjUwMWE4
YzBAY2hpbmEuaHVhd2VpLmNvbQo+Ny4gbXNnLWlkOiBwMDYyNTAxMDBjNGE5MjI2ZWFjODdAWzc1
LjE0NS4xNzYuMjQyXSAKPgo+Cj4KPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+Cj5f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+SWV0ZiBtYWls
aW5nIGxpc3QKPklldGZAaWV0Zi5vcmcKPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaWV0Zgo+Cj4KPkVuZCBvZiBJZXRmIERpZ2VzdCwgVm9sIDM5LCBJc3N1ZSAxMwo+Kioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCg==


From dhc2@dcrocker.net  Tue Aug  2 13:45:34 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98AE421F874B for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 13:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.67
X-Spam-Level: 
X-Spam-Status: No, score=-6.67 tagged_above=-999 required=5 tests=[AWL=-0.071,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PqiUNc7Os+d1 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 13:45:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C7A6321F862F for <ietf@ietf.org>; Tue,  2 Aug 2011 13:45:33 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p72KjcWA001320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Aug 2011 13:45:43 -0700
Message-ID: <4E3861F0.7080507@dcrocker.net>
Date: Tue, 02 Aug 2011 13:45:36 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com> <201108011141.30549.scott@kitterman.com>
In-Reply-To: <201108011141.30549.scott@kitterman.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 02 Aug 2011 13:45:43 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 20:45:34 -0000

On 8/1/2011 8:41 AM, Scott Kitterman wrote:
> In fairness to Hector, the functionality that he is complaining is missing was
> part of the original working group charter.


please cite the text from the original charter that promises such work and, just 
to be safe, please cite the current text that claims it should be there.

In other words, the current complaint is about something missing.  Please quote 
the specification of that and then the part of the original charter that said we 
would do it.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From brian.e.carpenter@gmail.com  Tue Aug  2 14:08:40 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2068F11E80A9 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjzMBeRX0pFJ for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:08:39 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8E59611E808F for <ietf@ietf.org>; Tue,  2 Aug 2011 14:08:39 -0700 (PDT)
Received: by vxi40 with SMTP id 40so195636vxi.31 for <ietf@ietf.org>; Tue, 02 Aug 2011 14:08:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Nwr0CM0+nw9lCDqVuF0HsqW5m2uogKs8JEsJRhK2BZI=; b=H9lqgKleFTsI32nXNXYy0Th0gTf/+bKyJjhyADRn7HrwPJmVpn1G7atHmRtr0Km722 G3zYyweYtET283zoidWyLierxov0Z77UfTI8FyaibEVmaRvpL3RsN2gtsXayb5sIYHLp 6Wn2PrjmCAHuMeiuA+eNxzZo3TPfaJlX9Ekl4=
Received: by 10.52.187.4 with SMTP id fo4mr1286913vdc.209.1312319329224; Tue, 02 Aug 2011 14:08:49 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id dn12sm62165vcb.16.2011.08.02.14.08.47 (version=SSLv3 cipher=OTHER); Tue, 02 Aug 2011 14:08:48 -0700 (PDT)
Message-ID: <4E38675D.6000100@gmail.com>
Date: Wed, 03 Aug 2011 09:08:45 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: A modest proposal for Friday meeting schedule
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>	<B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com>	<60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com>	<20110801133935.GC89723@verdi>	<2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com>	<4E371CD0.9010501@nostrum.com>	<535D447870130147BCE840BA@PST.JCK.COM> <075B1870-7D4C-4766-9D7F-279182275FBE@mnot.net>
In-Reply-To: <075B1870-7D4C-4766-9D7F-279182275FBE@mnot.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 21:08:40 -0000

On 2011-08-03 05:45, Mark Nottingham wrote:

<snip>

> 
> ... Some people will still doubtless complain.
> 

</snip>

Could we take this as the conclusion of this discussion?

I'm being serious. Tuning the schedule in the light of feedback
should be a constant concern, amd it will always be a balancing act
between varying preferences among participants, session chairs, and
area directors, *plus* constraints from room layout, costs and
availability at each venue. I expect the schedule to be a work in
progress for ever.

   Brian

From hsantos@isdg.net  Tue Aug  2 14:31:52 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5622D11E80BC for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.701
X-Spam-Level: 
X-Spam-Status: No, score=-3.701 tagged_above=-999 required=5 tests=[AWL=-1.102, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1pCGH8p8G9W for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:31:51 -0700 (PDT)
Received: from mail.santronics.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2BA11E80BE for <ietf@ietf.org>; Tue,  2 Aug 2011 14:31:50 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=10618; t=1312320714; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=OHRxTkPcSaa/9AQlIIqO4MA3q+g=; b=WowUlNgXlAkf34+SHeK/ dFm3J5A+B8tgiY7OObamb2mvqbjm+lrlrDYvUmNH81KIPS0AqKTx9GE4rBFBVKX3 r7wq7PA8iCmzQ6cUvVykVhioNueE92V8F6Jr+Pe8oTQJuD71gDw0X+MywAZeeH47 JK+L/2CtPlzVh0V8O49rGZA=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 02 Aug 2011 17:31:54 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer); 
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 776199593.32986.4168; Tue, 02 Aug 2011 17:31:54 -0400
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312320443; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=Vfa1CwsmfHryDdjcnl X7EJ/mtwrGMaha2dp3cSDmpOM=; b=cqKhQK1Idn/JpGR7a+GE8N0JQ/9Vafs06Y EOYPCJFNVO61j+b0Bs+8msVwQDodfGpOHvzXsFlV0tctCLajmKzrR0GqihNdrWNX NMHbG5IzLURixOLjOd8fBW272TMFk7sWdX607GIKpRh3rz5AdU7yMeAqe3Yh7ECr aOjS/2Sg4=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 02 Aug 2011 17:27:23 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1747481080.349.156; Tue, 02 Aug 2011 17:27:22 -0400
Message-ID: <4E386CF8.5020508@isdg.net>
Date: Tue, 02 Aug 2011 17:32:40 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com> <4E352A74.6080703@isdg.net>	<773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>	<201108011141.30549.scott@kitterman.com> <4E3861F0.7080507@dcrocker.net>
In-Reply-To: <4E3861F0.7080507@dcrocker.net>
Content-Type: multipart/mixed; boundary="------------070905060901020509080403"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 21:31:52 -0000

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

Dave CROCKER wrote:

> On 8/1/2011 8:41 AM, Scott Kitterman wrote:
>> In fairness to Hector, the functionality that he is complaining is 
>> missing was
>> part of the original working group charter.
> 
> 
> please cite the text from the original charter that promises such work 
> and, just to be safe, please cite the current text that claims it should 
> be there.
> 
> In other words, the current complaint is about something missing.  
> Please quote the specification of that and then the part of the original 
> charter that said we would do it.

We are perfectly aware you never believed in policy, never really 
acknowledge it, fought hard against its progress. I can respect that 
position. But I am bit vex as to why you are questioning its existence 
as an original and still current WG work item.

The DKIM WG always had among its charter work items to produce a 
Domain Policy standard and even thought the charter was revised over 
the years, Policy is still today among the WG chartered item today. I 
personally have not seen or read of any official statement to conclude 
the WG and stop all remaining work, nor a change in the charter to 
official remain policy as a work item.

Attached is 2005 copy of the charter I have on disk. Please note how 
reputation was declared of out of scope, yet it continued to disrupt 
the WG and revamped DKIM to its present condition.

Two other WG RFC work items were completed; one directly related to 
producing the "Requirements for a DKIM Signing Practices Protocol" 
RFC5016, and a Threat Analysis RFC4686 which includes among its 
analysis how policy can mitigate certain security threats using Policy.

You, yourself, wrote a RFC5585 called

     "DomainKeys Identified Mail (DKIM) Service Overview"

with signing practices peppered over all the document as a major piece 
of the system. This sentence is found in the abstract:

    DKIM also enables a mechanism that permits potential email signers to
    publish information about their email signing practices; this will
    permit email receivers to make additional assessments about messages.

And the RFC includes a spiffy process flow illustration titled

       "DKIM Service Architecture"

with a Checking Signing Practice component as a major piece of this 
design.

So I am "scratching my head" here wondering why you are now 
questioning how a framework designed over 5 years had major work 
productions dismissed, especially those related to security, in the 
pursuit of the unrestricted resigner and 3rd party trust vendor 
service market and now seem to suggest the DKIM WG Domain Signing 
Practices standardization efforts was not a work item and never 
existed in the first place as a charter item, when in fact, it is 
still today a WG charter item.

Very odd.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com

--------------070905060901020509080403
Content-Type: text/plain;
 name="DKIM-charter-06bl.txt"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="DKIM-charter-06bl.txt"

DQoNCkRSQUZUIElFVEYgV09SS0lORyBHUk9VUCBDSEFSVEVSICANCjE0IE9jdCAyMDA1DQoN
Cg0KRG9tYWluIEtleXMgSWRlbnRpZmllZCBNZXNzYWdlIChES0lNKQ0KDQoNCkNIQUlSUzog
DQogICAgIFRCRA0KQVJFQSBESVJFQ1RPUlM6IA0KICAgICBSdXNzZWxsIEhvdXNsZXksIFNh
bSBIYXJ0bWFuDQpBUkVBIEFEVklTT1I6IA0KICAgICBSdXNzZWxsIEhvdXNsZXkgPGhvdXNs
ZXlAdmlnaWxzZWMuY29tPg0KTUFJTElORyBMSVNUUzogDQogICAgR2VuZXJhbCBEaXNjdXNz
aW9uOiBpZXRmLWRraW1AbWlwYXNzb2Mub3JnDQogICAgVG8gU3Vic2NyaWJlOiBodHRwOi8v
bWlwYXNzb2Mub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zi1ka2ltDQogICAgQXJjaGl2ZTog
aHR0cDovL21pcGFzc29jLm9yZy9waXBlcm1haWwvaWV0Zi1ka2ltLw0KDQpERVNDUklQVElP
TiBPRiBXT1JLSU5HIEdST1VQOg0KDQpUaGUgSW50ZXJuZXQgbWFpbCBwcm90b2NvbHMgYW5k
IGluZnJhc3RydWN0dXJlIGFsbG93IG1haWwgc2VudCBmcm9tIG9uZSANCmRvbWFpbiB0byBw
dXJwb3J0IHRvIGJlIGZyb20gYW5vdGhlci4gIFdoaWxlIHRoZXJlIGFyZSBzb21ldGltZXMg
bGVnaXRpbWF0ZSANCnJlYXNvbnMgZm9yIGRvaW5nIHRoaXMsIGl0IGhhcyBiZWNvbWUgYSBz
b3VyY2Ugb2YgZ2VuZXJhbCBjb25mdXNpb24sIGFzIHdlbGwgDQphcyBhIG1lY2hhbmlzbSBm
b3IgZnJhdWQgYW5kIGZvciBkaXN0cmlidXRpb24gb2Ygc3BhbSAod2hlbiBkb25lIA0KaWxs
ZWdpdGltYXRlbHksIGl0J3MgY2FsbGVkICJzcG9vZmluZyIpLiAgVGhlIERLSU0gd29ya2lu
ZyBncm91cCB3aWxsIA0KcHJvZHVjZSBzdGFuZGFyZHMtdHJhY2sgc3BlY2lmaWNhdGlvbnMg
dGhhdCBhbGxvdyBhIGRvbWFpbiB0byB0YWtlIA0KcmVzcG9uc2liaWxpdHksIHVzaW5nIGRp
Z2l0YWwgc2lnbmF0dXJlcywgZm9yIGhhdmluZyB0YWtlbiBwYXJ0IGluIHRoZSANCnRyYW5z
bWlzc2lvbiBvZiBhbiBlbWFpbCBtZXNzYWdlIGFuZCB0byBwdWJsaXNoICJwb2xpY3kiIGlu
Zm9ybWF0aW9uIGFib3V0IA0KaG93IGl0IGFwcGxpZXMgdGhvc2Ugc2lnbmF0dXJlcy4gIFRh
a2VuIHRvZ2V0aGVyLCB0aGVzZSB3aWxsDQphc3Npc3QgcmVjZWl2aW5nIGRvbWFpbnMgaW4g
ZGV0ZWN0aW5nIChvciBydWxpbmcgb3V0KSBjZXJ0YWluIGZvcm1zIG9mIA0Kc3Bvb2Zpbmcg
YXMgaXQgcGVydGFpbnMgdG8gdGhlIHNpZ25pbmcgZG9tYWluLg0KDQpUaGUgREtJTSB3b3Jr
aW5nIGdyb3VwIHdpbGwgcHJvZHVjZSBzdW1tYXJpZXMgb2YgdGhlIHRocmVhdHMgdGhhdCBh
cmUgDQphZGRyZXNzZWQgYnkgdGhlIHN0YW5kYXJkcy10cmFjayBzcGVjaWZpY2F0aW9ucywg
d2hpbGUgYWNrbm93bGVkZ2luZyB0aGVpciANCmxpbWl0YXRpb25zIGFuZCBzY29wZS4gIFRo
ZSBES0lNIHdvcmtpbmcgZ3JvdXAgd2lsbCBhbHNvIHByb2R1Y2Ugc2VjdXJpdHkgDQpyZXF1
aXJlbWVudHMgdG8gZ3VpZGUgdGhlaXIgZWZmb3J0cywgYW5kIHdpbGwgYW5hbHl6ZSB0aGUg
aW1wYWN0IG9uIHNlbmRlcnMgDQphbmQgcmVjZWl2ZXJzIHdobyBhcmUgbm90IHVzaW5nIERL
SU0sIHBhcnRpY3VsYXJseSBhbnkgY2FzZXMgaW4gd2hpY2gNCm1haWwgbWF5IGJlIGluYXBw
cm9wcmlhdGVseSBsYWJlbGVkIGFzIHN1c3BpY2lvdXMgb3Igc3Bvb2ZlZC4NCg0KV2hpbGUg
dGhlIHRlY2huaXF1ZXMgc3BlY2lmaWVkIGJ5IHRoZSBES0lNIHdvcmtpbmcgZ3JvdXAgd2ls
bCBub3QgcHJldmVudCANCmZyYXVkIG9yIHNwYW0sIHRoZXkgd2lsbCBwcm92aWRlIGEgdmFs
dWFibGUgdG9vbCBmb3IgZGVmZW5zZSBhZ2FpbnN0IHRoZW0gYnkgDQphbGxvd2luZyByZWNl
aXZpbmcgZG9tYWlucyB0byBkZXRlY3Qgc3Bvb2Zpbmcgb2Yga25vd24gZG9tYWlucy4gIFRo
ZSANCnN0YW5kYXJkcy10cmFjayBzcGVjaWZpY2F0aW9ucyB3aWxsIG5vdCBtYW5kYXRlIGFu
eSBwYXJ0aWN1bGFyIGFjdGlvbiBieSB0aGUgDQpyZWNlaXZpbmcgZG9tYWluIHdoZW4gc3Bv
b2ZpbmcgaXMgZGV0ZWN0ZWQuICBUaGUgREtJTSB3b3JraW5nIGdyb3VwIHdpbGwgbm90IA0K
YXR0ZW1wdCB0byBkZWZpbmUgc3VjaCBhY3Rpb25zLCB0byBlc3RhYmxpc2ggcmVxdWlyZW1l
bnRzIGZvciB0cnVzdCANCnJlbGF0aW9uc2hpcHMgYmV0d2VlbiBkb21haW5zLCBvciB0byBz
cGVjaWZ5IHJlcHV0YXRpb24gb3IgYWNjcmVkaXRhdGlvbiANCnN5c3RlbXMuICANCg0KVGhl
IHNpZ25hdHVyZXMgd2lsbCB1c2UgcHVibGljLWtleSBjcnlwdG9ncmFwaHkgYW5kIHdpbGwg
YmUgYmFzZWQgb24gZG9tYWluIA0KbmFtZSBpZGVudGlmaWVycy4gIFB1YmxpYyBrZXlzIG5l
ZWRlZCB0byB2YWxpZGF0ZSB0aGUgc2lnbmF0dXJlcyB3aWxsIGJlIA0Kc3RvcmVkIGluIHRo
ZSByZXNwb25zaWJsZSBpZGVudGl0eSdzIEROUyBoaWVyYXJjaHkuICBUaGUgc3BlY2lmaWNh
dGlvbnMgd2lsbCANCmJlIGJhc2VkIG9uIHRoZSBmb2xsb3dpbmcgSW50ZXJuZXQgRHJhZnRz
OiANCg0KKiBkcmFmdC1mZW50b24tZGtpbS10aHJlYXRzDQoqIGRyYWZ0LWFsbG1hbi1ka2lt
LWJhc2UNCiogZHJhZnQtYWxsbWFuLWRraW0tc3NwDQoNCndoaWNoIHJlcHJlc2VudCBleHBl
cmltZW50YXRpb24gYW5kIGNvbnNlbnN1cyBmcm9tIGEgbnVtYmVyIG9mIGRlc2lnbmVycyBh
bmQgDQplYXJseSBpbXBsZW1lbnRvcnMuICANCiANClNpbmNlIGV4cGVyaW1lbnRhdGlvbiBy
ZXN1bHRlZCBpbiBzaWduaWZpY2FudCBJbnRlcm5ldCBkZXBsb3ltZW50IG9mIHRoZXNlIA0K
c3BlY2lmaWNhdGlvbnMsIHRoZSBES0lNIHdvcmtpbmcgZ3JvdXAgd2lsbCBtYWtlIGV2ZXJ5
IHJlYXNvbmFibGUgYXR0ZW1wdCB0byANCmtlZXAgY2hhbmdlcyBjb21wYXRpYmxlIHdpdGgg
d2hhdCBpcyBkZXBsb3llZCwgbWFraW5nIGluY29tcGF0aWJsZSBjaGFuZ2VzIA0Kb25seSB3
aGVuIHRoZXkgYXJlIG5lY2Vzc2FyeSBmb3IgdGhlIHN1Y2Nlc3Mgb2YgdGhlIHNwZWNpZmlj
YXRpb25zLiAgDQoNClRoZSByZXN1bHRpbmcgcHJvdG9jb2xzIG11c3QgbWVldCB0eXBpY2Fs
IGNyaXRlcmlhIGZvciBzdWNjZXNzLiAgSW4gYWRkaXRpb24gDQp0byBzZWN1cml0eSwgdGhl
c2UgaW5jbHVkZSB1c2FiaWxpdHksIHNjYWxhYmlsaXR5LCBlYXNlIG9mIGRlcGxveW1lbnQs
IGFuZCANCmNyeXB0b2dyYXBoaWMgYWxnb3JpdGhtIGluZGVwZW5kZW5jZS4gIA0KDQpUbyBw
cmV2ZW50IHRoaXMgdGFzayBmcm9tIGJlY29taW5nIHVud2llbGR5LCBzZXZlcmFsIHJlbGF0
ZWQgdG9waWNzIGFyZQ0KY29uc2lkZXJlZCBvdXQgb2Ygc2NvcGUgZm9yIHRoZSBES0lNIHdv
cmtpbmcgZ3JvdXAuICBUaGVzZSB0b3BpY3MgaW5jbHVkZToNCg0KKiBSZXB1dGF0aW9uIGFu
ZCBhY2NyZWRpdGF0aW9uIHN5c3RlbXMuICBXaGlsZSB3ZSBleHBlY3QgdGhlc2UgdG8gYWRk
IHZhbHVlIA0KICB0byB3aGF0IGlzIGRlZmluZWQgYnkgdGhlIERLSU0gd29ya2luZyBncm91
cCwgdGhlaXIgZGV2ZWxvcG1lbnQgd2lsbCBiZSANCiAgc2VwYXJhdGUsIGFuZCBpcyBvdXQg
b2Ygc2NvcGUgZm9yIHRoZSBES0lNIHdvcmtpbmcgZ3JvdXAuICANCg0KKiBNZXNzYWdlIGNv
bnRlbnQgZW5jcnlwdGlvbi4gIA0KDQoqIEFkZGl0aW9uYWwga2V5IG1hbmFnZW1lbnQgcHJv
dG9jb2xzIG9yIGluZnJhc3RydWN0dXJlLiAgDQoNCiogU2lnbmF0dXJlcyB0aGF0IGFyZSBp
bnRlbmRlZCB0byBtYWtlIGxvbmctdGVybSBhc3NlcnRpb25zIGJleW9uZCB0aGUgDQogIGV4
cGVjdGVkIHRyYW5zaXQgdGltZSBvZiBhIG1lc3NhZ2UgZnJvbSBvcmlnaW5hdG9yIHRvIHJl
Y2lwaWVudCwgd2hpY2ggaXMgDQogIG5vcm1hbGx5IG9ubHkgYSBtYXR0ZXIgb2YgYSBmZXcg
ZGF5cyBhdCBtb3N0LiAgDQoNCiogU2lnbmF0dXJlcyB0aGF0IGF0dGVtcHQgdG8gbWFrZSBz
dHJvbmcgYXNzZXJ0aW9ucyBhYm91dCB0aGUgaWRlbnRpdHkgb2YgDQogIHRoZSBtZXNzYWdl
IGF1dGhvciwgYW5kIGRldGFpbHMgb2YgdXNlci1sZXZlbCBzaWduaW5nIG9mIG1lc3NhZ2Vz
IChhcyANCiAgZGlzdGluZ3Vpc2hlZCBmcm9tIGRvbWFpbi1sZXZlbCBrZXlzIHRoYXQgYXJl
IHJlc3RyaWN0ZWQgdG8gc3BlY2lmaWMgDQogIHVzZXJzKS4NCg0KKiBEdXBsaWNhdGlvbiBv
ZiBwcmlvciB3b3JrIGluIHNpZ25lZCBlbWFpbCwgaW5jdWRpbmcgUy9NSU1FIGFuZCBPcGVu
UEdQLiAgDQoNCk9uY2UgdGhlIHByaW1hcnkgZ29hbHMgYXJlIG1ldCwgdGhlIERLSU0gd29y
a2luZyBncm91cCBtYXkgYWxzbyBzdHVkeSANCndoZXRoZXIgdG8gYWRvcHQgYSB3b3JrIGl0
ZW0gZm9yIHNwZWNpZnlpbmcgYSBjb21tb24gbWVjaGFuaXNtIHRvIA0KY29tbXVuaWNhdGUg
dGhlIHJlc3VsdHMgb2YgbWVzc2FnZSB2ZXJpZmljYXRpb24gdG8gdGhlIG1lc3NhZ2UgcmVj
aXBpZW50LiAgDQpUaGUgZ2VuZXJhdGlvbiBvZiBhIHN0YW5kYXJkcy10cmFjayBzcGVjaWZp
Y2F0aW9uIHdpbGwgcmVxdWlyZSBhbiB1cGRhdGUgdG8gDQp0aGUgREtJTSB3b3JraW5nIGdy
b3VwIGNoYXJ0ZXIuICANCg0KVGhlIGRlbGl2ZXJhYmxlcyBmb3IgdGhlIERLSU0gd29ya2lu
ZyBncm91cCBhcmU6IA0KDQoqIGFuIGluZm9ybWF0aW9uYWwgUkZDIHByb3ZpZGluZyBhbiBv
dmVydmlldyBvZiBES0lNLCBob3cgaXQgY2FuIGZpdA0KICBpbnRvIG92ZXJhbGwgbWVzc2Fn
aW5nIHN5c3RlbXMgYW5kIG91dGxpbmluZyBwb3RlbnRpYWwgREtJTSBhcHBsaWN0aW9ucw0K
ICBhbmQgZnV0dXJlIGV4dGVuc2lvbnMNCiogYW4gaW5mb3JtYXRpb25hbCBSRkMgcHJlc2Vu
dGluZyBhIGRldGFpbGVkIHRocmVhdCBhbmFseXNpcyBvZiwgYW5kIA0KICBzZWN1cml0eSBy
ZXF1aXJlbWVudHMgZm9yLCBES0lNDQoqIGEgc3RhbmRhcmRzIHRyYWNrIHNwZWNpZmljYXRp
b24gZm9yIERLSU0gc2lnbmF0dXJlIGFuZCB2ZXJpZmljYXRpb24NCiogYSBzdGFuZGFyZHMg
dHJhY2sgc3BlY2lmaWNhdGlvbiBmb3IgREtJTSBwb2xpY3kgaGFuZGxpbmcNCiogYSBzdGFu
ZGFyZHMgdHJhY2sgc3BlY2lmaWNhdGlvbiBmb3IgYSBES0lNIEROUyBSZXNvdXJjZSBSZWNv
cmQNCg0KDQpHT0FMUyBBTkQgTUlMRVNUT05FUzoNCg0KMDIvMDYgICAgIFdHIGxhc3QgY2Fs
bCBvbiBES0lNIHRocmVhdHMgYW5kIHNlY3VyaXR5IHJlcXVpcmVtZW50cw0KMDUvMDYgICAg
IFdHIGxhc3QgY2FsbCBvbiBES0lNIHNpZ25hdHVyZSBzcGVjaWZpY2F0aW9uDQowOS8wNiAg
ICAgV0cgbGFzdCBjYWxsIG9uIERLSU0gcG9saWN5IHNwZWNpZmljYXRpb24NCjEyLzA2ICAg
ICBXRyBsYXN0IGNhbGwgb24gREtJTSBETlMgUmVzb3VyY2UgUmVjb3JkDQoxMi8wNiAgICAg
V0cgbGFzdCBjYWxsIG9uIG92ZXJ2aWV3IGRvY3VtZW50DQoNCg==
--------------070905060901020509080403--





From ekr@rtfm.com  Tue Aug  2 14:48:48 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6487411E80AE for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:48:48 -0700 (PDT)
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=[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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5fHXtdwpbZH9 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:48:48 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9F70211E808F for <ietf@ietf.org>; Tue,  2 Aug 2011 14:48:47 -0700 (PDT)
Received: by wyj26 with SMTP id 26so156582wyj.31 for <ietf@ietf.org>; Tue, 02 Aug 2011 14:48:56 -0700 (PDT)
Received: by 10.227.32.136 with SMTP id c8mr5715339wbd.7.1312321736158; Tue, 02 Aug 2011 14:48:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.145.209 with HTTP; Tue, 2 Aug 2011 14:48:36 -0700 (PDT)
In-Reply-To: <4E373C50.9010402@gmail.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <20110801233548.GL25922@nsn.com> <4E373C50.9010402@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 2 Aug 2011 14:48:36 -0700
Message-ID: <CABcZeBOYa3f_YgwaA0+wVXXBjDfCuFurjmTOHzSr2EXmcNWXjg@mail.gmail.com>
Subject: Re: "technical" plenary [was: A modest proposal for Friday meeting schedule]
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 21:48:48 -0000

On Mon, Aug 1, 2011 at 4:52 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> In any case, the IRTF Report, IAB Report and RSOC Report could certainly be
> made in the other plenary.

Or omitted entirely, since they are duplicative of data which would be better
communicated in writing.

-Ekr

From msk@cloudmark.com  Tue Aug  2 14:58:45 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE00C5E8004 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.671
X-Spam-Level: 
X-Spam-Status: No, score=-103.671 tagged_above=-999 required=5 tests=[AWL=-0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktz6Scr3iXgK for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 14:58:45 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0145E8003 for <ietf@ietf.org>; Tue,  2 Aug 2011 14:58:45 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Tue, 2 Aug 2011 14:58:55 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 2 Aug 2011 14:58:54 -0700
Subject: RE: DKIM Signatures now being applied to IETF Email
Thread-Topic: DKIM Signatures now being applied to IETF Email
Thread-Index: AcxRW6lACT3B2Kv4QOqe9mlInjDZ6gAAZ6ag
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF50B@EXCH-C2.corp.cloudmark.com>
References: <20110725171748.GA13506@amsl.com>	<4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com> <201108011141.30549.scott@kitterman.com>	<4E3861F0.7080507@dcrocker.net> <4E386CF8.5020508@isdg.net>
In-Reply-To: <4E386CF8.5020508@isdg.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 21:58:46 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBIZWN0b3IgU2Fu
dG9zDQo+IFNlbnQ6IFR1ZXNkYXksIEF1Z3VzdCAwMiwgMjAxMSAyOjMzIFBNDQo+IFRvOiBpZXRm
QGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBES0lNIFNpZ25hdHVyZXMgbm93IGJlaW5nIGFwcGxp
ZWQgdG8gSUVURiBFbWFpbA0KPiANCj4gV2UgYXJlIHBlcmZlY3RseSBhd2FyZSB5b3UgbmV2ZXIg
YmVsaWV2ZWQgaW4gcG9saWN5LCBuZXZlciByZWFsbHkNCj4gYWNrbm93bGVkZ2UgaXQsIGZvdWdo
dCBoYXJkIGFnYWluc3QgaXRzIHByb2dyZXNzLiBJIGNhbiByZXNwZWN0IHRoYXQNCj4gcG9zaXRp
b24uIEJ1dCBJIGFtIGJpdCB2ZXggYXMgdG8gd2h5IHlvdSBhcmUgcXVlc3Rpb25pbmcgaXRzIGV4
aXN0ZW5jZQ0KPiBhcyBhbiBvcmlnaW5hbCBhbmQgc3RpbGwgY3VycmVudCBXRyB3b3JrIGl0ZW0u
DQoNCldoZXJlIEkgY29tZSBmcm9tLCBwZXJzb25hbCBhdHRhY2tzIGRvbid0IHN1cHBvcnQgeW91
ciBwb3NpdGlvbjsgdGhleSBkZWdyYWRlIHlvdXIgY3JlZGliaWxpdHkuDQoNCj4gVGhlIERLSU0g
V0cgYWx3YXlzIGhhZCBhbW9uZyBpdHMgY2hhcnRlciB3b3JrIGl0ZW1zIHRvIHByb2R1Y2UgYQ0K
PiBEb21haW4gUG9saWN5IHN0YW5kYXJkIGFuZCBldmVuIHRob3VnaHQgdGhlIGNoYXJ0ZXIgd2Fz
IHJldmlzZWQgb3Zlcg0KPiB0aGUgeWVhcnMsIFBvbGljeSBpcyBzdGlsbCB0b2RheSBhbW9uZyB0
aGUgV0cgY2hhcnRlcmVkIGl0ZW0gdG9kYXkuIEkNCj4gcGVyc29uYWxseSBoYXZlIG5vdCBzZWVu
IG9yIHJlYWQgb2YgYW55IG9mZmljaWFsIHN0YXRlbWVudCB0byBjb25jbHVkZQ0KPiB0aGUgV0cg
YW5kIHN0b3AgYWxsIHJlbWFpbmluZyB3b3JrLCBub3IgYSBjaGFuZ2UgaW4gdGhlIGNoYXJ0ZXIg
dG8NCj4gb2ZmaWNpYWwgcmVtYWluIHBvbGljeSBhcyBhIHdvcmsgaXRlbS4NCg0KVGhlcmUgaXMg
bm8gcnVsZSBhbnl3aGVyZSB0aGF0IEkndmUgc2VlbiByZXF1aXJpbmcgYSB3b3JraW5nIGdyb3Vw
IHRvIGNvbXBsZXRlIGFsbCBvZiBpdHMgY2hhcnRlcmVkIGl0ZW1zIGlmIG9uZSBvZiB0aGVtIHR1
cm5zIG91dCB0byBiZSBhIGJhZCBvciBkYW5nZXJvdXMgaWRlYSwgZXNwZWNpYWxseSBpZiB0aGUg
c3BvbnNvcmluZyBBcmVhIERpcmVjdG9yIGNvbmN1cnMuICBJdCBkb2Vzbid0IG1hdHRlciB3aGF0
IG90aGVyIGluZm9ybWF0aW9uYWwgZG9jdW1lbnRzIGl0IG1heSBoYXZlIHByb2R1Y2VkIHByaW9y
IHRvIHRoYXQgcG9pbnQuICBUaGlzIGlzIGFsc28gdHJ1ZSBpZiB0aGUgd29ya2luZyBncm91cCBy
dW5zIG91dCBvZiBzdGVhbSB0byBrZWVwIHdvcmtpbmcgb24gc29tZXRoaW5nLiAgQWxsIG9mIHRo
b3NlIHRoaW5ncyBoYXBwZW5lZCBoZXJlLg0KIA0KVGhlIG9uZ29pbmcgY2xhaW1zIHRoYXQgdGhl
IHdvcmtpbmcgZ3JvdXAgd2FzIGd1aWRlZCBieSBzaW5pc3RlciBkZXNpZ25zIHRvIGJlbmVmaXQg
ZnJvbSBzb21lIHNwZWNpZmljIGFsdGVybmF0ZSBtYXJrZXQgYXJlIHNpbXBseSBhYnN1cmQuDQoN
Cg==

From john-ietf@jck.com  Tue Aug  2 15:51:17 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88F9511E80E3 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 15:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.63
X-Spam-Level: 
X-Spam-Status: No, score=-102.63 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LzXT2ndUL2Y0 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 15:51:13 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 62C0111E8095 for <ietf@ietf.org>; Tue,  2 Aug 2011 15:51:12 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QoNnr-000CEd-Cg; Tue, 02 Aug 2011 18:51:12 -0400
Date: Tue, 02 Aug 2011 18:51:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <E1090BD02A7BD74AA756B06E@PST.JCK.COM>
In-Reply-To: <4E36C3E3.6050500@stpeter.im>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E343791.7040401@qualcomm.com> <4E3439CE.4030509@joelhalpern.com> <4E36C3E3.6050500@stpeter.im>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Pete Resnick <presnick@qualcomm.com>, Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 22:51:17 -0000

On 7/30/11 11:05 AM, Joel M. Halpern wrote:
> It seems to me that this does two things, both small but
> useful. 1) It makes a minor change in the advancement
> procedures so that they are more reasonable.  They may still
> not be sufficiently reasonable to be used, but it improves
> them, and thereby improves the odds.

Actually, there is no evidence that this is an improvement.  I'd
agree that it is a minor change, but there has been no serious
analysis of whether it is an improvement or not.  To the extent
to which approving this lowers the odds of considering and
making changes that might actually have significant effects
(e.g., really sorting out what maturity levels mean in a world
of increasingly complex standards), it is harmful.  See long
discussion below.

> 2) It is coupled to an
> intent to actually behave according to what the document
> says.  Such an intent is obviously not feasible without some
> change.

Well, yes and no.  My sense of the discussion over the last year
is that a significant fraction of the community believes that
the critical path change in this area is an adjustment to the
threshold for Proposed Standard.  That issue is addressed in
draft-bradner-restore-proposed, which requires no change to RFC
2026 or other formal procedures at all.  It is not addressed in
this document.

>  It is useful to have our behavior and our documented
> description of how we work match because the mismatch causes
> confusion, at least for new participants, and sometimes even
> for experienced participants.

I agree with this.  But this document doesn't make nearly enough
of a contribution in that area to justify approving it.  It
addresses exactly one provision of our processes in which
documentation and practice don't align, a provision about which
there is no subtlety or confusion within the community at all
(even though new participants may be confused).  If the issue is
important, then let's make a serious effort to update the places
where 2026, 2028, 2031, 2360, 3710, 4071, and probably several
other documents have fallen at least somewhat out of line with
reality.  If the particular issue of the annual review is really
more important than any of those other issues, I assume that a
stand-along document that changed it would rapidly achieve
community consensus (albeit with some complaints about wasted
time).  Certainly it should not be sufficient to justify
approving this document... the change is almost irrelevant to
it. 

> It might be the case that it will improve the advancement
> percentage. It might not.  I can not imagine that it will
> make that even worse.

I can because the effects of changes like this are actually very
hard to predict.  It increases the requirements for the second
level, however slightly.  Since we have trouble getting things
to the second level now, that increased requirement might reduce
incentives to bring things off Proposed at a least as much as a
theoretical "just one more level and then you are finished"
change would increase those incentives.  By changing Proposed
from "1/3 of the way" to "1/2 way or a bit more", it might
remove a small incentive to take the additional step.

In addition, the "publication without a new RFC" provision may
actually further increase the de facto requirements for Proposed
Standards by requiring that those documents be edited to a high
standard of clear English and specification precision.  While,
IMO, we have taken too little advantage of it, the current
provisions of RFC 2026 permit publishing a Proposed Standard as
soon as the WG understands it, leaving language cleanup (and
refined translation from the writing styles of many people in
the community whether native speakers of English or not) for
Draft Standard versions.

More important, for those of us who believe that a maturity
system based on rigid named categories that apply to entire
documents has outlived its usefulness as our specifications have
become more complex, approval of this document is almost certain
to cause consideration of such approaches to be postponed by
some years as people complain that the changes made in this
draft must have time to take effect and be evaluated.

   ---

A more extended analysis of other aspects of the situation with
this document follows.  Those who don't like extended analyses
might want to stop reading at some point.



A very long time ago, a then-professor of mine observed that one
of the most common sources of failures in engineering,
especially computer engineering, was to look at a problem that
seemed too large or too intractable, find some easily-changed
and tractable part of the problem, do something with it (almost
anything), and then claim that significant progress had been
made on the original/ real problem because one had started on
it.   In many cases, the approach actually makes the real
problem harder: systems become more complex, applying remedies
later turns out to be more complicated, and so on.  The narrow
"solution" may also use up energy and creates expectations that
make it harder than it would have been otherwise to take on the
real work when the narrow job fails to solve any significant
problems.

An even more insidious version of the same approach is to
identify a problem and claim it is serious enough that one needs
to do _something_.  One then proceeds to do something that has
nothing at all to do with the problem, just to demonstrate
motion (or in the hope that setting a butterfly in motion in one
part of the world will cause major change elsewhere).

These approaches are very different from taking a large design
issue and modularizing it into pieces that can be worked out
separately but with clear and well-understood interfaces.  Doing
that right requires that the overall design issue be understood
well enough to define all of the modules and interfaces, not
doing one piece, ignoring the poorly-understood rest, and hoping
that things will sort themselves out.

The IETF periodically falls into this trap.  We often see
protocols that are designed to handle the easy issues adopted
without consideration of the harder ones and edge cases, only to
discover that those protocols represent a framework into which
solutions for the other issues won't fit.  The largest symptoms
of this used to show up only with Security issues -- protocols
being designed without security provisions with the expectation
that security  would somehow be patched in later... and despite
repeated experiences that such patches are rarely completely
satisfactory.    Now we see it spreading: I've seen "we knew
about those issues but ignored them and now have to clean up the
mess somehow" comments in two separate WGs in recent weeks and
suspect that there are many more.  Many of the comments on this
list try to justify approving this draft on the same basis.

These "there is a problem so let's do something and hope it will
help", "even though we can demonstrate no logic that would
predict that the change being proposed will result in the
desired effect", and "let's fix something to show that we can"
approaches are _always_ justified on the basis of "baby steps"
or "incremental efforts".   Those justifications would be quite
reasonable if we actually had good evidence of the linkages.  In
the absence of such demonstrated linkages, we are just thrashing
around and wasting energy --energy that, under other
circumstances, could actually be used to address the problems. 

So, while I applaud the efforts of the authors of this draft to
remove controversial and largely extraneous material, it seems
to me that the core issue remains the one that many people have
commented on in much earlier versions: At present, we don't get
many documents from Proposed Standard to Draft Standard, despite
the requirements for Draft Standard being slightly lower than
those set forth for Internet Standard in this document.  We have
a possibly-serious problem with the norms for Proposed Standard
being too high in practice --far beyond what RFC 2026 requires.
It is noteworthy that draft-housley-two-maturity-levels no
longer makes any claim to solve that problem.  On the other
hand, there has been considerable discussion in the community,
previously supported by the strongest advocates for the
predecessors of the current draft, that the norms for getting to
Proposed Standard _are_ the keystone problem.  I don't
personally believe that -- I think things are more complicated--
but I do see it as a critical element (see
draft-bradner-restore-proposed (expired today but can be
reposted if that would be useful)).

So this draft now ignores the threshold problem for Proposed
Standard and argues that "Changing the Internet Standards
Process from three maturity levels to two is intended to create
an environment where lessons from implementation and deployment
experience are used to improve specifications".  But there is no
logic to support the belief that intention will be satisfied.
The purpose of the three-level system is to create an
environment where the same lessons can be learned, applied, and
documented.  This document does nothing to change or improve
that environment unless one believes that, magically, removing
the third level will increase motivations for getting things to
draft.  The problem, which the document still describes, is that
documents don't move off the first level, not that somehow the
existence of the third one is pressing things down.

In progressing by baby steps, actual babies fall down a lot.
Usually they learn while falling and keep trying until they get
it right.  Equally important, for their purposes, the important
target is learning how to walk more reliably, not reaching a
specific goal or solving a particular problem.  The IETF lacks
those advantages: First, we are focused on the goal of making a
change and have posited that change in terms of a choice between
this particular document and doing nothing --all other
possibilities have been dismissed without significant
consideration.  To quote one of the co-authors of this draft
from a different thread:

> Herein lies the real problem:  As with many process and
> structure discussions in the IETF, folk often see only a
> simplistic, binary choice between whatever they prefer, versus
> something akin to chaos.
> 
> The world is more nuanced than that, and the choices more rich.

I agree, but this document is being treated as that sort of
binary choice.

Second, the community is easily exhausted by process debates and
the debate about this particular document has now been going on
for 13+ months.  Even if the suggestion made at the plenary
about opening 2026 were serious, does anyone actually believe
the community will be able to take up and evaluate more
significant process changes in the near future?  Or that this
document, if approved, will not be used to justify deferring
discussion of other changes because we have to see how it works
out?

So this is not "baby steps".  It is one step, a step that makes
a change that isn't demonstrably connected to the problem it
purports to solve and that leads into a dead end.

   john


> 






From moore@network-heretics.com  Tue Aug  2 16:29:00 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 996B211E80F2 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 16:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level: 
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2+W7Oad9AUoB for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 16:29:00 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 09C5211E8095 for <ietf@ietf.org>; Tue,  2 Aug 2011 16:29:00 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id BF6D420A28; Tue,  2 Aug 2011 19:29:09 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 02 Aug 2011 19:29:09 -0400
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=4SkS3O5KwJGUjP8nc0qciTJUP4w=; b=WK G38pVQ9qCSlh6CoaDxknBrra9KkYZBRVpeCcfmZPgr36RHBk6YWArlRMCY2J1bH4 TFAJdC7kOlQFj7NmopYv+0F2IYu4gC6S0UemJcfauqVRy/TVGziY6NtCKBULfXvA SXHMIrMunXaLuyFwzqzRcbN49lR/IjK2LF0r6HoUQ=
X-Sasl-enc: HeY1t1L1JPSJj40GaR9+TJZlI+CUHAJwNqkvq5jdSQWJ 1312327749
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 20B29457B1C; Tue,  2 Aug 2011 19:29:09 -0400 (EDT)
Subject: Re: A modest proposal for Friday meeting schedule
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E38675D.6000100@gmail.com>
Date: Tue, 2 Aug 2011 19:29:08 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <F6400B62-9B4F-4896-8894-89515140A1EB@network-heretics.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>	<B8E48539-BB03-41AB-8484-769624453E91@standardstrack.com>	<60D77A8A-7F31-471A-920A-51CD0B1279B8@lucidvision.com>	<20110801133935.GC89723@verdi>	<2C57DB73-695A-442A-AAEA-8194464D7122@vigilsec.com>	<4E371CD0.9010501@nostrum.com>	<535D447870130147BCE840BA@PST.JCK.COM> <075B1870-7D4C-4766-9D7F-279182275FBE@mnot.net> <4E38675D.6000100@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 23:29:00 -0000

On Aug 2, 2011, at 5:08 PM, Brian E Carpenter wrote:

> Could we take this as the conclusion of this discussion?

+1

> I'm being serious. Tuning the schedule in the light of feedback
> should be a constant concern, amd it will always be a balancing act
> between varying preferences among participants, session chairs, and
> area directors, *plus* constraints from room layout, costs and
> availability at each venue. I expect the schedule to be a work in
> progress for ever.

+1

From joelja@bogus.com  Tue Aug  2 17:22:32 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E31CD11E8108 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 17:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fPY3fYjbp4Ed for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 17:22:32 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2E26811E80F2 for <ietf@ietf.org>; Tue,  2 Aug 2011 17:22:31 -0700 (PDT)
Received: from [10.101.144.52] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p730LMwp091989 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 3 Aug 2011 00:21:23 GMT (envelope-from joelja@bogus.com)
Subject: Re: A modest proposal...
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=utf-8
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@mail.gmail.com>
Date: Tue, 2 Aug 2011 17:21:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C10D71D-4D9E-4129-9A32-43FB07DD565E@bogus.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org> <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com> <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@mail.gmail.com>
To: Mark Atwood <mra@pobox.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 03 Aug 2011 00:21:24 +0000 (UTC)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 00:22:33 -0000

On Aug 1, 2011, at 12:57 PM, Mark Atwood wrote:

> On Mon, Aug 1, 2011 at 10:08 AM, Hadriel Kaplan =
<HKaplan@acmepacket.com> wrote:
>>=20
>> Fascinating.  I had no idea that there even *was* such a phrase in =
common usage, let alone that there was known etymology for it.  One =
learns something new every day.
>> But I meant it quite literally: a moderate/humble/etc. proposal for =
Friday meeting schedule.
>=20
> English is funny that way, and it's one of the things that make it
> such a difficult language to learn.

=E8=8D=89=E6=B3=A5=E9=A9=AC

...

=E6=B2=B3=E8=9F=B9

idiom isn't a new concept.

>  A great deal of the meaning is
> not in the literal meaning of a given chain of words, but is also
> contained in the historical and literary allusions that given phrases
> may have, which often have the direct opposite or at least very
> different meaning than the literal words.
>=20
> ..m
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From jmh@joelhalpern.com  Tue Aug  2 17:23:24 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B52111E8108 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 17:23:24 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zm49DE4iCet for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 17:23:23 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:22]) by ietfa.amsl.com (Postfix) with ESMTP id 9373E11E80F0 for <ietf@ietf.org>; Tue,  2 Aug 2011 17:23:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 1861F325BF6D; Tue,  2 Aug 2011 17:23:32 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.71.0.17] (rrcs-208-105-237-226.nys.biz.rr.com [208.105.237.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 6566E3245306; Tue,  2 Aug 2011 17:23:31 -0700 (PDT)
Message-ID: <4E389500.90309@joelhalpern.com>
Date: Tue, 02 Aug 2011 20:23:28 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E343791.7040401@qualcomm.com> <4E3439CE.4030509@joelhalpern.com> <4E36C3E3.6050500@stpeter.im> <E1090BD02A7BD74AA756B06E@PST.JCK.COM>
In-Reply-To: <E1090BD02A7BD74AA756B06E@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 00:23:24 -0000

With mild apologies, I have retained John's text below because, even 
though I come to a different conclusion, I thought it important to 
retain for now.  If folks choose to follow up on this, significant 
trimming is recommended.

John, as far as I can tell there are three problems which various folks 
have wanted this document or its predecessor to address:
1) That the bar for PS is too high
2) That not enough documents are advancing up the standards track
3) That what we do and what we say we do do not match.

Clearly, these problems are related.
We could try to adopt a change that would address all three.  I dobut we 
would accomplish anything.

As far as I can tell, this document sensible tries to address one of 
these, namely item 3.  It tries to align what we document with what we 
do.  In order to do so, it also makes a change which may help item 2. 
It may not.

Now, you can argue that it is taking up energy that should go to item 1. 
  That is not unreasonable.  Except that I consider all the proposals I 
have seen for item 1 to be failures.  They fail in different ways, but 
they all have appeared to me to be bad ideas.  (I think, based on 
conversations, some folks were supporting the previous version of this 
document in the mistaken believe that it did more to address that than 
it actually provided.)

As such, we can either do nothing, or take this step that in my personal 
opinion addresses item 3, might turn out to help item 2, and does not 
hurt item 1.
I believe I understand your point below that without understanding how 
we ought to address problem 1, it is hard to be confident we are not 
making it worse rather than better.

Yours,
Joel

On 8/2/2011 6:51 PM, John C Klensin wrote:
>
> On 7/30/11 11:05 AM, Joel M. Halpern wrote:
>> It seems to me that this does two things, both small but
>> useful. 1) It makes a minor change in the advancement
>> procedures so that they are more reasonable.  They may still
>> not be sufficiently reasonable to be used, but it improves
>> them, and thereby improves the odds.
>
> Actually, there is no evidence that this is an improvement.  I'd
> agree that it is a minor change, but there has been no serious
> analysis of whether it is an improvement or not.  To the extent
> to which approving this lowers the odds of considering and
> making changes that might actually have significant effects
> (e.g., really sorting out what maturity levels mean in a world
> of increasingly complex standards), it is harmful.  See long
> discussion below.
>
>> 2) It is coupled to an
>> intent to actually behave according to what the document
>> says.  Such an intent is obviously not feasible without some
>> change.
>
> Well, yes and no.  My sense of the discussion over the last year
> is that a significant fraction of the community believes that
> the critical path change in this area is an adjustment to the
> threshold for Proposed Standard.  That issue is addressed in
> draft-bradner-restore-proposed, which requires no change to RFC
> 2026 or other formal procedures at all.  It is not addressed in
> this document.
>
>>   It is useful to have our behavior and our documented
>> description of how we work match because the mismatch causes
>> confusion, at least for new participants, and sometimes even
>> for experienced participants.
>
> I agree with this.  But this document doesn't make nearly enough
> of a contribution in that area to justify approving it.  It
> addresses exactly one provision of our processes in which
> documentation and practice don't align, a provision about which
> there is no subtlety or confusion within the community at all
> (even though new participants may be confused).  If the issue is
> important, then let's make a serious effort to update the places
> where 2026, 2028, 2031, 2360, 3710, 4071, and probably several
> other documents have fallen at least somewhat out of line with
> reality.  If the particular issue of the annual review is really
> more important than any of those other issues, I assume that a
> stand-along document that changed it would rapidly achieve
> community consensus (albeit with some complaints about wasted
> time).  Certainly it should not be sufficient to justify
> approving this document... the change is almost irrelevant to
> it.
>
>> It might be the case that it will improve the advancement
>> percentage. It might not.  I can not imagine that it will
>> make that even worse.
>
> I can because the effects of changes like this are actually very
> hard to predict.  It increases the requirements for the second
> level, however slightly.  Since we have trouble getting things
> to the second level now, that increased requirement might reduce
> incentives to bring things off Proposed at a least as much as a
> theoretical "just one more level and then you are finished"
> change would increase those incentives.  By changing Proposed
> from "1/3 of the way" to "1/2 way or a bit more", it might
> remove a small incentive to take the additional step.
>
> In addition, the "publication without a new RFC" provision may
> actually further increase the de facto requirements for Proposed
> Standards by requiring that those documents be edited to a high
> standard of clear English and specification precision.  While,
> IMO, we have taken too little advantage of it, the current
> provisions of RFC 2026 permit publishing a Proposed Standard as
> soon as the WG understands it, leaving language cleanup (and
> refined translation from the writing styles of many people in
> the community whether native speakers of English or not) for
> Draft Standard versions.
>
> More important, for those of us who believe that a maturity
> system based on rigid named categories that apply to entire
> documents has outlived its usefulness as our specifications have
> become more complex, approval of this document is almost certain
> to cause consideration of such approaches to be postponed by
> some years as people complain that the changes made in this
> draft must have time to take effect and be evaluated.
>
>     ---
>
> A more extended analysis of other aspects of the situation with
> this document follows.  Those who don't like extended analyses
> might want to stop reading at some point.
>
>
>
> A very long time ago, a then-professor of mine observed that one
> of the most common sources of failures in engineering,
> especially computer engineering, was to look at a problem that
> seemed too large or too intractable, find some easily-changed
> and tractable part of the problem, do something with it (almost
> anything), and then claim that significant progress had been
> made on the original/ real problem because one had started on
> it.   In many cases, the approach actually makes the real
> problem harder: systems become more complex, applying remedies
> later turns out to be more complicated, and so on.  The narrow
> "solution" may also use up energy and creates expectations that
> make it harder than it would have been otherwise to take on the
> real work when the narrow job fails to solve any significant
> problems.
>
> An even more insidious version of the same approach is to
> identify a problem and claim it is serious enough that one needs
> to do _something_.  One then proceeds to do something that has
> nothing at all to do with the problem, just to demonstrate
> motion (or in the hope that setting a butterfly in motion in one
> part of the world will cause major change elsewhere).
>
> These approaches are very different from taking a large design
> issue and modularizing it into pieces that can be worked out
> separately but with clear and well-understood interfaces.  Doing
> that right requires that the overall design issue be understood
> well enough to define all of the modules and interfaces, not
> doing one piece, ignoring the poorly-understood rest, and hoping
> that things will sort themselves out.
>
> The IETF periodically falls into this trap.  We often see
> protocols that are designed to handle the easy issues adopted
> without consideration of the harder ones and edge cases, only to
> discover that those protocols represent a framework into which
> solutions for the other issues won't fit.  The largest symptoms
> of this used to show up only with Security issues -- protocols
> being designed without security provisions with the expectation
> that security  would somehow be patched in later... and despite
> repeated experiences that such patches are rarely completely
> satisfactory.    Now we see it spreading: I've seen "we knew
> about those issues but ignored them and now have to clean up the
> mess somehow" comments in two separate WGs in recent weeks and
> suspect that there are many more.  Many of the comments on this
> list try to justify approving this draft on the same basis.
>
> These "there is a problem so let's do something and hope it will
> help", "even though we can demonstrate no logic that would
> predict that the change being proposed will result in the
> desired effect", and "let's fix something to show that we can"
> approaches are _always_ justified on the basis of "baby steps"
> or "incremental efforts".   Those justifications would be quite
> reasonable if we actually had good evidence of the linkages.  In
> the absence of such demonstrated linkages, we are just thrashing
> around and wasting energy --energy that, under other
> circumstances, could actually be used to address the problems.
>
> So, while I applaud the efforts of the authors of this draft to
> remove controversial and largely extraneous material, it seems
> to me that the core issue remains the one that many people have
> commented on in much earlier versions: At present, we don't get
> many documents from Proposed Standard to Draft Standard, despite
> the requirements for Draft Standard being slightly lower than
> those set forth for Internet Standard in this document.  We have
> a possibly-serious problem with the norms for Proposed Standard
> being too high in practice --far beyond what RFC 2026 requires.
> It is noteworthy that draft-housley-two-maturity-levels no
> longer makes any claim to solve that problem.  On the other
> hand, there has been considerable discussion in the community,
> previously supported by the strongest advocates for the
> predecessors of the current draft, that the norms for getting to
> Proposed Standard _are_ the keystone problem.  I don't
> personally believe that -- I think things are more complicated--
> but I do see it as a critical element (see
> draft-bradner-restore-proposed (expired today but can be
> reposted if that would be useful)).
>
> So this draft now ignores the threshold problem for Proposed
> Standard and argues that "Changing the Internet Standards
> Process from three maturity levels to two is intended to create
> an environment where lessons from implementation and deployment
> experience are used to improve specifications".  But there is no
> logic to support the belief that intention will be satisfied.
> The purpose of the three-level system is to create an
> environment where the same lessons can be learned, applied, and
> documented.  This document does nothing to change or improve
> that environment unless one believes that, magically, removing
> the third level will increase motivations for getting things to
> draft.  The problem, which the document still describes, is that
> documents don't move off the first level, not that somehow the
> existence of the third one is pressing things down.
>
> In progressing by baby steps, actual babies fall down a lot.
> Usually they learn while falling and keep trying until they get
> it right.  Equally important, for their purposes, the important
> target is learning how to walk more reliably, not reaching a
> specific goal or solving a particular problem.  The IETF lacks
> those advantages: First, we are focused on the goal of making a
> change and have posited that change in terms of a choice between
> this particular document and doing nothing --all other
> possibilities have been dismissed without significant
> consideration.  To quote one of the co-authors of this draft
> from a different thread:
>
>> Herein lies the real problem:  As with many process and
>> structure discussions in the IETF, folk often see only a
>> simplistic, binary choice between whatever they prefer, versus
>> something akin to chaos.
>>
>> The world is more nuanced than that, and the choices more rich.
>
> I agree, but this document is being treated as that sort of
> binary choice.
>
> Second, the community is easily exhausted by process debates and
> the debate about this particular document has now been going on
> for 13+ months.  Even if the suggestion made at the plenary
> about opening 2026 were serious, does anyone actually believe
> the community will be able to take up and evaluate more
> significant process changes in the near future?  Or that this
> document, if approved, will not be used to justify deferring
> discussion of other changes because we have to see how it works
> out?
>
> So this is not "baby steps".  It is one step, a step that makes
> a change that isn't demonstrably connected to the problem it
> purports to solve and that leads into a dead end.
>
>     john
>
>
>>
>
>
>
>
>
>

From jmh@joelhalpern.com  Tue Aug  2 17:28:10 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB5A11E80F0 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 17:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.963
X-Spam-Level: 
X-Spam-Status: No, score=-100.963 tagged_above=-999 required=5 tests=[AWL=-1.636, BAYES_00=-2.599, FRT_PROFILE2=1.981, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BglXm-N-LCcj for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 17:28:09 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:22]) by ietfa.amsl.com (Postfix) with ESMTP id 9749811E80A1 for <ietf@ietf.org>; Tue,  2 Aug 2011 17:28:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id A082C325BF6D for <ietf@ietf.org>; Tue,  2 Aug 2011 17:28:19 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.71.0.17] (rrcs-208-105-237-226.nys.biz.rr.com [208.105.237.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 5BE5D3245D45 for <ietf@ietf.org>; Tue,  2 Aug 2011 17:28:19 -0700 (PDT)
Message-ID: <4E389620.1030604@joelhalpern.com>
Date: Tue, 02 Aug 2011 20:28:16 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
CC: IETF-Discussion list <ietf@ietf.org>
Subject: Re: Languages, idiom, reference, subtext, ...
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org> <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com> <CANW5CYVuZopM-w45qiPHzzn9vR-W7TyJ7BA0+Vw5VwNhTKj4Eg@mail.gmail.com> <1C10D71D-4D9E-4129-9A32-43FB07DD565E@bogus.com>
In-Reply-To: <1C10D71D-4D9E-4129-9A32-43FB07DD565E@bogus.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 00:28:10 -0000

It was once explained to me that a government agency that takes 
information extraction seriously has several levels of testing for 
language proficiency.  For all (okay, maybe almost all, I do not have 
the details) the languages they care about, the higher level testing 
focuses on knowledge of culture, literature, and similar context for 
actually understanding what is being said.

Yours,
Joel (Halpern)

On 8/2/2011 8:21 PM, Joel Jaeggli wrote:
>
> On Aug 1, 2011, at 12:57 PM, Mark Atwood wrote:
>
>> On Mon, Aug 1, 2011 at 10:08 AM, Hadriel Kaplan<HKaplan@acmepacket.com>  wrote:
>>>
>>> Fascinating.  I had no idea that there even *was* such a phrase in common usage, let alone that there was known etymology for it.  One learns something new every day.
>>> But I meant it quite literally: a moderate/humble/etc. proposal for Friday meeting schedule.
>>
>> English is funny that way, and it's one of the things that make it
>> such a difficult language to learn.
>
> è�‰æ³¥é©¬
>
> ...
>
> æ²³èŸ¹
>
> idiom isn't a new concept.
>
>>   A great deal of the meaning is
>> not in the literal meaning of a given chain of words, but is also
>> contained in the historical and literary allusions that given phrases
>> may have, which often have the direct opposite or at least very
>> different meaning than the literal words.
>>
>> ..m
>> _______________________________________________
>> 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 hallam@gmail.com  Tue Aug  2 18:03:20 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8155D11E80D9 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 18:03:20 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7gS1l2uK5Xrc for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 18:03:19 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6D76011E80A1 for <ietf@ietf.org>; Tue,  2 Aug 2011 18:03:19 -0700 (PDT)
Received: by gxk19 with SMTP id 19so226060gxk.31 for <ietf@ietf.org>; Tue, 02 Aug 2011 18:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HsOSvRTa7g7e7q+RBQAQtRMFZxLJKYGkySubeSIZVJ8=; b=srBCQbvGt825gWYH26ZlwctKolT7PCE1Oc99R4gNHJBBm1hca1WQiJ0ScThitul3Ts jOTgJVBPVljutf5YYqTXq6tn6XGzacNy+hfj4gQm216Coo/LzdypySYQygNJvNb8oO+e 8LzzNRm0sTyFrvRl5mHl4t+0kK+cW2fHrncLk=
MIME-Version: 1.0
Received: by 10.101.131.33 with SMTP id i33mr4596650ann.28.1312333408702; Tue, 02 Aug 2011 18:03:28 -0700 (PDT)
Received: by 10.100.34.3 with HTTP; Tue, 2 Aug 2011 18:03:28 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20110801172353.0696f868@resistor.net>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <6.2.5.6.2.20110801172353.0696f868@resistor.net>
Date: Tue, 2 Aug 2011 21:03:28 -0400
Message-ID: <CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com>
Subject: Re: Drafts Submissions cut-off
From: Phillip Hallam-Baker <hallam@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=001636c5be92a711b504a98f6e6d
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 01:03:20 -0000

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

Well here we have a rule that seems to be codified so it has the exact
opposite of any rational effect.

Either don't have a cutoff at all or make it a requirement that all
materials be submitted in advance of the meeting.


On Mon, Aug 1, 2011 at 8:46 PM, SM <sm@resistor.net> wrote:

> Hi Phillip,
>
> At 11:31 AM 8/1/2011, Phillip Hallam-Baker wrote:
>
>> Over the weekend I attempted to determine the rules for discussion of
>> drafts at IETF meetings and was surprised to discover that they are not
>> actually written down anywhere (other than on the meetings page). As a
>> result we appear to have an anomalous situation in which an author who
>> misses the cut-off date for ID submissions is in fact entitled to sit on the
>> draft for two weeks and then submit when the ID queue re-opens.
>>
>> I suggest that this is a sub-optimal state of affairs. I see two
>> solutions:
>>
>> 1) Codify the requirement that materials to be discussed at the meeting
>> must be submitted before the cut-off and that submissions made during
>> meetings are strictly limited to revisions occurring after and between WG
>> sessions. [Except in exceptional circumstances with AD approval]
>>
>> 2) Eliminate the 2 week cut off completely.
>>
>
> I'll start by quoting Scott Brim [1]:
>
>  "One generation's rule of thumb becomes the next generation's dogma.
>   The IETF should sit up and really think when someone suggests that
>   a process has become dogma."
>
> Quoting Ned [2]:
>
>  "I'd much rather breach the sanctity of the rules by getting rid of
>   some of them entirely."
>
> Quoting Russ [3]:
>
>  "When all of the Internet-Drafts were processed by Secretariat staff,
>   there was a huge workload concern.  Now that the Internet-Draft
>   Submission Tool (IDST) is taking the bulk of the load, there are
>   resources to deal with these exceptions, as was just demonstrated."
>
> Which was in response to John Klensin who said [4]:
>
>  "The original reason for those cutoffs -- even more important
>   than giving people time to read drafts -- was that the
>   submissions were overwhelming the Secretariat.  Not only did
>   they have other things to do in the weeks before the meeting, it
>   was becoming unpredictable whether a draft submitted in advance
>   of the meeting would be posted early enough for the relevant WG
>   to look at it.  The split between "new" and "revised" drafts was
>   another attempt to protect the Secretariat -- notions of having
>   to formally approve WG drafts came later."
>
> And Dave said [5]:
>
>  "It would seem that the right thing is to remove the cutoff and let
>    each working group decide on what drafts will be worked on."
>
> Spencer Dawkins [6] quoted Section 7.1 of RFC 2418.
>
> Pete Resnick was of the opinion [7] that:
>
>  "The cutoff is an arbitrary procedure to try (poorly IMO) to enforce
>   the 2418 rule."
>
> I suggest that WG chairs stop asking the working group whether they have
> read the draft as it is silly.  It is an impossible task to keep up with the
> flood of I-D that are submitted on Meeting Monday.
>
> Regards,
> -sm
>
> 1. msg-id: 48821469.4050907@employees.org
> 2. msg-id: 01MXC0962CLI00007A@mauve.**mrochek.com<01MXC0962CLI00007A@mauve.mrochek.com>
> 3. msg-id: 20080719191556.567F03A6A32@**core3.amsl.com<20080719191556.567F03A6A32@core3.amsl.com>
> 4. msg-id: 2E1B2AB9703690B8E1EEBE90@p3.**JCK.COM<2E1B2AB9703690B8E1EEBE90@p3.JCK.COM>
> 5. msg-id: 48826DC0.8000307@dcrocker.net
> 6. msg-id: 013501c8ea6a$271e28a0$6501a8c0**@china.huawei.com<6501a8c0@china.huawei.com>
> 7. msg-id: p06250100c4a9226eac87@[75.145.**176.242]
>



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

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

Well here we have a rule that seems to be codified so it has the exact oppo=
site of any rational effect.<div><br></div><div>Either don&#39;t have a cut=
off at all or make it a requirement that all materials be submitted in adva=
nce of the meeting.</div>
<div><br><br><div class=3D"gmail_quote">On Mon, Aug 1, 2011 at 8:46 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;">
Hi Phillip,<div class=3D"im"><br>
At 11:31 AM 8/1/2011, Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Over the weekend I attempted to determine the rules for discussion of draft=
s at IETF meetings and was surprised to discover that they are not actually=
 written down anywhere (other than on the meetings page). As a result we ap=
pear to have an anomalous situation in which an author who misses the cut-o=
ff date for ID submissions is in fact entitled to sit on the draft for two =
weeks and then submit when the ID queue re-opens.<br>

<br>
I suggest that this is a sub-optimal state of affairs. I see two solutions:=
<br>
<br>
1) Codify the requirement that materials to be discussed at the meeting mus=
t be submitted before the cut-off and that submissions made during meetings=
 are strictly limited to revisions occurring after and between WG sessions.=
 [Except in exceptional circumstances with AD approval]<br>

<br>
2) Eliminate the 2 week cut off completely.<br>
</blockquote>
<br></div>
I&#39;ll start by quoting Scott Brim [1]:<br>
<br>
 =A0&quot;One generation&#39;s rule of thumb becomes the next generation&#3=
9;s dogma.<br>
 =A0 The IETF should sit up and really think when someone suggests that<br>
 =A0 a process has become dogma.&quot;<br>
<br>
Quoting Ned [2]:<br>
<br>
 =A0&quot;I&#39;d much rather breach the sanctity of the rules by getting r=
id of<br>
 =A0 some of them entirely.&quot;<br>
<br>
Quoting Russ [3]:<br>
<br>
 =A0&quot;When all of the Internet-Drafts were processed by Secretariat sta=
ff,<br>
 =A0 there was a huge workload concern. =A0Now that the Internet-Draft<br>
 =A0 Submission Tool (IDST) is taking the bulk of the load, there are<br>
 =A0 resources to deal with these exceptions, as was just demonstrated.&quo=
t;<br>
<br>
Which was in response to John Klensin who said [4]:<br>
<br>
 =A0&quot;The original reason for those cutoffs -- even more important<br>
 =A0 than giving people time to read drafts -- was that the<br>
 =A0 submissions were overwhelming the Secretariat. =A0Not only did<br>
 =A0 they have other things to do in the weeks before the meeting, it<br>
 =A0 was becoming unpredictable whether a draft submitted in advance<br>
 =A0 of the meeting would be posted early enough for the relevant WG<br>
 =A0 to look at it. =A0The split between &quot;new&quot; and &quot;revised&=
quot; drafts was<br>
 =A0 another attempt to protect the Secretariat -- notions of having<br>
 =A0 to formally approve WG drafts came later.&quot;<br>
<br>
And Dave said [5]:<br>
<br>
 =A0&quot;It would seem that the right thing is to remove the cutoff and le=
t<br>
 =A0 =A0each working group decide on what drafts will be worked on.&quot;<b=
r>
<br>
Spencer Dawkins [6] quoted Section 7.1 of RFC 2418.<br>
<br>
Pete Resnick was of the opinion [7] that:<br>
<br>
 =A0&quot;The cutoff is an arbitrary procedure to try (poorly IMO) to enfor=
ce<br>
 =A0 the 2418 rule.&quot;<br>
<br>
I suggest that WG chairs stop asking the working group whether they have re=
ad the draft as it is silly. =A0It is an impossible task to keep up with th=
e flood of I-D that are submitted on Meeting Monday.<br>
<br>
Regards,<br>
-sm<br>
<br>
1. msg-id: <a href=3D"mailto:48821469.4050907@employees.org" target=3D"_bla=
nk">48821469.4050907@employees.org</a><br>
2. msg-id: <a href=3D"mailto:01MXC0962CLI00007A@mauve.mrochek.com" target=
=3D"_blank">01MXC0962CLI00007A@mauve.<u></u>mrochek.com</a><br>
3. msg-id: <a href=3D"mailto:20080719191556.567F03A6A32@core3.amsl.com" tar=
get=3D"_blank">20080719191556.567F03A6A32@<u></u>core3.amsl.com</a><br>
4. msg-id: <a href=3D"mailto:2E1B2AB9703690B8E1EEBE90@p3.JCK.COM" target=3D=
"_blank">2E1B2AB9703690B8E1EEBE90@p3.<u></u>JCK.COM</a><br>
5. msg-id: <a href=3D"mailto:48826DC0.8000307@dcrocker.net" target=3D"_blan=
k">48826DC0.8000307@dcrocker.net</a><br>
6. msg-id: 013501c8ea6a$271e28a0$<a href=3D"mailto:6501a8c0@china.huawei.co=
m" target=3D"_blank">6501a8c0<u></u>@china.huawei.com</a><br>
7. msg-id: p06250100c4a9226eac87@[75.145.<u></u>176.242] <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>

--001636c5be92a711b504a98f6e6d--

From presnick@qualcomm.com  Tue Aug  2 18:52:18 2011
Return-Path: <presnick@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8A2C5E8010 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 18:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.509
X-Spam-Level: 
X-Spam-Status: No, score=-106.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HADMCzFlD3Vl for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 18:52:17 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id BE2DA5E800E for <ietf@ietf.org>; Tue,  2 Aug 2011 18:52:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1312336348; x=1343872348; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4E38A9CA.4030204@qualcomm.com>|Date:=20Tu e,=202=20Aug=202011=2020:52:10=20-0500|From:=20Pete=20Res nick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Phillip=20Hallam-Baker=20<hall am@gmail.com>|CC:=20SM=20<sm@resistor.net>,=20IETF=20Disc ussion=20Mailing=20List=20<ietf@ietf.org>|Subject:=20Re: =20Drafts=20Submissions=20cut-off|References:=20<CAMm+Lwi c08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.co m>=09<6.2.5.6.2.20110801172353.0696f868@resistor.net>=20< CAMm+Lwj=3DHWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mai l.gmail.com>|In-Reply-To:=20<CAMm+Lwj=3DHWRh_1408_geR+6E5 ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com>|Content-Type: =20text/plain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Df lowed|Content-Transfer-Encoding:=207bit|X-Originating-IP: =20[172.30.39.5]; bh=S166dlNEXaykLCS2PROO/+972cssiHfI2Co7M5myfqI=; b=bozJwb4fze/9h54Fukit9CZbC0L0ePE7Tj4te4ZJaUDrtiE9P17yePG0 24RD8voSKIapkl9BsUbCJyXLg5seEw6GfG231YPy8r8UW9TEVjNZGEDuA QJjuDbipgnnsvkoyO/CWcuqG8WhBlN7Eo5BbD7PnI3zw0Q6PQP2dYXuA1 k=;
X-IronPort-AV: E=McAfee;i="5400,1158,6426"; a="107509818"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 02 Aug 2011 18:52:13 -0700
X-IronPort-AV: E=Sophos;i="4.67,306,1309762800"; d="scan'208";a="106799904"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 02 Aug 2011 18:52:13 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.323.0; Tue, 2 Aug 2011 18:52:12 -0700
Message-ID: <4E38A9CA.4030204@qualcomm.com>
Date: Tue, 2 Aug 2011 20:52:10 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Drafts Submissions cut-off
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>	<6.2.5.6.2.20110801172353.0696f868@resistor.net> <CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com>
In-Reply-To: <CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: SM <sm@resistor.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 01:52:18 -0000

On 8/2/11 8:03 PM, Phillip Hallam-Baker wrote:
> Either don't have a cutoff at all or make it a requirement that all 
> materials be submitted in advance of the meeting.

Personally, I think chairs should have the discretion to allow or 
disallow discussion of documents submitted at any time, that they should 
be tougher about what they disallow, and that they should face the wrath 
of their WG members and their AD if they aren't. Right now, we have a 
deadline, but also allow for special dispensation to let drafts through. 
If chairs feel that they need *some* deadline written down somewhere in 
order to push back on things, I have an alternate suggestion:

Right now, all -00 submissions of WG drafts are gated on chair approval 
(I believe in an automated fashion). We could simply make the tool gate 
*all* WG submissions from some time before the meeting through the 
meeting week. That way, chairs can decide whether they will enforce the 
deadline and not let the draft through, or make exceptions and let the 
drafts through. See above statement regarding "wrath" if the chairs 
abuse this authority in either direction.

(If we had the resources, we could make the tool settable on a per-WG 
basis: One chair could say, "I want to gate all drafts", another could 
say, "I want to gate none", and others could put in a date range for 
gating.)

Again, I don't think there needs to be a cutoff or a gating function. 
Chairs already have the authority to tell folks to go jump in a lake. 
But I'm not against a tool if chairs feel like they need some sort of 
"official" pushback mechanism.

pr

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


From akatlas@gmail.com  Tue Aug  2 20:12:53 2011
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9D4D11E8081 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 20:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.725
X-Spam-Level: 
X-Spam-Status: No, score=-2.725 tagged_above=-999 required=5 tests=[AWL=-0.793, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIC4SgnBJ5yl for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 20:12:53 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 047E111E811B for <ietf@ietf.org>; Tue,  2 Aug 2011 20:12:52 -0700 (PDT)
Received: by pzk33 with SMTP id 33so419923pzk.18 for <ietf@ietf.org>; Tue, 02 Aug 2011 20:13:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=WWDty5G4mxvcu7BV15nlFuaRGPdA9E6lqWOxqRmwOvk=; b=fWokPC+T58f7m5ASPqf5+KC0j+9cYLtnqMUwBcHSvWHi9Rd20YtllHPd0vU2RCCggh ravVuwfw2EsSi14iJiWaBMQzYV4VLiIzcfHqlRq29NXqN5EMZQgP97o8V2fFln4PyI3b WtneNys++Xr/bNRw9KIi1DwYxw1zlURhc6oDc=
MIME-Version: 1.0
Received: by 10.142.201.14 with SMTP id y14mr4113492wff.227.1312341183571; Tue, 02 Aug 2011 20:13:03 -0700 (PDT)
Received: by 10.68.50.6 with HTTP; Tue, 2 Aug 2011 20:13:03 -0700 (PDT)
In-Reply-To: <4E38A9CA.4030204@qualcomm.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <6.2.5.6.2.20110801172353.0696f868@resistor.net> <CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com> <4E38A9CA.4030204@qualcomm.com>
Date: Tue, 2 Aug 2011 23:13:03 -0400
Message-ID: <CAG4d1rfEAO6LmMVDCEObZRsGtkakKE7fpO+oJUTJgiDUqvT1WQ@mail.gmail.com>
Subject: Re: Drafts Submissions cut-off
From: Alia Atlas <akatlas@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=000e0cd32f1612284304a9913eda
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 03:12:54 -0000

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

Several years ago, when submitting drafts became automated, we used to have
a hard cut-off and be unable to submit new drafts until after IETF.

That caused issues if discussions caused the desire to change/update drafts
during the meeting, then there was no way of having an easily accessible
version.

The current situation is a compromise where drafts can be updated during the
meeting - and WG chairs have discretion.

I think we've tweaked this one enough - not all WGs are the same.

Alia

On Tue, Aug 2, 2011 at 9:52 PM, Pete Resnick <presnick@qualcomm.com> wrote:

> On 8/2/11 8:03 PM, Phillip Hallam-Baker wrote:
>
>> Either don't have a cutoff at all or make it a requirement that all
>> materials be submitted in advance of the meeting.
>>
>
> Personally, I think chairs should have the discretion to allow or disallow
> discussion of documents submitted at any time, that they should be tougher
> about what they disallow, and that they should face the wrath of their WG
> members and their AD if they aren't. Right now, we have a deadline, but also
> allow for special dispensation to let drafts through. If chairs feel that
> they need *some* deadline written down somewhere in order to push back on
> things, I have an alternate suggestion:
>
> Right now, all -00 submissions of WG drafts are gated on chair approval (I
> believe in an automated fashion). We could simply make the tool gate *all*
> WG submissions from some time before the meeting through the meeting week.
> That way, chairs can decide whether they will enforce the deadline and not
> let the draft through, or make exceptions and let the drafts through. See
> above statement regarding "wrath" if the chairs abuse this authority in
> either direction.
>
> (If we had the resources, we could make the tool settable on a per-WG
> basis: One chair could say, "I want to gate all drafts", another could say,
> "I want to gate none", and others could put in a date range for gating.)
>
> Again, I don't think there needs to be a cutoff or a gating function.
> Chairs already have the authority to tell folks to go jump in a lake. But
> I'm not against a tool if chairs feel like they need some sort of "official"
> pushback mechanism.
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.**com/~presnick/<http://www.qualcomm.com/%7Epresnick/>
> >
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
>
> ______________________________**_________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/**listinfo/ietf<https://www.ietf.org/mailman/listinfo/ietf>
>

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

Several years ago, when submitting drafts became automated, we used to have=
 a hard cut-off and be unable to submit new drafts until after IETF.<br><br=
>That caused issues if discussions caused the desire to change/update draft=
s during the meeting, then there was no way of having an easily accessible =
version.<br>
<br>The current situation is a compromise where drafts can be updated durin=
g the meeting - and WG chairs have discretion.<br><br>I think we&#39;ve twe=
aked this one enough - not all WGs are the same.<br><br>Alia<br><br><div cl=
ass=3D"gmail_quote">
On Tue, Aug 2, 2011 at 9:52 PM, Pete Resnick <span dir=3D"ltr">&lt;<a href=
=3D"mailto:presnick@qualcomm.com">presnick@qualcomm.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On 8/2/11 8:03 PM, Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Either don&#39;t have a cutoff at all or make it a requirement that all mat=
erials be submitted in advance of the meeting.<br>
</blockquote>
<br></div>
Personally, I think chairs should have the discretion to allow or disallow =
discussion of documents submitted at any time, that they should be tougher =
about what they disallow, and that they should face the wrath of their WG m=
embers and their AD if they aren&#39;t. Right now, we have a deadline, but =
also allow for special dispensation to let drafts through. If chairs feel t=
hat they need *some* deadline written down somewhere in order to push back =
on things, I have an alternate suggestion:<br>

<br>
Right now, all -00 submissions of WG drafts are gated on chair approval (I =
believe in an automated fashion). We could simply make the tool gate *all* =
WG submissions from some time before the meeting through the meeting week. =
That way, chairs can decide whether they will enforce the deadline and not =
let the draft through, or make exceptions and let the drafts through. See a=
bove statement regarding &quot;wrath&quot; if the chairs abuse this authori=
ty in either direction.<br>

<br>
(If we had the resources, we could make the tool settable on a per-WG basis=
: One chair could say, &quot;I want to gate all drafts&quot;, another could=
 say, &quot;I want to gate none&quot;, and others could put in a date range=
 for gating.)<br>

<br>
Again, I don&#39;t think there needs to be a cutoff or a gating function. C=
hairs already have the authority to tell folks to go jump in a lake. But I&=
#39;m not against a tool if chairs feel like they need some sort of &quot;o=
fficial&quot; pushback mechanism.<br>

<br>
pr<br><font color=3D"#888888">
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/%7Epresnick/" target=3D"=
_blank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Incorporated - Direct phone: <a href=3D"tel:%28858%29651-4478" val=
ue=3D"+18586514478" target=3D"_blank">(858)651-4478</a>, Fax: <a href=3D"te=
l:%28858%29651-1102" value=3D"+18586511102" target=3D"_blank">(858)651-1102=
</a><br>

<br>
______________________________<u></u>_________________<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/<u></u>listinfo/ietf</a><br>
</font></blockquote></div><br>

--000e0cd32f1612284304a9913eda--

From dhc2@dcrocker.net  Tue Aug  2 20:58:09 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E7F11E8130 for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 20:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.662
X-Spam-Level: 
X-Spam-Status: No, score=-6.662 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AfAdp1pKSo4P for <ietf@ietfa.amsl.com>; Tue,  2 Aug 2011 20:58:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4ADE211E812E for <ietf@ietf.org>; Tue,  2 Aug 2011 20:58:09 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p733vvXq008892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Aug 2011 20:58:03 -0700
Message-ID: <4E38C744.5080901@dcrocker.net>
Date: Tue, 02 Aug 2011 20:57:56 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: A modest proposal...
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <7140E333-68BD-4916-A3E0-B177FE3CE199@lilacglade.org> <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com>
In-Reply-To: <AA167777-04EA-4C00-9364-16DCB9BEE719@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 02 Aug 2011 20:58:03 -0700 (PDT)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 03:58:10 -0000

On 8/1/2011 10:08 AM, Hadriel Kaplan wrote:
> Fascinating.  I had no idea that there even*was*  such a phrase in common usage, let alone that there was known etymology for it.  One learns something new every day.
> But I meant it quite literally: a moderate/humble/etc. proposal for Friday meeting schedule.


Hadriel,

Your proposal looked entirely serious to me and the only cultural import I saw 
was one of respecting people's desires to get home, perhaps a bit more than our 
desire for lunch at a reasonable hour (except for Spain)...

I've seen the phrase used frequently for just the sort of thing you offered, 
namely something of limited scope and intent, seeking a narrow, pragmatic 
improvement.  And it seems pretty clear from the multiple responses that other 
folks interpreted your posting similarly.

Some phrases do indeed become cultural and linguistic icons, but it never 
occurred to me that anyone saw this phrase that way.  Given a couple of thousand 
regular participants in IETF lists, I suspect the list of such latent 
sensitivities is quite long.

My own concern about this is that I never enjoy being reminded, once again, 
about just how poorly educated I am, since I hadn't heard of Swift's essay...

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From christer.holmberg@ericsson.com  Wed Aug  3 01:34:30 2011
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BF921F8B19 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 01:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PYLvtLkjtNq for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 01:34:30 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 30F6521F8880 for <ietf@ietf.org>; Wed,  3 Aug 2011 01:34:30 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-5e-4e390820e324
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id B4.1A.09774.028093E4; Wed,  3 Aug 2011 10:34:41 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.123]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Wed, 3 Aug 2011 10:34:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wed, 3 Aug 2011 10:32:43 +0200
Subject: RE: "technical" plenary [was: A modest proposal for Friday meeting schedule]
Thread-Topic: "technical" plenary [was: A modest proposal for Friday meeting schedule]
Thread-Index: AcxRXgN1SA72tYrUSU2vZO/KQ0YlqgAWeai3
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05851DB6190FF6@ESESSCMS0356.eemea.ericsson.se>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <20110801233548.GL25922@nsn.com> <4E373C50.9010402@gmail.com>, <CABcZeBOYa3f_YgwaA0+wVXXBjDfCuFurjmTOHzSr2EXmcNWXjg@mail.gmail.com>
In-Reply-To: <CABcZeBOYa3f_YgwaA0+wVXXBjDfCuFurjmTOHzSr2EXmcNWXjg@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
X-Brightmail-Tracker: AAAAAA==
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 08:34:30 -0000

>>In any case, the IRTF Report, IAB Report and RSOC Report could certainly =
be
>>made in the other plenary.
>
>Or omitted entirely, since they are duplicative of data which would be bet=
ter
>communicated in writing.

...and/or use some Internet technology, by producing YouTube report videos,=
 that people can watch whenever they have time :)

Regards,

Christer=

From ole@cisco.com  Wed Aug  3 04:16:06 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3068321F8B6E for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 04:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.792
X-Spam-Level: 
X-Spam-Status: No, score=-102.792 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11p2hQofqZEG for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 04:16:05 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 7F67921F8B6C for <ietf@ietf.org>; Wed,  3 Aug 2011 04:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=892; q=dns/txt; s=iport; t=1312370177; x=1313579777; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=QFS+gmWCzzXwWGUVKGd+l1ACiWXy8BLJLOs1imkAe7E=; b=F8z22dACVx4IpsYgjnE3j0GPxSrL4hUvOWCyuWaAE1O9f6cEpYJRjtVs L8AAznTE4LvwBWMhMlUyTj1iIWh9uCtdGJp/BkP/BL4HcMjwcIWZEeY0U wQ3AxnlzsC1YJpfgl/S1+gAdueQMLpVU6qw/XG2vFcTxMzJusNFbVzyuF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJ4tOU6rRDoJ/2dsb2JhbAA/A6ded4FAAQEBAQMBAQEPAQIBJDQLEAtGJzAGEyKHTqF4AYMcDwGbNYM+gwQEh1qVDYcY
X-IronPort-AV: E=Sophos;i="4.67,309,1309737600";  d="scan'208";a="9184294"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-7.cisco.com with ESMTP; 03 Aug 2011 11:16:16 +0000
Received: from sjc-vpn7-506.cisco.com (sjc-vpn7-506.cisco.com [10.21.145.250]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p73BGFub003004; Wed, 3 Aug 2011 11:16:15 GMT
Date: Wed, 3 Aug 2011 04:16:15 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: RE: "technical" plenary [was: A modest proposal for Friday meeting schedule]
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05851DB6190FF6@ESESSCMS0356.eemea.ericsson.se>
Message-ID: <alpine.OSX.2.01.1108030415020.848@sjc-vpn7-506.cisco.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <20110801233548.GL25922@nsn.com> <4E373C50.9010402@gmail.com>, <CABcZeBOYa3f_YgwaA0+wVXXBjDfCuFurjmTOHzSr2EXmcNWXjg@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05851DB6190FF6@ESESSCMS0356.eemea.ericsson.se>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 11:16:06 -0000

Oh, I can just see it now: YouTube of plenary with bad-attitute 
subtitles....

:-)


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 3 Aug 2011, Christer Holmberg wrote:

> 
> >>In any case, the IRTF Report, IAB Report and RSOC Report could certainly be
> >>made in the other plenary.
> >
> >Or omitted entirely, since they are duplicative of data which would be better
> >communicated in writing.
> 
> ...and/or use some Internet technology, by producing YouTube report 
> videos, that people can watch whenever they have time :)
> 
> Regards,
> 
> Christer
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From hsantos@isdg.net  Wed Aug  3 04:42:31 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 140EC21F8B77 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 04:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.66
X-Spam-Level: 
X-Spam-Status: No, score=-3.66 tagged_above=-999 required=5 tests=[AWL=-1.061,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wB-Y-7qLa5f6 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 04:42:30 -0700 (PDT)
Received: from dkim.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9DFDC21F8B7E for <ietf@ietf.org>; Wed,  3 Aug 2011 04:42:22 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1908; t=1312371750; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=5Mh+MgsNrAItBclxPdqVzgMplaQ=; b=VhucWvoMJltapMYzEhyA rEDJl77mU6E6VEYgcC43BS6WSNxPGvXXBJC1QTVEl6bCnj3AyXJ9I0Pdee5+x1Zx F/WMuFoehxuBvHSxM4cts9y0Pesth4kANSwvXExLUt4BQeHXhW+b6wT9u5nNxXvi DlowoBjmjyDoVqD9mhjxc54=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 07:42:30 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 827235102.33902.2832; Wed, 03 Aug 2011 07:42:30 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 07:38:00 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1798519377.562.7740; Wed, 03 Aug 2011 07:38:00 -0400
Message-ID: <4E393455.6020102@isdg.net>
Date: Wed, 03 Aug 2011 07:43:17 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com>	<4E352A74.6080703@isdg.net>	<773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com>	<201108011141.30549.scott@kitterman.com>	<4E3861F0.7080507@dcrocker.net>	<4E386CF8.5020508@isdg.net> <F5833273385BB34F99288B3648C4F06F13512DF50B@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF50B@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 11:42:31 -0000

Murray S. Kucherawy wrote:

>> We are perfectly aware you never believed in policy, never really
>> acknowledge it, fought hard against its progress. I can respect that
>> position. But I am bit vex as to why you are questioning its existence
>> as an original and still current WG work item.
> 
> Where I come from, personal attacks don't support your 
> position; they degrade your credibility.

And with your personal animosity towards me, I'm sure you will repeat 
this to negate concerns.

I don't view expressing a public recorded oppositional stance as an 
attack.

> The ongoing claims that the working group was guided by sinister 
> designs to benefit from some specific alternate market are simply absurd.

No one stated it was sinister.  That blab always came from your 
description whenever anyone dared to state the obviousness of the 
conflict of interest in the WG.

1) I always stated both security and trust ideas are necessary and 
should of been incorporated. I opposed eliminating author domain 
semantics and security and especially opposed the rewrite and limiting 
the protocol specification to exclusively only 3rd party TRUST Service 
Engine integration out of the box,

2) I illustrated two examples of how unrestricted resigner creating 
mail integration problems, effectively making it impossible for any 
kind of policy to work reliably outside prearranged known communications.

As a DKIM implementor and one of those "sinister" capitalist creating 
products that include allowing a business to create trust services as 
well,  the above has made it very difficult and I see little to no 
payoff in DKIM future - as it currently written in its limited nature 
to only trust and for writing software with no design considerations 
for controlling and restricting resigning.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com






From hallam@gmail.com  Wed Aug  3 05:44:15 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A50D21F8B09 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 05:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hquCu-iuCXXa for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 05:44:14 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7C67D21F8AFC for <ietf@ietf.org>; Wed,  3 Aug 2011 05:44:14 -0700 (PDT)
Received: by qwc23 with SMTP id 23so546256qwc.31 for <ietf@ietf.org>; Wed, 03 Aug 2011 05:44:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=b7hAlBuK3hGIzOIrX1sO1t1wDU222a3no/I2547EtFw=; b=xUh99lL0TTXFUdx6XvKRAdwD23R8vgfp8tkWDBYptl1c4d0/pbWYmdD+0nf9AzUGCw rbyOoSbWu5/uuIuVOfvl3vChkwKImsVfoYYWQS2TLH9Xd5kMgCgv+R9NKnT50i9W5WvX f8BYai48KRG+uE7CI0gzZZCorVHOR7RGnQ/HQ=
Received: by 10.224.198.68 with SMTP id en4mr5509184qab.223.1312375464243; Wed, 03 Aug 2011 05:44:24 -0700 (PDT)
Received: from [10.78.121.106] (mobile-198-228-196-233.mycingular.net [198.228.196.233]) by mx.google.com with ESMTPS id d12sm560691qcd.26.2011.08.03.05.44.19 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 03 Aug 2011 05:44:22 -0700 (PDT)
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <6.2.5.6.2.20110801172353.0696f868@resistor.net> <CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com> <4E38A9CA.4030204@qualcomm.com>
In-Reply-To: <4E38A9CA.4030204@qualcomm.com>
Mime-Version: 1.0 (iPad Mail 8C148)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <039F5C24-25B0-4291-816B-FB1DD68858B1@gmail.com>
X-Mailer: iPad Mail (8C148)
From: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Drafts Submissions cut-off
Date: Wed, 3 Aug 2011 08:55:14 -0400
To: Pete Resnick <presnick@qualcomm.com>
Cc: SM <sm@resistor.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 12:44:15 -0000

Again, perfectly reasonable, but not actually documented as the process.

We write everything else down, why not this?


Sent from my iPad

On Aug 2, 2011, at 21:52, Pete Resnick <presnick@qualcomm.com> wrote:

> On 8/2/11 8:03 PM, Phillip Hallam-Baker wrote:
>> Either don't have a cutoff at all or make it a requirement that all mater=
ials be submitted in advance of the meeting.
>=20
> Personally, I think chairs should have the discretion to allow or disallow=
 discussion of documents submitted at any time, that they should be tougher a=
bout what they disallow, and that they should face the wrath of their WG mem=
bers and their AD if they aren't. Right now, we have a deadline, but also al=
low for special dispensation to let drafts through. If chairs feel that they=
 need *some* deadline written down somewhere in order to push back on things=
, I have an alternate suggestion:
>=20
> Right now, all -00 submissions of WG drafts are gated on chair approval (I=
 believe in an automated fashion). We could simply make the tool gate *all* W=
G submissions from some time before the meeting through the meeting week. Th=
at way, chairs can decide whether they will enforce the deadline and not let=
 the draft through, or make exceptions and let the drafts through. See above=
 statement regarding "wrath" if the chairs abuse this authority in either di=
rection.
>=20
> (If we had the resources, we could make the tool settable on a per-WG basi=
s: One chair could say, "I want to gate all drafts", another could say, "I w=
ant to gate none", and others could put in a date range for gating.)
>=20
> Again, I don't think there needs to be a cutoff or a gating function. Chai=
rs already have the authority to tell folks to go jump in a lake. But I'm no=
t against a tool if chairs feel like they need some sort of "official" pushb=
ack mechanism.
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
>=20

From ajs@anvilwalrusden.com  Wed Aug  3 06:02:18 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FD921F87F0 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 06:02:18 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLTMAom2D8rs for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 06:02:17 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB8C21F85A1 for <ietf@ietf.org>; Wed,  3 Aug 2011 06:02:17 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 760F11ECB41C for <ietf@ietf.org>; Wed,  3 Aug 2011 13:02:29 +0000 (UTC)
Date: Wed, 3 Aug 2011 09:02:27 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Drafts Submissions cut-off
Message-ID: <20110803130227.GE31442@shinkuro.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <6.2.5.6.2.20110801172353.0696f868@resistor.net> <CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com> <4E38A9CA.4030204@qualcomm.com> <039F5C24-25B0-4291-816B-FB1DD68858B1@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <039F5C24-25B0-4291-816B-FB1DD68858B1@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 13:02:18 -0000

On Wed, Aug 03, 2011 at 08:55:14AM -0400, Phillip Hallam-Baker wrote:

> We write everything else down, why not this?

My original objection was to exactly this trend.  I don't believe that
writing everything down is a good idea.  Some things require
judgement, not rules; and if we have moved to the point where we
actually have to use Robert's Rules or some cognate in order to
function because judgement no longer works for this organization, then
I suggest the IETF has outlived its usefulness and ought to be put
down.

I like the submission cut-off because it is a useful forcing function
to get drafts in by a reasonable time before the meeting so that
people can read them.  But I wouldn't argue for it on principled
grounds, and if people really believe we need to do something, I'm in
favour of getting rid of that.  I nevertheless predict that such a
decision will yield less good results than what we have now.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From jari.arkko@piuha.net  Wed Aug  3 06:03:09 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1986B21F8B3B for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 06:03:09 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSD9HhRG5Ocy for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 06:03:08 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 783CA21F8B37 for <ietf@ietf.org>; Wed,  3 Aug 2011 06:03:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D28C22D403; Wed,  3 Aug 2011 16:03:19 +0300 (EEST)
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 uJpIktKGn-mv; Wed,  3 Aug 2011 16:03:19 +0300 (EEST)
Received: from www.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0C97B2CE66; Wed,  3 Aug 2011 16:03:19 +0300 (EEST)
Received: from 87.93.72.13 (SquirrelMail authenticated user jarkko) by www.piuha.net with HTTP; Wed, 3 Aug 2011 16:03:19 +0300
Message-ID: <11f54413f26495d97ab1ff5cf7ac9f9c.squirrel@www.piuha.net>
In-Reply-To: <039F5C24-25B0-4291-816B-FB1DD68858B1@gmail.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <6.2.5.6.2.20110801172353.0696f868@resistor.net> <CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com> <4E38A9CA.4030204@qualcomm.com> <039F5C24-25B0-4291-816B-FB1DD68858B1@gmail.com>
Date: Wed, 3 Aug 2011 16:03:19 +0300
Subject: Re: Drafts Submissions cut-off
From: jari.arkko@piuha.net
To: "Phillip Hallam-Baker" <hallam@gmail.com>
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Pete Resnick <presnick@qualcomm.com>, SM <sm@resistor.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 13:03:09 -0000

By the way, it has been pretty usual practise for me to make an exemption
for drafts needing revision and in the beyond-wg stages. Resolving
directorate/iesg comments, for instance. I did this for some drafts prior
to ietf-81, for instance.

Note that this is a separate issue from the general deadline discussion.
There is no good reason to hold drafts, unless they are discussed in the
meeting. Be aware that you can ask for this from your AD (who in turn
makes a request to secretary).

Jari


From john-ietf@jck.com  Wed Aug  3 06:36:38 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3F4921F8B2A for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 06:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.645
X-Spam-Level: 
X-Spam-Status: No, score=-102.645 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3UxnyCA8q+8q for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 06:36:37 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 8030B21F8B2E for <ietf@ietf.org>; Wed,  3 Aug 2011 06:36:36 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qobck-0001cU-KR; Wed, 03 Aug 2011 09:36:39 -0400
Date: Wed, 03 Aug 2011 09:36:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <A3DA08EB16343C89CD53A26F@PST.JCK.COM>
In-Reply-To: <4E389500.90309@joelhalpern.com>
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu> <12B69DB8-AFDD-4C40-BC9A-0A8158D9F7C0@nostrum.com> <0D43A851-C57B-484F-ADDD-BBD7A412689C@standardstrack.com> <4E343791.7040401@qualcomm.com> <4E3439CE.4030509@joelhalpern.com> <4E36C3E3.6050500@stpeter.im> <E1090BD02A7BD74AA756B06E@PST.JCK.COM> <4E389500.90309@joelhalpern.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: Pete Resnick <presnick@qualcomm.com>, Bradner Scott <sob@harvard.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 13:36:38 -0000

--On Tuesday, August 02, 2011 20:23 -0400 "Joel M. Halpern"
<jmh@joelhalpern.com> wrote:

> With mild apologies, I have retained John's text below
> because, even though I come to a different conclusion, I
> thought it important to retain for now.  If folks choose to
> follow up on this, significant trimming is recommended.

Trimmed :-)

> John, as far as I can tell there are three problems which
> various folks have wanted this document or its predecessor to
> address:
> 1) That the bar for PS is too high
> 2) That not enough documents are advancing up the standards
> track
> 3) That what we do and what we say we do do not match.

I agree with your summary so far.

> Clearly, these problems are related.

That is less clear to me.  While I think that (1) is at least
part of the cause of (2), both of the following seem almost
equally plausible:

	(i) At the time the current model was assembled, IETF
	participation was much more heavily weighted toward
	researchers and others who had the flexibility to be
	able to concentrate on getting things right with
	multiple iterations and gradual advancement.  As the
	Internet has evolved toward an environment in which
	short-term product needs dominate, a larger percentage
	of IETF participants have needs to get a reasonable spec
	agreed on so it can be implemented and deployed, but
	little need to refine and revise unless flaws in the
	specs cause serious and user- or operator- visible
	interoperability problems.
	
	(ii) At the time the current model was assembled, IETF
	specifications tended to be for relatively simple
	protocols with either few options or orthogonal ones
	without complex interactions.  Today, we are seeing far
	more specs with optional variations, options that
	interact in complex ways, profiles for different
	purposes, etc.  We have whole working groups whose
	purpose it is to sort out the operational implications
	of protocols developed in other WGs (and sometimes still
	under development.   In that environment, having
	maturity categories that require an entire complex
	protocol, regardless of profiles or sets of options, to
	be classified into a small range of mutually-exclusive
	sets just makes no sense almost independent of how many
	categories we have.   Whether we can remove obstacles or
	not, we don't have the right incentives in place to get
	people to do things that make no sense to them (or to
	their sponsors).   Indeed, _increasing_ the number of
	categories might help: for example, perhaps we need a
	"base spec and 'mandatory to implement' pieces are fine,
	but we don't know about some of the option sets"
	category.

If some combination of those hypotheses is actually the driving
force behind few specs getting past Proposed, then nothing we do
about getting things into Proposed more easily will make any
difference.  Nor is fussing with the number of maturity levels
likely to have any useful effect.

In addition, (3) appears to me almost completely unconnected
with the other two.  Sure, we don't use annual review and never
have.  And it is definitely unattractive to have rules around
that we don't follow.  I would be a lot happier if we removed or
clarified _every_ rule in our specs that we don't follow (or if
we followed more of them).   But I haven't heard even a claim
that removing a rule that we haven't followed from 2026 would
make it easier to get documents approved as Proposed or that it
would increase, even slightly, the number of documents that are
advanced.

> We could try to adopt a change that would address all three.
> I dobut we would accomplish anything.

ok

> As far as I can tell, this document sensible tries to address
> one of these, namely item 3.  It tries to align what we
> document with what we do.  In order to do so, it also makes a
> change which may help item 2. It may not.

But there is no connection at all.  If we wanted to address item
3, then all it would take is a _really_ short RFC that updated
2026 and said "that provision has never been used and is now
eliminated".  As I indicated in my long note, I can't believe
there would be any controversy about such a document other than
complaints that we were wasting time that could be better spent
in other ways.

Might it help with item 2?  While I can't _prove_ it would not,
I don't recall seeing a single argument, either in the document
drafts or on the list, that justifies even a strong hypothesis
that the existence of a rule that we have never followed has
discouraged even a single specification.   If one thought there
was an interaction of that sort, it would make far more sense
logically to try applying the rule to see what effect that would
actually have.  I'm not suggesting that, if only because I
wonder whether moving RFC 3261, RFC 2616, or RFC 2460 to
Historic on the grounds of non-advancement would make us look
the most ridiculous.

> Now, you can argue that it is taking up energy that should go
> to item 1.   That is not unreasonable.  Except that I consider
> all the proposals I have seen for item 1 to be failures.  They
> fail in different ways, but they all have appeared to me to be
> bad ideas. 

Well, that is interesting. I'd be delighted to discuss some of
those proposals with you, but I don't believe that the community
has discussed any proposals that are intended to make
improvements on item 1 in at least the last half-dozen years.
Some attempts to have such discussions have been ruled out of
order on the grounds that they address a different topic than
draft-housley-two-maturity-levels.  Ones that merely would have
required the IESG to conduct a small-scale experiment have been
ignored.  Suggestions about others have been dealt with by
fairly clear statements that the IESG would not consider them as
individual submissions and that a WG would never be approved.

That may made all of them failures, but, if it does, there are,
IMO, some much more fundamental problems with our processes
than, e.g., whether the annual review rule is being used.

But, more important, I'm not making the argument that this is
"taking up energy that should go to item 1" (even though I
believe that to be true).  I think this document should stand
(or not) on its own content and what it proposes.   But it only
solves item 3 while making much more significant and noticeable
changes --look at its title for starters-- in the area of item
2... with no real justification for believing that it will have
any positive effect on the issue you identify as item 2
whatsoever.

I also believe that, if it is approved, it will be used as a
further excuse to not take up any proposals that might actually
solve blocking problems.  But I consider that an almost-separate
issue as well because, if this would really be effective against
_either_ issue 1 or 2, that would be worth the price.

> As such, we can either do nothing, or take this step that in
> my personal opinion addresses item 3, might turn out to help
> item 2, and does not hurt item 1.

See above.  I think that making a very significant change in the
standards process -- changing the number of maturity levels and
criteria for them certainly is such a change-- requires more
justification for believing it might be effective than "might
turn out to help".  The latter looks too much like
decision-making by throwing pasta at the wall... and using only
a single strand of pasta.

In addition, while I think it unlikely, there is a rational
argument (outlined in my earlier note and notes by others) for
believing that lowering the number of maturity levels and trying
to accomplish maturity level changes without new documents will
increase the pressure to get Proposed Standards just right.
Pressure to get Proposed Standards just right appears to be one
of the primary causes of the high threshold for those documents.
There is actually a stronger argument that this might make item
1 worse than there is that it will make item 2 better.


> I believe I understand your point below that without
> understanding how we ought to address problem 1, it is hard to
> be confident we are not making it worse rather than better.

Thanks,
   john




From suresh.krishnan@ericsson.com  Wed Aug  3 08:05:52 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B777421F8B55 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 08:05:52 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nAvBuvKUkcj for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 08:05:52 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 39A2621F8B51 for <ietf@ietf.org>; Wed,  3 Aug 2011 08:05:52 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p73F60ki026053 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Aug 2011 10:06:02 -0500
Received: from [142.133.10.107] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.31) with Microsoft SMTP Server (TLS) id 8.3.137.0; Wed, 3 Aug 2011 11:06:01 -0400
Message-ID: <4E396339.4080008@ericsson.com>
Date: Wed, 3 Aug 2011 11:03:21 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Last Call:	<draft-gundavelli-v6ops-pmipv6-address-reservations-00.txt> (Reserved IPv6 Interface Identifier for Proxy Mobile IPv6) to	Informational RFC
References: <20110729121436.14048.14658.idtracker@ietfa.amsl.com> <4E32AF70.3080901@gmail.com>
In-Reply-To: <4E32AF70.3080901@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 15:05:52 -0000

Hi Alex,

On 11-07-29 09:02 AM, Alexandru Petrescu wrote:
> I do think that pmipv6 has some issues about how it does mag-mn
> interface.  One solution to one issue may be this reserved iid.
>
> Is this updating the stds track rfc5453 "reserved iids"?

No. It does not. RFC5453 explicitly sets up an IANA registry for setting 
up such IDs. This draft just uses that IANA registry.

Thanks
Suresh

From dhc2@dcrocker.net  Wed Aug  3 08:38:17 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C643221F8B22 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 08:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.358
X-Spam-Level: 
X-Spam-Status: No, score=-6.358 tagged_above=-999 required=5 tests=[AWL=-0.359, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DyCrNNFkBa2j for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 08:38:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 047F121F8B01 for <ietf@ietf.org>; Wed,  3 Aug 2011 08:38:17 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p73FcIte026781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2011 08:38:23 -0700
Message-ID: <4E396B66.60504@dcrocker.net>
Date: Wed, 03 Aug 2011 08:38:14 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: DKIM Signatures now being applied to IETF Email
References: <20110725171748.GA13506@amsl.com><4E2DAF60.8030307@dcrocker.net><4E2FFFDF.2080601@ieca.com><005d01cc4d44$3136eda0$4001a8c0@gateway.2wire.net><4E3288EE.9050201@dcrocker.net><006101cc4dea$2c9bdd40$4001a8c0@gateway.2wire.net>	<CAC4RtVDSHEhcffUx=+Y2vORb1TBmgs=XmGrvJgAc1upo-5SbEQ@mail.gmail.com>	<00ad01cc4ea3$1e06ce20$4001a8c0@gateway.2wire.net><F5833273385BB34F99288B3648C4F06F13512DF4CE@EXCH-C2.corp.cloudmark.com><4E352A74.6080703@isdg.net> <773596F4-6312-4723-97F1-EAEDED6E37F4@guppylake.com> <018601cc50ed$4d6f1ae0$4001a8c0@gateway.2wire.net>
In-Reply-To: <018601cc50ed$4d6f1ae0$4001a8c0@gateway.2wire.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]); Wed, 03 Aug 2011 08:38:24 -0700 (PDT)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 15:38:17 -0000

On 8/2/2011 1:11 AM, t.petch wrote:
> When people have a need, and want a technical solution, and then find that
> what at first sight appeared to be a solution is not one, then they may be
> disappointed, and be critical.  That is human nature.
 >
> When that happens is a time to reflect, to look at the requirements that
> were not met.

Tom, one of the other, preferred characteristics of human nature is to take 
constructive action upon identifying a problem.  So I look forward to seeing 
your proposal and pursuit of a solution to this important problem that DKIM does 
not try to solve.


> And, as I said before, my criticism is of those who have imposed this
> technology on the IETF lists, not of the technology itself.

Indeed.  It really is irresponsible of them to improve the accountability of 
email going out through the IETF.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From warren@kumari.net  Wed Aug  3 09:22:06 2011
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B536121F8BBF for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.134
X-Spam-Level: 
X-Spam-Status: No, score=-102.134 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eiTu183UnRts for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:22:06 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 3724D21F8BD3 for <ietf@ietf.org>; Wed,  3 Aug 2011 09:22:05 -0700 (PDT)
Received: from dhcp-172-19-118-113.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 038E01B416C4 for <ietf@ietf.org>; Wed,  3 Aug 2011 12:22:07 -0400 (EDT)
From: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: subject_prefix on IETF Discuss?
Date: Wed, 3 Aug 2011 12:22:04 -0400
Message-Id: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 16:22:06 -0000

Hi all,

I seem to remember discussions about this a long time ago, but searching =
through archives gets no love...

How do folk feel about having asking for subject_prefix to be set on the =
IETF Discussion List (AKA this one!) - this will prefix mail sent to =
this list with something like "[Discussion]" or "[IETF]" or something =
[0].

Background: I used to just filter this list into a mailbox / folder =
(based upon List-Id:), but then I would forget to read it, so I have =
removed that procmail rule. Having a prefix would make it easier to tell =
at a glance what list the mail is associated with, what it might be =
about, etc. Yes, I *could* just make a procmail rule to munge the =
subject myself, but that seems icky, and solving it for the general case =
(and making Discussions more like the other IETF lists feels better).

W

[0]: Let the bike-shedding on actual prefix used begin...



From dhc2@dcrocker.net  Wed Aug  3 09:35:14 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 429E021F8678 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.638
X-Spam-Level: 
X-Spam-Status: No, score=-6.638 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4PVh5CPJVHH for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:35:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A6FAA21F8686 for <ietf@ietf.org>; Wed,  3 Aug 2011 09:35:13 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p73GZK0q027930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 3 Aug 2011 09:35:25 -0700
Message-ID: <4E3978C4.1060503@dcrocker.net>
Date: Wed, 03 Aug 2011 09:35:16 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
In-Reply-To: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.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]); Wed, 03 Aug 2011 09:35:25 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 16:35:14 -0000

> How do folk feel about having asking for subject_prefix to be set on the IETF Discussion List (AKA this one!) - this will prefix mail sent to this list with something like "[Discussion]" or "[IETF]" or something [0].


+1

The visual cue this convention provides is helpful and it's an extremely 
widespread convention.

[Discussion] could apply to any group, anywhere, whereas  [IETF] nicely 
identifies exactly this list.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From stpeter@stpeter.im  Wed Aug  3 09:36:51 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 251C421F8BF0 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.688
X-Spam-Level: 
X-Spam-Status: No, score=-102.688 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HudOkw6aB8e for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:36:50 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A321221F8BEE for <ietf@ietf.org>; Wed,  3 Aug 2011 09:36:50 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 70BE141309; Wed,  3 Aug 2011 10:38:22 -0600 (MDT)
Message-ID: <4E39792C.2080605@stpeter.im>
Date: Wed, 03 Aug 2011 10:37:00 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E3978C4.1060503@dcrocker.net>
In-Reply-To: <4E3978C4.1060503@dcrocker.net>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Dave CROCKER <dhc2@dcrocker.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 16:36:51 -0000

On 8/3/11 10:35 AM, Dave CROCKER wrote:
> 
>> How do folk feel about having asking for subject_prefix to be set on
>> the IETF Discussion List (AKA this one!) - this will prefix mail sent
>> to this list with something like "[Discussion]" or "[IETF]" or
>> something [0].
> 
> 
> +1
> 
> The visual cue this convention provides is helpful and it's an extremely
> widespread convention.
> 
> [Discussion] could apply to any group, anywhere, whereas  [IETF] nicely
> identifies exactly this list.

Yes please!

/psa

From peter@denic.de  Wed Aug  3 09:40:25 2011
Return-Path: <peter@denic.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC18221F8A23 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:40:25 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4WQMaN5RZZi for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:40:25 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id 5D54721F88A1 for <ietf@ietf.org>; Wed,  3 Aug 2011 09:40:25 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QoeUk-00032Y-Rw; Wed, 03 Aug 2011 18:40:34 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QoeUk-0006me-NU; Wed, 03 Aug 2011 18:40:34 +0200
Date: Wed, 3 Aug 2011 18:40:34 +0200
From: Peter Koch <pk@ISOC.DE>
To: IETF Discussion List <ietf@ietf.org>
Subject: Re: subject_prefix on IETF Discuss?
Message-ID: <20110803164034.GP6118@x27.adm.denic.de>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E3978C4.1060503@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E3978C4.1060503@dcrocker.net>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 16:40:26 -0000

On Wed, Aug 03, 2011 at 09:35:16AM -0700, Dave CROCKER wrote:
> 
> >How do folk feel about having asking for subject_prefix to be set on the 
> >IETF Discussion List (AKA this one!) - this will prefix mail sent to this 
> >list with something like "[Discussion]" or "[IETF]" or something [0].

> The visual cue this convention provides is helpful and it's an extremely 
> widespread convention.

maybe we should eat our own dog food as served in RFC 2919 or,
to touch another popular issue, declare 2919 "Historic"?

-Peter

PS: <http://tools.ietf.org/html/draft-koch-subject-tags-considered-00>

From stpeter@stpeter.im  Wed Aug  3 09:48:39 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1514421F8AF7 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.686
X-Spam-Level: 
X-Spam-Status: No, score=-102.686 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id erdaPAbi-NeR for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:48:38 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A0BDD21F8782 for <ietf@ietf.org>; Wed,  3 Aug 2011 09:48:38 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 46E484137D; Wed,  3 Aug 2011 10:50:10 -0600 (MDT)
Message-ID: <4E397BF0.7030608@stpeter.im>
Date: Wed, 03 Aug 2011 10:48:48 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Peter Koch <pk@ISOC.DE>
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E3978C4.1060503@dcrocker.net> <20110803164034.GP6118@x27.adm.denic.de>
In-Reply-To: <20110803164034.GP6118@x27.adm.denic.de>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 16:48:39 -0000

On 8/3/11 10:40 AM, Peter Koch wrote:

> PS: <http://tools.ietf.org/html/draft-koch-subject-tags-considered-00>

Given that almost all of the WG lists have subject prefixes, it seems
most folks find your arguments less than compelling.

/psa



From dhc2@dcrocker.net  Wed Aug  3 09:56:10 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 075CC21F8BB1 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.636
X-Spam-Level: 
X-Spam-Status: No, score=-6.636 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xg0yeC+SiGcO for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 09:56:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id DF53621F8BBC for <ietf@ietf.org>; Wed,  3 Aug 2011 09:56:08 -0700 (PDT)
Received: from [192.168.1.156] (adsl-67-124-149-98.dsl.pltn13.pacbell.net [67.124.149.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p73GuAbk028395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 3 Aug 2011 09:56:16 -0700
Message-ID: <4E397DA6.9000004@dcrocker.net>
Date: Wed, 03 Aug 2011 09:56:06 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E3978C4.1060503@dcrocker.net> <20110803164034.GP6118@x27.adm.denic.de>
In-Reply-To: <20110803164034.GP6118@x27.adm.denic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 03 Aug 2011 09:56:16 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 16:56:10 -0000

On 8/3/2011 9:40 AM, Peter Koch wrote:
>> The visual cue this convention provides is helpful and it's an extremely
>> widespread convention.
>
> maybe we should eat our own dog food as served in RFC 2919 or,
> to touch another popular issue, declare 2919 "Historic"?


Peter,

That's a rather odd suggestion to make

    *  in a message that conforms to that RFC

    *  with many of us using mail software (such as Thunderbird) that detects 
List-* fields and adapts, such as offering a "Reply List" command when present

So...

    -1.

d/

ps.  Besides its being benign to have redundant indication of list handling, the 
different conventions serve different purposes.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dwm@xpasc.com  Wed Aug  3 10:13:50 2011
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7E721F87C3 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[AWL=-1.394, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x7JSDmxEAv9K for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:13:49 -0700 (PDT)
Received: from mail.xpasc.com (mail.xpasc.com [68.164.244.189]) by ietfa.amsl.com (Postfix) with ESMTP id B2B0E21F87C2 for <ietf@ietf.org>; Wed,  3 Aug 2011 10:13:49 -0700 (PDT)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id A628110008D for <ietf@ietf.org>; Wed,  3 Aug 2011 10:14:02 -0700 (PDT)
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 iz6Urb83he00; Wed, 03 Aug 2011 10:14:02 -0700
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id EBC7310058A for <ietf@ietf.org>; Wed,  3 Aug 2011 10:13:59 -0700 (PDT)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id p73HDw1K017509 for <ietf@ietf.org>; Wed, 3 Aug 2011 10:13:58 -0700
Date: Wed, 3 Aug 2011 10:13:58 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
In-Reply-To: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
Message-ID: <Pine.LNX.4.64.1108031010460.2447@egate.xpasc.com>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Propel-ID: iz6Urb83he00
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:13:50 -0000

On Wed, 3 Aug 2011, Warren Kumari wrote:

> I seem to remember discussions about this a long time ago, but searching
> through archives gets no love...
>
> How do folk feel about having asking for subject_prefix to be set on the
> IETF Discussion List (AKA this one!) - this will prefix mail sent to
> this list with something like "[Discussion]" or "[IETF]" or something
> [0].

I'd REALLY like such a tag ... almost all the other lists I subscribe to
use such a prefix. [IETF] would be my preference. Short is good. I'm
happy to let those who prefer to not have such a prefix setup their
procmail rules to remove it. <-:)

From evnikita2@gmail.com  Wed Aug  3 10:16:43 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE8B521F87C3 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.55
X-Spam-Level: 
X-Spam-Status: No, score=-3.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhcmIC4DmtLR for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:16:43 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0952721F87C5 for <ietf@ietf.org>; Wed,  3 Aug 2011 10:16:42 -0700 (PDT)
Received: by fxe6 with SMTP id 6so1265460fxe.31 for <ietf@ietf.org>; Wed, 03 Aug 2011 10:16:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=cLz5PSSHgiiDXerVeHFo2lvzcBeTaJIU/ZntnpdWipA=; b=bfIonYh6WxqBLN1yohtWKmTE92m6BpQKHqu85i5DNnMWTan+55FUv5+nhuAmtEyBOR i9xSduFlQdUvAVXcKL7iXmZohmEBjOq5cIbPEzU2DBph2MfBRsdU2Guwlvz2tynnGXYI CNPBPkkBLby0WWUXYgmW1sX7y3P+hJ72UFnN8=
Received: by 10.223.161.16 with SMTP id p16mr4173297fax.125.1312391807242; Wed, 03 Aug 2011 10:16:47 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id h22sm647854faa.36.2011.08.03.10.16.44 (version=SSLv3 cipher=OTHER); Wed, 03 Aug 2011 10:16:45 -0700 (PDT)
Message-ID: <4E3982A4.9020307@gmail.com>
Date: Wed, 03 Aug 2011 20:17:24 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <Pine.LNX.4.64.1108031010460.2447@egate.xpasc.com>
In-Reply-To: <Pine.LNX.4.64.1108031010460.2447@egate.xpasc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:16:43 -0000

03.08.2011 20:13, David Morris wrote:
>
> On Wed, 3 Aug 2011, Warren Kumari wrote:
>
>> I seem to remember discussions about this a long time ago, but searching
>> through archives gets no love...
>>
>> How do folk feel about having asking for subject_prefix to be set on the
>> IETF Discussion List (AKA this one!) - this will prefix mail sent to
>> this list with something like "[Discussion]" or "[IETF]" or something
>> [0].
> I'd REALLY like such a tag ... almost all the other lists I subscribe to
> use such a prefix. [IETF] would be my preference. Short is good. I'm
> happy to let those who prefer to not have such a prefix setup their
> procmail rules to remove it.<-:)

+1.  I approve of such idea.  Mykyta

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


From R.E.Sonneveld@sonnection.nl  Wed Aug  3 10:17:25 2011
Return-Path: <R.E.Sonneveld@sonnection.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BDFA21F8865 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.349
X-Spam-Level: 
X-Spam-Status: No, score=-4.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AYhtXdGhdaI8 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:17:24 -0700 (PDT)
Received: from mx20.mailtransaction.com (mx20.mailtransaction.com [78.46.16.213]) by ietfa.amsl.com (Postfix) with ESMTP id 54C6121F87C5 for <ietf@ietf.org>; Wed,  3 Aug 2011 10:17:24 -0700 (PDT)
Received: from process-dkim-sign-daemon.helium.mailtransaction.com by helium.mailtransaction.com (Oracle Communications Messaging Exchange Server 7u4-18.01 64bit (built Jul 15 2010)) id <0LPD002003SHP100@helium.mailtransaction.com>; Wed, 03 Aug 2011 19:17:24 +0200 (CEST)
Received: from lion.sonnection.nl (lion.sonnection.nl [80.127.135.138]) by helium.mailtransaction.com (Oracle Communications Messaging Exchange Server 7u4-18.01 64bit (built Jul 15 2010)) with ESMTP id <0LPD00010410DH00@helium.mailtransaction.com>; Wed, 03 Aug 2011 19:17:24 +0200 (CEST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from a80-127-135-139.adsl.xs4all.nl (a80-127-135-139.adsl.xs4all.nl [80.127.135.139]) by lion.sonnection.nl (Sun Java(tm) System Messaging Server 7.3-11.01 32bit (built Sep 1 2009)) with ESMTPA id <0LPD00H05410G500@lion.sonnection.nl> for ietf@ietf.org; Wed, 03 Aug 2011 19:17:24 +0200 (CEST)
Message-id: <4E398376.5040603@sonnection.nl>
Date: Wed, 03 Aug 2011 19:20:54 +0200
From: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
To: David Morris <dwm@xpasc.com>
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <Pine.LNX.4.64.1108031010460.2447@egate.xpasc.com>
In-reply-to: <Pine.LNX.4.64.1108031010460.2447@egate.xpasc.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sonnection.nl; s=2009;  t=1312391844; bh=MBtCLEv3CgkeHLnFNf2ZAN59qtARJ9G4mV2mzsF6WE4=;  h=MIME-version:Content-transfer-encoding:Content-type:Message-id: Date:From:To:Cc:Subject:References:In-reply-to; b=RtEB0VYk5mups9MLxq1bwMKSpHOK9aD5V6nN0HItnH19VIQ6h2UCWR5Sg1XXatT1O DLR82FlTwP8qhTAhla106gnEL+97LEDNIsZrILXTPw0OgYF1+/WDNYcA67QhHDE8Qs +xqmJTjQE26dhvGcdQgx+/fdlG+pCAUUGB99VrYc=
X-DKIM: OpenDKIM Filter v2.1.3 helium.mailtransaction.com 0LPD002003SHP100
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:17:25 -0000

On 8/3/11 7:13 PM, David Morris wrote:
>
> On Wed, 3 Aug 2011, Warren Kumari wrote:
>
>> I seem to remember discussions about this a long time ago, but searching
>> through archives gets no love...
>>
>> How do folk feel about having asking for subject_prefix to be set on the
>> IETF Discussion List (AKA this one!) - this will prefix mail sent to
>> this list with something like "[Discussion]" or "[IETF]" or something
>> [0].
> I'd REALLY like such a tag ... almost all the other lists I subscribe to
> use such a prefix. [IETF] would be my preference. Short is good. I'm
> happy to let those who prefer to not have such a prefix setup their
> procmail rules to remove it.<-:)

s/procmail rules/sieve filter/

:-)

/rolf


From mcr@sandelman.ca  Wed Aug  3 10:51:31 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA47821F8AEE for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.552
X-Spam-Level: 
X-Spam-Status: No, score=-1.552 tagged_above=-999 required=5 tests=[AWL=0.402,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vEZUN6XqndpR for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:51:31 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id A81D721F8AA8 for <ietf@ietf.org>; Wed,  3 Aug 2011 10:51:30 -0700 (PDT)
Received: from marajade.sandelman.ca (wlan204.sandelman.ca [209.87.252.204]) by relay.sandelman.ca (Postfix) with ESMTPS id E8D4934171 for <ietf@ietf.org>; Wed,  3 Aug 2011 13:50:51 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 9C19D98411 for <ietf@ietf.org>; Wed,  3 Aug 2011 13:51:29 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: is IETF trying to do too much?
In-Reply-To: <D992EEF2-5DAE-4884-951E-8B8CD370657C@network-heretics.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <D992EEF2-5DAE-4884-951E-8B8CD370657C@network-heretics.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Wed, 03 Aug 2011 13:51:29 -0400
Message-ID: <24260.1312393889@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:51:31 -0000

>>>>> "Keith" == Keith Moore <moore@network-heretics.com> writes:
    Keith> I keep going to working group meetings that have overflowing
    Keith> agendas of mostly presentations, with little time for
    Keith> discussion. 

+1

And chairs, please don't tell me to take it "offline" --- the meeting is
offline.  The list is "online".  The purpose of the meeting is to
discuss, not for "presenters" to "present".

I understand that for some organizations, unless a participant does a
presentation, they get no funding to travel.  Not my problem.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From tglassey@earthlink.net  Wed Aug  3 10:55:09 2011
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 845D69E8002 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:55:09 -0700 (PDT)
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.785, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3jfplEzu3eGC for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:55:09 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 010B59E8001 for <ietf@ietf.org>; Wed,  3 Aug 2011 10:55:08 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Kvk7O2tAYaWXPb2Pc8xiIlbZGAe6mccYYwjgSy2tG0RxlkZvTmUYl40TJdkxmBH/; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [207.111.209.5] (helo=[192.168.1.100]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Qoff7-0005bD-5X for ietf@ietf.org; Wed, 03 Aug 2011 13:55:21 -0400
Message-ID: <4E398BA5.7020508@earthlink.net>
Date: Wed, 03 Aug 2011 10:55:49 -0700
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>	<4E3978C4.1060503@dcrocker.net> <20110803164034.GP6118@x27.adm.denic.de>
In-Reply-To: <20110803164034.GP6118@x27.adm.denic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79c21a6de766489dd3708a59abb3418e2d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.111.209.5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:55:09 -0000

On 8/3/2011 9:40 AM, Peter Koch wrote:
> On Wed, Aug 03, 2011 at 09:35:16AM -0700, Dave CROCKER wrote:
>>> How do folk feel about having asking for subject_prefix to be set on the
>>> IETF Discussion List (AKA this one!) - this will prefix mail sent to this
>>> list with something like "[Discussion]" or "[IETF]" or something [0].
>> The visual cue this convention provides is helpful and it's an extremely
>> widespread convention.
This would allow the IETF mailers to identify and for the rest of us to 
better setup SUBJECT Filters for our mailing so this makes sense and is 
an easy fix which has been requested several times over the last couple 
of years.

todd
> maybe we should eat our own dog food as served in RFC 2919 or,
> to touch another popular issue, declare 2919 "Historic"?
>
> -Peter
>
> PS:<http://tools.ietf.org/html/draft-koch-subject-tags-considered-00>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


-- 
Todd S. Glassey
This is from my personal email account and any materials from this account come with personal disclaimers.

Further I OPT OUT of any and all commercial emailings.


From ned+ietf@mauve.mrochek.com  Wed Aug  3 10:57:56 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1B5C21F85B9 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:57:56 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cFZK5UPg0WyU for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:57:56 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 25D3D21F85B1 for <ietf@ietf.org>; Wed,  3 Aug 2011 10:57:56 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4ET4G0ARK00XHUW@mauve.mrochek.com> for ietf@ietf.org; Wed, 3 Aug 2011 10:57:12 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 3 Aug 2011 10:57:05 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4ET4COJYS00VHKR@mauve.mrochek.com>
Date: Wed, 03 Aug 2011 10:53:08 -0700 (PDT)
Subject: Re: subject_prefix on IETF Discuss?
In-reply-to: "Your message dated Wed, 03 Aug 2011 18:40:34 +0200" <20110803164034.GP6118@x27.adm.denic.de>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E3978C4.1060503@dcrocker.net> <20110803164034.GP6118@x27.adm.denic.de>
To: Peter Koch <pk@ISOC.DE>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1312394173; i=@mrochek.com; bh=SNEMAtMOzspZb1losW0I4wQIrMOtLxaPS+4lDcPue0k=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=MqJA5cYe2CERCxjFF2D+MwaeL2CazdDFefJH6aqmqnnO7cd8dRF2wxV0ui92XJ//T +ExwomcuAkkeov+Z5SL0b99S/QaizvEo4OANVu8xGa+cDkwysh9VlIIU+rOPN5JPP+ 5t/rtSY2odeGrqgPFtDBHp9mINwWZRZI5hfeR/y8=
Cc: IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:57:56 -0000

> On Wed, Aug 03, 2011 at 09:35:16AM -0700, Dave CROCKER wrote:
> >
> > >How do folk feel about having asking for subject_prefix to be set on the
> > >IETF Discussion List (AKA this one!) - this will prefix mail sent to this
> > >list with something like "[Discussion]" or "[IETF]" or something [0].

> > The visual cue this convention provides is helpful and it's an extremely
> > widespread convention.

> maybe we should eat our own dog food as served in RFC 2919 or,
> to touch another popular issue, declare 2919 "Historic"?

The IETF list already inserts the all the proper list- headers:

 List-Id: IETF-Discussion <ietf.ietf.org>
 List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>,
  <mailto:ietf-request@ietf.org?subject=unsubscribe>
 List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
 List-Post: <mailto:ietf@ietf.org>
 List-Help: <mailto:ietf-request@ietf.org?subject=help> 
 List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
  <mailto:ietf-request@ietf.org?subject=subscribe>

It's all I need for sorting and, for that matter, I can trivially set up rules
to add the [ietf] or whatever tag myself if I prefer that. As others have
pointed out, we even have a standard for doing this stuff.

OTOH, I can also remove the [ietf] tag if the list starts putting it in there.
So count me as mildly disliking this proposal.

> -Peter

> PS: <http://tools.ietf.org/html/draft-koch-subject-tags-considered-00>

Pretty much agree with the points raised in this draft.

				Ned

From tglassey@earthlink.net  Wed Aug  3 10:58:17 2011
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA919E800C for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.332
X-Spam-Level: 
X-Spam-Status: No, score=-3.332 tagged_above=-999 required=5 tests=[AWL=-0.733, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nb1ibsUt6ngY for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:58:16 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 5991721F8610 for <ietf@ietf.org>; Wed,  3 Aug 2011 10:58:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=dXCl8b/ZS9IUqYqKykXsLL9et5aG3AbG1bZE6PmZmDLXw+JVQ9673CdxQhB3uOZ2; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [207.111.209.5] (helo=[192.168.1.100]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Qofi8-0006BT-MM for ietf@ietf.org; Wed, 03 Aug 2011 13:58:28 -0400
Message-ID: <4E398C61.8000204@earthlink.net>
Date: Wed, 03 Aug 2011 10:58:57 -0700
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Drafts Submissions cut-off
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com>	<6.2.5.6.2.20110801172353.0696f868@resistor.net>	<CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com> <4E38A9CA.4030204@qualcomm.com>
In-Reply-To: <4E38A9CA.4030204@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79825d0c37deac3cb270f49b0e73ee685a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.111.209.5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:58:17 -0000

On 8/2/2011 6:52 PM, Pete Resnick wrote:
> On 8/2/11 8:03 PM, Phillip Hallam-Baker wrote:
>> Either don't have a cutoff at all or make it a requirement that all 
>> materials be submitted in advance of the meeting.
>
> Personally, I think chairs should have the discretion to allow or 
> disallow discussion of documents submitted at any time, that they 
> should be tougher about what they disallow, and that they should face 
> the wrath of their WG members and their AD if they aren't. Right now, 
> we have a deadline, but also allow for special dispensation to let 
> drafts through. 
Then the Chair or the WG Management becomes the controller of the actual 
vetting process and what the content of the standard is, and that 
violates the Fair and Open mindset again. The Chair of the WG is the 
facilitator of the groups operations and nothing else.

> If chairs feel that they need *some* deadline written down somewhere 
> in order to push back on things, I have an alternate suggestion:
>
> Right now, all -00 submissions of WG drafts are gated on chair 
> approval (I believe in an automated fashion). We could simply make the 
> tool gate *all* WG submissions from some time before the meeting 
> through the meeting week. That way, chairs can decide whether they 
> will enforce the deadline and not let the draft through, or make 
> exceptions and let the drafts through. See above statement regarding 
> "wrath" if the chairs abuse this authority in either direction.
>
> (If we had the resources, we could make the tool settable on a per-WG 
> basis: One chair could say, "I want to gate all drafts", another could 
> say, "I want to gate none", and others could put in a date range for 
> gating.)
>
> Again, I don't think there needs to be a cutoff or a gating function. 
> Chairs already have the authority to tell folks to go jump in a lake. 
> But I'm not against a tool if chairs feel like they need some sort of 
> "official" pushback mechanism.
>
> pr
>


-- 
Todd S. Glassey
This is from my personal email account and any materials from this account come with personal disclaimers.

Further I OPT OUT of any and all commercial emailings.


From mcr@sandelman.ca  Wed Aug  3 10:58:34 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F09A09E800F for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level: 
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qgWG2ymgpXzE for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 10:58:34 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 585599E800A for <ietf@ietf.org>; Wed,  3 Aug 2011 10:58:34 -0700 (PDT)
Received: from marajade.sandelman.ca (wlan204.sandelman.ca [209.87.252.204]) by relay.sandelman.ca (Postfix) with ESMTPS id AD50C341EB; Wed,  3 Aug 2011 13:58:23 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 8C75398411; Wed,  3 Aug 2011 13:59:01 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Drafts Submissions cut-off
In-Reply-To: <20110801185545.GG22542@shinkuro.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Wed, 03 Aug 2011 13:59:01 -0400
Message-ID: <25311.1312394341@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 17:58:35 -0000

>>>>> "Andrew" == Andrew Sullivan <ajs@anvilwalrusden.com> writes:
    >> I suggest that this is a sub-optimal state of affairs. I see two solutions:
    >> 
    >> 1) Codify the requirement that materials to be discussed at the meeting must
    >> be submitted before the cut-off and that submissions made during meetings
    >> are strictly limited to revisions occurring after and between WG sessions.
    >> [Except in exceptional circumstances with AD approval]
    >> 
    >> 2) Eliminate the 2 week cut off completely.

    Andrew> Speaking as a WG chair but only for myself, I am opposed to either of
    Andrew> these two options.

    Andrew> (1) makes it impossible for Chairs to say, "We had a really good
    Andrew> discussion between the cut-off and the queue re-opening.  The editors
    Andrew> think they got it; please check the new text against the
    Andrew> discussion

Well, if the discussion (on the mailing list) was so good, then the
number of changes to the document should be very precise, and should of
course, be in an email on the mailing list, right?

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From petithug@acm.org  Wed Aug  3 11:16:47 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D60C021F8A36 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1Un4CpyJcHn for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:16:46 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id CF0A121F8A23 for <ietf@ietf.org>; Wed,  3 Aug 2011 11:16:46 -0700 (PDT)
Received: from [IPv6:2001:55c:4c15:5f80:a800:4ff:fe00:a04] (unknown [IPv6:2001:55c:4c15:5f80:a800:4ff:fe00:a04]) by implementers.org (Postfix) with ESMTPS id B7FFF202C8; Wed,  3 Aug 2011 20:14:05 +0200 (CEST)
Message-ID: <4E399097.4080409@acm.org>
Date: Wed, 03 Aug 2011 11:16:55 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: is IETF trying to do too much?
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com>	<E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org>	<D992EEF2-5DAE-4884-951E-8B8CD370657C@network-heretics.com> <24260.1312393889@marajade.sandelman.ca>
In-Reply-To: <24260.1312393889@marajade.sandelman.ca>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:16:47 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/03/2011 10:51 AM, Michael Richardson wrote:
> 
>>>>>> "Keith" == Keith Moore <moore@network-heretics.com> writes:
>     Keith> I keep going to working group meetings that have overflowing
>     Keith> agendas of mostly presentations, with little time for
>     Keith> discussion. 
> 
> +1
> 
> And chairs, please don't tell me to take it "offline" --- the meeting is
> offline.  The list is "online".  The purpose of the meeting is to
> discuss, not for "presenters" to "present".

I completely agree with this, but I would point out that there is some barriers
to having discussions during the meeting.  I went to one session where the I-D
was updated just before the presentation and the slides were not available
(that's an extreme case, but it's not the first time it happened).  I would have
things to discuss about this presentation if I had a chance to read it and think
a bit about it.

In my opinion, the cut-off as it is is fine for I-Ds that will be presented,
chairs should not accept requests for slots without a first draft of the
presentation, a WG session without agenda on the Saturday should be canceled and
chairs should upload the presentations as soon they receive them.

I personally would like to switch to the Tufte style, (i.e. uploading a
printout, which can also be distributed to people before the meeting in printed
form, and having *only* a discussion), but I am not sure how people will react.

> 
> I understand that for some organizations, unless a participant does a
> presentation, they get no funding to travel.  Not my problem.
> 


- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk45kJUACgkQ9RoMZyVa61enngCghnXLkseUPCv55TQGhUMUcyRK
Dz8An3psJdYaPdiXAZDTRm1gezts3IjY
=18Fh
-----END PGP SIGNATURE-----

From johnl@iecc.com  Wed Aug  3 11:21:34 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A18B21F8549 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.593
X-Spam-Level: 
X-Spam-Status: No, score=-110.593 tagged_above=-999 required=5 tests=[AWL=0.606, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkHHOV5AEjQp for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:21:34 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id D7E7721F842D for <ietf@ietf.org>; Wed,  3 Aug 2011 11:21:33 -0700 (PDT)
Received: (qmail 32778 invoked from network); 3 Aug 2011 18:21:45 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 3 Aug 2011 18:21:45 -0000
Received: (qmail 26225 invoked from network); 3 Aug 2011 18:21:45 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Aug 2011 18:21:45 -0000
Date: 3 Aug 2011 18:21:23 -0000
Message-ID: <20110803182123.95411.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
In-Reply-To: <4E398376.5040603@sonnection.nl>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:21:34 -0000

>> happy to let those who prefer to not have such a prefix setup their
>> procmail rules to remove it.<-:)

Gee, I was about to say I was happy for people who want a subject tag
to add one using procmail or whatever.

I'm not unalterably opposed to subject tags, but I believe that the
IETF's dogfood is of the List-ID: flavor.

R's,
John

From ajs@anvilwalrusden.com  Wed Aug  3 11:22:23 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF2B21F842D for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:22:23 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+T3SF0ZMN-x for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:22:22 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 620BE21F8A70 for <ietf@ietf.org>; Wed,  3 Aug 2011 11:22:22 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 94B611ECB41C for <ietf@ietf.org>; Wed,  3 Aug 2011 18:22:34 +0000 (UTC)
Date: Wed, 3 Aug 2011 14:22:32 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Drafts Submissions cut-off
Message-ID: <20110803182231.GI31442@shinkuro.com>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com> <20110801185545.GG22542@shinkuro.com> <25311.1312394341@marajade.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25311.1312394341@marajade.sandelman.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:22:23 -0000

On Wed, Aug 03, 2011 at 01:59:01PM -0400, Michael Richardson wrote:
 
> Well, if the discussion (on the mailing list) was so good, then the
> number of changes to the document should be very precise, and should of
> course, be in an email on the mailing list, right?

Not necessarily.  Especially in the sorts of cases I'm thinking about,
one sometimes sees two or three different proposals for text, general
kicking around of large issues, and so on.  It's the editors'
responsibility to synthesise that input and come up with final text
that reflects the views of the WG.  The text might have gone to the
list before being incorporated, but might as easily have been put into
the draft where it was needed, and the list sent a pointer.

In case it wasn't clear, I'm really only thinking of the sort of
large-scale changes or discussions that will sometimes affect drafts,
typically when a major substantive issue (like of principle) has to be
dealt with.  Small and narrowly focussed issues can almost always be
worked out on list.  But if we only ever had issues that could be
worked out on list, then we wouldn't need to have IETF meetings at
all.

If there's some progress in the sort of large issue of this sort, I
want chairs to have the freedom to include that progress in their
consideration.  (Indeed, there's an argument to be made that the
particular irritant that kicked off this discussion is exactly that
sort of case, although we seem to be thrashing it out on the list
anyway.)  I know we can all think of 20 minute presentations 15 of
which were details of the entire history of a WG draft; I don't
believe that is as valuable as using in-person time to hash out the
large problems facing a WG, and if there is late input to the latter
class of discussion I'm all for including it.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From stpeter@stpeter.im  Wed Aug  3 11:28:18 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87D421F8906 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.682
X-Spam-Level: 
X-Spam-Status: No, score=-102.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ii+VVl1aHjch for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:28:18 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 44A0D21F86D8 for <ietf@ietf.org>; Wed,  3 Aug 2011 11:28:17 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 64F914137E; Wed,  3 Aug 2011 12:29:51 -0600 (MDT)
Message-ID: <4E39934D.7050709@stpeter.im>
Date: Wed, 03 Aug 2011 12:28:29 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: subject_prefix on IETF Discuss?
References: <20110803182123.95411.qmail@joyce.lan>
In-Reply-To: <20110803182123.95411.qmail@joyce.lan>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:28:18 -0000

On 8/3/11 12:21 PM, John Levine wrote:
>>> happy to let those who prefer to not have such a prefix setup their
>>> procmail rules to remove it.<-:)
> 
> Gee, I was about to say I was happy for people who want a subject tag
> to add one using procmail or whatever.
> 
> I'm not unalterably opposed to subject tags, but I believe that the
> IETF's dogfood is of the List-ID: flavor.

Which WG list do you suggest should be the guinea pig? Or shall we
change them all at once to remove the dreaded subject prefix? :)

/psa


From mail@sabahattin-gucukoglu.com  Wed Aug  3 11:44:12 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9209111E808C for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.19
X-Spam-Level: 
X-Spam-Status: No, score=0.19 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzHxqoHTCpxs for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:44:12 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by ietfa.amsl.com (Postfix) with ESMTP id ADC4A11E8088 for <ietf@ietf.org>; Wed,  3 Aug 2011 11:44:11 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:43456) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S394FB> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Wed, 3 Aug 2011 19:44:22 +0100
Received: from [172.20.10.2] (178.243.26.6) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Wed, 03 Aug 2011 19:44:20 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: subject_prefix on IETF Discuss?
In-Reply-To: <20110803182123.95411.qmail@joyce.lan>
Date: Wed, 3 Aug 2011 21:44:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E313B16-E2ED-4836-8685-D2BC5A6DC42F@sabahattin-gucukoglu.com>
References: <20110803182123.95411.qmail@joyce.lan>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1314989062.e92cff@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:44:12 -0000

On 3 Aug 2011, at 21:21, John Levine wrote:
>>> happy to let those who prefer to not have such a prefix setup their
>>> procmail rules to remove it.<-:)
>=20
> Gee, I was about to say I was happy for people who want a subject tag
> to add one using procmail or whatever.
>=20
> I'm not unalterably opposed to subject tags, but I believe that the
> IETF's dogfood is of the List-ID: flavor.

Yes.  It follows the same construction, and rationale, of not messing =
around with the Reply-To: field, when enough information is available in =
list software-specific headers to build whatever user indications or =
reply functionality is required.

But I do understand people's desire of these sorts of tags, and I know =
for a fact that many commonly-used UAs simply have neither the filtering =
nor display capabilities to resist them.  So I would not oppose a =
general motion to make this change.  It's one less nice thing about the =
ietf list, though.

-1 +/- 0.25

Cheers,
Sabahattin

From johnl@iecc.com  Wed Aug  3 11:47:28 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1BE911E80D0 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tjMCSXWxW3FX for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 11:47:28 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id D3BED11E80CF for <ietf@ietf.org>; Wed,  3 Aug 2011 11:47:20 -0700 (PDT)
Received: (qmail 32982 invoked from network); 3 Aug 2011 18:47:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=80d5.4e3997c4.k1108; bh=DeeEW2lffQ5mA0uBdqdGWnVW9oZIimq9D0/kn71Jf2M=; b=F/cQPisjNWKC9qhz3r0ZOjvpglE7A6uwUFwRPLOS+XnSvUWPU07e0eJM1WZ8N99q+jDxSYTlHyxGAJ53/342l4F0pUgz2GwvLoV3QtcQ2u4EZ2uZWKftnP7sHDqfu5/Ebc78KBaor+cL1v9q7oyInTIgL04cSJvuTFwcGBcw+yg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 3 Aug 2011 18:47:10 -0000
Date: 3 Aug 2011 14:47:32 -0400
Message-ID: <alpine.BSF.2.00.1108031441480.98477@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Peter Saint-Andre" <stpeter@stpeter.im>
Subject: Re: subject_prefix on IETF Discuss?
In-Reply-To: <4E39934D.7050709@stpeter.im>
References: <20110803182123.95411.qmail@joyce.lan> <4E39934D.7050709@stpeter.im>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:47:28 -0000

>> I'm not unalterably opposed to subject tags, but I believe that the
>> IETF's dogfood is of the List-ID: flavor.
>
> Which WG list do you suggest should be the guinea pig? Or shall we
> change them all at once to remove the dreaded subject prefix? :)

I said I'm not unalterably opposed.  My advice would be to leave well 
enough alone.

If the IETF used a better list manager, the subject tag would be a 
per-user option, but noooo ...

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 randy_presuhn@mindspring.com  Wed Aug  3 12:18:48 2011
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D7C21F8AFA for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.362
X-Spam-Level: 
X-Spam-Status: No, score=-102.362 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id McJT+7-foeKF for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:18:47 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 764CB21F8AF5 for <ietf@ietf.org>; Wed,  3 Aug 2011 12:18:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=AznX8eKXBGHxArUYoU81zRRAdECYfeC3U9v0wMP2RUTfNNy3kKvXxftJjPZyaDCZ; 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.55.172.135] (helo=oemcomputer) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Qogxw-0002Sz-96 for ietf@ietf.org; Wed, 03 Aug 2011 15:18:52 -0400
Message-ID: <00e701cc5213$06b3ba80$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <CAMm+Lwic08qbAiLjhAygB3wJd7GJVvu-wYeabWB0XkdiamtDaA@mail.gmail.com><6.2.5.6.2.20110801172353.0696f868@resistor.net><CAMm+Lwj=HWRh_1408_geR+6E5ZPwuGPxsG3m7UEvN4rpvXp7JQ@mail.gmail.com><4E38A9CA.4030204@qualcomm.com><039F5C24-25B0-4291-816B-FB1DD68858B1@gmail.com> <20110803130227.GE31442@shinkuro.com>
Subject: Re: Drafts Submissions cut-off
Date: Wed, 3 Aug 2011 12:24:54 -0700
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8887f779e183b2ee28831c1211922443a88753e17e114bcd6c6350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.55.172.135
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 19:18:48 -0000

Hi -

> From: "Andrew Sullivan" <ajs@anvilwalrusden.com>
> To: <ietf@ietf.org>
> Sent: Wednesday, August 03, 2011 6:02 AM
> Subject: Re: Drafts Submissions cut-off
...
> I like the submission cut-off because it is a useful forcing function
> to get drafts in by a reasonable time before the meeting so that
> people can read them.  But I wouldn't argue for it on principled
> grounds, and if people really believe we need to do something, I'm in
> favour of getting rid of that.  I nevertheless predict that such a
> decision will yield less good results than what we have now.

Other, less contrived "forcing functions" are possible.
For example, I know of at least one WG chair who insisted on
including links in meeting agendas to the the exact versions of the
drafts to be discussed.  This caused the agenda posting cutoff
to become the effective deadline.  This is also consistent with
the expressed goal of giving chairs some flexibility.

But we don't need more rules to practice this!  It would not bother
me at all if the two-week cutoff were eliminated.  If anything, it
would encourage chairs to be more precise in their meeting agendas.

Randy


From mrex@sap.com  Wed Aug  3 12:26:32 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC32B21F8B42 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:26:32 -0700 (PDT)
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.290,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NuSOecyeUth0 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:26:32 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2F10321F8B39 for <ietf@ietf.org>; Wed,  3 Aug 2011 12:26:32 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p73JQe6f008661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Aug 2011 21:26:40 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108031926.p73JQdHj019455@fs4113.wdf.sap.corp>
Subject: Re: subject_prefix on IETF Discuss?
To: stpeter@stpeter.im (Peter Saint-Andre)
Date: Wed, 3 Aug 2011 21:26:39 +0200 (MEST)
In-Reply-To: <4E39934D.7050709@stpeter.im> from "Peter Saint-Andre" at Aug 3, 11 12:28:29 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: johnl@iecc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 19:26:33 -0000

Peter Saint-Andre wrote:
> 
> John Levine wrote:
> > 
> > I'm not unalterably opposed to subject tags, but I believe that the
> > IETF's dogfood is of the List-ID: flavor.
> 
> Which WG list do you suggest should be the guinea pig? Or shall we
> change them all at once to remove the dreaded subject prefix? :)

What exactly are you discussing?  List-Id: is present on this list
already, and the WG mailing lists I'm subscribed to have both,
List-Id: and subject_prefix.

subject_prefix will work even with very ancient MUAs, such as the
one I use, so I'm OK.  But the subject_prefix does not scale well
when multiple IETF mailings lists are CC-ed and discussion ensues
(replying to all lists).

Will a subject_prefix confuse MUAs that support "threading" for
cross-posted discussions?

-Martin

From housley@vigilsec.com  Wed Aug  3 12:28:18 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C17F5E8002 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:28:18 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nthJDidPSuw1 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:28:17 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 991A9228006 for <ietf@ietf.org>; Wed,  3 Aug 2011 12:28:17 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 92E89F2412A; Wed,  3 Aug 2011 15:28:37 -0400 (EDT)
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 EPO5DmgIKr3Z; Wed,  3 Aug 2011 15:28:26 -0400 (EDT)
Received: from [192.168.2.101] (pool-96-241-176-45.washdc.fios.verizon.net [96.241.176.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D5D48F24134; Wed,  3 Aug 2011 15:28:36 -0400 (EDT)
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20110728234859.075cb888@resistor.net>
Date: Wed, 3 Aug 2011 15:28:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 19:28:18 -0000

SM:

> =46rom Section 2.1:
>=20
> "no existing published requirements are relaxed".
>=20
> Are these published requirements BCPs?

Yes.


> =46rom Section 2.2:
>=20
>  'This maturity level is a merger of Draft Standard and Standard as
>   specified in RFC 2026 [1].  The chosen name avoids confusion between
>   "Draft Standard" and "Internet-Draft".'
>=20
> Shouldn't that be "Internet Standard" instead of "Standard"?

Look at RFC 2026.  The three level defined there are Proposed Standard, =
Draft Standard, and Standard.

The draft-housley-two-maturity-levels proposes two levels: Proposed =
Standard and Internet Standard.


>   "The request for reclassification is sent to the IESG along with an
>    explanation of how the criteria have been met.
>    The criteria are:
>=20
>   (1) There are at least two independent interoperating =
implementations
>       with widespread deployment and successful operational =
experience.
>=20
>   (2) There are no errata against the specification that would cause a
>       new implementation to fail to interoperate with deployed ones.
>=20
>   (3) There are no unused features in the specification that greatly
>       increase implementation complexity."
>=20
> The document that has been the subject of innumerable messages =
highlights how difficult it can be to reclassify a RFC.  Moreover, it =
amplified the divide between application folks and operators.  The IESG =
could have used the review clause from RFC 2026 and:
>=20
>  (i)  requested an implementation report from the people in favor of =
the
>       proposed standard; and
>=20
>  (ii) a statement about deployment to determine whether there are =
operational
>       issues that have to be addressed.
>=20
> I don't know whether application folks and operators agree that =
cross-area requires mutual understanding.
>=20
> The creation of interoperable protocol implementations requires clear =
specifications.  Interoperability does not mean that the protocol would =
not have unintended effects on the network.  That is where operational =
experience comes in.  It can serve as valuable input to improve a =
specification.  For what it is worth, there approximately 75 =
implementation reports have been submitted since 1996.

I am well aware of the implementation reports.  The premise here is that =
the protocol specification is "good enough" there are at least two =
interoperable implementations and the protocol is deployed widely.  The =
implementation report would become optional.


> A two-step maturity level folds the two different classes of issues =
into one.  Quoting RFC 5657, which this draft unfortunately does not =
reference:
>=20
>  "Moving documents along the standards track can be an important =
signal
>   to the user and implementor communities, and the process of
>   submitting a standard for advancement can help improve that standard
>   or the quality of implementations that participate."
>=20
> During a discussion on another mailing list, it has been mentioned =
that such an effort has a cost.  Lumping all the issues together can =
only increase that cost.

People are not doing many implementation reports.  As you say above, =
there are only about 75 of them.  How many protocols are documented in =
RFCs?  That is a very low percentage in my view.

So, I see the cost quite differently.  Most protocols are published as =
Proposed Standards, and they are never advanced.  I'm seeking a process =
where implementation and deployment experience actually improves the =
protocol specifications.  Today, that rarely happens, and when it does, =
the document recycles at Proposed Standard and the reader does not know =
whether it happened or not.


> Strangely, this draft argues for measuring "interoperability through =
widespread deployment of multiple implementations from different code =
bases".  It will be more difficult to remove features once =
implementations are widely deployed.  Keeping the feature fight within =
the Draft Standard  discussion can reduce the level of controversy at =
the last step.  As a side note, it would be less costly if feature =
evaluation was based on implementations instead of what people would =
like to keep (only one implementation of a feature).

This is an argument for the status quo.  We have decades of experience =
with that not working.  That is essentially an argument for a single =
maturity level; that is how the process is really working today.


> Once a Proposed Standard is published, it is expected that people will =
go and write code, if they have not done so yet, and evaluate whether =
their implementation can interoperate with other implementations.  I =
don't see anything in this draft that encourages that.

Of course that is what we want.  Even better if the running code is used =
to make decisions before the protocol become a Proposed Standard.


> In the RFC 5000 range, there are 7 Internet Standards, 13 Draft =
Standards and 537 Proposed Standards.  One of the arguments for this =
draft is that it reduces the number of IESG evaluations, and other =
review cycles, from three to two.  Basically, this draft is to adjust =
the environment so that the IESG can review everything.  It does not =
reduce the barrier of "intended proposed standards" to the RFC 2026 =
level.  It does not offer any incentive to advance document along the =
Standards Track.

This document is not about IESG review time, except for the elimination =
of the requirement for annual reviews which are not done anyway.  If =
that is what you get from the document, then I have done a very poor job =
in writing it.  That is not the point at all.

Russ=

From derhoermi@gmx.net  Wed Aug  3 12:46:45 2011
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D4A21F8B39 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=-0.914, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GGVXktj2d8RT for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:46:44 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 1721F21F8A70 for <ietf@ietf.org>; Wed,  3 Aug 2011 12:46:43 -0700 (PDT)
Received: (qmail invoked by alias); 03 Aug 2011 19:46:53 -0000
Received: from dslb-094-223-181-191.pools.arcor-ip.net (EHLO HIVE) [94.223.181.191] by mail.gmx.net (mp045) with SMTP; 03 Aug 2011 21:46:53 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/qlEJ9MFfqsBFwGCf1mYG8eGjE2CbDtGyY9evoZl 97HjNvDIbvPrX3
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Warren Kumari <warren@kumari.net>
Subject: Re: subject_prefix on IETF Discuss?
Date: Wed, 03 Aug 2011 21:46:54 +0200
Message-ID: <lt8j37h6musc4o6q617mecuop2l8m3r545@hive.bjoern.hoehrmann.de>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
In-Reply-To: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 19:46:45 -0000

* Warren Kumari wrote:
>Background: I used to just filter this list into a mailbox / folder
>(based upon List-Id:), but then I would forget to read it, so I have
>removed that procmail rule. Having a prefix would make it easier to tell
>at a glance what list the mail is associated with, what it might be
>about, etc. Yes, I *could* just make a procmail rule to munge the
>subject myself, but that seems icky, and solving it for the general case
>(and making Discussions more like the other IETF lists feels better).

If you would like your mail client to identify the mailing list next to
the subject header, then it seems your client should just do that, which
would avoid all the problems munging the subject header entails. Seems
to be a popular feature aswell, so I'd think clients support this...
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From d3e3e3@gmail.com  Wed Aug  3 12:50:07 2011
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741E811E807E for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.459
X-Spam-Level: 
X-Spam-Status: No, score=-104.459 tagged_above=-999 required=5 tests=[AWL=-0.860, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1ZdBPFlF2-d for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:50:07 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id AE90021F882E for <ietf@ietf.org>; Wed,  3 Aug 2011 12:50:06 -0700 (PDT)
Received: by gyd5 with SMTP id 5so769937gyd.31 for <ietf@ietf.org>; Wed, 03 Aug 2011 12:50:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=SmZm+z54CWZu/xy9NAOZi6P/Wq6z3ZAEIXDe6IwybsE=; b=AcBaBSHdZNos3HgJ953I/2K60VPi3A+YFK7kP3jMFa8xSU61ymaW6K31iNegzPusfo 0Zp60yO77xGr4FFz09LWUf66sBRgZ9XT2BEb4fCF9q36ETrgzyRbAl3IeXxVmbhTH2nm oLkE37WYoetY0Le717AlwkTO1hz36vVxNByFc=
Received: by 10.151.21.13 with SMTP id y13mr1085470ybi.239.1312401017969; Wed, 03 Aug 2011 12:50:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.50.5 with HTTP; Wed, 3 Aug 2011 12:49:57 -0700 (PDT)
In-Reply-To: <20110803185436.C266E11E808C@ietfa.amsl.com>
References: <20110803185436.C266E11E808C@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 3 Aug 2011 15:49:57 -0400
Message-ID: <CAF4+nEFfYXJBqJauPrSFddtoi0cVXS9vWf-KQWr7KQRLqcAo3A@mail.gmail.com>
Subject: Re: New Non-WG Mailing List: happiana -- IETF/W3C/IANA Registry Happiness
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: presnick@qualcomm.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 19:50:07 -0000

Why can't we get informative explanations of what problem non-WG
mailing lists are trying to address?

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, Aug 3, 2011 at 2:54 PM, IETF Secretariat
<ietf-secretariat@ietf.org> wrote:
>
> A new IETF non-working group email list has been created.
>
> List address: happiana@ietf.org
> Archive: http://www.ietf.org/mail-archive/web/happiana/
> To subscribe: https://www.ietf.org/mailman/listinfo/happiana
>
> Purpose: This list is for discussion of IANA Registry issues to
> result in Happy IETF, Happy W3C, and Happy IANA.
>
> For additional information, please contact the list administrators.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>

From stpeter@stpeter.im  Wed Aug  3 12:54:40 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A70B21F861E for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.677
X-Spam-Level: 
X-Spam-Status: No, score=-102.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrsMIAkYTOem for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 12:54:39 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACAE21F85CE for <ietf@ietf.org>; Wed,  3 Aug 2011 12:54:39 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 230CE4137E; Wed,  3 Aug 2011 13:56:11 -0600 (MDT)
Message-ID: <4E39A789.6070109@stpeter.im>
Date: Wed, 03 Aug 2011 13:54:49 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: New Non-WG Mailing List: happiana -- IETF/W3C/IANA Registry Happiness
References: <20110803185436.C266E11E808C@ietfa.amsl.com> <CAF4+nEFfYXJBqJauPrSFddtoi0cVXS9vWf-KQWr7KQRLqcAo3A@mail.gmail.com>
In-Reply-To: <CAF4+nEFfYXJBqJauPrSFddtoi0cVXS9vWf-KQWr7KQRLqcAo3A@mail.gmail.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: presnick@qualcomm.com, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 19:54:40 -0000

On 8/3/11 1:49 PM, Donald Eastlake wrote:
> Why can't we get informative explanations of what problem non-WG
> mailing lists are trying to address?
>>
>> Purpose: This list is for discussion of IANA Registry issues to
>> result in Happy IETF, Happy W3C, and Happy IANA.

Various folks have found it difficult to do things like register new
media types. There's been discussion among a small group of people to
streamline those processes (getting ADs out of the way, improving the
interface to IANA, etc.). The list started out as a small, private
design team and is now being opened to wider participation.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stpeter@stpeter.im  Wed Aug  3 13:45:01 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3D211E8078 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 13:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.674
X-Spam-Level: 
X-Spam-Status: No, score=-102.674 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mf9eoSvo9g6F for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 13:45:01 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 494C121F851F for <ietf@ietf.org>; Wed,  3 Aug 2011 13:45:01 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 020FB400F6; Wed,  3 Aug 2011 14:46:34 -0600 (MDT)
Message-ID: <4E39B358.7060409@stpeter.im>
Date: Wed, 03 Aug 2011 14:45:12 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: subject_prefix on IETF Discuss?
References: <201108031926.p73JQdHj019455@fs4113.wdf.sap.corp>
In-Reply-To: <201108031926.p73JQdHj019455@fs4113.wdf.sap.corp>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: johnl@iecc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 20:45:02 -0000

On 8/3/11 1:26 PM, Martin Rex wrote:

> subject_prefix will work even with very ancient MUAs, such as the
> one I use, so I'm OK.  But the subject_prefix does not scale well
> when multiple IETF mailings lists are CC-ed and discussion ensues
> (replying to all lists).

"Doctor, it hurts when I do that."

/psa



From hsantos@isdg.net  Wed Aug  3 14:19:51 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 557D511E808E for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 14:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.622
X-Spam-Level: 
X-Spam-Status: No, score=-3.622 tagged_above=-999 required=5 tests=[AWL=-1.023, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UZWg9Uh6lguv for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 14:19:50 -0700 (PDT)
Received: from groups.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id EF9EC11E8088 for <ietf@ietf.org>; Wed,  3 Aug 2011 14:19:49 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6919; t=1312406396; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=ZHdjJfwwTnpgnn/peY9lkKzI6Ac=; b=Guzbf5vLaW+dlgKwzz7h HynbFtr/ZHzQuncRv3tHO5oexhU9LxkzaT6nXouwIpzJzlRAkNT8zubQgK7iA5ZB PTuXGLUJwkqEsYAgR2z1wZZyMysxAQMHeNpfxaMAJwjAXrRZo+O9r2Z4t8Otr4kn FmrmZMTLlEc9urxjMSfe85U=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 17:19:56 -0400
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 861880849.34734.5700; Wed, 03 Aug 2011 17:19:56 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 17:15:23 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1833161674.602.4296; Wed, 03 Aug 2011 17:15:22 -0400
Message-ID: <4E39BB74.4090808@isdg.net>
Date: Wed, 03 Aug 2011 17:19:48 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>
In-Reply-To: <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 21:19:51 -0000

I appreciate this exchange here. I have a better idea of the draft and 
your intention  I have a few comments.

What I have noticed of late are fast track RFCs are coming out of no 
where, very fast and sometimes are indirectly related to a WG but not 
a WG chartered work item, and it may have an unforeseen influence in 
the WG end results.  While not all WGs are the same, this is what I 
experienced in the DKIM WG.  The problem comes when there is little or 
isolating vetting to this external work.

For the most part, once work gets an RFC or even just an published 
I-D, it also comes with a complex to be labeled as a "standard" to 
"throw the book" at others; "you are not following the standard." 
While they are technically wrong, it happens and it puts others in 
defensive position. But it also shows why there are derivative work or 
why an RFC does not get followed 100%.

I guess, if anything, if we are going to allow for faster maturity, we 
probably need some guidelines (if not already in place) in how non-WG 
RFC productions could influence a current WG.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com

Russ Housley wrote:
> SM:
> 
>> From Section 2.1:
>>
>> "no existing published requirements are relaxed".
>>
>> Are these published requirements BCPs?
> 
> Yes.
> 
> 
>> From Section 2.2:
>>
>>  'This maturity level is a merger of Draft Standard and Standard as
>>   specified in RFC 2026 [1].  The chosen name avoids confusion between
>>   "Draft Standard" and "Internet-Draft".'
>>
>> Shouldn't that be "Internet Standard" instead of "Standard"?
> 
> Look at RFC 2026.  The three level defined there are Proposed Standard, Draft Standard, and Standard.
> 
> The draft-housley-two-maturity-levels proposes two levels: Proposed Standard and Internet Standard.
> 
> 
>>   "The request for reclassification is sent to the IESG along with an
>>    explanation of how the criteria have been met.
>>    The criteria are:
>>
>>   (1) There are at least two independent interoperating implementations
>>       with widespread deployment and successful operational experience.
>>
>>   (2) There are no errata against the specification that would cause a
>>       new implementation to fail to interoperate with deployed ones.
>>
>>   (3) There are no unused features in the specification that greatly
>>       increase implementation complexity."
>>
>> The document that has been the subject of innumerable messages highlights how difficult it can be to reclassify a RFC.  Moreover, it amplified the divide between application folks and operators.  The IESG could have used the review clause from RFC 2026 and:
>>
>>  (i)  requested an implementation report from the people in favor of the
>>       proposed standard; and
>>
>>  (ii) a statement about deployment to determine whether there are operational
>>       issues that have to be addressed.
>>
>> I don't know whether application folks and operators agree that cross-area requires mutual understanding.
>>
>> The creation of interoperable protocol implementations requires clear specifications.  Interoperability does not mean that the protocol would not have unintended effects on the network.  That is where operational experience comes in.  It can serve as valuable input to improve a specification.  For what it is worth, there approximately 75 implementation reports have been submitted since 1996.
> 
> I am well aware of the implementation reports.  The premise here is that the protocol specification is "good enough" there are at least two interoperable implementations and the protocol is deployed widely.  The implementation report would become optional.
> 
> 
>> A two-step maturity level folds the two different classes of issues into one.  Quoting RFC 5657, which this draft unfortunately does not reference:
>>
>>  "Moving documents along the standards track can be an important signal
>>   to the user and implementor communities, and the process of
>>   submitting a standard for advancement can help improve that standard
>>   or the quality of implementations that participate."
>>
>> During a discussion on another mailing list, it has been mentioned that such an effort has a cost.  Lumping all the issues together can only increase that cost.
> 
> People are not doing many implementation reports.  As you say above, there are only about 75 of them.  How many protocols are documented in RFCs?  That is a very low percentage in my view.
> 
> So, I see the cost quite differently.  Most protocols are published as Proposed Standards, and they are never advanced.  I'm seeking a process where implementation and deployment experience actually improves the protocol specifications.  Today, that rarely happens, and when it does, the document recycles at Proposed Standard and the reader does not know whether it happened or not.
> 
> 
>> Strangely, this draft argues for measuring "interoperability through widespread deployment of multiple implementations from different code bases".  It will be more difficult to remove features once implementations are widely deployed.  Keeping the feature fight within the Draft Standard  discussion can reduce the level of controversy at the last step.  As a side note, it would be less costly if feature evaluation was based on implementations instead of what people would like to keep (only one implementation of a feature).
> 
> This is an argument for the status quo.  We have decades of experience with that not working.  That is essentially an argument for a single maturity level; that is how the process is really working today.
> 
> 
>> Once a Proposed Standard is published, it is expected that people will go and write code, if they have not done so yet, and evaluate whether their implementation can interoperate with other implementations.  I don't see anything in this draft that encourages that.
> 
> Of course that is what we want.  Even better if the running code is used to make decisions before the protocol become a Proposed Standard.
> 
> 
>> In the RFC 5000 range, there are 7 Internet Standards, 13 Draft Standards and 537 Proposed Standards.  One of the arguments for this draft is that it reduces the number of IESG evaluations, and other review cycles, from three to two.  Basically, this draft is to adjust the environment so that the IESG can review everything.  It does not reduce the barrier of "intended proposed standards" to the RFC 2026 level.  It does not offer any incentive to advance document along the Standards Track.
> 
> This document is not about IESG review time, except for the elimination of the requirement for annual reviews which are not done anyway.  If that is what you get from the document, then I have done a very poor job in writing it.  That is not the point at all.
> 
> Russ
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 







From tony@att.com  Wed Aug  3 14:44:33 2011
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7517C11E8094 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 14:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GbS3gFGMJrVM for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 14:44:33 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by ietfa.amsl.com (Postfix) with ESMTP id EA00511E808C for <ietf@ietf.org>; Wed,  3 Aug 2011 14:44:32 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-2.tower-120.messagelabs.com!1312407883!31096066!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 15632 invoked from network); 3 Aug 2011 21:44:44 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-2.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Aug 2011 21:44:44 -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 p73Lj9rY010733 for <ietf@ietf.org>; Wed, 3 Aug 2011 17:45:09 -0400
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 p73Lj1CG010674 for <ietf@ietf.org>; Wed, 3 Aug 2011 17:45:01 -0400
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 p73LiZUH024203 for <ietf@ietf.org>; Wed, 3 Aug 2011 17:44:35 -0400
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p73LiU5O024022 for <ietf@ietf.org>; Wed, 3 Aug 2011 17:44:30 -0400
Received: from [130.10.229.179] (vpn-130-10-229-179.vpn.sest.att.com[130.10.229.179]) by maillennium.att.com (mailgw1) with ESMTP id <20110803214429gw100e4lv2e> (Authid: tony); Wed, 3 Aug 2011 21:44:29 +0000
X-Originating-IP: [130.10.229.179]
Message-ID: <4E39C13B.4020208@att.com>
Date: Wed, 03 Aug 2011 17:44:27 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
In-Reply-To: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 21:44:33 -0000

On 8/3/2011 12:22 PM, Warren Kumari wrote:
> Hi all,
>
> I seem to remember discussions about this a long time ago, but searching through archives gets no love...
>
> How do folk feel about having asking for subject_prefix to be set on the IETF Discussion List (AKA this one!) - this will prefix mail sent to this list with something like "[Discussion]" or "[IETF]" or something [0].

-1 cause it breaks signatures

This might be mitigated if authentication-results support were added.

     Tony Hansen

PS. I do my sorting based on the To/Cc field as much as anything.

From brian.e.carpenter@gmail.com  Wed Aug  3 14:45:29 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8906511E80AC for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 14:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yT1LRN2aqQcu for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 14:45:29 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E88BA11E80AB for <ietf@ietf.org>; Wed,  3 Aug 2011 14:45:28 -0700 (PDT)
Received: by vws12 with SMTP id 12so1093016vws.31 for <ietf@ietf.org>; Wed, 03 Aug 2011 14:45:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AHH+ONuc4Pk86wy2OCqzQdI/GKyFdyANc8HMuiuixEE=; b=LlGRM5M3j1VyzyzIJJbWwAsy3jgs/Q89d7SQfQBOzdMS1KbSjnh892421Clii9oxlo 0TPyErFkPN4bAQq0msveP+WPog+Av5VoQcuWplI1IfMfZDt0j06/3T6giXyUdgcqEqlR IyVSwA/doVuN6Je9vxN/PEWXwwrRTEnr2jPiY=
Received: by 10.220.7.74 with SMTP id c10mr4710vcc.5.1312407940584; Wed, 03 Aug 2011 14:45:40 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id d20sm478192vcp.34.2011.08.03.14.45.38 (version=SSLv3 cipher=OTHER); Wed, 03 Aug 2011 14:45:40 -0700 (PDT)
Message-ID: <4E39C180.90408@gmail.com>
Date: Thu, 04 Aug 2011 09:45:36 +1200
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: Hector Santos <hsantos@isdg.net>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <4E39BB74.4090808@isdg.net>
In-Reply-To: <4E39BB74.4090808@isdg.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 21:45:29 -0000

Hector,


On 2011-08-04 09:19, Hector Santos wrote:
> I appreciate this exchange here. I have a better idea of the draft and
> your intention  I have a few comments.
> 
> What I have noticed of late are fast track RFCs are coming out of no
> where, very fast and sometimes are indirectly related to a WG but not a
> WG chartered work item, and it may have an unforeseen influence in the
> WG end results.  While not all WGs are the same, this is what I
> experienced in the DKIM WG.  The problem comes when there is little or
> isolating vetting to this external work.

Can you be more specific? Are you talking about

a) drafts that appear in the WG with very mature text, so complete
the WG progress very quickly?

b) drafts that are direct submissions to the IESG, and go through
IETF Last Call and IESG review without coming near the WG?

c) drafts that are Independent Submissions to the RFC Editor,
so are only subject to minimal review by the IESG and are not
IETF documents at all?

And in case a) or b), are you talking about standards track and BCP
documents, or about informational or experimental ones?

> For the most part, once work gets an RFC or even just an published I-D,
> it also comes with a complex to be labeled as a "standard" to "throw the
> book" at others; "you are not following the standard." While they are
> technically wrong, it happens and it puts others in defensive position.
> But it also shows why there are derivative work or why an RFC does not
> get followed 100%.
> 
> I guess, if anything, if we are going to allow for faster maturity, we
> probably need some guidelines (if not already in place) in how non-WG
> RFC productions could influence a current WG.

I don't understand that without understanding what kind of document
you are concerned about.

   Brian

From dave@cridland.net  Wed Aug  3 15:39:31 2011
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E3D822800E for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 15:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level: 
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VX1F-E50ohDR for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 15:39:30 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9AA11E80AD for <ietf@ietf.org>; Wed,  3 Aug 2011 15:39:30 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 6C1A61168087; Wed,  3 Aug 2011 23:39:38 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+y3NgoHQhzW; Wed,  3 Aug 2011 23:39:35 +0100 (BST)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 0B9D51168067; Wed,  3 Aug 2011 23:39:35 +0100 (BST)
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E39C13B.4020208@att.com>
In-Reply-To: <4E39C13B.4020208@att.com>
MIME-Version: 1.0
Message-Id: <13103.1312411175.046494@puncture>
Date: Wed, 03 Aug 2011 23:39:35 +0100
From: Dave Cridland <dave@cridland.net>
To: Tony Hansen <tony@att.com>, IETF-Discussion <ietf@ietf.org>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 22:39:31 -0000

On Wed Aug  3 22:44:27 2011, Tony Hansen wrote:
> PS. I do my sorting based on the To/Cc field as much as anything.

I do Sieve to assign IMAP keywords based on the List-Id header field  
which my MUA then uses to colourize differently in the summary  
listing based on the settings it finds in ACAP.

Do I win?

(I'm largely against subject prefixes, but not sufficient to jump up  
and down about).

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From dougb@dougbarton.us  Wed Aug  3 15:40:21 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62ECC22800E for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 15:40:21 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HFr-vkl2V2N for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 15:40:20 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7D637228010 for <ietf@ietf.org>; Wed,  3 Aug 2011 15:40:20 -0700 (PDT)
Received: (qmail 26126 invoked by uid 399); 3 Aug 2011 22:40:30 -0000
Received: from unknown (HELO 12-207-105-211.globalsuite.net) (dougb@dougbarton.us@12.207.105.211) by mail2.fluidhosting.com with ESMTPAM; 3 Aug 2011 22:40:30 -0000
X-Originating-IP: 12.207.105.211
X-Sender: dougb@dougbarton.us
Message-ID: <4E39CE5A.3020605@dougbarton.us>
Date: Wed, 03 Aug 2011 15:40:26 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: subject_prefix on IETF Discuss?
References: <20110803182123.95411.qmail@joyce.lan>
In-Reply-To: <20110803182123.95411.qmail@joyce.lan>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 22:40:21 -0000

On 08/03/2011 11:21, John Levine wrote:
>>> happy to let those who prefer to not have such a prefix setup their
>>> procmail rules to remove it.<-:)
> 
> Gee, I was about to say I was happy for people who want a subject tag
> to add one using procmail or whatever.
> 
> I'm not unalterably opposed to subject tags, but I believe that the
> IETF's dogfood is of the List-ID: flavor.

+1 on both counts.


-- 

	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 sm@resistor.net  Wed Aug  3 15:55:50 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C46E11E80B3 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 15:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Db0r8SzzN-aY for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 15:55:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EAA6B11E809B for <ietf@ietf.org>; Wed,  3 Aug 2011 15:55:47 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p73MttpS023470 for <ietf@ietf.org>; Wed, 3 Aug 2011 15:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1312412158; bh=O73lWtV+BMK5bZ/jsy73A6dx9cprWoBjjH/2LbaPu08=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=v3HZAG8/ZAqhyuKRJnhkyP7MkwcIfr02EhAri/ClbRUPJgEqV5108LnI4wQyeFBL+ 2RPHs+1PUI+wfQfa1b76R1Mqer8E5Uisntqz9OpA0epA/ecBqeiU8gxvOU5UI1paU5 nytlB/fSRpgm1YaPkqj+dwn9MVCHDiIUjxUTFKOM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1312412158; bh=O73lWtV+BMK5bZ/jsy73A6dx9cprWoBjjH/2LbaPu08=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=yINuuC9QyudGG35D4zjAXNrNYHX2bdse1nOlHzLZ/EwTZJOo7+GrydvIU4U7P2ead gAwRHd6RLnUzPOkYYoHIwXOa8RBhmGDP5Ug9UCbWeCKgQHr3uP+iCkBBT808qyZDBx GTs6lC63TMAXq7/JZz/ysi9ZBxbUSGMU1tppYy/4=
Message-Id: <6.2.5.6.2.20110803112858.0b445178@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 03 Aug 2011 15:48:14 -0700
To: IETF Discussion List <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: subject_prefix on IETF Discuss?
In-Reply-To: <4E397BF0.7030608@stpeter.im>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E3978C4.1060503@dcrocker.net> <20110803164034.GP6118@x27.adm.denic.de> <4E397BF0.7030608@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 22:55:50 -0000

At 09:48 AM 8/3/2011, Peter Saint-Andre wrote:
>Given that almost all of the WG lists have subject prefixes, it seems
>most folks find your arguments less than compelling.

Not really, it's the default setting for the WG lists and nobody 
bothered changing the setting.  As mentioned in 
draft-koch-subject-tags-considered-00, the tag is ambiguous when used 
for list identification.

Discussions about subject tagging are rarely about compelling 
arguments; it's a religious debate.  The tagging was introduced due 
to the inability of a well-known MUA to implement RFC 2919 for 
messages sorting.  As time went by, people viewed it as the norm.

As this is a matter of local preference, it is better to leave it to 
the subscriber to add the subject tag if he/she believes that it is useful.

Regards,
-sm 


From hsantos@isdg.net  Wed Aug  3 16:06:37 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1249911E80BC for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.587
X-Spam-Level: 
X-Spam-Status: No, score=-3.587 tagged_above=-999 required=5 tests=[AWL=-0.988, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AB5jZlMAAK+X for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:06:36 -0700 (PDT)
Received: from ntbbs.santronics.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C522711E809B for <ietf@ietf.org>; Wed,  3 Aug 2011 16:06:35 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1690; t=1312412803; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=J67iEsVCHqR3fcAcrm5fMv9M7yA=; b=LFmsYtYxwEh/U60LHUPD Y4PUvKCHl6rpPIuiWC8JpeByRrIxNlXkFDhWmPSfd9wnFeiOpfRgvnzYFcsDl6xY ss81YNQz8SOtzfILNGWb2QjEfyKwT6kdgrrr2aS1jAaXybmOxQ7S6KpaACsiEYBz 4QsRi9bCOsoSON/DdNwqeZQ=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 19:06:43 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 868286499.34928.3308; Wed, 03 Aug 2011 19:06:41 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 19:02:07 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1839566346.606.3300; Wed, 03 Aug 2011 19:02:07 -0400
Message-ID: <4E39D47C.20509@isdg.net>
Date: Wed, 03 Aug 2011 19:06:36 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>	<4E39C13B.4020208@att.com> <13103.1312411175.046494@puncture>
In-Reply-To: <13103.1312411175.046494@puncture>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Tony Hansen <tony@att.com>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 23:06:37 -0000

Dave Cridland wrote:
> On Wed Aug  3 22:44:27 2011, Tony Hansen wrote:
>> PS. I do my sorting based on the To/Cc field as much as anything.
> 
> I do Sieve to assign IMAP keywords based on the List-Id header field 
> which my MUA then uses to colourize differently in the summary listing 
> based on the settings it finds in ACAP.
> 
> Do I win?
> 
> (I'm largely against subject prefixes, but not sufficient to jump up and 
> down about).

+1, In theory I am against any mail alterations. But the list tag has 
helped MUAs that do not have rules filtering or the user is not savvy 
enough to figure out.  We avoided it for a long time in our list 
server product, and when it was finally added, it became and remain 
very popular. It is now the default setup for a new list.

I will say today, more MUA are aware of mailing list with automated 
unsubscribe features (by looking at the 5322.List-XXXXX added 
headers).  I personally use these to separate folders since the 
subject tag may be turned off by the server.

Some Negatives:

When DKIM was introduced, a mail integrity technology, now needed to 
work with a natural mail integrity breaking system. Even though DKIM 
offered a body tag (l=) feature to help exclude list footer text in 
the body hash verification process, changing the subject tag broke 
original signatures.

List resigners help alleviate this issue, but at the expense of losing 
original DKIM integrity information opening a loop hole for security 
concerns and potential interoperability issues with submission 
downlinks (members) with DKIM security support.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From moore@network-heretics.com  Wed Aug  3 16:33:12 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6696921F8ACE for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.93
X-Spam-Level: 
X-Spam-Status: No, score=-2.93 tagged_above=-999 required=5 tests=[AWL=-0.331,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JSaoEIn4qhZG for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:33:12 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id E54D921F85B1 for <ietf@ietf.org>; Wed,  3 Aug 2011 16:33:11 -0700 (PDT)
Received: from [65.16.145.177] (helo=host65-16-145-177.birch.net) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <moore@network-heretics.com>) id 1QokwE-00068q-L3; Wed, 03 Aug 2011 19:33:22 -0400
Subject: Re: subject_prefix on IETF Discuss?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
Date: Wed, 3 Aug 2011 19:33:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <92A4D854-F108-4A62-9B2D-8678FBC22D63@network-heretics.com>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-ELNK-Trace: 867ef52fd101ecb3d6dd28457998182d7e972de0d01da940f7159e60c98ccd3885ab39a9ddd947b3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 65.16.145.177
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 23:33:12 -0000

On Aug 3, 2011, at 12:22 PM, Warren Kumari wrote:

> How do folk feel about having asking for subject_prefix to be set on =
the IETF Discussion List (AKA this one!) - this will prefix mail sent to =
this list with something like "[Discussion]" or "[IETF]" or something =
[0].

My preference is to not have these prefixes.  I have all of my list mail =
go to a separate folder for each list.  The subject prefixes just add =
clutter.=20

That said, I realize a lot of people don't use mail folders and have =
dysfunctional user agents.  I'll be annoyed if a subject prefix is =
added, but I'll cope.

Keith=

From msk@cloudmark.com  Wed Aug  3 16:41:06 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69AFC11E809B for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.157
X-Spam-Level: 
X-Spam-Status: No, score=-103.157 tagged_above=-999 required=5 tests=[AWL=-0.558, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKv6Eiz9H1nW for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:41:06 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 06FA721F8557 for <ietf@ietf.org>; Wed,  3 Aug 2011 16:41:06 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Wed, 3 Aug 2011 16:41:19 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF list <ietf@ietf.org>
Date: Wed, 3 Aug 2011 16:41:18 -0700
Subject: RE: subject_prefix on IETF Discuss?
Thread-Topic: subject_prefix on IETF Discuss?
Thread-Index: AcxSNcIf9aa8JJOQQlercXuaxufdaQAANv8w
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF56A@EXCH-C2.corp.cloudmark.com>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <92A4D854-F108-4A62-9B2D-8678FBC22D63@network-heretics.com>
In-Reply-To: <92A4D854-F108-4A62-9B2D-8678FBC22D63@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 23:41:06 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of K=
eith Moore
> Sent: Wednesday, August 03, 2011 4:33 PM
> To: IETF list
> Subject: Re: subject_prefix on IETF Discuss?
>=20
> My preference is to not have these prefixes.  I have all of my list
> mail go to a separate folder for each list.  The subject prefixes just
> add clutter.
>=20
> That said, I realize a lot of people don't use mail folders and have
> dysfunctional user agents.  I'll be annoyed if a subject prefix is
> added, but I'll cope.

That about sums up my view as well.

From bew@cisco.com  Wed Aug  3 17:33:19 2011
Return-Path: <bew@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549B221F8A1A for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 17:33:19 -0700 (PDT)
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=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkqwralNXCuh for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 17:33:19 -0700 (PDT)
Received: from nm24.access.bullet.mail.sp2.yahoo.com (nm24.access.bullet.mail.sp2.yahoo.com [98.139.44.151]) by ietfa.amsl.com (Postfix) with SMTP id 36EF211E8095 for <ietf@ietf.org>; Wed,  3 Aug 2011 17:33:19 -0700 (PDT)
Received: from [98.139.44.105] by nm24.access.bullet.mail.sp2.yahoo.com with NNFMP; 04 Aug 2011 00:33:31 -0000
Received: from [98.139.44.90] by tm10.access.bullet.mail.sp2.yahoo.com with NNFMP; 04 Aug 2011 00:33:31 -0000
Received: from [127.0.0.1] by omp1027.access.mail.sp2.yahoo.com with NNFMP; 04 Aug 2011 00:33:31 -0000
X-Yahoo-Newman-Id: 773085.39902.bm@omp1027.access.mail.sp2.yahoo.com
Received: (qmail 66807 invoked from network); 4 Aug 2011 00:33:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1312418011; bh=GO+MhJKahbyAlZaMN6o650wDPcm8Hxt7fWE34ftbTvU=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=GzD49y8CA//jhUxDfxBjaxuKahbVIMQohep/89w6G7OXEgygR69zkMQItn4lf6gEY6tntbLNJsudPprY/WOVMs42KbMT0VT9hJYeWqF/37k9JFM9dQq5n81KWIHJ6lzx7qCBkYj7i+VxZw8vjgchwViHX2hITVRnotIVXAoYl9E=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: uPaRxfIVM1kn_E6BO_MeaKKbxbVIIvaKDXCh3BAkR3eVE7K a82unTc2oaj5eR6Va01SF.eshziem6PXt0p0mO6DLVZxiE7z1hrgfHWl6TR8 mvSU8YVCS1awmZn0S2CWxV3UiSKD8rejx.8SoAL6DoLsMvgSh2t.L0R59ePQ vdMjbUC7aVa4t7bFgOSxzNOLwk2Zha_yqSvTNdKMRB7c4lLVA4hZ81X6ISNu G3efVCiq64sY_4Xxu36sQufVm13jR1bbYRO7IRGVduVsDq3TSLHneTjFFdVx BEbcSCEGP1RLLucTGUZg2IDWJ7BPKAhOKoHv5y0uXck6q2a9iu0309itIFo6 5PljGxjOE9XWYIvdHHHpIjvi3PYT7bjlaSFwQP0GfDmyWz_z2oTnr5I378g0 59EuhWrc.3PVAHDXgYj3qxDAoK8mE33w93U0US9psQNL_
X-Yahoo-SMTP: 32nDaXmswBB_JniSOQ0NY72Nq.3.ushdrbBADol90kQ-
Received: from stealth-10-32-244-210.cisco.com (bew@70.239.230.164 with plain) by smtp107.sbc.mail.gq1.yahoo.com with SMTP; 03 Aug 2011 17:33:31 -0700 PDT
Subject: Re: [secdir] secdir review of draft-ietf-msec-gdoi-update
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Weis <bew@cisco.com>
In-Reply-To: <tsl8vrd2hz4.fsf@mit.edu>
Date: Wed, 3 Aug 2011 17:33:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B61042D-0BB4-42EA-970B-DDA36A659DA9@cisco.com>
References: <tsl8vrd2hz4.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-msec-gdoi-update@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 00:33:19 -0000

Hi Sam,

Thanks for your review.

Your first comment is pointing out a typo (groupkey-pull should be =
groupkey-push), which I've fixed.

The anti-replay description in Section 3.3 should not say that the push =
message sequence number will be reset to 1. Text earlier in this section =
says that the SEQ payload carries the next expected sequence number, and =
so when the KEK is installed that is the number that should be =
installed. I've adjusted the text to say this: "If this group has a KEK, =
the KEK policy and keys are marked as ready for use and the GM knows to =
expect a sequence number not less than the one distributed in the SEQ =
payload." Let me know if that change sufficiently clears up the =
confusion.

Thanks,
Brian

On Aug 1, 2011, at 9:51 AM, Sam Hartman wrote:

>=20
> This update to the GDOI specification significantly improves clarity =
and
> readability.
> However, there is one issue that I think should be addressed prior to
> publication:
>=20
>=20
> At the top of page 11, the spec claims that a seq payload protects
> against group members responding to groupkey-pull messages sent prior =
to
> joining the group.
> I'm reasonably sure that should be groupkey-push messages; I believe =
the
> nonce payloads provide replay protection for the pull exchange.
>=20
> Actually, it's more complicated than that.  Section 3.3 also seems to
> believe the sequence number is about pull exchanges. However it says
> that  a GM should always expect the push message sequence number to be
> reset to 1.
> Why is that reasonable? If a group is ongoing, don't we want to tell =
new
> members what the sequence number currently is rather than having them
> assume it is 1? The push message is multicast, so we cannot maintain a
> separate sequence number for each member.
>=20
> I think either there is some sort of error with the description of the
> replay mechanisms or it requires significantly more explanation.
> _______________________________________________
> secdir mailing list
> secdir@ietf.org
> https://www.ietf.org/mailman/listinfo/secdir
> wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview


--=20
Brian Weis
Security Standards and Technology, SRTG, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com






From hsantos@isdg.net  Wed Aug  3 19:34:26 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C02511E80D0 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 19:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.122
X-Spam-Level: 
X-Spam-Status: No, score=-3.122 tagged_above=-999 required=5 tests=[AWL=-1.387, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dpIMlQW4L4Gj for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 19:34:25 -0700 (PDT)
Received: from mail.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6D5C311E809D for <ietf@ietf.org>; Wed,  3 Aug 2011 19:34:23 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2006; t=1312425274; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=s/3/XtSYRit07a0kvLTjjE2ZtqM=; b=nSOB4n5SlXvMDvvlpfEh 7QmAVFwFhRem4MVm57uGxgpdv49FoU8WrQN8nGTldp4yOfLxxQIPZvDMVwKklVp7 jDz1eOQZLoGJuTUicmRim3kGrF0H1qegNKSXghaAa24vVCpsagjnENTdNJWjYTZi mnqJZPmVBMvMutodFXNLyn8=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 22:34:34 -0400
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 880757719.35207.3460; Wed, 03 Aug 2011 22:34:33 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 03 Aug 2011 22:29:58 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1852037033.630.5380; Wed, 03 Aug 2011 22:29:57 -0400
Message-ID: <4E3A0555.1070700@isdg.net>
Date: Wed, 03 Aug 2011 22:35:01 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <4E39BB74.4090808@isdg.net> <4E39C180.90408@gmail.com>
In-Reply-To: <4E39C180.90408@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 02:34:26 -0000

Brian E Carpenter asked:

> Can you be more specific? Are you talking about
> 
> a) drafts that appear in the WG with very mature text, so complete
> the WG progress very quickly?
> 
> b) drafts that are direct submissions to the IESG, and go through
> IETF Last Call and IESG review without coming near the WG?
> 
> c) drafts that are Independent Submissions to the RFC Editor,
> so are only subject to minimal review by the IESG and are not
> IETF documents at all?
> 
> And in case a) or b), are you talking about standards track and BCP
> documents, or about informational or experimental ones?

Hi Brian,

 From what I have experienced, it doesn't matter what the fast track 
non-WG RFC status is - any status can have a surprising WG goal 
changing influence.

I don't really see that as the main concern until it is a competing or 
conflictive externally produced RFC, especially if it was originally 
deem out of scope in a WG charter. IMO, in such a case, it should be 
part of a WG charter change and a WG vetting process before it is made 
into an RFC and/or allowed to change the WG goals.

I am not an expert with IETF procedures and I don't wish to call that 
a "Loop Hole" but it appears to be one.  It seems to me a two-maturity 
level may inadvertently create more of these WG conflicts without the 
proper due diligence to watch for these type of situations.

Maybe the experience in the DKIM WG was an exception and not the rule 
typical of a WG, but if was a new reflection of an "IETF change" 
making it more possible to fast track RFCs, the review process needs 
to take into account the consequences it can have in any related WG. 
Is that a time problem? A WG Chair/AD issue?  Too much work for the AD 
reviews?  Not enough synergism of among all parties?  I can't say and 
quite maybe it was just an exceptional experience and not the norm. 
But I believe a watchdog for these type of possibilities will help.

-- 
Hector Santos, CTO
http://www.santronics.com





From hsantos@isdg.net  Wed Aug  3 21:12:20 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 410A421F875C for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 21:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.048
X-Spam-Level: 
X-Spam-Status: No, score=-3.048 tagged_above=-999 required=5 tests=[AWL=-1.371, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9z4uqQlZ-cg for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 21:12:19 -0700 (PDT)
Received: from ftp.catinthebox.net (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1D14C21F875E for <ietf@ietf.org>; Wed,  3 Aug 2011 21:12:18 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=601; t=1312431149; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=lim2qPOZ1f4r9QAhM4TMYpPQHg0=; b=UxXTmv8GqSbsk3HFElVQ Ct5tmKX8hjL62wDPLcAi8TNec3snpNr2MUU2H4qc7PZEtw815dS3ufYC8s49oi28 Erw9iC/Asy9APeHNfInDswSfCV4A2oOCIfYILrpeP2uhMAR957aaXFXpQDetfI91 m8B5HoTtSrQpwYyQvcUDTng=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 04 Aug 2011 00:12:29 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 886632888.35458.784; Thu, 04 Aug 2011 00:12:28 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 04 Aug 2011 00:07:55 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1857913283.634.5060; Thu, 04 Aug 2011 00:07:54 -0400
Message-ID: <4E3A1C51.4040908@isdg.net>
Date: Thu, 04 Aug 2011 00:13:05 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: I-D Working groups and mailing list
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 04:12:20 -0000

I would like to propose that new I-D submissions include information 
about the existence of a Working Group, if any, and/or discussion 
group list address, if any, for to join and participate in the 
development of the I-D or simply to follow it.

I think I have read some I-D that including this useful information, 
but most do not. Its one the first things I look for.

I was going to suggest the same for an RFC, but it could be the WG was 
closed down by this time.

Just a thought if it makes sense.


-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From john-ietf@jck.com  Wed Aug  3 21:40:12 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF0411E80DF for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 21:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.643
X-Spam-Level: 
X-Spam-Status: No, score=-102.643 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sn6KPzUFpKR8 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 21:40:11 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 608BB11E80CD for <ietf@ietf.org>; Wed,  3 Aug 2011 21:40:11 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QopjH-000G1X-9y; Thu, 04 Aug 2011 00:40:19 -0400
Date: Thu, 04 Aug 2011 00:40:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jorge Contreras <cntreras@gmail.com>
Subject: Re: Opening BCP 79 (was: Re: encouraging compliance with IPR disclosure rules)
Message-ID: <5ADA383E3F3009852FF24D44@PST.JCK.COM>
In-Reply-To: <A9AD4C8E-0C48-4834-AECB-E6A8F29670A3@gmail.com>
References: <B172582ABAE9F7EA0B06DB36@PST.JCK.COM> <A9AD4C8E-0C48-4834-AECB-E6A8F29670A3@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 04:40:12 -0000

--On Wednesday, August 03, 2011 16:49 -0400 Jorge Contreras
<cntreras@gmail.com> wrote:

> John,
> 
> I'll jump in to save Marshall the trouble. I was asked by the
> IESG to put together a straw man first draft in collaboration
> with Scott Bradner. From what I see, many IDs are developed by
> a couple of authors before submitting to the larger IETF. is
> that unusual?  Clearly the intention is to have full community
> engagement, but 1200 people can't write a first draft (or at
> least not very well...) 

Jorge,

We are supposed to have some very specific rules about design
teams, especially ones that are commissioned by WG Chairs or
equivalent to prepare drafts.  Given "asked by the IESG to put
together...", your effort qualifies as such a design team.
Under those rules the relevant parts of the community are
supposed to be informed of the effort.  When, for example, Russ
initiated the work that led to RFC 5680, there was such an
announcement.

Finding out by accident doesn't constitute "informed".    Unless
the IESG has decided recently to exempt itself from that rule,
your effort is not off to a good start.

  regards,
     john


From McQuilWP@pobox.com  Thu Aug  4 00:11:31 2011
Return-Path: <McQuilWP@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0E4E21F8A7D for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 00:11:29 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ul5yT4Ij7vqa for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 00:11:28 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 1012C21F8A7A for <ietf@ietf.org>; Thu,  4 Aug 2011 00:11:27 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 290AC364D; Thu,  4 Aug 2011 03:11:40 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=z1yWyYEU9XkK YFip5e74LDaY6ZU=; b=FOe3XgGuiLqu1bBylnNIzbGk6AJG0PukPWwZGhI9gGHB ZVzoh29N0hQXRAhJa2YWEKu7nBseW+9EP73PIWrCzjZTA1ZLDQVxk5HTarUYaAvz mtIGoZOHVhTkgzQRf8jzeo66KUUUJ4ytRucFAjQ9i2nqvgFHRiRBkOtUqiEPJkg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=jDib8e gH16J9k6gpHptMam/tiRz0714BdL24lV3H5NCu0LsqVUGsENN0v6c207T1Jig055 kOEQbWUJoh9mJVcWeSj6bwbTm+DC8p9haYAWqsANjFAztC0HAhGtPKRJ0ndatrf/ ZBj1FyTqWTxQi4umvuHZiSzqakmgFhiRtqfgY=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 21601364C; Thu,  4 Aug 2011 03:11:40 -0400 (EDT)
Received: from BQ07NB (unknown [70.181.252.118]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id 7B61E364B; Thu,  4 Aug 2011 03:11:39 -0400 (EDT)
Date: Thu, 4 Aug 2011 00:11:38 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <1568238908.20110804001138@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: I-D Working groups and mailing list
In-Reply-To: <4E3A1C51.4040908@isdg.net>
References: <4E3A1C51.4040908@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: FFC24EF4-BE68-11E0-861E-1DC62E706CDE-02871704!b-pb-sasl-quonix.pobox.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 07:11:32 -0000

On Wed, 2011-08-03, Hector Santos wrote:
> I would like to propose that new I-D submissions include information
> about the existence of a Working Group, if any, and/or discussion
> group list address, if any, for to join and participate in the 
> development of the I-D or simply to follow it.

> I think I have read some I-D that including this useful information,
> but most do not. Its one the first things I look for.

> I was going to suggest the same for an RFC, but it could be the WG was
> closed down by this time.

> Just a thought if it makes sense.

+100

Perhaps it could be included in the ID-Announce message.


-- 
Bill McQuillan <McQuilWP@pobox.com>


From julian.reschke@gmx.de  Thu Aug  4 01:36:43 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52A2121F8BB1 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 01:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.186
X-Spam-Level: 
X-Spam-Status: No, score=-104.186 tagged_above=-999 required=5 tests=[AWL=-1.587, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drxbKFZXT0HC for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 01:36:42 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 621D721F8BBA for <ietf@ietf.org>; Thu,  4 Aug 2011 01:36:42 -0700 (PDT)
Received: (qmail invoked by alias); 04 Aug 2011 08:36:50 -0000
Received: from p508FD5FC.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.213.252] by mail.gmx.net (mp068) with SMTP; 04 Aug 2011 10:36:50 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18QH6Zp6dkQ0+2TqrbwQKsp2KC7ktqsZidJZL2NGC Myb5l7qnfJRxZ5
Message-ID: <4E3A5A1E.8050002@gmx.de>
Date: Thu, 04 Aug 2011 10:36:46 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Bill McQuillan <McQuilWP@pobox.com>
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com>
In-Reply-To: <1568238908.20110804001138@pobox.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 08:36:43 -0000

On 2011-08-04 09:11, Bill McQuillan wrote:
>
> On Wed, 2011-08-03, Hector Santos wrote:
>> I would like to propose that new I-D submissions include information
>> about the existence of a Working Group, if any, and/or discussion
>> group list address, if any, for to join and participate in the
>> development of the I-D or simply to follow it.
>
>> I think I have read some I-D that including this useful information,
>> but most do not. Its one the first things I look for.
>
>> I was going to suggest the same for an RFC, but it could be the WG was
>> closed down by this time.
>
>> Just a thought if it makes sense.
>
> +100
>
> Perhaps it could be included in the ID-Announce message.

+1

This should be mandatory in IDs.



From peter@denic.de  Thu Aug  4 02:04:00 2011
Return-Path: <peter@denic.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDC5221F8B17 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 02:04:00 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2hUwbImTq0D for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 02:04:00 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id D154021F8B15 for <ietf@ietf.org>; Thu,  4 Aug 2011 02:03:58 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1Qotqe-0000xV-7i; Thu, 04 Aug 2011 11:04:12 +0200
Received: from localhost by x27.adm.denic.de with local  id 1Qotqe-00053u-3y; Thu, 04 Aug 2011 11:04:12 +0200
Date: Thu, 4 Aug 2011 11:04:12 +0200
From: Peter Koch <pk@ISOC.DE>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: I-D Working groups and mailing list
Message-ID: <20110804090412.GC6118@x27.adm.denic.de>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E3A5A1E.8050002@gmx.de>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 09:04:00 -0000

On Thu, Aug 04, 2011 at 10:36:46AM +0200, Julian Reschke wrote:

> >>I think I have read some I-D that including this useful information,
> >>but most do not. Its one the first things I look for.

> >>Just a thought if it makes sense.
> >
> >+100
> >
> >Perhaps it could be included in the ID-Announce message.
> 
> +1
> 
> This should be mandatory in IDs.

I-D announcements are already copied to the relevant WG for WG drafts.
Non-WG drafts may have the WG name in between '-' in the filename,
allowing an easy identification of the WG the author thinks the draft is
relevant to. A discussion mailing list is not mandatory for a draft
and it could be that the author is still looking.  As a courtesy to
the reader, i've used this kind of hint in the past where applicable.
But please, let us not add another mandatory boilerplate piece of text.

-Peter

From evnikita2@gmail.com  Thu Aug  4 02:08:27 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A784821F8B52 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 02:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.453
X-Spam-Level: 
X-Spam-Status: No, score=-3.453 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id duKTd-PRCNwX for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 02:08:27 -0700 (PDT)
Received: from mail-ey0-f174.google.com (mail-ey0-f174.google.com [209.85.215.174]) by ietfa.amsl.com (Postfix) with ESMTP id DFCAD21F8B3E for <ietf@ietf.org>; Thu,  4 Aug 2011 02:08:26 -0700 (PDT)
Received: by eyx24 with SMTP id 24so236974eyx.19 for <ietf@ietf.org>; Thu, 04 Aug 2011 02:08:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Sqp3MajLxaTPazI9FlxksO3+kdbR2EH1UphZr38tGqY=; b=rRqOhI4UUaSfc0KZn4Ri5DKTgZGbuhdceKWJYcSdexLOQwBwnjcjHVyfNXRZLIou/X 0wKtwU8/j44gGJoSmI1PTssWcBrPbmASYnh5K2n7XnUO1C6D/WnGO88ros0VCr/OlMfi wNiTt1qi9Lf00CFm1NxDS1X7yPysEfNERH9DQ=
Received: by 10.205.65.205 with SMTP id xn13mr175439bkb.284.1312448917208; Thu, 04 Aug 2011 02:08:37 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id n11sm471798bkd.47.2011.08.04.02.08.35 (version=SSLv3 cipher=OTHER); Thu, 04 Aug 2011 02:08:36 -0700 (PDT)
Message-ID: <4E3A61BA.9010403@gmail.com>
Date: Thu, 04 Aug 2011 12:09:14 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de> <20110804090412.GC6118@x27.adm.denic.de>
In-Reply-To: <20110804090412.GC6118@x27.adm.denic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 09:08:27 -0000

04.08.2011 12:04, Peter Koch wrote:
> On Thu, Aug 04, 2011 at 10:36:46AM +0200, Julian Reschke wrote:
>
>>>> I think I have read some I-D that including this useful information,
>>>> but most do not. Its one the first things I look for.
>>>> Just a thought if it makes sense.
>>> +100
>>>
>>> Perhaps it could be included in the ID-Announce message.
>> +1
>>
>> This should be mandatory in IDs.
> I-D announcements are already copied to the relevant WG for WG drafts.
> Non-WG drafts may have the WG name in between '-' in the filename,
> allowing an easy identification of the WG the author thinks the draft is
> relevant to. A discussion mailing list is not mandatory for a draft
> and it could be that the author is still looking.  As a courtesy to
> the reader, i've used this kind of hint in the past where applicable.
> But please, let us not add another mandatory boilerplate piece of text.

I think it's possible to add an additional text field in the I-D 
Submission tools allowing the author/editor to specify the link to the 
page which would lead the reader in the discussion and copy such link in 
the I-D announce and/or Datatracker page.  And at the author's/editor's 
discretion, such link may be put in the draft's body.

Mykyta

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


From hartmans@mit.edu  Thu Aug  4 06:25:19 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAC121F8A1A; Thu,  4 Aug 2011 06:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.985
X-Spam-Level: 
X-Spam-Status: No, score=-103.985 tagged_above=-999 required=5 tests=[AWL=-1.720, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id po6YCBo4zDpF; Thu,  4 Aug 2011 06:25:19 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id F1AFA21F89C2; Thu,  4 Aug 2011 06:25:18 -0700 (PDT)
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 19301201C7; Thu,  4 Aug 2011 09:28:14 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 461134234; Thu,  4 Aug 2011 09:25:22 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Brian Weis <bew@cisco.com>
Subject: Re: [secdir] secdir review of draft-ietf-msec-gdoi-update
References: <tsl8vrd2hz4.fsf@mit.edu> <8B61042D-0BB4-42EA-970B-DDA36A659DA9@cisco.com>
Date: Thu, 04 Aug 2011 09:25:22 -0400
In-Reply-To: <8B61042D-0BB4-42EA-970B-DDA36A659DA9@cisco.com> (Brian Weis's message of "Wed, 3 Aug 2011 17:33:30 -0700")
Message-ID: <tsld3glux4t.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: draft-ietf-msec-gdoi-update@tools.ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 13:25:19 -0000

>>>>> "Brian" == Brian Weis <bew@cisco.com> writes:

    Brian> Hi Sam, Thanks for your review.

    Brian> Your first comment is pointing out a typo (groupkey-pull
    Brian> should be groupkey-push), which I've fixed.

    Brian> The anti-replay description in Section 3.3 should not say
    Brian> that the push message sequence number will be reset to
    Brian> 1. Text earlier in this section says that the SEQ payload
    Brian> carries the next expected sequence number, and so when the
    Brian> KEK is installed that is the number that should be
    Brian> installed. I've adjusted the text to say this: "If this group
    Brian> has a KEK, the KEK policy and keys are marked as ready for
    Brian> use and the GM knows to expect a sequence number not less
    Brian> than the one distributed in the SEQ payload." Let me know if
    Brian> that change sufficiently clears up the confusion.

Yes, all looks good.
The typo plus the text in 3e.3 caused me to wonder whether something
more complex than I had anticipated was going on with replay.
The new text is quite clear.

From nsb@guppylake.com  Thu Aug  4 06:25:49 2011
Return-Path: <nsb@guppylake.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0155821F8B03 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 06:25:49 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfeYcbX9PoNQ for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 06:25:48 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 59B3821F8B7E for <ietf@ietf.org>; Thu,  4 Aug 2011 06:25:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=PlMZprM+RNhO0K6SmSJJrdfFYPwRS3LGt3FfgPsrTIioLBtOB9hfQQKEjivMfg8Wmtm4E6RcdPljXadHwzwqJcNhj1SElsW/A/bdVBFf5YOr0UcVBL6P5GXlQW0kRvFA;
Received: from 184-203-12-130.pools.spcsdns.net ([184.203.12.130] helo=[192.168.0.197]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1Qoxw0-0004DV-3P for ietf@ietf.org; Thu, 04 Aug 2011 09:26:01 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: subject_prefix on IETF Discuss?
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <01O4ET4COJYS00VHKR@mauve.mrochek.com>
Date: Thu, 4 Aug 2011 09:25:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C30C8122-76C7-47DE-BEB5-04021A6CF635@guppylake.com>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <4E3978C4.1060503@dcrocker.net> <20110803164034.GP6118@x27.adm.denic.de> <01O4ET4COJYS00VHKR@mauve.mrochek.com>
To: ietf list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 13:25:49 -0000

Yes.  No.  No.  Yes.  Maybe.  Let me elaborate.

On Aug 3, 2011, at 12:35 PM, Dave CROCKER wrote:

> The visual cue this convention provides is helpful and it's an =
extremely widespread convention.


+1.  The effect on users is completely different, even though the same =
information is in there somewhere.  And the least fortunate users are =
both stuck with unhelpful user agents AND not in a position to do the =
kind of processing that would add the tag automatically.  So adding the =
tag is good from a usability perspective.

On Aug 3, 2011, at 1:53 PM, ned+ietf@mauve.mrochek.com wrote:

> The IETF list already inserts the all the proper list- headers:
> .......It's all I need for sorting .....
> OTOH, I can also remove the [ietf] tag if the list starts putting it =
in there.
> So count me as mildly disliking this proposal.

Yes, this is step back from standards to informal practice, so adding =
the tag is bad from an IETF/formal perspective, though perhaps only =
mildly so.

On Aug 3, 2011, at 5:44 PM, Tony Hansen wrote:

> -1 cause it breaks signatures


It's certainly bad if it breaks signatures.  On the other hand, if we =
can preserve the authentication results so that we have confidence in =
both the sender and the list exploder -- including the different forms =
of the Subject: field -- that would be a nice technical =
exercise/demonstration and a reference DKIM-handling example for other =
list software.

So I think this largely depends on how hard someone is willing to work =
on it.    -- Nathaniel



From mcr@sandelman.ca  Thu Aug  4 06:44:43 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4BBF21F8531 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 06:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level: 
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[AWL=0.503,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAgPNxN-Iw0Z for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 06:44:43 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 585F721F852C for <ietf@ietf.org>; Thu,  4 Aug 2011 06:44:43 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.236.58]) by relay.sandelman.ca (Postfix) with ESMTPS id 3E270340E1; Thu,  4 Aug 2011 09:44:32 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 9E4C798411; Thu,  4 Aug 2011 09:45:03 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: is IETF trying to do too much?
In-Reply-To: <4E399097.4080409@acm.org>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <D992EEF2-5DAE-4884-951E-8B8CD370657C@network-heretics.com> <24260.1312393889@marajade.sandelman.ca> <4E399097.4080409@acm.org>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 04 Aug 2011 09:45:03 -0400
Message-ID: <17974.1312465503@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 13:44:43 -0000

>>>>> "Marc" == Marc Petit-Huguenin <petithug@acm.org> writes:
    Marc> I personally would like to switch to the Tufte style,
    Marc> (i.e. uploading a printout, which can also be distributed to
    Marc> people before the meeting in printed form, and having *only* a
    Marc> discussion), but I am not sure how people will react.

I agree.
I would modify to say that projected slides with diagrams on them are a
good thing to permit discussion.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 



From john-ietf@jck.com  Thu Aug  4 06:47:32 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C38B621F8B39 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 06:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level: 
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGdwcFxHYnOR for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 06:47:32 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2F25421F8B20 for <ietf@ietf.org>; Thu,  4 Aug 2011 06:47:32 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QoyGr-0004DT-MG; Thu, 04 Aug 2011 09:47:33 -0400
Date: Thu, 04 Aug 2011 09:47:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Julian Reschke <julian.reschke@gmx.de>, Bill McQuillan <McQuilWP@pobox.com>
Subject: Re: I-D Working groups and mailing list
Message-ID: <EA34AC5BC8D9995010AB7429@PST.JCK.COM>
In-Reply-To: <4E3A5A1E.8050002@gmx.de>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de>
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 Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 13:47:32 -0000

--On Thursday, August 04, 2011 10:36 +0200 Julian Reschke
<julian.reschke@gmx.de> wrote:

> On 2011-08-04 09:11, Bill McQuillan wrote:
>> 
>> On Wed, 2011-08-03, Hector Santos wrote:
>>> I would like to propose that new I-D submissions include
>>> information about the existence of a Working Group, if any,
>>> and/or discussion group list address, if any, for to join
>>> and participate in the development of the I-D or simply to
>>> follow it.
>> 
>>> I think I have read some I-D that including this useful
>>> information, but most do not. Its one the first things I
>>> look for.
>...
>>> Just a thought if it makes sense.

> This should be mandatory in IDs.

Many of us think this is a good idea.  Many of us have been
including it when we remember and are easily reminded to include
it in the next update when we do not.  

Reminding people is probably a good idea.  Including an explicit
placeholder for this in templates would probably be a good idea.
It would make a good habit.

But there are circumstances in which the appropriate mailing
list is not known at the time of posting and others in which
permission to use an obvious mailing list requires pre-approval
that might significantly delay posting of a draft.

What we don't need, IMO, is more rules, especially rules that
would then need exception procedures, open up opportunities for
appeals about approval processes and the use of particular
lists, etc. 

   john


From dhc2@dcrocker.net  Thu Aug  4 07:04:50 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC4821F8A7B for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:04:50 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqVYAfq6aGDH for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:04:49 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B737821F8A69 for <ietf@ietf.org>; Thu,  4 Aug 2011 07:04:49 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p74E4xSH020371 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 4 Aug 2011 07:05:04 -0700
Message-ID: <4E3AA704.4@dcrocker.net>
Date: Thu, 04 Aug 2011 07:04:52 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de> <EA34AC5BC8D9995010AB7429@PST.JCK.COM>
In-Reply-To: <EA34AC5BC8D9995010AB7429@PST.JCK.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]); Thu, 04 Aug 2011 07:05:04 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 14:04:50 -0000

On 8/4/2011 6:47 AM, John C Klensin wrote:
>> This should be mandatory in IDs.
...
> But there are circumstances in which the appropriate mailing
> list is not known at the time of posting and others in which
> permission to use an obvious mailing list requires pre-approval
> that might significantly delay posting of a draft.
>
> What we don't need, IMO, is more rules,


Make the rule a SHOULD.  That allows exceptions.

When issuing an I-D, there needs to be a clear, affirmative obligation to help 
readers participate in discussion about the draft.

I suggested a requirement like this quite a few years ago and arguments similar 
to John's were invoked to kill it.

Based on how rare discussion venue citation remain, it's time to make the matter 
more explicit and formal.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dworley@avaya.com  Thu Aug  4 07:11:16 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6008321F8B34 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.465
X-Spam-Level: 
X-Spam-Status: No, score=-103.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d5Jlse1LG+KC for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:11:15 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id D19DB21F8A7A for <ietf@ietf.org>; Thu,  4 Aug 2011 07:11:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAGOoOk7GmAcF/2dsb2JhbABCp2Z3gUABAQEBAgESKA8eBwsFCwIBCA0IIRAyJQEBBAENDRqHSqVHApwjhWNfBJggi1s
X-IronPort-AV: E=Sophos;i="4.67,316,1309752000"; d="scan'208";a="295196442"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Aug 2011 10:11:09 -0400
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; 04 Aug 2011 10:08:18 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Thu, 4 Aug 2011 10:11:08 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: John C Klensin <john-ietf@jck.com>, Julian Reschke <julian.reschke@gmx.de>, Bill McQuillan <McQuilWP@pobox.com>
Date: Thu, 4 Aug 2011 10:11:06 -0400
Subject: RE: I-D Working groups and mailing list
Thread-Topic: I-D Working groups and mailing list
Thread-Index: AcxSrR7Z+eZEE6I1R9e8Jgj5aXYi/gAAfqX4
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de>,<EA34AC5BC8D9995010AB7429@PST.JCK.COM>
In-Reply-To: <EA34AC5BC8D9995010AB7429@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 Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 14:11:16 -0000

> >>> From: Hector Santos
> >>> I would like to propose that new I-D submissions include
> >>> information about the existence of a Working Group, if any,
> >>> and/or discussion group list address, if any, for to join
> >>> and participate in the development of the I-D or simply to
> >>> follow it.

We already have mechanisms like this in place.  Most I-Ds include the
relevant WG in their name, and the extremely popular XML2RFC format
has a <workgroup> element for specifying the relevant WG.  And the I-D
submission tool checks that field.  (I just got bitten by that.)  The
XML2RFC tool carries the <workgroup> value into the page headers of
the text form (at least in some circumstances).

Once one knows the WG name, one can go through www.ietf.org to find
the information about the WG, including its mailing list.  (Though one
has to know some lore to do this successfully.)

> From: John C Klensin
> What we don't need, IMO, is more rules, especially rules that
> would then need exception procedures, [...]

Indeed, yes.  Our most limited resource is the labor of the real staff
and the volunteers, and we should not introduce a change that would
consume their labor unless there is a significant benefit to be
obtained.

Dale

From dworley@avaya.com  Thu Aug  4 07:13:03 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B90FE21F8ACA for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.468
X-Spam-Level: 
X-Spam-Status: No, score=-103.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEOQ7XqsvIs2 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:13:03 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 08B3121F88A5 for <ietf@ietf.org>; Thu,  4 Aug 2011 07:13:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EABaoOk6HCzI1/2dsb2JhbABCp2Z3gUABAQEBAgESKDQQCwIBCA0IIRAyJQEBBAESCBqHSqVGApwjhWNfBJggi1s
X-IronPort-AV: E=Sophos;i="4.67,316,1309752000"; d="scan'208";a="260553367"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Aug 2011 10:13:16 -0400
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; 04 Aug 2011 10:05:27 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Thu, 4 Aug 2011 10:13:14 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Bill McQuillan <McQuilWP@pobox.com>, IETF Discussion <ietf@ietf.org>
Date: Thu, 4 Aug 2011 10:12:08 -0400
Subject: RE: I-D Working groups and mailing list
Thread-Topic: I-D Working groups and mailing list
Thread-Index: AcxSdc6jvDEXAa9KRC6/xBcM26q7rAAOrFpI
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F57E0@DC-US1MBEX4.global.avaya.com>
References: <4E3A1C51.4040908@isdg.net>,<1568238908.20110804001138@pobox.com>
In-Reply-To: <1568238908.20110804001138@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 14:13:03 -0000

> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Bill McQ=
uillan [McQuilWP@pobox.com]
>
> Perhaps it could be included in the ID-Announce message.

In a lot of situations, the I-D submission tool knows the name of the relev=
ant working group
and could include its mailing list address in the announcement automaticall=
y.

Dale

From julian.reschke@gmx.de  Thu Aug  4 07:22:53 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B030E21F87BD for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.768
X-Spam-Level: 
X-Spam-Status: No, score=-104.768 tagged_above=-999 required=5 tests=[AWL=-2.169, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M+imctAyjnXX for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:22:53 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 938D721F8794 for <ietf@ietf.org>; Thu,  4 Aug 2011 07:22:50 -0700 (PDT)
Received: (qmail invoked by alias); 04 Aug 2011 14:16:24 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp032) with SMTP; 04 Aug 2011 16:16:24 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/50Qkw90b56Q/DNAKokC8qha+1sSj09OTsBEM31k 6yDtXCK+WaChIa
Message-ID: <4E3AA9B5.3060500@gmx.de>
Date: Thu, 04 Aug 2011 16:16:21 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de>, <EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: John C Klensin <john-ietf@jck.com>, Bill McQuillan <McQuilWP@pobox.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 14:22:53 -0000

On 2011-08-04 16:11, Worley, Dale R (Dale) wrote:
>>>>> From: Hector Santos
>>>>> I would like to propose that new I-D submissions include
>>>>> information about the existence of a Working Group, if any,
>>>>> and/or discussion group list address, if any, for to join
>>>>> and participate in the development of the I-D or simply to
>>>>> follow it.
>
> We already have mechanisms like this in place.  Most I-Ds include the
> relevant WG in their name, and the extremely popular XML2RFC format
> has a<workgroup>  element for specifying the relevant WG.  And the I-D
> submission tool checks that field.  (I just got bitten by that.)  The

Since when does the ID submission tool check the XML???

> XML2RFC tool carries the<workgroup>  value into the page headers of
> the text form (at least in some circumstances).
>
> Once one knows the WG name, one can go through www.ietf.org to find
> the information about the WG, including its mailing list.  (Though one
> has to know some lore to do this successfully.)

Indeed.

 > ...

Best regards, Julian

From dhc2@dcrocker.net  Thu Aug  4 07:54:45 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F0A621F8AEE for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:54:45 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YNiLm7SmXyS for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 07:54:44 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EC1D721F8AEA for <ietf@ietf.org>; Thu,  4 Aug 2011 07:54:44 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p74Essrc021281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 4 Aug 2011 07:54:59 -0700
Message-ID: <4E3AB2B8.6080501@dcrocker.net>
Date: Thu, 04 Aug 2011 07:54:48 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de>, <EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 04 Aug 2011 07:55:00 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 14:54:45 -0000

On 8/4/2011 7:11 AM, Worley, Dale R (Dale) wrote:
> Once one knows the WG name,


And when there is no working group that the document is associated with?

In addition, there is a certain degree of exclusionary culture that comes with a 
requirement that a new reader know how to derive a mailing list address from a 
cryptic working group reference or go through the work to find it.

One might argue that this is a test of their resolve and that we want to filter 
against overly casual participation, but that seems an odd bit of logic.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From hsantos@isdg.net  Thu Aug  4 08:10:13 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C66621F8AF7 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 08:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.005
X-Spam-Level: 
X-Spam-Status: No, score=-3.005 tagged_above=-999 required=5 tests=[AWL=-1.328, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qX03mWlpORmx for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 08:10:12 -0700 (PDT)
Received: from ftp.catinthebox.net (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7F39721F8AE4 for <ietf@ietf.org>; Thu,  4 Aug 2011 08:10:12 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1159; t=1312470579; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=rRrjWFjDGp5IclTNTjD+8vN6Rx8=; b=nxlsnvtTUupjyV4IPBr/ 4ldQzn0q/VRnt5y4KX98UJkFp55QPurc/FpMLS5tlVAda6G7zN1R6ZQJQJ5D7ny8 ZeXupjaeA3/1QFfRQFJbzlUAh/7gyTB1mXXtonpIsXN0nfFsN6p4dWS+e1mW4Njv GcTUmVObEcqAUaqIyDns6rE=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 04 Aug 2011 11:09:39 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer); 
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 926043296.36138.5552; Thu, 04 Aug 2011 11:09:19 -0400
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312470285; h=Received:Received:Message-ID: Date:From:Organization:Subject:To:List-ID; bh=nlMa1WVT/19ngQhK+r Qn1N0qWOF3nTgbE5VfL77wEYA=; b=G69oj7PgWnJgAYGeyYaafCdWp7no5Rj97F lGh+KMCD2O/mPRQ+Wt57hBOigqYX69Sk8HMf0UHC9r9Rr2BwWY8WlksSUy0tEnBx LpwTWxN68PLwukbv9N/57LGr8sAXc/7Q44NYFmHhe0BPL+9tHo1cdvpV4K0YSTrD ke/wj6ykc=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 04 Aug 2011 11:04:45 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1897324471.855.6500; Thu, 04 Aug 2011 11:04:45 -0400
Message-ID: <4E3AB642.3070208@isdg.net>
Date: Thu, 04 Aug 2011 11:09:54 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com>	<4E3A5A1E.8050002@gmx.de>, <EA34AC5BC8D9995010AB7429@PST.JCK.COM>	<CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com> <4E3AB2B8.6080501@dcrocker.net>
In-Reply-To: <4E3AB2B8.6080501@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 15:10:13 -0000

I don't know if there is a need for "template" changes or some formal 
section in the write up, but it would seem to me that an author who 
has reached a level of getting WG assigned and/or even started a 
mailing list (IETF or otherwise) would be very eager to announce it in 
a new I-D (01?) submission.  But then again, I can imagine some that 
don't wish to expose this for whatever reason, perhaps to keep the 
"team" light (and private) until they feel its ready public work - or 
not.

-- 
Hector Santos, CTO
http://www.santronics.com


Dave CROCKER wrote:
> 
> 
> On 8/4/2011 7:11 AM, Worley, Dale R (Dale) wrote:
>> Once one knows the WG name,
> 
> 
> And when there is no working group that the document is associated with?
> 
> In addition, there is a certain degree of exclusionary culture that 
> comes with a requirement that a new reader know how to derive a mailing 
> list address from a cryptic working group reference or go through the 
> work to find it.
> 
> One might argue that this is a test of their resolve and that we want to 
> filter against overly casual participation, but that seems an odd bit of 
> logic.
> 
> d/







From ietfdbh@comcast.net  Wed Aug  3 13:45:28 2011
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7DD11E8090 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 13:45:28 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNeL9isPzPs6 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 13:45:27 -0700 (PDT)
Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0609E11E8094 for <ietf@ietf.org>; Wed,  3 Aug 2011 13:45:27 -0700 (PDT)
Received: from omta24.emeryville.ca.mail.comcast.net ([76.96.30.92]) by qmta10.emeryville.ca.mail.comcast.net with comcast id FwgM1h0091zF43QAAwlcGV; Wed, 03 Aug 2011 20:45:36 +0000
Received: from davidPC ([67.189.235.106]) by omta24.emeryville.ca.mail.comcast.net with comcast id FwkW1h00Y2JQnJT8kwkXwY; Wed, 03 Aug 2011 20:44:35 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <carlberg@g11.org.uk>, "'Stephen Hanna'" <shanna@juniper.net>
References: <20110726104135.13472eudbij0eaqs@portland.eukhosting.net><AC6674AB7BC78549BB231821ABF7A9AEB674516F2B@EMBX01-WF.jnpr.net> <20110726112346.35893ibie0kwerqc@portland.eukhosting.net>
In-Reply-To: <20110726112346.35893ibie0kwerqc@portland.eukhosting.net>
Subject: RE: [secdir] secdir review of draft-ietf-dime-priority-avps-04
Date: Wed, 3 Aug 2011 16:45:24 -0400
Message-ID: <72EB8D918E1340B78140B407CFDF8BAE@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7601.17609
Thread-index: AcxLhz1rdtZ6yE5iS46ImQV7TaxW6gGgZf0Q
X-Mailman-Approved-At: Thu, 04 Aug 2011 09:43:53 -0700
Cc: lionel.morand@orange-ftgroup.com, draft-ietf-dime-priority-avps.all@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 20:45:28 -0000

Hi,

Documents containing MIB modules must include a discussion of the
sensitivity of the tables/objects in the MIB module. This includes the
possible impact to the managed technologies that could be caused by an
unauthorized or misguided change to a configuration, for example.
Certainly the potential impact of using MIB objects to change the
relative priority of a managed technology's sessions would need to be
included in the read-write security considerations of the MIB module.
See https://svn.tools.ietf.org/area/ops/trac/wiki/mib-security

Using AVPs in Diameter to affect a similar change to the relative
priority of a managed technology's sessions warrants a similar
consideration of the sensitivity of the specific AVPs.   

David Harrington
Director, IETF Transport Area
Member of SECDIR, OPSDIR, and MIB Doctors directorates
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

> -----Original Message-----
> From: secdir-bounces@ietf.org 
> [mailto:secdir-bounces@ietf.org] On Behalf Of carlberg@g11.org.uk
> Sent: Tuesday, July 26, 2011 7:24 AM
> To: Stephen Hanna
> Cc: lionel.morand@orange-ftgroup.com; 
> draft-ietf-dime-priority-avps.all@tools.ietf.org; 
> ietf@ietf.org; secdir@ietf.org
> Subject: Re: [secdir] secdir review of 
> draft-ietf-dime-priority-avps-04
> 
> Steve,
> 
> 
> Quoting Stephen Hanna <shanna@juniper.net>:
> 
> > Thanks for your response, Ken.
> >
> > Removing the last sentence that you quoted would make things
worse.
> > Readers of this draft should definitely familiarize themselves
with
> > the security considerations related to priority. We should make
that
> > easier, not harder. The fact that those considerations also apply
to
> > other RFCs does not remove the fact that they apply to this 
> one also.
> 
> but those considerations do not directly apply to DIAMETER.
> 
> > You cannot publish a document whose security considerations
section
> > says (as this one effectively does today), "There are lots 
> of security
> > considerations related to this document. To understand them,
please
> > dig through all the referenced documents and figure it out 
> yourself."
> > Doing that digging and analysis is the job of the document
editors.
> 
> agreed, speaking in the general sense.  But again, the security  
> considerations of these other protocols do not apply to the 
> operation  
> of Diameter.
> 
> > In order to ease the burden on you, I think a reasonable
compromise
> > would be for YOU to review the documents referenced and decide
which
> > have the most relevant security considerations. Then you could
list
> > those explicitly in the last paragraph of the Security 
> Considerations.
> 
> I'm concerned about the implications of your recommendation.  If we

> extend this position to other work in the IETF, then efforts like  
> defining MIBs would mean that each MIB draft would need to perform a

> security considerations analysis of each protocol that an objects  
> refers to in the context of SNMP.  And one can extend the argument  
> that each protocol operating on top of TCP (and/or UDP) and IP would

> need to perform an analysis on how TCP/UDP and IP may affect 
> the upper  
> layer protocol.  We don't do that today.
> 
> cheers,
> 
> -ken
> 
> 
> _______________________________________________
> secdir mailing list
> secdir@ietf.org
> https://www.ietf.org/mailman/listinfo/secdir
> 


From rsk@gsp.org  Wed Aug  3 16:21:50 2011
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD3221F8770 for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:21:50 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DeeU1tjcwEf for <ietf@ietfa.amsl.com>; Wed,  3 Aug 2011 16:21:49 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id A8DA521F876F for <ietf@ietf.org>; Wed,  3 Aug 2011 16:21:49 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.113.dsl.charm.net [207.114.17.113]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id p73NLxOd024319 for <ietf@ietf.org>; Wed, 3 Aug 2011 19:22:01 -0400 (EDT)
Received: from vorlon.gsp.org (vorlon.gsp.org [192.168.0.20]) by squonk.gsp.org (8.14.3/8.14.3) with ESMTP id p73NQPcd017930 for <ietf@ietf.org>; Wed, 3 Aug 2011 19:26:25 -0400 (EDT)
Received: from localhost6.localdomain6 (localhost.localdomain [127.0.0.1]) by vorlon.gsp.org (8.14.3/8.14.3/Debian-9.2ubuntu1) with ESMTP id p73NLr16027105 for <ietf@ietf.org>; Wed, 3 Aug 2011 19:21:53 -0400
Received: (from rsk@localhost) by localhost6.localdomain6 (8.14.3/8.14.3/Submit) id p73NLp7N027099 for ietf@ietf.org; Wed, 3 Aug 2011 19:21:51 -0400
Date: Wed, 3 Aug 2011 19:21:51 -0400
From: Richard Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
Message-ID: <20110803232151.GA26475@gsp.org>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Thu, 04 Aug 2011 09:43:53 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 23:21:50 -0000

-1.

This list complies with RFC 2919, which alleviates the need for the
horrible, unscalable, obsolete, ugly kludge of Subject-line tags.
I suggest that anyone who really, *really* wants them on their copies
of messages arrange to have them added locally (perhaps by procmail or
similar) and not force them on those of us who have chosen mail processing
software that correctly uses List-Id.

---rsk

From msk@cloudmark.com  Thu Aug  4 10:33:16 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB44521F8B46 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 10:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.634
X-Spam-Level: 
X-Spam-Status: No, score=-103.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hW+Uey2ANTEx for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 10:33:16 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 69DF621F8B01 for <ietf@ietf.org>; Thu,  4 Aug 2011 10:33:16 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 4 Aug 2011 10:33:31 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF Discussion <ietf@ietf.org>
Date: Thu, 4 Aug 2011 10:33:29 -0700
Subject: RE: I-D Working groups and mailing list
Thread-Topic: I-D Working groups and mailing list
Thread-Index: AcxShYPENAfWKET7R0GKovCSjeOeaAARvnbw
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF57A@EXCH-C2.corp.cloudmark.com>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com>	<4E3A5A1E.8050002@gmx.de> <20110804090412.GC6118@x27.adm.denic.de>
In-Reply-To: <20110804090412.GC6118@x27.adm.denic.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 17:33:17 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of P=
eter Koch
> Sent: Thursday, August 04, 2011 2:04 AM
> To: IETF Discussion
> Subject: Re: I-D Working groups and mailing list
>=20
> I-D announcements are already copied to the relevant WG for WG drafts.
> Non-WG drafts may have the WG name in between '-' in the filename,
> allowing an easy identification of the WG the author thinks the draft is
> relevant to. A discussion mailing list is not mandatory for a draft
> and it could be that the author is still looking.  As a courtesy to
> the reader, i've used this kind of hint in the past where applicable.
> But please, let us not add another mandatory boilerplate piece of text.

+1.  I don't agree that there's a problem to solve here.  The IESG is alrea=
dy in place to prevent end-runs around established procedure or conflicts w=
ith active working groups.

From stpeter@stpeter.im  Thu Aug  4 10:36:51 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4E321F8BD5 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 10:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.667
X-Spam-Level: 
X-Spam-Status: No, score=-102.667 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THWo-xrQjIzw for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 10:36:51 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id F164B21F8BB6 for <ietf@ietf.org>; Thu,  4 Aug 2011 10:36:50 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B7D5C413A1; Thu,  4 Aug 2011 11:38:29 -0600 (MDT)
Message-ID: <4E3AD8C1.2060907@stpeter.im>
Date: Thu, 04 Aug 2011 11:37:05 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: New Non-WG Mailing List: happiana -- IETF/W3C/IANA Registry Happiness
References: <20110803185436.C266E11E808C@ietfa.amsl.com> <CAF4+nEFfYXJBqJauPrSFddtoi0cVXS9vWf-KQWr7KQRLqcAo3A@mail.gmail.com> <4E39A789.6070109@stpeter.im>
In-Reply-To: <4E39A789.6070109@stpeter.im>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 17:36:51 -0000

On 8/3/11 1:54 PM, Peter Saint-Andre wrote:
> On 8/3/11 1:49 PM, Donald Eastlake wrote:
>> Why can't we get informative explanations of what problem non-WG
>> mailing lists are trying to address?
>>>
>>> Purpose: This list is for discussion of IANA Registry issues to
>>> result in Happy IETF, Happy W3C, and Happy IANA.
> 
> Various folks have found it difficult to do things like register new
> media types. There's been discussion among a small group of people to
> streamline those processes (getting ADs out of the way, improving the
> interface to IANA, etc.). The list started out as a small, private
> design team and is now being opened to wider participation.

To be 100% clear, the difficulties that some folks have reported are
decidedly *not* limited to media types. Those working on the happiana
"design team" are looking into the possibility of "bis" documents
regarding registration procedures for URI schemes (RFC 4395), link
relations (RFC 5988), media types (RFC 4288), header fields (RFC 3864)
primarily for HTTP, and perhaps others. It might be that some of the
reported difficulties are more a matter of perception than of reality.
It might be that the relevant Area Directors (mostly in apps) need to
get out of the way so that SDOs wanting to register things in the
standards tree can interface directly with IANA. And so on. If you are
are interested in these issues, please join the discussion on the
happiana@ietf.org list:

https://www.ietf.org/mailman/listinfo/happiana

Thanks.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From msk@cloudmark.com  Thu Aug  4 10:38:21 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 921AD11E8089 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 10:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.634
X-Spam-Level: 
X-Spam-Status: No, score=-103.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P5KaV0r4L+Su for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 10:38:21 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 2D69C11E8077 for <ietf@ietf.org>; Thu,  4 Aug 2011 10:38:21 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 4 Aug 2011 10:38:33 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 4 Aug 2011 10:38:32 -0700
Subject: RE: I-D Working groups and mailing list
Thread-Topic: I-D Working groups and mailing list
Thread-Index: AcxSuKqjqejXmoC5T1qZrggQ+5RhGAAFCSnA
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com>	<4E3A5A1E.8050002@gmx.de>, <EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com> <4E3AB2B8.6080501@dcrocker.net> <4E3AB642.3070208@isdg.net>
In-Reply-To: <4E3AB642.3070208@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 17:38:21 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of H=
ector Santos
> Sent: Thursday, August 04, 2011 8:10 AM
> To: ietf@ietf.org
> Cc: ietf@ietf.org
> Subject: Re: I-D Working groups and mailing list
>=20
> I don't know if there is a need for "template" changes or some formal
> section in the write up, but it would seem to me that an author who
> has reached a level of getting WG assigned and/or even started a
> mailing list (IETF or otherwise) would be very eager to announce it in
> a new I-D (01?) submission.  But then again, I can imagine some that
> don't wish to expose this for whatever reason, perhaps to keep the
> "team" light (and private) until they feel its ready public work - or
> not.

OK, now I *really* don't know what the proposal is.

If we're not creating something formal, then the rules/procedures we have i=
n place now are sufficient.  Those are:

If a WG has been created and "owns" the document, then the document has the=
 WG name in its filename and usually says the name of the working group at =
the top of the first page.

If it's an individual submission associated with a working group, it has th=
e first of those two.

If it's an individual submission not tracking a working group, the work may=
 or may not benefit from some explicit association, and none is required.

In any case, I'm now quite confused about what change is being proposed her=
e.


From krishnabirth@gmail.com  Thu Aug  4 11:42:33 2011
Return-Path: <krishnabirth@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 694AC11E80C8 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 11:42:33 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVDdb7FK7Hru for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 11:42:33 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id E229111E80C0 for <ietf@ietf.org>; Thu,  4 Aug 2011 11:42:32 -0700 (PDT)
Received: by yie30 with SMTP id 30so1444120yie.31 for <ietf@ietf.org>; Thu, 04 Aug 2011 11:42:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=zWzMA3qB1ibKhjPb5NMrxNe8fq0ACrkikS8NRCutmyw=; b=jjsMYDauV9PwV6QOI4F/I+0tHztLBnetpIm8G9qn2MVD/8MgkV8ZCAv5keeN1Fgp8I odwL974uG0BFN1GzfbzBIFqSRn0R00+eFoG9a67dFiF/SJW4lvUYK3eyWpyFvbT3GsUv iRUdaX9xLjPLjfdQdmjtfrpdrT3fpHIjzGkj4=
MIME-Version: 1.0
Received: by 10.236.200.168 with SMTP id z28mr1646781yhn.331.1312483367240; Thu, 04 Aug 2011 11:42:47 -0700 (PDT)
Received: by 10.236.105.199 with HTTP; Thu, 4 Aug 2011 11:42:47 -0700 (PDT)
Date: Thu, 4 Aug 2011 18:42:47 +0000
Message-ID: <CAHRyTMMNj7vpXMaoZ1x4hGBVUBqDYDSJN_MUu+unbuTHGh5mHw@mail.gmail.com>
Subject: Is BIOS in the IETF scope?
From: Krishna Birth <krishnabirth@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 18:42:33 -0000

Does IETF in it's scope deal with the BIOS on the hardware?  Sorry if
I am off-topic.  Perhaps there are some bright engineers  reading this
that could help.

I am prepared to offer 200 euros  if any engineer alters the BIOS
fonts to a font that I prefer using opensource, ?Coreboot.  I am not a
techie and I believe this is a reasonable project and thus I would
need easy to follow instructions (YouTube video being posted?) and
sending in the mail the corrected BIOS chip -- more discussion on this
would be required and I would need this as downloadable and covering
the necessary hardware specs for all users and support (through
payment) as things evolve.



Regards


Meeku

From hsantos@isdg.net  Thu Aug  4 18:32:29 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92F9521F885A for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 18:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.426
X-Spam-Level: 
X-Spam-Status: No, score=-3.426 tagged_above=-999 required=5 tests=[AWL=-0.827, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PppvgPzWndI1 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 18:32:28 -0700 (PDT)
Received: from dkim.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7879421F8867 for <ietf@ietf.org>; Thu,  4 Aug 2011 18:32:27 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2163; t=1312507955; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=5MwQUKXb8Xkp9naIri2AsQNpNgw=; b=gch01SBnbx3KZ6xWwNak NcFve8Y3iPSP7O/gZI93cWHltGyL72+VM+PTYGMXfrc1fwD28xb/t7BOyduK+gJZ RSdZZOHjnHwhNbzava+rV+XJHRNB7KdVe7ghMJSh1PRV0YyTpKjzUpsyS99mbBqK PX2mAZiaTTN5/Ec4pxBAA9s=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 04 Aug 2011 21:32:35 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=isdg.net header.s=tms1 header.i=isdg.net;  adsp=pass policy=all author.d=isdg.net signer.d=isdg.net (originating signer); 
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 963383867.36983.5928; Thu, 04 Aug 2011 21:31:40 -0400
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312507626; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=byeNa5lQAi9DaZpLE8 RulbxFscaii8URVO6Ya85SxqA=; b=d/RKfc4uCwSN/9kIYmSVxSu37Ww58JGH73 U3MghoczexSY3DrK2BgwEQkaInetvBQaaKCly7KAv/CFX6Q+8MLdzuh8zNx3nHFv /d0m8rt6no+h4qJsyBY6sTBfw3Al1iwLcwfuFwNOWzIoccMLMYEkt9Bsv3FEckwf Kz9Q3ECgE=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 04 Aug 2011 21:27:06 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1934664455.1106.6660; Thu, 04 Aug 2011 21:27:05 -0400
Message-ID: <4E3B481F.5030702@isdg.net>
Date: Thu, 04 Aug 2011 21:32:15 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net>	<1568238908.20110804001138@pobox.com>	<4E3A5A1E.8050002@gmx.de>, <EA34AC5BC8D9995010AB7429@PST.JCK.COM>	<CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com>	<4E3AB2B8.6080501@dcrocker.net> <4E3AB642.3070208@isdg.net> <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 01:32:29 -0000

How my suggestion was to be done, I left as open ended for the IETF 
vets to consider if it makes sense, how its done and/or if already 
provided, maybe highlight that info. Whatever. But most of all, I was 
mostly suggesting a technical writing style or helpful guideline to 
authors to consider. Those who thinks it benefits readers will add the 
info when possible.  Those who don't, well, won't.

Not a big deal.

Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Hector Santos
>> Sent: Thursday, August 04, 2011 8:10 AM
>> To: ietf@ietf.org
>> Cc: ietf@ietf.org
>> Subject: Re: I-D Working groups and mailing list
>>
>> I don't know if there is a need for "template" changes or some formal
>> section in the write up, but it would seem to me that an author who
>> has reached a level of getting WG assigned and/or even started a
>> mailing list (IETF or otherwise) would be very eager to announce it in
>> a new I-D (01?) submission.  But then again, I can imagine some that
>> don't wish to expose this for whatever reason, perhaps to keep the
>> "team" light (and private) until they feel its ready public work - or
>> not.
> 
> OK, now I *really* don't know what the proposal is.
> 
> If we're not creating something formal, then the rules/procedures we have in place now are sufficient.  Those are:
> 
> If a WG has been created and "owns" the document, then the document has the WG name in its filename and usually says the name of the working group at the top of the first page.
> 
> If it's an individual submission associated with a working group, it has the first of those two.
> 
> If it's an individual submission not tracking a working group, the work may or may not benefit from some explicit association, and none is required.
> 
> In any case, I'm now quite confused about what change is being proposed here.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From phdgang@gmail.com  Thu Aug  4 19:55:31 2011
Return-Path: <phdgang@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B2321F866A; Thu,  4 Aug 2011 19:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.254
X-Spam-Level: 
X-Spam-Status: No, score=-3.254 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IlYZYRrjoF+P; Thu,  4 Aug 2011 19:55:30 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 50E3721F859F; Thu,  4 Aug 2011 19:55:30 -0700 (PDT)
Received: by vws12 with SMTP id 12so1205745vws.31 for <multiple recipients>; Thu, 04 Aug 2011 19:55:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dWqnDSSNTlSyWppiuKPD0X3NdfHc0UdcsH2aBxMr4rg=; b=E9JUw/Gp/xSaGw0XdAtl+rPsEpryScFSD1ASNJCWOp0YWdgBDmP/yJaCdZ1Xt1kd0l KP0JeqY5xKDSMSyLy3eCX66hpW0g/TuCG/sefj1cRBcgar4F6YObyem8ewkOZ+Eavx6z EGc7ob+dvp1NRjz6jEMylU5+RNMB7uttqDNZU=
MIME-Version: 1.0
Received: by 10.52.177.195 with SMTP id cs3mr1652697vdc.185.1312512946318; Thu, 04 Aug 2011 19:55:46 -0700 (PDT)
Received: by 10.52.169.129 with HTTP; Thu, 4 Aug 2011 19:55:46 -0700 (PDT)
In-Reply-To: <20110801190301.16571.58632.idtracker@ietfa.amsl.com>
References: <20110801190301.16571.58632.idtracker@ietfa.amsl.com>
Date: Fri, 5 Aug 2011 10:55:46 +0800
Message-ID: <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-3gpp-eps-03.txt> (IPv6 in 3GPP Evolved Packet System) to Informational RFC
From: GangChen <phdgang@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: v6ops@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 02:55:31 -0000

Hello Authors,

I think it is worth adding some texts to describe mobile CPE case, in
which CPEs with wireless modem use 3GPP access as uplink.

Gang


2011/8/2, The IESG <iesg-secretary@ietf.org>:
>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'IPv6 in 3GPP Evolved Packet System'
>   <draft-ietf-v6ops-3gpp-eps-03.txt> as an Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-08-15. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    Use of data services in smart phones and broadband services via HSPA
>    and HSPA+, in particular Internet services, has increased rapidly and
>    operators that have deployed networks based on 3GPP network
>    architectures are facing IPv4 address shortages at the Internet
>    registries and are feeling a pressure to migrate to IPv6.  This
>    document describes the support for IPv6 in 3GPP network
>    architectures.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

From narten@us.ibm.com  Thu Aug  4 21:53:01 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3395A21F8564 for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 21:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level: 
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YKcTFsQej+Wk for <ietf@ietfa.amsl.com>; Thu,  4 Aug 2011 21:53:00 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF1321F8563 for <ietf@ietf.org>; Thu,  4 Aug 2011 21:52:58 -0700 (PDT)
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by e9.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p754KAHA018582 for <ietf@ietf.org>; Fri, 5 Aug 2011 00:20:10 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p754r4rZ131628 for <ietf@ietf.org>; Fri, 5 Aug 2011 00:53:06 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p754r3EK018331 for <ietf@ietf.org>; Fri, 5 Aug 2011 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p754r3Yw018321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 5 Aug 2011 01:53:03 -0300
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 p754r3Sl029265 for <ietf@ietf.org>; Fri, 5 Aug 2011 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p754r23b029192 for ietf@ietf.org; Fri, 5 Aug 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201108050453.p754r23b029192@rotala.raleigh.ibm.com>
Date: Fri, 05 Aug 2011 00:53:02 -0400
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 04:53:01 -0000

Total of 239 messages in the last 7 days.
 
script run at: Fri Aug  5 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.44% |   13 |  7.08% |   112663 | hsantos@isdg.net
  6.28% |   15 |  5.61% |    89298 | moore@network-heretics.com
  5.86% |   14 |  5.04% |    80276 | dhc2@dcrocker.net
  3.77% |    9 |  3.06% |    48648 | msk@cloudmark.com
  3.35% |    8 |  2.55% |    40544 | stpeter@stpeter.im
  2.51% |    6 |  3.28% |    52218 | john-ietf@jck.com
  2.93% |    7 |  2.66% |    42416 | despres.remi@laposte.net
  2.51% |    6 |  2.37% |    37723 | brian.e.carpenter@gmail.com
  2.09% |    5 |  2.52% |    40075 | daedulus@btconnect.com
  1.67% |    4 |  2.62% |    41778 | jmh@joelhalpern.com
  2.09% |    5 |  2.03% |    32312 | michel@arneill-py.sacramento.ca.us
  2.09% |    5 |  1.85% |    29513 | joelja@bogus.com
  2.09% |    5 |  1.82% |    29048 | johnl@iecc.com
  2.09% |    5 |  1.69% |    26909 | pch-ietf@u-1.phicoh.com
  1.67% |    4 |  1.72% |    27404 | housley@vigilsec.com
  1.67% |    4 |  1.64% |    26121 | eburger-l@standardstrack.com
  1.67% |    4 |  1.47% |    23361 | john@jlc.net
  1.26% |    3 |  1.78% |    28340 | hallam@gmail.com
  1.67% |    4 |  1.34% |    21403 | hartmans-ietf@mit.edu
  1.26% |    3 |  1.46% |    23211 | sm@resistor.net
  1.26% |    3 |  1.15% |    18228 | tnadeau@lucidvision.com
  1.26% |    3 |  1.06% |    16839 | ajs@anvilwalrusden.com
  1.26% |    3 |  1.05% |    16689 | mcr@sandelman.ca
  0.84% |    2 |  1.34% |    21385 | framefritti@gmail.com
  1.26% |    3 |  0.92% |    14684 | pk@isoc.de
  0.84% |    2 |  1.05% |    16772 | nsb@guppylake.com
  0.84% |    2 |  1.02% |    16204 | presnick@qualcomm.com
  0.84% |    2 |  0.85% |    13537 | tony@att.com
  0.84% |    2 |  0.83% |    13152 | mrw@lilacglade.org
  0.84% |    2 |  0.82% |    13096 | hkaplan@acmepacket.com
  0.84% |    2 |  0.80% |    12776 | tglassey@earthlink.net
  0.84% |    2 |  0.80% |    12754 | mra@pobox.com
  0.84% |    2 |  0.78% |    12467 | barryleiba@computer.org
  0.84% |    2 |  0.77% |    12310 | ole@cisco.com
  0.84% |    2 |  0.76% |    12171 | scott@kitterman.com
  0.84% |    2 |  0.75% |    11865 | scott.brim@gmail.com
  0.84% |    2 |  0.75% |    11863 | ggm+ietf@apnic.net
  0.84% |    2 |  0.74% |    11743 | evnikita2@gmail.com
  0.84% |    2 |  0.72% |    11497 | vesely@tana.it
  0.84% |    2 |  0.72% |    11454 | dworley@avaya.com
  0.84% |    2 |  0.70% |    11117 | mohta@necom830.hpcl.titech.ac.jp
  0.84% |    2 |  0.70% |    11078 | david.kessens@nsn.com
  0.84% |    2 |  0.66% |    10547 | julian.reschke@gmx.de
  0.42% |    1 |  0.97% |    15362 | lars.eggert@nokia.com
  0.42% |    1 |  0.96% |    15221 | ron.even.tlv@gmail.com
  0.42% |    1 |  0.84% |    13382 | sob@harvard.edu
  0.42% |    1 |  0.80% |    12743 | narten@us.ibm.com
  0.42% |    1 |  0.78% |    12353 | marshall.eubanks@gmail.com
  0.42% |    1 |  0.71% |    11253 | akatlas@gmail.com
  0.42% |    1 |  0.68% |    10828 | tobias.gondrom@gondrom.org
  0.42% |    1 |  0.66% |    10452 | marka@isc.org
  0.42% |    1 |  0.64% |    10113 | maurice@tehcorner.com
  0.42% |    1 |  0.60% |     9496 | rogerj@gmail.com
  0.42% |    1 |  0.58% |     9199 | fred.l.templin@boeing.com
  0.42% |    1 |  0.57% |     9151 | jordi.palet@consulintel.es
  0.42% |    1 |  0.52% |     8321 | huitema@microsoft.com
  0.42% |    1 |  0.51% |     8098 | ietfdbh@comcast.net
  0.42% |    1 |  0.49% |     7859 | bew@cisco.com
  0.42% |    1 |  0.48% |     7700 | nishida@sfc.wide.ad.jp
  0.42% |    1 |  0.48% |     7688 | aallen@rim.com
  0.42% |    1 |  0.48% |     7569 | alexandru.petrescu@gmail.com
  0.42% |    1 |  0.46% |     7355 | jeroen@unfix.org
  0.42% |    1 |  0.45% |     7166 | richard@shockey.us
  0.42% |    1 |  0.43% |     6881 | randy@qualcomm.com
  0.42% |    1 |  0.41% |     6548 | dimitri.papadimitriou@alcatel-lucent.com
  0.42% |    1 |  0.41% |     6481 | otroan@employees.org
  0.42% |    1 |  0.40% |     6400 | bob.hinden@gmail.com
  0.42% |    1 |  0.40% |     6381 | dcrocker@gmail.com
  0.42% |    1 |  0.40% |     6326 | petithug@acm.org
  0.42% |    1 |  0.39% |     6210 | ned+ietf@mauve.mrochek.com
  0.42% |    1 |  0.39% |     6195 | phdgang@gmail.com
  0.42% |    1 |  0.39% |     6181 | wjhns1@hardakers.net
  0.42% |    1 |  0.38% |     6115 | lear@cisco.com
  0.42% |    1 |  0.38% |     6112 | r.e.sonneveld@sonnection.nl
  0.42% |    1 |  0.38% |     6088 | rja.lists@gmail.com
  0.42% |    1 |  0.38% |     6034 | randy_presuhn@mindspring.com
  0.42% |    1 |  0.36% |     5803 | john_brzozowski@cable.comcast.com
  0.42% |    1 |  0.36% |     5776 | paul.hoffman@vpnc.org
  0.42% |    1 |  0.36% |     5721 | mcquilwp@pobox.com
  0.42% |    1 |  0.36% |     5698 | gwz@net-zen.net
  0.42% |    1 |  0.35% |     5615 | john@jck.com
  0.42% |    1 |  0.35% |     5614 | d3e3e3@gmail.com
  0.42% |    1 |  0.35% |     5500 | mnot@mnot.net
  0.42% |    1 |  0.34% |     5470 | mail@sabahattin-gucukoglu.com
  0.42% |    1 |  0.34% |     5453 | adam@nostrum.com
  0.42% |    1 |  0.34% |     5334 | ynir@checkpoint.com
  0.42% |    1 |  0.33% |     5331 | jari.arkko@piuha.net
  0.42% |    1 |  0.33% |     5319 | adrian@olddog.co.uk
  0.42% |    1 |  0.33% |     5275 | derhoermi@gmx.net
  0.42% |    1 |  0.33% |     5236 | christer.holmberg@ericsson.com
  0.42% |    1 |  0.33% |     5209 | spencer@wonderhamster.org
  0.42% |    1 |  0.33% |     5178 | dwm@xpasc.com
  0.42% |    1 |  0.32% |     5112 | dave@cridland.net
  0.42% |    1 |  0.32% |     5019 | rsk@gsp.org
  0.42% |    1 |  0.31% |     4976 | krishnabirth@gmail.com
  0.42% |    1 |  0.31% |     4884 | suresh.krishnan@ericsson.com
  0.42% |    1 |  0.31% |     4867 | chris.newman@oracle.com
  0.42% |    1 |  0.30% |     4833 | touch@isi.edu
  0.42% |    1 |  0.30% |     4814 | jaap@nlnetlabs.nl
  0.42% |    1 |  0.30% |     4814 | dougb@dougbarton.us
  0.42% |    1 |  0.30% |     4810 | mrex@sap.com
  0.42% |    1 |  0.30% |     4741 | warren@kumari.net
  0.42% |    1 |  0.29% |     4650 | ekr@rtfm.com
--------+------+--------+----------+------------------------
100.00% |  239 |100.00% |  1591802 | Total

From julian.reschke@gmx.de  Fri Aug  5 01:45:19 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D677821F87F0 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 01:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.157
X-Spam-Level: 
X-Spam-Status: No, score=-104.157 tagged_above=-999 required=5 tests=[AWL=-1.558, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJa0oqojxgbR for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 01:45:19 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id C3B5F21F87E2 for <ietf@ietf.org>; Fri,  5 Aug 2011 01:45:18 -0700 (PDT)
Received: (qmail invoked by alias); 05 Aug 2011 08:45:32 -0000
Received: from p508FDEBF.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.222.191] by mail.gmx.net (mp022) with SMTP; 05 Aug 2011 10:45:32 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+8n75Ve0K8l7uH5tnLhCERoADY9Eca5pic4/6/Wj vx7VxPByAVyzjh
Message-ID: <4E3BADA7.9020404@gmx.de>
Date: Fri, 05 Aug 2011 10:45:27 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net>, <1568238908.20110804001138@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F57E0@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F57E0@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: Bill McQuillan <McQuilWP@pobox.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 08:45:19 -0000

On 2011-08-04 16:12, Worley, Dale R (Dale) wrote:
>> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Bill McQuillan [McQuilWP@pobox.com]
>>
>> Perhaps it could be included in the ID-Announce message.
>
> In a lot of situations, the I-D submission tool knows the name of the relevant working group
> and could include its mailing list address in the announcement automatically.
> ...

...which of course does only help those readers who get to the ID via 
the announcement.

In my experience, many ID authors actually forget to consider where to 
send feedback. Thus making this something to be checked upon ID 
submission (maybe with a way to opt-out) might be helpful.

Best regards, Julian

From sm@resistor.net  Fri Aug  5 02:50:17 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3079721F87F0 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 02:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNf0K-fDUhpI for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 02:50:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 07CC321F85C7 for <ietf@ietf.org>; Fri,  5 Aug 2011 02:50:05 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p759o8t3010689;  Fri, 5 Aug 2011 02:50:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1312537813; bh=TPre7mZH5ol4gT8Ylpm1+5N8087kSH2FNG3WnF5N6mg=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=sHrOxk8/K1tX6ftPnt7oRRwcNUKrd4BRADYoRtNojxbJkSqqPNTK4HyNvLPzHITPq 2tv6XlN1GusxyddorlB6adonHgPfhLCErS9BaczeuvYtbubfZi1pKRbs/1LZeGMQRq BCBp3+kZyKOAcE7NEQyNTyEw5ge+DS4fpMaluXU8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1312537813; bh=TPre7mZH5ol4gT8Ylpm1+5N8087kSH2FNG3WnF5N6mg=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=ERPpVVHeJ6x+pUV6biPNzJ9Gaf3yOkHmDHiAg7cZfVbSqkZb9pd3oFlj/O9GS3Lip T9mHFPXs2BR0wbbw9vJYjMy6hDjnLHY6jVRFjVNLkPQHCWvXgpHavYjwDSjoTSKiJW 3+08YWY77S9LHyWlJ8DcGtBQOLPrQ9VxDTH97goY=
Message-Id: <6.2.5.6.2.20110804043544.084eb5c0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 05 Aug 2011 02:45:10 -0700
To: Russ Housley <housley@vigilsec.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
In-Reply-To: <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 09:50:17 -0000

Hi Russ,
At 12:28 PM 8/3/2011, Russ Housley wrote:
>I am well aware of the implementation reports.  The premise here is 
>that the protocol specification is "good enough" there are at least 
>two interoperable implementations and the protocol is deployed 
>widely.  The implementation report would become optional.

One of the advantages of an implementation report is that it provides 
a statement about interoperability between two or more known 
implementations.  If there is any dispute about that claim, it can be 
resolved in a non-controversial way.  Determining whether a protocol 
is widely deployed is not always a clear-cut decision.

>People are not doing many implementation reports.  As you say above, 
>there are only about 75 of them.  How many protocols are documented 
>in RFCs?  That is a very low percentage in my view.

Yes, it's a very low percentage.  I don't have the figure for the 
number of protocols documented.  Given the low barrier for such 
reports, I would have expected to see more reports.  After all, if 
the RFC has been published, the protocol has been widely deployed, it 
should simply have been a matter of filing the short report.

 From draft-housley-two-maturity-levels-08:

    "this document measures interoperability through widespread deployment
     of multiple implementations from different code bases, thus condensing
     the two separate metrics into one."

This change is expected to solve the problem.  I am not convinced 
that the metrics is the problem.

>So, I see the cost quite differently.  Most protocols are published 
>as Proposed Standards, and they are never advanced.  I'm seeking a 
>process where implementation and deployment experience actually 
>improves the protocol specifications.  Today, that rarely happens, 
>and when it does, the

Agreed.

I didn't find any incentive to inject implementation and deployment 
experience into the process.

>This is an argument for the status quo.  We have decades of 
>experience with that not working.  That is essentially an argument 
>for a single maturity level; that is how the process is really working today.

I am not arguing for a single maturity level (the status quo).  I do 
not agree with the conclusion that the decades of stagnation is due 
to the three maturity level.

>This document is not about IESG review time, except for the 
>elimination of the requirement for annual reviews which are not done 
>anyway.  If that is what you get from the document, then I have done 
>a very poor job in writing it.  That is not the point at all.

I don't think that you did a poor job.  A three maturity level 
requires three IESG Evaluations.  A two maturity level requires two 
IESG Evaluations.  If more documents moved from Proposed Standard to 
the next level, it would obviously take more IESG review time.

I presume that the IESG will only use the following criteria for advancement:

  - two independent interoperating implementations with widespread
    deployment and successful operational experience

  - no errata against the specification

  - no unused features in the specification

And there won't be any DISCUSSes along the lines of:

   "I don't think the implementation reports are adequate for me to meet the
    requirements of 2026. It does not clearly identify what software 
was used or
    show support of each of the individual options and features."

   "Examples througout the document make use of non-example domains."

   "The implementation report is woefully inadequate to document there are
    interoperable implementations of all the features from two different
    code bases."

   "My Discuss was not addressed at all - I believe that the WG ignored the
    spirit of the implementation report requirement - my Discuss said that
    we should know that there are multiple implementations that have
    handled the significant changes in the recycling of this Draft Standard.
    The group apparently refused to update its implementation report"

Regards,
-sm 


From dhc2@dcrocker.net  Fri Aug  5 08:52:24 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31CAC21F8BF9 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 08:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.109
X-Spam-Level: 
X-Spam-Status: No, score=-5.109 tagged_above=-999 required=5 tests=[AWL=1.491,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZ3Nu4gFzYeq for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 08:52:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4D421F8B91 for <ietf@ietf.org>; Fri,  5 Aug 2011 08:52:23 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p75Fqams018091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 5 Aug 2011 08:52:41 -0700
Message-ID: <4E3C11BC.4030903@dcrocker.net>
Date: Fri, 05 Aug 2011 08:52:28 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I-D Working groups and mailing list
References: <4E3A1C51.4040908@isdg.net>, <1568238908.20110804001138@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F57E0@DC-US1MBEX4.global.avaya.com> <4E3BADA7.9020404@gmx.de>
In-Reply-To: <4E3BADA7.9020404@gmx.de>
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, 05 Aug 2011 08:52:41 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 15:52:24 -0000

On 8/5/2011 1:45 AM, Julian Reschke wrote:
> In my experience, many ID authors actually forget to consider where to send
> feedback. Thus making this something to be checked upon ID submission (maybe
> with a way to opt-out) might be helpful.

+1

When something is a routine expectation it is reasonable to build it into the 
model explicitly so that it (or its absence) can be detected structurally.

That said, the <note> construct works quite well, for those who remember to use 
it...

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From warren@kumari.net  Fri Aug  5 09:44:52 2011
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FB721F851A for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 09:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.387
X-Spam-Level: 
X-Spam-Status: No, score=-102.387 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5UE7VR9nOsZ4 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 09:44:52 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 26E4421F850E for <ietf@ietf.org>; Fri,  5 Aug 2011 09:44:51 -0700 (PDT)
Received: from dhcp-172-19-118-113.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id EC9B91B41540; Fri,  5 Aug 2011 12:45:08 -0400 (EDT)
Subject: Re: subject_prefix on IETF Discuss?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20110803232151.GA26475@gsp.org>
Date: Fri, 5 Aug 2011 12:45:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <20110803232151.GA26475@gsp.org>
To: Richard Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 16:44:52 -0000

On Aug 3, 2011, at 7:21 PM, Richard Kulawiec wrote:

>=20
> -1.
>=20
> This list complies with RFC 2919, which alleviates the need for the
> horrible, unscalable, obsolete, ugly kludge of Subject-line tags.
> I suggest that anyone who really, *really* wants them on their copies
> of messages arrange to have them added locally (perhaps by procmail or
> similar) and not force them on those of us who have chosen mail =
processing
> software that correctly uses List-Id.

Still a little confused how this morphed into a religious war on RFC =
2919 / List-Id.  I *did* mention in the original post that I had been =
using List-Id to organize mail -- which would lead to folders with a few =
thousands of unread mails, which I would then unceremoniously dump, =
because it was just too much to deal with..

Subject-line tags allow me to just drop everything in the inbox and =
then, at a glance figure out what to read, and in what order. I then =
move the read stuff (and that that I don't care about) into separate =
mailboxes.

For those who want to do the same (regardless of whether your religious =
views), this little bit of procmail woks for me, ymmv:

# Add an [IETF] to messages to the IETF list.
:0 fw
* ^List-Id:[ ].*\<ietf\.ietf\.org\>
|/bin/sed -e 's/^Subject:[ ]*/Subject: [IETF] /'




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


From gwz@net-zen.net  Fri Aug  5 00:46:12 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC66321F8B0A for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 00:46:12 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxmTkxhNHAu2 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 00:46:08 -0700 (PDT)
Received: from smtpauth01.prod.mesa1.secureserver.net (smtpauth01.prod.mesa1.secureserver.net [64.202.165.181]) by ietfa.amsl.com (Postfix) with SMTP id 9C21221F8B0C for <ietf@ietf.org>; Fri,  5 Aug 2011 00:46:08 -0700 (PDT)
Received: (qmail 32455 invoked from network); 5 Aug 2011 07:46:25 -0000
Received: from unknown (124.120.225.17) by smtpauth01.prod.mesa1.secureserver.net (64.202.165.181) with ESMTP; 05 Aug 2011 07:46:23 -0000
Message-ID: <4E3B9FC6.7090701@net-zen.net>
Date: Fri, 05 Aug 2011 14:46:14 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: bob.hinden@gmail.com
Subject: Queen Sirikit National Convention Center
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------080504080907030006080201"
X-Mailman-Approved-At: Fri, 05 Aug 2011 10:11:06 -0700
Cc: "Ole J. Jacobsen" <ole@cisco.com>, IETF Discussion <ietf@ietf.org>, odonoghue@iisoc.org, Henk Uijterwaal <henk@uijterwaal.nl>, tme@americafree.tv, Eric Burger <eburger@standardstrack.com>, st.amour@isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 07:46:13 -0000

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

I note that there is an opening on the IETF meeting calendar for an
Asian meeting in 2013.  Here is a suggestion:

Meeting Facilities:
http://www.qsncc.com/venue-information/our-facilities.html

There are 7 pages of "Official Hotels", starting at about $60/night.

Official Hotels: http://www.qsncc.com/visitor/official-hotels.html

--------------080504080907030006080201
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------080504080907030006080201--

From jounikor@gmail.com  Thu Aug  4 23:55:19 2011
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A034A11E8085; Thu,  4 Aug 2011 23:55:19 -0700 (PDT)
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_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOXEkHPj1NDu; Thu,  4 Aug 2011 23:55:19 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB2311E807F; Thu,  4 Aug 2011 23:55:18 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3134868fxe.31 for <multiple recipients>; Thu, 04 Aug 2011 23:55:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=bo3r2gvEr7T+Yws8RGXqWKGIEA/RdjMIRPUbwJMFF8o=; b=Bhm+GdW3mqpucuLGa+CYy0Yp6jGEIQvh/anehD2ZSWYfD8JM9Dlm5ioTrbUfbvhwy4 SEg1UEd8ZyM6rgiQ+BVBMI+ULXYLawG4mG7RbBFzcPjKVipFUb8+aeV0AqYJiR+q3erY BWRsJQhDVpe//GwIR8RNu4D+7cZGJuQ7SlLhc=
Received: by 10.204.142.143 with SMTP id q15mr589342bku.321.1312527334358; Thu, 04 Aug 2011 23:55:34 -0700 (PDT)
Received: from a88-114-68-66.elisa-laajakaista.fi (a88-114-68-66.elisa-laajakaista.fi [88.114.68.66]) by mx.google.com with ESMTPS id p24sm756251bkw.41.2011.08.04.23.55.32 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 04 Aug 2011 23:55:33 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-3gpp-eps-03.txt> (IPv6 in 3GPP Evolved Packet System) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Jouni <jounikor@gmail.com>
In-Reply-To: <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com>
Date: Fri, 5 Aug 2011 09:55:30 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <49A19FE6-7B0A-4876-8F1A-308F978CC8FC@gmail.com>
References: <20110801190301.16571.58632.idtracker@ietfa.amsl.com> <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1244.3)
X-Mailman-Approved-At: Fri, 05 Aug 2011 10:11:16 -0700
Cc: v6ops@ietf.org, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 06:55:19 -0000

Dear Gang,

I would be inclined to say that within the 3GPP scope the client is =
always the "UE" and its form factor or the end usage scenario does not =
really matter. It does not change the way the UE is expected to behave =
from the 3GPP system point of view, unless there is a new functional =
requirement from 3GPP.

- Jouni



On Aug 5, 2011, at 5:55 AM, GangChen wrote:

> Hello Authors,
>=20
> I think it is worth adding some texts to describe mobile CPE case, in
> which CPEs with wireless modem use 3GPP access as uplink.
>=20
> Gang
>=20
>=20
> 2011/8/2, The IESG <iesg-secretary@ietf.org>:
>>=20
>> The IESG has received a request from the IPv6 Operations WG (v6ops) =
to
>> consider the following document:
>> - 'IPv6 in 3GPP Evolved Packet System'
>>  <draft-ietf-v6ops-3gpp-eps-03.txt> as an Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2011-08-15. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>   Use of data services in smart phones and broadband services via =
HSPA
>>   and HSPA+, in particular Internet services, has increased rapidly =
and
>>   operators that have deployed networks based on 3GPP network
>>   architectures are facing IPv4 address shortages at the Internet
>>   registries and are feeling a pressure to migrate to IPv6.  This
>>   document describes the support for IPv6 in 3GPP network
>>   architectures.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From jounikor@gmail.com  Fri Aug  5 00:15:55 2011
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445385E800C; Fri,  5 Aug 2011 00:15:55 -0700 (PDT)
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_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HM5citeET4z4; Fri,  5 Aug 2011 00:15:54 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE745E8007; Fri,  5 Aug 2011 00:15:54 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3155136fxe.31 for <multiple recipients>; Fri, 05 Aug 2011 00:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=KeH08X5+N7kuvxthmyNkERoqG79a4MI2t2v4BXPRFsQ=; b=PUrg4YXInLFuHc/EeK2GN6WT+y26U+DxUa5OEDbKPZDKV432Uxx/nkmMfhZUtUJKpH rmPgCvtqJh+3+SFcve9dAaNfiWREH7l+LhljXW//bDsO5sQRJhc+EWnaqgOFCgShUN/z vVAlbu5VkJPoerShOKN4oDhSjjqzb9YMvJFpg=
Received: by 10.204.135.18 with SMTP id l18mr569696bkt.191.1312528562814; Fri, 05 Aug 2011 00:16:02 -0700 (PDT)
Received: from a88-114-68-66.elisa-laajakaista.fi (a88-114-68-66.elisa-laajakaista.fi [88.114.68.66]) by mx.google.com with ESMTPS id s14sm760005bkw.52.2011.08.05.00.16.01 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Aug 2011 00:16:01 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-3gpp-eps-03.txt> (IPv6 in 3GPP Evolved Packet System) to Informational RFC
From: Jouni <jounikor@gmail.com>
In-Reply-To: <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com>
Date: Fri, 5 Aug 2011 10:15:59 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B766CFB1-2EE0-456A-A6E3-0601F3B7BF9D@gmail.com>
References: <20110801190301.16571.58632.idtracker@ietfa.amsl.com> <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com>
To: ietf@ietf.org, IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-Mailman-Approved-At: Fri, 05 Aug 2011 10:11:16 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 07:15:55 -0000

I got one comment to our draft. Section 5.4 discusses some known =
neighbor discovery issues out there. I forgot to add one that I believe =
belongs here or then in Section 5.2; which one I am not sure yet. In =
Section 5.2 it is said that the GGSN/PGW provides an unique IID to the =
UE (i.e. guaranteed not to collide with GGSN/PGW's one) for the =
link-local address configuration. However, numerous modem drivers today =
fail (or don't even care) to deliver the received IID to the host OS =
stack and instead the driver comes up with its own (usually some =
imaginary MAC address based one..). Therefore, there is theoretical but =
very unlikely chance for link-local address collision between the UE and =
the gateway on the 3GPP link. Since the UE may or may not perform DAD =
this can be unnoticed during the address configuration phase.

- Jouni



2011/8/2, The IESG <iesg-secretary@ietf.org>:
>=20
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'IPv6 in 3GPP Evolved Packet System'
>  <draft-ietf-v6ops-3gpp-eps-03.txt> as an Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-08-15. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   Use of data services in smart phones and broadband services via HSPA
>   and HSPA+, in particular Internet services, has increased rapidly =
and
>   operators that have deployed networks based on 3GPP network
>   architectures are facing IPv4 address shortages at the Internet
>   registries and are feeling a pressure to migrate to IPv6.  This
>   document describes the support for IPv6 in 3GPP network
>   architectures.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


From brian.e.carpenter@gmail.com  Fri Aug  5 13:55:45 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77DFA11E80CA for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 13:55:45 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EdnipFltrYLH for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 13:55:44 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCDD11E80C1 for <ietf@ietf.org>; Fri,  5 Aug 2011 13:55:44 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3902762fxe.31 for <ietf@ietf.org>; Fri, 05 Aug 2011 13:56:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UHch6PVxfqHY0HIeiGMMsk+HcSIyg/LkHutm+HKyeSY=; b=Ags5bp2+QEH3MwbgvISWRqMSUpdW5oxqzJh2Hk8ka/QVPfSzireB4fKJ6jxd2XhbmI 46bkH5oL1xTeEO5R3GOImtc53INbMFnPo/921APX+27mOSo7P2mMWk66kPnPT9VyHh2p rG3ouG+nGQdWKwHYxHZRCGtj7VUe74Ks/aJIU=
Received: by 10.223.101.7 with SMTP id a7mr3441087fao.141.1312577762051; Fri, 05 Aug 2011 13:56:02 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id o7sm1252947fah.36.2011.08.05.13.55.56 (version=SSLv3 cipher=OTHER); Fri, 05 Aug 2011 13:56:00 -0700 (PDT)
Message-ID: <4E3C58D1.40306@gmail.com>
Date: Sat, 06 Aug 2011 08:55:45 +1200
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: Hector Santos <hsantos@isdg.net>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <4E39BB74.4090808@isdg.net> <4E39C180.90408@gmail.com> <4E3A0555.1070700@isdg.net>
In-Reply-To: <4E3A0555.1070700@isdg.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 20:55:45 -0000

Hector,

On 2011-08-04 14:35, Hector Santos wrote:
> Brian E Carpenter asked:
> 
>> Can you be more specific? Are you talking about
>>
>> a) drafts that appear in the WG with very mature text, so complete
>> the WG progress very quickly?
>>
>> b) drafts that are direct submissions to the IESG, and go through
>> IETF Last Call and IESG review without coming near the WG?
>>
>> c) drafts that are Independent Submissions to the RFC Editor,
>> so are only subject to minimal review by the IESG and are not
>> IETF documents at all?
>>
>> And in case a) or b), are you talking about standards track and BCP
>> documents, or about informational or experimental ones?
> 
> Hi Brian,
> 
> From what I have experienced, it doesn't matter what the fast track
> non-WG RFC status is - any status can have a surprising WG goal changing
> influence.
> 
> I don't really see that as the main concern until it is a competing or
> conflictive externally produced RFC, especially if it was originally
> deem out of scope in a WG charter. IMO, in such a case, it should be
> part of a WG charter change and a WG vetting process before it is made
> into an RFC and/or allowed to change the WG goals.

I'm still not getting your point. External events of all kinds can
affect a WG; for example publication of a much better technique in
an academic journal, or publication of a patent that is essential
to the chosen solution. Are you saying that the existing review process
for direct submission or Independent Submission RFCs fails to detect
work that overlaps with WGs?

> I am not an expert with IETF procedures and I don't wish to call that a
> "Loop Hole" but it appears to be one.  It seems to me a two-maturity
> level may inadvertently create more of these WG conflicts without the
> proper due diligence to watch for these type of situations.

How? It only concerns documents that have already gone through the
whole process of becoming Proposed Standard; essentially the changes
beyond that point in the standards track should always be quite minor.

> Maybe the experience in the DKIM WG was an exception and not the rule
> typical of a WG, but if was a new reflection of an "IETF change" making
> it more possible to fast track RFCs, the review process needs to take
> into account the consequences it can have in any related WG. Is that a
> time problem? A WG Chair/AD issue?  Too much work for the AD reviews? 
> Not enough synergism of among all parties?  I can't say and quite maybe
> it was just an exceptional experience and not the norm. But I believe a
> watchdog for these type of possibilities will help.

Which is exactly why we do have a review process for non-WG RFCs.

     Brian

From john-ietf@jck.com  Fri Aug  5 14:25:29 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3A021F8A7A for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 14:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.63
X-Spam-Level: 
X-Spam-Status: No, score=-102.63 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Wadnbcb4YJ1 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 14:25:29 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id D849A21F8551 for <ietf@ietf.org>; Fri,  5 Aug 2011 14:25:28 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QpRtk-000MBG-OF; Fri, 05 Aug 2011 17:25:41 -0400
Date: Fri, 05 Aug 2011 17:25:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Warren Kumari <warren@kumari.net>, Richard Kulawiec <rsk@gsp.org>
Subject: Re: subject_prefix on IETF Discuss?
Message-ID: <2732869C8B966402AD189C2B@PST.JCK.COM>
In-Reply-To: <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <20110803232151.GA26475@gsp.org> <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 21:25:29 -0000

--On Friday, August 05, 2011 12:45 -0400 Warren Kumari
<warren@kumari.net> wrote:

> 
> On Aug 3, 2011, at 7:21 PM, Richard Kulawiec wrote:
> 
>> 
>> -1.
>> 
>> This list complies with RFC 2919, which alleviates the need
>> for the horrible, unscalable, obsolete, ugly kludge of
>> Subject-line tags. I suggest that anyone who really, *really*
>> wants them on their copies of messages arrange to have them
>> added locally (perhaps by procmail or similar) and not force
>> them on those of us who have chosen mail processing software
>> that correctly uses List-Id.
> 
> Still a little confused how this morphed into a religious war
> on RFC 2919 / List-Id.  I *did* mention in the original post
> that I had been using List-Id to organize mail -- which would
> lead to folders with a few thousands of unread mails, which I
> would then unceremoniously dump, because it was just too much
> to deal with..
> 
> Subject-line tags allow me to just drop everything in the
> inbox and then, at a glance figure out what to read, and in
> what order. I then move the read stuff (and that that I don't
> care about) into separate mailboxes.

Warren,

I don't want to participate in the religious war, partially
because what I do is in the "something else" category.  But what
you are describing could easily be modeled, perhaps even more
efficiently, in terms of a search or classification that uses a
combination of List-ID (and maybe even the identified list name)
and the subject line (and maybe other information) in a boolean
or even weighted-score-based search to organize mail.  We know
how to do those things -- e.g., they lie at the core of
so-called Bayesian anti-spam procedures.  

The problem, religion-independent, is that many of our MUAs
don't provide good capabilities for doing anything like that
because they don't present interfaces for any of compound
boolean search, weighted factor search, effective "like this
one" heuristic  search, or successive refinement search --
especially in conjunction with an easy-to-use "take everything
found and either tag it in a special way or put it in a separate
folder" mechanism.  Most or all of the bits for some of these
are in the SIEVE collection, but MUAs and servers that are good
at using them and make them easy for users are not widely
available, especially for users who have other requirements
(like good, conforming, IMAP support).

To take the current debate as an example, if a user has to
choose between filtering or organizing mail using List-ID and
using subject lines, something is fundamentally broken
regardless of which choice is made.

Singling you out only because you made the comment, I would
remind you that your employer's public mail system is a major
offender in concentrating on search, rather than folder
management, but not providing sophisticated or iterative
refinement search procedures (nor supporting SIEVE).  I would
encourage you to encourage the responsible folks to clean up
their act, both in the interests of those users and to set a
good example for the industry.

     john


From dougb@dougbarton.us  Fri Aug  5 14:57:15 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A14D21F8B51 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 14:57:15 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzIV4UOJEYqK for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 14:57:14 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 26E3621F8B37 for <ietf@ietf.org>; Fri,  5 Aug 2011 14:57:13 -0700 (PDT)
Received: (qmail 32636 invoked by uid 399); 5 Aug 2011 21:57:18 -0000
Received: from unknown (HELO 12-207-105-211.globalsuite.net) (dougb@dougbarton.us@12.207.105.211) by mail2.fluidhosting.com with ESMTPAM; 5 Aug 2011 21:57:18 -0000
X-Originating-IP: 12.207.105.211
X-Sender: dougb@dougbarton.us
Message-ID: <4E3C6722.9010503@dougbarton.us>
Date: Fri, 05 Aug 2011 14:56:50 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <20110803232151.GA26475@gsp.org> <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net>
In-Reply-To: <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 21:57:15 -0000

On 08/05/2011 09:45, Warren Kumari wrote:
> Subject-line tags allow me to just drop everything in the inbox and then, at a glance figure out what to read, and in what order. I then move the read stuff (and that that I don't care about) into separate mailboxes.

To me it boils down to you saying in effect, "Here is my way of working
with e-mail, and I'd like the IETF to support it." If there was a way
that we could do that which had no impact on people who don't work that
way (such as the List-Id header) then I'd say go for it! But for those
of us who already filter our mail into folders these [tags] are useless
clutter that take up valuable screen real estate. If they break dkim
that's a whole 'nother category of problems. Personally I'd love to see
us be conservative in what we send, but I recognize that my view on this
is biased.

On some level I have sympathy for people who feel that they are stuck
with clients that don't have advanced features, but there are so many
competent clients available for free that it's hard for me to sympathize
with the view that "I need you to do this for me so that I can manage my
workflow better." When you add to that "If I filter to folders then I
just ignore the mail" it starts to sound a lot more like a personal
problem. :)


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 hsantos@isdg.net  Fri Aug  5 19:53:55 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEB8B11E8095 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 19:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.102
X-Spam-Level: 
X-Spam-Status: No, score=-3.102 tagged_above=-999 required=5 tests=[AWL=-1.103, BAYES_00=-2.599, SARE_BAYES_5x7=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GancKbtFA2fM for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 19:53:55 -0700 (PDT)
Received: from pop3.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBF021F88B6 for <ietf@ietf.org>; Fri,  5 Aug 2011 19:53:45 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2308; t=1312599237; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=YNvxg5BZ8xIdLuzW+FLYZbGST7s=; b=rPisHefI5PiLe3Cb2FuI OUQ/+jBCeEut5s011Wk0p3V12UP6vaFcVWIxs6yzu3Wux7HfvZx/d5MnCf6zAVDr fwvA6JaxEUMSp5c3kgrsP5FyOBRSSsmau4mVKDI8NzPtdWxofeif6+dI7f0jXJM2 nG7m6IHBzUcUG/69I+vf1/o=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 05 Aug 2011 22:53:57 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SELECTOR_DNS_PERM_FAILURE) header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=fail policy=all author.d=isdg.net asl.d=beta.winserver.com (unauthorized signer); 
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1054664061.38991.2532; Fri, 05 Aug 2011 22:53:01 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312598904; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=FC2fSZPZ14o8D+XR7V vob3yvgND6ElTsjlYMfm9m0D0=; b=hrIjgJvyU4Ga9P0bWPxvGxx7vSCd8sNMaG v7lO3kARyRCBeSm4hKthtXTvrCAVA9T9uJRXW1MAsgiq7aaqOYPVt/OadDPFRZCF 9bhYKnjW0RJ4P/TRP+dD7v74DlRoLyoRXaeC9kMRcPr0NxjaZ6GTYBzeHsMev5Of 5AJex4CUw=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 05 Aug 2011 22:48:24 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2025942158.133.756; Fri, 05 Aug 2011 22:48:23 -0400
Message-ID: <4E3CAC7C.7010000@isdg.net>
Date: Fri, 05 Aug 2011 22:52:44 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <4E39BB74.4090808@isdg.net> <4E39C180.90408@gmail.com> <4E3A0555.1070700@isdg.net> <4E3C58D1.40306@gmail.com>
In-Reply-To: <4E3C58D1.40306@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2011 02:53:56 -0000

Brian E Carpenter wrote:
> Are you saying that the existing review process
> for direct submission or Independent Submission RFCs fails to detect
> work that overlaps with WGs?

At least in one experience, I would not say it was a failure per se 
but more realistically, for many possible reasons, it simply fell 
through the cracks.  If interested, I can provide offlist summary 
outline example.

> Which is exactly why we do have a review process for non-WG RFCs.

Brian, no doubt. The IETF Review process and the procedures are in 
place for anyone to raise concerns and even appeal.

So in hindsight, it probably unrealistic to expect any IETF reviewer 
to catch consequential conflicts and in this case, I should of 
continued the appeal process as I had contemplated but several reasons 
I decided not to follow through.  Only then can concerns be raised for 
proper IETF review.

Maybe to help alleviate possible concerns with fast-track RFCs and 
perhaps reduce IETF reviewer time and provide some guidance, a short 
pre-review questionnaire asking relevant questions designed to 
highlight any possible conflict as known by the author and something 
the Reviewers might wish to know about, might be appropriate.

Example questions might be:

    1) Is this RFC directly or indirectly related to one or more existing
       IETF Working Groups?  If so, please list them below and continue
       with the additional questions.

    2) Is there any concept in your RFC which is deemed out of scope
       in the related Working Group? If so, which state the out of
       scope concept(s) in itemized format.

    3) Is there any concept in your RFC which competes and/or conflicts
       with the chartered goals of the related Working Group?

    4) Was this RFC vetted by the Working Group? If so, what was the
       conclusion?

Please note: In no way am I stating that these type of non-WG RFC work 
should not be written, put to a stop or not accepted by the IETF 
reviewers.  But with awareness, there be a reviewer problem solving 
suggestion to remove conflicts. Maybe it just a matter of 
word-smithing to make corrections. Again, if you wish, I can give you 
an example off-list to see why questions like these can help.


-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From dhc2@dcrocker.net  Fri Aug  5 20:11:53 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6531B21F8A36 for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 20:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.481
X-Spam-Level: 
X-Spam-Status: No, score=-5.481 tagged_above=-999 required=5 tests=[AWL=1.118,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rf1m4lkh1DZI for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 20:11:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CE7DC21F8A35 for <ietf@ietf.org>; Fri,  5 Aug 2011 20:11:52 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p763C6qg030137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 5 Aug 2011 20:12:11 -0700
Message-ID: <4E3CB0FF.2060609@dcrocker.net>
Date: Fri, 05 Aug 2011 20:11:59 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <20110803232151.GA26475@gsp.org> <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net> <4E3C6722.9010503@dougbarton.us>
In-Reply-To: <4E3C6722.9010503@dougbarton.us>
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, 05 Aug 2011 20:12:12 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2011 03:11:53 -0000

On 8/5/2011 2:56 PM, Doug Barton wrote:
> To me it boils down to you saying in effect, "Here is my way of working
> with e-mail, and I'd like the IETF to support it." If there was a way
> that we could do that which had no impact on people who don't work that
> way (such as the List-Id header) then I'd say go for it! But for those
> of us who already filter our mail into folders these [tags] are useless
> clutter that take up valuable screen real estate.


Doug,

Perhaps you missed the part about this being common practice, including for 
other IETF mailing lists?

You are already suffering with the useless clutter.  The incremental pain for 
you is going to be nil.


> If they break dkim that's a whole 'nother category of problems.

DKIM is designed for to deal with one posting and one delivery.  Mailing lists 
take delivery and re-post.  For almost all scenarios, DKIM was not intended to 
survive re-posting.


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From gwz@net-zen.net  Sat Aug  6 00:48:28 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDB7F21F85CA for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 00:48:28 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xVr4hG8bDltN for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 00:48:27 -0700 (PDT)
Received: from smtpauth02.prod.mesa1.secureserver.net (smtpauth02.prod.mesa1.secureserver.net [64.202.165.182]) by ietfa.amsl.com (Postfix) with SMTP id 3656921F85C4 for <ietf@ietf.org>; Sat,  6 Aug 2011 00:48:27 -0700 (PDT)
Received: (qmail 13269 invoked from network); 6 Aug 2011 07:48:46 -0000
Received: from unknown (124.120.216.246) by smtpauth02.prod.mesa1.secureserver.net (64.202.165.182) with ESMTP; 06 Aug 2011 07:48:44 -0000
Message-ID: <4E3CF1D7.6090603@net-zen.net>
Date: Sat, 06 Aug 2011 14:48:39 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <D88A3654-352B-451E-B55D-6A5A99FB441A@cisco.com>
In-Reply-To: <D88A3654-352B-451E-B55D-6A5A99FB441A@cisco.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------050501020908060304050800"
Cc: iaoc-mtgs@ISOC.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2011 07:48:29 -0000

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

On 8/6/2011 3:00 AM, Fred Baker wrote:
> On Aug 5, 2011, at 12:46 AM, Glen Zorn wrote:
> 
>> I note that there is an opening on the IETF meeting calendar for an
>> Asian meeting in 2013.  Here is a suggestion:
>>
>> Meeting Facilities:
>> http://www.qsncc.com/venue-information/our-facilities.html
>>
>> There are 7 pages of "Official Hotels", starting at about $60/night.
>>
>> Official Hotels: http://www.qsncc.com/visitor/official-hotels.html
>> <gwz.vcf>_______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> 
> Thanks for the suggestion.
> 
> I find your CC line highly confusing. I changed it.

And I changed it back, to include the IETF.

> 
> I have a few standard questions. 

Most of which, I imagine, should be answered by the IAOC.

Where I'm coming from is that, from my perspective, there should be

someone for whom any meeting is "at home"; it can't help but be a jaunt
for many, but there should be a group of people that is actively posting
drafts,

commenting on lists, and perhaps even chairing a working group for whom
it's not a jaunt.

There is no place in the world that is "safe", but we don't need obvious
complications like periodic coups, human trafficking in front of the
hotel, and so on.

I don't know how to interpret the term "human trafficking" here.  Are
you suggesting that there are slave markets in front of the Sheraton
(you might be, depending upon where your "news" comes from)?  I suspect,
though, that you are using it as a code word for prostitution.  If so,
tell us: did you raise the same objection about Quebec City?
Maastricht?  Prague?  Seoul?  Vancouver?  Paris?  In fact, prostitution
is legal in 3 of the last 4 cities in which we met and 2 out of the next
3...

There are various dietary issues based on health concerns and religious
matters. And oh yes, one of the issues is cost.
> 
> Who from the IETF comes from there (Bangkok)?

Me, for one.  But for that matter, who from the IETF comes from Quebec
City?  Maastricht?  Prague?  That hotbed of Internet innovation, Orlando?

> 
> In the photos, I saw no breakout rooms. I imagine they are built as needed using folding dividers or etc. What can you tell me about those facilities?

Ask the folks at the Convention Center; they are quite nice, in my
experience, and helpful.

> 
> Cost is an issue, and costs often trade off. A long and expensive flight to an expensive hotel 

that is separate from the conference facility and therefore doesn't help
us negotiate conference facility prices,

and oh by the way is far from a limited set of food options, is
something of a worst case. Finding ways to mitigate those helps.

You have suggested $60 rooms, which helps. Do any help with the price of
the conference center? How does catering fit?

Again, these would seem to be questions that the meeting organizers
should ask of the venue managers; I am a member of neither of those groups.

> The "food" section mentions a food court nearby: tell me about local markets with fresh healthful food, which some will need specific access to,

"Fresh" and "healthful" are loaded words which mean different things to
different people; for some if a vegetable isn't wrapped in three layers
of plastic it can't be "healthful"...

markets or restaurants that cater to kosher and muslim dietary rules, etc?

My understanding is that "kosher" has nearly as many meanings as there
are rabbis ;-); there are many halal restaurants nearby.

> 
> How is getting an airplane ticket? I went to Cisco Travel's web site with a view to pricing a round trip ticket to Bangkok, 

Going to Cisco Travel was probably your first mistake ;-).

determining whether the current unrest

What "current unrest" would that be?

affects travel advisories, and so on, and found that the vast majority
of itineraries available to me two weeks from now are sold out.

Hmm.  Popular destination, huh?

The Hipmunk Agony Index (http://www.hipmunk.com/#!SBA_BKK,Aug20_Aug27)
suggests that one could do worse, but there are relatively few flights
that actually get me there.
> 
> BTW, you'll note that, hat tip to folks who complain about long strings of flights, 

this one for me is SBA->SFO->NRT->BKK, and NRT->BKK is not a jump of a
puddle.

So, in other words (ignoring the SBA->??? hop which, unless SBA has
grown immensely since my last visit, will exist for just about any
destination outside the Southwestern US), it's one stop for you to
Bangkok.  Admittedly the mileage isn't inconsiderable, but in what
universe does that qualify as a "long string of flights"?  Bangkok is
one stop from every major airport in the US; there are quite a few
non-stop flights from Europe and, of course, Asia.  BTW, THAI Airways
flies non-stop LAX->BKK...

For me, more or less par for the course, but I guarantee that the folks
who plan meetings will be castigated for picking an out of the way place
if we go there.

RE:"out of the way", see above.

A worry: how many companies will choose to send less people as a way to
manage costs?

A quick spot-check of current prices suggests that tickets to Bangkok
are about $300 more than to Paris at the moment.  Is that going to break
the bank?

> 
> The site spoke of "WiFi Internet Areas". We would of course change that. How well is the building set up to support that? 

What capacity is available to the backbone from there? Same question re
the $60 hotels of which you speak?

The $60 hotel of which I spoke is the Amari Boulevard (hardly a dump); I
have no idea what their WiFi is like, but again that seems like a
question the organizers should ask the hotel.


Note that when the IETF shows up in common business hotels that have
pretty reasonable Internet access, we completely overload that service,

and as a result we have taken to replacing it while we are there. How
will that fit?
> 
> My daughter took her honeymoon in Phuket. 

Sorry to hear that; although the scenery around Phuket is amazing, it's
the last place I would go for a honeymoon (OK, so Las Vegas would be the
_last_ place, but nevertheless).  Koh Samui or Krabi would have been far
preferable...

Several stories related to that are strong advertisements for Thailand.
Some Really Are Not. Great subject in the presence of adult beverages.
> 
> But just looking at the web site, it seems like a nice facility, and the pictures are great. 
> 

Apricot was held at the convention center a few years ago and it worked
out quite nicely, I think.  In any case, the statement was made during
the administrative plenary that the IAOC was having trouble finding
venues in Asia w/o $300/night hotel price tags; this is a suggestion for
investigation.  I suspect that similar results could be had in Kuala
Lumpur, Jakarta, Manila or Phnom Penh (though those _are_ out-of-the-way
;-).  I don't intend to do your job for you, but if you (IAOC) could
come up with a set of specific, detailed questions I would probably be
willing to drop by QSNCC and investigate.

--------------050501020908060304050800
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------050501020908060304050800--

From marshall.eubanks@gmail.com  Sat Aug  6 06:47:52 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F38C121F857E for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 06:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.377
X-Spam-Level: 
X-Spam-Status: No, score=-103.377 tagged_above=-999 required=5 tests=[AWL=0.221, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YuxkshpABNtT for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 06:47:50 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 41A4021F8569 for <ietf@ietf.org>; Sat,  6 Aug 2011 06:47:50 -0700 (PDT)
Received: by gxk19 with SMTP id 19so199310gxk.31 for <ietf@ietf.org>; Sat, 06 Aug 2011 06:48:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rOl0YVe9exMYTVZ/2kV+IZK60mHz8BKr9Cq8NLqp0L4=; b=OwYAWDRSJJIHTCuPYLSQ8EH97vo5vhj5Ua+nUWHGhkAb+rAjrGQ4TA4gdIG9aSm4NV 7ULUB54CxGL55EZ2xhOqH8AN8cQ2Hmoqhevvu99100/8Tqs0o1zDgi49uhgq+/L9Pc9H O54558TW8Et3VclPc5aDkK7MpXxisEUOI8uxE=
MIME-Version: 1.0
Received: by 10.150.92.10 with SMTP id p10mr4159675ybb.138.1312638489421; Sat, 06 Aug 2011 06:48:09 -0700 (PDT)
Received: by 10.151.98.21 with HTTP; Sat, 6 Aug 2011 06:48:09 -0700 (PDT)
In-Reply-To: <4E3CF1D7.6090603@net-zen.net>
References: <4E3B9FC6.7090701@net-zen.net> <D88A3654-352B-451E-B55D-6A5A99FB441A@cisco.com> <4E3CF1D7.6090603@net-zen.net>
Date: Sat, 6 Aug 2011 09:48:09 -0400
Message-ID: <CAJNg7VJQeXY5eALOKorgCK4oL8_uD13E+af7cGYLOQnS7U0oxQ@mail.gmail.com>
Subject: Re: Queen Sirikit National Convention Center
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Glen Zorn <gwz@net-zen.net>
Content-Type: multipart/alternative; boundary=000e0cd402dce1675404a9d676f2
Cc: iaoc-mtgs@isoc.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2011 13:47:52 -0000

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

Dear Glen;

Thanks for all of this information. Do you know if there is an "off-season"
for
Bangkok ?

Regards
Marshall

On Sat, Aug 6, 2011 at 3:48 AM, Glen Zorn <gwz@net-zen.net> wrote:

> On 8/6/2011 3:00 AM, Fred Baker wrote:
> > On Aug 5, 2011, at 12:46 AM, Glen Zorn wrote:
> >
> >> I note that there is an opening on the IETF meeting calendar for an
> >> Asian meeting in 2013.  Here is a suggestion:
> >>
> >> Meeting Facilities:
> >> http://www.qsncc.com/venue-information/our-facilities.html
> >>
> >> There are 7 pages of "Official Hotels", starting at about $60/night.
> >>
> >> Official Hotels: http://www.qsncc.com/visitor/official-hotels.html
> >> <gwz.vcf>_______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >
> > Thanks for the suggestion.
> >
> > I find your CC line highly confusing. I changed it.
>
> And I changed it back, to include the IETF.
>
> >
> > I have a few standard questions.
>
> Most of which, I imagine, should be answered by the IAOC.
>
> Where I'm coming from is that, from my perspective, there should be
>
> someone for whom any meeting is "at home"; it can't help but be a jaunt
> for many, but there should be a group of people that is actively posting
> drafts,
>
> commenting on lists, and perhaps even chairing a working group for whom
> it's not a jaunt.
>
> There is no place in the world that is "safe", but we don't need obvious
> complications like periodic coups, human trafficking in front of the
> hotel, and so on.
>
> I don't know how to interpret the term "human trafficking" here.  Are
> you suggesting that there are slave markets in front of the Sheraton
> (you might be, depending upon where your "news" comes from)?  I suspect,
> though, that you are using it as a code word for prostitution.  If so,
> tell us: did you raise the same objection about Quebec City?
> Maastricht?  Prague?  Seoul?  Vancouver?  Paris?  In fact, prostitution
> is legal in 3 of the last 4 cities in which we met and 2 out of the next
> 3...
>
> There are various dietary issues based on health concerns and religious
> matters. And oh yes, one of the issues is cost.
> >
> > Who from the IETF comes from there (Bangkok)?
>
> Me, for one.  But for that matter, who from the IETF comes from Quebec
> City?  Maastricht?  Prague?  That hotbed of Internet innovation, Orlando?
>
> >
> > In the photos, I saw no breakout rooms. I imagine they are built as
> needed using folding dividers or etc. What can you tell me about those
> facilities?
>
> Ask the folks at the Convention Center; they are quite nice, in my
> experience, and helpful.
>
> >
> > Cost is an issue, and costs often trade off. A long and expensive flight
> to an expensive hotel
>
> that is separate from the conference facility and therefore doesn't help
> us negotiate conference facility prices,
>
> and oh by the way is far from a limited set of food options, is
> something of a worst case. Finding ways to mitigate those helps.
>
> You have suggested $60 rooms, which helps. Do any help with the price of
> the conference center? How does catering fit?
>
> Again, these would seem to be questions that the meeting organizers
> should ask of the venue managers; I am a member of neither of those groups.
>
> > The "food" section mentions a food court nearby: tell me about local
> markets with fresh healthful food, which some will need specific access to,
>
> "Fresh" and "healthful" are loaded words which mean different things to
> different people; for some if a vegetable isn't wrapped in three layers
> of plastic it can't be "healthful"...
>
> markets or restaurants that cater to kosher and muslim dietary rules, etc?
>
> My understanding is that "kosher" has nearly as many meanings as there
> are rabbis ;-); there are many halal restaurants nearby.
>
> >
> > How is getting an airplane ticket? I went to Cisco Travel's web site with
> a view to pricing a round trip ticket to Bangkok,
>
> Going to Cisco Travel was probably your first mistake ;-).
>
> determining whether the current unrest
>
> What "current unrest" would that be?
>
> affects travel advisories, and so on, and found that the vast majority
> of itineraries available to me two weeks from now are sold out.
>
> Hmm.  Popular destination, huh?
>
> The Hipmunk Agony Index (http://www.hipmunk.com/#!SBA_BKK,Aug20_Aug27)
> suggests that one could do worse, but there are relatively few flights
> that actually get me there.
> >
> > BTW, you'll note that, hat tip to folks who complain about long strings
> of flights,
>
> this one for me is SBA->SFO->NRT->BKK, and NRT->BKK is not a jump of a
> puddle.
>
> So, in other words (ignoring the SBA->??? hop which, unless SBA has
> grown immensely since my last visit, will exist for just about any
> destination outside the Southwestern US), it's one stop for you to
> Bangkok.  Admittedly the mileage isn't inconsiderable, but in what
> universe does that qualify as a "long string of flights"?  Bangkok is
> one stop from every major airport in the US; there are quite a few
> non-stop flights from Europe and, of course, Asia.  BTW, THAI Airways
> flies non-stop LAX->BKK...
>
> For me, more or less par for the course, but I guarantee that the folks
> who plan meetings will be castigated for picking an out of the way place
> if we go there.
>
> RE:"out of the way", see above.
>
> A worry: how many companies will choose to send less people as a way to
> manage costs?
>
> A quick spot-check of current prices suggests that tickets to Bangkok
> are about $300 more than to Paris at the moment.  Is that going to break
> the bank?
>
> >
> > The site spoke of "WiFi Internet Areas". We would of course change that.
> How well is the building set up to support that?
>
> What capacity is available to the backbone from there? Same question re
> the $60 hotels of which you speak?
>
> The $60 hotel of which I spoke is the Amari Boulevard (hardly a dump); I
> have no idea what their WiFi is like, but again that seems like a
> question the organizers should ask the hotel.
>
>
> Note that when the IETF shows up in common business hotels that have
> pretty reasonable Internet access, we completely overload that service,
>
> and as a result we have taken to replacing it while we are there. How
> will that fit?
> >
> > My daughter took her honeymoon in Phuket.
>
> Sorry to hear that; although the scenery around Phuket is amazing, it's
> the last place I would go for a honeymoon (OK, so Las Vegas would be the
> _last_ place, but nevertheless).  Koh Samui or Krabi would have been far
> preferable...
>
> Several stories related to that are strong advertisements for Thailand.
> Some Really Are Not. Great subject in the presence of adult beverages.
> >
> > But just looking at the web site, it seems like a nice facility, and the
> pictures are great.
> >
>
> Apricot was held at the convention center a few years ago and it worked
> out quite nicely, I think.  In any case, the statement was made during
> the administrative plenary that the IAOC was having trouble finding
> venues in Asia w/o $300/night hotel price tags; this is a suggestion for
> investigation.  I suspect that similar results could be had in Kuala
> Lumpur, Jakarta, Manila or Phnom Penh (though those _are_ out-of-the-way
> ;-).  I don't intend to do your job for you, but if you (IAOC) could
> come up with a set of specific, detailed questions I would probably be
> willing to drop by QSNCC and investigate.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>

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

Dear Glen;<div><br></div><div>Thanks for all of this information. Do you kn=
ow if there is an &quot;off-season&quot; for=A0</div><div>Bangkok ?</div><d=
iv><br></div><div>Regards</div><div>Marshall<br><br><div class=3D"gmail_quo=
te">
On Sat, Aug 6, 2011 at 3:48 AM, Glen Zorn <span dir=3D"ltr">&lt;<a href=3D"=
mailto:gwz@net-zen.net">gwz@net-zen.net</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;">
On 8/6/2011 3:00 AM, Fred Baker wrote:<br>
<div><div></div><div class=3D"h5">&gt; On Aug 5, 2011, at 12:46 AM, Glen Zo=
rn wrote:<br>
&gt;<br>
&gt;&gt; I note that there is an opening on the IETF meeting calendar for a=
n<br>
&gt;&gt; Asian meeting in 2013. =A0Here is a suggestion:<br>
&gt;&gt;<br>
&gt;&gt; Meeting Facilities:<br>
&gt;&gt; <a href=3D"http://www.qsncc.com/venue-information/our-facilities.h=
tml" target=3D"_blank">http://www.qsncc.com/venue-information/our-facilitie=
s.html</a><br>
&gt;&gt;<br>
&gt;&gt; There are 7 pages of &quot;Official Hotels&quot;, starting at abou=
t $60/night.<br>
&gt;&gt;<br>
&gt;&gt; Official Hotels: <a href=3D"http://www.qsncc.com/visitor/official-=
hotels.html" target=3D"_blank">http://www.qsncc.com/visitor/official-hotels=
.html</a><br>
</div></div>&gt;&gt; &lt;gwz.vcf&gt;_______________________________________=
________<br>
&gt;&gt; Ietf mailing list<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;<br>
&gt; Thanks for the suggestion.<br>
&gt;<br>
&gt; I find your CC line highly confusing. I changed it.<br>
<br>
And I changed it back, to include the IETF.<br>
<br>
&gt;<br>
&gt; I have a few standard questions.<br>
<br>
Most of which, I imagine, should be answered by the IAOC.<br>
<br>
Where I&#39;m coming from is that, from my perspective, there should be<br>
<br>
someone for whom any meeting is &quot;at home&quot;; it can&#39;t help but =
be a jaunt<br>
for many, but there should be a group of people that is actively posting<br=
>
drafts,<br>
<br>
commenting on lists, and perhaps even chairing a working group for whom<br>
it&#39;s not a jaunt.<br>
<br>
There is no place in the world that is &quot;safe&quot;, but we don&#39;t n=
eed obvious<br>
complications like periodic coups, human trafficking in front of the<br>
hotel, and so on.<br>
<br>
I don&#39;t know how to interpret the term &quot;human trafficking&quot; he=
re. =A0Are<br>
you suggesting that there are slave markets in front of the Sheraton<br>
(you might be, depending upon where your &quot;news&quot; comes from)? =A0I=
 suspect,<br>
though, that you are using it as a code word for prostitution. =A0If so,<br=
>
tell us: did you raise the same objection about Quebec City?<br>
Maastricht? =A0Prague? =A0Seoul? =A0Vancouver? =A0Paris? =A0In fact, prosti=
tution<br>
is legal in 3 of the last 4 cities in which we met and 2 out of the next<br=
>
3...<br>
<br>
There are various dietary issues based on health concerns and religious<br>
matters. And oh yes, one of the issues is cost.<br>
&gt;<br>
&gt; Who from the IETF comes from there (Bangkok)?<br>
<br>
Me, for one. =A0But for that matter, who from the IETF comes from Quebec<br=
>
City? =A0Maastricht? =A0Prague? =A0That hotbed of Internet innovation, Orla=
ndo?<br>
<br>
&gt;<br>
&gt; In the photos, I saw no breakout rooms. I imagine they are built as ne=
eded using folding dividers or etc. What can you tell me about those facili=
ties?<br>
<br>
Ask the folks at the Convention Center; they are quite nice, in my<br>
experience, and helpful.<br>
<br>
&gt;<br>
&gt; Cost is an issue, and costs often trade off. A long and expensive flig=
ht to an expensive hotel<br>
<br>
that is separate from the conference facility and therefore doesn&#39;t hel=
p<br>
us negotiate conference facility prices,<br>
<br>
and oh by the way is far from a limited set of food options, is<br>
something of a worst case. Finding ways to mitigate those helps.<br>
<br>
You have suggested $60 rooms, which helps. Do any help with the price of<br=
>
the conference center? How does catering fit?<br>
<br>
Again, these would seem to be questions that the meeting organizers<br>
should ask of the venue managers; I am a member of neither of those groups.=
<br>
<br>
&gt; The &quot;food&quot; section mentions a food court nearby: tell me abo=
ut local markets with fresh healthful food, which some will need specific a=
ccess to,<br>
<br>
&quot;Fresh&quot; and &quot;healthful&quot; are loaded words which mean dif=
ferent things to<br>
different people; for some if a vegetable isn&#39;t wrapped in three layers=
<br>
of plastic it can&#39;t be &quot;healthful&quot;...<br>
<br>
markets or restaurants that cater to kosher and muslim dietary rules, etc?<=
br>
<br>
My understanding is that &quot;kosher&quot; has nearly as many meanings as =
there<br>
are rabbis ;-); there are many halal restaurants nearby.<br>
<br>
&gt;<br>
&gt; How is getting an airplane ticket? I went to Cisco Travel&#39;s web si=
te with a view to pricing a round trip ticket to Bangkok,<br>
<br>
Going to Cisco Travel was probably your first mistake ;-).<br>
<br>
determining whether the current unrest<br>
<br>
What &quot;current unrest&quot; would that be?<br>
<br>
affects travel advisories, and so on, and found that the vast majority<br>
of itineraries available to me two weeks from now are sold out.<br>
<br>
Hmm. =A0Popular destination, huh?<br>
<br>
The Hipmunk Agony Index (<a href=3D"http://www.hipmunk.com/#!SBA_BKK,Aug20_=
Aug27" target=3D"_blank">http://www.hipmunk.com/#!SBA_BKK,Aug20_Aug27</a>)<=
br>
suggests that one could do worse, but there are relatively few flights<br>
that actually get me there.<br>
&gt;<br>
&gt; BTW, you&#39;ll note that, hat tip to folks who complain about long st=
rings of flights,<br>
<br>
this one for me is SBA-&gt;SFO-&gt;NRT-&gt;BKK, and NRT-&gt;BKK is not a ju=
mp of a<br>
puddle.<br>
<br>
So, in other words (ignoring the SBA-&gt;??? hop which, unless SBA has<br>
grown immensely since my last visit, will exist for just about any<br>
destination outside the Southwestern US), it&#39;s one stop for you to<br>
Bangkok. =A0Admittedly the mileage isn&#39;t inconsiderable, but in what<br=
>
universe does that qualify as a &quot;long string of flights&quot;? =A0Bang=
kok is<br>
one stop from every major airport in the US; there are quite a few<br>
non-stop flights from Europe and, of course, Asia. =A0BTW, THAI Airways<br>
flies non-stop LAX-&gt;BKK...<br>
<br>
For me, more or less par for the course, but I guarantee that the folks<br>
who plan meetings will be castigated for picking an out of the way place<br=
>
if we go there.<br>
<br>
RE:&quot;out of the way&quot;, see above.<br>
<br>
A worry: how many companies will choose to send less people as a way to<br>
manage costs?<br>
<br>
A quick spot-check of current prices suggests that tickets to Bangkok<br>
are about $300 more than to Paris at the moment. =A0Is that going to break<=
br>
the bank?<br>
<br>
&gt;<br>
&gt; The site spoke of &quot;WiFi Internet Areas&quot;. We would of course =
change that. How well is the building set up to support that?<br>
<br>
What capacity is available to the backbone from there? Same question re<br>
the $60 hotels of which you speak?<br>
<br>
The $60 hotel of which I spoke is the Amari Boulevard (hardly a dump); I<br=
>
have no idea what their WiFi is like, but again that seems like a<br>
question the organizers should ask the hotel.<br>
<br>
<br>
Note that when the IETF shows up in common business hotels that have<br>
pretty reasonable Internet access, we completely overload that service,<br>
<br>
and as a result we have taken to replacing it while we are there. How<br>
will that fit?<br>
&gt;<br>
&gt; My daughter took her honeymoon in Phuket.<br>
<br>
Sorry to hear that; although the scenery around Phuket is amazing, it&#39;s=
<br>
the last place I would go for a honeymoon (OK, so Las Vegas would be the<br=
>
_last_ place, but nevertheless). =A0Koh Samui or Krabi would have been far<=
br>
preferable...<br>
<br>
Several stories related to that are strong advertisements for Thailand.<br>
Some Really Are Not. Great subject in the presence of adult beverages.<br>
&gt;<br>
&gt; But just looking at the web site, it seems like a nice facility, and t=
he pictures are great.<br>
&gt;<br>
<br>
Apricot was held at the convention center a few years ago and it worked<br>
out quite nicely, I think. =A0In any case, the statement was made during<br=
>
the administrative plenary that the IAOC was having trouble finding<br>
venues in Asia w/o $300/night hotel price tags; this is a suggestion for<br=
>
investigation. =A0I suspect that similar results could be had in Kuala<br>
Lumpur, Jakarta, Manila or Phnom Penh (though those _are_ out-of-the-way<br=
>
;-). =A0I don&#39;t intend to do your job for you, but if you (IAOC) could<=
br>
come up with a set of specific, detailed questions I would probably be<br>
willing to drop by QSNCC and investigate.<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>
<br></blockquote></div><br></div>

--000e0cd402dce1675404a9d676f2--

From bob.hinden@gmail.com  Sat Aug  6 07:15:06 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 631A621F865E for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 07:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.167
X-Spam-Level: 
X-Spam-Status: No, score=-103.167 tagged_above=-999 required=5 tests=[AWL=0.432, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfO4rBsqExLz for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 07:15:05 -0700 (PDT)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id A46B121F858D for <ietf@ietf.org>; Sat,  6 Aug 2011 07:15:05 -0700 (PDT)
Received: by iye1 with SMTP id 1so5205317iye.27 for <ietf@ietf.org>; Sat, 06 Aug 2011 07:15:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Q6DJk7CpN1lxEUTm5KykN9ZG0u3UhryPVQmyBmpRm+A=; b=DW7+i0aTIxakjxQpm6+Hb3wHhJZOtliUvIbWh0SqRbKsk6mLjMUM/xNHVxRfYUAHhC OPotzmnmsFUtYJKd67qF2w6A2EtNQLCDuy8Cs06EPNpOsBEIoF/Ml/MudNIoBk6blHXj nJXhLtOU1atfmKiyezDx1NMVs7wb+dBzNR4gs=
MIME-Version: 1.0
Received: by 10.231.93.135 with SMTP id v7mr1440205ibm.18.1312640125917; Sat, 06 Aug 2011 07:15:25 -0700 (PDT)
Received: by 10.231.149.138 with HTTP; Sat, 6 Aug 2011 07:15:25 -0700 (PDT)
In-Reply-To: <4E32E571.4050108@dcrocker.net>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <A78EB07C-8D05-4EC1-9800-AC07502FCB6B@gmail.com> <573CDFAC-1C01-43F1-9878-EF6EB57F6710@vigilsec.com> <4E32E571.4050108@dcrocker.net>
Date: Sat, 6 Aug 2011 07:15:25 -0700
Message-ID: <CAH0=7GUY4FPRGnqHPQ=RJCMmzfVN4y_51AYsh6Ec0nL_mLebPw@mail.gmail.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
From: Bob Hinden <bob.hinden@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2011 14:15:06 -0000

Dave,

On Fri, Jul 29, 2011 at 9:53 AM, Dave CROCKER <dhc2@dcrocker.net> wrote:
>
>
> On 7/29/2011 11:13 AM, Russ Housley wrote:
>>>>
>>>> (2) At any time after two years from the approval of this document as =
a
>>>> BCP, the IESG may choose to reclassify any Draft Standard document as
>>>> Proposed Standard.
>>>
>>> I think this is unfair to the people who have done considerable work to
>>> get
>>> a document to Draft Standard. =A0I hope that the IESG would only do thi=
s
>>> after giving a lot of notice to the authors, appropriate working groups=
,
>>> and the IETF community to give them the opportunity to request
>>> advancement
>>> to Internet Standard.
>>
>> This was added after the discussion that Draft Standards could linger fo=
r
>> a
>> very long time. =A0Some people said that would not be a problem, and oth=
er
>> people said it would be harmful. =A0I conclude that no one knows, so we
>> should
>> include the powers necessary to resolve the problems if they emerge. =A0=
If
>> they
>> do not emerge, there is no requirement that the IESG do anything.
>
> If a document no longer has anyone watching it, there's a reasonable conc=
ern
> that it no longer has much constituency. =A0In that case, it's better to =
treat
> it as immature rather than mature.

In order to have reached Draft Standard, the w.g. must have shown
multiple implementations.  In at least one case I can think about the
protocol is very widely used operationally.  The working group is
disbanded, only the mailing list remains.  The protocol is very mature
and stable.  It's only the IETF activity that is inactive.

You can't measure maturity of a protocol at draft standard by looking
at the IETF activity.

Bob




>
>
>>> I think this Section of the document needs to provide additional detail
>>> on
>>> how this should work.
>>
>> I do not think we should add speculation about the potential problems to
>> this
>> document.
>
> +1
>
> d/
> --
>
> =A0Dave Crocker
> =A0Brandenburg InternetWorking
> =A0bbiw.net
>

From gwz@net-zen.net  Sat Aug  6 09:16:47 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EBC721F88A0 for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 09:16:47 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZxBAN+bHmX5 for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 09:16:46 -0700 (PDT)
Received: from p3plsmtpa01-06.prod.phx3.secureserver.net (p3plsmtpa01-06.prod.phx3.secureserver.net [72.167.82.86]) by ietfa.amsl.com (Postfix) with SMTP id 9BFCC21F8891 for <ietf@ietf.org>; Sat,  6 Aug 2011 09:16:46 -0700 (PDT)
Received: (qmail 17554 invoked from network); 6 Aug 2011 16:17:07 -0000
Received: from unknown (124.120.216.246) by p3plsmtpa01-06.prod.phx3.secureserver.net (72.167.82.86) with ESMTP; 06 Aug 2011 16:17:06 -0000
Message-ID: <4E3D68FC.5020908@net-zen.net>
Date: Sat, 06 Aug 2011 23:17:00 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <D88A3654-352B-451E-B55D-6A5A99FB441A@cisco.com> <4E3CF1D7.6090603@net-zen.net> <CAJNg7VJQeXY5eALOKorgCK4oL8_uD13E+af7cGYLOQnS7U0oxQ@mail.gmail.com>
In-Reply-To: <CAJNg7VJQeXY5eALOKorgCK4oL8_uD13E+af7cGYLOQnS7U0oxQ@mail.gmail.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------060908080907000704040000"
Cc: iaoc-mtgs@isoc.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2011 16:16:47 -0000

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

On 8/6/2011 8:48 PM, Marshall Eubanks wrote:
> Dear Glen;
> 
> Thanks for all of this information. Do you know if there is an
> "off-season" for 
> Bangkok ?

Yes, it's pretty much now (July, August & September).  However, November
is widely considered the nicest month of the year: it's at the tail end
of the rainy season, so the air is drying out but it's not too hot.
December is very nice, too, but it's the beginning of the high tourist
season so hotel prices go up.

BTW, I neglected to mention in my reply to Fred that the convention
center is a couple of blocks from one of the largest markets in the
city, specializing in seafood.  It's a night market, meaning that it
doesn't open until around midnight but if you're an early riser it
doesn't close until 8-9 AM.  There are several Western-style
supermarkets nearby, too.

...

--------------060908080907000704040000
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------060908080907000704040000--

From dworley@avaya.com  Sat Aug  6 17:56:26 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7902421F863A for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 17:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.97
X-Spam-Level: 
X-Spam-Status: No, score=-102.97 tagged_above=-999 required=5 tests=[AWL=-0.371, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NaQ30plwjMcV for <ietf@ietfa.amsl.com>; Sat,  6 Aug 2011 17:56:26 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1FAB621F861A for <ietf@ietf.org>; Sat,  6 Aug 2011 17:56:24 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EABbhPU6HCzI1/2dsb2JhbABCp2p3gUABAQEBAgESKD8FCwIBCA0BByEQMiUBAQQBDQ0ah0uhRwKaZIVnXwSYKIte
X-IronPort-AV: E=Sophos;i="4.67,330,1309752000"; d="scan'208";a="200499809"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 06 Aug 2011 20:56:44 -0400
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; 06 Aug 2011 20:48:51 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Sat, 6 Aug 2011 20:56:44 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Glen Zorn <gwz@net-zen.net>, Fred Baker <fred@cisco.com>
Date: Sat, 6 Aug 2011 20:54:01 -0400
Subject: RE: Queen Sirikit National Convention Center
Thread-Topic: Queen Sirikit National Convention Center
Thread-Index: AcxUDU7JYwIEnHe8TYmuWbXRWOwTZgAjzDXg
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F57E1@DC-US1MBEX4.global.avaya.com>
References: <4E3B9FC6.7090701@net-zen.net> <D88A3654-352B-451E-B55D-6A5A99FB441A@cisco.com>, <4E3CF1D7.6090603@net-zen.net>
In-Reply-To: <4E3CF1D7.6090603@net-zen.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: "iaoc-mtgs@ISOC.org" <iaoc-mtgs@ISOC.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Aug 2011 00:56:26 -0000

> From: Glen Zorn
>=20
> I don't know how to interpret the term "human trafficking" here.  Are
> you suggesting that there are slave markets in front of the Sheraton

I am still trying to clear my mind of the vision of enslaved
IETFers...  Given the difficulty many of us have convincing our
employers to send us to the IETF, our market value must be small, if
not negative.

Dale

From evnikita2@gmail.com  Sat Aug  6 21:11:36 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8ADF21F85FE; Sat,  6 Aug 2011 21:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Ojbn-6DDYLo; Sat,  6 Aug 2011 21:11:36 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD0521F85E3; Sat,  6 Aug 2011 21:11:35 -0700 (PDT)
Received: by fxe6 with SMTP id 6so806173fxe.31 for <multiple recipients>; Sat, 06 Aug 2011 21:11:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=RJnDt7qzlpmzX3LFhEKCCuNo+RTZ9tIkbhjjtnn/79c=; b=sbOGB0/cMJud/h9LIQrFFcCR0oO+2ADRZ0crO5zi1B0d+garnzR7o48/v4XiUYkKLM DT9C/HgxKCCE9bE8/Ah6XVdGfFMpaBrTUkvs9/CqpmhHxvqBb64dWAL7MPr/DjPK4qx7 oqY3wdszNoBPYz/cEbOai6gyxdqNWV9ITWni8=
Received: by 10.223.15.138 with SMTP id k10mr5395023faa.101.1312690315635; Sat, 06 Aug 2011 21:11:55 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id a2sm3147232fak.1.2011.08.06.21.11.53 (version=SSLv3 cipher=OTHER); Sat, 06 Aug 2011 21:11:54 -0700 (PDT)
Message-ID: <4E3E10B1.3070003@gmail.com>
Date: Sun, 07 Aug 2011 07:12:33 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>, iesg <iesg@ietf.org>
Subject: Re: Last Call: <draft-yevstifeyev-ion-report-06.txt> (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC
References: <20110712143944.20141.23357.idtracker@ietfa.amsl.com>
In-Reply-To: <20110712143944.20141.23357.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Aug 2011 04:11:36 -0000

Hello all,

Based on feedback received during Last Call, I decided to forward the 
document only in that part which moves RFC 4693 to Historic, pointing 
those who want motivation and/or any further information to the IESG and 
excluding everything related to it from the draft.

Thanks everybody for your comments and criticism.

Mykyta Yevstifeyev

12.07.2011 17:39, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Report on the Experiment with IETF Operational Notes (IONs)'
>    <draft-yevstifeyev-ion-report-06.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-08-09. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document reports on the IETF Operational Notes (IONs) process
>     experiment, conducted by RFC 4693 in accordance with RFC 3933.  It
>     also updates RFC 4693 and changes its status to Historic.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-yevstifeyev-ion-report/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-yevstifeyev-ion-report/
>
>
> 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 john-ietf@jck.com  Sun Aug  7 09:18:46 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DCE21F85F7 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 09:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.613
X-Spam-Level: 
X-Spam-Status: No, score=-102.613 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boKIqDFDRSRP for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 09:18:46 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2869121F8568 for <ietf@ietf.org>; Sun,  7 Aug 2011 09:18:45 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qq648-0008ps-SZ; Sun, 07 Aug 2011 12:19:05 -0400
X-Vipre-Scanned: 047D040200276D047D054F-TDI
Date: Sun, 07 Aug 2011 12:19:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>, ietf@ietf.org
Subject: RE: I-D Working groups and mailing list
Message-ID: <68496DEA09A833357F1852EC@[192.168.1.128]>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com>	<4E3A5A1E.8050002@gmx.de> ,	<EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com> <4E3AB2B8.6080501@dcrocker.net> <4E3AB642.3070208@isdg.net> <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Aug 2011 16:18:47 -0000

--On Thursday, August 04, 2011 10:38 -0700 "Murray S. Kucherawy"
<msk@cloudmark.com> wrote:

>...
>> I don't know if there is a need for "template" changes or
>> some formal section in the write up, but it would seem to me
>> that an author who has reached a level of getting WG assigned
>...
> OK, now I *really* don't know what the proposal is.
> 
> If we're not creating something formal, then the
> rules/procedures we have in place now are sufficient.  Those
> are:
> 
> If a WG has been created and "owns" the document, then the
> document has the WG name in its filename and usually says the
> name of the working group at the top of the first page.
> 
> If it's an individual submission associated with a working
> group, it has the first of those two.
> 
> If it's an individual submission not tracking a working group,
> the work may or may not benefit from some explicit
> association, and none is required.
> 
> In any case, I'm now quite confused about what change is being
> proposed here.

Murray,

While I agree this has exploded out of control and into the
weeds, I think there is one fundamental issue.  That is whether
someone can easily find the right mailing list on which to
discuss a posted draft.  Modulo distractions, the responses
seem, in my highly prejudiced view, to fall into the following
categories:

(1) We should modify the posting tools and instructions to the
Secretariat so that no I-D can be posted unless a mailing list
reference appears (and probably appears in a designated format
and place).

(2) For WG-ish documents, it is easy enough to figure out where
the discussion forum is, at least if you have a clue.  The
advocates for (1) point out that clues are not universally
distributed.

(3) Especially for non-WG documents, some of us are fearful of a
requirement to designate a discussion forum as a prerequisite
for posting a document, especially since some documents are
posted in order to initiate a discussion of forum.  In
principle, all such documents could be pointed to the IETF list.
That is not necessarily an optimal solution even though it would
likely be the effect of requiring an announcement as in (1).

(4) Others (probably a partially overlapping group with (3))
just find more rules and requirements for more boilerplate
undesirable.  They would (at least mostly) be happy if lots of
off-list notes went to authors of I-Ds for which the discussion
forum wasn't clear, asking them about the discussion forum and
recommending that it be included in the next draft.   That might
actually encourage discussion and would be as, or more,
effective at retraining authors than more rules.

   john


From john-ietf@jck.com  Sun Aug  7 09:31:11 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 271C921F8754 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 09:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.613
X-Spam-Level: 
X-Spam-Status: No, score=-102.613 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGxFVakrCRLB for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 09:31:10 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 7EE5C21F8753 for <ietf@ietf.org>; Sun,  7 Aug 2011 09:31:10 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qq6GD-00097S-Hp; Sun, 07 Aug 2011 12:31:33 -0400
X-Vipre-Scanned: 0488708200276E048871CF-TDI
Date: Sun, 07 Aug 2011 12:31:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing	the Standards Track to Two Maturity Levels) to BCP
Message-ID: <2B40B46C035E190E57776B11@[192.168.1.128]>
In-Reply-To: <CAH0=7GUY4FPRGnqHPQ=RJCMmzfVN4y_51AYsh6Ec0nL_mLebPw@mail.gmail.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <A78EB07C-8D05-4EC1-9800-AC07502FCB6B@gmail.com> <573CDFAC-1C01-43F1-9878-EF6EB57F6710@vigilsec.com> <4E32E571.4050108@dcrocker.net> <CAH0=7GUY4FPRGnqHPQ=RJCMmzfVN4y_51AYsh6Ec0nL_mLebPw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Aug 2011 16:31:11 -0000

--On Saturday, August 06, 2011 07:15 -0700 Bob Hinden
<bob.hinden@gmail.com> wrote:

>> If a document no longer has anyone watching it, there's a
>> reasonable concern that it no longer has much constituency.
>> =C2=A0In that case, it's better to treat it as immature =
rather
>> than mature.
>=20
> In order to have reached Draft Standard, the w.g. must have
> shown multiple implementations.  In at least one case I can
> think about the protocol is very widely used operationally.
> The working group is disbanded, only the mailing list remains.
> The protocol is very mature and stable.  It's only the IETF
> activity that is inactive.

Moreover, if the community that produced the Draft Standard came
to the IETF for the purpose of working on the particular
specification (and, presumably, its predecessors), decided they
were finished, and went away, perhaps after seeing it widely
deployed, there may be an even stronger argument for moving it
to Internet Standard than would be the case if there are still
people around and messing with it.
>=20
> You can't measure maturity of a protocol at draft standard by
> looking at the IETF activity.

Right.

   john




From presnick@qualcomm.com  Sun Aug  7 10:57:45 2011
Return-Path: <presnick@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81FE121F8752 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 10:57:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.512
X-Spam-Level: 
X-Spam-Status: No, score=-106.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BPWoY8gmCwRy for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 10:57:44 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 1257D21F874F for <ietf@ietf.org>; Sun,  7 Aug 2011 10:57:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1312739887; x=1344275887; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4E3ED22B.3060405@qualcomm.com>|Date:=20Su n,=207=20Aug=202011=2012:58:03=20-0500|From:=20Pete=20Res nick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Glen=20Zorn=20<gwz@net-zen.net >|CC:=20<iaoc-mtgs@ISOC.org>,=20IETF=20Discussion=20<ietf @ietf.org>|Subject:=20Re:=20Queen=20Sirikit=20National=20 Convention=20Center|References:=20<4E3B9FC6.7090701@net-z en.net>|In-Reply-To:=20<4E3B9FC6.7090701@net-zen.net> |Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1" =3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.39.5]; bh=mBCE6IZsGUKn6GRnIvmX1n9l3SvsJDtJYe7bG/OmhEk=; b=GDqmbb7tahG81iCxYgETE0eQnO9Aple66bw04yzMIFBWSzYx5COoK2qE h9J9MF4eFqO0p/G+KurKb0oYcHvKtLOTKGC0S9YuihGMrCgyFAMPZ+fXk bn7aodGE7cOL1jBzr1N80PLLWn5tEfWxUtFqqIFiSDjzn0JhEHobeB3RV 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,6431"; a="108461498"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 07 Aug 2011 10:58:06 -0700
X-IronPort-AV: E=Sophos;i="4.67,333,1309762800"; d="scan'208";a="155319340"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 07 Aug 2011 10:58:06 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.323.0; Sun, 7 Aug 2011 10:58:06 -0700
Message-ID: <4E3ED22B.3060405@qualcomm.com>
Date: Sun, 7 Aug 2011 12:58:03 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Glen Zorn <gwz@net-zen.net>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net>
In-Reply-To: <4E3B9FC6.7090701@net-zen.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: iaoc-mtgs@ISOC.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Aug 2011 17:57:45 -0000

On 8/5/11 2:46 AM, Glen Zorn wrote:
> I note that there is an opening on the IETF meeting calendar for an
> Asian meeting in 2013.  Here is a suggestion:
>
> Meeting Facilities:
> http://www.qsncc.com/venue-information/our-facilities.html
>    

I'm happy to have the IAOC look at this site. But one of the items that 
I've heard is consistently on the "wish list" for sites is "under one 
roof". Looking at the hotel list and at Google maps, there isn't a hotel 
closer than 1km walk from the convention center, and the larger ones are 
further than that. That's not a show-stopper, but I can say personally 
that I am lazy and do not relish the walk at 7:15am to make it to the 
IESG meeting. I was similarly not a fan of the Vienna IETF meeting site, 
which was likewise situated away from the hotels.

Again, not the end of the world (cheaper lodging prices are welcome), 
but neither is it ideal.

pr

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


From mcr@sandelman.ca  Sun Aug  7 17:25:08 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D97421F87F0 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 17:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.713
X-Spam-Level: 
X-Spam-Status: No, score=-1.713 tagged_above=-999 required=5 tests=[AWL=0.241,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hjNcDgmd8Wdp for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 17:25:07 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2A11621F855F for <ietf@ietf.org>; Sun,  7 Aug 2011 17:25:07 -0700 (PDT)
Received: from marajade.sandelman.ca (wlan204.sandelman.ca [209.87.252.204]) by relay.sandelman.ca (Postfix) with ESMTPS id 0E6A83423C; Sun,  7 Aug 2011 20:25:02 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id E41F998411; Sun,  7 Aug 2011 20:25:41 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <4E3ED22B.3060405@qualcomm.com>
References: <4E3B9FC6.7090701@net-zen.net> <4E3ED22B.3060405@qualcomm.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Sun, 07 Aug 2011 20:25:41 -0400
Message-ID: <4179.1312763141@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: iaoc-mtgs@ISOC.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 00:25:08 -0000

>>>>> "Pete" == Pete Resnick <presnick@qualcomm.com> writes:
    Pete> On 8/5/11 2:46 AM, Glen Zorn wrote:
    >> I note that there is an opening on the IETF meeting calendar for
    >> an Asian meeting in 2013.  Here is a suggestion:
    >> 
    >> Meeting Facilities:
    >> http://www.qsncc.com/venue-information/our-facilities.html
    >> 

    Pete> I'm happy to have the IAOC look at this site. But one of the
    Pete> items that I've heard is consistently on the "wish list" for
    Pete> sites is "under one roof". Looking at the hotel list and at
    Pete> Google maps, there isn't a hotel closer than 1km walk from the
    Pete> convention center, and the larger ones are further than
    Pete> that. That's not a show-stopper, but I can say personally that
    Pete> I am lazy and do not relish the walk at 7:15am to make it to
    Pete> the IESG meeting. I was similarly not a fan of the Vienna IETF
    Pete> meeting site, which was likewise situated away from the
    Pete> hotels.

Yes, and we repeated this in numerous other places too. 
Maastrich and Dublin (I'm told).
Montreal (both times)...

The problem with Vienna wasn't that the was a walk, but that there was
no canonical bar!!!!  This is *REALLY* the problem.  IETFs want a place
to sit and relax and 

In fact, the walk from the Hilton to the Quebec Conference Centre was
pretty close to 1km, and we didn't seem to have a canonical bar either.
Some suggested that had the reception room in Quebec had food/drink
service, it would have actually been very very very good.
(but, I would argue that Commensal was in fact that canonical lunch
location...) 

I travelled 15m on RTC (Quebec City) from Laval University.  
The residences were pretty rough, but I wasn't bothered because the
7minute frequency continued on until 1am.  In Vienna it also wasn't a
long trip, but there was obvious place to "run into" other IETFers.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From fred@cisco.com  Sun Aug  7 17:40:33 2011
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BCC521F87ED for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 17:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.868
X-Spam-Level: 
X-Spam-Status: No, score=-102.868 tagged_above=-999 required=5 tests=[AWL=-0.269, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDLaQPjjyj5d for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 17:40:32 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id BDDEA21F87D9 for <ietf@ietf.org>; Sun,  7 Aug 2011 17:40:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=413; q=dns/txt; s=iport; t=1312764057; x=1313973657; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=78BPVxntyJ5obt4FLlY3sdoODA1NxpVOXhMiwXkHeCw=; b=eNc1NIzzQbMPc4N45rcmMd7BWfDFlS4asGRVwPHHfflb026lNDcPW/4e lkbHFeqJ8FXYrYVQqBltcT9+LdcCQrAdO4mw6Ul7NRdnEDeuSiZuAkRPO MqjJy6T899Zflux8H5Nac/i81c4kbWgptS/wG3Zyprhlytsu3T8UtC2TD 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAAIwP06rRDoJ/2dsb2JhbABCpzV3gUABAQEBAgESAScuEQULCw44VwY1h0ucRgGdRIVnXwSHXIsmhQiMAA
X-IronPort-AV: E=Sophos;i="4.67,334,1309737600"; d="scan'208";a="10624046"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-6.cisco.com with ESMTP; 08 Aug 2011 00:40:56 +0000
Received: from stealth-10-32-244-221.cisco.com (stealth-10-32-244-221.cisco.com [10.32.244.221]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p780eucu032469; Mon, 8 Aug 2011 00:40:56 GMT
Received: from [127.0.0.1] by stealth-10-32-244-221.cisco.com (PGP Universal service); Sun, 07 Aug 2011 17:40:56 -0700
X-PGP-Universal: processed; by stealth-10-32-244-221.cisco.com on Sun, 07 Aug 2011 17:40:56 -0700
Subject: Re: Queen Sirikit National Convention Center
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4179.1312763141@marajade.sandelman.ca>
Date: Sun, 7 Aug 2011 17:40:48 -0700
Message-Id: <DA637393-B05B-45E7-9A8B-DCCC8D79C1CF@cisco.com>
References: <4E3B9FC6.7090701@net-zen.net> <4E3ED22B.3060405@qualcomm.com> <4179.1312763141@marajade.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qualcomm.com>, iaoc-mtgs@ISOC.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 00:40:33 -0000

On Aug 7, 2011, at 5:25 PM, Michael Richardson wrote:

> In fact, the walk from the Hilton to the Quebec Conference Centre was
> pretty close to 1km

?

It was out the lobby behind the restaurant and down two escalators. Even =
if you walked across the courtyard at street level and then wandered =
back to the location we were using - the way I walked the first time I =
found it - it wasn't a km.=

From prvs=0201256df7=medel@globetel.com.ph  Sun Aug  7 17:58:35 2011
Return-Path: <prvs=0201256df7=medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50C8021F87C7 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 17:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.419
X-Spam-Level: 
X-Spam-Status: No, score=-1.419 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTLSN6Rw-OGO for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 17:58:34 -0700 (PDT)
Received: from smtp01.globetel.com.ph (smtp01.globetel.com.ph [203.177.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 325C321F87C5 for <ietf@ietf.org>; Sun,  7 Aug 2011 17:58:34 -0700 (PDT)
Received: from exgtbh01.globetel.com ([10.225.208.17]) by smtp01.globetel.com.ph (8.14.4/8.14.4) with ESMTP id p780waOp020128;  Mon, 8 Aug 2011 08:58:37 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.145]) by exgtbh01.globetel.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Aug 2011 08:58:56 +0800
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: Last Call: <draft-housley-two-maturity-levels-08.txt>(Reducing the Standards Track to Two Maturity Levels) to BCP
Date: Mon, 8 Aug 2011 08:57:38 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE121089B6@EXVSGT02.globetel.com>
In-Reply-To: <6.2.5.6.2.20110804043544.084eb5c0@resistor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-housley-two-maturity-levels-08.txt>(Reducing the Standards Track to Two Maturity Levels) to BCP
Thread-Index: AcxTVTe8bxf1oBvYRJqySR6/A4yodQCD/l2A
X-Priority: 1
Priority: Urgent
Importance: high
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com><6.2.5.6.2.20110728234859.075cb888@resistor.net><B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: "SM" <sm@resistor.net>
X-OriginalArrivalTime: 08 Aug 2011 00:58:56.0760 (UTC) FILETIME=[59BEBF80:01CC5566]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-08-07_03:2011-08-07, 2011-08-07, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1108070317
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 00:58:35 -0000

Hi SM,
Pardon me;
1)Is there such thing as a "good enough" Criteria to handle this
concern?
2)Or as usual it passes "rough consensus" process?

Regards,
Medel
++++++++++++++++++++++++++++++++++++++++

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
SM
Sent: Friday, August 05, 2011 5:45 PM
To: Russ Housley
Cc: ietf@ietf.org
Subject: Re: Last Call:
<draft-housley-two-maturity-levels-08.txt>(Reducing the Standards Track
to Two Maturity Levels) to BCP

Hi Russ,
At 12:28 PM 8/3/2011, Russ Housley wrote:
>I am well aware of the implementation reports.  The premise here is=20
>that the protocol specification is "good enough" there are at least=20
>two interoperable implementations and the protocol is deployed=20
>widely.  The implementation report would become optional.

One of the advantages of an implementation report is that it provides=20
a statement about interoperability between two or more known=20
implementations.  If there is any dispute about that claim, it can be=20
resolved in a non-controversial way.  Determining whether a protocol=20
is widely deployed is not always a clear-cut decision.

>People are not doing many implementation reports.  As you say above,=20
>there are only about 75 of them.  How many protocols are documented=20
>in RFCs?  That is a very low percentage in my view.

Yes, it's a very low percentage.  I don't have the figure for the=20
number of protocols documented.  Given the low barrier for such=20
reports, I would have expected to see more reports.  After all, if=20
the RFC has been published, the protocol has been widely deployed, it=20
should simply have been a matter of filing the short report.

 From draft-housley-two-maturity-levels-08:

    "this document measures interoperability through widespread
deployment
     of multiple implementations from different code bases, thus
condensing
     the two separate metrics into one."

This change is expected to solve the problem.  I am not convinced=20
that the metrics is the problem.

>So, I see the cost quite differently.  Most protocols are published=20
>as Proposed Standards, and they are never advanced.  I'm seeking a=20
>process where implementation and deployment experience actually=20
>improves the protocol specifications.  Today, that rarely happens,=20
>and when it does, the

Agreed.

I didn't find any incentive to inject implementation and deployment=20
experience into the process.

>This is an argument for the status quo.  We have decades of=20
>experience with that not working.  That is essentially an argument=20
>for a single maturity level; that is how the process is really working
today.

I am not arguing for a single maturity level (the status quo).  I do=20
not agree with the conclusion that the decades of stagnation is due=20
to the three maturity level.

>This document is not about IESG review time, except for the=20
>elimination of the requirement for annual reviews which are not done=20
>anyway.  If that is what you get from the document, then I have done=20
>a very poor job in writing it.  That is not the point at all.

I don't think that you did a poor job.  A three maturity level=20
requires three IESG Evaluations.  A two maturity level requires two=20
IESG Evaluations.  If more documents moved from Proposed Standard to=20
the next level, it would obviously take more IESG review time.

I presume that the IESG will only use the following criteria for
advancement:

  - two independent interoperating implementations with widespread
    deployment and successful operational experience

  - no errata against the specification

  - no unused features in the specification

And there won't be any DISCUSSes along the lines of:

   "I don't think the implementation reports are adequate for me to meet
the
    requirements of 2026. It does not clearly identify what software=20
was used or
    show support of each of the individual options and features."

   "Examples througout the document make use of non-example domains."

   "The implementation report is woefully inadequate to document there
are
    interoperable implementations of all the features from two different
    code bases."

   "My Discuss was not addressed at all - I believe that the WG ignored
the
    spirit of the implementation report requirement - my Discuss said
that
    we should know that there are multiple implementations that have
    handled the significant changes in the recycling of this Draft
Standard.
    The group apparently refused to update its implementation report"

Regards,
-sm=20

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

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From hsantos@isdg.net  Sun Aug  7 18:21:54 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B6B21F86DE for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 18:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.37
X-Spam-Level: 
X-Spam-Status: No, score=-3.37 tagged_above=-999 required=5 tests=[AWL=-0.771,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IasQSMZ9nDrv for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 18:21:53 -0700 (PDT)
Received: from mail.catinthebox.net (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC3A21F86D7 for <ietf@ietf.org>; Sun,  7 Aug 2011 18:21:53 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1362; t=1312766533; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=T2FsP8bsHdabBY+20INjzkoev9Y=; b=Tgl8TBRc0g/1ssYOE3dL tVf1QjdDoLSz6/CcGBXuQrhZ7nF/kAlrVX7QDHDDq38YR+jesxxX3YjYduYU5G+E vOxdsST2Ot4LujU11c4bfRyaOkFmThJYJM/6hN9s4F1KEjxYxzYpln6mFGuBRw/r OaiAITQSBGvuNScTsePEHLI=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 07 Aug 2011 21:22:13 -0400
Authentication-Results: dkim.winserver.com; dkim=fail (DKIM_SIGNATURE_BAD) header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=fail policy=all author.d=isdg.net asl.d=beta.winserver.com (unauthorized signer); 
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1222000483.42168.3048; Sun, 07 Aug 2011 21:21:59 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312766241; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=TPO0T1Q6yLTTxHOUS2 /bxVNlPtV//RsH+edxjWuLXMw=; b=Ru8lP46oCMGlARhTyc5LFN5qJ2oR+wpb/9 +PaFdk7x9BFWGWCuGY7HHGxqjXBIsw+PgjcRs4ur6Kq99SlWjJALJg2MxsTIZhXm fe7EsSrrskHvnGvSYk9/Skl+4kw/xGsw4NWt8W+viuWBX6C/s6AdXvEHB4uv4pOK bflLELpCQ=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 07 Aug 2011 21:17:21 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2193279518.563.7240; Sun, 07 Aug 2011 21:17:20 -0400
Message-ID: <4E3F3A56.806@isdg.net>
Date: Sun, 07 Aug 2011 21:22:30 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt>	(Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net>
In-Reply-To: <6.2.5.6.2.20110804043544.084eb5c0@resistor.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 01:21:54 -0000

SM wrote:

>> People are not doing many implementation reports.  As you say above, 
>> there are only about 75 of them.  How many protocols are documented in 
>> RFCs?  That is a very low percentage in my view.
> 
> Yes, it's a very low percentage.  I don't have the figure for the number 
> of protocols documented.  Given the low barrier for such reports, I 
> would have expected to see more reports.  After all, if the RFC has been 
> published, the protocol has been widely deployed, it should simply have 
> been a matter of filing the short report.

Of course, when implementation reports are written, one has to 
watchful for the summarized analytical results that either attempt to 
add weight to an desired goal or mask the undesired goal and natural 
result.

In one such report, I was able to show the data collection indicated 
an undesired result was indeed the natural and dominant implementation 
mode.  The 2nd revision tweaked the semantics enough to hide the 
higher weight of the data collected for the undesirable dominant mode. 
  When that change was also seen and noted, it was added back in the 
3rd revision as a "oops" exclusion.

This is not an exercise we should have to go through.  Engineers must 
have complete faith in implementation reports.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From rcallon@juniper.net  Sun Aug  7 20:46:50 2011
Return-Path: <rcallon@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEC2521F882E for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 20:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFGgbP5LgPum for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 20:46:49 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id E1D5521F85C0 for <ietf@ietf.org>; Sun,  7 Aug 2011 20:46:47 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTj9cP265lyVh++g9Tpolwic0ckVqAhnR@postini.com; Sun, 07 Aug 2011 20:47:14 PDT
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; Sun, 7 Aug 2011 20:45:55 -0700
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; Sun, 7 Aug 2011 23:45:55 -0400
From: Ross Callon <rcallon@juniper.net>
To: Pete Resnick <presnick@qualcomm.com>, Glen Zorn <gwz@net-zen.net>
Date: Sun, 7 Aug 2011 23:45:53 -0400
Subject: RE: Queen Sirikit National Convention Center
Thread-Topic: Queen Sirikit National Convention Center
Thread-Index: AcxVK6XwDg1g9te7QNulfULShIrNrgAUPHzA
Message-ID: <DF7F294AF4153D498141CBEFADB17704C2E190C704@EMBX01-WF.jnpr.net>
References: <4E3B9FC6.7090701@net-zen.net> <4E3ED22B.3060405@qualcomm.com>
In-Reply-To: <4E3ED22B.3060405@qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc-mtgs@ISOC.org" <iaoc-mtgs@ISOC.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 03:46:50 -0000

I attended an APRICOT meeting at the Queen Sirikit National Convention Cent=
er many years ago. The bad news is that we needed to take cabs back and for=
th between our hotel and the meeting. The good news is that at least at tha=
t time cabs were readily available and *very* reasonably priced. The meetin=
g location seemed quite good to me (from my recollection). The hotel that w=
e stayed at was not horridly expensive, but was not cheap and the US dollar=
 has probably lost about half of its value since then (it was a very nice h=
otel that catered to westerners).=20

Ross

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Pet=
e Resnick
Sent: Sunday, August 07, 2011 1:58 PM
To: Glen Zorn
Cc: iaoc-mtgs@ISOC.org; IETF Discussion
Subject: Re: Queen Sirikit National Convention Center

On 8/5/11 2:46 AM, Glen Zorn wrote:
> I note that there is an opening on the IETF meeting calendar for an
> Asian meeting in 2013.  Here is a suggestion:
>
> Meeting Facilities:
> http://www.qsncc.com/venue-information/our-facilities.html
>   =20

I'm happy to have the IAOC look at this site. But one of the items that=20
I've heard is consistently on the "wish list" for sites is "under one=20
roof". Looking at the hotel list and at Google maps, there isn't a hotel=20
closer than 1km walk from the convention center, and the larger ones are=20
further than that. That's not a show-stopper, but I can say personally=20
that I am lazy and do not relish the walk at 7:15am to make it to the=20
IESG meeting. I was similarly not a fan of the Vienna IETF meeting site,=20
which was likewise situated away from the hotels.

Again, not the end of the world (cheaper lodging prices are welcome),=20
but neither is it ideal.

pr

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

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

From mnot@mnot.net  Sun Aug  7 21:35:32 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A911B11E807C for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 21:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.671
X-Spam-Level: 
X-Spam-Status: No, score=-105.671 tagged_above=-999 required=5 tests=[AWL=-3.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJY4PoRoSj2G for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 21:35:31 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id C5D4911E8078 for <ietf@ietf.org>; Sun,  7 Aug 2011 21:35:31 -0700 (PDT)
Received: from host9027e4f94482.mnot.net (unknown [118.209.98.127]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DBFC3509DB; Mon,  8 Aug 2011 00:35:49 -0400 (EDT)
Subject: Re: Queen Sirikit National Convention Center
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/mixed; boundary=Apple-Mail-8--536502398
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4E3B9FC6.7090701@net-zen.net>
Date: Mon, 8 Aug 2011 14:35:46 +1000
Message-Id: <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net>
References: <4E3B9FC6.7090701@net-zen.net>
To: Glen Zorn <gwz@net-zen.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 04:35:32 -0000

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

Looks fine to me. I have very little sympathy for those whinging about =
long flights.

While where at it:
  http://www.mcec.com.au/

Brand-new conference centre, canonical hotel is a Hilton, and boy can I =
show you some bars...

Cheers,


On 05/08/2011, at 5:46 PM, Glen Zorn wrote:

> I note that there is an opening on the IETF meeting calendar for an
> Asian meeting in 2013.  Here is a suggestion:
>=20
> Meeting Facilities:
> http://www.qsncc.com/venue-information/our-facilities.html
>=20
> There are 7 pages of "Official Hotels", starting at about $60/night.
>=20
> Official Hotels: http://www.qsncc.com/visitor/official-hotels.html

--Apple-Mail-8--536502398
Content-Disposition: attachment;
	filename=gwz.vcf
Content-Type: text/x-vcard;
	name="gwz.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--Apple-Mail-8--536502398
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

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

--
Mark Nottingham   http://www.mnot.net/




--Apple-Mail-8--536502398--

From gwz@net-zen.net  Sun Aug  7 22:58:21 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E4F21F87C5 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 22:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LP58DlBdNo74 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 22:58:19 -0700 (PDT)
Received: from smtpauth20.prod.mesa1.secureserver.net (smtpauth20.prod.mesa1.secureserver.net [64.202.165.36]) by ietfa.amsl.com (Postfix) with SMTP id C201921F8751 for <ietf@ietf.org>; Sun,  7 Aug 2011 22:58:19 -0700 (PDT)
Received: (qmail 10878 invoked from network); 8 Aug 2011 05:58:40 -0000
Received: from unknown (58.11.239.227) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 08 Aug 2011 05:58:39 -0000
Message-ID: <4E3F7B08.4000209@net-zen.net>
Date: Mon, 08 Aug 2011 12:58:32 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <4E3ED22B.3060405@qualcomm.com>
In-Reply-To: <4E3ED22B.3060405@qualcomm.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------030703040003090400000205"
Cc: iaoc-mtgs@ISOC.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 05:58:21 -0000

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

On 8/8/2011 12:58 AM, Pete Resnick wrote:
> On 8/5/11 2:46 AM, Glen Zorn wrote:
>> I note that there is an opening on the IETF meeting calendar for an
>> Asian meeting in 2013.  Here is a suggestion:
>>
>> Meeting Facilities:
>> http://www.qsncc.com/venue-information/our-facilities.html
>>    
> 
> I'm happy to have the IAOC look at this site. But one of the items that
> I've heard is consistently on the "wish list" for sites is "under one
> roof". Looking at the hotel list and at Google maps, there isn't a hotel
> closer than 1km walk from the convention center, and the larger ones are
> further than that. That's not a show-stopper, but I can say personally
> that I am lazy and do not relish the walk at 7:15am to make it to the
> IESG meeting. 

I would not recommend walking in any case (Thai people rarely walk any
further than absolutely necessary ;-).  However, the CC has it's own
subway stop, with convenient connections to the Sky Train.  Some hotels
are more convenient than others, of course; for example, the Westin and
Sheraton are located adjacent to & opposite, respectively, a subway
station one stop from the CC.  In any case, a taxi from any of the
hotels on the list would today cost < $3 (probably closer to $2) one way.

> I was similarly not a fan of the Vienna IETF meeting site,
> which was likewise situated away from the hotels.
> 
> Again, not the end of the world (cheaper lodging prices are welcome),
> but neither is it ideal.
> 
> pr
> 

--------------030703040003090400000205
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------030703040003090400000205--

From gwz@net-zen.net  Sun Aug  7 23:26:15 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7C821F8997 for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 23:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HeZDX+gQFikm for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 23:26:14 -0700 (PDT)
Received: from p3plsmtpa07-05.prod.phx3.secureserver.net (p3plsmtpa07-05.prod.phx3.secureserver.net [173.201.192.234]) by ietfa.amsl.com (Postfix) with SMTP id 9376721F898E for <ietf@ietf.org>; Sun,  7 Aug 2011 23:26:14 -0700 (PDT)
Received: (qmail 7496 invoked from network); 8 Aug 2011 06:26:39 -0000
Received: from unknown (58.11.239.227) by p3plsmtpa07-05.prod.phx3.secureserver.net (173.201.192.234) with ESMTP; 08 Aug 2011 06:26:38 -0000
Message-ID: <4E3F8199.2090809@net-zen.net>
Date: Mon, 08 Aug 2011 13:26:33 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net>
In-Reply-To: <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------060902020709030108070705"
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 06:26:15 -0000

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

On 8/8/2011 11:35 AM, Mark Nottingham wrote:
> Looks fine to me. I have very little sympathy for those whinging
> about long flights.
> 
> While where at it: http://www.mcec.com.au/
> 
> Brand-new conference centre, canonical hotel is a Hilton, and boy can
> I show you some bars...

Unfortunately, the cheapest room @ the Hilton Melbourne South Wharf
right now is > $290/night (AU$280).

...

--------------060902020709030108070705
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------060902020709030108070705--

From mnot@mnot.net  Sun Aug  7 23:31:34 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1F921F893C for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 23:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.653
X-Spam-Level: 
X-Spam-Status: No, score=-105.653 tagged_above=-999 required=5 tests=[AWL=-3.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id suC7mMc5H5pA for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 23:31:33 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 1621521F88B6 for <ietf@ietf.org>; Sun,  7 Aug 2011 23:31:33 -0700 (PDT)
Received: from host9027e4f94482.mnot.net (unknown [118.209.98.127]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 20BF050A64; Mon,  8 Aug 2011 02:31:49 -0400 (EDT)
Subject: Re: Queen Sirikit National Convention Center
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4E3F8199.2090809@net-zen.net>
Date: Mon, 8 Aug 2011 16:31:46 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <44669682-8560-4100-8871-F6876BB695F6@mnot.net>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net>
To: Glen Zorn <gwz@net-zen.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 06:31:34 -0000

On 08/08/2011, at 4:26 PM, Glen Zorn wrote:

> On 8/8/2011 11:35 AM, Mark Nottingham wrote:
>> Looks fine to me. I have very little sympathy for those whinging
>> about long flights.
>>=20
>> While where at it: http://www.mcec.com.au/
>>=20
>> Brand-new conference centre, canonical hotel is a Hilton, and boy can
>> I show you some bars...
>=20
> Unfortunately, the cheapest room @ the Hilton Melbourne South Wharf
> right now is > $290/night (AU$280).


Doesn't seem that much more than Quebec City, IIRC. And, of course, =
there are *plenty* of hotels within a reasonable walk.

Anyway.

Cheers,


--
Mark Nottingham   http://www.mnot.net/




From ole@cisco.com  Mon Aug  8 00:56:19 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8B0821F89B8 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 00:56:19 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rm7EOrvJk2JT for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 00:56:19 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 403F321F8A36 for <ietf@ietf.org>; Mon,  8 Aug 2011 00:56:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=526; q=dns/txt; s=iport; t=1312790204; x=1313999804; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=SIzVxSzGnQK4VeeLhpCn/usAlljaQ4dFE0HGaqyBhYA=; b=FiKclfpwefYdyOdHoy8+dASN5U9sGz2RVullNs/w3DJ1mihdsfqj3nZ8 GYQCpYXxUkJyFvj6KHdVA/qM0WcalsoZ2qoLDOlXOLJ+OKA4f7qj4VNwX jxmylK/XVYH5ZFTaXUnDsN4d1F/d2yd9zS9RiF1elfQV8k8wIMTDaix9o c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EALuVP06rRDoH/2dsb2JhbABCpzh3gUABAQEBAgESAQIBJC4REAsOOFcGNYdLnjIBgxwPAZpZhkYEh1ycLg
X-IronPort-AV: E=Sophos;i="4.67,336,1309737600"; d="scan'208";a="10711585"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-2.cisco.com with ESMTP; 08 Aug 2011 07:56:43 +0000
Received: from sjc-vpn7-506.cisco.com (sjc-vpn7-506.cisco.com [10.21.145.250]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p787ugpx011896; Mon, 8 Aug 2011 07:56:42 GMT
Date: Mon, 8 Aug 2011 00:56:42 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <44669682-8560-4100-8871-F6876BB695F6@mnot.net>
Message-ID: <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 07:56:20 -0000

Nothing is "a reasonable walk" when the average temperature is 32 C.
At least not for the "average" IETF attendee.

(34 in April, 31 in December, lowest nightime temp 21 in December and
27 in April-May-June).

We did APRICOT at this venue in 2002. Not a bad place for a 
conference, but most certainly requires transportation to the hotels.


ole

On Mon, 8 Aug 2011, Mark Nottingham wrote:

> 
> And, of course, there are *plenty* of hotels within a reasonable 
> walk.
> 
> Anyway.
> 
> Cheers,
> 

From ole@cisco.com  Mon Aug  8 00:57:06 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E34321F8559 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 00:57:06 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xErnfa5RtwtH for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 00:57:05 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id A3E9721F854C for <ietf@ietf.org>; Mon,  8 Aug 2011 00:57:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=271; q=dns/txt; s=iport; t=1312790251; x=1313999851; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=gd5X8f7zY6doyIM9hmrv9mo0Si8MpljwZa5vXH9u05E=; b=EBlx/WnVyC2A3QGX4MuFjwPbA7fJWdsOQzV1nkBbQi5MkZbAOtViVso6 Ls4Pu8003vJuHCnjSL0yLQgReERkWwmty4BHzSjB5sxh0T5Ru+LZYG2ri Wvd4KORWKYCWxXzbGzRiD3hmWlIolwM19YaK056xf8F1ZygMXZQ9bIw86 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EALuVP06rRDoH/2dsb2JhbAA/A6c4d4FAAQEBAQMSAQIBJD8QCw44VwYTIqV9AYMcDwGaWYNAgwYEh1yVFYcZ
X-IronPort-AV: E=Sophos;i="4.67,336,1309737600"; d="scan'208";a="10711318"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-4.cisco.com with ESMTP; 08 Aug 2011 07:57:30 +0000
Received: from sjc-vpn7-506.cisco.com (sjc-vpn7-506.cisco.com [10.21.145.250]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p787vUIg012674; Mon, 8 Aug 2011 07:57:30 GMT
Date: Mon, 8 Aug 2011 00:57:29 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <44669682-8560-4100-8871-F6876BB695F6@mnot.net>
Message-ID: <alpine.OSX.2.01.1108080057110.15710@sjc-vpn7-506.cisco.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 07:57:06 -0000

Oh, I see you were referring to Melbourne, sorry :-)

ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From ynir@checkpoint.com  Mon Aug  8 06:56:40 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF70021F8AE1 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 06:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.497
X-Spam-Level: 
X-Spam-Status: No, score=-10.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GtPh5JWphX71 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 06:56:40 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA4321F8ADE for <ietf@ietf.org>; Mon,  8 Aug 2011 06:56:39 -0700 (PDT)
X-CheckPoint: {4E3FF8A8-2-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p78Duw0f000445;  Mon, 8 Aug 2011 16:56:58 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Mon, 8 Aug 2011 16:56:58 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ole Jacobsen <ole@cisco.com>
Date: Mon, 8 Aug 2011 16:56:57 +0300
Subject: Re: Queen Sirikit National Convention Center
Thread-Topic: Queen Sirikit National Convention Center
Thread-Index: AcxV0wmws6HaWZvHQ86sIibUPIJdvg==
Message-ID: <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 13:56:40 -0000

On Aug 8, 2011, at 10:56 AM, Ole Jacobsen wrote:

>=20
>=20
> Nothing is "a reasonable walk" when the average temperature is 32 C.
> At least not for the "average" IETF attendee.
>=20
> (34 in April, 31 in December, lowest nightime temp 21 in December and
> 27 in April-May-June).

Pretty much like Tel Aviv in August.

Tucson or Phoenix have much higher temperatures, but what it lacks in raw d=
egrees, Bangkok makes up for with suffocating humidity.

I don't think there's an amount of air conditioning that would make me comp=
lain in Bangkok.=

From john-ietf@jck.com  Mon Aug  8 07:42:48 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B37F21F8B08 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7--L+uf-6rn for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:42:47 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 84F5221F8B05 for <ietf@ietf.org>; Mon,  8 Aug 2011 07:42:47 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QqR2p-000LvJ-V2; Mon, 08 Aug 2011 10:43:08 -0400
Date: Mon, 08 Aug 2011 10:43:07 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir@checkpoint.com>, Ole Jacobsen <ole@cisco.com>
Subject: Re: Queen Sirikit National Convention Center
Message-ID: <1D5C586851E84A87B99E6E0A@PST.JCK.COM>
In-Reply-To: <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@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: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 14:42:48 -0000

--On Monday, August 08, 2011 16:56 +0300 Yoav Nir
<ynir@checkpoint.com> wrote:

>> (34 in April, 31 in December, lowest nightime temp 21 in
>> December and 27 in April-May-June).
> 
> Pretty much like Tel Aviv in August.
> 
> Tucson or Phoenix have much higher temperatures, but what it
> lacks in raw degrees, Bangkok makes up for with suffocating
> humidity.
> 
> I don't think there's an amount of air conditioning that would
> make me complain in Bangkok.

I've been in meetings in Bangkok and been cold in the meeting
rooms.  Of course, tastes differ... but I grew up in Tucson and
rather liked the summers especially as long as relative humidity
stayed in single digits. :-)

Of course, given some of the other suggestions made recently, we
probably should also be considering Tel Aviv as a meeting site
-- from what I understand, non-trivial numbers of IETF
participants (unlike some places discussed recently), plausible
hotel costs, decent airport and international connections, good
in-country Internet infrastructure.  Might be plausible for a
late fall or early spring meeting if there are adequate meeting
facilities... I take the above to be a hint that August should
be avoided.

    john






From eburger@standardstrack.com  Fri Aug  5 10:45:09 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B475E21F8BAE for <ietf@ietfa.amsl.com>; Fri,  5 Aug 2011 10:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.361
X-Spam-Level: 
X-Spam-Status: No, score=-102.361 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMpWOv-loyeK; Fri,  5 Aug 2011 10:45:09 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 295AA21F8B86; Fri,  5 Aug 2011 10:45:09 -0700 (PDT)
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:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=U1z3f/KZqtqoUubVVJ5bL5Ix+ddLfZ5DGcgRsJpfxc/lus/YfnHD10BtlK6K1WG9PANeQLVAiDNIuYBpPevLo4FhU0xL9E7L3gPMWOZq9fGqijuZNd5BFSjPZuMxse8Y;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QpJR5-0000wj-M5; Fri, 05 Aug 2011 05:23:31 -0700
Subject: Re: Queen Sirikit National Convention Center
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4E3B9FC6.7090701@net-zen.net>
Date: Fri, 5 Aug 2011 08:23:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4E77A49-E1C6-4A5E-8425-E4BC1DFF9FCD@standardstrack.com>
References: <4E3B9FC6.7090701@net-zen.net>
To: Glen Zorn <gwz@net-zen.net>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Mailman-Approved-At: Mon, 08 Aug 2011 07:44:15 -0700
Cc: Jacobsen Ole <ole@cisco.com>, IETF Discussion <ietf@ietf.org>, odonoghue@iisoc.org, Uijterwaal Henk <henk@uijterwaal.nl>, Bob Hinden <bob.hinden@gmail.com>, Eubanks Marshall <tme@americafree.tv>, "St. Amour Lynn" <st.amour@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 17:45:09 -0000

I like Thailand, and Bangkok is a StarAlliance hub. I am assuming the =
political troubles are settled now, and probably will be for sure in 2 =
years.


On Aug 5, 2011, at 3:46 AM, Glen Zorn wrote:

> I note that there is an opening on the IETF meeting calendar for an
> Asian meeting in 2013.  Here is a suggestion:
>=20
> Meeting Facilities:
> http://www.qsncc.com/venue-information/our-facilities.html
>=20
> There are 7 pages of "Official Hotels", starting at about $60/night.
>=20
> Official Hotels: http://www.qsncc.com/visitor/official-hotels.html
> <gwz.vcf>


From john@jck.com  Sun Aug  7 09:44:57 2011
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4EB21F854D for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 09:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hs0EwkiEPjZi for <ietf@ietfa.amsl.com>; Sun,  7 Aug 2011 09:44:56 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 5561F21F84FD for <ietf@ietf.org>; Sun,  7 Aug 2011 09:44:56 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qq6TX-0009fO-Dw for ietf@ietf.org; Sun, 07 Aug 2011 12:45:19 -0400
X-Vipre-Scanned: 04950A9500276E04950BE2-TDI
Date: Sun, 07 Aug 2011 12:45:18 -0400
From: John C Klensin <john@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt>	(Reducing the Standards Track to Two Maturity Levels) to BCP
Message-ID: <420C8B2470E5AAC8A12E5740@[192.168.1.128]>
In-Reply-To: <6.2.5.6.2.20110804043544.084eb5c0@resistor.net>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.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-Mailman-Approved-At: Mon, 08 Aug 2011 07:44:15 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Aug 2011 16:44:57 -0000

To add one observation to SM's comment and other observations
that the scarcity of implementation reports implies that they
are somehow difficult...

--On Friday, August 05, 2011 02:45 -0700 SM <sm@resistor.net>
wrote:
 
> I presume that the IESG will only use the following criteria
> for advancement:
> 
>   - two independent interoperating implementations with
> widespread
>     deployment and successful operational experience
> 
>   - no errata against the specification
> 
>   - no unused features in the specification
> 
> And there won't be any DISCUSSes along the lines of:
> 
>    "I don't think the implementation reports are adequate for
> me to meet the
>     requirements of 2026. It does not clearly identify what
> software was used or
>     show support of each of the individual options and
> features."
> 
>    "Examples througout the document make use of non-example
> domains."
> 
>    "The implementation report is woefully inadequate to
> document there are
>     interoperable implementations of all the features from two
> different code bases."
> 
>    "My Discuss was not addressed at all - I believe that the
> WG ignored the
>     spirit of the implementation report requirement - my
> Discuss said that
>     we should know that there are multiple implementations
> that have
>     handled the significant changes in the recycling of this
> Draft Standard.
>     The group apparently refused to update its implementation
> report"

An alternate hypothesis about the low numbers of implementation
reports on file is that people try them, get responses like the
ones SM lists above, and react with "why bother -- this is a
waste of time that I can better spend in other ways".  And that
is the end, not just of the report being commented on, but any
others that could have come from that author or participant.  

While it has not been raised as a specific argument for this
two-maturity-levels proposal, getting rid of formal
implementation reports might, for that reason, be useful in
getting documents advanced.  However, it does not improve the
case for two levels instead of three and won't help if IESG
members express the same thoughts --not in terms of
interoperability reports but in terms of lack of conviction the
interoperability had actually been demonstrated in the case of
that particular spec.  

I note that, when RFC 4846 and what became 5742 were under
discussion, a then-IESG member pointed out to me that, despite
the restrictions in those documents, if something in a draft
really offended him, he could always find a way to state his
objections in a way that would conform to the 4846/5742 rules.
The same comment presumably applies to presumed proofs of
independent interoperable implementations.

   john


From frnkblk@iname.com  Sun Aug  7 21:22:33 2011
Return-Path: <frnkblk@iname.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DFC121F877F; Sun,  7 Aug 2011 21:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.354
X-Spam-Level: 
X-Spam-Status: No, score=-2.354 tagged_above=-999 required=5 tests=[AWL=1.145,  BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, GB_I_LETTER=-2, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D20pK9NAmZJ3; Sun,  7 Aug 2011 21:22:32 -0700 (PDT)
Received: from premieronline.net (smtp1-3.premieronline.net [96.31.0.23]) by ietfa.amsl.com (Postfix) with ESMTP id 40BD621F8548; Sun,  7 Aug 2011 21:22:29 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=199.120.69.26; 
Received: from BULKFAMLAPTOP (unverified [199.120.69.26])  by premieronline.net (SurgeMail 5.0n) with ESMTP id 29531710-1729245  for multiple; Sun, 07 Aug 2011 23:22:53 -0500
From: "Frank Bulk" <frnkblk@iname.com>
To: "'Keith Moore'" <moore@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net> <52599079-C6E9-48F9-AFAE-78E7989FB105@network-heretics.com>
In-Reply-To: <52599079-C6E9-48F9-AFAE-78E7989FB105@network-heretics.com>
Subject: RE: [v6ops] 6to4v2 (as in ripv2)?
Date: Sun, 7 Aug 2011 23:22:29 -0500
Message-ID: <009e01cc5582$d51bcc60$7f536520$@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcxMiriIWmxxIR09QDaIGoHS//aBGAIfH75Q
Content-Language: en-us
X-Authenticated-User: fbulk@premieronline.net 
X-SpamDetect: : 0.000000 
X-Info: aspam skipped due to (g_smite_skip_auth)
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=0 Stars=0 Good=3 Friend=408 Surbl=0 Catch=0 r=0 ip=199.120.69.26
X-IP-stats: Incoming Outgoing Last 0, First 883, in=13688188, out=64386, spam=0 Known=true ip=199.120.69.26
X-Mailman-Approved-At: Mon, 08 Aug 2011 07:44:15 -0700
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org, Philip Homburg <pch-v6ops@u-1.phicoh.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: frnkblk@iname.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 04:22:33 -0000

Hmmm...it's been well documented that 6to4 causes bad experiences, not
decreases the chance of having them.  Since much of the IPv6-accssible
content is dual-stacked, unless you're using an application that implements
HE, the odds are in your favor to use IPv4 rather than IPv4+6to4.

Frank

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
Keith Moore
Sent: Wednesday, July 27, 2011 1:25 PM
To: Philip Homburg
Cc: IPv6 Operations; Keith Moore; ietf@ietf.org
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?

On Jul 27, 2011, at 4:32 AM, Philip Homburg wrote:

> In your letter dated Wed, 27 Jul 2011 12:38:33 +1000 you wrote:
>> In message <4E2F4491.30102@gmail.com>, Brian E Carpenter writes:
>>> Of course, if implementors choose to drop the code you might not be
>>> able to upgrade software versions - but hopefully by that time you
>>> will have native IPv6 service anyway.
>> 
>> Which is exactly why HISTORIC is NOT appropriate. 
> 
> With rfc3484-revise and the documented brokenness of 6to4, it doesn't make
> any sense for implementors to offer 6to4 anyhow.

False.  It makes even more sense to offer 6to4 because it significantly
decreases the chance that it will cause a bad experience for users of
services that provide both v4 and v6 addresses, while increasing the chance
letting local hosts/users talk to v6-only services/hosts.

<snip>

Keith

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


From joelja@bogus.com  Mon Aug  8 07:48:45 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8B1F21F8AFE for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:48:45 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G+sh3v-UmtZg for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:48:45 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5352421F855A for <ietf@ietf.org>; Mon,  8 Aug 2011 07:48:45 -0700 (PDT)
Received: from [192.168.1.171] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p78Emvcv024932 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 8 Aug 2011 14:48:57 GMT (envelope-from joelja@bogus.com)
Subject: Re: Queen Sirikit National Convention Center
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <1D5C586851E84A87B99E6E0A@PST.JCK.COM>
Date: Mon, 8 Aug 2011 07:48:56 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <D33EE792-B42A-411D-B919-F8110A69D455@bogus.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com> <1D5C586851E84A87B99E6E0A@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 08 Aug 2011 14:48:58 +0000 (UTC)
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 14:48:45 -0000

On Aug 8, 2011, at 7:43 AM, John C Klensin wrote:

> 
> 
> --On Monday, August 08, 2011 16:56 +0300 Yoav Nir
> <ynir@checkpoint.com> wrote:
> 
>>> (34 in April, 31 in December, lowest nightime temp 21 in
>>> December and 27 in April-May-June).
>> 
>> Pretty much like Tel Aviv in August.
>> 
>> Tucson or Phoenix have much higher temperatures, but what it
>> lacks in raw degrees, Bangkok makes up for with suffocating
>> humidity.
>> 
>> I don't think there's an amount of air conditioning that would
>> make me complain in Bangkok.
> 
> I've been in meetings in Bangkok and been cold in the meeting
> rooms.  Of course, tastes differ... but I grew up in Tucson and
> rather liked the summers especially as long as relative humidity
> stayed in single digits. :-)
> 
> Of course, given some of the other suggestions made recently, we
> probably should also be considering Tel Aviv as a meeting site
> -- from what I understand, non-trivial numbers of IETF
> participants (unlike some places discussed recently), plausible
> hotel costs, decent airport and international connections, good
> in-country Internet infrastructure.  Might be plausible for a
> late fall or early spring meeting if there are adequate meeting
> facilities... I take the above to be a hint that August should
> be avoided.

Wanna have the visa-issue like in the US?

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


From moore@network-heretics.com  Mon Aug  8 07:54:59 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA4121F8B31 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.125
X-Spam-Level: 
X-Spam-Status: No, score=-4.125 tagged_above=-999 required=5 tests=[AWL=0.874,  BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RyXaRoPX22gM for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:54:58 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 7737521F8B22 for <ietf@ietf.org>; Mon,  8 Aug 2011 07:54:58 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 23D5B20B66; Mon,  8 Aug 2011 10:55:24 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 08 Aug 2011 10:55:24 -0400
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=/5oxYVqQFzN4eG8xUv+3DbKhG6k=; b=J2 fdFfgU0sBnORG9pTadTqQjw2+BAVmm9Q8UV/axWWkmkyWp7b4YHhM5hNXmfZ8CNo Fu2G0t4UJuYIT4W05tew0VR2mBgK0rq2wiytL/v5OW0BjCAWbr7ihRTNPtobpFzh 7YTNOfJK1ytbzpzrRucWdhrRX/pCPMyBXf1HFC4qA=
X-Sasl-enc: Xmxa5/VqrVp/gkrP5tJUMeFhpKWeWIuM7me2Sg0uBZRA 1312815323
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 3412E457405; Mon,  8 Aug 2011 10:55:23 -0400 (EDT)
Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <009e01cc5582$d51bcc60$7f536520$@iname.com>
Date: Mon, 8 Aug 2011 10:55:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C9A978E-0672-44CC-B7F2-82E0439FFB49@network-heretics.com>
References: <13205C286662DE4387D9AF3AC30EF456D3F431D11F@EMBX01-WF.jnpr.net>	<4E2DE4EC.1030109@gmail.com> <4E2E2FBA.1030304@gmail.com>	<13205C286662DE4387D9AF3AC30EF456D3F44833C5@EMBX01-WF.jnpr.net>	<4E2EDF23.3060804@gmail.com> <4E2F4491.30102@gmail.com>	<20110727023833.5C72D1232958@drugs.dv.isc.org>	<m1QlzXt-0001gSC@stereo.hq.phicoh.net> <52599079-C6E9-48F9-AFAE-78E7989FB105@network-heretics.com> <009e01cc5582$d51bcc60$7f536520$@iname.com>
To: frnkblk@iname.com
X-Mailer: Apple Mail (2.1084)
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 14:54:59 -0000

To clarify, what I meant here is that with 3484-revise address selection =
rules in place, 6to4 is an overall benefit.  6to4 provides a means of =
accessing v6-only hosts and services when no other means is available.   =
And though one might argue that there are too few v6-only hosts and =
services to matter, that's a temporary situation.

Keith

On Aug 8, 2011, at 12:22 AM, Frank Bulk wrote:

> Hmmm...it's been well documented that 6to4 causes bad experiences, not
> decreases the chance of having them.  Since much of the IPv6-accssible
> content is dual-stacked, unless you're using an application that =
implements
> HE, the odds are in your favor to use IPv4 rather than IPv4+6to4.
>=20
> Frank
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of
> Keith Moore
> Sent: Wednesday, July 27, 2011 1:25 PM
> To: Philip Homburg
> Cc: IPv6 Operations; Keith Moore; ietf@ietf.org
> Subject: Re: [v6ops] 6to4v2 (as in ripv2)?
>=20
> On Jul 27, 2011, at 4:32 AM, Philip Homburg wrote:
>=20
>> In your letter dated Wed, 27 Jul 2011 12:38:33 +1000 you wrote:
>>> In message <4E2F4491.30102@gmail.com>, Brian E Carpenter writes:
>>>> Of course, if implementors choose to drop the code you might not be
>>>> able to upgrade software versions - but hopefully by that time you
>>>> will have native IPv6 service anyway.
>>>=20
>>> Which is exactly why HISTORIC is NOT appropriate.=20
>>=20
>> With rfc3484-revise and the documented brokenness of 6to4, it doesn't =
make
>> any sense for implementors to offer 6to4 anyhow.
>=20
> False.  It makes even more sense to offer 6to4 because it =
significantly
> decreases the chance that it will cause a bad experience for users of
> services that provide both v4 and v6 addresses, while increasing the =
chance
> letting local hosts/users talk to v6-only services/hosts.
>=20
> <snip>
>=20
> Keith
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From john-ietf@jck.com  Mon Aug  8 07:56:10 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67FF21F8B45 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TXJrzumZqYm for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 07:56:10 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 3F97821F8B22 for <ietf@ietf.org>; Mon,  8 Aug 2011 07:56:10 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QqRFm-000MK9-MY; Mon, 08 Aug 2011 10:56:30 -0400
Date: Mon, 08 Aug 2011 10:56:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Queen Sirikit National Convention Center
Message-ID: <AB06F33E67B2E07CF6CA8B44@PST.JCK.COM>
In-Reply-To: <D33EE792-B42A-411D-B919-F8110A69D455@bogus.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com> <1D5C586851E84A87B99E6E0A@PST.JCK.COM> <D33EE792-B42A-411D-B919-F8110A69D455@bogus.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: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 14:56:11 -0000

--On Monday, August 08, 2011 07:48 -0700 Joel Jaeggli
<joelja@bogus.com> wrote:

>...
>> Of course, given some of the other suggestions made recently,
>> we probably should also be considering Tel Aviv as a meeting
>> site -- from what I understand, non-trivial numbers of IETF
>> participants (unlike some places discussed recently),
>> plausible hotel costs, decent airport and international
>> connections, good in-country Internet infrastructure.  Might
>> be plausible for a late fall or early spring meeting if there
>> are adequate meeting facilities... I take the above to be a
>> hint that August should be avoided.
> 
> Wanna have the visa-issue like in the US?

I'm aware of the problem.  I'm also aware that we keep holding
meetings in the US and that some participants didn't find Canada
a whole lot better this time around.   And I'm also aware that
Israeli passport holders have absolutely no chance of getting
visas for some of the locations that have been discussed
recently, no matter how much they participate in the IETF or how
long in advance they apply.  So I'd personally think that issue
should be in the "tradeoff" category, rather than the
"showstopper" one.

   john



From joelja@bogus.com  Mon Aug  8 09:09:04 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA61521F86AD for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 09:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hOk0yS+YzjUb for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 09:09:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 644F821F86AB for <ietf@ietf.org>; Mon,  8 Aug 2011 09:09:04 -0700 (PDT)
Received: from [10.101.144.59] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p78G9K7V029289 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 8 Aug 2011 16:09:20 GMT (envelope-from joelja@bogus.com)
Subject: Re: Queen Sirikit National Convention Center
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <AB06F33E67B2E07CF6CA8B44@PST.JCK.COM>
Date: Mon, 8 Aug 2011 09:09:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <584EC2B1-9E8C-44B5-AB68-04855CD0B3CE@bogus.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com> <1D5C586851E84A87B99E6E0A@PST.JCK.COM> <D33EE792-B42A-411D-B919-F8110A69D455@bogus.com> <AB06F33E67B2E07CF6CA8B44@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 08 Aug 2011 16:09:22 +0000 (UTC)
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 16:09:04 -0000

On Aug 8, 2011, at 7:56 AM, John C Klensin wrote:
>>=20
>> Wanna have the visa-issue like in the US?
>=20
> I'm aware of the problem.  I'm also aware that we keep holding
> meetings in the US and that some participants didn't find Canada
> a whole lot better this time around.   And I'm also aware that
> Israeli passport holders have absolutely no chance of getting
> visas for some of the locations that have been discussed
> recently, no matter how much they participate in the IETF or how
> long in advance they apply.  So I'd personally think that issue
> should be in the "tradeoff" category, rather than the
> "showstopper" one.

Having worked for a company with it's headquarters in Ramat Gan and it's =
manufacturing in Penang I prefer to not make my or someone else's =
travels more complex than strictly necessary.=

From john-ietf@jck.com  Mon Aug  8 10:35:14 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D299D21F8B52 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 10:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Owax0kliW5q for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 10:35:13 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id A652421F8B09 for <ietf@ietf.org>; Mon,  8 Aug 2011 10:35:13 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QqTji-000PPe-Fq; Mon, 08 Aug 2011 13:35:34 -0400
Date: Mon, 08 Aug 2011 13:35:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Queen Sirikit National Convention Center
Message-ID: <5257F0B5E369B4773FCE170F@PST.JCK.COM>
In-Reply-To: <584EC2B1-9E8C-44B5-AB68-04855CD0B3CE@bogus.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com> <1D5C586851E84A87B99E6E0A@PST.JCK.COM> <D33EE792-B42A-411D-B919-F8110A69D455@bogus.com> <AB06F33E67B2E07CF6CA8B44@PST.JCK.COM> <584EC2B1-9E8C-44B5-AB68-04855CD0B3CE@bogus.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: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 17:35:14 -0000

--On Monday, August 08, 2011 09:09 -0700 Joel Jaeggli
<joelja@bogus.com> wrote:

>> I'm aware of the problem.  I'm also aware that we keep holding
>> meetings in the US and that some participants didn't find
>> Canada a whole lot better this time around.   And I'm also
>> aware that Israeli passport holders have absolutely no chance
>> of getting visas for some of the locations that have been
>> discussed recently, no matter how much they participate in
>> the IETF or how long in advance they apply.  So I'd
>> personally think that issue should be in the "tradeoff"
>> category, rather than the "showstopper" one.
> 
> Having worked for a company with it's headquarters in Ramat
> Gan and it's manufacturing in Penang I prefer to not make my
> or someone else's travels more complex than strictly necessary.

Sounds like a worthwhile goal.  Did you have a collection of
places in mind that have the necessary infrastructure for an
IETF meeting, convenient travel connections (however you define
that), a plausible cost structure (ditto), and no visa issues
for anyone who might reasonably choose to participate in the
IETF?  Ideally, add "good sponsorship opportunities and likely
sponsors" to those qualifications.  Unless that yields a list of
at least moderate length, I repeat my comment about tradeoffs.

    john


From moore@network-heretics.com  Mon Aug  8 11:04:59 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE5AD21F8B6A for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 11:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level: 
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fk+mrmWhHfxR for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 11:04:59 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id F36AD21F8AD8 for <ietf@ietf.org>; Mon,  8 Aug 2011 11:04:58 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 6DF4F20B76; Mon,  8 Aug 2011 14:05:25 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Mon, 08 Aug 2011 14:05:25 -0400
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=Uv7IDJuj0FUb1SNJow9nfDGBFsk=; b=PR yQAq7eIRgEGoxp0Qsmu2VysLuQmPrwGcuHuIz5xMQnJFjNDSvnb2fkcWIWW25uiE eKeGaR5wFpa0qYsnwGUwSDqbzgsMFWAFdnojmQ8h+mkYN4kN6gHBAcwy1ZUI/Oka hcpWypyko+1QHyX09RPfaWsKh50+ejMyox7EWog84=
X-Sasl-enc: 8bvI45w8fsqIHDhjknZxujw6cCisWNubEbRXgIY+/PgO 1312826724
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F63245B2AB; Mon,  8 Aug 2011 14:05:24 -0400 (EDT)
Subject: Re: I-D Working groups and mailing list
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF5F9@EXCH-C2.corp.cloudmark.com>
Date: Mon, 8 Aug 2011 14:05:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <85179AA5-0964-4013-A9EF-117CAD22EAD4@network-heretics.com>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com>	<4E3A5A1E.8050002@gmx.de> , <EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com> <4E3AB2B8.6080501@dcrocker.net> <4E3AB642.3070208@isdg.net> <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com> <68496DEA09A833357F1852EC@[192.168.1.128]> <F5833273385BB34F99288B3648C4F06F13512DF5F9@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 18:04:59 -0000

On Aug 8, 2011, at 1:28 PM, Murray S. Kucherawy wrote:

>> -----Original Message-----
>> From: John C Klensin [mailto:john-ietf@jck.com]
>> Sent: Sunday, August 07, 2011 9:19 AM
>> To: Murray S. Kucherawy; ietf@ietf.org
>> Subject: RE: I-D Working groups and mailing list
>>=20
>> (4) Others (probably a partially overlapping group with (3))
>> just find more rules and requirements for more boilerplate
>> undesirable.  They would (at least mostly) be happy if lots of
>> off-list notes went to authors of I-Ds for which the discussion
>> forum wasn't clear, asking them about the discussion forum and
>> recommending that it be included in the next draft.   That might
>> actually encourage discussion and would be as, or more,
>> effective at retraining authors than more rules.
>=20
> This is my preference.  If the author(s) don't include a "discuss this =
here" section, then they're inviting direct comments, and maybe that's =
what they prefer.  If not, they will quickly learn to either find or =
create a forum, even if that's just ietf@ietf.org, and mention such in =
the draft.

+1

Keith


From joelja@bogus.com  Mon Aug  8 11:07:44 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C78321F8B56 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 11:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 539m8KzzX-zo for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 11:07:43 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 88EAA21F8B67 for <ietf@ietf.org>; Mon,  8 Aug 2011 11:07:43 -0700 (PDT)
Received: from [10.101.144.59] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p78I81S3035721 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 8 Aug 2011 18:08:02 GMT (envelope-from joelja@bogus.com)
Subject: Re: Queen Sirikit National Convention Center
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <5257F0B5E369B4773FCE170F@PST.JCK.COM>
Date: Mon, 8 Aug 2011 11:07:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1EF20AC6-00D3-4C01-A10D-483AB3AC7DC1@bogus.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com> <1D5C586851E84A87B99E6E0A@PST.JCK.COM> <D33EE792-B42A-411D-B919-F8110A69D455@bogus.com> <AB06F33E67B2E07CF6CA8B44@PST.JCK.COM> <584EC2B1-9E8C-44B5-AB68-04855CD0B3CE@bogus.com> <5257F0B5E369B4773FCE170F@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 08 Aug 2011 18:08:02 +0000 (UTC)
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 18:07:44 -0000

On Aug 8, 2011, at 10:35 AM, John C Klensin wrote:

>=20
>=20
> --On Monday, August 08, 2011 09:09 -0700 Joel Jaeggli
> <joelja@bogus.com> wrote:
>=20
>>> I'm aware of the problem.  I'm also aware that we keep holding
>>> meetings in the US and that some participants didn't find
>>> Canada a whole lot better this time around.   And I'm also
>>> aware that Israeli passport holders have absolutely no chance
>>> of getting visas for some of the locations that have been
>>> discussed recently, no matter how much they participate in
>>> the IETF or how long in advance they apply.  So I'd
>>> personally think that issue should be in the "tradeoff"
>>> category, rather than the "showstopper" one.
>>=20
>> Having worked for a company with it's headquarters in Ramat
>> Gan and it's manufacturing in Penang I prefer to not make my
>> or someone else's travels more complex than strictly necessary.
>=20
> Sounds like a worthwhile goal.  Did you have a collection of
> places in mind that have the necessary infrastructure for an
> IETF meeting, convenient travel connections (however you define
> that), a plausible cost structure (ditto).

My employeers have hosted two ietf meetings, QED.

> and no visa issues
> for anyone who might reasonably choose to participate in the
> IETF?

We've heard from the community where minimizing our exposure to visa is =
should be in our list of priorities. I know of no previous location, =
where I involved in the meeting planning where there were no visa issue.

>  Ideally, add "good sponsorship opportunities and likely
> sponsors" to those qualifications.  Unless that yields a list of
> at least moderate length, I repeat my comment about tradeoffs.
>=20
>    john
>=20


From john-ietf@jck.com  Mon Aug  8 11:28:15 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A841921F8B61 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 11:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2gC+fCfkD2o for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 11:28:15 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id C24BA21F8B2F for <ietf@ietf.org>; Mon,  8 Aug 2011 11:28:14 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QqUZ1-0000fM-G2; Mon, 08 Aug 2011 14:28:35 -0400
Date: Mon, 08 Aug 2011 14:28:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Queen Sirikit National Convention Center
Message-ID: <D4B47756367AB7D21DDE2123@PST.JCK.COM>
In-Reply-To: <1EF20AC6-00D3-4C01-A10D-483AB3AC7DC1@bogus.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com> <1D5C586851E84A87B99E6E0A@PST.JCK.COM> <D33EE792-B42A-411D-B919-F8110A69D455@bogus.com> <AB06F33E67B2E07CF6CA8B44@PST.JCK.COM> <584EC2B1-9E8C-44B5-AB68-04855CD0B3CE@bogus.com> <5257F0B5E369B4773FCE170F@PST.JCK.COM> <1EF20AC6-00D3-4C01-A10D-483AB3AC7DC1@bogus.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: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 18:28:15 -0000

--On Monday, August 08, 2011 11:07 -0700 Joel Jaeggli
<joelja@bogus.com> wrote:

> We've heard from the community where minimizing our exposure
> to visa is should be in our list of priorities. I know of no
> previous location, where I involved in the meeting planning
> where there were no visa issue.

Joel,

That is exactly my point.  There is probably no where in the
world that is completely free of visa issues for everyone.  So
the IAOC tries to minimize visa aggravation or spread the
aggravation around, weighing the visa issues against others.   I
think they do a moderately good job of it; others might give
them either higher or lower scores.

I think, if possible, we should strive to not have serious visa
aggravation for the same group of people two meetings in a row.
But, because "no visa aggravation, problems, or high fees for
anyone" is going to be rare or impossible, the visa issues with
any given location are just another tradeoff unless the rules
are so severe in practice that almost no one can get it.

I'm willing (indeed happy) to have IAOC sort out those tradeoffs
even though I would prefer that they be a tad more open with the
community about the decisions they are making and why.

   john


From rbonica@juniper.net  Mon Aug  8 11:36:50 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78BF721F8BB1; Mon,  8 Aug 2011 11:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.538
X-Spam-Level: 
X-Spam-Status: No, score=-106.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vFYzqTWNl8R; Mon,  8 Aug 2011 11:36:50 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 97DD421F8BA2; Mon,  8 Aug 2011 11:36:49 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTkAs3OCtvcEJfEGRBcHNgvn823Po1nTK@postini.com; Mon, 08 Aug 2011 11:37:16 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 8 Aug 2011 10:49:07 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Mon, 8 Aug 2011 13:49:06 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Date: Mon, 8 Aug 2011 13:49:05 -0400
Subject: RE: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Topic: draft-ietf-v6ops-6to4-to-historic  (yet again)
Thread-Index: AcxK13EXQuzfLCzMQFivvvTkow95TgLG9cng
Message-ID: <13205C286662DE4387D9AF3AC30EF456D43CF6CECA@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 18:36:50 -0000

Folks,

After an active discussion, it is clear that there is no consensus. So, I w=
ill transition draft-ietf-v6ops-6to4-to-historic to the DEAD state.

                                                    Ron


> -----Original Message-----
> From: Ronald Bonica
> Sent: Monday, July 25, 2011 10:31 AM
> To: ietf@ietf.org
> Subject: draft-ietf-v6ops-6to4-to-historic (yet again)
>=20
> Folks,
>=20
> After some discussion, the IESG is attempting to determine whether
> there is IETF consensus to do the following:
>=20
> - add a new section to draft-ietf-v6ops-6to4-to-historic
> - publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
>=20
> draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and
> convert their status to HISTORIC. It will also contain a new section
> describing what it means for RFCs 3056 and 3068 to be classified as
> HISTORIC. The new section will say that:
>=20
> - 6-to-4 should not be configured by default on any implementation
> (hosts, cpe routers, other)
> - vendors will decide whether/when 6-to-4 will be removed from
> implementations. Likewise, operators will decide whether/when 6-to-4
> relays will be removed from their networks. The status of RFCs 3056 and
> 3068 should not be interpreted as a recommendation to remove 6-to-4 at
> any particular time.
>=20
>=20
> draft-ietf-v6ops-6to4-to-historic will not update RFC 2026. While it
> clarifies the meaning of "HISTORIC" in this particular case, it does
> not set a precedent for any future case.
>=20
> Please post your views on this course of action by August 8, 2011.
>=20
>=20
>                                                                    Ron
> Bonica
>=20
> <speaking as OPS Area AD>

From ned+ietf@mauve.mrochek.com  Mon Aug  8 13:43:20 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51CB311E8097 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 13:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vouQXDIREynJ for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 13:43:19 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2977011E8092 for <ietf@ietf.org>; Mon,  8 Aug 2011 13:43:19 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4LYDFUYOW010IHX@mauve.mrochek.com> for ietf@ietf.org; Mon, 8 Aug 2011 13:42:45 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 8 Aug 2011 13:42:40 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4LYDD0O3C00VHKR@mauve.mrochek.com>
Date: Mon, 08 Aug 2011 13:34:27 -0700 (PDT)
Subject: RE: I-D Working groups and mailing list
In-reply-to: "Your message dated Mon, 08 Aug 2011 10:28:18 -0700" <F5833273385BB34F99288B3648C4F06F13512DF5F9@EXCH-C2.corp.cloudmark.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de> <EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com> <4E3AB2B8.6080501@dcrocker.net> <4E3AB642.3070208@isdg.net> <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com> <68496DEA09A833357F1852EC@[192.168.1.128]> <F5833273385BB34F99288B3648C4F06F13512DF5F9@EXCH-C2.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1312836086; i=@mrochek.com; bh=x05UpCW4VXX0Zq97MJoyN3aGz2yLHnbc3LM8SB2o360=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=eRW8Cwa6B9Zgvmyli1h6TxDNcXjt0n4r+omMpfb5M03dmU9dy3uN3dzZNqZO33wOi vCGEAy7zS5gnVMdTNHolQAt6h5VuKJXaBtd7H7daAkvRC5JOOi8gmxFlSvpte5Dlq7 7QFOXjbtCPCeCstODtJjLObEAyYVHUxp+a/oqhi8=
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 20:43:20 -0000

> > -----Original Message-----
> > From: John C Klensin [mailto:john-ietf@jck.com]
> > Sent: Sunday, August 07, 2011 9:19 AM
> > To: Murray S. Kucherawy; ietf@ietf.org
> > Subject: RE: I-D Working groups and mailing list
> >
> > (4) Others (probably a partially overlapping group with (3))
> > just find more rules and requirements for more boilerplate
> > undesirable.  They would (at least mostly) be happy if lots of
> > off-list notes went to authors of I-Ds for which the discussion
> > forum wasn't clear, asking them about the discussion forum and
> > recommending that it be included in the next draft.

But flip it around and see what you get: Why should I, as a document author who
wants to notify people where the discussion of the draft should take place, be
forced to use either an ad-hoc location in the document or have to send out a
bunch of additional emails? Why can't there be an *OPTIONAL* well known
location in our draft format (and corresponding XML element(s)) that automated
tools can pick up on so at a minimum this information can go out as part of the
new draft notifications?

In other words, the issue of whether or not there's a well defined way  to
incorporate this information is almost entirely orthogonal to whether or not we
require it's presence.

> > That might
> > actually encourage discussion and would be as, or more,
> > effective at retraining authors than more rules.

> This is my preference.  If the author(s) don't include a "discuss this here"
> section, then they're inviting direct comments, and maybe that's what they
> prefer.

In that case the author can simply list their own address as the discussion
contact point. Why should have dig through an entire document looking for this
information or check my email for a separate message about it?

> If not, they will quickly learn to either find or create a forum, even if
> that's just ietf@ietf.org, and mention such in the draft.

> If it ain't broke, don't fix it.

But what we have now *is* broken, or at least fairly suboptimal.

				Ned

From tglassey@earthlink.net  Mon Aug  8 13:57:37 2011
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340CA11E80AE; Mon,  8 Aug 2011 13:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.57
X-Spam-Level: 
X-Spam-Status: No, score=-1.57 tagged_above=-999 required=5 tests=[AWL=-2.456,  BAYES_50=0.001, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZG+94lkYKFX; Mon,  8 Aug 2011 13:57:34 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 2087D11E80AD; Mon,  8 Aug 2011 13:57:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=KlqZOegCJPBcJAaBz9eHzN+3eyb8LK9RHAl+adagTmJUUEYx2S2/29uP7mDOXoQI; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [207.111.209.5] (helo=[192.168.1.100]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1QqWtX-0007Ou-DZ; Mon, 08 Aug 2011 16:57:55 -0400
Message-ID: <4E404DEF.1090207@earthlink.net>
Date: Mon, 08 Aug 2011 13:58:23 -0700
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: chair@IETF.org, ietf@ietf.org
Subject: You need to be aware that US Patent Laws have evolved and intentionally violating them is actionable no matter what the IETF tells you...
Content-Type: multipart/alternative; boundary="------------030407020907050105030506"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7972bd37f67fd7532396e3c4a3c42d2f6c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.111.209.5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 20:57:37 -0000

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

That means the IETF and the Chair's role itself can be sued for this. I 
suggest you folks investigate this and rethink the IPR rules because 
this makes ISOC criminally liable for this action as a RICO claim one 
would think.

Folks- there is a fundamental legal breakdown with two key issues - the 
first is PATENTS and the IETF's Liability and the other is the abuse of 
the RESEARCH EXEMPTION which will not apply to anyone outside of the 
IETF workflow republishing anything from these mailing lists.

How this all boils down is that we have been lied to by many here who 
apparently want us to be legally accountable for patent and copyright 
damages - or they want to destroy those global IP protection schemes 
generally in what I call the "The world owns it because I wont pay for 
the fact I stole it" mindset.

The legal precedents are simple and show how incompetent the IPR WG has 
been in designing practices which intentionally break the law this 
content from the Ninth Circuit District Court's Jury Instructions book 
is excerpted.  This then, if there is a liability,  is most likely what 
your sponsors are in fact liable for.
---

    In the area of patent and copyright infringement, there is some
    authority for submitting the issue of willfulness to the jury. /See,
    e.g., Shiley, Inc. v. Bentley Lab./, 794 F.2d 1561, 1568 (Fed.
    Cir.1986) (applying 35 U.S.C. § 284), /cert. denied/, 479 U.S. 1087
    (1987).

    "Willful infringement carries a connotation of deliberate intent to
    deceive. Courts generally apply forceful labels such as
    'deliberate,' 'false,' 'misleading,' or 'fraudulent' to conduct that
    meets this standard." /Lindy Pen Co. v. Bic Pen Corp/., 982 F.2d
    1400, 1406 (9th Cir.1993) (also citing cases in other circuits
    regarding elements of a willfulness claim). /See also Committee for
    Idaho's High Desert, Inc/.,/v. Yost/, 92 F.3d 814, 825 (9th
    Cir.1996) (the term "exceptional" in 15 U.S.C. § 1117(a) for
    purposes of imposing treble damages, generally means the
    infringement was "malicious, fraudulent, deliberate or willful")
    (citing /Lindy Pen Co./, 928 F.2d at 1408);/Nintendo of America,
    Inc. v. Dragon Pacific Int'l/, 40 F.3d 1007, 1010 (9th Cir.1994)
    (where defendant willfully infringes trademark, trebling the damages
    is appropriate);/VMG Enters. v. F. Quesada & Franco, Inc/., 788 F.
    Supp. 648, 662 (D. Puerto Rico 1992) (treble damages granted when
    defendant's infringing actions are deemed to have been made
    "knowingly and willfully");/Polo Fashions v. Rabanne/, 661 F. Supp.
    89, 98 (S.D. Fla.1986) (in absence of extenuating circumstances,
    profits are to be trebled where counterfeiting is intentional and
    knowing).

    Regarding willful blindness, /see//Hard Rock Café Licensing Corp. v.
    Concession Servs/., 955 F.2d 1143, 1149 (7th Cir.1992) (to be
    willfully blind, a person must suspect wrongdoing and deliberately
    fail to investigate); /Chanel, Inc. v. Italian Activewear of
    Florida/, 931 F.2d 1472, 1476 (11th Cir.1991) (willful blindness
    could provide requisite intent or bad faith; determination of
    willful blindness depends on the circumstances and will generally be
    a question of fact for the factfinder after trial).

    A court may enter judgment for a damage award under 15 U.S.C. §
    1117(a) upon a finding of willfulness as well. /See Sealy, Inc. v.
    Easy Living, Inc./, 743 F.2d 1378, 1384 (9th Cir.1984) (district
    court found that conduct constituted willful and deliberate bad
    faith infringement of plaintiff's trademarks that was intended to
    and in fact did result in deception of the public); /Friend v. H.A.
    Friend & Co./, 416 F.2d 526, 534 (9th Cir.1969) (defendant's acts
    must be willful and calculated to trade upon the plaintiff's
    goodwill). /See also Horphag Research Ltd. v. Pellegrini/, 337 F.3d
    1036, 1042 (9th Cir.2003) ("Exceptional cases include cases in which
    the infringement is malicious, fraudulent, deliberate, or willful)
    and/Gracie v. Gracie/, 217 F.3d 1060, 1068 (9th Cir.2000).

---

What this finally reduces to is that we need a NEW PATENT AND IP POLICY 
and since all specific IETF Standards efforts come with code to 
implement and allow testing of the protocol in question, it is in fact a 
direct infringement. While the IETF is protected from these issues in 
publishing the documents - its members are not. And the IETF's copyright 
exemptions under section 107 clearly do not apply to parties publishing 
that information as part of their commercial offerings years later after 
all of that research is completed...

Sorry but reality is what it is.

Todd Glassey

-- 
Todd S. Glassey
This is from my personal email account and any materials from this account come with personal disclaimers.

Further I OPT OUT of any and all commercial emailings.


--------------030407020907050105030506
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 http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    That means the IETF and the Chair's role itself can be sued for
    this. I suggest you folks investigate this and rethink the IPR rules
    because this makes ISOC criminally liable for this action as a RICO
    claim one would think.<br>
    <br>
    Folks- there is a fundamental legal breakdown with two key issues -
    the first is PATENTS and the IETF's Liability and the other is the
    abuse of the RESEARCH EXEMPTION which will not apply to anyone
    outside of the IETF workflow republishing anything from these
    mailing lists.<br>
    <br>
    How this all boils down is that we have been lied to by many here
    who apparently want us to be legally accountable for patent and
    copyright damages - or they want to destroy those global IP
    protection schemes generally in what I call the "The world owns it
    because I wont pay for the fact I stole it" mindset.<br>
    <br>
    The legal precedents are simple and show how incompetent the IPR WG
    has been in designing practices which intentionally break the law
    this content from the Ninth Circuit District Court's Jury
    Instructions book is excerpted.&nbsp; This then, if there is a
    liability,&nbsp; is most likely what your sponsors are in fact liable
    for. <br>
    ---<br>
    <blockquote><font face="KZWRL L+ Times New"> In the area of patent
        and copyright infringement, there is some authority for
        submitting the issue of willfulness to the jury. </font><i><font
          face="FWIUO H+ Times New Roman,">See, e.g., Shiley, Inc. v.
          Bentley Lab.</font></i><font face="KZWRL L+ Times New">, 794
        F.2d 1561, 1568 (Fed. Cir.1986) (applying 35 U.S.C. &sect; 284), </font><i><font
          face="FWIUO H+ Times New Roman,">cert. denied</font></i><font
        face="KZWRL L+ Times New">, 479 U.S. 1087 (1987).</font><br>
      <font face="KZWRL L+ Times New"> </font><br>
      <font face="KZWRL L+ Times New"> &#8220;Willful infringement carries a
        connotation of deliberate intent to deceive. Courts generally
        apply forceful labels such as &#8216;deliberate,&#8217; &#8216;false,&#8217;
        &#8216;misleading,&#8217; or &#8216;fraudulent&#8217; to conduct that meets this
        standard.&#8221; </font><i><font face="FWIUO H+ Times New Roman,">
          Lindy Pen Co. v. Bic Pen Corp</font></i><font face="KZWRL L+
        Times New">., 982 F.2d 1400, 1406 (9th Cir.1993) (also citing
        cases in other circuits regarding elements of a willfulness
        claim). </font><i><font face="FWIUO H+ Times New Roman,">See
          also Committee for Idaho&#8217;s High Desert, Inc</font></i><font
        face="KZWRL L+ Times New">.,</font><i><font face="FWIUO H+ Times
          New Roman,"> v. Yost</font></i><font face="KZWRL L+ Times New">,
        92 F.3d 814, 825 (9th Cir.1996) (the term &#8220;exceptional&#8221; in 15
        U.S.C. &sect; 1117(a) for purposes of imposing treble damages,
        generally means the infringement was &#8220;malicious, fraudulent,
        deliberate or willful&#8221;) (citing </font><i><font face="FWIUO H+
          Times New Roman,">Lindy Pen Co.</font></i><font face="KZWRL L+
        Times New">, 928 F.2d at 1408);</font><i><font face="FWIUO H+
          Times New Roman,"> Nintendo of America, Inc. v. Dragon Pacific
          Int&#8217;l</font></i><font face="KZWRL L+ Times New">, 40 F.3d
        1007, 1010 (9th Cir.1994) (where defendant willfully infringes
        trademark, trebling the damages is appropriate);</font><i><font
          face="FWIUO H+ Times New Roman,">VMG Enters. v. F. Quesada
          &amp; Franco, Inc</font></i><font face="KZWRL L+ Times New">.,
        788 F. Supp. 648, 662 (D. Puerto Rico 1992) (treble damages
        granted when defendant&#8217;s infringing actions are deemed to have
        been made &#8220;knowingly and willfully&#8221;);</font><i><font face="FWIUO
          H+ Times New Roman,"> Polo Fashions v. Rabanne</font></i><font
        face="KZWRL L+ Times New">, 661 F. Supp. 89, 98 (S.D. Fla.1986)
        (in absence of extenuating circumstances, profits are to be
        trebled where counterfeiting is intentional and knowing). </font><br>
      <br>
      <font face="KZWRL L+ Times New"> Regarding willful blindness, </font><i><font
          face="KZWRL L+ Times New">see</font></i><i><font face="FWIUO
          H+ Times New Roman,"> Hard Rock Caf&eacute; Licensing Corp. v.
          Concession Servs</font></i><font face="KZWRL L+ Times New">.,
        955 F.2d 1143, 1149 (7th Cir.1992) (to be willfully blind, a
        person must suspect wrongdoing and deliberately fail to
        investigate); </font><i><font face="FWIUO H+ Times New Roman,">Chanel,
          Inc. v. Italian Activewear of Florida</font></i><font
        face="KZWRL L+ Times New">, 931 F.2d 1472, 1476 (11th Cir.1991)
        (willful blindness could provide requisite intent or bad faith;
        determination of willful blindness depends on the circumstances
        and will generally be a question of fact for the factfinder
        after trial). </font><br>
      <br>
      <font face="KZWRL L+ Times New"> A court may enter judgment for a
        damage award under 15 U.S.C. &sect; 1117(a) upon a finding of
        willfulness as well. </font><i><font face="FWIUO H+ Times New
          Roman,">See Sealy, Inc. v. Easy Living, Inc.</font></i><font
        face="KZWRL L+ Times New">, 743 F.2d 1378, 1384 (9th Cir.1984)
        (district court found that conduct constituted willful and
        deliberate bad faith infringement of plaintiff&#8217;s trademarks that
        was intended to and in fact did result in deception of the
        public); </font><i><font face="FWIUO H+ Times New Roman,">Friend
          v. H.A. Friend &amp; Co.</font></i><font face="KZWRL L+ Times
        New">, 416 F.2d 526, 534 (9th Cir.1969) (defendant&#8217;s acts must
        be willful and calculated to trade upon the plaintiff&#8217;s
        goodwill). </font><i><font face="FWIUO H+ Times New Roman,">See
          also Horphag Research Ltd. v. Pellegrini</font></i><font
        face="KZWRL L+ Times New">, 337 F.3d 1036, 1042 (9th Cir.2003)
        (&#8220;Exceptional cases include cases in which the infringement is
        malicious, fraudulent, deliberate, or willful</font><font
        face="FWIUO H+ Times New Roman,">) and</font><font face="KZWRL
        L+ Times New"> </font><i><font face="FWIUO H+ Times New Roman,">Gracie
          v. Gracie</font></i><font face="KZWRL L+ Times New">, 217 F.3d
        1060, 1068 (9th Cir.2000).</font><br>
    </blockquote>
    ---<br>
    <br>
    What this finally reduces to is that we need a NEW PATENT AND IP
    POLICY and since all specific IETF Standards efforts come with code
    to implement and allow testing of the protocol in question, it is in
    fact a direct infringement. While the IETF is protected from these
    issues in publishing the documents - its members are not. And the
    IETF's copyright exemptions under section 107 clearly do not apply
    to parties publishing that information as part of their commercial
    offerings years later after all of that research is completed... <br>
    <br>
    Sorry but reality is what it is.<br>
    <br>
    Todd Glassey<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Todd S. Glassey
This is from my personal email account and any materials from this account come with personal disclaimers. 

Further I OPT OUT of any and all commercial emailings. 
</pre>
  </body>
</html>

--------------030407020907050105030506--

From john-ietf@jck.com  Mon Aug  8 14:08:12 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8B711E80AC for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 14:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3fGInzHy92x for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 14:08:11 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6C311E8089 for <ietf@ietf.org>; Mon,  8 Aug 2011 14:08:11 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QqX3s-0003sC-4t; Mon, 08 Aug 2011 17:08:36 -0400
Date: Mon, 08 Aug 2011 17:08:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: RE: I-D Working groups and mailing list
Message-ID: <B362153E2F6FC9F236C96BF2@PST.JCK.COM>
In-Reply-To: <01O4LYDD0O3C00VHKR@mauve.mrochek.com>
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com>	<4E3A5A1E.8050002@gmx.de> <EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com> <4E3AB2B8.6080501@dcrocker.net> <4E3AB642.3070208@isdg.net> <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com> <68496DEA09A833357F1852EC@[192.168.1.128]> <F5833273385BB34F99288B3648C4F06F13512DF5F9@EXCH-C2.corp.cloudmark.com> <01O4LYDD0O3C00VHKR@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 21:08:12 -0000

--On Monday, August 08, 2011 13:34 -0700
ned+ietf@mauve.mrochek.com wrote:

>> > -----Original Message-----
>> > From: John C Klensin [mailto:john-ietf@jck.com]
>> > Sent: Sunday, August 07, 2011 9:19 AM
>> > To: Murray S. Kucherawy; ietf@ietf.org
>> > Subject: RE: I-D Working groups and mailing list
>> > 
>> > (4) Others (probably a partially overlapping group with (3))
>> > just find more rules and requirements for more boilerplate
>> > undesirable.  They would (at least mostly) be happy if lots
>> > of off-list notes went to authors of I-Ds for which the
>> > discussion forum wasn't clear, asking them about the
>> > discussion forum and recommending that it be included in
>> > the next draft.
> 
> But flip it around and see what you get: Why should I, as a
> document author who wants to notify people where the
> discussion of the draft should take place, be forced to use
> either an ad-hoc location in the document or have to send out a
> bunch of additional emails? Why can't there be an *OPTIONAL*
> well known location in our draft format (and corresponding XML
> element(s)) that automated tools can pick up on so at a
> minimum this information can go out as part of the new draft
> notifications?
> 
> In other words, the issue of whether or not there's a well
> defined way  to incorporate this information is almost
> entirely orthogonal to whether or not we require it's presence.

Absolutely.  If whomever is maintaining the tool sets wants to
provide that as an option element (or equivalent) for whatever
source language they are supporting, I have no problem with it
at all (and would be happy to convert my ad hoc mechanisms for
supplying that information to use it as I revise documents).  We
disagree in that I don't personally think it is worth the
trouble because I think we could as easily advise people to use
either a last subsection of an Introduction section or a <note>,
but I'm not maintaining the tools and therefore don't feel
entitled to a vote.

I have only two concerns:

(1) I don't want to see this made a requirement, largely because
I think it could easily turn into a bureaucratic mess.

(2) I don't want to see it (or anything else) back us into
either a requirement that everyone use xml2rfc or a requirement
that the source for I-Ds be submitted along with the formatted
ASCII-text versions.  So, while "optional well known location in
our draft format" is fine with me, tools that are expected to
pick information up by parsing XML and reading XML elements
aren't... simply because they would require that I-Ds be
prepared in XML and that the XML be generally available at
posting time.

    john


From sm@resistor.net  Mon Aug  8 16:10:11 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA1321F8876 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 16:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZL-14FCulxVJ for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 16:10:09 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BA3921F886D for <ietf@ietf.org>; Mon,  8 Aug 2011 16:10:09 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p78NANsG015764;  Mon, 8 Aug 2011 16:10:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1312845029; bh=DPtV847oEVkhSII8AXfOu61o+n4Og2H4e6K7Iivfgu0=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=A2+c/y6oM5SjdN1GxYnPtQvhKafzDHhl9cR4IBqqd2y/1bNXqwkmc0cwH4ygzpMdM gx+CxkJU/k5DV95cgksvnqCS1llTDuKRgNvN3S6IddqGHXVHu3VIaJ+JtdVkLldKCj OnPljk3fUdfcCYMlnSATmsy90pvI1dU2YfK4gZls=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1312845029; bh=DPtV847oEVkhSII8AXfOu61o+n4Og2H4e6K7Iivfgu0=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=uU2ug4HR85p39z3arch4Jnx5bjadFmo/mVnpkwm8No6HaU1ptH9PSkQoizty1MEs3 MrX0lWdzcOb+40jr9E5SN2TKOfO7K2OWT18G1uNHnDy5w8sTHcdV5wh/AepMFPZAPC OCNteU4wKu5hGbajhCvyAXmeFO8QwNmbxMVlhRo8=
Message-Id: <6.2.5.6.2.20110808151312.0608b1b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
X-Priority: 1 (Highest)
Date: Mon, 08 Aug 2011 15:33:39 -0700
To: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
From: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-housley-two-maturity-levels-08.txt>(Reducing the Standards Track to Two Maturity Levels) to BCP
In-Reply-To: <A5AD67DA1ACB9648831FD753485B2BFE121089B6@EXVSGT02.globetel .com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <A5AD67DA1ACB9648831FD753485B2BFE121089B6@EXVSGT02.globetel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 23:10:11 -0000

Hi Medel,
At 17:57 07-08-2011, GT RAMIREZ, Medel G. wrote:
>1)Is there such thing as a "good enough" Criteria to handle this
>concern?

Glen Zorn asked a question during the last plenary and there was a 
discussion [1] about "criteria" on this mailing list.

To be fair, I'll quote a message from Warren Kumari [2]:

   "While not all ADs read all drafts, most read a large fraction
    of them (and read them carefully and thoughtfully enough to
    catch a number of large issues (and nits) *that were not caught
    in LC*) -- I think that they deserve recognition for performing
    a valuable and un-fun function..."

>2)Or as usual it passes "rough consensus" process?

The process is based on consensus and not "rough consensus".

Regards,
-sm

P.S. http://www.ietf.org/mail-archive/web/ietf/current/msg67494.html

1. http://www.ietf.org/mail-archive/web/ietf/current/msg68008.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg68008.html 


From sm@resistor.net  Mon Aug  8 16:10:11 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D95221F886D for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 16:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHGO7MBLji2X for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 16:10:09 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B93E21F886C for <ietf@ietf.org>; Mon,  8 Aug 2011 16:10:09 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p78NANsI015764;  Mon, 8 Aug 2011 16:10:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1312845034; bh=vgwPra6H1nD7b8ke1LI7oc06ENpv3minkJy5BhGegT0=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=axCAOPzCwRjDujxkGTBZs7s62MCvFagUHpXfTfi9Tsn2WianYpHDwqkC1/sC0B376 os+80rgwkz3tjGvqMWDVrN6MspwIvEsNjubYGFQzEPbBVLah0hcg0Fz5IS2OzHBNPi u7UNNFN+rPaLMgC0Pm7O5rocZmqXnyGJDOPUaYt8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1312845034; bh=vgwPra6H1nD7b8ke1LI7oc06ENpv3minkJy5BhGegT0=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=4LX3fLhPFTcReO/s/9kNY1MeNEQwBt+CIL1Y7j3NUrfqnV5bouQt15nPFgbruOEoV CDYUsDNv130v4kRwqm8tpuUJyxvgpvjPULPomnT8auLp7fmxRpk6uy2ayMJZhEL7xG ax6QHb3W8Wx0YT05MuHDlWTL0oDZVaZhkx0V3bRw=
Message-Id: <6.2.5.6.2.20110808153638.08eb9108@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 08 Aug 2011 16:06:24 -0700
To: Hector Santos <hsantos@isdg.net>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt>	(Reducing the Standards Track to Two Maturity Levels) to BCP
In-Reply-To: <4E3F3A56.806@isdg.net>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <4E3F3A56.806@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 23:10:11 -0000

Hi Hector,
At 18:22 07-08-2011, Hector Santos wrote:
>Of course, when implementation reports are written, one has to 
>watchful for the summarized analytical results that either attempt 
>to add weight to an desired goal or mask the undesired goal and natural result.

An implementation report is written to further a desired goal, i.e. 
advancement of a specification along the Standards Track.

>This is not an exercise we should have to go through.  Engineers 
>must have complete faith in implementation reports.

Faith-based engineering and reality are mutually exclusive. :-)

Regards,
-sm 


From ned+ietf@mauve.mrochek.com  Mon Aug  8 16:51:40 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9F3421F8B9E for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 16:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLi7kDVI2CSq for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 16:51:40 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB5321F8B8E for <ietf@ietf.org>; Mon,  8 Aug 2011 16:51:40 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4M4XYJRQ800ZMBR@mauve.mrochek.com> for ietf@ietf.org; Mon, 8 Aug 2011 16:51:07 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 8 Aug 2011 16:51:01 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4M4XWCXZ000VHKR@mauve.mrochek.com>
Date: Mon, 08 Aug 2011 16:44:54 -0700 (PDT)
Subject: RE: I-D Working groups and mailing list
In-reply-to: "Your message dated Mon, 08 Aug 2011 17:08:35 -0400" <B362153E2F6FC9F236C96BF2@PST.JCK.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <4E3A1C51.4040908@isdg.net> <1568238908.20110804001138@pobox.com> <4E3A5A1E.8050002@gmx.de> <EA34AC5BC8D9995010AB7429@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222B1F57DF@DC-US1MBEX4.global.avaya.com> <4E3AB2B8.6080501@dcrocker.net> <4E3AB642.3070208@isdg.net> <F5833273385BB34F99288B3648C4F06F13512DF57B@EXCH-C2.corp.cloudmark.com> <68496DEA09A833357F1852EC@[192.168.1.128]> <F5833273385BB34F99288B3648C4F06F13512DF5F9@EXCH-C2.corp.cloudmark.com> <01O4LYDD0O3C00VHKR@mauve.mrochek.com> <B362153E2F6FC9F236C96BF2@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1312847387; i=@mrochek.com; bh=3B0l+mRnrOd2uqjb3nQuLk7LeaABGj9RGgFqxUi2pUI=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=KXuibwnIwrx7NgNMwhCXdvB4Zk5grZphTdunoMSTk553FB/OT9kyGYAI48ZY3xb4+ SHxm06HyKF1mPj16v56qXXhXL30dpq3A17eQdtgS8HXnv1gqhmoPW257riZRzPZgPZ q6S69BbXxtQBqbZ8l2DyDAK9ai0+7kJ5gKhCW7qI=
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 23:51:40 -0000

> --On Monday, August 08, 2011 13:34 -0700
> ned+ietf@mauve.mrochek.com wrote:

> >> > -----Original Message-----
> >> > From: John C Klensin [mailto:john-ietf@jck.com]
> >> > Sent: Sunday, August 07, 2011 9:19 AM
> >> > To: Murray S. Kucherawy; ietf@ietf.org
> >> > Subject: RE: I-D Working groups and mailing list
> >> >
> >> > (4) Others (probably a partially overlapping group with (3))
> >> > just find more rules and requirements for more boilerplate
> >> > undesirable.  They would (at least mostly) be happy if lots
> >> > of off-list notes went to authors of I-Ds for which the
> >> > discussion forum wasn't clear, asking them about the
> >> > discussion forum and recommending that it be included in
> >> > the next draft.
> >
> > But flip it around and see what you get: Why should I, as a
> > document author who wants to notify people where the
> > discussion of the draft should take place, be forced to use
> > either an ad-hoc location in the document or have to send out a
> > bunch of additional emails? Why can't there be an *OPTIONAL*
> > well known location in our draft format (and corresponding XML
> > element(s)) that automated tools can pick up on so at a
> > minimum this information can go out as part of the new draft
> > notifications?
> >
> > In other words, the issue of whether or not there's a well
> > defined way  to incorporate this information is almost
> > entirely orthogonal to whether or not we require it's presence.

> Absolutely.  If whomever is maintaining the tool sets wants to
> provide that as an option element (or equivalent) for whatever
> source language they are supporting, I have no problem with it
> at all (and would be happy to convert my ad hoc mechanisms for
> supplying that information to use it as I revise documents).  We
> disagree in that I don't personally think it is worth the
> trouble because I think we could as easily advise people to use
> either a last subsection of an Introduction section or a <note>,
> but I'm not maintaining the tools and therefore don't feel
> entitled to a vote.

> I have only two concerns:

> (1) I don't want to see this made a requirement, largely because
> I think it could easily turn into a bureaucratic mess.

It certainly does not make sense for it to be a requirement for drafts in
general. I'm less sure when it comes to drafts under active discussion - I
really don't have a problem with "repost that so everyone knows where to go".

> (2) I don't want to see it (or anything else) back us into
> either a requirement that everyone use xml2rfc or a requirement
> that the source for I-Ds be submitted along with the formatted
> ASCII-text versions.  So, while "optional well known location in
> our draft format" is fine with me, tools that are expected to
> pick information up by parsing XML and reading XML elements
> aren't... simply because they would require that I-Ds be
> prepared in XML and that the XML be generally available at
> posting time.

I agree with trying to keep things this way, but I also think that as the
community's tools become more refined and sophisticated some amount of lossage
associated with their non-use is going to be unavoidable.

				Ned

From dougb@dougbarton.us  Mon Aug  8 17:16:25 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4439B21F8BDB for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 17:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ox-nOXGN0qUc for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 17:16:24 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6426F21F8549 for <ietf@ietf.org>; Mon,  8 Aug 2011 17:16:24 -0700 (PDT)
Received: (qmail 12123 invoked by uid 399); 9 Aug 2011 00:16:21 -0000
Received: from unknown (HELO 12-207-105-211.globalsuite.net) (dougb@dougbarton.us@12.207.105.211) by mail2.fluidhosting.com with ESMTPAM; 9 Aug 2011 00:16:21 -0000
X-Originating-IP: 12.207.105.211
X-Sender: dougb@dougbarton.us
Message-ID: <4E407C54.8020802@dougbarton.us>
Date: Mon, 08 Aug 2011 17:16:20 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: subject_prefix on IETF Discuss?
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <20110803232151.GA26475@gsp.org> <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net> <4E3C6722.9010503@dougbarton.us> <4E3CB0FF.2060609@dcrocker.net>
In-Reply-To: <4E3CB0FF.2060609@dcrocker.net>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Dave CROCKER <dhc2@dcrocker.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 00:16:25 -0000

On 08/05/2011 20:11, Dave CROCKER wrote:
> 
> 
> On 8/5/2011 2:56 PM, Doug Barton wrote:
>> To me it boils down to you saying in effect, "Here is my way of working
>> with e-mail, and I'd like the IETF to support it." If there was a way
>> that we could do that which had no impact on people who don't work that
>> way (such as the List-Id header) then I'd say go for it! But for those
>> of us who already filter our mail into folders these [tags] are useless
>> clutter that take up valuable screen real estate.
> 
> 
> Doug,
> 
> Perhaps you missed the part about this being common practice, including
> for other IETF mailing lists?

Why yes Dave, this is my first time writing an e-mail, or participating
in a, what do you call them? Mailing list? So thanks for pointing that
out to me.

> You are already suffering with the useless clutter.  The incremental
> pain for you is going to be nil.

That's the argument of someone who thinks that the thing proposed is a
good idea. If you believed it to be a bad idea I'm sure that you
wouldn't be suggesting that we add to the incremental pain.

>> If they break dkim that's a whole 'nother category of problems.
> 
> DKIM is designed for to deal with one posting and one delivery.  Mailing
> lists take delivery and re-post.  For almost all scenarios, DKIM was not
> intended to survive re-posting.

I wasn't referring to the post from the originator to the list, I was
referring to the message posted from the list.


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 hsantos@isdg.net  Mon Aug  8 18:20:47 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92B3221F8C04 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 18:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjuBrLYIvide for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 18:20:46 -0700 (PDT)
Received: from mail.catinthebox.net (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 50C2B21F8C00 for <ietf@ietf.org>; Mon,  8 Aug 2011 18:20:45 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=271; t=1312852861; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=wLJnqYozbYrp7sSWA/w81GytxXk=; b=PJrE4yM1z3vyxQ1qbhZW UTVvXbVNCGfi+5R4N2W5lloebE15YjoXBJB0XbG2HAsPRykvWP7XxHtvwOS/u1vm sRvfCU7v1mjnQ5PZCITM758DMe2yLUf1V64ffZBUadeNzvTS3YoEL+tvknZx6CQc xiuL8+rShqzSjOcMU4JpMlU=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 08 Aug 2011 21:21:01 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=fail policy=all author.d=isdg.net asl.d=beta.winserver.com (unauthorized signer); 
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1308319814.1089.5796; Mon, 08 Aug 2011 21:20:40 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; t=1312852560; h=Received:Received:Message-ID: Date:From:Organization:To:Subject:List-ID; bh=70CPdgVJiDGiQI7Pt9 W8/03PwBsTn5L+nwAjfnTQkAA=; b=leBOm/d5UH9OO/UAH0i5sO0iy31QgZC7Vt GwNtbbrorfQqSeJyJsgwEvfwrkbLJJlH08E+o45H8CQ/Lmu3H9oQsrxUpdotWZye jvBgf8K8Bh1IRuC3t1EjjGEnQUIOEkIPrHOD1UT245c/pS7cGd+vZxcxooytlzEo Fyj8hboWw=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 08 Aug 2011 21:16:00 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2279597908.405.6252; Mon, 08 Aug 2011 21:15:58 -0400
Message-ID: <4E408B9F.4020809@isdg.net>
Date: Mon, 08 Aug 2011 21:21:35 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt>	(Reducing the Standards  Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <4E3F3A56.806@isdg.net> <6.2.5.6.2.20110808153638.08eb9108@resistor.net>
In-Reply-To: <6.2.5.6.2.20110808153638.08eb9108@resistor.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 01:20:47 -0000

SM wrote:

>> This is not an exercise we should have to go through.  Engineers must 
>> have complete faith in implementation reports.
> 
> Faith-based engineering and reality are mutually exclusive. :-)

Touche!

-- 
Hector Santos, CTO
http://www.santronics.com






From johnl@iecc.com  Mon Aug  8 20:08:20 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6523D21F885A for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 20:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.633
X-Spam-Level: 
X-Spam-Status: No, score=-110.633 tagged_above=-999 required=5 tests=[AWL=0.566, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EzbhbJ0BWpZL for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 20:08:20 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id C870D21F884F for <ietf@ietf.org>; Mon,  8 Aug 2011 20:08:19 -0700 (PDT)
Received: (qmail 85290 invoked from network); 9 Aug 2011 03:08:45 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 9 Aug 2011 03:08:45 -0000
Received: (qmail 3072 invoked from network); 9 Aug 2011 03:08:45 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Aug 2011 03:08:45 -0000
Date: 9 Aug 2011 03:08:23 -0000
Message-ID: <20110809030823.61303.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
In-Reply-To: <4E407C54.8020802@dougbarton.us>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 03:08:20 -0000

>> DKIM is designed for to deal with one posting and one delivery.  Mailing
>> lists take delivery and re-post.  For almost all scenarios, DKIM was not
>> intended to survive re-posting.
>
>I wasn't referring to the post from the originator to the list, I was
>referring to the message posted from the list.

The list signs the message on the way out, so the ietf.org signature
verifies.  If the original sender signed the message, his signature
won't verify but (to collapse several years of flamage on the DKIM
list) that's not a problem.

I still don't think we should add subject tags for the aforementioned
autotrofigiaskylousphagic reasons, but DKIM signs perfectly well
either way.

R's,
John




From dougb@dougbarton.us  Mon Aug  8 20:15:45 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0726111E80A7 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 20:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJ8FhqUBmhDL for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 20:15:44 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 314EF11E80A1 for <ietf@ietf.org>; Mon,  8 Aug 2011 20:15:43 -0700 (PDT)
Received: (qmail 17565 invoked by uid 399); 9 Aug 2011 03:16:09 -0000
Received: from unknown (HELO 12-207-105-211.globalsuite.net) (dougb@dougbarton.us@12.207.105.211) by mail2.fluidhosting.com with ESMTPAM; 9 Aug 2011 03:16:09 -0000
X-Originating-IP: 12.207.105.211
X-Sender: dougb@dougbarton.us
Message-ID: <4E40A677.60001@dougbarton.us>
Date: Mon, 08 Aug 2011 20:16:07 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: subject_prefix on IETF Discuss?
References: <20110809030823.61303.qmail@joyce.lan>
In-Reply-To: <20110809030823.61303.qmail@joyce.lan>
X-Enigmail-Version: 1.2pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 03:15:45 -0000

On 08/08/2011 20:08, John Levine wrote:
> I still don't think we should add subject tags for the aforementioned
> autotrofigiaskylousphagic reasons, but DKIM signs perfectly well
> either way.

Thank you for clarifying that.


-- 

	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 gwz@net-zen.net  Mon Aug  8 23:00:31 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCBCF11E8086 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vI9zTGoectdR for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:00:31 -0700 (PDT)
Received: from smtpauth12.prod.mesa1.secureserver.net (smtpauth12.prod.mesa1.secureserver.net [64.202.165.35]) by ietfa.amsl.com (Postfix) with SMTP id EBA3911E807B for <ietf@ietf.org>; Mon,  8 Aug 2011 23:00:30 -0700 (PDT)
Received: (qmail 1805 invoked from network); 9 Aug 2011 06:00:58 -0000
Received: from unknown (124.120.247.89) by smtpauth12.prod.mesa1.secureserver.net (64.202.165.35) with ESMTP; 09 Aug 2011 06:00:57 -0000
Message-ID: <4E40CD13.3020904@net-zen.net>
Date: Tue, 09 Aug 2011 13:00:51 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------070806090500060900010709"
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 06:00:31 -0000

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

On 8/8/2011 2:56 PM, Ole Jacobsen wrote:
> 
> 
> Nothing is "a reasonable walk" when the average temperature is 32 C.
> At least not for the "average" IETF attendee.

Just to add a little perspective for the Celsius-challenged ;-), 32C =
89.6F.  Warm, but not IMHO life-threatening, even for the sedentary ;-).

> 
> (34 in April, 31 in December, lowest nightime temp 21 in December and
> 27 in April-May-June).
> 
> We did APRICOT at this venue in 2002. Not a bad place for a 
> conference, but most certainly requires transportation to the hotels.

Yes, that would be a good idea; taxis are plentiful, extremely cheap
_and_ they'll actually take you places (as opposed to Seoul, MSP and QC,
where I have been repeatedly refused carriage)...

...

--------------070806090500060900010709
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------070806090500060900010709--

From randy@psg.com  Mon Aug  8 23:06:42 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77AF821F8588; Mon,  8 Aug 2011 23:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.467
X-Spam-Level: 
X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=0.132,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZxSKoXAEWouQ; Mon,  8 Aug 2011 23:06:42 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2691721F855A; Mon,  8 Aug 2011 23:06:42 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QqfT0-0002up-FF; Tue, 09 Aug 2011 06:07:06 +0000
Date: Tue, 09 Aug 2011 15:07:04 +0900
Message-ID: <m2ipq73ypj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Glen Zorn <gwz@net-zen.net>
Subject: Re: [xml2rfc] Multiple authors in reference
In-Reply-To: <4E40CE36.2000806@net-zen.net>
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com> <4E40CE36.2000806@net-zen.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 06:06:42 -0000

>> above five, the rfced's deal with the iesg is that the masthead lists
>> an editor and all the rest are in a Contributors or Authors section
> I see.  So the author limit isn't really a "guideline" (as advertised)
> or even a rule, just a backroom "deal".

have you taken your meds today?

From gwz@net-zen.net  Mon Aug  8 23:28:31 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3015F21F882E for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p52JEkYR0anL for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:28:30 -0700 (PDT)
Received: from p3plsmtpa01-09.prod.phx3.secureserver.net (p3plsmtpa01-09.prod.phx3.secureserver.net [72.167.82.89]) by ietfa.amsl.com (Postfix) with SMTP id B32AE21F8828 for <ietf@ietf.org>; Mon,  8 Aug 2011 23:28:30 -0700 (PDT)
Received: (qmail 28650 invoked from network); 9 Aug 2011 06:28:57 -0000
Received: from unknown (124.120.247.89) by p3plsmtpa01-09.prod.phx3.secureserver.net (72.167.82.89) with ESMTP; 09 Aug 2011 06:28:57 -0000
Message-ID: <4E40D3A3.30709@net-zen.net>
Date: Tue, 09 Aug 2011 13:28:51 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com>
In-Reply-To: <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------080006040608070309080902"
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 06:28:31 -0000

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

On 8/8/2011 8:56 PM, Yoav Nir wrote:

> 
> On Aug 8, 2011, at 10:56 AM, Ole Jacobsen wrote:
> 
>> 
>> 
>> Nothing is "a reasonable walk" when the average temperature is 32
>> C. At least not for the "average" IETF attendee.
>> 
>> (34 in April, 31 in December, lowest nightime temp 21 in December
>> and 27 in April-May-June).
> 
> Pretty much like Tel Aviv in August.
> 
> Tucson or Phoenix have much higher temperatures, but what it lacks in
> raw degrees, Bangkok makes up for with suffocating humidity.

I think that "suffocating" is a little over the top, but if you live in
a desert I suppose it might seem that way.  Nevertheless, the humidity
is nothing like that in NYC, Houston, Minneapolis (an IETF favorite) or
even Paris...

--------------080006040608070309080902
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------080006040608070309080902--

From gwz@net-zen.net  Mon Aug  8 23:31:59 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC8411E808A for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALCpRZ0yGJMB for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:31:59 -0700 (PDT)
Received: from p3plsmtpa06-02.prod.phx3.secureserver.net (p3plsmtpa06-02.prod.phx3.secureserver.net [173.201.192.103]) by ietfa.amsl.com (Postfix) with SMTP id 2892911E807B for <ietf@ietf.org>; Mon,  8 Aug 2011 23:31:59 -0700 (PDT)
Received: (qmail 23294 invoked from network); 9 Aug 2011 06:05:47 -0000
Received: from unknown (124.120.247.89) by p3plsmtpa06-02.prod.phx3.secureserver.net (173.201.192.103) with ESMTP; 09 Aug 2011 06:05:47 -0000
Message-ID: <4E40CE36.2000806@net-zen.net>
Date: Tue, 09 Aug 2011 13:05:42 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: [xml2rfc] Multiple authors in reference
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com>
In-Reply-To: <m2liv46zs5.wl%randy@psg.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------040200050005040901020603"
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 06:31:59 -0000

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

On 8/8/2011 4:03 PM, Randy Bush wrote:
>> When using <reference> and the document I am referencing has say 20
>>  authors. Is there a way to fill in the <author> field as "John Doe
>> et al" or do I have to list all the 20 authors?
> 
> above five, the rfced's deal with the iesg is that the masthead lists
> an editor and all the rest are in a Contributors or Authors section

I see.  So the author limit isn't really a "guideline" (as advertised)
or even a rule, just a backroom "deal".  I wonder how many other things
in the IETF are like that...certainly not many, in this age of IESG
transparency ;-).

--------------040200050005040901020603
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------040200050005040901020603--

From gwz@net-zen.net  Mon Aug  8 23:32:10 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1784C11E8091 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8O4hdptRRNhV for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 23:32:09 -0700 (PDT)
Received: from smtpauth14.prod.mesa1.secureserver.net (smtpauth14.prod.mesa1.secureserver.net [64.202.165.39]) by ietfa.amsl.com (Postfix) with SMTP id E82A111E807B for <ietf@ietf.org>; Mon,  8 Aug 2011 23:32:07 -0700 (PDT)
Received: (qmail 7951 invoked from network); 9 Aug 2011 06:32:35 -0000
Received: from unknown (124.120.247.89) by smtpauth14.prod.mesa1.secureserver.net (64.202.165.39) with ESMTP; 09 Aug 2011 06:32:35 -0000
Message-ID: <4E40D47B.2030909@net-zen.net>
Date: Tue, 09 Aug 2011 13:32:27 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <389DB247-47EC-4058-9D1B-643925B61B27@checkpoint.com> <1D5C586851E84A87B99E6E0A@PST.JCK.COM>
In-Reply-To: <1D5C586851E84A87B99E6E0A@PST.JCK.COM>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------050609050409090800090802"
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 06:32:10 -0000

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

On 8/8/2011 9:43 PM, John C Klensin wrote:
...

> Of course, given some of the other suggestions made recently, we
> probably should also be considering Tel Aviv as a meeting site

I like this idea.

> -- from what I understand, non-trivial numbers of IETF
> participants (unlike some places discussed recently), plausible
> hotel costs, decent airport and international connections, good
> in-country Internet infrastructure.  Might be plausible for a
> late fall or early spring meeting if there are adequate meeting
> facilities... I take the above to be a hint that August should
> be avoided.
> 
>     john
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

--------------050609050409090800090802
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------050609050409090800090802--

From peter@denic.de  Tue Aug  9 00:09:42 2011
Return-Path: <peter@denic.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABA1321F8438 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 00:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.979
X-Spam-Level: 
X-Spam-Status: No, score=-101.979 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2qQJnHnVyec9 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 00:09:41 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id D8D8921F851A for <ietf@ietf.org>; Tue,  9 Aug 2011 00:09:38 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QqgRs-0006n3-IF; Tue, 09 Aug 2011 09:10:00 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QqgRs-0003pU-El; Tue, 09 Aug 2011 09:10:00 +0200
Date: Tue, 9 Aug 2011 09:10:00 +0200
From: Peter Koch <pk@ISOC.DE>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
Message-ID: <20110809071000.GQ30809@x27.adm.denic.de>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 07:09:43 -0000

On Wed, Jul 27, 2011 at 07:02:07PM -0700, The IESG wrote:

> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Reducing the Standards Track to Two Maturity Levels'
>   <draft-housley-two-maturity-levels-08.txt> as a BCP


I have reviewed this version of the document and also the changes since -07.
While i am not sure that there is really a problem to solve, the current
version appears reasonable and an improvement over -07.  However, it would
benefit from a few clarifications before publication.  Also, even if it
will become part of BCP 9, i consider it a bit undesirable to distribute the core
IETF standards process across more than one document. For the short term,
that should be OK, though.

> 1.  Introduction

>    This document proposes several changes to the Internet Standards
>    Process defined in RFC 2026 [1].  In recent years, the Internet
>    Engineering Task Force (IETF) has witnessed difficulty in advancing
>    documents through the maturity levels: Proposed Standard, Draft
>    Standard, and finally Standard.  These changes are designed to
>    simplify the Standards Process and reduce impediments to standards
>    progression while preserving the most important benefits of the IETF
>    engineering approach.  In addition, the requirement for annual review
>    of standards-track documents that have not reached the top of the
>    maturity ladder is removed from the Internet Standards Process.

this informal language is a nice read, but consistency with RFC 2026
would suggest to say "standards track" instead of "maturity ladder".

> 2.  Two Maturity Levels

>    This document, once approved, replaces the three-tier maturity ladder
>    defined in RFC 2026 [1] with a two-tier maturity ladder.
>    Specifications become Internet Standards through a set of two
>    maturity levels known as the "standards track".  These maturity
>    levels are "Proposed Standard" and "Internet Standard".

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

Suggest to add a reference to section 6.1.1 of RFC 2026 to clarify that
"recommended action" is actually the WG's request for advancement.

> 2.2.  The Second Maturity Level: Internet Standard

>    This maturity level is a merger of Draft Standard and Standard as
>    specified in RFC 2026 [1].  The chosen name avoids confusion between
>    "Draft Standard" and "Internet-Draft".

>    The characterization of an Internet Standard remains as described in
>    RFC 2026 [1], which says:

>       An Internet Standard is characterized by a high degree of
>       technical maturity and by a generally held belief that the
>       specified protocol or service provides significant benefit
>       to the Internet community.

>    The criteria for advancing from Proposed Standard to Internet
>    Standard are confirmed by the IESG in an IETF-wide Last Call of at
>    least four weeks.  The request for reclassification is sent to the
>    IESG along with an explanation of how the criteria have been met.
>    The criteria are:

>    (1) There are at least two independent interoperating implementations
>        with widespread deployment and successful operational experience.

>    (2) There are no errata against the specification that would cause a
>        new implementation to fail to interoperate with deployed ones.

>    (3) There are no unused features in the specification that greatly
>        increase implementation complexity.

Operational complexity should be of equal concern.

>    (4) If patented or otherwise controlled technology is required for
>        implementation, the implementations demonstrate at least two
>        separate and successful uses of the licensing process.

>    After review and consideration of significant errata, the IESG will
>    perform an IETF-wide Last Call of at least four weeks on the
>    requested reclassification.

Is this another four weeks or the same as mentioned above?  In case of the
latter the first occurence could be removed to maintain chronological
ordering.

>    requested reclassification.  If there is consensus for
>    reclassification, the RFC will be reclassified without publication of
>    a new RFC.

So, how would a modified specification (say, with unused features not
passing criterion 3) be advanced?

>    As stated in RFC 2026 [1], in a timely fashion after the expiration
>    of the Last Call period, the IESG shall make its final determination
>    and notify the IETF of its decision via electronic mail to the IETF
>    Announce mailing list.  No changes are made to Section 6.1.2 of RFC
>    2026 [1].

Except for the extension of the LC period from two to four weeks, which
is good - but makes this an ambiguous statement.

> 2.3.  Transition to a Standards Track with Two Maturity Levels

>    Any protocol or service that is currently at the Proposed Standard
>    maturity level remains so.

>    Any protocol or service that is currently at the Standard maturity
>    level shall be immediately reclassified as an Internet Standard.

>    Any protocol or service that is currently at the abandoned Draft
>    Standard maturity level will retain that classification, absent
>    explicit actions.  Two possible actions are available:

>    (1) A Draft Standard may be reclassified as an Internet Standard as
>        soon as the criteria in Section 2.2 are satisfied.

>    (2) At any time after two years from the approval of this document as
>        a BCP, the IESG may choose to reclassify any Draft Standard
>        document as Proposed Standard.

> 3.  Removal of Requirement for Annual Review

>    In practice the annual review of Proposed Standard and Draft Standard
>    documents after two years called for in RFC 2026 [1] has not taken
>    place.  Lack of this review has not revealed any ill effects on the
>    Internet Standards Process.  As a result, the requirement for this
>    review is dropped.  No review cycle is imposed on standards track
>    documents at any maturity level.

I disagree with this analysis.  Lack of review (for whatever reason) has
lead to a perceived failure of the three-level standards track and thus
_had_ an effect on the standards process.  So, the reason to remove
this requirement is to bring it in line with reality and to deal with
the limited work force.

-Peter

From gwz@net-zen.net  Tue Aug  9 00:29:25 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B8721F8770 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 00:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5eKlqzI2IGI for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 00:29:24 -0700 (PDT)
Received: from p3plsmtpa07-06.prod.phx3.secureserver.net (p3plsmtpa07-06.prod.phx3.secureserver.net [173.201.192.235]) by ietfa.amsl.com (Postfix) with SMTP id A655121F86BA for <ietf@ietf.org>; Tue,  9 Aug 2011 00:29:24 -0700 (PDT)
Received: (qmail 27137 invoked from network); 9 Aug 2011 07:29:52 -0000
Received: from unknown (124.120.247.89) by p3plsmtpa07-06.prod.phx3.secureserver.net (173.201.192.235) with ESMTP; 09 Aug 2011 07:29:52 -0000
Message-ID: <4E40E1EA.5020603@net-zen.net>
Date: Tue, 09 Aug 2011 14:29:46 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: [xml2rfc] Multiple authors in reference
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com> <4E40CE36.2000806@net-zen.net> <6.2.5.6.2.20110808235035.07adc1a8@resistor.net>
In-Reply-To: <6.2.5.6.2.20110808235035.07adc1a8@resistor.net>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------000402070406090404060400"
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 07:29:25 -0000

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

On 8/9/2011 1:53 PM, SM wrote:
> Hi Glen, At 23:05 08-08-2011, Glen Zorn wrote:
>> I see.  So the author limit isn't really a "guideline" (as
>> advertised) or even a rule, just a backroom "deal".  I wonder how
>> many other things
> 
> http://www.rfc-editor.org/policy.html#policy.authlist

says

"There is no rigid limit on the size of this set, but there is likely to
be a discussion if the set exceeds five authors, in which case the right
answer is probably to list one editor."

which seems to be contradicted by Randy's assertion.

--------------000402070406090404060400
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------000402070406090404060400--

From joelja@bogus.com  Tue Aug  9 01:07:07 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C000921F8713; Tue,  9 Aug 2011 01:07:07 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ta8-+Jh2HAr; Tue,  9 Aug 2011 01:07:07 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2103221F8438; Tue,  9 Aug 2011 01:07:07 -0700 (PDT)
Received: from [192.168.1.170] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7987VYH081277 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 9 Aug 2011 08:07:33 GMT (envelope-from joelja@bogus.com)
Subject: Re: [xml2rfc] Multiple authors in reference
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <m2ipq73ypj.wl%randy@psg.com>
Date: Tue, 9 Aug 2011 01:07:30 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <FC3BAAFB-626D-4937-8304-BBA327917ECF@bogus.com>
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com> <4E40CE36.2000806@net-zen.net> <m2ipq73ypj.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 09 Aug 2011 08:07:35 +0000 (UTC)
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 08:07:07 -0000

On Aug 8, 2011, at 11:07 PM, Randy Bush wrote:

>>> above five, the rfced's deal with the iesg is that the masthead lists
>>> an editor and all the rest are in a Contributors or Authors section
>> I see.  So the author limit isn't really a "guideline" (as advertised)
>> or even a rule, just a backroom "deal".
> 
> have you taken your meds today?

http://tools.ietf.org/html/draft-rfc-editor-rfc2223bis-08

 2.12 Authors Listed on RFC


      The IESG and IETF have ratified a policy of limiting the number of
      authors listed in the first page header of an RFC.  The specific
      policy is as follows:


      (1)  A small set of author names, with affiliations, may appear on
           the front page header.  These should be the lead author(s)
           who are most responsible for the actual text.  When there are
           many contributors, the best choice will be to list the person
           or (few) persons who acted as document editor(s) (e.g.,"Tom
           Smith, Editor").


           There is no rigid limit on the size of this set, but there is
           likely to be a discussion if the set exceeds five authors, in
           which case the right answer is probably to list one editor.


           The RFC Editor will hold all the people listed on the front





RFC Editor                   Informational                     [Page 13]
 
Internet-Draft        Instructions to RFC Authors          1 August 2004




           page equally responsible for the final form and content of
           the published RFC.  In particular, the "Author's 48 Hours"
           final approval period will require signoff from all listed
           authors.


      (2)  An RFC may include a Contributors section, listing those
           contributors who deserve significant credit for the document
           contents.  The Contributors section is intended to provide a
           level of recognition greater than an acknowledgment and
           nearly equal to listing on the front page.  The choice of
           either, both, or none of Contributor and Acknowledgment
           sections in a particular RFC depends upon the circumstance.


      (3)  The body of an RFC may include an Acknowledgements section,
           in addition to or instead of a Contributors section.  An
           Acknowledgments section may be lengthy, and it may explain
           scope and nature of contributions.  It may also specify
           affiliations.


      (4)  The Author's Address section at the end of the RFC must
           include the authors listed in the front page header.  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.


           At the discretion of the author(s), contact addresses may
           also be included in the Contributors section for those
           contributors whose knowledge makes them useful future
           contacts for information about the RFC.


      (5)  The RFC Editor may grant exceptions to these guidelines upon
           specific IESG request or in other exceptional circumstances.


      Finally, it is important to note that the copyright rules
      governing RFC publication [IPC04] require that an RFC must:


           "[acknowledge] all major Contributors.  A major Contributor
           is any person who has materially or substantially contributed
           to the [RFC]."


      The Contributors and Acknowledgment sections fulfill this
      objective.

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


From gwz@net-zen.net  Tue Aug  9 05:53:21 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 374A221F8B21 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 05:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4HqySPj8TtWU for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 05:53:20 -0700 (PDT)
Received: from p3plsmtpa07-10.prod.phx3.secureserver.net (p3plsmtpa07-10.prod.phx3.secureserver.net [173.201.192.239]) by ietfa.amsl.com (Postfix) with SMTP id 94DB221F8B0C for <ietf@ietf.org>; Tue,  9 Aug 2011 05:53:20 -0700 (PDT)
Received: (qmail 22320 invoked from network); 9 Aug 2011 12:53:49 -0000
Received: from unknown (124.120.247.89) by p3plsmtpa07-10.prod.phx3.secureserver.net (173.201.192.239) with ESMTP; 09 Aug 2011 12:53:47 -0000
Message-ID: <4E412DD3.4050404@net-zen.net>
Date: Tue, 09 Aug 2011 19:53:39 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: [xml2rfc] Multiple authors in reference
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com> <4E40CE36.2000806@net-zen.net> <m2ipq73ypj.wl%randy@psg.com> <FC3BAAFB-626D-4937-8304-BBA327917ECF@bogus.com>
In-Reply-To: <FC3BAAFB-626D-4937-8304-BBA327917ECF@bogus.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------030102080300010909060500"
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 12:53:21 -0000

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

On 8/9/2011 3:07 PM, Joel Jaeggli wrote:
> 
> On Aug 8, 2011, at 11:07 PM, Randy Bush wrote:
> 
>>>> above five, the rfced's deal with the iesg is that the masthead
>>>> lists an editor and all the rest are in a Contributors or
>>>> Authors section
>>> I see.  So the author limit isn't really a "guideline" (as
>>> advertised) or even a rule, just a backroom "deal".
>> 
>> have you taken your meds today?
> 
> http://tools.ietf.org/html/draft-rfc-editor-rfc2223bis-08

Uh-huh, expired ~7 years ago.  A reasonable place to put this rule (if
you wanted to make it a rule) might have been RFC 5741 but it doesn't
seem to be there.

...

--------------030102080300010909060500
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------030102080300010909060500--

From wjhns1@hardakers.net  Tue Aug  9 07:52:05 2011
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A570521F876F for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 07:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.512
X-Spam-Level: 
X-Spam-Status: No, score=-3.512 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iGNp0tUSoS+e for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 07:52:05 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id 27F2D21F874E for <ietf@ietf.org>; Tue,  9 Aug 2011 07:52:05 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id A43DE668; Tue,  9 Aug 2011 07:52:03 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Glen Zorn <gwz@net-zen.net>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <4E3ED22B.3060405@qualcomm.com> <4E3F7B08.4000209@net-zen.net>
Date: Tue, 09 Aug 2011 07:52:03 -0700
In-Reply-To: <4E3F7B08.4000209@net-zen.net> (Glen Zorn's message of "Mon, 08 Aug 2011 12:58:32 +0700")
Message-ID: <sdd3gefxik.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: Pete Resnick <presnick@qualcomm.com>, iaoc-mtgs@ISOC.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 14:52:05 -0000

>>>>> On Mon, 08 Aug 2011 12:58:32 +0700, Glen Zorn <gwz@net-zen.net> said:

GZ> In any case, a taxi from any of the hotels on the list would today
GZ> cost < $3 (probably closer to $2) one way.

I'd argue that group shuttles, as has been done in the past, is probably
a better option than trying to have 1000 people even share taxi rides.
-- 
Wes Hardaker
SPARTA, Inc.

From rsk@gsp.org  Mon Aug  8 08:35:30 2011
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1875821F8AF9 for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 08:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6O233mbEWddk for <ietf@ietfa.amsl.com>; Mon,  8 Aug 2011 08:35:29 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id 821FD21F85C0 for <ietf@ietf.org>; Mon,  8 Aug 2011 08:35:29 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.113.dsl.charm.net [207.114.17.113]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id p78FZq44023980 for <ietf@ietf.org>; Mon, 8 Aug 2011 11:35:54 -0400 (EDT)
Received: from vorlon.gsp.org (vorlon.gsp.org [192.168.0.20]) by squonk.gsp.org (8.14.3/8.14.3) with ESMTP id p78Fe3Ie017448 for <ietf@ietf.org>; Mon, 8 Aug 2011 11:40:03 -0400 (EDT)
Received: from localhost6.localdomain6 (localhost.localdomain [127.0.0.1]) by vorlon.gsp.org (8.14.3/8.14.3/Debian-9.2ubuntu1) with ESMTP id p78FZlwD006083 for <ietf@ietf.org>; Mon, 8 Aug 2011 11:35:47 -0400
Received: (from rsk@localhost) by localhost6.localdomain6 (8.14.3/8.14.3/Submit) id p78FZkqM006082 for ietf@ietf.org; Mon, 8 Aug 2011 11:35:46 -0400
Date: Mon, 8 Aug 2011 11:35:46 -0400
From: Richard Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
Message-ID: <20110808153546.GA5290@gsp.org>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <20110803232151.GA26475@gsp.org> <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Tue, 09 Aug 2011 08:18:24 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2011 15:35:30 -0000

On Fri, Aug 05, 2011 at 12:45:06PM -0400, Warren Kumari wrote:
> Still a little confused how this morphed into a religious war on RFC 2919 / List-Id. 

I don't think it's a religious war: I think it's long since been
demonstrated that RFC 2919 (and 2369) including List-Id are not only
good ideas, but best practices, and that subject-line tags should
be deprecated/avoided/discouraged, because they're just a kludge.

That is, this is an issue of technical merit, not arbitrary whim.
So instead of bringing back the obsolete idea of subject-line tags, we
should instead be encouraging (a) all IETF lists *not* to use them, but to
use List-Id et.al. instead (b) all (relevant) mail software providers to
support them and (c) all (relevant) mail server providers to support them.
These mechanisms neatly solve a number of problems, and that better
positions everyone to tackle those that remain.

---rsk


From moore@network-heretics.com  Tue Aug  9 09:04:30 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D7D21F8C8B for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 09:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[AWL=-0.136, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DE4QJqTRs4Jq for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 09:04:29 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 8EBCA21F8C89 for <ietf@ietf.org>; Tue,  9 Aug 2011 09:04:29 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2219220E7E; Tue,  9 Aug 2011 12:04:58 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 09 Aug 2011 12:04:58 -0400
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=fuU03KCH+vIJiE/Tl96MaGMPqEA=; b=lW m8WEYkb5obWryYN70GbZ+O3TeGPIo+9mBzSMaw7Ts2w2K1PjUl4mrUxIATZDAXWK VZvw+HvQh6LndNQ0V2vMnbQHaXxFUH10KAX+BC/OVE60arj4MaaCoEKE4d4VUBGu JKfE+f06Tn1HkWUS/QAKIHRTyl9geBF0zqKB61f0g=
X-Sasl-enc: iUUlSesYatrTk+K/vsVhWz01i3Nf/DabQohNLXebaEaa 1312905897
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 505B541A626; Tue,  9 Aug 2011 12:04:57 -0400 (EDT)
Subject: Re: subject_prefix on IETF Discuss?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110808153546.GA5290@gsp.org>
Date: Tue, 9 Aug 2011 12:04:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB04A5B3-3F7C-4536-8EA4-633F9BBB4ACA@network-heretics.com>
References: <F7855AD4-930D-489F-BAC4-0CC921833E28@kumari.net> <20110803232151.GA26475@gsp.org> <0E20E4AB-A6A5-462C-8C46-B7C3C13F922B@kumari.net> <20110808153546.GA5290@gsp.org>
To: Richard Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 16:04:30 -0000

On Aug 8, 2011, at 11:35 AM, Richard Kulawiec wrote:

> On Fri, Aug 05, 2011 at 12:45:06PM -0400, Warren Kumari wrote:
>> Still a little confused how this morphed into a religious war on RFC =
2919 / List-Id.=20
>=20
> I don't think it's a religious war: I think it's long since been
> demonstrated that RFC 2919 (and 2369) including List-Id are not only
> good ideas, but best practices, and that subject-line tags should
> be deprecated/avoided/discouraged, because they're just a kludge.
>=20
> That is, this is an issue of technical merit, not arbitrary whim.
> So instead of bringing back the obsolete idea of subject-line tags, we
> should instead be encouraging (a) all IETF lists *not* to use them, =
but to
> use List-Id et.al. instead (b) all (relevant) mail software providers =
to
> support them and (c) all (relevant) mail server providers to support =
them.
> These mechanisms neatly solve a number of problems, and that better
> positions everyone to tackle those that remain.

+1


From phdgang@gmail.com  Tue Aug  9 09:13:57 2011
Return-Path: <phdgang@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AEB621F8C20; Tue,  9 Aug 2011 09:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.231
X-Spam-Level: 
X-Spam-Status: No, score=-3.231 tagged_above=-999 required=5 tests=[AWL=-0.232, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9vXDyoDiTKtk; Tue,  9 Aug 2011 09:13:56 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 65DA921F8C1A; Tue,  9 Aug 2011 09:13:56 -0700 (PDT)
Received: by vxi29 with SMTP id 29so142051vxi.31 for <multiple recipients>; Tue, 09 Aug 2011 09:14:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=L4SAryZ0/owXXo8VYcWV6BJW7PEVXhHp8Wsz6dwsXJg=; b=MF3KtqBv4ciSvTc8AoO1clSkAV4TiElysMDblVxnE7DBBjNCFAaKOnJ57GPTi+8S7r WcCk3/3pFZ6meCnAADwBJdeV7JeDEV3eMp9UKnch3MOU0v87DUuDyWkp+oZIMhBrHrxz Em7FAEKrXBrF1lwNTadTYsxBX+wD7RM0PbM7A=
MIME-Version: 1.0
Received: by 10.52.180.102 with SMTP id dn6mr6442281vdc.51.1312906465150; Tue, 09 Aug 2011 09:14:25 -0700 (PDT)
Received: by 10.52.169.129 with HTTP; Tue, 9 Aug 2011 09:14:25 -0700 (PDT)
In-Reply-To: <49A19FE6-7B0A-4876-8F1A-308F978CC8FC@gmail.com>
References: <20110801190301.16571.58632.idtracker@ietfa.amsl.com> <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com> <49A19FE6-7B0A-4876-8F1A-308F978CC8FC@gmail.com>
Date: Wed, 10 Aug 2011 00:14:25 +0800
Message-ID: <CAM+vMEQXsJoaezEwMVsQYUhR0AcxmBths2WuWgcBHS3=eCey_w@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-3gpp-eps-03.txt> (IPv6 in 3GPP Evolved Packet System) to Informational RFC
From: GangChen <phdgang@gmail.com>
To: Jouni <jounikor@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: v6ops@ietf.org, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 16:13:57 -0000

Dear Jouni,

In mobile CPE case, MT and TE are separated. That would need
additional requirements in some particular cases, e.g. dynamic IPv6
address allocation.

According to the 3GPP specification, the UE shall build the link-local
address using the interface identifier provided by the PDN GW upon PDN
connection establishment. However, MT may not be able to transfer the
interface identifier to TE in the CPE cases. The only thing the IP
devices can do is to select the interface identifier by some other
means and then perform Duplicate Address Detection, as specified in
RFC 4862. The PDN GW shall then perform the DAD check based on the
Neighbor Solicitation messages sent by the UE.

Therefore, there are some implementation factors that may change UE
behaviour in the CPE context. IMHO, it would be beneficial to describe
CPE consideration in section 5.3. CPE case has already appeared to be
a valid scenario in 3GPP

BRs

Gang

2011/8/5, Jouni <jounikor@gmail.com>:
> Dear Gang,
>
> I would be inclined to say that within the 3GPP scope the client is always
> the "UE" and its form factor or the end usage scenario does not really
> matter. It does not change the way the UE is expected to behave from the
> 3GPP system point of view, unless there is a new functional requirement from
> 3GPP.
>
> - Jouni
>
>
>
> On Aug 5, 2011, at 5:55 AM, GangChen wrote:
>
>> Hello Authors,
>>
>> I think it is worth adding some texts to describe mobile CPE case, in
>> which CPEs with wireless modem use 3GPP access as uplink.
>>
>> Gang
>>
>>
>> 2011/8/2, The IESG <iesg-secretary@ietf.org>:
>>>
>>> The IESG has received a request from the IPv6 Operations WG (v6ops) to
>>> consider the following document:
>>> - 'IPv6 in 3GPP Evolved Packet System'
>>>  <draft-ietf-v6ops-3gpp-eps-03.txt> as an Informational RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2011-08-15. Exceptionally, comments may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>   Use of data services in smart phones and broadband services via HSPA
>>>   and HSPA+, in particular Internet services, has increased rapidly and
>>>   operators that have deployed networks based on 3GPP network
>>>   architectures are facing IPv4 address shortages at the Internet
>>>   registries and are feeling a pressure to migrate to IPv6.  This
>>>   document describes the support for IPv6 in 3GPP network
>>>   architectures.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>
>

From Ed.Lewis@neustar.biz  Tue Aug  9 09:57:44 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54CF421F8B8C for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 09:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.677
X-Spam-Level: 
X-Spam-Status: No, score=-106.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8U74DwiZv6ae for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 09:57:43 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id A790321F8B89 for <ietf@ietf.org>; Tue,  9 Aug 2011 09:57:43 -0700 (PDT)
Received: from work-laptop-2 (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p79Gw33X029663; Tue, 9 Aug 2011 12:58:04 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.201.42] by work-laptop-2 (PGP Universal service); Tue, 09 Aug 2011 12:58:04 -0400
X-PGP-Universal: processed; by work-laptop-2 on Tue, 09 Aug 2011 12:58:04 -0400
Mime-Version: 1.0
Message-Id: <a06240800ca6713e13df6@[10.31.201.42]>
In-Reply-To: <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com>
Date: Tue, 9 Aug 2011 12:52:14 -0400
To: IETF Discussion <ietf@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: Queen Sirikit National Convention Center
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.71 on 10.20.30.4
Cc: ed.lewis@neustar.biz
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 16:57:44 -0000

At 0:56 -0700 8/8/11, Ole Jacobsen wrote:
>Nothing is "a reasonable walk" when the average temperature is 32 C.
>At least not for the "average" IETF attendee.
>
>(34 in April, 31 in December, lowest nightime temp 21 in December and
>27 in April-May-June).
>
>We did APRICOT at this venue in 2002. Not a bad place for a
>conference, but most certainly requires transportation to the hotels.

I was there too, for 10-14 days.  It was an experience I never 
forgot.  At the time there was considerable road work at a key 
intersection not far from the venue.  I was staying at the Windsor 
Suites with a room that could see the main entrance of the venue.

Despite the "long way" being about 1 mile, it would take about 45 
mins to get from the hotel to venue via a van/taxi.  And taxi's were 
funnier.  Although we had hotel cards printed in both English and 
Thai, the driver always needed an "interpreter" (usually a venue 
staff member at the door) to read the card back to him.  One 
English-speaking cabbie explained that this wasn't a language problem 
but an eyesight problem.  Most cabbies couldn't see well enough to 
make out the card's contents.  (Including the driver we spoke too.)

At least with the traffic moving so slow you didn't need good eyes to drive.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

I'm overly entertained.

From mrex@sap.com  Tue Aug  9 10:16:33 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2B221F8CC5 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 10:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.688
X-Spam-Level: 
X-Spam-Status: No, score=-9.688 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZkstHgeb-YZM for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 10:16:32 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id E294021F8CC4 for <ietf@ietf.org>; Tue,  9 Aug 2011 10:16:31 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p79HGexK027853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 9 Aug 2011 19:16:40 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108091716.p79HGdhL008452@fs4113.wdf.sap.corp>
Subject: Re: subject_prefix on IETF Discuss?
To: rsk@gsp.org
Date: Tue, 9 Aug 2011 19:16:39 +0200 (MEST)
In-Reply-To: <DB04A5B3-3F7C-4536-8EA4-633F9BBB4ACA@network-heretics.com> from "Keith Moore" at Aug 9, 11 12:04:56 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 17:16:33 -0000

Richard Kulawiec wrote:
> 
> I don't think it's a religious war: I think it's long since been
> demonstrated that RFC 2919 (and 2369) including List-Id are not only
> good ideas, but best practices, and that subject-line tags should
> be deprecated/avoided/discouraged, because they're just a kludge.
>  
> That is, this is an issue of technical merit, not arbitrary whim.
> So instead of bringing back the obsolete idea of subject-line tags, we
> should instead be encouraging (a) all IETF lists *not* to use them,

-2

List-Id: can be used to automatically archive EMails for mailing
list or other distributions which one reads only casually -- there
it saves manual work.

> but to
> use List-Id et.al. instead (b) all (relevant) mail software providers to
> support them and (c) all (relevant) mail server providers to support them.
> These mechanisms neatly solve a number of problems, and that better
> positions everyone to tackle those that remain.

If one intends to actually *process* close to all of the Emails hitting
one's inbox in near real time, then List-Id:, and any pre-sorting based
on it, will _always_ slow down processing (unless the MUA or the processing
is flawed).

Whereas a subject prefix significantly facilitates tracking of stuff
in a single large inbox.  I'm getting 300+/day Emails and try to read >95%
of it (my company internal Email is completely seperate at ~30/day, though).


-Martin

From nsb@guppylake.com  Tue Aug  9 11:30:16 2011
Return-Path: <nsb@guppylake.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BBC21F8BB1 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yM1hFREmeTRT for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:30:15 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 5032521F8B63 for <ietf@ietf.org>; Tue,  9 Aug 2011 11:30:15 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=UrV0i5C+oSgSHRW2k8pv+sptmyvdyhGDv3+qBTg21aQOEq7i9raRUcOhA5X0FnGbryUv59M9DPk4vClX6EmpCVYgvMhTVOTSyBXDRcHUjWpsY89YcidNcU9ldrccFpWF;
Received: from 184-202-16-37.pools.spcsdns.net ([184.202.16.37] helo=[192.168.0.197]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1Qqr4Y-0000ND-0e; Tue, 09 Aug 2011 14:30:38 -0400
Subject: Re: DKIM Signatures now being applied to IETF Email
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com>
Date: Tue, 9 Aug 2011 14:30:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E26526C8-E0F5-4F74-A18F-06AC13D8D359@guppylake.com>
References: <20110801225757.8527.qmail@joyce.lan> <C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Cc: John Levine <johnl@iecc.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 18:30:16 -0000

On Aug 1, 2011, Keith Moore wrote:

> Perhaps.  But it's difficult to escape the impression that this is =
another example of IETF failing to solve an important problem by =
focusing on a portion of the problem that's easy to solve, and ruling =
the difficult part out of scope for the time being.  Repeat as needed; =
you can always partition the remaining part of the problem again.
.....
> Does it follow, then, that the Right Thing to do is to avoid building =
any other parts of the system (even, say, the reputation service query =
protocol) until the easiest part is finished?

No extreme is likely to work, because this is essentially an =
optimization question for standards processes.	   We worry too little =
about the opportunity cost of the passage of time, so we fight =
time-consuming battles.  We should instead be trying to build an optimal =
pipeline of incremental progress in a generally positive direction, =
acknowledging inevitable mistakes along the way.

I'd like to view the IETF as a standards factory, with a certain optimal =
level of throughput that we're trying to achieve.  As with, say, a =
sausage factory, you don't just take in a single opinion, chop it up to =
bits, and deliver a snack-sized bit of RFC before moving on to process =
the next opinion.  The economic benefits of parallelism are so large =
that they dwarf all but the worst mistakes, so we accept the =
inevitability of a flawed process that lets a few bugs get through.  As =
a technologist I hate that(*), but it's true.   And it means that, if =
you can look back on a standard you worked on a few years ago and not =
have any regrets, you spent too much time on it.

So while we obviously need to focus on smallish, core chunks of =
technology like DKIM before devoting a lot of effort to building on top =
of them, we also need to start the latter before the former are =
completely finished.=20

If anything, we're late.  DKIM is almost a decade old.  It's pretty =
good, and we've long since reached diminishing returns.  There's plenty =
more to do.  It's time to move on.  -- Nathaniel

_____
(*) As a vegetarian I just feel smug. :-)



From cabo@tzi.org  Tue Aug  9 11:46:05 2011
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AADD21F8B13 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrXNjomEVbeK for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:46:05 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id B021521F8B08 for <ietf@ietf.org>; Tue,  9 Aug 2011 11:46:04 -0700 (PDT)
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 p79IkCMv021935; Tue, 9 Aug 2011 20:46:12 +0200 (CEST)
Received: from [192.168.217.105] (p5B3E722E.dip.t-dialin.net [91.62.114.46]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 046FC9D;  Tue,  9 Aug 2011 20:46:11 +0200 (CEST)
Subject: The fallacy of perfection (Re: DKIM Signatures now being applied to IETF Email)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <E26526C8-E0F5-4F74-A18F-06AC13D8D359@guppylake.com>
Date: Tue, 9 Aug 2011 20:46:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <67C78A3C-065C-444B-8F66-459F90804F5F@tzi.org>
References: <20110801225757.8527.qmail@joyce.lan> <C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com> <E26526C8-E0F5-4F74-A18F-06AC13D8D359@guppylake.com>
To: Nathaniel Borenstein <nsb@guppylake.com>
X-Mailer: Apple Mail (2.1084)
Cc: John Levine <johnl@iecc.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 18:46:05 -0000

On Aug 9, 2011, at 20:30, Nathaniel Borenstein wrote:

> We worry too little about the opportunity cost of the passage of time, =
so we fight time-consuming battles.  We should instead be trying to =
build an optimal pipeline of incremental progress in a generally =
positive direction, acknowledging inevitable mistakes along the way.

Nathaniel,

this (and the rest of your message) is probably the most profound =
observation I've heard about the IETF process for quite a while.

For another perspective on this, see section 2.7 "The fallacy of =
perfection" in "Garrulity and Fluff".
(http://www.iab.org/wp-content/IAB-uploads/2011/04/Bormann.pdf)

Gruesse, Carsten


From barryleiba.mailing.lists@gmail.com  Tue Aug  9 11:56:27 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46FAE21F8C3F for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.047
X-Spam-Level: 
X-Spam-Status: No, score=-103.047 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MbM3YaE0QYSL for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:56:26 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id A879521F88A0 for <ietf@ietf.org>; Tue,  9 Aug 2011 11:56:26 -0700 (PDT)
Received: by ywm21 with SMTP id 21so225818ywm.31 for <ietf@ietf.org>; Tue, 09 Aug 2011 11:56:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TJXefraecpOErLw5ZWB2WY6LqdLsc5tp8dzIZ/mm1YQ=; b=wOi59juzoAmxFBftAmgB51NgkFwu24BbUoP3Aeffh+zFE0cQBUPgTOOSonp6q5QWWX zujMABpMQqAUuWFT9/7LF5I/1IFsltOJQAIK18mO5d2k6tGvtFAKQFiXbQ93OCdbk9hK SxmHKjoDr+uVNSJLMRkf3FttqHamaw+mFEwKU=
MIME-Version: 1.0
Received: by 10.236.135.129 with SMTP id u1mr3786814yhi.246.1312916215608; Tue, 09 Aug 2011 11:56:55 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.181.13 with HTTP; Tue, 9 Aug 2011 11:56:55 -0700 (PDT)
In-Reply-To: <201108091716.p79HGdhL008452@fs4113.wdf.sap.corp>
References: <DB04A5B3-3F7C-4536-8EA4-633F9BBB4ACA@network-heretics.com> <201108091716.p79HGdhL008452@fs4113.wdf.sap.corp>
Date: Tue, 9 Aug 2011 14:56:55 -0400
X-Google-Sender-Auth: UBtsyQqny1EPjs99uVTCX9j_QcU
Message-ID: <CAC4RtVBso47fhsPJ6X0ja4Y0kn5fMoFFMk0cE3V7mJ4dhdNLuA@mail.gmail.com>
Subject: Re: subject_prefix on IETF Discuss?
From: Barry Leiba <barryleiba@computer.org>
To: mrex@sap.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 18:56:27 -0000

On Tue, Aug 9, 2011 at 1:16 PM, Martin Rex <mrex@sap.com> wrote:
> If one intends to actually *process* close to all of the Emails hitting
> one's inbox in near real time, then List-Id:, and any pre-sorting based
> on it, will _always_ slow down processing (unless the MUA or the processi=
ng
> is flawed).
>
> Whereas a subject prefix significantly facilitates tracking of stuff
> in a single large inbox. =A0I'm getting 300+/day Emails and try to read >=
95%
> of it (my company internal Email is completely seperate at ~30/day, thoug=
h).

This makes no sense to me, Martin.  Please explain why sorting based
on a subject prefix will work, while sorting based on a List-ID header
field will not.

Barry

From pfsinoz@gmail.com  Tue Aug  9 11:57:14 2011
Return-Path: <pfsinoz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F419211E80C3 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id niScq1foHc25 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 11:57:13 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 635C911E80A4 for <ietf@ietf.org>; Tue,  9 Aug 2011 11:57:13 -0700 (PDT)
Received: from Philip-MBP.local (unknown [80.187.205.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 454BEB66A0 for <ietf@ietf.org>; Tue,  9 Aug 2011 14:57:40 -0400 (EDT)
Message-ID: <4E41831E.9030209@gmail.com>
Date: Wed, 10 Aug 2011 04:57:34 +1000
From: Philip Smith <pfsinoz@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <a06240800ca6713e13df6@[10.31.201.42]>
In-Reply-To: <a06240800ca6713e13df6@[10.31.201.42]>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 18:57:14 -0000

Edward Lewis said the following on 10/08/11 02:52 :
> At 0:56 -0700 8/8/11, Ole Jacobsen wrote:
>>
>> We did APRICOT at this venue in 2002. Not a bad place for a
>> conference, but most certainly requires transportation to the hotels.
> 
> I was there too, for 10-14 days.  It was an experience I never forgot. 

While on the topic of QSNCC in Bangkok, I can contribute to the APRICOT
2002 experiences... Apart from hotels all being a long walk (there was
no subway in 2002, it was still being built), deploying wireless was a
challenge (or easy, depending on your point of view) as the centre had
been built specifically for a Governmental summit (perhaps ASEAN or
similar), so each hall was electromagnetically isolated. No leaky
wireless networks, but then a huge number of APs were needed. Which we
didn't realise in the site survey, not until turning up on the day to
deploy.

When APRICOT comes back to Bangkok in the future (it is a wonderful
conference/convention city), the subway will make the location much more
favourable, although I think the APIA Board will want to consider other
venues too in light of the previous experience with QSNCC.

philip
(APIA Board Chair)
--

From dean.willis@softarmor.com  Tue Aug  9 15:11:50 2011
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 773EA21F8B06 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 15:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.388
X-Spam-Level: 
X-Spam-Status: No, score=-103.388 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-WWAs6B0xvJ for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 15:11:50 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id D905521F8AFF for <ietf@ietf.org>; Tue,  9 Aug 2011 15:11:49 -0700 (PDT)
Received: by yxp4 with SMTP id 4so365940yxp.31 for <ietf@ietf.org>; Tue, 09 Aug 2011 15:12:19 -0700 (PDT)
Received: by 10.101.72.2 with SMTP id z2mr1719354ank.71.1312927939140; Tue, 09 Aug 2011 15:12:19 -0700 (PDT)
Received: from [192.168.2.143] (cpe-66-25-15-110.tx.res.rr.com [66.25.15.110]) by mx.google.com with ESMTPS id h15sm289364ank.39.2011.08.09.15.12.16 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 09 Aug 2011 15:12:18 -0700 (PDT)
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <4E40CD13.3020904@net-zen.net>
In-Reply-To: <4E40CD13.3020904@net-zen.net>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <E7FB3C1E-D298-4357-9965-8492AC758B42@softarmor.com>
Content-Transfer-Encoding: quoted-printable
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Queen Sirikit National Convention Center
Date: Tue, 9 Aug 2011 17:12:15 -0500
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 22:11:50 -0000

On Aug 9, 2011, at 1:00 AM, Glen Zorn wrote:

> On 8/8/2011 2:56 PM, Ole Jacobsen wrote:
>>=20
>>=20
>> Nothing is "a reasonable walk" when the average temperature is 32 C.
>> At least not for the "average" IETF attendee.
>=20
> Just to add a little perspective for the Celsius-challenged ;-), 32C =3D=

> 89.6F.  Warm, but not IMHO life-threatening, even for the sedentary =
;-).

Y'all come on down to Dallas. It was 39C while I was walking the dog =
last night, down from the daily peak of about 44C. We're looking forward =
to October, when the highs should drop to 32C. And the lows to around =
zero .... pack a sweater.

And yep, I'm probably a flabby, nigh-on-fiftyish average IETF attendee. =
We're tougher than you think, Ole!=20

On the other hand, 22 hours of air travel is pretty much close to fatal. =
Whatever happened to bunk beds on planes?=20

Couldn't we just rent a university building in Hawaii? That's sort of a =
midway point between everything. Classroom chairs can't be any worse =
than Hilton chairs, and it would be really handy to have built-in white =
boards for markup. Besides, I've always wanted to have a plenary in a =
football stadium. With cheerleaders.

--
Dean=

From mail@sabahattin-gucukoglu.com  Tue Aug  9 15:42:25 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F01221F86D2 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 15:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.586
X-Spam-Level: *
X-Spam-Status: No, score=1.586 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, MIME_QP_LONG_LINE=1.396, RCVD_IN_PBL=0.905]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gLOJ9P7ysTt1 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 15:42:24 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by ietfa.amsl.com (Postfix) with ESMTP id ABDF821F86B6 for <ietf@ietf.org>; Tue,  9 Aug 2011 15:42:24 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:33673) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S39B51> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Tue, 9 Aug 2011 23:42:53 +0100
Received: from [178.246.119.149] (178.246.119.149) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Tue, 09 Aug 2011 23:42:50 +0100
References: <DB04A5B3-3F7C-4536-8EA4-633F9BBB4ACA@network-heretics.com> <201108091716.p79HGdhL008452@fs4113.wdf.sap.corp> <CAC4RtVBso47fhsPJ6X0ja4Y0kn5fMoFFMk0cE3V7mJ4dhdNLuA@mail.gmail.com>
In-Reply-To: <CAC4RtVBso47fhsPJ6X0ja4Y0kn5fMoFFMk0cE3V7mJ4dhdNLuA@mail.gmail.com>
Mime-Version: 1.0 (iPhone Mail 8L1)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <A8D89C71-AFF3-4171-A146-FFFFEA1CD189@sabahattin-gucukoglu.com>
X-Mailer: iPhone Mail (8L1)
Subject: Re: subject_prefix on IETF Discuss?
Date: Wed, 10 Aug 2011 01:42:42 +0300
To: Barry Leiba <barryleiba@computer.org>
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1315521773.b735fd@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 22:42:25 -0000

n 9 Aug 2011, at 21:56, Barry Leiba <barryleiba@computer.org> wrote:

> On Tue, Aug 9, 2011 at 1:16 PM, Martin Rex <mrex@sap.com> wrote:
>> If one intends to actually *process* close to all of the Emails hitting
>> one's inbox in near real time, then List-Id:, and any pre-sorting based
>> on it, will _always_ slow down processing (unless the MUA or the processi=
ng
>> is flawed).
>>=20
>> Whereas a subject prefix significantly facilitates tracking of stuff
>> in a single large inbox.  I'm getting 300+/day Emails and try to read >95=
%
>> of it (my company internal Email is completely seperate at ~30/day, thoug=
h).
>=20
> This makes no sense to me, Martin.  Please explain why sorting based
> on a subject prefix will work, while sorting based on a List-ID header
> field will not.
>=20
I think the idea is that having the Subject prefix will allow sorting by vis=
ual inspection of one folder - the Inbox - where List-id will not.  I'm guil=
ty of that habit, too, I won't deny it.  But this is a  red herring - of cou=
rse, if you can sort matching messages into a folder, you can visually tag t=
hem, too.  And you can sort them using headers not usually displayed as with=
 those that are.  Using an existing header that's already displayed in an in=
dex is just a hack, (from majordomo days, not surprisingly, and meant as an a=
id to broken or ineffectual mail software) and the trick is to upgrade your M=
UA and list software, or make do with list folders otherwise.

Cheers,
Sabahattin

From mary.ietf.barnes@gmail.com  Tue Aug  9 16:04:38 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF5AA21F8AA8 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 16:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.935
X-Spam-Level: 
X-Spam-Status: No, score=-102.935 tagged_above=-999 required=5 tests=[AWL=-0.238, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, MANGLED_LIST=2.3, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjJixrOsC72O for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 16:04:35 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id F3A0721F8A80 for <ietf@ietf.org>; Tue,  9 Aug 2011 16:04:34 -0700 (PDT)
Received: by vxi29 with SMTP id 29so506046vxi.31 for <ietf@ietf.org>; Tue, 09 Aug 2011 16:05:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=Im+oSE66cepC1IWrXfmNQPvZaRxw+A+JFl5LiOHFt0c=; b=gigUZS/HRSjxI2fQOymwCWcWRIDkAa+Zz7IfJHXailj7/6qyvcuzrkWL208sf9e8kP i8DbR4Y4T+buEI8AaxM27Eq+aKnPrJw98heHI4iB68FzDjqPwf9DykATUIAQ2XyLnMwo bbbswXNci/l042DZIrEfQDQ+4K6w4RXKZTKOw=
MIME-Version: 1.0
Received: by 10.52.21.65 with SMTP id t1mr7848869vde.183.1312931104593; Tue, 09 Aug 2011 16:05:04 -0700 (PDT)
Received: by 10.52.167.34 with HTTP; Tue, 9 Aug 2011 16:05:04 -0700 (PDT)
Date: Tue, 9 Aug 2011 18:05:04 -0500
Message-ID: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com>
Subject: Gen-ART Review: Last Call <draft-ietf-p2psip-base-17.txt>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-p2psip-base.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=20cf307d05a61a974404aa1a986d
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 23:04:38 -0000

--20cf307d05a61a974404aa1a986d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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

Sorry for the delay, but a two week IETF-LC for a 150 page document two
weeks before an IETF meeting virtually ensures that the document  won't be
carefully reviewed by the community and that directorate reviews will are
late ;)   While this review was done specifically on the -17, I have
reviewed the diff and these comments still apply to the -18.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Document: draft-ietf-p2psip-base-17
Reviewer:  Mary Barnes
Review Date:  9 August  2011
IETF LC End Date: 22 July 2011

Summary: Not Ready.

Comments:
----------------
The document is very a dense (with detailed technical information) and long
(150 page) specification for a Peer-to-peer signaling protocol.  While the
overall technical functionality seems fairly correct and thoroughly
specified, the primary issue is a tremendous lack of normative language in
the main body of the document.  Non-inclusive details of such are included
below.

Major Issues:
-------------------

General:
--There is a fair number of cases where normative language should be used.
 I have detailed some (but certainly not all)  instances where it is lackin=
g
with proposed rewording.  I have also noted cases where it is used (lower
case) where it could be confused with needing normative language and where
it isn't necessary and there are some cases where it's just not clear. I
consider these major since it can impact interoperability and could lead
developers to not implement key functionality.

--There is also little or no normative language for the majority of the
elements in the structures - i.e., the reader has to assume which elements
are mandatory and which are optional and it's not always clear.   For
example, rather than saying "Field x contains blah", it should say "Field x
MUST contain blah" and rather than "The contents of the message will be x, =
y
and z", it should say something like "The message MUST (or SHOULD) contain
x, y and z".  I have not detailed the places where this is necessary in mos=
t
cases.  The authors should review the detailed definition for each of the
messages.

--The message names are used inconsistently.  The IANA registry has the
message codes all lower case.  There are places in the examples and the bod=
y
of the document where the _req part is missing, there is no "_", the first
letters are Upper case, etc.  The messages are also used in a general sense
- e.g., "MUST perform an Attach", which should really be stated as "MUST
send an attach_req message)

Major - Detailed:

- Sections 3.2.1, 3.2.2 and 3.3: lots of changes needed to reword using
normative language.

- Section 3.4, last paragraph: Needs to be reworded normatively and more
precisely. It's really not clear to me what the required behavior is as it
first says it needs to (which I'm not sure is a SHOULD or is REQUIRED to)
maintain connections to all the peers near and enough others.., but how muc=
h
is "enough".   Also, what is meant by the "specified link set" - is that
referring to all the nearby peers or the peers+enough others?  Or is this
more clearly (and normatively) specified elsewhere, such that a reference
could be added.

- Section 4.2: needs normative language - i.e.:
--"Each Usage needs to =85" ->  "Each Usage MUST=85"

- Section 5.1.1: Bullet items need normative language
-- 1st bullet: It's also  not clear what the its are in "it passes it up".
 I think it should be "the node passes the message up to the upper layers".
  However, this probably needs to be normative language - i.e., "the node
MUST pass the message to the upper layers".  The same applies to the third
bullet.
--bullet 2:  "the message is destined for this node and is passed up=85" ->
"the message is destined for this node and MUST be passed=85.,

- Section 5.1.2:
-- Paragraphs 5, 6, 7 and 8 need to be reworded to have normative
statements.
-- Last paragraph (9) mixes normative text with in an example. The normativ=
e
text needs to be separated from the example - e.g., split some of the
sentences into the normative behavior and then the example.

-Section 5.2.1 is totally inconsistent with the use of normative language
(i.e., lower case occurrences and lack of KEY words) - shouldn't the
following be normative statements something like the following:
-- First paragraph:
---First sentence:  "a node constructs" -> "a node MUST construct".
--- 3rd sentence: "resulting message will use the normal overlay routing" -=
>
"resulting message MUST use the normal overlay routing"
--- 4th sentence: "The node can also" ->  "The node MAY also"
-- Third paragraph:
--- 3rd sentence: "a single request can also" -> "a single request MAY also=
"
-- Fourth paragraph:
--- 1st sentence: this could be interpreted as normative:  "Because message=
s
may" ->  "Because messages can"
--- 3rd sentence:  "the request is retransmitted" ->  "the request MUST be
retransmitted"

-Section 5.3.2:
-- General: some of the contents of the structure have normative language
and others don't.  There is some normative behavior defined for these field=
s
later, so perhaps adding section references as you do for some fields would
be helpful.

For example:
--"overlay": shouldn't this be normative:  "the overlay name is hashed with
SHA-1" -> "the overlay name MUST be hashed with SHA-1"
--"destination_list": seems like some of this should be normative?

-Section 5.3.2.1:
--1st paragraph: shouldn't this be normative?
"the configuration document has a sequence number" ->  "the configuration
document MUST contain a sequence number"
-- 1st paragraph, last sentence: "may"  -> "can"

-Section 5.3.2.2:
--Paragraph after the 1st structure:  Shouldn't this be stated normatively
since it is described how the structure MUST be handled depending upon the
contents?
--Paragraph after second structure, suggest the following changes:
---"the generation counters should" ->  "the generation counters SHOULD"
---"An implementation could use.." -> "An implementation MAY use=85"
---"the node confirms that the generation counter matches" -> "the node MUS=
T
confirm that the generation counter matches"
---"If it does not match, it is silently dropped." -> "If it does not match=
,
it MUST be silently dropped."

-Section 5.3.3.1:
--1st para: "a request returns" -> "a request MUST return"
--1st para: "then the message code is the response code that matches the
request" ->
"then the message code MUST be set to the response code that matches the
request"
--2nd para: "message code is set" ->  "message code MUST be set"

-Section 5.3.4 - needs normative language:
--1st paragraph after GenericCertificate structure:
---"All signatures are formatted" -> "Alls signatures MUST be formatted"
---"The input structure=85varies.." ->  "The input structure =85 MAY vary=
=85"

-Section 5.4.1: "need to be described" -> "MUST be described"

-Section 5.4.2-Section 7.  These sections need to be carefully reviewed and
updated appropriately with normative text.  [ I have marks up for pages
55-102 where normative language is needed if someone wants those scanned an=
d
forwarded - I'm just too lazy to type them all out.]

- Section 8:  There is only one actual normative word used in this section!
 There is a lc "should" that ought to be "SHOULD".  I don't know if the
authors assumed that the normative language in TURN was sufficient, but I d=
o
not believe that is the case as it leaves the normative behavior to be
inferred by the reader/implementor. Rather than rewrite the whole section
myself, the authors need to review carefully. For example, there are "needs
to", which likely are really and lots of present tense statements (e.g.,
"The address of the peer is stored=85"), which ought to be MUSTs or SHOULDs=
.

- Section 9.2:  seems like this needs normative language. Suggest the
following:
OLD:
   For this Chord based topology plugin, the size of the Resource-ID is
   128 bits.  The hash of a Resource-ID is computed using SHA-1
   [RFC3174]then truncating the SHA-1 result to the most significant 128
   bits.
NEW:
   For Chord-RELOAD, the size of the Resource-ID MUST be
   128 bits.  The hash of a Resource-ID MUST be computed using SHA-1
   [RFC3174].  The SHA-1 result MUST be truncated to the most significant
   128 bits.

- Section 9.3: Needs normative language.
OLD:
   If a peer is not responsible for a Resource-ID k, but is directly
   connected to a node with Node-ID k, then it routes the message to
   that node.  Otherwise, it routes the request to the peer in the
   routing table that has the largest Node-ID that is in the interval
   between the peer and k.  If no such node is found, it finds the
   smallest Node-Id that is greater than k and routes the message to
   that node.
NEW:
   If a peer is not responsible for a Resource-ID k, but is directly
   connected to a node with Node-ID k, then it MUST route the message to
   that node.  Otherwise, it MUST route the request to the peer in the
   routing table that has the largest Node-ID that is in the interval
   between the peer and k.  If no such node is found, it MUST find the
   smallest Node-Id that is greater than k and MUST route the message to
   that node.

- Section 9.4: Needs normative language.

- Section 9.5: While this section does have a fair amount of normative
language, it is still lacking in a few cases:
--Item 2.:  "should" -> "SHOULD"
--Item 5.:  "The AP sends the response=85" -> "The AP MUST send the
response=85"
--1st paragraph after list: "=85can directly connect=85" -> "MAY directly
connect"
--2nd paragraph after list: "it can still populate" -> "it MAY still
populate"
--2nd paragraph after list: the description of the use of PING should be
reworded with normative language (I'll leave that exercise to the authors)
--3rd paragraph after the list:  "JP simply sends" -> "JP MUST send"

- Section 9.7.1:
--1st para:  ".., it then sends=85" -> ".., it then MUST send =85"
--3rd para: needs normative language
OLD:
   In no event does
   an attempt to reestablish connectivity with a lost neighbor allow the
   peer to remain in the neighbor table.
NEW:
   In the case of
   an attempt to reestablish connectivity with a lost neighbor, the peer
   MUST not remain in the neighbor table.
OR:
   In the case of
   an attempt to reestablish connectivity with a lost neighbor, the peer
   MUST be removed from the neighbor table.
-- 4th para: "should" -> "SHOULD" (2 cases),  "use Pings" -> "MUST use
Pings"

-Section 9.7.2:
--1st para:  "..the failed peer are removed.." -> "=85the failed peer MUST =
be
removed.."
--2nd para:  "=85the peer initiates=85" -> "=85the peer MUST initiate.."

-Section 9.7.3:
--1st para after list:  "is needed" -> "is REQUIRED"
--3rd para after list:  "the peer sends an Update" -> "the peer MUST send a=
n
Update"

-Section 9.7.4.4:  Needs a scrub for normative language

-Section 9.9: Needs a scrub for normative language.

-Section 10.1: General: Needs a lot of work to be specified using normative
language.  The majority of the configuration elements are not specified
using normative language - for example, terms such as permitted, allowed,
valid are used in statements rather than normative language
or they are indicative of the need for normative language.  A specific
example is in the definition for "clients-permitted":

OLD:
      This element represents whether clients are
      permitted or whether all nodes must be peers.  If it is set to
      "true" or absent, this indicates that clients are permitted.  If
      it is set to "false" then nodes are not allowed to remain clients
      after the initial join.

NEW:
      This element represents whether clients are
      permitted or whether all nodes need to be peers.  If clients
      are permitted, the element MUST be set to "true" or absent.
      If the nodes are not allowed to remain clients after the
      initial join, the element MUST be set to "false".

--Section 10.1 - 4th para after the element list states that "All of the no=
n
optional values MUST be provided".  However, the list of elements in the
previous paragraph are not specifically identified as non optional.  I thin=
k
the first 3 are mandatory.  So, I would suggest to re-word the 3rd paragrap=
h
as follows and delete the 1st sentence in the 4th paragraph noted above:
OLD:
   In addition, the kind element contains the following elements:
   max-count:  the maximum number of values which members of the overlay
      must support.
   data-model:  the data model to be used.
   max-size:  the maximum size of individual values.
   access-control:  the access control model to be used.
   max-node-multiple:  This is optional and only used when the access
      control is NODE-MULTIPLE.  This indicates the maximum value for
      the i counter.  This is an integer greater than 0.

NEW:
   In addition, the kind element MUST contain the following elements:
   max-count:  the maximum number of values which members of the overlay
      must support.
   data-model:  the data model to be used.
   max-size:  the maximum size of individual values.
   access-control:  the access control model to be used.

   The kind element MAY also contain the following element:
   max-node-multiple:  if the access control is NODE-MULTIPLE,
      this element MAY be included. This indicates the maximum value for
      the i counter.  It MUST be an integer greater than 0.

--Section 10.1, next to last para: There's no normative language, but it
seems there should be since it is specifying specification computations and
encoding that I believe are required.

- Section 10.2:  Needs more normative language:

-- 2nd para:
OLD: This value is provided by the user or some other out of band
     provisioning mechanism.

NEW: This value MUST be provided by the user or some other out of band
     provisioning mechanism."

-- 3rd para:
OLD:
   Once an address and URL for the configuration server is determined,
   the peer forms an HTTPS connection to that IP address.
NEW:
   Once an address and URL for the configuration server is determined,
   the peer MUST form an HTTPS connection to that IP address.

-- 4th para:  "which replaces" ->  "which MUST replace"

-- 5th para:  "nodes obtain the" -> "nodes MUST obtain the"

- Section 10.3:
-- 3rd para:  "is performed" -> "MUST be performed".
-- 3rd para: Bullets need to be modified to normative.
-- 4th para: "the certificate contains" -> "the certificate MUST contain"
-- para after 2nd set of bullets:  needs normative language.
-- 2nd para after 2nd set of bullets:  "The node then reads=85" ->  "The no=
de
MUST then use=85"

- Section 10.5:
--Second para: "the joining node first forms" -> "the joining node MUST
first form"
--3rd para:  text uses the phrase "it can note the Node-ID in the response
and use this Node-ID to start sending requests".  It's not clear whether th=
e
use of the Node-ID is a MAY or a MUST.

- Section 12. I'm assuming that the security directorate has reviewed this
in detail, thus my focus in reviewing this section was on general
understanding. The biggest issues is that there is NO normative language at
all in the security section.  As in other sections, terms like "need",
"are/is used/sent, etc.",  "ensure", lower case reserved words rather than
upper case, etc. are used when normative language ought to have been used.


- Section 13. IANA Registrations:
- General: there seem to be several registries for which the
usage/requirement is unclear as there's no mention of such in the body of
the document.  In general, references to the sections in the document
describing the information included in the registries would be more than
helpful.

- Section 13.5: Creates a RELOAD Application Registry, but the use and need
for such isn't described elsewhere in the document.

- Section 13.12. Forwarding Options Registry. SEction 5.3.2.3 seems to
define three flags for the Forwarding options type, so it's not clear to me
why this registry has just "invalid" and "reserved"


- Section 13.15:  Defines/registers a RELOAD URI schema but there is no
mention of this URI anywhere else in the document.  In what context is it
used?


Minor  Issues:
---------------------

- Section 1.2.1, 2nd paragraph: I don't understand the example as to why a
single application requires multiple usages - i.e, why voicemail?  Isn't th=
e
intent to say that an application might need to use both SIP and XMPP -
i.e., you wouldn't define a "usage" for an application, would you?

- Section 2. Some of the definitions use terms that are not yet defined, so
that's not particularly helpful - i.e,. Attach and Update are used. In some
cases (e.g., Connection Table), you could just delete the statement with th=
e
reference.

- Section 3.3, last paragraph.  Add a reference to 5.4.2.4  after
"RouteQuery method"

- Section 5.1: "If any of these are incorrect=85"  - need to specify what
qualifies as "incorrect" - is it wrong formatting, invalid header field
value, etc.?

- Section 5.1.2:
--1st paragraph: I have no idea what the "other three cases" references.

- Section 5.2: "may be configured" -> "can be configured",  "alternative
routing algorithms may be selected" -> "alternative routing algorithms MAY
be selected"

- Section 5.3:  The three parts of the messages are listed and the last
sentence says that "The following sections describe the format of each part
of the message", but there are 4 sub-sections in 5.3, with the first sectio=
n
NOT describing one of the three parts of the messages.  I suggest to strike
that last sentence and just put references to the sections in the list item=
s
for each of the three messages.

-Section 5.3.3:
--"critical" description:  "Whether this extension must be.." "Whether this
extension needs to be=85"

-Section 5.3.4:  1st para after certificate structure:  "may contain" ->
"MAY contain"

-Section 5.5: It would be helpful to highlight that foundation, priority an=
d
type are based on ICE, in particular since ICE is not discussed until the
subsequent section - e.g., "the foundation production" -> "the ICE
foundation production".

- Section 5.6:
-- The last three paragraphs are confusing.
---In particular, it's not clear what algorithms are being referenced in
this sentence:
  "We will first define each of these algorithms, then
   define overlay link protocols that use them."
--- In the note paragraph, I believe "These protocols have been chosen=85" =
is
referring to the three overlay link protocols supported by RELOAD per this
document.
---The Note to implementors paragraph seems out of context
--- Per my next comment, I suggest to move the detailed discussion of futur=
e
overlay link protocols to the appendix, so some of this text may be relevan=
t
only to that.

-Section 5.6.1:  I suggest that the sub-sections in this section be moved t=
o
an appendix and a reference to such be added.

-Section 5.6.3.1.1, next to the last paragraph:
"when a link may be failing" -> "when a link might be failing"

- Section 9.1: While this is an overview, it seems to me that some of this
is describing normative behavior (that I don't see specified else).  Per th=
e
general comment, I would reword the first sentence as follows:
OLD:
   The algorithm described here is a modified version of the Chord
   algorithm.
NEW:
    The algorithm described here, Chord-RELOAD is a modified version
    of the Chord algorithm.

- Section 10.3, 1st para:  "required" -> "REQUIRED"

- Section 10.3.1, last sentence: "must"  -> "MUST"

- Section 10.4, 1st para, last sentence: "should use" -> "SHOULD use"

- Section 11 - examples:
--General - there are no detailed messages shown anywhere for the examples.
There should be at least one, in particular given the comment above about
the RELOAD URI that is registered, but not mentioned anywhere else in the
document.
--first example (see my nit below about the examples not being numbered or
labeled in any way):  The third sentence says that "It gets routed to the
admitting peer (AP), yet the flow shows that the message first gets routed
to the PP and then onto AP. It would be helpful if that were clarified.
-  Also (general), the text mentions the use of ICE.  It's not clear to me
exactly where in the flow that happens - it would be good to annotate such
(i.e., in a similar manner as the TLS is illustrated).
- next to the last example (text on page 131, diagram on page 132): I'm
quite confused as the text states that JP has received an update from AP an=
d
thus now knows APs predecessors, which are also JP's predecessors, so JP
Attaches to them. However, the diagram does not show JP getting an Update
from AP and it shows JP doing Updates to PPP and PP rather than Attaches (a=
s
the text suggests).

- Section 13.10. Overlay link types: These specific string types are not
used elsewhere in the document.  Suggest that a reference to 5.6 be added
and these particular strings be included in parenthesis after the items in
the list.


- Section 13.16, Security considerations portion:
-- The first sentence doesn't make sense. Did you mean?
   "This media type is typically not used to
   transport information that needs to be kept confidential,
   however, there are cases where the integrity of the information is
   important."
-- "then the contents of the file need to be=85" -> "then the contents of t=
he
file MUST be =85"



Nits:
-----
- General: kind is sometimes "Kind" and sometimes "kind".  The former is
more readable and highlights it as a reserved word.

- Section 2.
--General: It would be helpful if the terms were alphabetized.
--Node: "We use the term "Node" to refer to =85" -> "Refers to =85"

- Section 3.2:
-- 2nd para, last sentence:  "refer such" -> "refer to such"
-- 3rd para, 1st sentence:  "concept" -> "entity"

- Section 4.1.4, 4th paragraph: I'm still not getting the applicability of
voicemail as a RELOAD Kind (per the reference also in section 1.2.1).  I
guess you are talking about a voicemail message (in this case) and a server
or application in section 1.2.1?   Voicemail just does not seem like an
obvious example to me.

- Section 5.1.1, last bullet:  "In that case,=85" ->  "In the latter case, =
=85"

- Section 5.1.2:
-- 2nd para:  "arrange" -> "ensure",  "This may be arranged" -> "This can b=
e
arranged=85"
-- 3rd para (1st after bullets): It's not clear that A=85E is a set of orde=
red
nodes in the example. I would suggest to reword as:
OLD:
   As an example of the first strategy, if node D
NEW:
  Consider an example with nodes A, B, C, D and E, respectively.  If
  node D=85.

- Section 5.3.1.1: First two sentences can be reworded more succinctly -
you're not really providing definitions here, put rather describing the
the syntax for and providing examples illustrative of the presentation
language.

OLD:
   The following definitions are used throughout RELOAD and so are
   defined here.  They also provide a convenient introduction to how to
   read the presentation language.
NEW:
   This section provides an introduction to the presentation language
   used throughout RELOAD.

- Section 5.3.3.1: Error_Data_Too_Old is duplicated.

- Section 5.5.1.6: Add references for SCTP and DCCP.

- Section 6.4.1.3:  The reference to "this Version" is superfluous. Propose
the following change:
OLD:
   This version of RELOAD (unlike previous versions) does not have an
   explicit Remove operation.
NEW:
   RELOAD does not have an explicit Remove operation.

- Section 9: General. The first sentence states that the algorithm defined
here is referred to as "chord-reload", however, subsequent sections don't
seem to use that term.  It would be more clear if that term was used. And,
really, it would be more consistent to use the term Chord-RELOAD. However,
this should also be consistent with the IANA-Registration which has
CHORD-RELOAD.

- Section 9.7.4.3, 3rd para:
-- Remove "Note to implementers".  Text already highlights that the text is
specific to implementations.
-- "may be found" -> "can be found"

- Section 9.8:  "For this topology plugin" -> "For Chord-RELOAD"

- Section 10.2, 2nd para:  "determines" -> "determining"

- Section 11:
- General: there are no labels for any of the call flows, so it's not alway=
s
clear what the text is referring to.  In general, I think the text precedes
the flow.
- "abbreviation" -> "abbreviations"

- Section 13.16:
--Interoperability considerations:  "knows" -> "known"

- Section 14: "provied" -> "provided"

- Appendix C: Delete now - it's totally useless as is.

--20cf307d05a61a974404aa1a986d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div><div><br></div><div>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://wik=
i.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/a=
rea/gen/trac/wiki/GenArtfaq</a>&gt;.</div>
<div><br></div><div>Sorry for the delay, but a two week IETF-LC for a 150 p=
age document two weeks before an IETF meeting virtually ensures that the do=
cument =A0won&#39;t be carefully reviewed by the community and that directo=
rate reviews will are late ;) =A0 While this review was done specifically o=
n the -17, I have reviewed the diff and these comments still apply to the -=
18.</div>
<div><br></div><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D</div><div><br></div><div>Document: draft-ietf-p2psip-base-17</div=
><div>Reviewer: =A0Mary Barnes=A0</div><div>Review Date: =A09 August =A0201=
1</div>
<div>IETF LC End Date: 22 July 2011</div><div><br></div><div>Summary: Not R=
eady. =A0</div><div><br></div><div>Comments:</div><div>----------------</di=
v><div>The document is very a dense (with detailed technical information) a=
nd long (150 page) specification for a Peer-to-peer signaling protocol. =A0=
While the overall technical functionality seems fairly correct and thorough=
ly specified, the primary issue is a tremendous lack of normative language =
in the main body of the document. =A0Non-inclusive details of such are incl=
uded below. =A0</div>
<div><br></div><div>Major Issues:</div><div>-------------------</div><div><=
br></div><div>General:=A0</div><div>--There is a fair number of cases where=
 normative language should be used. =A0I have detailed some (but certainly =
not all) =A0instances where it is lacking with proposed rewording. =A0I hav=
e also noted cases where it is used (lower case) where it could be confused=
 with needing normative language and where it isn&#39;t necessary and there=
 are some cases where it&#39;s just not clear. I consider these major since=
 it can impact interoperability and could lead developers to not implement =
key functionality. =A0</div>
<div><br></div><div>--There is also little or no normative language for the=
 majority of the elements in the structures - i.e., the reader has to assum=
e which elements are mandatory and which are optional and it&#39;s not alwa=
ys clear. =A0 For example, rather than saying &quot;Field x contains blah&q=
uot;, it should say &quot;Field x MUST contain blah&quot; and rather than &=
quot;The contents of the message will be x, y and z&quot;, it should say so=
mething like &quot;The message MUST (or SHOULD) contain x, y and z&quot;. =
=A0I have not detailed the places where this is necessary in most cases. =
=A0The authors should review the detailed definition for each of the messag=
es.=A0</div>
<div><br></div><div>--The message names are used inconsistently. =A0The IAN=
A registry has the message codes all lower case. =A0There are places in the=
 examples and the body of the document where the _req part is missing, ther=
e is no &quot;_&quot;, the first letters are Upper case, etc. =A0The messag=
es are also used in a general sense - e.g., &quot;MUST perform an Attach&qu=
ot;, which should really be stated as &quot;MUST send an attach_req message=
)</div>
<div><br></div><div>Major - Detailed:</div><div><br></div><div>- Sections 3=
.2.1, 3.2.2 and 3.3: lots of changes needed to reword using normative langu=
age. =A0</div><div><br></div><div>- Section 3.4, last paragraph: Needs to b=
e reworded normatively and more precisely. It&#39;s really not clear to me =
what the required behavior is as it first says it needs to (which I&#39;m n=
ot sure is a SHOULD or is REQUIRED to) maintain connections to all the peer=
s near and enough others.., but how much is &quot;enough&quot;. =A0 Also, w=
hat is meant by the &quot;specified link set&quot; - is that referring to a=
ll the nearby peers or the peers+enough others? =A0Or is this more clearly =
(and normatively) specified elsewhere, such that a reference could be added=
. =A0</div>
<div><br></div><div>- Section 4.2: needs normative language - i.e.:</div><d=
iv>--&quot;Each Usage needs to =85&quot; -&gt; =A0&quot;Each Usage MUST=85&=
quot;</div><div><br></div><div>- Section 5.1.1: Bullet items need normative=
 language</div>
<div>-- 1st bullet: It&#39;s also =A0not clear what the its are in &quot;it=
 passes it up&quot;. =A0I think it should be &quot;the node passes the mess=
age up to the upper layers&quot;. =A0 However, this probably needs to be no=
rmative language - i.e., &quot;the node MUST pass the message to the upper =
layers&quot;. =A0The same applies to the third bullet.=A0</div>
<div>--bullet 2: =A0&quot;the message is destined for this node and is pass=
ed up=85&quot; -&gt; &quot;the message is destined for this node and MUST b=
e passed=85.,=A0</div><div><br></div><div>- Section 5.1.2:</div><div>-- Par=
agraphs 5, 6, 7 and 8 need to be reworded to have normative statements.=A0<=
/div>
<div>-- Last paragraph (9) mixes normative text with in an example. The nor=
mative text needs to be separated from the example - e.g., split some of th=
e sentences into the normative behavior and then the example.=A0</div><div>
<br></div><div>-Section 5.2.1 is totally inconsistent with the use of norma=
tive language (i.e., lower case occurrences and lack of KEY words) - should=
n&#39;t the following be normative statements something like the following:=
=A0</div>
<div>-- First paragraph:</div><div>---First sentence: =A0&quot;a node const=
ructs&quot; -&gt; &quot;a node MUST construct&quot;.</div><div>--- 3rd sent=
ence: &quot;resulting message will use the normal overlay routing&quot; -&g=
t; &quot;resulting message MUST use the normal overlay routing&quot;</div>
<div>--- 4th sentence: &quot;The node can also&quot; -&gt; =A0&quot;The nod=
e MAY also&quot;</div><div>-- Third paragraph:=A0</div><div>--- 3rd sentenc=
e: &quot;a single request can also&quot; -&gt; &quot;a single request MAY a=
lso&quot;</div>
<div>-- Fourth paragraph:</div><div>--- 1st sentence: this could be interpr=
eted as normative: =A0&quot;Because messages may&quot; -&gt; =A0&quot;Becau=
se messages can&quot;</div><div>--- 3rd sentence: =A0&quot;the request is r=
etransmitted&quot; -&gt; =A0&quot;the request MUST be retransmitted&quot;</=
div>
<div><br></div><div>-Section 5.3.2:=A0</div><div>-- General: some of the co=
ntents of the structure have normative language and others don&#39;t. =A0Th=
ere is some normative behavior defined for these fields later, so perhaps a=
dding section references as you do for some fields would be helpful. =A0</d=
iv>
<div><br></div><div>For example:=A0</div><div>--&quot;overlay&quot;: should=
n&#39;t this be normative: =A0&quot;the overlay name is hashed with SHA-1&q=
uot; -&gt; &quot;the overlay name MUST be hashed with SHA-1&quot;</div><div=
>
--&quot;destination_list&quot;: seems like some of this should be normative=
?=A0</div><div><br></div><div>-Section <a href=3D"http://5.3.2.1">5.3.2.1</=
a>:</div><div>--1st paragraph: shouldn&#39;t this be normative?=A0</div><di=
v>
&quot;the configuration document has a sequence number&quot; -&gt; =A0&quot=
;the configuration document MUST contain a sequence number&quot;</div><div>=
-- 1st paragraph, last sentence: &quot;may&quot; =A0-&gt; &quot;can&quot;=
=A0</div>
<div><br></div><div>-Section <a href=3D"http://5.3.2.2">5.3.2.2</a>:</div><=
div>--Paragraph after the 1st structure: =A0Shouldn&#39;t this be stated no=
rmatively since it is described how the structure MUST be handled depending=
 upon the contents? =A0</div>
<div>--Paragraph after second structure, suggest the following changes:</di=
v><div>---&quot;the generation counters should&quot; -&gt; =A0&quot;the gen=
eration counters SHOULD&quot;</div><div>---&quot;An implementation could us=
e..&quot; -&gt; &quot;An implementation MAY use=85&quot;</div>
<div>---&quot;the node confirms that the generation counter matches&quot; -=
&gt; &quot;the node MUST confirm that the generation counter matches&quot;<=
/div><div>---&quot;If it does not match, it is silently dropped.&quot; -&gt=
; &quot;If it does not match, it MUST be silently dropped.&quot;</div>
<div><br></div><div>-Section <a href=3D"http://5.3.3.1">5.3.3.1</a>:</div><=
div>--1st para: &quot;a request returns&quot; -&gt; &quot;a request MUST re=
turn&quot;=A0</div><div>--1st para: &quot;then the message code is the resp=
onse code that matches the request&quot; -&gt;=A0</div>
<div>&quot;then the message code MUST be set to the response code that matc=
hes the request&quot;</div><div>--2nd para: &quot;message code is set&quot;=
 -&gt; =A0&quot;message code MUST be set&quot;</div><div><br></div><div>-Se=
ction 5.3.4 - needs normative language:</div>
<div>--1st paragraph after GenericCertificate structure:</div><div>---&quot=
;All signatures are formatted&quot; -&gt; &quot;Alls signatures MUST be for=
matted&quot;</div><div>---&quot;The input structure=85varies..&quot; -&gt; =
=A0&quot;The input structure =85 MAY vary=85&quot;</div>
<div><br></div><div>-Section 5.4.1: &quot;need to be described&quot; -&gt; =
&quot;MUST be described&quot;=A0</div><div><br></div><div>-Section 5.4.2-Se=
ction 7. =A0These sections need to be carefully reviewed and updated approp=
riately with normative text. =A0[ I have marks up for pages 55-102 where no=
rmative language is needed if someone wants those scanned and forwarded - I=
&#39;m just too lazy to type them all out.]=A0</div>
<div><br></div><div>- Section 8: =A0There is only one actual normative word=
 used in this section! =A0There is a lc &quot;should&quot; that ought to be=
 &quot;SHOULD&quot;. =A0I don&#39;t know if the authors assumed that the no=
rmative language in TURN was sufficient, but I do not believe that is the c=
ase as it leaves the normative behavior to be inferred by the reader/implem=
entor. Rather than rewrite the whole section myself, the authors need to re=
view carefully. For example, there are &quot;needs to&quot;, which likely a=
re really and lots of present tense statements (e.g., &quot;The address of =
the peer is stored=85&quot;), which ought to be MUSTs or SHOULDs.</div>
<div><br></div><div>- Section 9.2: =A0seems like this needs normative langu=
age. Suggest the following:</div><div>OLD:</div><div>=A0=A0 For this Chord =
based topology plugin, the size of the Resource-ID is</div><div>=A0=A0 128 =
bits. =A0The hash of a Resource-ID is computed using SHA-1</div>
<div>=A0=A0 [RFC3174]then truncating the SHA-1 result to the most significa=
nt 128</div><div>=A0=A0 bits.</div><div>NEW:</div><div>=A0=A0 For Chord-REL=
OAD, the size of the Resource-ID MUST be=A0</div><div>=A0=A0 128 bits. =A0T=
he hash of a Resource-ID MUST be computed using SHA-1</div>
<div>=A0=A0 [RFC3174]. =A0The SHA-1 result MUST be truncated to the most si=
gnificant=A0</div><div>=A0=A0 128 bits.</div><div><br></div><div>- Section =
9.3: Needs normative language.=A0</div><div>OLD:=A0</div><div>=A0=A0 If a p=
eer is not responsible for a Resource-ID k, but is directly</div>
<div>=A0=A0 connected to a node with Node-ID k, then it routes the message =
to</div><div>=A0=A0 that node. =A0Otherwise, it routes the request to the p=
eer in the</div><div>=A0=A0 routing table that has the largest Node-ID that=
 is in the interval</div>
<div>=A0=A0 between the peer and k. =A0If no such node is found, it finds t=
he</div><div>=A0=A0 smallest Node-Id that is greater than k and routes the =
message to</div><div>=A0=A0 that node.</div><div>NEW:=A0</div><div>=A0=A0 I=
f a peer is not responsible for a Resource-ID k, but is directly</div>
<div>=A0=A0 connected to a node with Node-ID k, then it MUST route the mess=
age to</div><div>=A0=A0 that node. =A0Otherwise, it MUST route the request =
to the peer in the</div><div>=A0=A0 routing table that has the largest Node=
-ID that is in the interval</div>
<div>=A0=A0 between the peer and k. =A0If no such node is found, it MUST fi=
nd the</div><div>=A0=A0 smallest Node-Id that is greater than k and MUST ro=
ute the message to</div><div>=A0=A0 that node.</div><div><br></div><div>- S=
ection 9.4: Needs normative language. =A0</div>
<div><br></div><div>- Section 9.5: While this section does have a fair amou=
nt of normative language, it is still lacking in a few cases:=A0</div><div>=
--Item 2.: =A0&quot;should&quot; -&gt; &quot;SHOULD&quot;</div><div>--Item =
5.: =A0&quot;The AP sends the response=85&quot; -&gt; &quot;The AP MUST sen=
d the response=85&quot;=A0</div>
<div>--1st paragraph after list: &quot;=85can directly connect=85&quot; -&g=
t; &quot;MAY directly connect&quot;</div><div>--2nd paragraph after list: &=
quot;it can still populate&quot; -&gt; &quot;it MAY still populate&quot;</d=
iv>
<div>--2nd paragraph after list: the description of the use of PING should =
be reworded with normative language (I&#39;ll leave that exercise to the au=
thors)</div><div>--3rd paragraph after the list: =A0&quot;JP simply sends&q=
uot; -&gt; &quot;JP MUST send&quot;=A0</div>
<div><br></div><div>- Section 9.7.1:</div><div>--1st para: =A0&quot;.., it =
then sends=85&quot; -&gt; &quot;.., it then MUST send =85&quot;</div><div>-=
-3rd para: needs normative language</div><div>OLD:</div><div>=A0=A0 In no e=
vent does</div>
<div>=A0=A0 an attempt to reestablish connectivity with a lost neighbor all=
ow the</div><div>=A0=A0 peer to remain in the neighbor table.=A0</div><div>=
NEW:=A0</div><div>=A0=A0 In the case of=A0</div><div>=A0=A0 an attempt to r=
eestablish connectivity with a lost neighbor, the peer=A0</div>
<div>=A0=A0 MUST not remain in the neighbor table.=A0</div><div>OR:=A0</div=
><div>=A0=A0 In the case of=A0</div><div>=A0=A0 an attempt to reestablish c=
onnectivity with a lost neighbor, the peer=A0</div><div>=A0=A0 MUST be remo=
ved from the neighbor table.</div>
<div>-- 4th para: &quot;should&quot; -&gt; &quot;SHOULD&quot; (2 cases), =
=A0&quot;use Pings&quot; -&gt; &quot;MUST use Pings&quot;</div><div><br></d=
iv><div>-Section 9.7.2:</div><div>--1st para: =A0&quot;..the failed peer ar=
e removed..&quot; -&gt; &quot;=85the failed peer MUST be removed..&quot;</d=
iv>
<div>--2nd para: =A0&quot;=85the peer initiates=85&quot; -&gt; &quot;=85the=
 peer MUST initiate..&quot;</div><div><br></div><div>-Section 9.7.3:</div><=
div>--1st para after list: =A0&quot;is needed&quot; -&gt; &quot;is REQUIRED=
&quot;</div>
<div>--3rd para after list: =A0&quot;the peer sends an Update&quot; -&gt; &=
quot;the peer MUST send an Update&quot;</div><div><br></div><div>-Section <=
a href=3D"http://9.7.4.4">9.7.4.4</a>: =A0Needs a scrub for normative langu=
age</div>
<div><br></div><div>-Section 9.9: Needs a scrub for normative language.=A0<=
/div><div><br></div><div>-Section 10.1: General: Needs a lot of work to be =
specified using normative language. =A0The majority of the configuration el=
ements are not specified using normative language - for example, terms such=
 as permitted, allowed, valid are used in statements rather than normative =
language</div>
<div>or they are indicative of the need for normative language. =A0A specif=
ic example is in the definition for &quot;clients-permitted&quot;:</div><di=
v><br></div><div>OLD:</div><div>=A0=A0 =A0 =A0This element represents wheth=
er clients are</div>
<div>=A0=A0 =A0 =A0permitted or whether all nodes must be peers. =A0If it i=
s set to</div><div>=A0=A0 =A0 =A0&quot;true&quot; or absent, this indicates=
 that clients are permitted. =A0If</div><div>=A0=A0 =A0 =A0it is set to &qu=
ot;false&quot; then nodes are not allowed to remain clients</div>
<div>=A0=A0 =A0 =A0after the initial join.=A0</div><div><br></div><div>NEW:=
=A0</div><div>=A0=A0 =A0 =A0This element represents whether clients are</di=
v><div>=A0=A0 =A0 =A0permitted or whether all nodes need to be peers. =A0If=
 clients=A0</div><div>=A0=A0 =A0 =A0are permitted, the element MUST be set =
to &quot;true&quot; or absent. =A0</div>
<div>=A0=A0 =A0 =A0If the nodes are not allowed to remain clients after the=
=A0</div><div>=A0=A0 =A0 =A0initial join, the element MUST be set to &quot;=
false&quot;.</div><div><br></div><div>--Section 10.1 - 4th para after the e=
lement list states that &quot;All of the non optional values MUST be provid=
ed&quot;. =A0However, the list of elements in the previous paragraph are no=
t specifically identified as non optional. =A0I think the first 3 are manda=
tory. =A0So, I would suggest to re-word the 3rd paragraph as follows and de=
lete the 1st sentence in the 4th paragraph noted above:=A0</div>
<div>OLD:</div><div>=A0=A0 In addition, the kind element contains the follo=
wing elements:</div><div>=A0=A0 max-count: =A0the maximum number of values =
which members of the overlay</div><div>=A0=A0 =A0 =A0must support.</div><di=
v>=A0=A0 data-model: =A0the data model to be used.</div>
<div>=A0=A0 max-size: =A0the maximum size of individual values.</div><div>=
=A0=A0 access-control: =A0the access control model to be used.</div><div>=
=A0=A0 max-node-multiple: =A0This is optional and only used when the access=
</div><div>=A0=A0 =A0 =A0control is NODE-MULTIPLE. =A0This indicates the ma=
ximum value for</div>
<div>=A0=A0 =A0 =A0the i counter. =A0This is an integer greater than 0.</di=
v><div><br></div><div>NEW:=A0</div><div>=A0=A0 In addition, the kind elemen=
t MUST contain the following elements:</div><div>=A0=A0 max-count: =A0the m=
aximum number of values which members of the overlay</div>
<div>=A0=A0 =A0 =A0must support.</div><div>=A0=A0 data-model: =A0the data m=
odel to be used.</div><div>=A0=A0 max-size: =A0the maximum size of individu=
al values.</div><div>=A0=A0 access-control: =A0the access control model to =
be used.</div><div><br>
</div><div>=A0=A0 The kind element MAY also contain the following element:<=
/div><div>=A0=A0 max-node-multiple: =A0if the access control is NODE-MULTIP=
LE,=A0</div><div>=A0=A0 =A0 =A0this element MAY be included. This indicates=
 the maximum value for</div>
<div>=A0=A0 =A0 =A0the i counter. =A0It MUST be an integer greater than 0. =
=A0=A0</div><div><br></div><div>--Section 10.1, next to last para: There&#3=
9;s no normative language, but it seems there should be since it is specify=
ing specification computations and encoding that I believe are required.=A0=
</div>
<div><br></div><div>- Section 10.2: =A0Needs more normative language:</div>=
<div><br></div><div>-- 2nd para:=A0</div><div>OLD: This value is provided b=
y the user or some other out of band=A0</div><div>=A0=A0 =A0 provisioning m=
echanism.</div>
<div><br></div><div>NEW: This value MUST be provided by the user or some ot=
her out of band=A0</div><div>=A0=A0 =A0 provisioning mechanism.&quot;</div>=
<div><br></div><div>-- 3rd para:=A0</div><div>OLD: =A0</div><div>=A0=A0 Onc=
e an address and URL for the configuration server is determined,</div>
<div>=A0=A0 the peer forms an HTTPS connection to that IP address.=A0</div>=
<div>NEW:=A0</div><div>=A0=A0 Once an address and URL for the configuration=
 server is determined,</div><div>=A0=A0 the peer MUST form an HTTPS connect=
ion to that IP address.=A0</div>
<div><br></div><div>-- 4th para: =A0&quot;which replaces&quot; -&gt; =A0&qu=
ot;which MUST replace&quot;</div><div><br></div><div>-- 5th para: =A0&quot;=
nodes obtain the&quot; -&gt; &quot;nodes MUST obtain the&quot;</div><div><b=
r>
</div><div>- Section 10.3:=A0</div><div>-- 3rd para: =A0&quot;is performed&=
quot; -&gt; &quot;MUST be performed&quot;. =A0</div><div>-- 3rd para: Bulle=
ts need to be modified to normative.=A0</div><div>-- 4th para: &quot;the ce=
rtificate contains&quot; -&gt; &quot;the certificate MUST contain&quot;</di=
v>
<div>-- para after 2nd set of bullets: =A0needs normative language.</div><d=
iv>-- 2nd para after 2nd set of bullets: =A0&quot;The node then reads=85&qu=
ot; -&gt; =A0&quot;The node MUST then use=85&quot;</div><div><br></div><div=
>- Section 10.5:</div>
<div>--Second para: &quot;the joining node first forms&quot; -&gt; &quot;th=
e joining node MUST first form&quot;</div><div>--3rd para: =A0text uses the=
 phrase &quot;it can note the Node-ID in the response and use this Node-ID =
to start sending requests&quot;. =A0It&#39;s not clear whether the use of t=
he Node-ID is a MAY or a MUST. =A0</div>
<div><br></div><div>- Section 12. I&#39;m assuming that the security direct=
orate has reviewed this in detail, thus my focus in reviewing this section =
was on general understanding. The biggest issues is that there is NO normat=
ive language at all in the security section. =A0As in other sections, terms=
 like &quot;need&quot;, &quot;are/is used/sent, etc.&quot;, =A0&quot;ensure=
&quot;, lower case reserved words rather than upper case, etc. are used whe=
n normative language ought to have been used.=A0</div>
<div><br></div><div><br></div><div>- Section 13. IANA Registrations:</div><=
div>- General: there seem to be several registries for which the usage/requ=
irement is unclear as there&#39;s no mention of such in the body of the doc=
ument. =A0In general, references to the sections in the document describing=
 the information included in the registries would be more than helpful.</di=
v>
<div><br></div><div>- Section 13.5: Creates a RELOAD Application Registry, =
but the use and need for such isn&#39;t described elsewhere in the document=
.=A0</div><div><br></div><div>- Section 13.12. Forwarding Options Registry.=
 SEction 5.3.2.3 seems to define three flags for the Forwarding options typ=
e, so it&#39;s not clear to me why this registry has just &quot;invalid&quo=
t; and &quot;reserved&quot;</div>
<div><br></div><div><br></div><div>- Section 13.15: =A0Defines/registers a =
RELOAD URI schema but there is no mention of this URI anywhere else in the =
document. =A0In what context is it used? =A0 =A0</div><div>=A0=A0 =A0 =A0 =
=A0</div><div><br>
</div><div>Minor =A0Issues:</div><div>---------------------</div><div><br><=
/div><div>- Section 1.2.1, 2nd paragraph: I don&#39;t understand the exampl=
e as to why a single application requires multiple usages - i.e, why voicem=
ail? =A0Isn&#39;t the intent to say that an application might need to use b=
oth SIP and XMPP - i.e., you wouldn&#39;t define a &quot;usage&quot; for an=
 application, would you? =A0=A0</div>
<div><br></div><div>- Section 2. Some of the definitions use terms that are=
 not yet defined, so that&#39;s not particularly helpful - i.e,. Attach and=
 Update are used. In some cases (e.g., Connection Table), you could just de=
lete the statement with the reference.=A0</div>
<div><br></div><div>- Section 3.3, last paragraph. =A0Add a reference to 5.=
4.2.4 =A0after &quot;RouteQuery method&quot;</div><div><br></div><div>- Sec=
tion 5.1: &quot;If any of these are incorrect=85&quot; =A0- need to specify=
 what qualifies as &quot;incorrect&quot; - is it wrong formatting, invalid =
header field=A0</div>
<div>value, etc.?</div><div><br></div><div>- Section 5.1.2:</div><div>--1st=
 paragraph: I have no idea what the &quot;other three cases&quot; reference=
s.=A0</div><div><br></div><div>- Section 5.2: &quot;may be configured&quot;=
 -&gt; &quot;can be configured&quot;, =A0&quot;alternative=A0</div>
<div>routing algorithms may be selected&quot; -&gt; &quot;alternative routi=
ng algorithms MAY be selected&quot;</div><div><br></div><div>- Section 5.3:=
 =A0The three parts of the messages are listed and the last sentence says t=
hat &quot;The following sections describe the format of each part of the me=
ssage&quot;, but there are 4 sub-sections in 5.3, with the first section NO=
T describing one of the three parts of the messages. =A0I suggest to strike=
 that last sentence and just put references to the sections in the list ite=
ms for each of the three messages.=A0</div>
<div><br></div><div>-Section 5.3.3:=A0</div><div>--&quot;critical&quot; des=
cription: =A0&quot;Whether this extension must be..&quot; &quot;Whether thi=
s extension needs to be=85&quot;=A0</div><div><br></div><div>-Section 5.3.4=
: =A01st para after certificate structure: =A0&quot;may contain&quot; -&gt;=
 &quot;MAY contain&quot;=A0</div>
<div><br></div><div>-Section 5.5: It would be helpful to highlight that fou=
ndation, priority and type are based on ICE, in particular since ICE is not=
 discussed until the subsequent section - e.g., &quot;the foundation produc=
tion&quot; -&gt; &quot;the ICE foundation production&quot;.=A0</div>
<div><br></div><div>- Section 5.6: =A0</div><div>-- The last three paragrap=
hs are confusing.=A0</div><div>---In particular, it&#39;s not clear what al=
gorithms are being referenced in this sentence:</div><div>=A0=A0&quot;We wi=
ll first define each of these algorithms, then</div>
<div>=A0=A0 define overlay link protocols that use them.&quot;</div><div>--=
- In the note paragraph, I believe &quot;These protocols have been chosen=
=85&quot; is referring to the three overlay link protocols supported by REL=
OAD per this document.</div>
<div>---The Note to implementors paragraph seems out of context</div><div>-=
-- Per my next comment, I suggest to move the detailed discussion of future=
 overlay link protocols to the appendix, so some of this text may be releva=
nt only to that.=A0</div>
<div><br></div><div>-Section 5.6.1: =A0I suggest that the sub-sections in t=
his section be moved to an appendix and a reference to such be added.=A0</d=
iv><div><br></div><div>-Section 5.6.3.1.1, next to the last paragraph:</div=
>
<div>&quot;when a link may be failing&quot; -&gt; &quot;when a link might b=
e failing&quot;</div><div><br></div><div>- Section 9.1: While this is an ov=
erview, it seems to me that some of this is describing normative behavior (=
that I don&#39;t see specified else). =A0Per the general comment, I would r=
eword the first sentence as follows:=A0</div>
<div>OLD:</div><div>=A0=A0 The algorithm described here is a modified versi=
on of the Chord</div><div>=A0=A0 algorithm.</div><div>NEW:</div><div>=A0=A0=
 =A0The algorithm described here, Chord-RELOAD is a modified version=A0</di=
v><div>=A0=A0 =A0of the Chord algorithm.</div>
<div><br></div><div>- Section 10.3, 1st para: =A0&quot;required&quot; -&gt;=
 &quot;REQUIRED&quot;</div><div><br></div><div>- Section 10.3.1, last sente=
nce: &quot;must&quot; =A0-&gt; &quot;MUST&quot;</div><div><br></div><div>- =
Section 10.4, 1st para, last sentence: &quot;should use&quot; -&gt; &quot;S=
HOULD use&quot;</div>
<div><br></div><div>- Section 11 - examples:</div><div>--General - there ar=
e no detailed messages shown anywhere for the examples. There should be at =
least one, in particular given the comment above about the RELOAD URI that =
is registered, but not mentioned anywhere else in the document.=A0</div>
<div>--first example (see my nit below about the examples not being numbere=
d or labeled in any way): =A0The third sentence says that &quot;It gets rou=
ted to the admitting peer (AP), yet the flow shows that the message first g=
ets routed to the PP and then onto AP. It would be helpful if that were cla=
rified.=A0</div>
<div>- =A0Also (general), the text mentions the use of ICE. =A0It&#39;s not=
 clear to me exactly where in the flow that happens - it would be good to a=
nnotate such (i.e., in a similar manner as the TLS is illustrated).=A0</div=
><div>
- next to the last example (text on page 131, diagram on page 132): I&#39;m=
 quite confused as the text states that JP has received an update from AP a=
nd thus now knows APs predecessors, which are also JP&#39;s predecessors, s=
o JP Attaches to them. However, the diagram does not show JP getting an Upd=
ate from AP and it shows JP doing Updates to PPP and PP rather than Attache=
s (as the text suggests). =A0</div>
<div><br></div><div>- Section 13.10. Overlay link types: These specific str=
ing types are not used elsewhere in the document. =A0Suggest that a referen=
ce to 5.6 be added and these particular strings be included in parenthesis =
after the items in the list. =A0</div>
<div><br></div><div><br></div><div>- Section 13.16, Security considerations=
 portion:=A0</div><div>-- The first sentence doesn&#39;t make sense. Did yo=
u mean?=A0</div><div>=A0=A0 &quot;This media type is typically not used to<=
/div>
<div>=A0=A0 transport information that needs to be kept confidential,=A0</d=
iv><div>=A0=A0 however, there are cases where the integrity of the informat=
ion is</div><div>=A0=A0 important.&quot;</div><div>-- &quot;then the conten=
ts of the file need to be=85&quot; -&gt; &quot;then the contents of the fil=
e MUST be =85&quot; =A0=A0</div>
<div><br></div><div><br></div><div><br></div><div>Nits:</div><div>-----</di=
v><div>- General: kind is sometimes &quot;Kind&quot; and sometimes &quot;ki=
nd&quot;. =A0The former is more readable and highlights it as a reserved wo=
rd.=A0</div>
<div><br></div><div>- Section 2. =A0</div><div>--General: It would be helpf=
ul if the terms were alphabetized.=A0</div><div>--Node: &quot;We use the te=
rm &quot;Node&quot; to refer to =85&quot; -&gt; &quot;Refers to =85&quot;</=
div>
<div><br></div><div>- Section 3.2:</div><div>-- 2nd para, last sentence: =
=A0&quot;refer such&quot; -&gt; &quot;refer to such&quot;</div><div>-- 3rd =
para, 1st sentence: =A0&quot;concept&quot; -&gt; &quot;entity&quot;</div><d=
iv>
<br></div><div>- Section 4.1.4, 4th paragraph: I&#39;m still not getting th=
e applicability of voicemail as a RELOAD Kind (per the reference also in se=
ction 1.2.1). =A0I guess you are talking about a voicemail message (in this=
 case) and a server or application in section 1.2.1? =A0 Voicemail just doe=
s not seem like an obvious example to me. =A0</div>
<div><br></div><div>- Section 5.1.1, last bullet: =A0&quot;In that case,=85=
&quot; -&gt; =A0&quot;In the latter case, =85&quot;=A0</div><div><br></div>=
<div>- Section 5.1.2:</div><div>-- 2nd para: =A0&quot;arrange&quot; -&gt; &=
quot;ensure&quot;, =A0&quot;This may be arranged&quot; -&gt; &quot;This can=
 be arranged=85&quot;=A0</div>
<div>-- 3rd para (1st after bullets): It&#39;s not clear that A=85E is a se=
t of ordered nodes in the example. I would suggest to reword as:</div><div>=
OLD:</div><div>=A0=A0 As an example of the first strategy, if node D=A0</di=
v><div>
NEW:=A0</div><div>=A0=A0Consider an example with nodes A, B, C, D and E, re=
spectively. =A0If=A0</div><div>=A0=A0node D=85.</div><div><br></div><div>- =
Section <a href=3D"http://5.3.1.1">5.3.1.1</a>: First two sentences can be =
reworded more succinctly - you&#39;re not really providing definitions here=
, put rather describing the=A0</div>
<div>the syntax for and providing examples illustrative of the presentation=
 language.=A0</div><div><br></div><div>OLD:=A0</div><div>=A0=A0 The followi=
ng definitions are used throughout RELOAD and so are</div><div>=A0=A0 defin=
ed here. =A0They also provide a convenient introduction to how to</div>
<div>=A0=A0 read the presentation language.</div><div>NEW:=A0</div><div>=A0=
=A0 This section provides an introduction to the presentation language</div=
><div>=A0=A0 used throughout RELOAD.=A0</div><div><br></div><div>- Section =
<a href=3D"http://5.3.3.1">5.3.3.1</a>: Error_Data_Too_Old is duplicated.</=
div>
<div><br></div><div>- Section <a href=3D"http://5.5.1.6">5.5.1.6</a>: Add r=
eferences for SCTP and DCCP.=A0</div><div><br></div><div>- Section <a href=
=3D"http://6.4.1.3">6.4.1.3</a>: =A0The reference to &quot;this Version&quo=
t; is superfluous. Propose the following change:</div>
<div>OLD:</div><div>=A0=A0 This version of RELOAD (unlike previous versions=
) does not have an</div><div>=A0=A0 explicit Remove operation.</div><div>NE=
W:=A0</div><div>=A0=A0 RELOAD does not have an explicit Remove operation.</=
div><div><br>
</div><div>- Section 9: General. The first sentence states that the algorit=
hm defined here is referred to as &quot;chord-reload&quot;, however, subseq=
uent sections don&#39;t seem to use that term. =A0It would be more clear if=
 that term was used. And, really, it would be more consistent to use the te=
rm Chord-RELOAD. However, this should also be consistent with the IANA-Regi=
stration which has CHORD-RELOAD.=A0</div>
<div><br></div><div>- Section 9.7.4.3, 3rd para:=A0</div><div>-- Remove &qu=
ot;Note to implementers&quot;. =A0Text already highlights that the text is =
specific to implementations.=A0</div><div>-- &quot;may be found&quot; -&gt;=
 &quot;can be found&quot;</div>
<div><br></div><div>- Section 9.8: =A0&quot;For this topology plugin&quot; =
-&gt; &quot;For Chord-RELOAD&quot;</div><div><br></div><div>- Section 10.2,=
 2nd para: =A0&quot;determines&quot; -&gt; &quot;determining&quot;</div><di=
v>
<br></div><div>- Section 11:=A0</div><div>- General: there are no labels fo=
r any of the call flows, so it&#39;s not always clear what the text is refe=
rring to. =A0In general, I think the text precedes the flow.=A0</div><div>-=
 &quot;abbreviation&quot; -&gt; &quot;abbreviations&quot;=A0</div>
<div><br></div><div>- Section 13.16:</div><div>--Interoperability considera=
tions: =A0&quot;knows&quot; -&gt; &quot;known&quot;=A0</div><div><br></div>=
<div>- Section 14: &quot;provied&quot; -&gt; &quot;provided&quot;</div><div=
>
<br></div><div>- Appendix C: Delete now - it&#39;s totally useless as is.</=
div></div>

--20cf307d05a61a974404aa1a986d--

From mary.ietf.barnes@gmail.com  Tue Aug  9 16:14:30 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2060221F8B04; Tue,  9 Aug 2011 16:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.08
X-Spam-Level: 
X-Spam-Status: No, score=-104.08 tagged_above=-999 required=5 tests=[AWL=0.917, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  J_CHICKENPOX_56=0.6, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpTeC4DNwkCW; Tue,  9 Aug 2011 16:14:26 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 19C5221F8B02; Tue,  9 Aug 2011 16:14:26 -0700 (PDT)
Received: by vws12 with SMTP id 12so498374vws.31 for <multiple recipients>; Tue, 09 Aug 2011 16:14:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AMKWaaNDDn847SiLu9bY124f85DjLrEcAHwaeTpDmaU=; b=QV5cZQwh+THhYhvr3yu4+jFsYEyCcv5YBxKbHGKV7IBOHKxU/rRng1ILB9cq3ZPr1f GUPii28lN+nA42zRLfbBwsEck59TCA1GQb/1Y/DHhum1x6LIk0ZRjMCRi0s9I6LMNf/x nc8ZNEBD7qBtLupKEuzgv54rOkfOUxW0dDBDY=
MIME-Version: 1.0
Received: by 10.52.69.194 with SMTP id g2mr4406587vdu.451.1312931695647; Tue, 09 Aug 2011 16:14:55 -0700 (PDT)
Received: by 10.52.167.34 with HTTP; Tue, 9 Aug 2011 16:14:55 -0700 (PDT)
In-Reply-To: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com>
References: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com>
Date: Tue, 9 Aug 2011 18:14:55 -0500
Message-ID: <CAHBDyN4Ot8RkosbL6aF_0H1_Ksj7tzRxwWg9YeEKcmaY9MFr+Q@mail.gmail.com>
Subject: Re: Gen-ART Review: Last Call <draft-ietf-p2psip-base-17.txt>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-p2psip-base.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=20cf307cffd8555b4a04aa1abbeb
Cc: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>, hgs+p2psip@cs.columbia.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 23:14:30 -0000

--20cf307cffd8555b4a04aa1abbeb
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I'm resending to try to capture one additional author (Henning) that bounce=
d
and the Gen-ART mailing list.  I could not find a valid email for Salman
Basset  Please reply to this email.

Thanks,
Mary.

On Tue, Aug 9, 2011 at 6:05 PM, Mary Barnes <mary.ietf.barnes@gmail.com>wro=
te:

>
> 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>.
>
> Sorry for the delay, but a two week IETF-LC for a 150 page document two
> weeks before an IETF meeting virtually ensures that the document  won't b=
e
> carefully reviewed by the community and that directorate reviews will are
> late ;)   While this review was done specifically on the -17, I have
> reviewed the diff and these comments still apply to the -18.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Document: draft-ietf-p2psip-base-17
> Reviewer:  Mary Barnes
> Review Date:  9 August  2011
> IETF LC End Date: 22 July 2011
>
> Summary: Not Ready.
>
> Comments:
> ----------------
> The document is very a dense (with detailed technical information) and lo=
ng
> (150 page) specification for a Peer-to-peer signaling protocol.  While th=
e
> overall technical functionality seems fairly correct and thoroughly
> specified, the primary issue is a tremendous lack of normative language i=
n
> the main body of the document.  Non-inclusive details of such are include=
d
> below.
>
> Major Issues:
> -------------------
>
> General:
> --There is a fair number of cases where normative language should be used=
.
>  I have detailed some (but certainly not all)  instances where it is lack=
ing
> with proposed rewording.  I have also noted cases where it is used (lower
> case) where it could be confused with needing normative language and wher=
e
> it isn't necessary and there are some cases where it's just not clear. I
> consider these major since it can impact interoperability and could lead
> developers to not implement key functionality.
>
> --There is also little or no normative language for the majority of the
> elements in the structures - i.e., the reader has to assume which element=
s
> are mandatory and which are optional and it's not always clear.   For
> example, rather than saying "Field x contains blah", it should say "Field=
 x
> MUST contain blah" and rather than "The contents of the message will be x=
, y
> and z", it should say something like "The message MUST (or SHOULD) contai=
n
> x, y and z".  I have not detailed the places where this is necessary in m=
ost
> cases.  The authors should review the detailed definition for each of the
> messages.
>
> --The message names are used inconsistently.  The IANA registry has the
> message codes all lower case.  There are places in the examples and the b=
ody
> of the document where the _req part is missing, there is no "_", the firs=
t
> letters are Upper case, etc.  The messages are also used in a general sen=
se
> - e.g., "MUST perform an Attach", which should really be stated as "MUST
> send an attach_req message)
>
> Major - Detailed:
>
> - Sections 3.2.1, 3.2.2 and 3.3: lots of changes needed to reword using
> normative language.
>
> - Section 3.4, last paragraph: Needs to be reworded normatively and more
> precisely. It's really not clear to me what the required behavior is as i=
t
> first says it needs to (which I'm not sure is a SHOULD or is REQUIRED to)
> maintain connections to all the peers near and enough others.., but how m=
uch
> is "enough".   Also, what is meant by the "specified link set" - is that
> referring to all the nearby peers or the peers+enough others?  Or is this
> more clearly (and normatively) specified elsewhere, such that a reference
> could be added.
>
> - Section 4.2: needs normative language - i.e.:
> --"Each Usage needs to =85" ->  "Each Usage MUST=85"
>
> - Section 5.1.1: Bullet items need normative language
> -- 1st bullet: It's also  not clear what the its are in "it passes it up"=
.
>  I think it should be "the node passes the message up to the upper layers=
".
>   However, this probably needs to be normative language - i.e., "the node
> MUST pass the message to the upper layers".  The same applies to the thir=
d
> bullet.
> --bullet 2:  "the message is destined for this node and is passed up=85" =
->
> "the message is destined for this node and MUST be passed=85.,
>
> - Section 5.1.2:
> -- Paragraphs 5, 6, 7 and 8 need to be reworded to have normative
> statements.
> -- Last paragraph (9) mixes normative text with in an example. The
> normative text needs to be separated from the example - e.g., split some =
of
> the sentences into the normative behavior and then the example.
>
> -Section 5.2.1 is totally inconsistent with the use of normative language
> (i.e., lower case occurrences and lack of KEY words) - shouldn't the
> following be normative statements something like the following:
> -- First paragraph:
> ---First sentence:  "a node constructs" -> "a node MUST construct".
> --- 3rd sentence: "resulting message will use the normal overlay routing"
> -> "resulting message MUST use the normal overlay routing"
> --- 4th sentence: "The node can also" ->  "The node MAY also"
> -- Third paragraph:
> --- 3rd sentence: "a single request can also" -> "a single request MAY
> also"
> -- Fourth paragraph:
> --- 1st sentence: this could be interpreted as normative:  "Because
> messages may" ->  "Because messages can"
> --- 3rd sentence:  "the request is retransmitted" ->  "the request MUST b=
e
> retransmitted"
>
> -Section 5.3.2:
> -- General: some of the contents of the structure have normative language
> and others don't.  There is some normative behavior defined for these fie=
lds
> later, so perhaps adding section references as you do for some fields wou=
ld
> be helpful.
>
> For example:
> --"overlay": shouldn't this be normative:  "the overlay name is hashed wi=
th
> SHA-1" -> "the overlay name MUST be hashed with SHA-1"
> --"destination_list": seems like some of this should be normative?
>
> -Section 5.3.2.1:
> --1st paragraph: shouldn't this be normative?
> "the configuration document has a sequence number" ->  "the configuration
> document MUST contain a sequence number"
> -- 1st paragraph, last sentence: "may"  -> "can"
>
> -Section 5.3.2.2:
> --Paragraph after the 1st structure:  Shouldn't this be stated normativel=
y
> since it is described how the structure MUST be handled depending upon th=
e
> contents?
> --Paragraph after second structure, suggest the following changes:
> ---"the generation counters should" ->  "the generation counters SHOULD"
> ---"An implementation could use.." -> "An implementation MAY use=85"
> ---"the node confirms that the generation counter matches" -> "the node
> MUST confirm that the generation counter matches"
> ---"If it does not match, it is silently dropped." -> "If it does not
> match, it MUST be silently dropped."
>
> -Section 5.3.3.1:
> --1st para: "a request returns" -> "a request MUST return"
> --1st para: "then the message code is the response code that matches the
> request" ->
> "then the message code MUST be set to the response code that matches the
> request"
> --2nd para: "message code is set" ->  "message code MUST be set"
>
> -Section 5.3.4 - needs normative language:
> --1st paragraph after GenericCertificate structure:
> ---"All signatures are formatted" -> "Alls signatures MUST be formatted"
> ---"The input structure=85varies.." ->  "The input structure =85 MAY vary=
=85"
>
> -Section 5.4.1: "need to be described" -> "MUST be described"
>
> -Section 5.4.2-Section 7.  These sections need to be carefully reviewed a=
nd
> updated appropriately with normative text.  [ I have marks up for pages
> 55-102 where normative language is needed if someone wants those scanned =
and
> forwarded - I'm just too lazy to type them all out.]
>
> - Section 8:  There is only one actual normative word used in this sectio=
n!
>  There is a lc "should" that ought to be "SHOULD".  I don't know if the
> authors assumed that the normative language in TURN was sufficient, but I=
 do
> not believe that is the case as it leaves the normative behavior to be
> inferred by the reader/implementor. Rather than rewrite the whole section
> myself, the authors need to review carefully. For example, there are "nee=
ds
> to", which likely are really and lots of present tense statements (e.g.,
> "The address of the peer is stored=85"), which ought to be MUSTs or SHOUL=
Ds.
>
> - Section 9.2:  seems like this needs normative language. Suggest the
> following:
> OLD:
>    For this Chord based topology plugin, the size of the Resource-ID is
>    128 bits.  The hash of a Resource-ID is computed using SHA-1
>    [RFC3174]then truncating the SHA-1 result to the most significant 128
>    bits.
> NEW:
>    For Chord-RELOAD, the size of the Resource-ID MUST be
>    128 bits.  The hash of a Resource-ID MUST be computed using SHA-1
>    [RFC3174].  The SHA-1 result MUST be truncated to the most significant
>    128 bits.
>
> - Section 9.3: Needs normative language.
> OLD:
>    If a peer is not responsible for a Resource-ID k, but is directly
>    connected to a node with Node-ID k, then it routes the message to
>    that node.  Otherwise, it routes the request to the peer in the
>    routing table that has the largest Node-ID that is in the interval
>    between the peer and k.  If no such node is found, it finds the
>    smallest Node-Id that is greater than k and routes the message to
>    that node.
> NEW:
>    If a peer is not responsible for a Resource-ID k, but is directly
>    connected to a node with Node-ID k, then it MUST route the message to
>    that node.  Otherwise, it MUST route the request to the peer in the
>    routing table that has the largest Node-ID that is in the interval
>    between the peer and k.  If no such node is found, it MUST find the
>    smallest Node-Id that is greater than k and MUST route the message to
>    that node.
>
> - Section 9.4: Needs normative language.
>
> - Section 9.5: While this section does have a fair amount of normative
> language, it is still lacking in a few cases:
> --Item 2.:  "should" -> "SHOULD"
> --Item 5.:  "The AP sends the response=85" -> "The AP MUST send the
> response=85"
> --1st paragraph after list: "=85can directly connect=85" -> "MAY directly
> connect"
> --2nd paragraph after list: "it can still populate" -> "it MAY still
> populate"
> --2nd paragraph after list: the description of the use of PING should be
> reworded with normative language (I'll leave that exercise to the authors=
)
> --3rd paragraph after the list:  "JP simply sends" -> "JP MUST send"
>
> - Section 9.7.1:
> --1st para:  ".., it then sends=85" -> ".., it then MUST send =85"
> --3rd para: needs normative language
> OLD:
>    In no event does
>    an attempt to reestablish connectivity with a lost neighbor allow the
>    peer to remain in the neighbor table.
> NEW:
>    In the case of
>    an attempt to reestablish connectivity with a lost neighbor, the peer
>    MUST not remain in the neighbor table.
> OR:
>    In the case of
>    an attempt to reestablish connectivity with a lost neighbor, the peer
>    MUST be removed from the neighbor table.
> -- 4th para: "should" -> "SHOULD" (2 cases),  "use Pings" -> "MUST use
> Pings"
>
> -Section 9.7.2:
> --1st para:  "..the failed peer are removed.." -> "=85the failed peer MUS=
T be
> removed.."
> --2nd para:  "=85the peer initiates=85" -> "=85the peer MUST initiate.."
>
> -Section 9.7.3:
> --1st para after list:  "is needed" -> "is REQUIRED"
> --3rd para after list:  "the peer sends an Update" -> "the peer MUST send
> an Update"
>
> -Section 9.7.4.4:  Needs a scrub for normative language
>
> -Section 9.9: Needs a scrub for normative language.
>
> -Section 10.1: General: Needs a lot of work to be specified using normati=
ve
> language.  The majority of the configuration elements are not specified
> using normative language - for example, terms such as permitted, allowed,
> valid are used in statements rather than normative language
> or they are indicative of the need for normative language.  A specific
> example is in the definition for "clients-permitted":
>
> OLD:
>       This element represents whether clients are
>       permitted or whether all nodes must be peers.  If it is set to
>       "true" or absent, this indicates that clients are permitted.  If
>       it is set to "false" then nodes are not allowed to remain clients
>       after the initial join.
>
> NEW:
>       This element represents whether clients are
>       permitted or whether all nodes need to be peers.  If clients
>       are permitted, the element MUST be set to "true" or absent.
>       If the nodes are not allowed to remain clients after the
>       initial join, the element MUST be set to "false".
>
> --Section 10.1 - 4th para after the element list states that "All of the
> non optional values MUST be provided".  However, the list of elements in =
the
> previous paragraph are not specifically identified as non optional.  I th=
ink
> the first 3 are mandatory.  So, I would suggest to re-word the 3rd paragr=
aph
> as follows and delete the 1st sentence in the 4th paragraph noted above:
> OLD:
>    In addition, the kind element contains the following elements:
>    max-count:  the maximum number of values which members of the overlay
>       must support.
>    data-model:  the data model to be used.
>    max-size:  the maximum size of individual values.
>    access-control:  the access control model to be used.
>    max-node-multiple:  This is optional and only used when the access
>       control is NODE-MULTIPLE.  This indicates the maximum value for
>       the i counter.  This is an integer greater than 0.
>
> NEW:
>    In addition, the kind element MUST contain the following elements:
>    max-count:  the maximum number of values which members of the overlay
>       must support.
>    data-model:  the data model to be used.
>    max-size:  the maximum size of individual values.
>    access-control:  the access control model to be used.
>
>    The kind element MAY also contain the following element:
>    max-node-multiple:  if the access control is NODE-MULTIPLE,
>       this element MAY be included. This indicates the maximum value for
>       the i counter.  It MUST be an integer greater than 0.
>
> --Section 10.1, next to last para: There's no normative language, but it
> seems there should be since it is specifying specification computations a=
nd
> encoding that I believe are required.
>
> - Section 10.2:  Needs more normative language:
>
> -- 2nd para:
> OLD: This value is provided by the user or some other out of band
>      provisioning mechanism.
>
> NEW: This value MUST be provided by the user or some other out of band
>      provisioning mechanism."
>
> -- 3rd para:
> OLD:
>    Once an address and URL for the configuration server is determined,
>    the peer forms an HTTPS connection to that IP address.
> NEW:
>    Once an address and URL for the configuration server is determined,
>    the peer MUST form an HTTPS connection to that IP address.
>
> -- 4th para:  "which replaces" ->  "which MUST replace"
>
> -- 5th para:  "nodes obtain the" -> "nodes MUST obtain the"
>
> - Section 10.3:
> -- 3rd para:  "is performed" -> "MUST be performed".
> -- 3rd para: Bullets need to be modified to normative.
> -- 4th para: "the certificate contains" -> "the certificate MUST contain"
> -- para after 2nd set of bullets:  needs normative language.
> -- 2nd para after 2nd set of bullets:  "The node then reads=85" ->  "The =
node
> MUST then use=85"
>
> - Section 10.5:
> --Second para: "the joining node first forms" -> "the joining node MUST
> first form"
> --3rd para:  text uses the phrase "it can note the Node-ID in the respons=
e
> and use this Node-ID to start sending requests".  It's not clear whether =
the
> use of the Node-ID is a MAY or a MUST.
>
> - Section 12. I'm assuming that the security directorate has reviewed thi=
s
> in detail, thus my focus in reviewing this section was on general
> understanding. The biggest issues is that there is NO normative language =
at
> all in the security section.  As in other sections, terms like "need",
> "are/is used/sent, etc.",  "ensure", lower case reserved words rather tha=
n
> upper case, etc. are used when normative language ought to have been used=
.
>
>
> - Section 13. IANA Registrations:
> - General: there seem to be several registries for which the
> usage/requirement is unclear as there's no mention of such in the body of
> the document.  In general, references to the sections in the document
> describing the information included in the registries would be more than
> helpful.
>
> - Section 13.5: Creates a RELOAD Application Registry, but the use and ne=
ed
> for such isn't described elsewhere in the document.
>
> - Section 13.12. Forwarding Options Registry. SEction 5.3.2.3 seems to
> define three flags for the Forwarding options type, so it's not clear to =
me
> why this registry has just "invalid" and "reserved"
>
>
> - Section 13.15:  Defines/registers a RELOAD URI schema but there is no
> mention of this URI anywhere else in the document.  In what context is it
> used?
>
>
> Minor  Issues:
> ---------------------
>
> - Section 1.2.1, 2nd paragraph: I don't understand the example as to why =
a
> single application requires multiple usages - i.e, why voicemail?  Isn't =
the
> intent to say that an application might need to use both SIP and XMPP -
> i.e., you wouldn't define a "usage" for an application, would you?
>
> - Section 2. Some of the definitions use terms that are not yet defined, =
so
> that's not particularly helpful - i.e,. Attach and Update are used. In so=
me
> cases (e.g., Connection Table), you could just delete the statement with =
the
> reference.
>
> - Section 3.3, last paragraph.  Add a reference to 5.4.2.4  after
> "RouteQuery method"
>
> - Section 5.1: "If any of these are incorrect=85"  - need to specify what
> qualifies as "incorrect" - is it wrong formatting, invalid header field
> value, etc.?
>
> - Section 5.1.2:
> --1st paragraph: I have no idea what the "other three cases" references.
>
> - Section 5.2: "may be configured" -> "can be configured",  "alternative
> routing algorithms may be selected" -> "alternative routing algorithms MA=
Y
> be selected"
>
> - Section 5.3:  The three parts of the messages are listed and the last
> sentence says that "The following sections describe the format of each pa=
rt
> of the message", but there are 4 sub-sections in 5.3, with the first sect=
ion
> NOT describing one of the three parts of the messages.  I suggest to stri=
ke
> that last sentence and just put references to the sections in the list it=
ems
> for each of the three messages.
>
> -Section 5.3.3:
> --"critical" description:  "Whether this extension must be.." "Whether th=
is
> extension needs to be=85"
>
> -Section 5.3.4:  1st para after certificate structure:  "may contain" ->
> "MAY contain"
>
> -Section 5.5: It would be helpful to highlight that foundation, priority
> and type are based on ICE, in particular since ICE is not discussed until
> the subsequent section - e.g., "the foundation production" -> "the ICE
> foundation production".
>
> - Section 5.6:
> -- The last three paragraphs are confusing.
> ---In particular, it's not clear what algorithms are being referenced in
> this sentence:
>   "We will first define each of these algorithms, then
>    define overlay link protocols that use them."
> --- In the note paragraph, I believe "These protocols have been chosen=85=
" is
> referring to the three overlay link protocols supported by RELOAD per thi=
s
> document.
> ---The Note to implementors paragraph seems out of context
> --- Per my next comment, I suggest to move the detailed discussion of
> future overlay link protocols to the appendix, so some of this text may b=
e
> relevant only to that.
>
> -Section 5.6.1:  I suggest that the sub-sections in this section be moved
> to an appendix and a reference to such be added.
>
> -Section 5.6.3.1.1, next to the last paragraph:
> "when a link may be failing" -> "when a link might be failing"
>
> - Section 9.1: While this is an overview, it seems to me that some of thi=
s
> is describing normative behavior (that I don't see specified else).  Per =
the
> general comment, I would reword the first sentence as follows:
> OLD:
>    The algorithm described here is a modified version of the Chord
>    algorithm.
> NEW:
>     The algorithm described here, Chord-RELOAD is a modified version
>     of the Chord algorithm.
>
> - Section 10.3, 1st para:  "required" -> "REQUIRED"
>
> - Section 10.3.1, last sentence: "must"  -> "MUST"
>
> - Section 10.4, 1st para, last sentence: "should use" -> "SHOULD use"
>
> - Section 11 - examples:
> --General - there are no detailed messages shown anywhere for the example=
s.
> There should be at least one, in particular given the comment above about
> the RELOAD URI that is registered, but not mentioned anywhere else in the
> document.
> --first example (see my nit below about the examples not being numbered o=
r
> labeled in any way):  The third sentence says that "It gets routed to the
> admitting peer (AP), yet the flow shows that the message first gets route=
d
> to the PP and then onto AP. It would be helpful if that were clarified.
> -  Also (general), the text mentions the use of ICE.  It's not clear to m=
e
> exactly where in the flow that happens - it would be good to annotate suc=
h
> (i.e., in a similar manner as the TLS is illustrated).
> - next to the last example (text on page 131, diagram on page 132): I'm
> quite confused as the text states that JP has received an update from AP =
and
> thus now knows APs predecessors, which are also JP's predecessors, so JP
> Attaches to them. However, the diagram does not show JP getting an Update
> from AP and it shows JP doing Updates to PPP and PP rather than Attaches =
(as
> the text suggests).
>
> - Section 13.10. Overlay link types: These specific string types are not
> used elsewhere in the document.  Suggest that a reference to 5.6 be added
> and these particular strings be included in parenthesis after the items i=
n
> the list.
>
>
> - Section 13.16, Security considerations portion:
> -- The first sentence doesn't make sense. Did you mean?
>    "This media type is typically not used to
>    transport information that needs to be kept confidential,
>    however, there are cases where the integrity of the information is
>    important."
> -- "then the contents of the file need to be=85" -> "then the contents of=
 the
> file MUST be =85"
>
>
>
> Nits:
> -----
> - General: kind is sometimes "Kind" and sometimes "kind".  The former is
> more readable and highlights it as a reserved word.
>
> - Section 2.
> --General: It would be helpful if the terms were alphabetized.
> --Node: "We use the term "Node" to refer to =85" -> "Refers to =85"
>
> - Section 3.2:
> -- 2nd para, last sentence:  "refer such" -> "refer to such"
> -- 3rd para, 1st sentence:  "concept" -> "entity"
>
> - Section 4.1.4, 4th paragraph: I'm still not getting the applicability o=
f
> voicemail as a RELOAD Kind (per the reference also in section 1.2.1).  I
> guess you are talking about a voicemail message (in this case) and a serv=
er
> or application in section 1.2.1?   Voicemail just does not seem like an
> obvious example to me.
>
> - Section 5.1.1, last bullet:  "In that case,=85" ->  "In the latter case=
,
> =85"
>
> - Section 5.1.2:
> -- 2nd para:  "arrange" -> "ensure",  "This may be arranged" -> "This can
> be arranged=85"
> -- 3rd para (1st after bullets): It's not clear that A=85E is a set of
> ordered nodes in the example. I would suggest to reword as:
> OLD:
>    As an example of the first strategy, if node D
> NEW:
>   Consider an example with nodes A, B, C, D and E, respectively.  If
>   node D=85.
>
> - Section 5.3.1.1: First two sentences can be reworded more succinctly -
> you're not really providing definitions here, put rather describing the
> the syntax for and providing examples illustrative of the presentation
> language.
>
> OLD:
>    The following definitions are used throughout RELOAD and so are
>    defined here.  They also provide a convenient introduction to how to
>    read the presentation language.
> NEW:
>    This section provides an introduction to the presentation language
>    used throughout RELOAD.
>
> - Section 5.3.3.1: Error_Data_Too_Old is duplicated.
>
> - Section 5.5.1.6: Add references for SCTP and DCCP.
>
> - Section 6.4.1.3:  The reference to "this Version" is superfluous.
> Propose the following change:
> OLD:
>    This version of RELOAD (unlike previous versions) does not have an
>    explicit Remove operation.
> NEW:
>    RELOAD does not have an explicit Remove operation.
>
> - Section 9: General. The first sentence states that the algorithm define=
d
> here is referred to as "chord-reload", however, subsequent sections don't
> seem to use that term.  It would be more clear if that term was used. And=
,
> really, it would be more consistent to use the term Chord-RELOAD. However=
,
> this should also be consistent with the IANA-Registration which has
> CHORD-RELOAD.
>
> - Section 9.7.4.3, 3rd para:
> -- Remove "Note to implementers".  Text already highlights that the text =
is
> specific to implementations.
> -- "may be found" -> "can be found"
>
> - Section 9.8:  "For this topology plugin" -> "For Chord-RELOAD"
>
> - Section 10.2, 2nd para:  "determines" -> "determining"
>
> - Section 11:
> - General: there are no labels for any of the call flows, so it's not
> always clear what the text is referring to.  In general, I think the text
> precedes the flow.
> - "abbreviation" -> "abbreviations"
>
> - Section 13.16:
> --Interoperability considerations:  "knows" -> "known"
>
> - Section 14: "provied" -> "provided"
>
> - Appendix C: Delete now - it's totally useless as is.
>

--20cf307cffd8555b4a04aa1abbeb
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I&#39;m resending to try to capture one additional author (Henning) that bo=
unced and the Gen-ART mailing list. =A0I could not find a valid email for S=
alman Basset =A0Please reply to this email.<div><br></div><div>Thanks,</div=
>
<div>Mary.<br><br><div class=3D"gmail_quote">On Tue, Aug 9, 2011 at 6:05 PM=
, Mary Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:mary.ietf.barnes@gmai=
l.com">mary.ietf.barnes@gmail.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex;">
<div><div><br></div><div>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://wik=
i.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http://wik=
i.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.</div>

<div><br></div><div>Sorry for the delay, but a two week IETF-LC for a 150 p=
age document two weeks before an IETF meeting virtually ensures that the do=
cument =A0won&#39;t be carefully reviewed by the community and that directo=
rate reviews will are late ;) =A0 While this review was done specifically o=
n the -17, I have reviewed the diff and these comments still apply to the -=
18.</div>

<div><br></div><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D</div><div><br></div><div>Document: draft-ietf-p2psip-base-17</div=
><div>Reviewer: =A0Mary Barnes=A0</div><div>Review Date: =A09 August =A0201=
1</div>

<div>IETF LC End Date: 22 July 2011</div><div><br></div><div>Summary: Not R=
eady. =A0</div><div><br></div><div>Comments:</div><div>----------------</di=
v><div>The document is very a dense (with detailed technical information) a=
nd long (150 page) specification for a Peer-to-peer signaling protocol. =A0=
While the overall technical functionality seems fairly correct and thorough=
ly specified, the primary issue is a tremendous lack of normative language =
in the main body of the document. =A0Non-inclusive details of such are incl=
uded below. =A0</div>

<div><br></div><div>Major Issues:</div><div>-------------------</div><div><=
br></div><div>General:=A0</div><div>--There is a fair number of cases where=
 normative language should be used. =A0I have detailed some (but certainly =
not all) =A0instances where it is lacking with proposed rewording. =A0I hav=
e also noted cases where it is used (lower case) where it could be confused=
 with needing normative language and where it isn&#39;t necessary and there=
 are some cases where it&#39;s just not clear. I consider these major since=
 it can impact interoperability and could lead developers to not implement =
key functionality. =A0</div>

<div><br></div><div>--There is also little or no normative language for the=
 majority of the elements in the structures - i.e., the reader has to assum=
e which elements are mandatory and which are optional and it&#39;s not alwa=
ys clear. =A0 For example, rather than saying &quot;Field x contains blah&q=
uot;, it should say &quot;Field x MUST contain blah&quot; and rather than &=
quot;The contents of the message will be x, y and z&quot;, it should say so=
mething like &quot;The message MUST (or SHOULD) contain x, y and z&quot;. =
=A0I have not detailed the places where this is necessary in most cases. =
=A0The authors should review the detailed definition for each of the messag=
es.=A0</div>

<div><br></div><div>--The message names are used inconsistently. =A0The IAN=
A registry has the message codes all lower case. =A0There are places in the=
 examples and the body of the document where the _req part is missing, ther=
e is no &quot;_&quot;, the first letters are Upper case, etc. =A0The messag=
es are also used in a general sense - e.g., &quot;MUST perform an Attach&qu=
ot;, which should really be stated as &quot;MUST send an attach_req message=
)</div>

<div><br></div><div>Major - Detailed:</div><div><br></div><div>- Sections 3=
.2.1, 3.2.2 and 3.3: lots of changes needed to reword using normative langu=
age. =A0</div><div><br></div><div>- Section 3.4, last paragraph: Needs to b=
e reworded normatively and more precisely. It&#39;s really not clear to me =
what the required behavior is as it first says it needs to (which I&#39;m n=
ot sure is a SHOULD or is REQUIRED to) maintain connections to all the peer=
s near and enough others.., but how much is &quot;enough&quot;. =A0 Also, w=
hat is meant by the &quot;specified link set&quot; - is that referring to a=
ll the nearby peers or the peers+enough others? =A0Or is this more clearly =
(and normatively) specified elsewhere, such that a reference could be added=
. =A0</div>

<div><br></div><div>- Section 4.2: needs normative language - i.e.:</div><d=
iv>--&quot;Each Usage needs to =85&quot; -&gt; =A0&quot;Each Usage MUST=85&=
quot;</div><div><br></div><div>- Section 5.1.1: Bullet items need normative=
 language</div>

<div>-- 1st bullet: It&#39;s also =A0not clear what the its are in &quot;it=
 passes it up&quot;. =A0I think it should be &quot;the node passes the mess=
age up to the upper layers&quot;. =A0 However, this probably needs to be no=
rmative language - i.e., &quot;the node MUST pass the message to the upper =
layers&quot;. =A0The same applies to the third bullet.=A0</div>

<div>--bullet 2: =A0&quot;the message is destined for this node and is pass=
ed up=85&quot; -&gt; &quot;the message is destined for this node and MUST b=
e passed=85.,=A0</div><div><br></div><div>- Section 5.1.2:</div><div>-- Par=
agraphs 5, 6, 7 and 8 need to be reworded to have normative statements.=A0<=
/div>

<div>-- Last paragraph (9) mixes normative text with in an example. The nor=
mative text needs to be separated from the example - e.g., split some of th=
e sentences into the normative behavior and then the example.=A0</div><div>

<br></div><div>-Section 5.2.1 is totally inconsistent with the use of norma=
tive language (i.e., lower case occurrences and lack of KEY words) - should=
n&#39;t the following be normative statements something like the following:=
=A0</div>

<div>-- First paragraph:</div><div>---First sentence: =A0&quot;a node const=
ructs&quot; -&gt; &quot;a node MUST construct&quot;.</div><div>--- 3rd sent=
ence: &quot;resulting message will use the normal overlay routing&quot; -&g=
t; &quot;resulting message MUST use the normal overlay routing&quot;</div>

<div>--- 4th sentence: &quot;The node can also&quot; -&gt; =A0&quot;The nod=
e MAY also&quot;</div><div>-- Third paragraph:=A0</div><div>--- 3rd sentenc=
e: &quot;a single request can also&quot; -&gt; &quot;a single request MAY a=
lso&quot;</div>

<div>-- Fourth paragraph:</div><div>--- 1st sentence: this could be interpr=
eted as normative: =A0&quot;Because messages may&quot; -&gt; =A0&quot;Becau=
se messages can&quot;</div><div>--- 3rd sentence: =A0&quot;the request is r=
etransmitted&quot; -&gt; =A0&quot;the request MUST be retransmitted&quot;</=
div>

<div><br></div><div>-Section 5.3.2:=A0</div><div>-- General: some of the co=
ntents of the structure have normative language and others don&#39;t. =A0Th=
ere is some normative behavior defined for these fields later, so perhaps a=
dding section references as you do for some fields would be helpful. =A0</d=
iv>

<div><br></div><div>For example:=A0</div><div>--&quot;overlay&quot;: should=
n&#39;t this be normative: =A0&quot;the overlay name is hashed with SHA-1&q=
uot; -&gt; &quot;the overlay name MUST be hashed with SHA-1&quot;</div><div=
>

--&quot;destination_list&quot;: seems like some of this should be normative=
?=A0</div><div><br></div><div>-Section <a href=3D"http://5.3.2.1" target=3D=
"_blank">5.3.2.1</a>:</div><div>--1st paragraph: shouldn&#39;t this be norm=
ative?=A0</div>
<div>
&quot;the configuration document has a sequence number&quot; -&gt; =A0&quot=
;the configuration document MUST contain a sequence number&quot;</div><div>=
-- 1st paragraph, last sentence: &quot;may&quot; =A0-&gt; &quot;can&quot;=
=A0</div>

<div><br></div><div>-Section <a href=3D"http://5.3.2.2" target=3D"_blank">5=
.3.2.2</a>:</div><div>--Paragraph after the 1st structure: =A0Shouldn&#39;t=
 this be stated normatively since it is described how the structure MUST be=
 handled depending upon the contents? =A0</div>

<div>--Paragraph after second structure, suggest the following changes:</di=
v><div>---&quot;the generation counters should&quot; -&gt; =A0&quot;the gen=
eration counters SHOULD&quot;</div><div>---&quot;An implementation could us=
e..&quot; -&gt; &quot;An implementation MAY use=85&quot;</div>

<div>---&quot;the node confirms that the generation counter matches&quot; -=
&gt; &quot;the node MUST confirm that the generation counter matches&quot;<=
/div><div>---&quot;If it does not match, it is silently dropped.&quot; -&gt=
; &quot;If it does not match, it MUST be silently dropped.&quot;</div>

<div><br></div><div>-Section <a href=3D"http://5.3.3.1" target=3D"_blank">5=
.3.3.1</a>:</div><div>--1st para: &quot;a request returns&quot; -&gt; &quot=
;a request MUST return&quot;=A0</div><div>--1st para: &quot;then the messag=
e code is the response code that matches the request&quot; -&gt;=A0</div>

<div>&quot;then the message code MUST be set to the response code that matc=
hes the request&quot;</div><div>--2nd para: &quot;message code is set&quot;=
 -&gt; =A0&quot;message code MUST be set&quot;</div><div><br></div><div>
-Section 5.3.4 - needs normative language:</div>
<div>--1st paragraph after GenericCertificate structure:</div><div>---&quot=
;All signatures are formatted&quot; -&gt; &quot;Alls signatures MUST be for=
matted&quot;</div><div>---&quot;The input structure=85varies..&quot; -&gt; =
=A0&quot;The input structure =85 MAY vary=85&quot;</div>

<div><br></div><div>-Section 5.4.1: &quot;need to be described&quot; -&gt; =
&quot;MUST be described&quot;=A0</div><div><br></div><div>-Section 5.4.2-Se=
ction 7. =A0These sections need to be carefully reviewed and updated approp=
riately with normative text. =A0[ I have marks up for pages 55-102 where no=
rmative language is needed if someone wants those scanned and forwarded - I=
&#39;m just too lazy to type them all out.]=A0</div>

<div><br></div><div>- Section 8: =A0There is only one actual normative word=
 used in this section! =A0There is a lc &quot;should&quot; that ought to be=
 &quot;SHOULD&quot;. =A0I don&#39;t know if the authors assumed that the no=
rmative language in TURN was sufficient, but I do not believe that is the c=
ase as it leaves the normative behavior to be inferred by the reader/implem=
entor. Rather than rewrite the whole section myself, the authors need to re=
view carefully. For example, there are &quot;needs to&quot;, which likely a=
re really and lots of present tense statements (e.g., &quot;The address of =
the peer is stored=85&quot;), which ought to be MUSTs or SHOULDs.</div>

<div><br></div><div>- Section 9.2: =A0seems like this needs normative langu=
age. Suggest the following:</div><div>OLD:</div><div>=A0=A0 For this Chord =
based topology plugin, the size of the Resource-ID is</div><div>=A0=A0 128 =
bits. =A0The hash of a Resource-ID is computed using SHA-1</div>

<div>=A0=A0 [RFC3174]then truncating the SHA-1 result to the most significa=
nt 128</div><div>=A0=A0 bits.</div><div>NEW:</div><div>=A0=A0 For Chord-REL=
OAD, the size of the Resource-ID MUST be=A0</div><div>=A0=A0 128 bits. =A0T=
he hash of a Resource-ID MUST be computed using SHA-1</div>

<div>=A0=A0 [RFC3174]. =A0The SHA-1 result MUST be truncated to the most si=
gnificant=A0</div><div>=A0=A0 128 bits.</div><div><br></div><div>- Section =
9.3: Needs normative language.=A0</div><div>OLD:=A0</div><div>=A0=A0 If a p=
eer is not responsible for a Resource-ID k, but is directly</div>

<div>=A0=A0 connected to a node with Node-ID k, then it routes the message =
to</div><div>=A0=A0 that node. =A0Otherwise, it routes the request to the p=
eer in the</div><div>=A0=A0 routing table that has the largest Node-ID that=
 is in the interval</div>

<div>=A0=A0 between the peer and k. =A0If no such node is found, it finds t=
he</div><div>=A0=A0 smallest Node-Id that is greater than k and routes the =
message to</div><div>=A0=A0 that node.</div><div>NEW:=A0</div><div>=A0=A0 I=
f a peer is not responsible for a Resource-ID k, but is directly</div>

<div>=A0=A0 connected to a node with Node-ID k, then it MUST route the mess=
age to</div><div>=A0=A0 that node. =A0Otherwise, it MUST route the request =
to the peer in the</div><div>=A0=A0 routing table that has the largest Node=
-ID that is in the interval</div>

<div>=A0=A0 between the peer and k. =A0If no such node is found, it MUST fi=
nd the</div><div>=A0=A0 smallest Node-Id that is greater than k and MUST ro=
ute the message to</div><div>=A0=A0 that node.</div><div><br></div><div>- S=
ection 9.4: Needs normative language. =A0</div>

<div><br></div><div>- Section 9.5: While this section does have a fair amou=
nt of normative language, it is still lacking in a few cases:=A0</div><div>=
--Item 2.: =A0&quot;should&quot; -&gt; &quot;SHOULD&quot;</div><div>--Item =
5.: =A0&quot;The AP sends the response=85&quot; -&gt; &quot;The AP MUST sen=
d the response=85&quot;=A0</div>

<div>--1st paragraph after list: &quot;=85can directly connect=85&quot; -&g=
t; &quot;MAY directly connect&quot;</div><div>--2nd paragraph after list: &=
quot;it can still populate&quot; -&gt; &quot;it MAY still populate&quot;</d=
iv>

<div>--2nd paragraph after list: the description of the use of PING should =
be reworded with normative language (I&#39;ll leave that exercise to the au=
thors)</div><div>--3rd paragraph after the list: =A0&quot;JP simply sends&q=
uot; -&gt; &quot;JP MUST send&quot;=A0</div>

<div><br></div><div>- Section 9.7.1:</div><div>--1st para: =A0&quot;.., it =
then sends=85&quot; -&gt; &quot;.., it then MUST send =85&quot;</div><div>-=
-3rd para: needs normative language</div><div>OLD:</div><div>=A0=A0 In no e=
vent does</div>

<div>=A0=A0 an attempt to reestablish connectivity with a lost neighbor all=
ow the</div><div>=A0=A0 peer to remain in the neighbor table.=A0</div><div>=
NEW:=A0</div><div>=A0=A0 In the case of=A0</div><div>=A0=A0 an attempt to r=
eestablish connectivity with a lost neighbor, the peer=A0</div>

<div>=A0=A0 MUST not remain in the neighbor table.=A0</div><div>OR:=A0</div=
><div>=A0=A0 In the case of=A0</div><div>=A0=A0 an attempt to reestablish c=
onnectivity with a lost neighbor, the peer=A0</div><div>=A0=A0 MUST be remo=
ved from the neighbor table.</div>

<div>-- 4th para: &quot;should&quot; -&gt; &quot;SHOULD&quot; (2 cases), =
=A0&quot;use Pings&quot; -&gt; &quot;MUST use Pings&quot;</div><div><br></d=
iv><div>-Section 9.7.2:</div><div>--1st para: =A0&quot;..the failed peer ar=
e removed..&quot; -&gt; &quot;=85the failed peer MUST be removed..&quot;</d=
iv>

<div>--2nd para: =A0&quot;=85the peer initiates=85&quot; -&gt; &quot;=85the=
 peer MUST initiate..&quot;</div><div><br></div><div>-Section 9.7.3:</div><=
div>--1st para after list: =A0&quot;is needed&quot; -&gt; &quot;is REQUIRED=
&quot;</div>

<div>--3rd para after list: =A0&quot;the peer sends an Update&quot; -&gt; &=
quot;the peer MUST send an Update&quot;</div><div><br></div><div>-Section <=
a href=3D"http://9.7.4.4" target=3D"_blank">9.7.4.4</a>: =A0Needs a scrub f=
or normative language</div>

<div><br></div><div>-Section 9.9: Needs a scrub for normative language.=A0<=
/div><div><br></div><div>-Section 10.1: General: Needs a lot of work to be =
specified using normative language. =A0The majority of the configuration el=
ements are not specified using normative language - for example, terms such=
 as permitted, allowed, valid are used in statements rather than normative =
language</div>

<div>or they are indicative of the need for normative language. =A0A specif=
ic example is in the definition for &quot;clients-permitted&quot;:</div><di=
v><br></div><div>OLD:</div><div>=A0=A0 =A0 =A0This element represents wheth=
er clients are</div>

<div>=A0=A0 =A0 =A0permitted or whether all nodes must be peers. =A0If it i=
s set to</div><div>=A0=A0 =A0 =A0&quot;true&quot; or absent, this indicates=
 that clients are permitted. =A0If</div><div>=A0=A0 =A0 =A0it is set to &qu=
ot;false&quot; then nodes are not allowed to remain clients</div>

<div>=A0=A0 =A0 =A0after the initial join.=A0</div><div><br></div><div>NEW:=
=A0</div><div>=A0=A0 =A0 =A0This element represents whether clients are</di=
v><div>=A0=A0 =A0 =A0permitted or whether all nodes need to be peers. =A0If=
 clients=A0</div><div>=A0=A0 =A0 =A0are permitted, the element MUST be set =
to &quot;true&quot; or absent. =A0</div>

<div>=A0=A0 =A0 =A0If the nodes are not allowed to remain clients after the=
=A0</div><div>=A0=A0 =A0 =A0initial join, the element MUST be set to &quot;=
false&quot;.</div><div><br></div><div>--Section 10.1 - 4th para after the e=
lement list states that &quot;All of the non optional values MUST be provid=
ed&quot;. =A0However, the list of elements in the previous paragraph are no=
t specifically identified as non optional. =A0I think the first 3 are manda=
tory. =A0So, I would suggest to re-word the 3rd paragraph as follows and de=
lete the 1st sentence in the 4th paragraph noted above:=A0</div>

<div>OLD:</div><div>=A0=A0 In addition, the kind element contains the follo=
wing elements:</div><div>=A0=A0 max-count: =A0the maximum number of values =
which members of the overlay</div><div>=A0=A0 =A0 =A0must support.</div><di=
v>=A0=A0 data-model: =A0the data model to be used.</div>

<div>=A0=A0 max-size: =A0the maximum size of individual values.</div><div>=
=A0=A0 access-control: =A0the access control model to be used.</div><div>=
=A0=A0 max-node-multiple: =A0This is optional and only used when the access=
</div><div>=A0=A0 =A0 =A0control is NODE-MULTIPLE. =A0This indicates the ma=
ximum value for</div>

<div>=A0=A0 =A0 =A0the i counter. =A0This is an integer greater than 0.</di=
v><div><br></div><div>NEW:=A0</div><div>=A0=A0 In addition, the kind elemen=
t MUST contain the following elements:</div><div>=A0=A0 max-count: =A0the m=
aximum number of values which members of the overlay</div>

<div>=A0=A0 =A0 =A0must support.</div><div>=A0=A0 data-model: =A0the data m=
odel to be used.</div><div>=A0=A0 max-size: =A0the maximum size of individu=
al values.</div><div>=A0=A0 access-control: =A0the access control model to =
be used.</div><div><br>

</div><div>=A0=A0 The kind element MAY also contain the following element:<=
/div><div>=A0=A0 max-node-multiple: =A0if the access control is NODE-MULTIP=
LE,=A0</div><div>=A0=A0 =A0 =A0this element MAY be included. This indicates=
 the maximum value for</div>

<div>=A0=A0 =A0 =A0the i counter. =A0It MUST be an integer greater than 0. =
=A0=A0</div><div><br></div><div>--Section 10.1, next to last para: There&#3=
9;s no normative language, but it seems there should be since it is specify=
ing specification computations and encoding that I believe are required.=A0=
</div>

<div><br></div><div>- Section 10.2: =A0Needs more normative language:</div>=
<div><br></div><div>-- 2nd para:=A0</div><div>OLD: This value is provided b=
y the user or some other out of band=A0</div><div>=A0=A0 =A0 provisioning m=
echanism.</div>

<div><br></div><div>NEW: This value MUST be provided by the user or some ot=
her out of band=A0</div><div>=A0=A0 =A0 provisioning mechanism.&quot;</div>=
<div><br></div><div>-- 3rd para:=A0</div><div>OLD: =A0</div><div>=A0=A0 Onc=
e an address and URL for the configuration server is determined,</div>

<div>=A0=A0 the peer forms an HTTPS connection to that IP address.=A0</div>=
<div>NEW:=A0</div><div>=A0=A0 Once an address and URL for the configuration=
 server is determined,</div><div>=A0=A0 the peer MUST form an HTTPS connect=
ion to that IP address.=A0</div>

<div><br></div><div>-- 4th para: =A0&quot;which replaces&quot; -&gt; =A0&qu=
ot;which MUST replace&quot;</div><div><br></div><div>-- 5th para: =A0&quot;=
nodes obtain the&quot; -&gt; &quot;nodes MUST obtain the&quot;</div><div><b=
r>

</div><div>- Section 10.3:=A0</div><div>-- 3rd para: =A0&quot;is performed&=
quot; -&gt; &quot;MUST be performed&quot;. =A0</div><div>-- 3rd para: Bulle=
ts need to be modified to normative.=A0</div><div>-- 4th para: &quot;the ce=
rtificate contains&quot; -&gt; &quot;the certificate MUST contain&quot;</di=
v>

<div>-- para after 2nd set of bullets: =A0needs normative language.</div><d=
iv>-- 2nd para after 2nd set of bullets: =A0&quot;The node then reads=85&qu=
ot; -&gt; =A0&quot;The node MUST then use=85&quot;</div><div><br></div><div=
>- Section 10.5:</div>

<div>--Second para: &quot;the joining node first forms&quot; -&gt; &quot;th=
e joining node MUST first form&quot;</div><div>--3rd para: =A0text uses the=
 phrase &quot;it can note the Node-ID in the response and use this Node-ID =
to start sending requests&quot;. =A0It&#39;s not clear whether the use of t=
he Node-ID is a MAY or a MUST. =A0</div>

<div><br></div><div>- Section 12. I&#39;m assuming that the security direct=
orate has reviewed this in detail, thus my focus in reviewing this section =
was on general understanding. The biggest issues is that there is NO normat=
ive language at all in the security section. =A0As in other sections, terms=
 like &quot;need&quot;, &quot;are/is used/sent, etc.&quot;, =A0&quot;ensure=
&quot;, lower case reserved words rather than upper case, etc. are used whe=
n normative language ought to have been used.=A0</div>

<div><br></div><div><br></div><div>- Section 13. IANA Registrations:</div><=
div>- General: there seem to be several registries for which the usage/requ=
irement is unclear as there&#39;s no mention of such in the body of the doc=
ument. =A0In general, references to the sections in the document describing=
 the information included in the registries would be more than helpful.</di=
v>

<div><br></div><div>- Section 13.5: Creates a RELOAD Application Registry, =
but the use and need for such isn&#39;t described elsewhere in the document=
.=A0</div><div><br></div><div>- Section 13.12. Forwarding Options Registry.=
 SEction 5.3.2.3 seems to define three flags for the Forwarding options typ=
e, so it&#39;s not clear to me why this registry has just &quot;invalid&quo=
t; and &quot;reserved&quot;</div>

<div><br></div><div><br></div><div>- Section 13.15: =A0Defines/registers a =
RELOAD URI schema but there is no mention of this URI anywhere else in the =
document. =A0In what context is it used? =A0 =A0</div><div>=A0=A0 =A0 =A0 =
=A0</div><div>
<br>
</div><div>Minor =A0Issues:</div><div>---------------------</div><div><br><=
/div><div>- Section 1.2.1, 2nd paragraph: I don&#39;t understand the exampl=
e as to why a single application requires multiple usages - i.e, why voicem=
ail? =A0Isn&#39;t the intent to say that an application might need to use b=
oth SIP and XMPP - i.e., you wouldn&#39;t define a &quot;usage&quot; for an=
 application, would you? =A0=A0</div>

<div><br></div><div>- Section 2. Some of the definitions use terms that are=
 not yet defined, so that&#39;s not particularly helpful - i.e,. Attach and=
 Update are used. In some cases (e.g., Connection Table), you could just de=
lete the statement with the reference.=A0</div>

<div><br></div><div>- Section 3.3, last paragraph. =A0Add a reference to 5.=
4.2.4 =A0after &quot;RouteQuery method&quot;</div><div><br></div><div>- Sec=
tion 5.1: &quot;If any of these are incorrect=85&quot; =A0- need to specify=
 what qualifies as &quot;incorrect&quot; - is it wrong formatting, invalid =
header field=A0</div>

<div>value, etc.?</div><div><br></div><div>- Section 5.1.2:</div><div>--1st=
 paragraph: I have no idea what the &quot;other three cases&quot; reference=
s.=A0</div><div><br></div><div>- Section 5.2: &quot;may be configured&quot;=
 -&gt; &quot;can be configured&quot;, =A0&quot;alternative=A0</div>

<div>routing algorithms may be selected&quot; -&gt; &quot;alternative routi=
ng algorithms MAY be selected&quot;</div><div><br></div><div>- Section 5.3:=
 =A0The three parts of the messages are listed and the last sentence says t=
hat &quot;The following sections describe the format of each part of the me=
ssage&quot;, but there are 4 sub-sections in 5.3, with the first section NO=
T describing one of the three parts of the messages. =A0I suggest to strike=
 that last sentence and just put references to the sections in the list ite=
ms for each of the three messages.=A0</div>

<div><br></div><div>-Section 5.3.3:=A0</div><div>--&quot;critical&quot; des=
cription: =A0&quot;Whether this extension must be..&quot; &quot;Whether thi=
s extension needs to be=85&quot;=A0</div><div><br></div><div>-Section 5.3.4=
: =A01st para after certificate structure: =A0&quot;may contain&quot; -&gt;=
 &quot;MAY contain&quot;=A0</div>

<div><br></div><div>-Section 5.5: It would be helpful to highlight that fou=
ndation, priority and type are based on ICE, in particular since ICE is not=
 discussed until the subsequent section - e.g., &quot;the foundation produc=
tion&quot; -&gt; &quot;the ICE foundation production&quot;.=A0</div>

<div><br></div><div>- Section 5.6: =A0</div><div>-- The last three paragrap=
hs are confusing.=A0</div><div>---In particular, it&#39;s not clear what al=
gorithms are being referenced in this sentence:</div><div>=A0=A0&quot;We wi=
ll first define each of these algorithms, then</div>

<div>=A0=A0 define overlay link protocols that use them.&quot;</div><div>--=
- In the note paragraph, I believe &quot;These protocols have been chosen=
=85&quot; is referring to the three overlay link protocols supported by REL=
OAD per this document.</div>

<div>---The Note to implementors paragraph seems out of context</div><div>-=
-- Per my next comment, I suggest to move the detailed discussion of future=
 overlay link protocols to the appendix, so some of this text may be releva=
nt only to that.=A0</div>

<div><br></div><div>-Section 5.6.1: =A0I suggest that the sub-sections in t=
his section be moved to an appendix and a reference to such be added.=A0</d=
iv><div><br></div><div>-Section 5.6.3.1.1, next to the last paragraph:</div=
>

<div>&quot;when a link may be failing&quot; -&gt; &quot;when a link might b=
e failing&quot;</div><div><br></div><div>- Section 9.1: While this is an ov=
erview, it seems to me that some of this is describing normative behavior (=
that I don&#39;t see specified else). =A0Per the general comment, I would r=
eword the first sentence as follows:=A0</div>

<div>OLD:</div><div>=A0=A0 The algorithm described here is a modified versi=
on of the Chord</div><div>=A0=A0 algorithm.</div><div>NEW:</div><div>=A0=A0=
 =A0The algorithm described here, Chord-RELOAD is a modified version=A0</di=
v><div>=A0=A0 =A0of the Chord algorithm.</div>

<div><br></div><div>- Section 10.3, 1st para: =A0&quot;required&quot; -&gt;=
 &quot;REQUIRED&quot;</div><div><br></div><div>- Section 10.3.1, last sente=
nce: &quot;must&quot; =A0-&gt; &quot;MUST&quot;</div><div><br></div><div>- =
Section 10.4, 1st para, last sentence: &quot;should use&quot; -&gt; &quot;S=
HOULD use&quot;</div>

<div><br></div><div>- Section 11 - examples:</div><div>--General - there ar=
e no detailed messages shown anywhere for the examples. There should be at =
least one, in particular given the comment above about the RELOAD URI that =
is registered, but not mentioned anywhere else in the document.=A0</div>

<div>--first example (see my nit below about the examples not being numbere=
d or labeled in any way): =A0The third sentence says that &quot;It gets rou=
ted to the admitting peer (AP), yet the flow shows that the message first g=
ets routed to the PP and then onto AP. It would be helpful if that were cla=
rified.=A0</div>

<div>- =A0Also (general), the text mentions the use of ICE. =A0It&#39;s not=
 clear to me exactly where in the flow that happens - it would be good to a=
nnotate such (i.e., in a similar manner as the TLS is illustrated).=A0</div=
>
<div>
- next to the last example (text on page 131, diagram on page 132): I&#39;m=
 quite confused as the text states that JP has received an update from AP a=
nd thus now knows APs predecessors, which are also JP&#39;s predecessors, s=
o JP Attaches to them. However, the diagram does not show JP getting an Upd=
ate from AP and it shows JP doing Updates to PPP and PP rather than Attache=
s (as the text suggests). =A0</div>

<div><br></div><div>- Section 13.10. Overlay link types: These specific str=
ing types are not used elsewhere in the document. =A0Suggest that a referen=
ce to 5.6 be added and these particular strings be included in parenthesis =
after the items in the list. =A0</div>

<div><br></div><div><br></div><div>- Section 13.16, Security considerations=
 portion:=A0</div><div>-- The first sentence doesn&#39;t make sense. Did yo=
u mean?=A0</div><div>=A0=A0 &quot;This media type is typically not used to<=
/div>

<div>=A0=A0 transport information that needs to be kept confidential,=A0</d=
iv><div>=A0=A0 however, there are cases where the integrity of the informat=
ion is</div><div>=A0=A0 important.&quot;</div><div>-- &quot;then the conten=
ts of the file need to be=85&quot; -&gt; &quot;then the contents of the fil=
e MUST be =85&quot; =A0=A0</div>

<div><br></div><div><br></div><div><br></div><div>Nits:</div><div>-----</di=
v><div>- General: kind is sometimes &quot;Kind&quot; and sometimes &quot;ki=
nd&quot;. =A0The former is more readable and highlights it as a reserved wo=
rd.=A0</div>

<div><br></div><div>- Section 2. =A0</div><div>--General: It would be helpf=
ul if the terms were alphabetized.=A0</div><div>--Node: &quot;We use the te=
rm &quot;Node&quot; to refer to =85&quot; -&gt; &quot;Refers to =85&quot;</=
div>

<div><br></div><div>- Section 3.2:</div><div>-- 2nd para, last sentence: =
=A0&quot;refer such&quot; -&gt; &quot;refer to such&quot;</div><div>-- 3rd =
para, 1st sentence: =A0&quot;concept&quot; -&gt; &quot;entity&quot;</div><d=
iv>

<br></div><div>- Section 4.1.4, 4th paragraph: I&#39;m still not getting th=
e applicability of voicemail as a RELOAD Kind (per the reference also in se=
ction 1.2.1). =A0I guess you are talking about a voicemail message (in this=
 case) and a server or application in section 1.2.1? =A0 Voicemail just doe=
s not seem like an obvious example to me. =A0</div>

<div><br></div><div>- Section 5.1.1, last bullet: =A0&quot;In that case,=85=
&quot; -&gt; =A0&quot;In the latter case, =85&quot;=A0</div><div><br></div>=
<div>- Section 5.1.2:</div><div>-- 2nd para: =A0&quot;arrange&quot; -&gt; &=
quot;ensure&quot;, =A0&quot;This may be arranged&quot; -&gt; &quot;This can=
 be arranged=85&quot;=A0</div>

<div>-- 3rd para (1st after bullets): It&#39;s not clear that A=85E is a se=
t of ordered nodes in the example. I would suggest to reword as:</div><div>=
OLD:</div><div>=A0=A0 As an example of the first strategy, if node D=A0</di=
v><div>

NEW:=A0</div><div>=A0=A0Consider an example with nodes A, B, C, D and E, re=
spectively. =A0If=A0</div><div>=A0=A0node D=85.</div><div><br></div><div>- =
Section <a href=3D"http://5.3.1.1" target=3D"_blank">5.3.1.1</a>: First two=
 sentences can be reworded more succinctly - you&#39;re not really providin=
g definitions here, put rather describing the=A0</div>

<div>the syntax for and providing examples illustrative of the presentation=
 language.=A0</div><div><br></div><div>OLD:=A0</div><div>=A0=A0 The followi=
ng definitions are used throughout RELOAD and so are</div><div>=A0=A0 defin=
ed here. =A0They also provide a convenient introduction to how to</div>

<div>=A0=A0 read the presentation language.</div><div>NEW:=A0</div><div>=A0=
=A0 This section provides an introduction to the presentation language</div=
><div>=A0=A0 used throughout RELOAD.=A0</div><div><br></div><div>- Section =
<a href=3D"http://5.3.3.1" target=3D"_blank">5.3.3.1</a>: Error_Data_Too_Ol=
d is duplicated.</div>

<div><br></div><div>- Section <a href=3D"http://5.5.1.6" target=3D"_blank">=
5.5.1.6</a>: Add references for SCTP and DCCP.=A0</div><div><br></div><div>=
- Section <a href=3D"http://6.4.1.3" target=3D"_blank">6.4.1.3</a>: =A0The =
reference to &quot;this Version&quot; is superfluous. Propose the following=
 change:</div>

<div>OLD:</div><div>=A0=A0 This version of RELOAD (unlike previous versions=
) does not have an</div><div>=A0=A0 explicit Remove operation.</div><div>NE=
W:=A0</div><div>=A0=A0 RELOAD does not have an explicit Remove operation.</=
div><div>
<br>
</div><div>- Section 9: General. The first sentence states that the algorit=
hm defined here is referred to as &quot;chord-reload&quot;, however, subseq=
uent sections don&#39;t seem to use that term. =A0It would be more clear if=
 that term was used. And, really, it would be more consistent to use the te=
rm Chord-RELOAD. However, this should also be consistent with the IANA-Regi=
stration which has CHORD-RELOAD.=A0</div>

<div><br></div><div>- Section 9.7.4.3, 3rd para:=A0</div><div>-- Remove &qu=
ot;Note to implementers&quot;. =A0Text already highlights that the text is =
specific to implementations.=A0</div><div>-- &quot;may be found&quot; -&gt;=
 &quot;can be found&quot;</div>

<div><br></div><div>- Section 9.8: =A0&quot;For this topology plugin&quot; =
-&gt; &quot;For Chord-RELOAD&quot;</div><div><br></div><div>- Section 10.2,=
 2nd para: =A0&quot;determines&quot; -&gt; &quot;determining&quot;</div><di=
v>

<br></div><div>- Section 11:=A0</div><div>- General: there are no labels fo=
r any of the call flows, so it&#39;s not always clear what the text is refe=
rring to. =A0In general, I think the text precedes the flow.=A0</div><div>-=
 &quot;abbreviation&quot; -&gt; &quot;abbreviations&quot;=A0</div>

<div><br></div><div>- Section 13.16:</div><div>--Interoperability considera=
tions: =A0&quot;knows&quot; -&gt; &quot;known&quot;=A0</div><div><br></div>=
<div>- Section 14: &quot;provied&quot; -&gt; &quot;provided&quot;</div><div=
>

<br></div><div>- Appendix C: Delete now - it&#39;s totally useless as is.</=
div></div>
</blockquote></div><br></div>

--20cf307cffd8555b4a04aa1abbeb--

From hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com  Tue Aug  9 21:55:31 2011
Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C3BA21F8751; Tue,  9 Aug 2011 21:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.548, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cMmzp8Ma00PB; Tue,  9 Aug 2011 21:55:31 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id E611121F874E; Tue,  9 Aug 2011 21:55:30 -0700 (PDT)
Received: by pzk33 with SMTP id 33so2307173pzk.18 for <multiple recipients>; Tue, 09 Aug 2011 21:56:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0Ga0EMu1BSyXLc9Xe8Je5MK5XVYDzrrcFVzEFlbdyYs=; b=sL3QFUxkP9foUBu/njSEznLvOB1ffSZdWfDQglFUsOE2LO3zYOSqvRW88A0imiks9Z S6ts42sF+J5b6G64FsSWImGeUneqgdknHMtxIRHwCWY3k6ajP0vL/mcUvPSNWVv+Y1Bl r0+X53Y8bsO8k5I0YUXSU6m14g8G4hyKUfwEA=
Received: by 10.143.20.12 with SMTP id x12mr3614243wfi.105.1312952161163; Tue, 09 Aug 2011 21:56:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.157.2 with HTTP; Tue, 9 Aug 2011 21:55:41 -0700 (PDT)
In-Reply-To: <4E412DD3.4050404@net-zen.net>
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com> <4E40CE36.2000806@net-zen.net> <m2ipq73ypj.wl%randy@psg.com> <FC3BAAFB-626D-4937-8304-BBA327917ECF@bogus.com> <4E412DD3.4050404@net-zen.net>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Wed, 10 Aug 2011 06:55:41 +0200
Message-ID: <CAHhFybrBDdj9v0rRxdwjeen5rL3c2=yaF_ORDe3FGhqiMXuPfQ@mail.gmail.com>
Subject: Re: [xml2rfc] Multiple authors in reference
To: Glen Zorn <gwz@net-zen.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 04:55:31 -0000

On 9 August 2011 14:53, Glen Zorn wrote:

> A reasonable place to put this rule (if you wanted to make it a rule)
> might have been RFC 5741 but it doesn't seem to be there.

If you insist on it RFC 5741 (thanks, I didn't know it) has a reference
to <http://www.rfc-editor.org/styleguide.html>.  Admittedly I don't get
why the obscure case of more than five authors is so interesting here:

The really problematic cases are less than one author.

-Frank

From mrex@sap.com  Tue Aug  9 22:00:04 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3C0E21F8500 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 22:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.987
X-Spam-Level: 
X-Spam-Status: No, score=-9.987 tagged_above=-999 required=5 tests=[AWL=0.262,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FromDcQQwv6Y for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 22:00:04 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id E232721F84DC for <ietf@ietf.org>; Tue,  9 Aug 2011 22:00:03 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p7A50U3D010871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 10 Aug 2011 07:00:30 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108100500.p7A50TdF018207@fs4113.wdf.sap.corp>
Subject: Re: subject_prefix on IETF Discuss?
To: barryleiba@computer.org (Barry Leiba)
Date: Wed, 10 Aug 2011 07:00:29 +0200 (MEST)
In-Reply-To: <CAC4RtVBso47fhsPJ6X0ja4Y0kn5fMoFFMk0cE3V7mJ4dhdNLuA@mail.gmail.com> from "Barry Leiba" at Aug 9, 11 02:56:55 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 05:00:04 -0000

Barry Leiba wrote:
> 
> On Tue, Aug 9, 2011 at 1:16 PM, Martin Rex <mrex@sap.com> wrote:
> > If one intends to actually *process* close to all of the Emails hitting
> > one's inbox in near real time, then List-Id:, and any pre-sorting based
> > on it, will _always_ slow down processing (unless the MUA or the processing
> > is flawed).
> >
> > Whereas a subject prefix significantly facilitates tracking of stuff
> > in a single large inbox.  I'm getting 300+/day Emails and try to read >95%
> > of it (my company internal Email is completely seperate at ~30/day, though).
> 
> This makes no sense to me, Martin.  Please explain why sorting based
> on a subject prefix will work, while sorting based on a List-ID header
> field will not.

I do not sort EMail at all (my MUA does not support sorting).
subject_prefix _obviates_ sorting.

MUAs typically display the inbox with (status,sender,subject,received-time).

With subject_prefix I can quite easily tell apart discussions from several
IETF mailing lists, and it works with _every_ MUA with default settings.

-Martin

From evnikita2@gmail.com  Tue Aug  9 22:05:40 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAFD21F8546; Tue,  9 Aug 2011 22:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.361
X-Spam-Level: 
X-Spam-Status: No, score=-3.361 tagged_above=-999 required=5 tests=[AWL=0.238,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1J8apbhrbq6c; Tue,  9 Aug 2011 22:05:39 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 34A9221F8540; Tue,  9 Aug 2011 22:05:39 -0700 (PDT)
Received: by fxe6 with SMTP id 6so706871fxe.31 for <multiple recipients>; Tue, 09 Aug 2011 22:06:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+0d+5tn6r1qQexuihObMfI0byILN7oFqYJgk1EPhtkQ=; b=rX/zJOx7WxnRZBxqTrIiiGSUbDiQ286NCXAUpVR9OWP+Pqs0IfVtb3mWc+vSPy5zGS Bcr1yQEWCqyyC63+RcTLXjT40/0XERK007X2EY2obh7N7DkpjRxnj0FgxT1MeX0znqvH VdLaN/93/oQi/SAYm7zCqnWqNNnGZfn1rPN7s=
Received: by 10.223.9.217 with SMTP id m25mr10356216fam.122.1312952769197; Tue, 09 Aug 2011 22:06:09 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id r4sm464105fam.10.2011.08.09.22.06.06 (version=SSLv3 cipher=OTHER); Tue, 09 Aug 2011 22:06:07 -0700 (PDT)
Message-ID: <4E4211E5.6060301@gmail.com>
Date: Wed, 10 Aug 2011 08:06:45 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Subject: Re: [xml2rfc] Multiple authors in reference
References: <4E3F9E70.6080204@250bpm.com> <m2liv46zs5.wl%randy@psg.com> <4E40CE36.2000806@net-zen.net> <m2ipq73ypj.wl%randy@psg.com> <FC3BAAFB-626D-4937-8304-BBA327917ECF@bogus.com> <4E412DD3.4050404@net-zen.net> <CAHhFybrBDdj9v0rRxdwjeen5rL3c2=yaF_ORDe3FGhqiMXuPfQ@mail.gmail.com>
In-Reply-To: <CAHhFybrBDdj9v0rRxdwjeen5rL3c2=yaF_ORDe3FGhqiMXuPfQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 05:05:40 -0000

10.08.2011 7:55, Frank Ellermann wrote:
> On 9 August 2011 14:53, Glen Zorn wrote:
>
>> A reasonable place to put this rule (if you wanted to make it a rule)
>> might have been RFC 5741 but it doesn't seem to be there.
> If you insist on it RFC 5741 (thanks, I didn't know it) has a reference
> to<http://www.rfc-editor.org/styleguide.html>.  Admittedly I don't get
> why the obscure case of more than five authors is so interesting here:

Please note that eg. RFC 4357 has 12 authors and only 3 of them listed 
in the header.  These 3 occur in the reference.  RFC Editor, when 
preparing the draft for publication, settles this issue with all 
declared authors.

Some obscure cases happened, for instance, RFC 2989, which has nearly 20 
authors listed in the header.  They all occur in the official format of 
the reference.  The current practice is to list not more than 5 authors, 
but in exceptional cases all will be kept.  Correspondingly, as an 
answer to the question which started this topic, one is obliged to list 
all authors listed in the header in the Reference section.  So I see no 
real problem here.

Mykyta

> The really problematic cases are less than one author.
>
> -Frank
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



From gwz@net-zen.net  Tue Aug  9 23:01:40 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7733521F86D8 for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 23:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnv9GedUHw6j for <ietf@ietfa.amsl.com>; Tue,  9 Aug 2011 23:01:40 -0700 (PDT)
Received: from smtpauth17.prod.mesa1.secureserver.net (smtpauth17.prod.mesa1.secureserver.net [64.202.165.29]) by ietfa.amsl.com (Postfix) with SMTP id E8F5E21F86D7 for <ietf@ietf.org>; Tue,  9 Aug 2011 23:01:39 -0700 (PDT)
Received: (qmail 9301 invoked from network); 10 Aug 2011 06:02:09 -0000
Received: from unknown (124.120.242.122) by smtpauth17.prod.mesa1.secureserver.net (64.202.165.29) with ESMTP; 10 Aug 2011 06:02:06 -0000
Message-ID: <4E421ED5.9050004@net-zen.net>
Date: Wed, 10 Aug 2011 13:01:57 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Wes Hardaker <wjhns1@hardakers.net>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <4E3ED22B.3060405@qualcomm.com> <4E3F7B08.4000209@net-zen.net> <sdd3gefxik.fsf@wjh.hardakers.net>
In-Reply-To: <sdd3gefxik.fsf@wjh.hardakers.net>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------090503050106060701040307"
Cc: Pete Resnick <presnick@qualcomm.com>, iaoc-mtgs@ISOC.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 06:01:40 -0000

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

On 8/9/2011 9:52 PM, Wes Hardaker wrote:

>>>>>> On Mon, 08 Aug 2011 12:58:32 +0700, Glen Zorn <gwz@net-zen.net> said:
> 
> GZ> In any case, a taxi from any of the hotels on the list would today
> GZ> cost < $3 (probably closer to $2) one way.
> 
> I'd argue that group shuttles, as has been done in the past, is probably
> a better option than trying to have 1000 people even share taxi rides.

There are 7 pages of "official hotels".  Some might have shuttles many
won't.  In addition traffic is such that a shuttle might take a very
long time, since bus drivers tend in my experience to follow set routes
rather than routing around congestion (of which there is a lot ;-).  In
any case, I would say that public transportation would likely be the
best alternative unless the hotel in question is very close and you
don't mind the adventure of walking. Currently the price of a 15 trip
pass on BTS (the SkyTrain) is Bht 350 (about $11.66); a 3 day pass on
MRT (the subway -- QSNCC is on the subway) is ~$7.33, so about $30 would
basically take care of travel expenses for the week...

--------------090503050106060701040307
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------090503050106060701040307--

From gwz@net-zen.net  Wed Aug 10 00:16:31 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7064F21F86C2 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 00:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eKGLHJhJioX6 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 00:16:30 -0700 (PDT)
Received: from p3plsmtpa01-02.prod.phx3.secureserver.net (p3plsmtpa01-02.prod.phx3.secureserver.net [72.167.82.82]) by ietfa.amsl.com (Postfix) with SMTP id D0EC421F863A for <ietf@ietf.org>; Wed, 10 Aug 2011 00:16:29 -0700 (PDT)
Received: (qmail 27916 invoked from network); 10 Aug 2011 07:16:59 -0000
Received: from unknown (124.120.242.122) by p3plsmtpa01-02.prod.phx3.secureserver.net (72.167.82.82) with ESMTP; 10 Aug 2011 07:16:59 -0000
Message-ID: <4E423064.10604@net-zen.net>
Date: Wed, 10 Aug 2011 14:16:52 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <4E40CD13.3020904@net-zen.net> <E7FB3C1E-D298-4357-9965-8492AC758B42@softarmor.com>
In-Reply-To: <E7FB3C1E-D298-4357-9965-8492AC758B42@softarmor.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------090805010301070604040705"
Cc: Mark Nottingham <mnot@mnot.net>, Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 07:16:31 -0000

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

On 8/10/2011 5:12 AM, Dean Willis wrote:
...

> Y'all come on down to Dallas. It was 39C while I was walking the dog
> last night, down from the daily peak of about 44C. We're looking
> forward to October, when the highs should drop to 32C. And the lows
> to around zero .... pack a sweater.
> 
> And yep, I'm probably a flabby, nigh-on-fiftyish average IETF
> attendee. We're tougher than you think, Ole!
> 
> On the other hand, 22 hours of air travel is pretty much close to
> fatal.

My total travel time home from QC was ~32 hours.  I lived...

> 
> Whatever happened to bunk beds on planes?

Or seats designed for adults rather than children, for that matter?

> 
> Couldn't we just rent a university building in Hawaii? That's sort of
> a midway point between everything. Classroom chairs can't be any
> worse than Hilton chairs, and it would be really handy to have
> built-in white boards for markup. Besides, I've always wanted to have
> a plenary in a football stadium. With cheerleaders.
> 
> -- Dean
> 

--------------090805010301070604040705
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------090805010301070604040705--

From sm@resistor.net  Wed Aug 10 00:19:07 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF1921F863A for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 00:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+lWS7cnA6QH for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 00:19:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B9E21F84E0 for <ietf@ietf.org>; Wed, 10 Aug 2011 00:19:05 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p7A7JRQ7012885;  Wed, 10 Aug 2011 00:19:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1312960773; bh=K/dfrii680ZRSgb+TPzp3juDgSikODXJdiMfBggmAXI=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Fabl3JxVCMQt7u0XtMR1AqpvZXWCBVtQ31c0mocevlmHB0+kNU8fdn8pPGotd9kxl 1+MkVMYBae01apcpixlaCWRMTX+APwG4L06bExuEx2A1mMffaRu64njc7CjSsP6+Jw RzhVYF1Ky/XzmN3vldFvN0tUmSiQMUYfDmzEgkNI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1312960773; bh=K/dfrii680ZRSgb+TPzp3juDgSikODXJdiMfBggmAXI=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Iy06ad5ha2IGWp68bfkX5cgJ1N0KlaaRqp+neNbroxSmpkXKdOwu7XLPLXqud352k a70902KeFbOz4nqNVivCf4ua9M8mLSkByH3BI4YMcNpp4VX+v+KBWk+v82o9vp+Lvg ZBnLtRVDK6di3LmCaYnPm0JdzgDRx8GwdENtEJtY=
Message-Id: <6.2.5.6.2.20110809211255.0ab541b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 09 Aug 2011 23:58:27 -0700
To: Carsten Bormann <cabo@tzi.org>
From: SM <sm@resistor.net>
Subject: Re: The fallacy of perfection (Re: DKIM Signatures now being applied to IETF Email)
In-Reply-To: <67C78A3C-065C-444B-8F66-459F90804F5F@tzi.org>
References: <20110801225757.8527.qmail@joyce.lan> <C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com> <E26526C8-E0F5-4F74-A18F-06AC13D8D359@guppylake.com> <67C78A3C-065C-444B-8F66-459F90804F5F@tzi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 07:19:07 -0000

Hi Carsten,
At 11:46 09-08-2011, Carsten Bormann wrote:
>For another perspective on this, see section 2.7 "The fallacy of 
>perfection" in "Garrulity and Fluff".
>(http://www.iab.org/wp-content/IAB-uploads/2011/04/Bormann.pdf)

That's an interesting document.  From Section 2.1:

   "The worst source of complexity, however, is the need to appease 
stakeholders."

As the draft points out, the cost of achieving consensus is to accept 
changes even though it only serves to make the protocol more 
complex.  Some of these changes are not even implemented when they 
are optional or else they are only actually useful for one implementation.

Ignoring MUSTs (Section 2.3) invites long debates.  Instead of having 
the RFC align with implementations in the wild, the situation is such 
that implementers are pressured to adhere to the RFC.

It is quite a feat to make a protocol future-proof (Section 
2.5).  Unfortunately, the process pushes specifications in such a 
direction due to the misguided belief that a perfect protocol is an 
attainable goal.  The fact that specifications are initially of a 
higher quality encourages less flexibility.  In other words, the 
committee is more reluctant to accept changes at a later stage.

Section 2.7 discusses about the tendency to ignore aspects of reality 
that are unpleasant.  On an unrelated note, I would like to 
congratulate NAT operators for the universal deployment of NAT. 
:-)  The reality is whatever the IETF thinks of the principles of 
Internet architecture, operators will violate those principles when 
the latter conflicts with their core value; which is about making 
money.  In simple terms, that protocol that has been designed to do 
almost everything won't gain traction if the input from operators is 
not taken into account.

Quoting Section 2.7:

   "In the IETF, the desire for high quality often leads to a struggle
    at the end to convince the IESG to accept the result. See "appeasing
    stakeholders", "big design up front", "check-mark requirement" above
    for some of the results. It may be better for a protocol to leave a
    flank wide open, and look for the actual requirements to be fulfilled
    in its actual use, then to design in a half-hearted solution appeasing
    the blocking IESG member that then quickly becomes a piece of fluff
    when it is replaced (or, worse, over-painted) by the real thing. (The
    stick of keeping a protocol "experimental" instead of "standards track"
    is then often used to push those "solutions" through.)"

As much as I agree with the above, it in unconceivable that 
draft-bormann-core-6lowpan-fluff-minus would be considered for 
publication in the IETF Stream as such an uncomfortable truth might 
be deemed as unacceptable.

Five years ago, a BCP was published to describe the best current 
practice for a widely deployed Experimental protocol.  The working 
group "came up with modifications to the protocol that the WG thought 
made it better but that implementors didn't see any reasons to deploy".

This thread was initially about DKIM Signatures now being applied to 
IETF Email.  Some people from the IETF sausage factory are aware that 
DKIM is broken; i.e. DKIM signatures will fail to verify when a 
message goes through a mailing list.  Some people might call that a 
flaw, others might say that it is by design.  The point is that it is 
not possible to address all cases.  As Nathaniel Borenstein put it, 
can we accept the inevitability of a flawed process that lets a few 
bugs get through?

These multi-year "big design up front" efforts favor high quality of 
documents at the expense of timeliness.  The longer the design effort 
takes, the shorter the incremental benefit.

Regards,
-sm 


From swmike@swm.pp.se  Wed Aug 10 00:41:48 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D40121F86D0 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 00:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id endXNiGFF8dG for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 00:41:48 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id F0F4821F86C4 for <ietf@ietf.org>; Wed, 10 Aug 2011 00:41:47 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id BB3F1A0; Wed, 10 Aug 2011 09:42:16 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id B8F1E9F for <ietf@ietf.org>; Wed, 10 Aug 2011 09:42:16 +0200 (CEST)
Date: Wed, 10 Aug 2011 09:42:16 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <4E41831E.9030209@gmail.com>
Message-ID: <alpine.DEB.2.00.1108100924200.4709@uplift.swm.pp.se>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <a06240800ca6713e13df6@[10.31.201.42]> <4E41831E.9030209@gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 07:41:48 -0000

On Wed, 10 Aug 2011, Philip Smith wrote:

> When APRICOT comes back to Bangkok in the future (it is a wonderful 
> conference/convention city), the subway will make the location much more 
> favourable, although I think the APIA Board will want to consider other 
> venues too in light of the previous experience with QSNCC.

I would just like to chime in that QSNCC is in an ideal spot in Bangkok, 
connecting both major public transportation that work very well (MRT and 
BTS). There are plenty of USD30-40 / night hotels nearby (< 10 minute 
walking distance) if one doesn't need the more highend ones which would be 
a few stops away on the BTS.

Low season is april-october, it's warm (35-40C during the days, 25-30C 
during the nights) and extremely humid both day and night.

Regarding political problems, there is no way to tell beforehand, but 
having experienced last years problems on-site (I was there march-april) 
they looked a lot worse on TV compared to actually being there. There was 
little problem avoiding it, and QSNCC isn't in the areas targeted last 
year.

So it's more down to if the site works practically to establish 
infrastructure needed and if there is someone locally willing to sponsor 
the event, especially with helping out with practicalities.

Flights are plentyful to Bangkok from all over the world, though most 
flights to/from the US seems to go via Japan.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From ole@cisco.com  Wed Aug 10 01:06:19 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8210421F86DE for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 01:06:19 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Blu-Q-eiY1au for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 01:06:18 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id C9E3121F86DD for <ietf@ietf.org>; Wed, 10 Aug 2011 01:06:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=3060; q=dns/txt; s=iport; t=1312963610; x=1314173210; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=eZUix1fGedHCkF9Bi4oEmx4eXmnoJs6eg4ACRXisEb4=; b=Xz3F6vGrxRQ2W9WF6br993vRNQAfyu6IVnhoDf/txPw7QSrTjik/wGD5 IVjK9pN77DmBtFrcX6pitIrh8vy30d9MXwQAc6sQHWthuItuaqV71HrVE WrUV/Qk870Zjy6m5BdsBfdfRt0DCydyzbusmXOwphi2vQKlwKQo1pciCw 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAE47Qk6rRDoH/2dsb2JhbAA+A6dJd4FAAQEBAQIBAQEBDwECASQuBgsFCwsOCi4nMAYTGgiHSwSfFgGDHA8BmxiDQIMGBIddlR6HGw
X-IronPort-AV: E=Sophos;i="4.67,349,1309737600"; d="scan'208";a="11645013"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-2.cisco.com with ESMTP; 10 Aug 2011 08:06:49 +0000
Received: from sjc-vpn7-506.cisco.com (sjc-vpn7-506.cisco.com [10.21.145.250]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7A86m9X031081; Wed, 10 Aug 2011 08:06:48 GMT
Date: Wed, 10 Aug 2011 01:06:48 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <alpine.DEB.2.00.1108100924200.4709@uplift.swm.pp.se>
Message-ID: <alpine.OSX.2.01.1108100058040.40148@sjc-vpn7-506.cisco.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <a06240800ca6713e13df6@[10.31.201.42]> <4E41831E.9030209@gmail.com> <alpine.DEB.2.00.1108100924200.4709@uplift.swm.pp.se>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 08:06:19 -0000

Just on the topic of political unrest: Once the situation rises to the 
level of "international news", all bets are off. Regardless of the 
actual danger, companies (and even countries) will issue travel bans
or advisories which makes it impossible to have a normal meeting.

Last year's August/September APNIC meeting was supposed to be in 
Bangkok. Nice venue, sponsorship in place, all set to go. But in June
APNIC pulled the plug and moved the meeting to Australia (City of Gold 
Coast). It was felt that even moving the meeting to somewhere else
in Thailand would be problematic because the travel advisories and
bans said in effect "don't fly through BKK" (which was unaffected by
the riots in a small section of downtown). It's true that the riots
DID cause the venue hotel to close, but at least in theory the meeting
could have been held in Phuket or some place like that. APNIC is of 
course a much smaller meeting in terms of attandee figures, so finding
an alterntive venue isn't that complicated, but I would NOT want to be
in the business of moving an IETF meeting 2 months before the event.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 10 Aug 2011, Mikael Abrahamsson wrote:

> On Wed, 10 Aug 2011, Philip Smith wrote:
> 
> > When APRICOT comes back to Bangkok in the future (it is a wonderful
> > conference/convention city), the subway will make the location much more
> > favourable, although I think the APIA Board will want to consider other
> > venues too in light of the previous experience with QSNCC.
> 
> I would just like to chime in that QSNCC is in an ideal spot in Bangkok,
> connecting both major public transportation that work very well (MRT and BTS).
> There are plenty of USD30-40 / night hotels nearby (< 10 minute walking
> distance) if one doesn't need the more highend ones which would be a few stops
> away on the BTS.
> 
> Low season is april-october, it's warm (35-40C during the days, 25-30C during
> the nights) and extremely humid both day and night.
> 
> Regarding political problems, there is no way to tell beforehand, but having
> experienced last years problems on-site (I was there march-april) they looked
> a lot worse on TV compared to actually being there. There was little problem
> avoiding it, and QSNCC isn't in the areas targeted last year.
> 
> So it's more down to if the site works practically to establish infrastructure
> needed and if there is someone locally willing to sponsor the event,
> especially with helping out with practicalities.
> 
> Flights are plentyful to Bangkok from all over the world, though most flights
> to/from the US seems to go via Japan.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From hsantos@isdg.net  Wed Aug 10 01:57:27 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 854F921F876F for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 01:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level: 
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[AWL=-0.729, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zq9I-6iO-WTX for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 01:57:26 -0700 (PDT)
Received: from ftp.catinthebox.net (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6AC21F84F2 for <ietf@ietf.org>; Wed, 10 Aug 2011 01:57:25 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2588; t=1312966671; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=WvNccyv6nBPbFlSQ4dtVXm0/9/A=; b=njKGGGjoV2LG3BhJEL39 qkaEV6tk233ddLBWIjvNweFa/pnw0eU6DsSpK/TuCoErzta03ZTXuaNq0bDiRV1R uhlfXcSF1EwENOIHaVRSCYZG8y0oax2P48XM4wR35WUKPyB5MvFLQuWdjvKfk81I SIGa0Wxx3giNCfid/ywXI7s=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 10 Aug 2011 04:57:51 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1422105899.3546.4144; Wed, 10 Aug 2011 04:57:07 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2588; t=1312966346; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=vKv/ub4 nUmyPkLE1Bx8+BAVy32io0fQGdM6ChgXFaAc=; b=GAT5JBB7rfGO5OxemlTeT8v 0EYSvHLYTbvsQrP/UUkSH96/oroD3gUbOlwjeLo+kxlcGzwteJ4s48DPjU7ovgQz 6yOSNFUB/qdSLwxBi6d/r+c5TiTlyXnJUxwY2Rd6G8gdWauJ2W2Rsdxarv4yINQd mty/c7j+atxsnWP7qZEo=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 10 Aug 2011 04:52:26 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2393384080.570.7256; Wed, 10 Aug 2011 04:52:25 -0400
Message-ID: <4E424808.3080100@isdg.net>
Date: Wed, 10 Aug 2011 04:57:44 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: The fallacy of perfection (Re: DKIM Signatures now being	applied to IETF Email)
References: <20110801225757.8527.qmail@joyce.lan>	<C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com>	<E26526C8-E0F5-4F74-A18F-06AC13D8D359@guppylake.com>	<67C78A3C-065C-444B-8F66-459F90804F5F@tzi.org> <6.2.5.6.2.20110809211255.0ab541b8@resistor.net>
In-Reply-To: <6.2.5.6.2.20110809211255.0ab541b8@resistor.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 08:57:27 -0000

SM wrote:
> Hi Carsten,
> At 11:46 09-08-2011, Carsten Bormann wrote:
>> For another perspective on this, see section 2.7 "The fallacy of 
>> perfection" in "Garrulity and Fluff".
>> (http://www.iab.org/wp-content/IAB-uploads/2011/04/Bormann.pdf)
> 
> That's an interesting document.  From Section 2.1:

Yes, it is a interesting document.

> .... In simple terms, that 
> protocol that has been designed to do almost everything won't gain 
> traction if the input from operators is not taken into account.

+1 and this, in my opinion, is the blessing and curse of the IETF and 
when coupled with the outdated Rough Consensus decision making 
guideline, it can have had a negative impact in the final outcome.

I have been part of several open technical standard organizations 
where the philosophical difference of the mixed discipline 
environment, i.e. Administrators vs Developers was the source of doom, 
especially when the art of compromising is lacking or unachievable.

My view, it all begins with the main source. It is very important the 
editor(s) recognize input is coming from all sides.  Once they shun 
one group over another and use Rough Consensus (RC) as the measuring 
stick to shun others, its over.  Everyone loses.

RC is ok when everyone in the group (team) have a similar discipline 
or mindset.  But when there extreme mindsets, it simply doesn't work 
for the benefit of the main WG or protocol goal. This is like 
prematurely inviting a technical sales team, documentation team or 
help desk to a project R&D effort.  They might fit better during a 
early functional requirement stage or Product R&D effort, but when 
conflicts mindset are smack in the middle of a protocol design, that 
spells problems.

Of course, All input is input so generally, at the end of the day, 
this is more about a management problem - a.k.a IETF WG Chairs. 
Ideally, the editors should be very keen to these differences

Anyway, today, I don't think Rough Consensus is a good decision 
making, issues settling tool that can resolve problems by blowing away 
a good size minority out the door.  That causes problems. When there 
is disperse group, I believe a super majority is a fundamental and 
statistically correct requirement that have a maximum beneficial 
outcome.   This is akin to adding features to a product; when there is 
no clear answer - you make it optional.  Throwing it away will invite 
support issues. :)

I said more than I wanted to, but its just my opinion.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From gwz@net-zen.net  Wed Aug 10 02:34:27 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C11B821F86D6 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 02:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFb+uAv5ljTd for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 02:34:27 -0700 (PDT)
Received: from p3plsmtpa01-01.prod.phx3.secureserver.net (p3plsmtpa01-01.prod.phx3.secureserver.net [72.167.82.81]) by ietfa.amsl.com (Postfix) with SMTP id 2B65021F86D0 for <ietf@ietf.org>; Wed, 10 Aug 2011 02:34:26 -0700 (PDT)
Received: (qmail 20679 invoked from network); 10 Aug 2011 09:34:57 -0000
Received: from unknown (124.120.242.122) by p3plsmtpa01-01.prod.phx3.secureserver.net (72.167.82.81) with ESMTP; 10 Aug 2011 09:34:57 -0000
Message-ID: <4E4250BC.9070305@net-zen.net>
Date: Wed, 10 Aug 2011 16:34:52 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: Queen Sirikit National Convention Center
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <a06240800ca6713e13df6@[10.31.201.42]> <4E41831E.9030209@gmail.com> <alpine.DEB.2.00.1108100924200.4709@uplift.swm.pp.se> <alpine.OSX.2.01.1108100058040.40148@sjc-vpn7-506.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108100058040.40148@sjc-vpn7-506.cisco.com>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------040403040608070808030605"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 09:34:27 -0000

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

On 8/10/2011 3:06 PM, Ole Jacobsen wrote:

...

> I would NOT want to be in the business of moving an IETF meeting 2
> months before the event.

Certainly not, but all hell can break loose with little or no warning
virtually anywhere (see
http://www.boston.com/bigpicture/2011/08/london_riots.html).

...

--------------040403040608070808030605
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------040403040608070808030605--

From ole@cisco.com  Wed Aug 10 05:19:23 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8EA21F87C7 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 05:19:23 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7S9TPAxVXJ7K for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 05:19:22 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 8E11221F87C5 for <ietf@ietf.org>; Wed, 10 Aug 2011 05:19:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=178; q=dns/txt; s=iport; t=1312978794; x=1314188394; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=cCcwdwzg6IHt9/V+GHnKrMSV/PHbpIkGrwqg8NCyjEU=; b=FQUgnxcSveBOCJuTDdM/VnYCYJ+JkAwmt3MTaX23s4SBgoW70BEjtZRI kkgm18N0tDvjfvmtfM2jdfH53g1J9VrhPP6Ps3MKOVoB/pcZEMb3LhMpX h+dsiaovQSj+EHjHFfakHYSiUEBM2N94lFbpIHMjIxDP8uO2xxEW3BDng M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABN3Qk6rRDoJ/2dsb2JhbABBp0h3gUABAQEBAgESAQIBJD8FCwtGVwY1h0yfSgGDHw8BmySGRgSHXZw5
X-IronPort-AV: E=Sophos;i="4.67,350,1309737600"; d="scan'208";a="11705823"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-5.cisco.com with ESMTP; 10 Aug 2011 12:19:52 +0000
Received: from sjc-vpn7-506.cisco.com (sjc-vpn7-506.cisco.com [10.21.145.250]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7ACJqFE011430; Wed, 10 Aug 2011 12:19:52 GMT
Date: Wed, 10 Aug 2011 05:19:52 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <E7FB3C1E-D298-4357-9965-8492AC758B42@softarmor.com>
Message-ID: <alpine.OSX.2.01.1108100514140.42018@sjc-vpn7-506.cisco.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <4E40CD13.3020904@net-zen.net> <E7FB3C1E-D298-4357-9965-8492AC758B42@softarmor.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 12:19:23 -0000

On Tue, 9 Aug 2011, Dean Willis wrote:


> We're tougher than you think, Ole!
> 
> 
> --
> Dean
> 

Judging by the whining, I sometimes wonder.... :-)

Ole's iPad

From jounikor@gmail.com  Tue Aug  9 11:48:57 2011
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42E1A21F8B34; Tue,  9 Aug 2011 11:48:57 -0700 (PDT)
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_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UvaA5gBmDNkg; Tue,  9 Aug 2011 11:48:56 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id B8DA121F8B32; Tue,  9 Aug 2011 11:48:55 -0700 (PDT)
Received: by fxe6 with SMTP id 6so341830fxe.31 for <multiple recipients>; Tue, 09 Aug 2011 11:49:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=ALWE83sZowNR2NyqMPlnO/aF0dsN0jC+2k7utjW+RpE=; b=PyL+RUumOMg9ny2UNWgQm0qHXagJJux3n69wu3gu/g/JqVhinnIUQyWu+4r9/ermW4 X6YZwOqaVTqM/TVb+Ywh8HGt9/QtW66KlrrKoqPNb5wVdyztSxCs/slNWKxA4brsjlXB /Gyp5IocLsBxghOp8/QlObvAUbIqR+TIjghEo=
Received: by 10.223.76.71 with SMTP id b7mr9888772fak.30.1312915764501; Tue, 09 Aug 2011 11:49:24 -0700 (PDT)
Received: from a88-114-69-10.elisa-laajakaista.fi (a88-114-69-10.elisa-laajakaista.fi [88.114.69.10]) by mx.google.com with ESMTPS id e10sm151765fak.18.2011.08.09.11.49.22 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 09 Aug 2011 11:49:23 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-3gpp-eps-03.txt> (IPv6 in 3GPP Evolved Packet System) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: jouni korhonen <jounikor@gmail.com>
In-Reply-To: <CAM+vMEQXsJoaezEwMVsQYUhR0AcxmBths2WuWgcBHS3=eCey_w@mail.gmail.com>
Date: Tue, 9 Aug 2011 21:49:21 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E7AFA6A-0025-4FF4-B5CF-D32A0F3CFF4F@gmail.com>
References: <20110801190301.16571.58632.idtracker@ietfa.amsl.com> <CAM+vMEQ-qsobxrozvzgnRiiHJjRwDPBbGeNe9qKacvQ+0Fj7GA@mail.gmail.com> <49A19FE6-7B0A-4876-8F1A-308F978CC8FC@gmail.com> <CAM+vMEQXsJoaezEwMVsQYUhR0AcxmBths2WuWgcBHS3=eCey_w@mail.gmail.com>
To: GangChen <phdgang@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 10 Aug 2011 08:43:39 -0700
Cc: v6ops@ietf.org, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 18:48:57 -0000

Dear Gang,

On Aug 9, 2011, at 7:14 PM, GangChen wrote:

> Dear Jouni,
>=20
> In mobile CPE case, MT and TE are separated. That would need
> additional requirements in some particular cases, e.g. dynamic IPv6
> address allocation.

Separate MT & TE is part of the existing 3GPP specifications. There is =
nothing CPE specific in that.

> According to the 3GPP specification, the UE shall build the link-local
> address using the interface identifier provided by the PDN GW upon PDN
> connection establishment. However, MT may not be able to transfer the
> interface identifier to TE in the CPE cases. The only thing the IP

See my earlier mail: =
http://www.ietf.org/mail-archive/web/v6ops/current/msg10213.html
This is again not specific to a CPE case but rather a driver framework =
brokenness issue.

> devices can do is to select the interface identifier by some other
> means and then perform Duplicate Address Detection, as specified in
> RFC 4862. The PDN GW shall then perform the DAD check based on the
> Neighbor Solicitation messages sent by the UE.

A GGSN/PPGW is already supposed to perform a DAD check. Referring to =
3GPP TS29.061 Section 11.2.1.3.4, which says:
"For IPv6 Address Autoconfiguration to work properly, network entities =
which act as an access router towards the MS/UE, i.e. PDN GW, Serving =
GW, and ePDG, shall be consistent with the RFCs specifying this process =
(for example RFC 4862 [83] and RFC 4861 [89]), unless stated otherwise =
in this or other 3GPP specifications."

And there is no text in specs that would state using "shall" that the =
PGW/GGSN/SGW must not perform DAD check or not to answer to an NS.. on a =
contrary (see text in Section 11.2.3.2 & 11.2.3.2a.. not that the text =
is the best regarding handling an NS but still).

> Therefore, there are some implementation factors that may change UE
> behaviour in the CPE context. IMHO, it would be beneficial to describe
> CPE consideration in section 5.3. CPE case has already appeared to be
> a valid scenario in 3GPP

I still cannot see any CPE specific considerations here. I witness same =
thing almost daily with my 3G dongle, which was the reason for =
http://www.ietf.org/mail-archive/web/v6ops/current/msg10213.html.

- Jouni

>=20
> BRs
>=20
> Gang
>=20
> 2011/8/5, Jouni <jounikor@gmail.com>:
>> Dear Gang,
>>=20
>> I would be inclined to say that within the 3GPP scope the client is =
always
>> the "UE" and its form factor or the end usage scenario does not =
really
>> matter. It does not change the way the UE is expected to behave from =
the
>> 3GPP system point of view, unless there is a new functional =
requirement from
>> 3GPP.
>>=20
>> - Jouni
>>=20
>>=20
>>=20
>> On Aug 5, 2011, at 5:55 AM, GangChen wrote:
>>=20
>>> Hello Authors,
>>>=20
>>> I think it is worth adding some texts to describe mobile CPE case, =
in
>>> which CPEs with wireless modem use 3GPP access as uplink.
>>>=20
>>> Gang
>>>=20
>>>=20
>>> 2011/8/2, The IESG <iesg-secretary@ietf.org>:
>>>>=20
>>>> The IESG has received a request from the IPv6 Operations WG (v6ops) =
to
>>>> consider the following document:
>>>> - 'IPv6 in 3GPP Evolved Packet System'
>>>> <draft-ietf-v6ops-3gpp-eps-03.txt> as an Informational RFC
>>>>=20
>>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>>> final comments on this action. Please send substantive comments to =
the
>>>> ietf@ietf.org mailing lists by 2011-08-15. Exceptionally, comments =
may be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>=20
>>>> Abstract
>>>>=20
>>>>=20
>>>>  Use of data services in smart phones and broadband services via =
HSPA
>>>>  and HSPA+, in particular Internet services, has increased rapidly =
and
>>>>  operators that have deployed networks based on 3GPP network
>>>>  architectures are facing IPv4 address shortages at the Internet
>>>>  registries and are feeling a pressure to migrate to IPv6.  This
>>>>  document describes the support for IPv6 in 3GPP network
>>>>  architectures.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>>>>=20
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-3gpp-eps/
>>>>=20
>>>>=20
>>>> No IPR declarations have been submitted directly on this I-D.
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20


From ycai@cisco.com  Tue Aug  9 13:49:49 2011
Return-Path: <ycai@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF6E21F8B04; Tue,  9 Aug 2011 13:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.532
X-Spam-Level: 
X-Spam-Status: No, score=-0.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBtadf2gVD0A; Tue,  9 Aug 2011 13:49:48 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id DA42821F8B02; Tue,  9 Aug 2011 13:49:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ycai@cisco.com; l=10968; q=dns/txt; s=iport; t=1312923018; x=1314132618; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=CKrLUywYoxwv2VZEj3FNiVTIxKhr3CKT4sw6BlHN+uY=; b=EOCmw3d7tH3DzQy/0WeQJwSSPGPruhOAqYcjZFGVPAEHhbNmN/+49JVt gPI3UWQfeCAqmyYmM9mVObEZjsYYn7g1D5D9I2w2/OA36lNEz+TBQQzvp FZ7sPwPW0QV/7W07Kukkx55hC/+Mx2tv4vgpVK89yvYr1GsTMxF4Jlvsl c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8IABOdQU6rRDoJ/2dsb2JhbABCpz0Cd4FAAQEBAQIBAQEBDwEnAgExCwUNAQhnBjABAQQBDQUbB4dLBJ8QAZ5ahkYEh1yLKYUShF2DAIQc
X-IronPort-AV: E=Sophos;i="4.67,345,1309737600"; d="scan'208";a="11479663"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-8.cisco.com with ESMTP; 09 Aug 2011 20:50:16 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p79KoGCj030223; Tue, 9 Aug 2011 20:50:16 GMT
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 9 Aug 2011 13:50:16 -0700
Received: from 128.107.161.230 ([128.107.161.230]) by xmb-sjc-216.amer.cisco.com ([171.70.151.184]) with Microsoft Exchange Server HTTP-DAV ; Tue,  9 Aug 2011 20:50:15 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Tue, 09 Aug 2011 13:50:21 -0700
Subject: Re: [pim] tsv-dir review of draft-ietf-pim-mtid-08
From: Yiqun Cai <ycai@cisco.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>, IETF Discussion <ietf@ietf.org>
Message-ID: <CA66EB9D.AF52C%ycai@cisco.com>
Thread-Topic: [pim] tsv-dir review of draft-ietf-pim-mtid-08
Thread-Index: AcxW1fQVCxnlCmf+6kW+cOAFGDDVgQ==
In-Reply-To: <A9EFAA60-85DE-40F1-86C3-B9652E9CC0EA@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 09 Aug 2011 20:50:16.0307 (UTC) FILETIME=[F149CC30:01CC56D5]
X-Mailman-Approved-At: Wed, 10 Aug 2011 08:43:39 -0700
Cc: TSV Area <tsv-area@ietf.org>, pim@ietf.org, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2011 20:49:49 -0000

Marshall,  thank you very much for the review.

Some of my comments are inline.


On 6/30/11 7:22 AM, "Marshall Eubanks" <marshall.eubanks@gmail.com> wrote:

> 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.
> 
> Note : I also reviewed the WG mailing list discussions for this document.
> 
> This draft is basically ready for publication, but has some issues that in my
> opinion should be fixed before publication.
> 
> There are, however, some issues that I think that should be addressed, either
> in a follow-on document, or a revision of this document.
> 
> draft-ietf-pim-mtid  introduces a new type of PIM Join Attribute [RFC5384],
> the MT-ID Join Attribute, that extends
> PIM signaling to cover multiple topologies and to enable the identification of
> which topology should be used when
> constructing a particular multicast distribution tree.
> 
> Multiple topologies have been used for some time in unicast (they are
> supported by IS-IS and OSPF), and also in multicast. The most common multicast
> requirement for multiple topologies is for video transport, where important or
> expensive video streams (say, of sporting events) are protected from
> disruption by multiple transport on completely different network paths. In
> that use, if a network link goes down or becomes congested or otherwise
> suboptimal, another source of the video data is already present and the
> display can be seamlessly switched to the other copy of the stream. This use
> case is alluded to in the document.
> 
> Another use case for multiple-topologies is to separate out different types of
> traffic (say, latency sensitive traffic from larger, bulk, flows). This is not
> alluded to in this document, and it is not clear to what extent this was
> intended. These multiple topologies may or may not result
> in the replication of data, and so may not be intended by the author. However,
> I would say that this could be used to support this, and so it will be. If
> there is some reason NOT to use this mechanism for this purpose, some
> description of the reasons why would be in order.
> 
> This document sets up a numerical variable, the  MT-ID Join Attribute, to
> assign to multicast topologies, to be used to separate different topologies
> for different paths. This number for a given multicast topology need not be
> the same as any unicast multiple topology identifiers, and similarly the
> multicast topologies and the underlying unicast topologies may be different.

You are right that there are indeed more use cases that can make use of the
functions described by this draft.  And some do exist in the field.

However, we (as co-authors) were very reluctant to list them.  We felt this
would be more appropriate to be described and published as whitepapers by
vendors, and we indeed have discussed them in public on behalf of our
employer.

It was our intention to try to keep this draft focused on the changes
required from a PIM protocol point of view.  I hope you will understand and
appreciate our viewpoints.


> 
> This document is sort, straight-forward, and relatively well-written. I had a
> few non-fatal issues.  (I would be glad to suggest some text for any of these
> issues to the authors if they interested.)
> 
> Minor Issues :
> 
> Section 3.2 
> 
> "- As shown earlier, this value is not required to be the same as the MT-ID
> used by the unicast routing protocols that contribute routes to the topology.
> In practice, when only one unicast routing protocol (such as OSPF or IS-IS) is
> used, the PIM MT-ID is RECOMMENDED to be assigned using the same value as the
> IGP topology identifier. Using the same example presented earlier, if
> every route in PIM 500 is contributed by OSPF 1000, it is RECOMMENDED to name
> this RPF topology as PIM 1000 instead of PIM 500. This is for the purpose of
> reducing management overhead and simplifying troubleshooting."
> 
> In the actual example, PIM 500 is not the same network topology as OSPF 1000
> (it has an extra link, to the source, obtained by MBGP). This is specifically
> mentioned previously in the text. So, this is NOT the same example as
> presented earlier and it is NOT clear that this recommendation applies here.

What we tried to say here is that,

1. If a PIM topology has routes contributed by different protocols, say OSPF
and MBGP,  it is better to use a different MT-ID for PIM.  For example, use
500 for PIM and 1000 for OSPF.

2. But if a PIM topology has all its routes contributed by a single
protocol,  then it is better to use the same MT-ID as the underlying unicast
protocol and in this case, 1000 is used for both PIM and OSPF.

Please let us know if the explanation helps and we will definitely
appreciate if you suggest some text here.

> 
> If this is left as is, it will certainly confuse some people. I would suggest
> adding text to clarify this, or creating another example where the
> unicast and multicast topologies are the same.
> 
> Section 4.2.3 
> 
> "- There is at most 1 PIM MT-ID attribute encoded. If there are multiple PIM
> MT-ID Join Attributes included, only the last one is accepted for this
> particular source. Processing of the rest of the Join message continues."
> 
> Is this a typo ? 
> 
> s/at most/at least/
> 
> would seem to be appropriate. (It says, "at most" 1, and then describes what
> do to if there is more than 1.) Otherwise, please explain what is meant.

We did mean there can be "at most" 1 MT-ID attribute.

But if there are more than 1 included, most likely due to an implementation
error, the rest of the paragraph suggests what an implementation should do.
Would it be better if we add "due to an implementation error"?

> 
> Section 6.
> 
> The Labels for Section 6.1 and 6.2 are the same. I suspect this is just a
> typo, and they should be
> 
> 6.1. PIM-Hello Options
> 
> 6.2. PIM Join Attribute Types
> 

Good catch.  Will fix.

> More Substantive Issues :
> 
> I had two substantive issues with this document.
> 
> 1.) The range for the topologies. It is highly likely that the users of this
> capability would want to use multiple topologies differently for different
> multicast address ranges. For example, use of two topologies is likely to be
> an expensive customer option, that not all customers would pay for, and so
> would not apply to all multicast addresses. Or, the backup typologies may
> (probably will be) tailored differently for different customers in different
> locations. Or, topologies might be tailored for different data types
> (different backups for real time video conferencing versus TV broadcast
> transmissions, say). This is very briefly alluded to in Section 3.1, but no
> consideration is given to issues arising from this.
> 
> For example, suppose I have two customers, and I wish to have one basic
> topology (say, PIM 100) for 239.10/16, and I wish to have two backup
> topologies for the two customers (say, PIM 1001 for 239.10.1/24 and PIM 1002
> for 239.10.2/24.) Can I have PIM 100 cover both the PIM 1001 and PIM 1002
> range ? Are there issues with this ? Would it be better to split PIM 100 into
> pieces to match 1001 and 1002 ? Nothing like this is discussed

The draft allows the above to happen.  Because as I indicated earlier, the
draft tries to focus on the protocol changes required to support the
functionality but not the deployment cases that can make use of it.

> 
> I can easily see interoperability issues arising from this (i.e., vendor A
> might allow PIM 100 to overlap PIM 1001 and PIM 1002, and vendor B might not).
> I think that some text to discuss the entire issue of ranging (presumably,
> that they can be allowed and overlaps SHOULD be supported) is needed.
> 
> Again, this could be out of scope here, but, then, where will it appear ?

I agree it is out of scope for the reasons I explained earlier but I don't
have a good answer what is the best practice to document all these cases.

> 
> 2.) There is very little discussion as to how to use this capability. Now,
> this might be considered out of scope for this document, but there will be
> issues, and I do not see a follow-on in the pipeline.
> 
> Issues include sharing of links and the general connections between
> topologies. It is likely that in real uses, a portion of the multiple
> topologies may be either physically shared or directly linked. It may not be
> possible to engineer out all single points of failure, for example an undersea
> cable. This is possible with the first use case (independent topologies for
> video) and likely with the second (different topologies for different types of
> content). 
> 

Yes, same as above.

> Issues I see here include
> 
> - the actual multicast data will not include any PIM attributes.  How, then,
> is a midpoint router receiving two copies of every packet know that it
> shouldn't just drop one, and only populate one of the downstreams ? Or, should
> it replicate one input into both downstream topologies ? I can easily see
> interop issues here, and possibly even more basic transport issues from
> replicated data. 
> 

To use the functionality, the two streams of multicast must differ somehow
at the network layer.  For example, one uses (S1,G1) and the other uses
(S2,G2). Because the addresses are different, the forwarding trees will be
built using routes in the (multiple) topologies.  And once the forwarding
trees are built, the actual action of "forwarding" doesn't need to be
concerned with topologies.

> - if at any point the two multicast topologies go through a shared LAN or
> switch or any sort of multiple access network, how are the topological flows
> going to be kept distinct. (This is similar to the above, but the actual
> routers might be kept separate.)
> 
> - what happens with failovers ? If a link fails, SHOULD the backup links not
> collapse the topologies ? Again, I think some thought and text would be
> useful.
> 
> If there is a solution to this, it may be simple (you MUST use tunnels) or it
> may be complicated. In either case, some text here would be good.
> 

Marshall,  it would be good if you can suggest some text for us to use.
Thanks.


> Regards
> Marshall 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


-- 
Yiqun


From ycai@cisco.com  Wed Aug 10 03:41:13 2011
Return-Path: <ycai@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0DED21F86E0; Wed, 10 Aug 2011 03:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.857
X-Spam-Level: 
X-Spam-Status: No, score=-0.857 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tf13mgVXDd4L; Wed, 10 Aug 2011 03:41:12 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietfa.amsl.com (Postfix) with ESMTP id E887E21F86DE; Wed, 10 Aug 2011 03:41:11 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 9DC729B0009; Wed, 10 Aug 2011 12:42:33 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 90A439B0001; Wed, 10 Aug 2011 12:42:33 +0200 (CEST)
Received: from ftrdsmtp4.rd.francetelecom.fr ([10.192.128.49]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 10 Aug 2011 12:02:40 +0200
Received: from mail pickup service by ftrdsmtp4.rd.francetelecom.fr with Microsoft SMTPSVC; Wed, 10 Aug 2011 02:17:45 +0200
Received: from omfeda06.si.francetelecom.fr ([10.98.3.82]) by ftrdsmtp4.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 9 Aug 2011 22:50:25 +0200
Received: from omfeda14.si.francetelecom.fr (unknown [10.98.77.166]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 2D88CC803A; Tue,  9 Aug 2011 22:50:25 +0200 (CEST)
Received: from omfeda14.si.francetelecom.fr (localhost.localdomain [127.0.0.1]) by omfeda14.si.francetelecom.fr (ESMTP service) with SMTP id 1B9C92AC8B4; Tue,  9 Aug 2011 22:50:25 +0200 (CEST)
Received: from mail.ietf.org (mail.ietf.org [12.22.58.30]) by relais-inet.francetelecom.com (ESMTP service) with ESMTP id 7537D2AC8B2; Tue,  9 Aug 2011 22:50:24 +0200 (CEST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A0AB21F8B05; Tue,  9 Aug 2011 13:49:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1312922991; bh=jGrZ81X00klaf0McedkKG1XXA3WKvCKfLPXRji3SMD4=; h=Date:From:To:Message-ID:In-Reply-To:Mime-version:Cc:Subject: List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=BQsNXm5WJ/Ajd8SK3xPLOlV6AX6bWHA0eoTSlCsbKkVYiMMR/1OlbAfb2lBjH/swG l7S6AsJs11s2QkLGXrhPdASwMp/E7A7MdWsQF5ffVSclQADB0iWdJcKaTCTobHPfIw XtwdoHAEl2QpkEslSHisooBLsdJR82kSjXvOAoIk=
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF6E21F8B04; Tue,  9 Aug 2011 13:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBtadf2gVD0A; Tue,  9 Aug 2011 13:49:48 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id DA42821F8B02; Tue,  9 Aug 2011 13:49:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ycai@cisco.com; l=10968; q=dns/txt; s=iport; t=1312923018; x=1314132618; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=CKrLUywYoxwv2VZEj3FNiVTIxKhr3CKT4sw6BlHN+uY=; b=EOCmw3d7tH3DzQy/0WeQJwSSPGPruhOAqYcjZFGVPAEHhbNmN/+49JVt gPI3UWQfeCAqmyYmM9mVObEZjsYYn7g1D5D9I2w2/OA36lNEz+TBQQzvp FZ7sPwPW0QV/7W07Kukkx55hC/+Mx2tv4vgpVK89yvYr1GsTMxF4Jlvsl c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8IABOdQU6rRDoJ/2dsb2JhbABCpz0Cd4FAAQEBAQIBAQEBDwEnAgExCwUNAQhnBjABAQQBDQUbB4dLBJ8QAZ5ahkYEh1yLKYUShF2DAIQc
X-IronPort-AV: E=Sophos;i="4.67,345,1309737600"; d="scan'208";a="11479663"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-8.cisco.com with ESMTP; 09 Aug 2011 20:50:16 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p79KoGCj030223; Tue, 9 Aug 2011 20:50:16 GMT
Received: from xmb-sjc-216.amer.cisco.com ([171.70.151.184]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 9 Aug 2011 13:50:16 -0700
Received: from 128.107.161.230 ([128.107.161.230]) by xmb-sjc-216.amer.cisco.com ([171.70.151.184]) with Microsoft Exchange Server HTTP-DAV ; Tue,  9 Aug 2011 20:50:15 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Tue, 09 Aug 2011 13:50:21 -0700
From: Yiqun Cai <ycai@cisco.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>, IETF Discussion <ietf@ietf.org>
Message-ID: <CA66EB9D.AF52C%ycai@cisco.com>
Thread-Topic: [pim] tsv-dir review of draft-ietf-pim-mtid-08
Thread-Index: AcxW1fQVCxnlCmf+6kW+cOAFGDDVgQ==
In-Reply-To: <A9EFAA60-85DE-40F1-86C3-B9652E9CC0EA@gmail.com>
Mime-version: 1.0
X-OriginalArrivalTime: 09 Aug 2011 20:50:16.0307 (UTC) FILETIME=[F149CC30:01CC56D5]
Subject: Re: [pim] tsv-dir review of draft-ietf-pim-mtid-08
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.8.9.204214
X-Mailman-Approved-At: Wed, 10 Aug 2011 08:43:39 -0700
Cc: TSV Area <tsv-area@ietf.org>, pim@ietf.org, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 10:41:13 -0000

Marshall,  thank you very much for the review.

Some of my comments are inline.


On 6/30/11 7:22 AM, "Marshall Eubanks" <marshall.eubanks@gmail.com> wrote:

> 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.
> 
> Note : I also reviewed the WG mailing list discussions for this document.
> 
> This draft is basically ready for publication, but has some issues that in my
> opinion should be fixed before publication.
> 
> There are, however, some issues that I think that should be addressed, either
> in a follow-on document, or a revision of this document.
> 
> draft-ietf-pim-mtid  introduces a new type of PIM Join Attribute [RFC5384],
> the MT-ID Join Attribute, that extends
> PIM signaling to cover multiple topologies and to enable the identification of
> which topology should be used when
> constructing a particular multicast distribution tree.
> 
> Multiple topologies have been used for some time in unicast (they are
> supported by IS-IS and OSPF), and also in multicast. The most common multicast
> requirement for multiple topologies is for video transport, where important or
> expensive video streams (say, of sporting events) are protected from
> disruption by multiple transport on completely different network paths. In
> that use, if a network link goes down or becomes congested or otherwise
> suboptimal, another source of the video data is already present and the
> display can be seamlessly switched to the other copy of the stream. This use
> case is alluded to in the document.
> 
> Another use case for multiple-topologies is to separate out different types of
> traffic (say, latency sensitive traffic from larger, bulk, flows). This is not
> alluded to in this document, and it is not clear to what extent this was
> intended. These multiple topologies may or may not result
> in the replication of data, and so may not be intended by the author. However,
> I would say that this could be used to support this, and so it will be. If
> there is some reason NOT to use this mechanism for this purpose, some
> description of the reasons why would be in order.
> 
> This document sets up a numerical variable, the  MT-ID Join Attribute, to
> assign to multicast topologies, to be used to separate different topologies
> for different paths. This number for a given multicast topology need not be
> the same as any unicast multiple topology identifiers, and similarly the
> multicast topologies and the underlying unicast topologies may be different.

You are right that there are indeed more use cases that can make use of the
functions described by this draft.  And some do exist in the field.

However, we (as co-authors) were very reluctant to list them.  We felt this
would be more appropriate to be described and published as whitepapers by
vendors, and we indeed have discussed them in public on behalf of our
employer.

It was our intention to try to keep this draft focused on the changes
required from a PIM protocol point of view.  I hope you will understand and
appreciate our viewpoints.


> 
> This document is sort, straight-forward, and relatively well-written. I had a
> few non-fatal issues.  (I would be glad to suggest some text for any of these
> issues to the authors if they interested.)
> 
> Minor Issues :
> 
> Section 3.2 
> 
> "- As shown earlier, this value is not required to be the same as the MT-ID
> used by the unicast routing protocols that contribute routes to the topology.
> In practice, when only one unicast routing protocol (such as OSPF or IS-IS) is
> used, the PIM MT-ID is RECOMMENDED to be assigned using the same value as the
> IGP topology identifier. Using the same example presented earlier, if
> every route in PIM 500 is contributed by OSPF 1000, it is RECOMMENDED to name
> this RPF topology as PIM 1000 instead of PIM 500. This is for the purpose of
> reducing management overhead and simplifying troubleshooting."
> 
> In the actual example, PIM 500 is not the same network topology as OSPF 1000
> (it has an extra link, to the source, obtained by MBGP). This is specifically
> mentioned previously in the text. So, this is NOT the same example as
> presented earlier and it is NOT clear that this recommendation applies here.

What we tried to say here is that,

1. If a PIM topology has routes contributed by different protocols, say OSPF
and MBGP,  it is better to use a different MT-ID for PIM.  For example, use
500 for PIM and 1000 for OSPF.

2. But if a PIM topology has all its routes contributed by a single
protocol,  then it is better to use the same MT-ID as the underlying unicast
protocol and in this case, 1000 is used for both PIM and OSPF.

Please let us know if the explanation helps and we will definitely
appreciate if you suggest some text here.

> 
> If this is left as is, it will certainly confuse some people. I would suggest
> adding text to clarify this, or creating another example where the
> unicast and multicast topologies are the same.
> 
> Section 4.2.3 
> 
> "- There is at most 1 PIM MT-ID attribute encoded. If there are multiple PIM
> MT-ID Join Attributes included, only the last one is accepted for this
> particular source. Processing of the rest of the Join message continues."
> 
> Is this a typo ? 
> 
> s/at most/at least/
> 
> would seem to be appropriate. (It says, "at most" 1, and then describes what
> do to if there is more than 1.) Otherwise, please explain what is meant.

We did mean there can be "at most" 1 MT-ID attribute.

But if there are more than 1 included, most likely due to an implementation
error, the rest of the paragraph suggests what an implementation should do.
Would it be better if we add "due to an implementation error"?

> 
> Section 6.
> 
> The Labels for Section 6.1 and 6.2 are the same. I suspect this is just a
> typo, and they should be
> 
> 6.1. PIM-Hello Options
> 
> 6.2. PIM Join Attribute Types
> 

Good catch.  Will fix.

> More Substantive Issues :
> 
> I had two substantive issues with this document.
> 
> 1.) The range for the topologies. It is highly likely that the users of this
> capability would want to use multiple topologies differently for different
> multicast address ranges. For example, use of two topologies is likely to be
> an expensive customer option, that not all customers would pay for, and so
> would not apply to all multicast addresses. Or, the backup typologies may
> (probably will be) tailored differently for different customers in different
> locations. Or, topologies might be tailored for different data types
> (different backups for real time video conferencing versus TV broadcast
> transmissions, say). This is very briefly alluded to in Section 3.1, but no
> consideration is given to issues arising from this.
> 
> For example, suppose I have two customers, and I wish to have one basic
> topology (say, PIM 100) for 239.10/16, and I wish to have two backup
> topologies for the two customers (say, PIM 1001 for 239.10.1/24 and PIM 1002
> for 239.10.2/24.) Can I have PIM 100 cover both the PIM 1001 and PIM 1002
> range ? Are there issues with this ? Would it be better to split PIM 100 into
> pieces to match 1001 and 1002 ? Nothing like this is discussed

The draft allows the above to happen.  Because as I indicated earlier, the
draft tries to focus on the protocol changes required to support the
functionality but not the deployment cases that can make use of it.

> 
> I can easily see interoperability issues arising from this (i.e., vendor A
> might allow PIM 100 to overlap PIM 1001 and PIM 1002, and vendor B might not).
> I think that some text to discuss the entire issue of ranging (presumably,
> that they can be allowed and overlaps SHOULD be supported) is needed.
> 
> Again, this could be out of scope here, but, then, where will it appear ?

I agree it is out of scope for the reasons I explained earlier but I don't
have a good answer what is the best practice to document all these cases.

> 
> 2.) There is very little discussion as to how to use this capability. Now,
> this might be considered out of scope for this document, but there will be
> issues, and I do not see a follow-on in the pipeline.
> 
> Issues include sharing of links and the general connections between
> topologies. It is likely that in real uses, a portion of the multiple
> topologies may be either physically shared or directly linked. It may not be
> possible to engineer out all single points of failure, for example an undersea
> cable. This is possible with the first use case (independent topologies for
> video) and likely with the second (different topologies for different types of
> content). 
> 

Yes, same as above.

> Issues I see here include
> 
> - the actual multicast data will not include any PIM attributes.  How, then,
> is a midpoint router receiving two copies of every packet know that it
> shouldn't just drop one, and only populate one of the downstreams ? Or, should
> it replicate one input into both downstream topologies ? I can easily see
> interop issues here, and possibly even more basic transport issues from
> replicated data. 
> 

To use the functionality, the two streams of multicast must differ somehow
at the network layer.  For example, one uses (S1,G1) and the other uses
(S2,G2). Because the addresses are different, the forwarding trees will be
built using routes in the (multiple) topologies.  And once the forwarding
trees are built, the actual action of "forwarding" doesn't need to be
concerned with topologies.

> - if at any point the two multicast topologies go through a shared LAN or
> switch or any sort of multiple access network, how are the topological flows
> going to be kept distinct. (This is similar to the above, but the actual
> routers might be kept separate.)
> 
> - what happens with failovers ? If a link fails, SHOULD the backup links not
> collapse the topologies ? Again, I think some thought and text would be
> useful.
> 
> If there is a solution to this, it may be simple (you MUST use tunnels) or it
> may be complicated. In either case, some text here would be good.
> 

Marshall,  it would be good if you can suggest some text for us to use.
Thanks.


> Regards
> Marshall 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim


-- 
Yiqun

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

From vesely@tana.it  Wed Aug 10 10:49:11 2011
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E15E21F87D3 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 10:49:11 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OC5SiLIXD6kr for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 10:49:10 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 878F321F87C3 for <ietf@ietf.org>; Wed, 10 Aug 2011 10:49:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1312998582; bh=tAmGPjQ5wcbEreVkD7CkXWbcZ8+ozxjbwrW0jT+QjVI=; l=696; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=W1gVNf42phNsqAMRZV1oWWQ8r/m4NxsiIbAH4U8+Rhd2QnzrfDcyjU7j2Y/zjEqHY G6vD70QDU6KKoy033y58QXkMGP+OnPRNjbQ99ySs5Tj9SuWS93jdQm+H4/MflV0Gp7 6S+Yh2AC2pjH3nvq/IIEfz//AsMVYNd0mkmnEc7c=
Received: from [109.113.198.243] ([109.113.198.243]) (AUTH: PLAIN 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 10 Aug 2011 19:49:41 +0200 id 00000000005DC035.000000004E42C4B5.00006623
Message-ID: <4E42C4AF.6010108@tana.it>
Date: Wed, 10 Aug 2011 19:49:35 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The fallacy of perfection
References: <20110801225757.8527.qmail@joyce.lan>	<C9E3B446-9AA6-4724-82DD-5F6DC2F083F9@network-heretics.com>	<E26526C8-E0F5-4F74-A18F-06AC13D8D359@guppylake.com>	<67C78A3C-065C-444B-8F66-459F90804F5F@tzi.org> <6.2.5.6.2.20110809211255.0ab541b8@resistor.net>
In-Reply-To: <6.2.5.6.2.20110809211255.0ab541b8@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 17:49:11 -0000

On 10.08.2011 08:58, SM wrote:
> The reality is whatever the IETF thinks of the principles of Internet
> architecture, operators will violate those principles when the latter
> conflicts with their core value; which is about making money.  In simple
> terms, that protocol that has been designed to do almost everything won't
> gain traction if the input from operators is not taken into account.

An operator is whoever operates the Internet, including IETFers and
programmers, besides telecoms.  Money is an inheritance from pre-existing
establishments, and one that doesn't work very well.  IMHO, the Internet can
be considered part of the world's effort to limit its exceeding power.

From adrian@olddog.co.uk  Wed Aug 10 11:34:38 2011
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5981121F8A35; Wed, 10 Aug 2011 11:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yooWTGkBvUo2; Wed, 10 Aug 2011 11:34:37 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 49C3521F8AB8; Wed, 10 Aug 2011 11:34:37 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id p7AIZ7Eh018202;  Wed, 10 Aug 2011 19:35:07 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id p7AIZ6FX018193 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 10 Aug 2011 19:35:07 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ben Campbell'" <ben@nostrum.com>, <draft-shiomoto-ccamp-switch-programming.all@tools.ietf.org>
References: <F18F3E79-4E0C-4071-B85D-638D3BD0FD6D@nostrum.com>
In-Reply-To: <F18F3E79-4E0C-4071-B85D-638D3BD0FD6D@nostrum.com>
Subject: RE: Gen-ART LC Review of draft-shiomoto-ccamp-switch-programming
Date: Wed, 10 Aug 2011 19:35:05 +0100
Message-ID: <041501cc578c$3a12f2a0$ae38d7e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG1+OT49B/2RN3qN9t1gDIbVZDKbpVDJcxg
Content-Language: en-gb
Cc: gen-art@ietf.org, 'The IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 18:34:38 -0000

Hi Ben,

Thanks for reading.

> Nits/editorial comments:
> 
> -- section 1, paragraph 4: "...with relation to the programming..."
> 
> ... in relation to...

Yeah. RFC Editor note if Stewart is watching (although I'm guessing the RFC
Editor might just fix this anyway).

> -- 3.1, last paragraph:
> 
> Note that the references say SHOULD rather than MUST. Using "must not" here,
> even non-normatively, seems a bit overstated.

Disagree. The caveat is that we are defining something different. We are looking
at the case where we want to know that it is safe to start sending data. We are
using the existence of some "SHOULD" statements in related RFCs that describe
related behavior, to derive a "must" that covers when it is known to be safe.

Cheers,
Adrian


From mary.ietf.barnes@gmail.com  Wed Aug 10 12:25:49 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2911321F8B21; Wed, 10 Aug 2011 12:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.381
X-Spam-Level: 
X-Spam-Status: No, score=-103.381 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7UB7iE-LDJGK; Wed, 10 Aug 2011 12:25:48 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5E021F8A35; Wed, 10 Aug 2011 12:25:48 -0700 (PDT)
Received: by vxi29 with SMTP id 29so1379984vxi.31 for <multiple recipients>; Wed, 10 Aug 2011 12:26:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=XSAvd48C196JTSMw7iH9nzkDcxgG0a7tXDj8tG+RWQ8=; b=ILpwFoNALZmSAKDQ/vABCdA2aHuR2tHT5/2yCZVOjWX5qWT0+pCbXUxs192PvW7/3x rmVLAMkqHRcXzTbHbywNDKrGq+jjhWoX7IOH8+EPqbgdepQfUxhTatke4DK6C7mLL1jQ BAo8BOquGYWvP1/7dlwOOEMc0zRCfNSgjIdTs=
MIME-Version: 1.0
Received: by 10.52.70.5 with SMTP id i5mr1327609vdu.250.1313004380190; Wed, 10 Aug 2011 12:26:20 -0700 (PDT)
Received: by 10.52.167.34 with HTTP; Wed, 10 Aug 2011 12:26:20 -0700 (PDT)
Date: Wed, 10 Aug 2011 14:26:20 -0500
Message-ID: <CAHBDyN6a-mHy2Zqt0tRYUc0yK4vjkzoNB9WChDGZ271h-gs1mQ@mail.gmail.com>
Subject: Gen-ART Review: Last Call <draft-ietf-lisp-lig-04.txt>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: draft-ietf-lisp-lig.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=20cf307d04caab797e04aa2ba721
Cc: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 19:25:49 -0000

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

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-lisp-lig-04
Reviewer:  Mary Barnes
Review Date:  10 August 2011
IETF LC End Date:  12 August 2011

Summary:  Ready with comments/nits

Comments/minor issues:
------------------------------------

- Section 3, Routing Locator definition: The third sentence is a little
difficult to parse.  I would suggest to reword something like the following
 (based on my interpretation of what the text is intended to say):
OLD:
      Typically, RLOCs are
      numbered from topologically-aggregatable blocks that are assigned
      to a site at each point to which it attaches to the global
      Internet; where the topology is defined by the connectivity of
      provider networks, RLOCs can be thought of as PA addresses.
NEW:
      Typically, RLOCs are
      numbered from topologically-aggregatable blocks that are assigned
      to a site at each point to which it attaches to the global
      Internet.  Thus, the topology is defined by the connectivity of
      provider networks and RLOCs can be thought of as PA addresses.

Also, you'll have to pardon my ignorance, but it's not obvious to me what PA
stands for. I googled and I think it's Provider Aggregatable (and not
Physical Address, which was my first reaction).  I also found it expanded in
draft-lisp-eid-block, which has a definition of RLOC that is mostly verbatim
to this one, which makes me wonder why the terms need to be redefined in
this document and isn't there the potential for the definitions to become
inconsistent?

- Section 3, Endpoint ID definition.  It's not clear to me how SIP relates
to LISP.   I would think it's sufficient to use a DNS lookup as the example
and delete the non-specific reference to a "SIP Exchange".

Nits:
-----

- Section 2, 2nd paragraph: "Map Resolvers" -> "Map-Resolvers"
- Section 3, 2nd bullet: "Map Replier" -> "Map-Replier"
- Section 3, last paragraph: "for lig initiating site" -> "for the lig
initiating site"
- Section 3, last paragraph: shouldn't "lig self" be "ligging yourself"?
- Section 4.1, last paragraph before sample output for ligging yourself:
"to originating site" -> "to the originating site"

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

<div><br></div><div>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.too=
ls.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/g=
en/trac/wiki/GenArtfaq</a>&gt;.</div>
<div><br></div><div>Please resolve these comments along with any other Last=
 Call comments you may receive.</div><div><br></div><div>Document: draft-ie=
tf-lisp-lig-04</div><div>Reviewer: =A0Mary Barnes=A0</div><div>Review Date:=
 =A010 August 2011</div>
<div>IETF LC End Date: =A012 August 2011</div><div><br></div><div>Summary: =
=A0Ready with comments/nits</div><div><br></div><div>Comments/minor issues:=
</div><div>------------------------------------</div><div><br></div><div>- =
Section 3, Routing Locator definition: The third sentence is a little diffi=
cult to parse. =A0I would suggest to reword something like the following =
=A0(based on my interpretation of what the text is intended to say):</div>
<div>OLD:</div><div>=A0=A0 =A0 =A0Typically, RLOCs are</div><div>=A0=A0 =A0=
 =A0numbered from topologically-aggregatable blocks that are assigned</div>=
<div>=A0=A0 =A0 =A0to a site at each point to which it attaches to the glob=
al</div><div>=A0=A0 =A0 =A0Internet; where the topology is defined by the c=
onnectivity of</div>
<div>=A0=A0 =A0 =A0provider networks, RLOCs can be thought of as PA address=
es.</div><div>NEW:</div><div>=A0=A0 =A0 =A0Typically, RLOCs are</div><div>=
=A0=A0 =A0 =A0numbered from topologically-aggregatable blocks that are assi=
gned</div><div>=A0=A0 =A0 =A0to a site at each point to which it attaches t=
o the global</div>
<div>=A0=A0 =A0 =A0Internet. =A0Thus, the topology is defined by the connec=
tivity of</div><div>=A0=A0 =A0 =A0provider networks and RLOCs can be though=
t of as PA addresses. =A0=A0</div><div><br></div><div>Also, you&#39;ll have=
 to pardon my ignorance, but it&#39;s not obvious to me what PA stands for.=
 I googled and I think it&#39;s Provider Aggregatable (and not Physical Add=
ress, which was my first reaction). =A0I also found it expanded in draft-li=
sp-eid-block, which has a definition of RLOC that is mostly verbatim to thi=
s one, which makes me wonder why the terms need to be redefined in this doc=
ument and isn&#39;t there the potential for the definitions to become incon=
sistent?=A0</div>
<div><br></div><div>- Section 3, Endpoint ID definition. =A0It&#39;s not cl=
ear to me how SIP relates to LISP. =A0 I would think it&#39;s sufficient to=
 use a DNS lookup as the example and delete the non-specific reference to a=
 &quot;SIP Exchange&quot;. =A0</div>
<div><br></div><div>Nits:</div><div>-----</div><div><br></div><div>- Sectio=
n 2, 2nd paragraph: &quot;Map Resolvers&quot; -&gt; &quot;Map-Resolvers&quo=
t;</div><div>- Section 3, 2nd bullet: &quot;Map Replier&quot; -&gt; &quot;M=
ap-Replier&quot;=A0</div>
<div>- Section 3, last paragraph: &quot;for lig initiating site&quot; -&gt;=
 &quot;for the lig initiating site&quot;</div><div>- Section 3, last paragr=
aph: shouldn&#39;t &quot;lig self&quot; be &quot;ligging yourself&quot;?=A0=
</div>
<div>- Section 4.1, last paragraph before sample output for ligging yoursel=
f:</div><div>&quot;to originating site&quot; -&gt; &quot;to the originating=
 site&quot; =A0</div><div><br></div><div><br></div>

--20cf307d04caab797e04aa2ba721--

From mnot@mnot.net  Wed Aug 10 18:40:49 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94D7C21F8BC4 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 18:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.623
X-Spam-Level: 
X-Spam-Status: No, score=-105.623 tagged_above=-999 required=5 tests=[AWL=-3.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8uepjbxMiYi for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 18:40:49 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id E832321F8BB8 for <ietf@ietf.org>; Wed, 10 Aug 2011 18:40:48 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.98.127]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id AF386509DB for <ietf@ietf.org>; Wed, 10 Aug 2011 21:41:15 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Fwd: New Non-WG Mailing List: sami -- State Migration 
Date: Thu, 11 Aug 2011 11:41:12 +1000
References: <20110810212225.4803721F8715@ietfa.amsl.com>
To: IETF Discussion <ietf@ietf.org>
Message-Id: <BEDE0671-0196-43B5-940B-E6CDDBF20D09@mnot.net>
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 01:40:49 -0000

I'm curious -- why was a new list created, when there's already a =
(fairly quiet) clouds@ mailing list?

(just trying to reduce the absurd number of mailing lists I need to =
follow)


Begin forwarded message:

> From: IETF Secretariat <ietf-secretariat@ietf.org>
> Subject: New Non-WG Mailing List: sami -- State Migration=20
> Date: 11 August 2011 7:22:25 AM AEST
> To: IETF Announcement list <ietf-announce@ietf.org>
> Cc: opsawg@ietf.org, dromasca@avaya.com, sami@ietf.org
>=20
>=20
>=20
> A new IETF non-working group email list has been created.
>=20
> List address: sami@ietf.org
> Archive: http://www.ietf.org/mail-archive/web/sami/
> To subscribe: https://www.ietf.org/mailman/listinfo/sami (Subject to =
List Administrator Approval)
>=20
> Purpose: To facilitate Virtual Machine(VM) migration without =
disruption to running applications and security, service state =
associated with the specific migrating VM needs to be migrated too. This =
mail list is used for discussions on use cases, scope, and potential =
standard works.=20
>=20
> For additional information, please contact the list administrators.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

--
Mark Nottingham   http://www.mnot.net/




From joelja@bogus.com  Wed Aug 10 21:40:43 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3382C21F8A6F for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 21:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cp7Qpx5kbo97 for <ietf@ietfa.amsl.com>; Wed, 10 Aug 2011 21:40:42 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7D92B11E8073 for <ietf@ietf.org>; Wed, 10 Aug 2011 21:40:42 -0700 (PDT)
Received: from zorch.lan (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7B4f1Zn026124 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 11 Aug 2011 04:41:13 GMT (envelope-from joelja@bogus.com)
Subject: Re: is IETF trying to do too much?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <17974.1312465503@marajade.sandelman.ca>
Date: Wed, 10 Aug 2011 21:10:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D9CAEEA-C7F6-4BE2-BC83-F989663BA17E@bogus.com>
References: <F9F155A0-142F-4D48-8A89-690BC22CECB1@acmepacket.com> <E9E015CE-912E-4509-988C-53047CFD923B@lilacglade.org> <D992EEF2-5DAE-4884-951E-8B8CD370657C@network-heretics.com> <24260.1312393889@marajade.sandelman.ca> <4E399097.4080409@acm.org> <17974.1312465503@marajade.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 11 Aug 2011 04:41:15 +0000 (UTC)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 04:40:43 -0000

On Aug 4, 2011, at 6:45 AM, Michael Richardson wrote:

>=20
>>>>>> "Marc" =3D=3D Marc Petit-Huguenin <petithug@acm.org> writes:
>    Marc> I personally would like to switch to the Tufte style,
>    Marc> (i.e. uploading a printout, which can also be distributed to
>    Marc> people before the meeting in printed form, and having *only* =
a
>    Marc> discussion), but I am not sure how people will react.
>=20
> I agree.
> I would modify to say that projected slides with diagrams on them are =
a
> good thing to permit discussion.

I'm reasonably certain that the reason than v6ops has between 13-19 =
minutes allotted for each of the drafts on the agenda (which not all the =
drafts or problems) is not because of the projector.


> --=20
> ]       He who is tired of Weird Al is tired of life!           |  =
firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net =
architect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ =
|device driver[
>   Kyoto Plus: watch the video =
<http://www.youtube.com/watch?v=3Dkzx1ycLXQSE>
> 	               then sign the petition.=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From ole@cisco.com  Thu Aug 11 00:17:10 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1F421F84BF for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 00:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WIECztyhVE+2 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 00:17:08 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id A08A121F8448 for <ietf@ietf.org>; Thu, 11 Aug 2011 00:17:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1359; q=dns/txt; s=iport; t=1313047061; x=1314256661; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=6/Gy9j1LO3XO10w3q4Cf6qJafzzupbu4VESJDp139ro=; b=NMeXjw92g/MjBE+GWkFWXABIsnXfSJefeLyKU+OwXgoN98H2M8vS+4lO MSQOWAtlRlNdjUS3ojFkz9SRx7gBA0A6HLMDr3MLP2ayLqQtHbeulFzxK lYgk4Xvk/bUOLxl6d8VYYJonln+lbnzubNvAMeEMagnOJEh2Hq90I7+0r M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EABCBQ06rRDoJ/2dsb2JhbAA+A6dHd4FAAQEBAQIBEgECASQ/BQsLDgouVwYTGgiHTASdeQGDHw8BmzmDQIMGBIdflSOHGw
X-IronPort-AV: E=Sophos;i="4.67,355,1309737600"; d="scan'208";a="12068653"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-8.cisco.com with ESMTP; 11 Aug 2011 07:17:40 +0000
Received: from sjc-vpn7-506.cisco.com (sjc-vpn7-506.cisco.com [10.21.145.250]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7B7Hd7R019003; Thu, 11 Aug 2011 07:17:39 GMT
Date: Thu, 11 Aug 2011 00:17:39 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Glen Zorn <gwz@net-zen.net>
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <4E4250BC.9070305@net-zen.net>
Message-ID: <alpine.OSX.2.01.1108110005390.50372@sjc-vpn7-506.cisco.com>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <a06240800ca6713e13df6@[10.31.201.42]> <4E41831E.9030209@gmail.com> <alpine.DEB.2.00.1108100924200.4709@uplift.swm.pp.se> <alpine.OSX.2.01.1108100058040.40148@sjc-vpn7-506.cisco.com> <4E4250BC.9070305@net-zen.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 07:17:10 -0000

Glen,

I am NOT arguing against holding a meeting in Thailand if we find a 
suitable venue, sponsors, available dates and all that. I was merely 
pointing out that companies and governments tend to over-react and 
issue blanket warnings and bans for places with the kind of unrest we 
are talking about. The APNIC meeting is a classic illustration of the 
problem: a relatively small (but violent) protest in one part of 
Bangkok basically ends up turning all of Thailand into a no-go zone 
for a very long time.

Since I have not hear a single word of news from Thailand for a long
time (apart from that story about the jailed American author), I 
assume things are "just fine" there nowadays. Human trafficking 
nothwithstanding :-)

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 10 Aug 2011, Glen Zorn wrote:

> On 8/10/2011 3:06 PM, Ole Jacobsen wrote:
> 
> ...
> 
> > I would NOT want to be in the business of moving an IETF meeting 2
> > months before the event.
> 
> Certainly not, but all hell can break loose with little or no warning
> virtually anywhere (see
> http://www.boston.com/bigpicture/2011/08/london_riots.html).
> 
> ...
> 

From swmike@swm.pp.se  Thu Aug 11 00:44:12 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE1321F88A6 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 00:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EO6fEFkaHAzS for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 00:44:11 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 8B4D321F889F for <ietf@ietf.org>; Thu, 11 Aug 2011 00:44:10 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9466C9F; Thu, 11 Aug 2011 09:44:41 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8FEE69E for <ietf@ietf.org>; Thu, 11 Aug 2011 09:44:41 +0200 (CEST)
Date: Thu, 11 Aug 2011 09:44:41 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: Queen Sirikit National Convention Center
In-Reply-To: <alpine.OSX.2.01.1108110005390.50372@sjc-vpn7-506.cisco.com>
Message-ID: <alpine.DEB.2.00.1108110937410.4709@uplift.swm.pp.se>
References: <4E3B9FC6.7090701@net-zen.net> <9828472B-FD8C-4579-8F9C-0D68E3263BD0@mnot.net> <4E3F8199.2090809@net-zen.net> <44669682-8560-4100-8871-F6876BB695F6@mnot.net> <alpine.OSX.2.01.1108080049490.15710@sjc-vpn7-506.cisco.com> <a06240800ca6713e13df6@[10.31.201.42]> <4E41831E.9030209@gmail.com> <alpine.DEB.2.00.1108100924200.4709@uplift.swm.pp.se> <alpine.OSX.2.01.1108100058040.40148@sjc-vpn7-506.cisco.com> <4E4250BC.9070305@net-zen.net> <alpine.OSX.2.01.1108110005390.50372@sjc-vpn7-506.cisco.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 07:44:12 -0000

On Thu, 11 Aug 2011, Ole Jacobsen wrote:

> Since I have not hear a single word of news from Thailand for a long 
> time (apart from that story about the jailed American author), I assume 
> things are "just fine" there nowadays. Human trafficking 
> nothwithstanding :-)

They just performed an election 
<http://en.wikipedia.org/wiki/Thai_general_election,_2011> and there was a 
clear winner and the result doesn't seem to be contested, so right now 
there are no obvious issues to cause major political problems.

Basically, the "red shirt" protesters from last year got their party 
elected, so if there are going to be protests, it'll be some other group.

Of course, 2013 is a long way out so there is no way to tell for sure, but 
as someone else wrote, London right now shows that there is nothing that 
is sure anywhere.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From daedulus@btconnect.com  Thu Aug 11 01:41:42 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC06E21F8B0E for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 01:41:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zz2evoThdZPW for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 01:41:42 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by ietfa.amsl.com (Postfix) with ESMTP id DBA7B21F8B0C for <ietf@ietf.org>; Thu, 11 Aug 2011 01:41:41 -0700 (PDT)
Received: from host81-159-99-55.range81-159.btcentralplus.com (HELO pc6) ([81.159.99.55]) by c2bthomr14.btconnect.com with SMTP id DXQ78622; Thu, 11 Aug 2011 09:42:12 +0100 (BST)
Message-ID: <00ce01cc57f9$b66be7e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <mrex@sap.com>
References: <201108100500.p7A50TdF018207@fs4113.wdf.sap.corp>
Subject: Re: subject_prefix on IETF Discuss?
Date: Thu, 11 Aug 2011 09:38:46 +0200
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.4E4395E3.0065, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.11.74514:17:7.586, ip=81.159.99.55, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_PATH, __INT_PROD_COMP, BODY_SIZE_1900_1999, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr14.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.4E4395E5.009E,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 08:41:42 -0000

----- Original Message -----
From: "Martin Rex" <mrex@sap.com>
To: "Barry Leiba" <barryleiba@computer.org>
Cc: <ietf@ietf.org>
Sent: Wednesday, August 10, 2011 7:00 AM

Barry Leiba wrote:
>
> On Tue, Aug 9, 2011 at 1:16 PM, Martin Rex <mrex@sap.com> wrote:
> > If one intends to actually *process* close to all of the Emails hitting
> > one's inbox in near real time, then List-Id:, and any pre-sorting based
> > on it, will _always_ slow down processing (unless the MUA or the processing
> > is flawed).
> >
> > Whereas a subject prefix significantly facilitates tracking of stuff
> > in a single large inbox. I'm getting 300+/day Emails and try to read >95%
> > of it (my company internal Email is completely seperate at ~30/day, though).
>
> This makes no sense to me, Martin.  Please explain why sorting based
> on a subject prefix will work, while sorting based on a List-ID header
> field will not.

I do not sort EMail at all (my MUA does not support sorting).
subject_prefix _obviates_ sorting.

MUAs typically display the inbox with (status,sender,subject,received-time).

With subject_prefix I can quite easily tell apart discussions from several
IETF mailing lists, and it works with _every_ MUA with default settings.

<tp>
Until you get a Last Call, which is cross posted to the WG list, and some
replies have
[wgfb] and some do not, and then it gets cross posted to SAAG and we get
[wgfb][saag] or [saag][wgfb] or [saag] or [wgfb] or ....  You could of course
request an update to all MUAs to ignore prefixes when collating.

But nope, prefixes are a dead technology; do not insert them on the IETF list
(speaking as one whose MUA, supplied by the manufacturer who supplies most of
the world's MUAs, cannot do anything with List-Id:-(.

Tom Petch
</tp>

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


From stbryant@cisco.com  Thu Aug 11 02:40:07 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1513F21F8ABB; Thu, 11 Aug 2011 02:40:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.554
X-Spam-Level: 
X-Spam-Status: No, score=-110.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AreF9hftziU; Thu, 11 Aug 2011 02:40:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1BA21F8AD8; Thu, 11 Aug 2011 02:40:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=936; q=dns/txt; s=iport; t=1313055640; x=1314265240; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bw3V98fBLbap01lcm8onoOXNwJmZq/BFy3c5iBKEfm8=; b=M93q8sErCbatqjrgIWhufafSs8O0qnrr9L/YfD1XQO6gFkrBPUhLW+5N Fv64j3OWitNPw3ylFNgymQXSmooE9lERUis/bgnKtG4KuC16EZ9Pz1paY 79tdty9uCaGK+q9kbsQF5J/Hlfgb+QuhqyLW7sOfNtm8fuhqOISO0NwD3 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtcGAJmiQ06Q/khR/2dsb2JhbABBmEGPCHeBQAEBAQEDEgECASI6BgEQCxgJFg8JAwIBAgFFEwEHAQEepX4Bgx8PAZtHhkYEkw6QcA
X-IronPort-AV: E=Sophos;i="4.67,355,1309737600"; d="scan'208";a="110019602"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 11 Aug 2011 09:40:39 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7B9edWj003499; Thu, 11 Aug 2011 09:40:39 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p7B9eb81013296; Thu, 11 Aug 2011 10:40:38 +0100 (BST)
Message-ID: <4E43A395.5070507@cisco.com>
Date: Thu, 11 Aug 2011 10:40:37 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Gen-ART LC Review of draft-shiomoto-ccamp-switch-programming
References: <F18F3E79-4E0C-4071-B85D-638D3BD0FD6D@nostrum.com> <041501cc578c$3a12f2a0$ae38d7e0$@olddog.co.uk>
In-Reply-To: <041501cc578c$3a12f2a0$ae38d7e0$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'Ben Campbell' <ben@nostrum.com>, draft-shiomoto-ccamp-switch-programming.all@tools.ietf.org, gen-art@ietf.org, 'The IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 09:40:07 -0000

On 10/08/2011 19:35, Adrian Farrel wrote:
> Hi Ben,
>
> Thanks for reading.
>
>> Nits/editorial comments:
>>
>> -- section 1, paragraph 4: "...with relation to the programming..."
>>
>> ... in relation to...
> Yeah. RFC Editor note if Stewart is watching (although I'm guessing the RFC
> Editor might just fix this anyway).
>
>> -- 3.1, last paragraph:
>>
>> Note that the references say SHOULD rather than MUST. Using "must not" here,
>> even non-normatively, seems a bit overstated.
> Disagree. The caveat is that we are defining something different. We are looking
> at the case where we want to know that it is safe to start sending data. We are
> using the existence of some "SHOULD" statements in related RFCs that describe
> related behavior, to derive a "must" that covers when it is known to be safe.
>

Point 1 in the RFC editor's note, point 2 assumed to be addressed by the 
above email.

Stewart

From dromasca@avaya.com  Thu Aug 11 06:45:45 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D886821F8A1A for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 06:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.918
X-Spam-Level: 
X-Spam-Status: No, score=-102.918 tagged_above=-999 required=5 tests=[AWL=-0.319, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2dfellFrPgU8 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 06:45:45 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1219221F898E for <ietf@ietf.org>; Thu, 11 Aug 2011 06:45:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtAAAIvbQ07GmAcF/2dsb2JhbABBl36PSHeBQAEBAQEDAQEBCwQeCisJFwQCAQgNAQMDAQEBCwIEDAsBBgEmHwkIAQEEARIIARmHUaBTApwdhWhfBJg3i0g
X-IronPort-AV: E=Sophos;i="4.67,355,1309752000"; d="scan'208";a="201356648"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 11 Aug 2011 09:46:18 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Aug 2011 09:43:03 -0400
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: New Non-WG Mailing List: sami -- State Migration 
Date: Thu, 11 Aug 2011 15:46:16 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04037E1892@307622ANEX5.global.avaya.com>
In-Reply-To: <BEDE0671-0196-43B5-940B-E6CDDBF20D09@mnot.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Non-WG Mailing List: sami -- State Migration 
Thread-Index: AcxXx84JtrKpATVcSSiflnvajOS1jgAY/wkA
References: <20110810212225.4803721F8715@ietfa.amsl.com> <BEDE0671-0196-43B5-940B-E6CDDBF20D09@mnot.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Mark Nottingham" <mnot@mnot.net>, "IETF Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 13:45:46 -0000

Hi Mark,

The scope of the new mail list is much more restricted than the one of
the clouds list.=20

I acknowledge that there is a balance we all need to keep within
reasonable limits between many too focused lists and lesser more general
lists. My opinion is that it's better to discuss on lists that are
focused on manageable and smaller lists of items. Hopefully not too many
of them.=20

BTW - was not clouds@ shut down? In any case I do not see it listed at
http://www.ietf.org/list/nonwg.html.=20

Regards,

Dan




> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
> Mark Nottingham
> Sent: Thursday, August 11, 2011 4:41 AM
> To: IETF Discussion
> Subject: Fwd: New Non-WG Mailing List: sami -- State Migration
>=20
> I'm curious -- why was a new list created, when there's already a
> (fairly quiet) clouds@ mailing list?
>=20
> (just trying to reduce the absurd number of mailing lists I need to
> follow)
>=20
>=20
> Begin forwarded message:
>=20
> > From: IETF Secretariat <ietf-secretariat@ietf.org>
> > Subject: New Non-WG Mailing List: sami -- State Migration
> > Date: 11 August 2011 7:22:25 AM AEST
> > To: IETF Announcement list <ietf-announce@ietf.org>
> > Cc: opsawg@ietf.org, dromasca@avaya.com, sami@ietf.org
> >
> >
> >
> > A new IETF non-working group email list has been created.
> >
> > List address: sami@ietf.org
> > Archive: http://www.ietf.org/mail-archive/web/sami/
> > To subscribe: https://www.ietf.org/mailman/listinfo/sami (Subject to
> List Administrator Approval)
> >
> > Purpose: To facilitate Virtual Machine(VM) migration without
> disruption to running applications and security, service state
> associated with the specific migrating VM needs to be migrated too.
> This mail list is used for discussions on use cases, scope, and
> potential standard works.
> >
> > For additional information, please contact the list administrators.
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> --
> Mark Nottingham   http://www.mnot.net/
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From ben@nostrum.com  Wed Aug 10 11:45:50 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8F3C21F8B0F; Wed, 10 Aug 2011 11:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.415
X-Spam-Level: 
X-Spam-Status: No, score=-102.415 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FucvijPYJ7Wb; Wed, 10 Aug 2011 11:45:50 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE5E21F8B0A; Wed, 10 Aug 2011 11:45:50 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p7AIkLgX054314 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 10 Aug 2011 13:46:22 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC Review of draft-shiomoto-ccamp-switch-programming
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <041501cc578c$3a12f2a0$ae38d7e0$@olddog.co.uk>
Date: Wed, 10 Aug 2011 13:46:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8231CB2F-7E4A-4AC5-9530-A674B56F6DE7@nostrum.com>
References: <F18F3E79-4E0C-4071-B85D-638D3BD0FD6D@nostrum.com> <041501cc578c$3a12f2a0$ae38d7e0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1244.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Thu, 11 Aug 2011 08:13:59 -0700
Cc: draft-shiomoto-ccamp-switch-programming.all@tools.ietf.org, gen-art@ietf.org, 'The IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2011 18:45:51 -0000

On Aug 10, 2011, at 1:35 PM, Adrian Farrel wrote:

> Disagree. The caveat is that we are defining something different. We =
are looking
> at the case where we want to know that it is safe to start sending =
data. We are
> using the existence of some "SHOULD" statements in related RFCs that =
describe
> related behavior, to derive a "must" that covers when it is known to =
be safe.
>=20

Okay, that makes sense. It might not hurt (but would be okay not to) to =
add a sentence explaining that this doc suggests a stronger requirement =
than in the source RFCs in order to be sure of safety.

Thanks!

Ben.=

From rsk@gsp.org  Thu Aug 11 07:21:42 2011
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C98D921F89BE for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 07:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.549
X-Spam-Level: 
X-Spam-Status: No, score=-5.549 tagged_above=-999 required=5 tests=[AWL=1.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N3H4D88B+it4 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 07:21:39 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id 5AEF221F8997 for <ietf@ietf.org>; Thu, 11 Aug 2011 07:21:39 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.113.dsl.charm.net [207.114.17.113]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id p7BEMA1S031917 for <ietf@ietf.org>; Thu, 11 Aug 2011 10:22:12 -0400 (EDT)
Received: from vorlon.gsp.org (vorlon.gsp.org [192.168.0.20]) by squonk.gsp.org (8.14.3/8.14.3) with ESMTP id p7BEQB1I021374 for <ietf@ietf.org>; Thu, 11 Aug 2011 10:26:11 -0400 (EDT)
Received: from localhost6.localdomain6 (localhost.localdomain [127.0.0.1]) by vorlon.gsp.org (8.14.3/8.14.3/Debian-9.2ubuntu1) with ESMTP id p7BEM5lQ012907 for <ietf@ietf.org>; Thu, 11 Aug 2011 10:22:05 -0400
Received: (from rsk@localhost) by localhost6.localdomain6 (8.14.3/8.14.3/Submit) id p7BEM3fJ012903 for ietf@ietf.org; Thu, 11 Aug 2011 10:22:03 -0400
Date: Thu, 11 Aug 2011 10:22:03 -0400
From: Richard Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
Message-ID: <20110811142203.GA8143@gsp.org>
References: <DB04A5B3-3F7C-4536-8EA4-633F9BBB4ACA@network-heretics.com> <201108091716.p79HGdhL008452@fs4113.wdf.sap.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201108091716.p79HGdhL008452@fs4113.wdf.sap.corp>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Thu, 11 Aug 2011 08:13:59 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 14:21:42 -0000

On Tue, Aug 09, 2011 at 07:16:39PM +0200, Martin Rex wrote:
> Whereas a subject prefix significantly facilitates tracking of stuff
> in a single large inbox.  I'm getting 300+/day Emails and try to read >95%
> of it (my company internal Email is completely seperate at ~30/day, though).

Let me start with a preamble: I think that those of us who choose
to "drink from the firehose" by subscribing to many mailing lists
or newsgroups or RSS feeds, especially those with lots of traffic,
have by doing so taken upon ourselves the obligation of finding
and configuring the right tools to make our decisions work for us.
(And in a complementary way, I think those operating those resources,
have taken upon themselves the obligation to run those resources per
spec, e.g. -request per RFC 2142, List-Id per RFC 2919, and so on.)
When everyone does so, things work very smoothly...which is ummm, kinda
the reason that we have these standards.


Now, to the substance of what you've said:

I'm not surprised this presents difficulties: funneling all incoming
mail into one mailbox means that...all incoming mail is in one mailbox.
And while it's still possible to sort, tag, and filter that mail easily
if you have a quality mail client [1] those tasks aren't as easy as
they could be if that mail was in separate mailboxes.

So let me suggest this methodology, which isn't the right one or the
best one or anything like that, just one that works for me.  Decide which
mailing lists are important to you, which are less important, etc.
Use procmail to sort all incoming messages on a per-list basis into
individual files in directories named accordingly, e.g:

	high/outages
	medium/nanog
	medium/ietf
	medium/ip
	medium/infowarrior
	low/funsec
	low/nanog-announce

Now it's all pre-sorted by list, making it easy to peruse any of them,
and all the lists are organized by priority, making it easier to decide
which ones to read when you're pressed for time.  (It's also possible to
clone incoming messages with procmail so that you can also have a
single file that has copies of everything, just in case you want that.)

No need for subject-line tags.  And everything is nicely separated so
that if you choose to search it it's easy to focus on what you want.
This also makes it easy to handle archiving, deletion, and other
mail-related tasks.

---rsk

[1] I use and highly recommend mutt, which is lightweight, pretty secure,
full-featured, extensible, well-supported, works beautifully via ssh,
and runs on all professional-quality operating systems.  It's also quite
efficient and makes many common mail tasks very easy and fast.

From rsk@gsp.org  Thu Aug 11 07:48:54 2011
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA1D621F8888 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 07:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.724
X-Spam-Level: 
X-Spam-Status: No, score=-5.724 tagged_above=-999 required=5 tests=[AWL=0.875,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6uYXPRV8tNi for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 07:48:54 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3424521F8770 for <ietf@ietf.org>; Thu, 11 Aug 2011 07:48:54 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.113.dsl.charm.net [207.114.17.113]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id p7BEnRig015925 for <ietf@ietf.org>; Thu, 11 Aug 2011 10:49:28 -0400 (EDT)
Received: from vorlon.gsp.org (vorlon.gsp.org [192.168.0.20]) by squonk.gsp.org (8.14.3/8.14.3) with ESMTP id p7BErSnq001540 for <ietf@ietf.org>; Thu, 11 Aug 2011 10:53:28 -0400 (EDT)
Received: from localhost6.localdomain6 (localhost.localdomain [127.0.0.1]) by vorlon.gsp.org (8.14.3/8.14.3/Debian-9.2ubuntu1) with ESMTP id p7BEnMMp021808 for <ietf@ietf.org>; Thu, 11 Aug 2011 10:49:22 -0400
Received: (from rsk@localhost) by localhost6.localdomain6 (8.14.3/8.14.3/Submit) id p7BEnMbG021802 for ietf@ietf.org; Thu, 11 Aug 2011 10:49:22 -0400
Date: Thu, 11 Aug 2011 10:49:22 -0400
From: Richard Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
Message-ID: <20110811144922.GA19146@gsp.org>
References: <CAC4RtVBso47fhsPJ6X0ja4Y0kn5fMoFFMk0cE3V7mJ4dhdNLuA@mail.gmail.com> <201108100500.p7A50TdF018207@fs4113.wdf.sap.corp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201108100500.p7A50TdF018207@fs4113.wdf.sap.corp>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Thu, 11 Aug 2011 08:14:00 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 14:48:55 -0000

On Wed, Aug 10, 2011 at 07:00:29AM +0200, Martin Rex wrote:
> With subject_prefix I can quite easily tell apart discussions from several
> IETF mailing lists, and it works with _every_ MUA with default settings.

The fact that poor, broken, obsolete, or non-standards-compliant
MUAs exist is not a valid reason for inflicting a fundamentally-broken
kludge on the people who have chosen their MUAs with care.

And actually, no, you can't *always* tell those discussion apart,
nor can you tell them from off-list replies...because (a) discussions
which cross multiple lists may carry the subject-line tags from
each list and (b) off-list replies will also -- unless someone takes the
time to hand-edit the Subject line and remove the tag or mark it
[off-list] -- carry the tag.  This is one of the many reasons why
List-Id is vastly superior: it solves both these problems.

For example, consider these exquisite little inconveniences (chosen
from thousands of examples on hand):

	Subject: Re: [asterisk-security] [asterisk-dev] dahdi system.conf update
	Subject: [WEB SECURITY] [HITB-Announce] HITB2011AMS Conference Materials
	Subject: [opensuse-project] Re: [opensuse-testing] Re: [opensuse-factory] Request to change MS6

I like the last one particularly: as the conversation thread migrated,
the subject-line tags managed to gradually colonize the entire Subject
line, thereby obliviating the actual Subject.  (Yes, incidentally, I suppose
you could set up your MUA to honor the leftmost tag, but that does nothing
to solve problem (b) above or any of the other I haven't bothered to enumerate,
and anyway if your MUA is that smart...then you could just use List-Id.)

And I haven't even gotten into all the circumstances where [.*] appears
on a Subject line and has nothing to do with the mailing list's name.

---rsk

From ajs@anvilwalrusden.com  Thu Aug 11 08:24:23 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D6AA21F888A for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 08:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjHyyP+irF1a for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 08:24:22 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id AD9EA21F8B2F for <ietf@ietf.org>; Thu, 11 Aug 2011 08:24:20 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 66B741ECB41D for <ietf@ietf.org>; Thu, 11 Aug 2011 15:24:55 +0000 (UTC)
Date: Thu, 11 Aug 2011 11:24:52 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
Message-ID: <20110811152452.GI95640@shinkuro.com>
References: <CAC4RtVBso47fhsPJ6X0ja4Y0kn5fMoFFMk0cE3V7mJ4dhdNLuA@mail.gmail.com> <201108100500.p7A50TdF018207@fs4113.wdf.sap.corp> <20110811144922.GA19146@gsp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110811144922.GA19146@gsp.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 15:24:23 -0000

On Thu, Aug 11, 2011 at 10:49:22AM -0400, Richard Kulawiec wrote:

> And actually, no, you can't *always* tell those discussion apart,
> nor can you tell them from off-list replies.

List headers don't guarantee helping with that, though, either,
because many lists will supporess the echo of the list mail to you if
you are also mentioned in the addressee headers.  Given the prevalence
of people using reply-all, that happens often.  Then some mail in the
discussion arrives in your inbox and other mail arrives in the list
box.  And yes, this could be alleviated by people replying just to the
list, but a lot of mail clients seem not to provide a convenient way
to do that.

I don't want the additional subject line cruft, but the list headers
are not a magic answer.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From stpeter@stpeter.im  Thu Aug 11 08:54:46 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D86221F8A95 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 08:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.639
X-Spam-Level: 
X-Spam-Status: No, score=-102.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PA1EJf8om70f for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 08:54:45 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C676221F85CA for <ietf@ietf.org>; Thu, 11 Aug 2011 08:54:45 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9AE3D41477; Thu, 11 Aug 2011 09:57:02 -0600 (MDT)
Message-ID: <4E43FB67.2040305@stpeter.im>
Date: Thu, 11 Aug 2011 09:55:19 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: New Non-WG Mailing List: sami -- State Migration
References: <20110810212225.4803721F8715@ietfa.amsl.com> <BEDE0671-0196-43B5-940B-E6CDDBF20D09@mnot.net> <EDC652A26FB23C4EB6384A4584434A04037E1892@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04037E1892@307622ANEX5.global.avaya.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 15:54:46 -0000

On 8/11/11 7:46 AM, Romascanu, Dan (Dan) wrote:

> BTW - was not clouds@ shut down? In any case I do not see it listed at
> http://www.ietf.org/list/nonwg.html. 

It was indeed closed down.

/psa

From mrex@sap.com  Thu Aug 11 08:58:46 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1963B21F8BB9 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 08:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.004
X-Spam-Level: 
X-Spam-Status: No, score=-10.004 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EyBMNWi0Pfvf for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 08:58:45 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 5156121F8BBA for <ietf@ietf.org>; Thu, 11 Aug 2011 08:58:45 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p7BFx0h0002742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 11 Aug 2011 17:59:00 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>
Subject: Re: subject_prefix on IETF Discuss?
To: rsk@gsp.org (Richard Kulawiec)
Date: Thu, 11 Aug 2011 17:58:59 +0200 (MEST)
In-Reply-To: <20110811142203.GA8143@gsp.org> from "Richard Kulawiec" at Aug 11, 11 10:22:03 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 15:58:46 -0000

Richard Kulawiec wrote:
> 
> Let me start with a preamble: I think that those of us who choose
> to "drink from the firehose" by subscribing to many mailing lists

List-Id: is only useful for folks who have either lots of time on
their hands, or want to use automatic archival and have no desire
to actually process the email they're receiving.

> 
> Now, to the substance of what you've said:
> 
> I'm not surprised this presents difficulties: funneling all incoming
> mail into one mailbox means that...all incoming mail is in one mailbox.

Yes, and that is the most efficient way to perform full processing.
I'm a simple human being that can focus his mind and his eyesight
only on one single thing at a time, so everything has to be serialized
anyway, and no amount of slicing and dicing the stuff will reduce
the amount of processing -- but most of it will incur additional actions
to open it when it is not queued in a single inbox.


>
> And while it's still possible to sort, tag, and filter that mail easily
> if you have a quality mail client [1] those tasks aren't as easy as
> they could be if that mail was in separate mailboxes.

seperate mailboxes is OK for archiving, but it adds complexity and
costs additional time if the intention is to really process 95% of the
stuff (5% is junk that I delete without opening).


-Martin

From barryleiba.mailing.lists@gmail.com  Thu Aug 11 09:25:30 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE3F21F8C3A for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 09:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.044
X-Spam-Level: 
X-Spam-Status: No, score=-103.044 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjcLRA0WBeeX for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 09:25:30 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 52BC921F8C39 for <ietf@ietf.org>; Thu, 11 Aug 2011 09:25:30 -0700 (PDT)
Received: by ywm21 with SMTP id 21so1590504ywm.31 for <ietf@ietf.org>; Thu, 11 Aug 2011 09:26:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=GTHczJK44Y0mBurHSeKdddS1vRA81KbzIslOIUhdpbo=; b=w3IK65yzOn4isCdQSF7t7+LK5W3nDbeMNyyu/s0H/7NjNZ+EvqdgLaxuCXWWmPo/dW W3dr/EzVbg7HECaJ4DAOYlBww3ZeCrKGw8sjnyrEr05VxxyPA4r5pWWCYQCbUbWIWLtW vzd16ZZaWOVRXUcQku6C/ImcT/7rPHtcLYFsM=
MIME-Version: 1.0
Received: by 10.147.87.18 with SMTP id p18mr8724463yal.24.1313079964627; Thu, 11 Aug 2011 09:26:04 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.181.13 with HTTP; Thu, 11 Aug 2011 09:26:04 -0700 (PDT)
In-Reply-To: <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>
References: <20110811142203.GA8143@gsp.org> <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>
Date: Thu, 11 Aug 2011 12:26:04 -0400
X-Google-Sender-Auth: 28Q6AJbinulrMtsbeImvsutzYds
Message-ID: <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>
Subject: Re: subject_prefix on IETF Discuss?
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 16:25:31 -0000

> List-Id: is only useful for folks who have either lots of time on
> their hands, or want to use automatic archival and have no desire
> to actually process the email they're receiving.
...
> I'm a simple human being that can focus his mind and his eyesight
> only on one single thing at a time, so everything has to be serialized
> anyway, and no amount of slicing and dicing the stuff will reduce
> the amount of processing -- but most of it will incur additional actions
> to open it when it is not queued in a single inbox.

Martin, please don't assume that everyone deals with their email the
way you do.  I sort my mail using List-ID header fields, each list's
messages go into a separate mailbox (organized much the way Richard
Kulawiec suggests), and I find it *fabulously* useful and efficient.
Still, I would never suggest that you had to do it that way, nor that
your way isn't useful.  Your way isn't useful FOR ME.  Apparently, my
way isn't useful FOR YOU.  =C0 chacun, son go=FBt, after all.

So the question really goes to the mailman people: can we get an
option to make the prefix inclusion a subscriber option?  Each list
would have a default behaviour, but each user could change it (just as
I now change every list's "suppress duplicates" option when I
subscribe to it, which makes sure my folders contain complete
threads).  That would make everyone happy.

As long as the option goes by mailing list, and everyone has to eat
the preference of whoever sets up the list, we'll have endless and
non-productive arguments (like this one) about it.

Barry

From joelja@bogus.com  Thu Aug 11 09:29:45 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4523F21F8C21 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 09:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, J_CHICKENPOX_55=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cj0PX551vS25 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 09:29:44 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9369321F8C19 for <ietf@ietf.org>; Thu, 11 Aug 2011 09:29:42 -0700 (PDT)
Received: from [10.101.144.59] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7BGUEmZ064411 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 11 Aug 2011 16:30:15 GMT (envelope-from joelja@bogus.com)
Subject: Re: subject_prefix on IETF Discuss?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <20110811152452.GI95640@shinkuro.com>
Date: Thu, 11 Aug 2011 09:30:08 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <022AB9B7-14FE-4B0D-B3C5-A2BF0E7E4A40@bogus.com>
References: <CAC4RtVBso47fhsPJ6X0ja4Y0kn5fMoFFMk0cE3V7mJ4dhdNLuA@mail.gmail.com> <201108100500.p7A50TdF018207@fs4113.wdf.sap.corp> <20110811144922.GA19146@gsp.org> <20110811152452.GI95640@shinkuro.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 11 Aug 2011 16:30:15 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 16:29:45 -0000

On Aug 11, 2011, at 8:24 AM, Andrew Sullivan wrote:

> On Thu, Aug 11, 2011 at 10:49:22AM -0400, Richard Kulawiec wrote:
> 
>> And actually, no, you can't *always* tell those discussion apart,
>> nor can you tell them from off-list replies.
> 
> List headers don't guarantee helping with that, though, either,
> because many lists will supporess the echo of the list mail to you if
> you are also mentioned in the addressee headers.  Given the prevalence
> of people using reply-all, that happens often.  Then some mail in the
> discussion arrives in your inbox and other mail arrives in the list
> box.  And yes, this could be alleviated by people replying just to the
> list, but a lot of mail clients seem not to provide a convenient way
> to do that.

:0 Whc: msgid.lock
| formail -D 8192 msgid.cache
:0 a:
.duplicates/

is pretty much magical if you have the ability to procmail.

> I don't want the additional subject line cruft, but the list headers
> are not a magic answer.
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 


From moore@network-heretics.com  Thu Aug 11 10:00:39 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3B521F8B4C for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 10:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.426
X-Spam-Level: 
X-Spam-Status: No, score=-3.426 tagged_above=-999 required=5 tests=[AWL=0.173,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfEUE+KNWy6v for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 10:00:38 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id A2E2421F8B4A for <ietf@ietf.org>; Thu, 11 Aug 2011 10:00:38 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2468B20B8F; Thu, 11 Aug 2011 13:01:13 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 11 Aug 2011 13:01:13 -0400
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=FfVDIQhvxdbjwHFiGeLan0niQLw=; b=Of ZhOdcDnIDOvuHh3Tqn7Qe/hBF68sb74QPRT3DA8zf6H8dnSbu4iEu2Wrb+RAz/Ow 0iWwY8I/A/+mByew6dHKe2QRgAcgPFfMWvRiSqx7NrBpSDZaFddRNki8ncNHRLkB LqQt/2lESL9DkVZWuho2+luCwofB9yfXFpNkl0W9M=
X-Sasl-enc: W/ONt8JPhcON8n68WyWSiBMc5bAzui1ayKy9k9B1Hgno 1313082072
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2EEAF45CC20; Thu, 11 Aug 2011 13:01:12 -0400 (EDT)
Subject: Re: subject_prefix on IETF Discuss?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>
Date: Thu, 11 Aug 2011 13:01:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <782AD17E-9C28-445E-A894-8658873A88C2@network-heretics.com>
References: <20110811142203.GA8143@gsp.org> <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp> <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 17:00:39 -0000

On Aug 11, 2011, at 12:26 PM, Barry Leiba wrote:

>> List-Id: is only useful for folks who have either lots of time on
>> their hands, or want to use automatic archival and have no desire
>> to actually process the email they're receiving.
> ...
>> I'm a simple human being that can focus his mind and his eyesight
>> only on one single thing at a time, so everything has to be =
serialized
>> anyway, and no amount of slicing and dicing the stuff will reduce
>> the amount of processing -- but most of it will incur additional =
actions
>> to open it when it is not queued in a single inbox.
>=20
> Martin, please don't assume that everyone deals with their email the
> way you do.  I sort my mail using List-ID header fields, each list's
> messages go into a separate mailbox (organized much the way Richard
> Kulawiec suggests), and I find it *fabulously* useful and efficient.
> Still, I would never suggest that you had to do it that way, nor that
> your way isn't useful.  Your way isn't useful FOR ME.  Apparently, my
> way isn't useful FOR YOU.  =C0 chacun, son go=FBt, after all.

Something that I've observed for many years is that people really don't =
like to change the tools and practices that they have used regularly and =
for a long time, even when new tools and/or practices are more =
functional.

(It turns out that I'm the same way.   Back in the winter of 1980 I =
ported James Gosling's Emacs to VMS.  I haven't used Gosling Emacs since =
circa 1985, but I'm still using Gosling's key bindings.  I've ported =
those key bindings to every editor I've used since then.  I programmed =
almost exclusively in C between 1980 and 2009 or so, at which point I =
started learning Python and now write most of my code in it.  I have no =
regrets about learning Python, but I also have no regrets at sticking =
with C for so long.   Even though GUI interfaces have long since become =
commonplace on desktops, the application that I use most is still a =
terminal emulator as an interface to bash.   And I'd still be using MH =
to read my mail if it had decent IMAP support.)

So if people want to stick with mail user agents that don't recognize =
List-ID, if they want to have all of their mail end up in one mailbox, =
if they want to use "sort by subject" to classify their incoming mail - =
I don't blame them.   Sure there are better tools these days, but it's =
understandable if they are hesitant to invest the time required to =
evaluate and learn new tools and new ways of handling mail, and =
potentially disrupt their ability to communicate while doing so.

Munging the subject field of mailing list traffic is really ugly, but =
many people have long-entrenched work habits that rely on it.  I don't =
think that existing lists should change their behavior, and I certainly =
don't think it should be the default behavior for new lists, but I would =
like to see it be a subscriber option for new lists.

Keith


From ihalfar@fit.vutbr.cz  Thu Aug 11 11:28:16 2011
Return-Path: <ihalfar@fit.vutbr.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C85821F8B4D for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 11:28:16 -0700 (PDT)
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_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q+w1YUPwUK96 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 11:28:15 -0700 (PDT)
Received: from kazi.fit.vutbr.cz (kazi6.fit.vutbr.cz [IPv6:2001:67c:1220:808::93e5:80c]) by ietfa.amsl.com (Postfix) with ESMTP id 606D621F8B51 for <ietf@ietf.org>; Thu, 11 Aug 2011 11:28:15 -0700 (PDT)
Received: from [172.16.254.2] (dhcpu061.fit.vutbr.cz [147.229.181.61]) (authenticated user=ihalfar mech=PLAIN bits=0) by kazi.fit.vutbr.cz (envelope-from ihalfar@fit.vutbr.cz) (8.14.5/8.14.4) with ESMTP id p7BISk8h022987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 11 Aug 2011 20:28:47 +0200 (CEST)
Date: Thu, 11 Aug 2011 20:28:45 +0200 (CEST)
From: Patrik Halfar <ihalfar@fit.vutbr.cz>
X-X-Sender: xeg@andromeda
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
In-Reply-To: <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>
Message-ID: <alpine.LNX.2.00.1108112013440.27441@andromeda>
References: <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>
User-Agent: Alpine 2.00 (LNX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Scanned-By: MIMEDefang 2.71 on 147.229.8.12
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 18:28:16 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 11 Aug 2011, Martin Rex wrote:

> Richard Kulawiec wrote:
>>
>> Let me start with a preamble: I think that those of us who choose
>> to "drink from the firehose" by subscribing to many mailing lists
>
> List-Id: is only useful for folks who have either lots of time on
> their hands, or want to use automatic archival and have no desire
> to actually process the email they're receiving.

Don't understand your note List-Id: require lots of time.

>
>>
>> Now, to the substance of what you've said:
>>
>> I'm not surprised this presents difficulties: funneling all incoming
>> mail into one mailbox means that...all incoming mail is in one mailbox.
>
> Yes, and that is the most efficient way to perform full processing.
> I'm a simple human being that can focus his mind and his eyesight
> only on one single thing at a time, so everything has to be serialized
> anyway, and no amount of slicing and dicing the stuff will reduce
> the amount of processing -- but most of it will incur additional actions
> to open it when it is not queued in a single inbox.
>

I'm simple human as well and I need processing most of e-mail on mobile 
devices. Then prefixes in subject don't allow see subject on first sight. 
What's more sorting into directories allowes  download just required 
messages and don't download lists which can wait.


>
>>
>> And while it's still possible to sort, tag, and filter that mail easily
>> if you have a quality mail client [1] those tasks aren't as easy as
>> they could be if that mail was in separate mailboxes.
>
> seperate mailboxes is OK for archiving, but it adds complexity and
> costs additional time if the intention is to really process 95% of the
> stuff (5% is junk that I delete without opening).
>
>
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

Patrik

- -- 
Ing. Patrik Halfar
Faculty of Information Technology
Bozetechova 2, 612 66 Brno, Czech republic
  Phone: +420 (541) 14-1327 (VUT/office)
  Phone: +420 (606) 609-172
Jabber: xeg@jabbim.cz (private)
    PGP: B577 58A0 2125 161D 294C 7F77 17B6 B8F0 BE0A 9B1D
    Web: http://www.fit.vutbr.cz/~ihalfar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBAgAGBQJORB9dAAoJEBe2uPC+CpsdkQUP/iBkNod2RT1GqTNIrCkprIuJ
IbhGI1mYONR/IWw5EkonmgasyQnoJmiEr4qftN6xZ5OvrwpElRdKRCRcTLflyaD0
+6y5jzOnuHVe2ZQ8OKo/s8HmuspiQ3mj/PXZ+xz9RydlAJwZodV/Uf8SXUnyFpMN
xdlSqa0uDhU3Yproa7YuE4xD9V4BPmajAU7rDRwk2/v/RiehXJPwby8tpn1vtWju
xm94aQwU0aoHNBAe+/ntaAB4rZ6H3Zbg9vU4nCbnNygmk8bghRaFVlQugSH9uPSE
hGHjurtLt4Vps2lgnz2cNdgrHhe/EYb5PoeezJDw0N9q/5lFFlx/ITeuo3cg7HtS
SoESZwSr4AkINRKaluMrsHiYs6iS4at7USjbZnxCv0sBuaVGuAVZqcdKxV9gP158
d3iHc2DtZ/uyjak7sxFTIhCFD3ksCYMpkhwkv61YsCFubs3kjyJkhT1RQsB6ZXEV
yxYPAWYGveHisQayWP6nC/EehsLm/T3ZemMRcqAjFc3mFp9TkfBumAdEzfaLchN5
BtaahJxm5O/t5Vh6uRb9zt1Ybc8pVI5auKqYWWVQUSa5G0tEpe4ODmL6ES9f69sK
D3nlMAc+FCnqUWLgOuwpZCqlGS92xiKGYoFlHRztUr8hLnZP1kZtfiwxvn4Pzsy5
uMnRyjoCUlmkaGKPNjF/
=QmsU
-----END PGP SIGNATURE-----

From randy@psg.com  Thu Aug 11 15:11:24 2011
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C25C21F8AAC; Thu, 11 Aug 2011 15:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYZsa2RC5AMs; Thu, 11 Aug 2011 15:11:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A38C021F8AA8; Thu, 11 Aug 2011 15:11:23 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <randy@psg.com>) id 1QrdTq-000Did-Ae; Thu, 11 Aug 2011 22:11:58 +0000
Date: Fri, 12 Aug 2011 07:11:57 +0900
Message-ID: <m2k4aja98y.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>, IETF IDR <idr@ietf.org>
Subject: Re: [Idr] Last Call: <draft-ietf-idr-deprecate-as-sets-05.txt>	(Deprecation of	the use of BGP AS_SET, AS_CONFED_SET.) to Informational RFC
In-Reply-To: <20110811154722.11750.88395.idtracker@ietfa.amsl.com>
References: <20110811154722.11750.88395.idtracker@ietfa.amsl.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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 22:11:24 -0000

> The IESG has received a request from the Inter-Domain Routing WG (idr) to
> consider the following document:
> - 'Deprecation of the use of BGP AS_SET, AS_CONFED_SET.'
>   <draft-ietf-idr-deprecate-as-sets-05.txt> as an Informational RFC

i have read and support this document.  AS-Sets are essentially unused,
the deprecation is needed for the sidr work, and their removal will make
many research and ops tools which run against bgp announcements easier.

randy

From mnot@mnot.net  Thu Aug 11 16:09:48 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C31F21F85A0 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 16:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.595
X-Spam-Level: 
X-Spam-Status: No, score=-105.595 tagged_above=-999 required=5 tests=[AWL=-2.996, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-X2kszbU6wD for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 16:09:47 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id B2D5421F871C for <ietf@ietf.org>; Thu, 11 Aug 2011 16:09:47 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.98.127]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C547D50A64; Thu, 11 Aug 2011 19:10:02 -0400 (EDT)
Subject: Re: New Non-WG Mailing List: sami -- State Migration
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4E43FB67.2040305@stpeter.im>
Date: Fri, 12 Aug 2011 09:09:58 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBE8CF6D-9469-499E-B5F2-EDA0322945B4@mnot.net>
References: <20110810212225.4803721F8715@ietfa.amsl.com> <BEDE0671-0196-43B5-940B-E6CDDBF20D09@mnot.net> <EDC652A26FB23C4EB6384A4584434A04037E1892@307622ANEX5.global.avaya.com> <4E43FB67.2040305@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1244.3)
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 23:09:48 -0000

On 12/08/2011, at 1:55 AM, Peter Saint-Andre wrote:

> On 8/11/11 7:46 AM, Romascanu, Dan (Dan) wrote:
>=20
>> BTW - was not clouds@ shut down? In any case I do not see it listed =
at
>> http://www.ietf.org/list/nonwg.html.=20
>=20
> It was indeed closed down.

Hmm. <https://www.ietf.org/mailman/listinfo/clouds> doesn't indicate =
this, and I was able to subscribe on 2 July. I haven't seen anything =
on-list since that would indicate it's closed (excepting the silence, of =
course).

When lists are shut down, it'd be nice if the appropriate clean-up was =
done as well; e.g., disallowing subscriptions, appropriate notice on the =
front page.

Cheers,=20

P.S. Yet another example of our "Beware of the Leopard" communication =
style at the IETF :)


--
Mark Nottingham   http://www.mnot.net/




From fluffy@cisco.com  Thu Aug 11 17:42:44 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1067911E808B for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 17:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.183
X-Spam-Level: 
X-Spam-Status: No, score=-104.183 tagged_above=-999 required=5 tests=[AWL=-0.184, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_56=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4cQ8vq60E4X for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 17:42:41 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 8871411E8080 for <ietf@ietf.org>; Thu, 11 Aug 2011 17:42:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=32205; q=dns/txt; s=iport; t=1313109797; x=1314319397; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=p4XZZcwGftGi10cHZgUk1Pmsh+zxeaDTuaXUtMELzS0=; b=bc8Tv3Ho6pPXNu+LIh7hnrlrimp2+pNIVtY0B91d6f+7jgXCBbuEmAIH RFC+9SgmlyzOxnD+gd4i4ADnP1Se7ViAIEXdF3tTIcBIWAniDnhlicTqo rYn2fgAM9/6+KcKnAKmTg6kNgNx9kcQ3kXdAiAe1pledgyxzrsq6Jilyg Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADh2RE6rRDoG/2dsb2JhbABBp153gUABAQEBAgEBAQEPAQcNRwsFCwsUBC4nMAYTIodNBJoHAZ5zhWhfBIdfizCRDw
X-IronPort-AV: E=Sophos;i="4.67,359,1309737600"; d="scan'208";a="12395305"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-3.cisco.com with ESMTP; 12 Aug 2011 00:43:15 +0000
Received: from dhcp-171-68-21-78.cisco.com (dhcp-171-68-21-78.cisco.com [171.68.21.78]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7C0hF4o021696; Fri, 12 Aug 2011 00:43:15 GMT
Subject: Re: Gen-ART Review: Last Call <draft-ietf-p2psip-base-17.txt>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com>
Date: Thu, 11 Aug 2011 17:43:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D9C4F6D-53B4-4F77-AB4E-45A4BA911406@cisco.com>
References: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 00:42:44 -0000

Thanks for the detailed review - you caught some good stuff. Most of =
this makes essence but we should probably talk about usage of 2119 =
language.=20

On Aug 9, 2011, at 16:05 , Mary Barnes wrote:
> simple
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Document: draft-ietf-p2psip-base-17
> Reviewer:  Mary Barnes=20
> Review Date:  9 August  2011
> IETF LC End Date: 22 July 2011
>=20
> Summary: Not Ready. =20
>=20
> Comments:
> ----------------
> The document is very a dense (with detailed technical information) and =
long (150 page) specification for a Peer-to-peer signaling protocol.  =
While the overall technical functionality seems fairly correct and =
thoroughly specified, the primary issue is a tremendous lack of =
normative language in the main body of the document.  Non-inclusive =
details of such are included below. =20

The 2119 MUST/SHOULD/MAY terms are simply abbreviations for some words =
defined in 2119, and different WGs have different styles about how =
extensively they should be used. P2PSIP has obviously been on the more =
sparing side of that spectrum. This isn't to say that there aren't any =
places where it would be useful to add such language, but rather that =
our policy has been to add it principally where there is likely =
ambiguity, rather than everywhere where behavior is defined. I'll work =
thought these and see where they might help reduce the chance of a an =
implementers doing the wrong thing but in generally when we define a =
structure in something like ASN.1 or ABNF, if the structure always has a =
field X, we just use the language like ASN.1 or ABNF to indicate it =
always has that. We don't  also say it MUST be there.=20

>=20
> Major Issues:
> -------------------
>=20
> General:=20
> --There is a fair number of cases where normative language should be =
used.  I have detailed some (but certainly not all)  instances where it =
is lacking with proposed rewording.  I have also noted cases where it is =
used (lower case) where it could be confused with needing normative =
language and where it isn't necessary and there are some cases where =
it's just not clear. I consider these major since it can impact =
interoperability and could lead developers to not implement key =
functionality. =20
>=20
> --There is also little or no normative language for the majority of =
the elements in the structures - i.e., the reader has to assume which =
elements are mandatory and which are optional and it's not always clear. =
  For example, rather than saying "Field x contains blah", it should say =
"Field x MUST contain blah" and rather than "The contents of the message =
will be x, y and z", it should say something like "The message MUST (or =
SHOULD) contain x, y and z".  I have not detailed the places where this =
is necessary in most cases.  The authors should review the detailed =
definition for each of the messages.=20
>=20

However, the syntax actually tells you whether a field is mandatory or =
not. I.e.,
there is a "select/case" syntax for indicating optional fields (and some =
fields are
variable length). So I don't think it's really ambiguous in the general =
case whether
a field need be present.

With that said, this seems like something that would be better discussed =
real time - I may be missing the point on some of these. When would be a =
good time to have a call?

> --The message names are used inconsistently.  The IANA registry has =
the message codes all lower case.  There are places in the examples and =
the body of the document where the _req part is missing, there is no =
"_", the first letters are Upper case, etc.  The messages are also used =
in a general sense - e.g., "MUST perform an Attach", which should really =
be stated as "MUST send an attach_req message)

Well, it's the Attach is much more than sending a attach_req and we =
found that trying to add more just make the document even longer and =
harder to understand than it currently is. We been pretty careful about =
the case as some systems auto generate code out the the structures in =
the draft. I'm glad to walk through these and figure them out with you. =
That said, these have been changed various times and it's hard to find =
them all so there could certainly be a mistakes in this.=20


>=20
> Major - Detailed:
>=20
> - Sections 32.1, 3.2.2 and 3.3: lots of changes needed to reword using =
normative language. =20
>=20
> - Section 3.4, last paragraph: Needs to be reworded normatively and =
more precisely. It's really not clear to me what the required behavior =
is as it first says it needs to (which I'm not sure is a SHOULD or is =
REQUIRED to) maintain connections to all the peers near and enough =
others.., but how much is "enough".   Also, what is meant by the =
"specified link set" - is that referring to all the nearby peers or the =
peers+enough others?  Or is this more clearly (and normatively) =
specified elsewhere, such that a reference could be added =20

All of section 3 is overview and not meant to have the normative =
descriptions which happen in the later sections.=20

>=20
> - Section 4.2: needs normative language - i.e.:
> --"Each Usage needs to =85" ->  "Each Usage MUST=85"

This gets into the whole 2119 usage of words in requirements. Right here =
we are writing requirements for what future RFC needs to include.=20

>=20
> - Section 5.1.1: Bullet items need normative language
> -- 1st bullet: It's also  not clear what the its are in "it passes it =
up".  I think it should be "the node passes the message up to the upper =
layers".   However, this probably needs to be normative language - i.e., =
"the node MUST pass the message to the upper layers".  The same applies =
to the third bullet.=20
> --bullet 2:  "the message is destined for this node and is passed up=85"=
 -> "the message is destined for this node and MUST be passed=85.,=20

members of the WG objected to MUST level mandating of how the actually =
server software was architected. Note this passing up a level is not =
about anything to do with what happens on the wire. See section 6 of =
2119 which pretty much says not to use MUST this way.

>=20
> - Section 5.1.2:
> -- Paragraphs 5, 6, 7 and 8 need to be reworded to have normative =
statements.=20

Let's talk on the phone - I'm not seeing the issue here.=20

> -- Last paragraph (9) mixes normative text with in an example. The =
normative text needs to be separated from the example

seriously? I'm just not getting how this will help make it more =
interoperable but again, glad to change if we can figure out a real =
improvement.=20

> - e.g., split some of the sentences into the normative behavior and =
then the example.=20
>=20
> -Section 5.2.1 is totally inconsistent with the use of normative =
language (i.e., lower case occurrences and lack of KEY words) - =
shouldn't the following be normative statements something like the =
following:=20
> -- First paragraph:
> ---First sentence:  "a node constructs" -> "a node MUST construct".
> --- 3rd sentence: "resulting message will use the normal overlay =
routing" -> "resulting message MUST use the normal overlay routing"
> --- 4th sentence: "The node can also" ->  "The node MAY also"
> -- Third paragraph:=20
> --- 3rd sentence: "a single request can also" -> "a single request MAY =
also"
> -- Fourth paragraph:
> --- 1st sentence: this could be interpreted as normative:  "Because =
messages may" ->  "Because messages can"
2119 is very clear it refers to MAY and not may. I really don't know =
what word is best here but ignoring 2119, which word looks better "may" =
or "can" for this sentence?

> --- 3rd sentence:  "the request is retransmitted" ->  "the request =
MUST be retransmitted"
>=20

This all looks like internal software design to help

> -Section 5.3.2:=20
> -- General: some of the contents of the structure have normative =
language and others don't.  There is some normative behavior defined for =
these fields later, so perhaps adding section references as you do for =
some fields would be helpful. =20
>=20
> For example:=20
> --"overlay": shouldn't this be normative:  "the overlay name is hashed =
with SHA-1" -> "the overlay name MUST be hashed with SHA-1"
> --"destination_list": seems like some of this should be normative?=20
>=20
> -Section 5.3.2.1:
> --1st paragraph: shouldn't this be normative?=20
> "the configuration document has a sequence number" ->  "the =
configuration document MUST contain a sequence number"
> -- 1st paragraph, last sentence: "may"  -> "can"=20
>=20
> -Section 5.3.2.2:
> --Paragraph after the 1st structure:  Shouldn't this be stated =
normatively since it is described how the structure MUST be handled =
depending upon the contents? =20
> --Paragraph after second structure, suggest the following changes:
> ---"the generation counters should" ->  "the generation counters =
SHOULD"
> ---"An implementation could use.." -> "An implementation MAY use=85"
> ---"the node confirms that the generation counter matches" -> "the =
node MUST confirm that the generation counter matches"
> ---"If it does not match, it is silently dropped." -> "If it does not =
match, it MUST be silently dropped."
>=20
> -Section 5.3.3.1:
> --1st para: "a request returns" -> "a request MUST return"=20
> --1st para: "then the message code is the response code that matches =
the request" ->=20
> "then the message code MUST be set to the response code that matches =
the request"
> --2nd para: "message code is set" ->  "message code MUST be set"
>=20
> -Section 5.3.4 - needs normative language:
> --1st paragraph after GenericCertificate structure:
> ---"All signatures are formatted" -> "Alls signatures MUST be =
formatted"
> ---"The input structure=85varies.." ->  "The input structure =85 MAY =
vary=85"
>=20
> -Section 5.4.1: "need to be described" -> "MUST be described"=20
>=20
> -Section 5.4.2-Section 7.  These sections need to be carefully =
reviewed and updated appropriately with normative text.  [ I have marks =
up for pages 55-102 where normative language is needed if someone wants =
those scanned and forwarded - I'm just too lazy to type them all out.]=20=

>=20
> - Section 8:  There is only one actual normative word used in this =
section!  There is a lc "should" that ought to be "SHOULD".  I don't =
know if the authors assumed that the normative language in TURN was =
sufficient, but I do not believe that is the case as it leaves the =
normative behavior to be inferred by the reader/implementor. Rather than =
rewrite the whole section myself, the authors need to review carefully. =
For example, there are "needs to", which likely are really and lots of =
present tense statements (e.g., "The address of the peer is stored=85"), =
which ought to be MUSTs or SHOULDs.
>=20
> - Section 9.2:  seems like this needs normative language. Suggest the =
following:
> OLD:
>    For this Chord based topology plugin, the size of the Resource-ID =
is
>    128 bits.  The hash of a Resource-ID is computed using SHA-1
>    [RFC3174]then truncating the SHA-1 result to the most significant =
128
>    bits.
> NEW:
>    For Chord-RELOAD, the size of the Resource-ID MUST be=20
>    128 bits.  The hash of a Resource-ID MUST be computed using SHA-1
>    [RFC3174].  The SHA-1 result MUST be truncated to the most =
significant=20
>    128 bits.
>=20
> - Section 9.3: Needs normative language.=20
> OLD:=20
>    If a peer is not responsible for a Resource-ID k, but is directly
>    connected to a node with Node-ID k, then it routes the message to
>    that node.  Otherwise, it routes the request to the peer in the
>    routing table that has the largest Node-ID that is in the interval
>    between the peer and k.  If no such node is found, it finds the
>    smallest Node-Id that is greater than k and routes the message to
>    that node.
> NEW:=20
>    If a peer is not responsible for a Resource-ID k, but is directly
>    connected to a node with Node-ID k, then it MUST route the message =
to
>    that node.  Otherwise, it MUST route the request to the peer in the
>    routing table that has the largest Node-ID that is in the interval
>    between the peer and k.  If no such node is found, it MUST find the
>    smallest Node-Id that is greater than k and MUST route the message =
to
>    that node.
>=20
> - Section 9.4: Needs normative language. =20
>=20
> - Section 9.5: While this section does have a fair amount of normative =
language, it is still lacking in a few cases:=20
> --Item 2.:  "should" -> "SHOULD"
> --Item 5.:  "The AP sends the response=85" -> "The AP MUST send the =
response=85"=20
> --1st paragraph after list: "=85can directly connect=85" -> "MAY =
directly connect"
> --2nd paragraph after list: "it can still populate" -> "it MAY still =
populate"
> --2nd paragraph after list: the description of the use of PING should =
be reworded with normative language (I'll leave that exercise to the =
authors)
> --3rd paragraph after the list:  "JP simply sends" -> "JP MUST send"=20=

>=20
> - Section 9.7.1:
> --1st para:  ".., it then sends=85" -> ".., it then MUST send =85"
> --3rd para: needs normative language
> OLD:
>    In no event does
>    an attempt to reestablish connectivity with a lost neighbor allow =
the
>    peer to remain in the neighbor table.=20
> NEW:=20
>    In the case of=20
>    an attempt to reestablish connectivity with a lost neighbor, the =
peer=20
>    MUST not remain in the neighbor table.=20
> OR:=20
>    In the case of=20
>    an attempt to reestablish connectivity with a lost neighbor, the =
peer=20
>    MUST be removed from the neighbor table.
> -- 4th para: "should" -> "SHOULD" (2 cases),  "use Pings" -> "MUST use =
Pings"
>=20
> -Section 9.7.2:
> --1st para:  "..the failed peer are removed.." -> "=85the failed peer =
MUST be removed.."
> --2nd para:  "=85the peer initiates=85" -> "=85the peer MUST =
initiate.."
>=20
> -Section 9.7.3:
> --1st para after list:  "is needed" -> "is REQUIRED"
> --3rd para after list:  "the peer sends an Update" -> "the peer MUST =
send an Update"
>=20
> -Section 9.7.4.4:  Needs a scrub for normative language
>=20
> -Section 9.9: Needs a scrub for normative language.=20
>=20
> -Section 10.1: General: Needs a lot of work to be specified using =
normative language.  The majority of the configuration elements are not =
specified using normative language - for example, terms such as =
permitted, allowed, valid are used in statements rather than normative =
language
> or they are indicative of the need for normative language.  A specific =
example is in the definition for "clients-permitted":
>=20
> OLD:
>       This element represents whether clients are
>       permitted or whether all nodes must be peers.  If it is set to
>       "true" or absent, this indicates that clients are permitted.  If
>       it is set to "false" then nodes are not allowed to remain =
clients
>       after the initial join.=20
>=20
> NEW:=20
>       This element represents whether clients are
>       permitted or whether all nodes need to be peers.  If clients=20
>       are permitted, the element MUST be set to "true" or absent. =20
>       If the nodes are not allowed to remain clients after the=20
>       initial join, the element MUST be set to "false".
>=20
> --Section 10.1 - 4th para after the element list states that "All of =
the non optional values MUST be provided".  However, the list of =
elements in the previous paragraph are not specifically identified as =
non optional.  I think the first 3 are mandatory.  So, I would suggest =
to re-word the 3rd paragraph as follows and delete the 1st sentence in =
the 4th paragraph noted above:=20
> OLD:
>    In addition, the kind element contains the following elements:
>    max-count:  the maximum number of values which members of the =
overlay
>       must support.
>    data-model:  the data model to be used.
>    max-size:  the maximum size of individual values.
>    access-control:  the access control model to be used.
>    max-node-multiple:  This is optional and only used when the access
>       control is NODE-MULTIPLE.  This indicates the maximum value for
>       the i counter.  This is an integer greater than 0.
>=20
> NEW:=20
>    In addition, the kind element MUST contain the following elements:
>    max-count:  the maximum number of values which members of the =
overlay
>       must support.
>    data-model:  the data model to be used.
>    max-size:  the maximum size of individual values.
>    access-control:  the access control model to be used.
>=20
>    The kind element MAY also contain the following element:
>    max-node-multiple:  if the access control is NODE-MULTIPLE,=20
>       this element MAY be included. This indicates the maximum value =
for
>       the i counter.  It MUST be an integer greater than 0.  =20
>=20
> --Section 10.1, next to last para: There's no normative language, but =
it seems there should be since it is specifying specification =
computations and encoding that I believe are required.=20
>=20
> - Section 10.2:  Needs more normative language:
>=20
> -- 2nd para:=20
> OLD: This value is provided by the user or some other out of band=20
>      provisioning mechanism.
>=20
> NEW: This value MUST be provided by the user or some other out of band=20=

>      provisioning mechanism."
>=20
> -- 3rd para:=20
> OLD: =20
>    Once an address and URL for the configuration server is determined,
>    the peer forms an HTTPS connection to that IP address.=20
> NEW:=20
>    Once an address and URL for the configuration server is determined,
>    the peer MUST form an HTTPS connection to that IP address.=20
>=20
> -- 4th para:  "which replaces" ->  "which MUST replace"
>=20
> -- 5th para:  "nodes obtain the" -> "nodes MUST obtain the"
>=20
> - Section 10.3:=20
> -- 3rd para:  "is performed" -> "MUST be performed". =20
> -- 3rd para: Bullets need to be modified to normative.=20
> -- 4th para: "the certificate contains" -> "the certificate MUST =
contain"
> -- para after 2nd set of bullets:  needs normative language.
> -- 2nd para after 2nd set of bullets:  "The node then reads=85" ->  =
"The node MUST then use=85"
>=20
> - Section 10.5:
> --Second para: "the joining node first forms" -> "the joining node =
MUST first form"
> --3rd para:  text uses the phrase "it can note the Node-ID in the =
response and use this Node-ID to start sending requests".  It's not =
clear whether the use of the Node-ID is a MAY or a MUST. =20
>=20
> - Section 12. I'm assuming that the security directorate has reviewed =
this in detail, thus my focus in reviewing this section was on general =
understanding. The biggest issues is that there is NO normative language =
at all in the security section.  As in other sections, terms like =
"need", "are/is used/sent, etc.",  "ensure", lower case reserved words =
rather than upper case, etc. are used when normative language ought to =
have been used.=20
>=20
>=20
> - Section 13. IANA Registrations:
> - General: there seem to be several registries for which the =
usage/requirement is unclear as there's no mention of such in the body =
of the document.  In general, references to the sections in the document =
describing the information included in the registries would be more than =
helpful.
>=20
> - Section 13.5: Creates a RELOAD Application Registry, but the use and =
need for such isn't described elsewhere in the document=20

Section 5.5.2.1 defines the usage of this and contains the text=20

      A 16-bit application-id as defined in the Section 13.5.  This
      number represents the IANA registered application that is going to
      send data on this connection. =20

>=20
> - Section 13.12. Forwarding Options Registry. SEction 5.3.2.3 seems to =
define three flags for the Forwarding options type, so it's not clear to =
me why this registry has just "invalid" and "reserved"
>=20

The registry is for the ForwardingOptionsType code points and not the =
flags. Any new forwarding option could use any of these flags. The flags =
only indicate who needs to understand the the forwarding option.=20

>=20
> - Section 13.15:  Defines/registers a RELOAD URI schema but there is =
no mention of this URI anywhere else in the document.  In what context =
is it used?   =20

It would be used by other specifications that use Reload. It's not used =
inside of reload itself. Folks wanted it defined here so we kept it =
consistent and other specs could use the URI.=20

>        =20
>=20
> Minor  Issues:
> ---------------------
>=20
> - Section 1.2.1, 2nd paragraph: I don't understand the example as to =
why a single application requires multiple usages - i.e, why voicemail?  =
Isn't the intent to say that an application might need to use both SIP =
and XMPP - i.e., you wouldn't define a "usage" for an application, would =
you?  =20
storing voicemail in the DHT would require a different usage than the =
type of rendezvous service of XMPP or SIP

>=20
> - Section 2. Some of the definitions use terms that are not yet =
defined, so that's not particularly helpful - i.e,. Attach and Update =
are used. In some cases (e.g., Connection Table), you could just delete =
the statement with the reference.=20
>=20

I'm not sure how to resolve this. I agree that by the time we get to the =
definition, if you have not read the rest of the document, the sentence, =
" This includes nodes with which Attach handshakes have
      been done but which have not sent any Updates." does not currently =
mean something that you can understand. But after reading the document, =
this sense helps clear up something implementors were confused about so =
I definitely don't want to loose it. I'd like to fix this but not sure =
what you are suggesting. Are you suggesting just saying in these terms =
are defined later with a forward reference and leaving the sentence =
there?


> - Section 3.3, last paragraph.  Add a reference to 5.4.2.4  after =
"RouteQuery method"
>=20
> - Section 5.1: "If any of these are incorrect=85"  - need to specify =
what qualifies as "incorrect" - is it wrong formatting, invalid header =
field=20
> value, etc.?
>=20
> - Section 5.1.2:
> --1st paragraph: I have no idea what the "other three cases" =
references.=20
>=20
> - Section 5.2: "may be configured" -> "can be configured",  =
"alternative=20
> routing algorithms may be selected" -> "alternative routing algorithms =
MAY be selected"
>=20
> - Section 5.3:  The three parts of the messages are listed and the =
last sentence says that "The following sections describe the format of =
each part of the message", but there are 4 sub-sections in 5.3, with the =
first section NOT describing one of the three parts of the messages.  I =
suggest to strike that last sentence and just put references to the =
sections in the list items for each of the three messages.=20
>=20
> -Section 5.3.3:=20
> --"critical" description:  "Whether this extension must be.." "Whether =
this extension needs to be=85"=20
>=20
> -Section 5.3.4:  1st para after certificate structure:  "may contain" =
-> "MAY contain"=20
>=20
> -Section 5.5: It would be helpful to highlight that foundation, =
priority and type are based on ICE, in particular since ICE is not =
discussed until the subsequent section - e.g., "the foundation =
production" -> "the ICE foundation production".=20
>=20
> - Section 5.6: =20
> -- The last three paragraphs are confusing.=20
> ---In particular, it's not clear what algorithms are being referenced =
in this sentence:
>   "We will first define each of these algorithms, then
>    define overlay link protocols that use them."
> --- In the note paragraph, I believe "These protocols have been =
chosen=85" is referring to the three overlay link protocols supported by =
RELOAD per this document.
> ---The Note to implementors paragraph seems out of context
> --- Per my next comment, I suggest to move the detailed discussion of =
future overlay link protocols to the appendix, so some of this text may =
be relevant only to that.=20
>=20
> -Section 5.6.1:  I suggest that the sub-sections in this section be =
moved to an appendix and a reference to such be added.=20
>=20
> -Section 5.6.3.1.1, next to the last paragraph:
> "when a link may be failing" -> "when a link might be failing"
>=20
> - Section 9.1: While this is an overview, it seems to me that some of =
this is describing normative behavior (that I don't see specified else). =
 Per the general comment, I would reword the first sentence as follows:=20=

> OLD:
>    The algorithm described here is a modified version of the Chord
>    algorithm.
> NEW:
>     The algorithm described here, Chord-RELOAD is a modified version=20=

>     of the Chord algorithm.
>=20
> - Section 10.3, 1st para:  "required" -> "REQUIRED"
>=20
> - Section 10.3.1, last sentence: "must"  -> "MUST"
>=20
> - Section 10.4, 1st para, last sentence: "should use" -> "SHOULD use"
>=20
> - Section 11 - examples:
> --General - there are no detailed messages shown anywhere for the =
examples. There should be at least one, in particular given the comment =
above about the RELOAD URI that is registered, but not mentioned =
anywhere else in the document.=20
> --first example (see my nit below about the examples not being =
numbered or labeled in any way):  The third sentence says that "It gets =
routed to the admitting peer (AP), yet the flow shows that the message =
first gets routed to the PP and then onto AP. It would be helpful if =
that were clarified.=20
> -  Also (general), the text mentions the use of ICE.  It's not clear =
to me exactly where in the flow that happens - it would be good to =
annotate such (i.e., in a similar manner as the TLS is illustrated).=20
> - next to the last example (text on page 131, diagram on page 132): =
I'm quite confused as the text states that JP has received an update =
from AP and thus now knows APs predecessors, which are also JP's =
predecessors, so JP Attaches to them. However, the diagram does not show =
JP getting an Update from AP and it shows JP doing Updates to PPP and PP =
rather than Attaches (as the text suggests). =20
>=20
> - Section 13.10. Overlay link types: These specific string types are =
not used elsewhere in the document.  Suggest that a reference to 5.6 be =
added and these particular strings be included in parenthesis after the =
items in the list. =20

makes sense=20


>=20
>=20
> - Section 13.16, Security considerations portion:=20
> -- The first sentence doesn't make sense. Did you mean?=20
>    "This media type is typically not used to
>    transport information that needs to be kept confidential,=20
>    however, there are cases where the integrity of the information is
>    important."

yes - that is much better - this text was added late and received little =
review=20

> -- "then the contents of the file need to be=85" -> "then the contents =
of the file MUST be =85"  =20
>=20
>=20
>=20
> Nits:
> -----
> - General: kind is sometimes "Kind" and sometimes "kind".  The former =
is more readable and highlights it as a reserved word.=20

 Seems reasonable

>=20
> - Section 2. =20
> --General: It would be helpful if the terms were alphabetized.=20

this is easy to do but complicates the forward reference problem. =
Thoughts on what is best?

> --Node: "We use the term "Node" to refer to =85" -> "Refers to =85"
>=20
> - Section 3.2:
> -- 2nd para, last sentence:  "refer such" -> "refer to such"
that needs to b fixed

> -- 3rd para, 1st sentence:  "concept" -> "entity"
>=20
> - Section 4.1.4,
(this is section 4.1.1 for others reading this)=20

> 4th paragraph: I'm still not getting the applicability of voicemail as =
a RELOAD Kind (per the reference also in section 1.2.1).  I guess you =
are talking about a voicemail message (in this case) and a server or =
application in section 1.2.1?   Voicemail just does not seem like an =
obvious example to me. =20

All it is trying to say is the size of a storing the audio for a =
voicemail in the overlay is much larger than saving a link. Note that =
several people in the WG think it is nuts to try and save a full voice =
message in the overlay and several others think the opposite. This =
argument was avoid by explicitly mention in this draft the example of =
voicemail.

>=20
> - Section 5.1.1, last bullet:  "In that case,=85" ->  "In the latter =
case, =85"=20
make sense=20


>=20
> - Section 5.1.2:
> -- 2nd para:  "arrange" -> "ensure",  "This may be arranged" -> "This =
can be arranged=85"=20
make sense

> -- 3rd para (1st after bullets): It's not clear that A=85E is a set of =
ordered nodes in the example. I would suggest to reword as:
> OLD:
>    As an example of the first strategy, if node D=20
> NEW:=20
>   Consider an example with nodes A, B, C, D and E, respectively.  If=20=

>   node D=85.
ok

>=20
> - Section 5.3.1.1: First two sentences can be reworded more succinctly =
- you're not really providing definitions here, put rather describing =
the=20
> the syntax for and providing examples illustrative of the presentation =
language.=20
>=20
> OLD:=20
>    The following definitions are used throughout RELOAD and so are
>    defined here. =20

we really are defining opaque and true and false here=20

> They also provide a convenient introduction to how to
>    read the presentation language.
> NEW:=20
>    This section provides an introduction to the presentation language
>    used throughout RELOAD.=20
>=20
> - Section 5.3.3.1: Error_Data_Too_Old is duplicated.
that's embarrassing :-)=20

>=20
> - Section 5.5.1.6: Add references for SCTP and DCCP.=20
>=20
> - Section 6.4.1.3:  The reference to "this Version" is superfluous. =
Propose the following change:
> OLD:
>    This version of RELOAD (unlike previous versions) does not have an
>    explicit Remove operation.
> NEW:=20
>    RELOAD does not have an explicit Remove operation.

make sense

>=20
> - Section 9: General. The first sentence states that the algorithm =
defined here is referred to as "chord-reload", however, subsequent =
sections don't seem to use that term.

uh, that should have been upper case in this section.=20

>  It would be more clear if that term was used. And, really, it would =
be more consistent to use the term Chord-RELOAD. However, this should =
also be consistent with the IANA-Registration which has CHORD-RELOAD.=20
>=20
> - Section 9.7.4.3, 3rd para:=20
> -- Remove "Note to implementers".  Text already highlights that the =
text is specific to implementations.=20
> -- "may be found" -> "can be found"
>=20
> - Section 9.8:  "For this topology plugin" -> "For Chord-RELOAD"
>=20
> - Section 10.2, 2nd para:  "determines" -> "determining"
needs to be fixed

>=20
> - Section 11:=20
> - General: there are no labels for any of the call flows, so it's not =
always clear what the text is referring to.  In general, I think the =
text precedes the flow.=20
> - "abbreviation" -> "abbreviations"=20
needs to be fixed

>=20
> - Section 13.16:
> --Interoperability considerations:  "knows" -> "known"=20
needs to be fixed

>=20
> - Section 14: "provied" -> "provided"
needs to be fixed
>=20
> - Appendix C: Delete now - it's totally useless as is.
make sense

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


From sob@harvard.edu  Thu Aug 11 17:49:57 2011
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D26D21F8ACE for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 17:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.799
X-Spam-Level: 
X-Spam-Status: No, score=-102.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P+D5HFGZgbV6 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 17:49:56 -0700 (PDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by ietfa.amsl.com (Postfix) with ESMTP id 9F03121F8A70 for <ietf@ietf.org>; Thu, 11 Aug 2011 17:49:56 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by golem.sobco.com (Postfix) with ESMTP id EC7FC70C7C5C; Thu, 11 Aug 2011 20:50:31 -0400 (EDT)
Subject: Re: Gen-ART Review: Last Call <draft-ietf-p2psip-base-17.txt>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Scott O. Bradner" <sob@harvard.edu>
In-Reply-To: <6D9C4F6D-53B4-4F77-AB4E-45A4BA911406@cisco.com>
Date: Thu, 11 Aug 2011 20:50:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AC691A0-2E6C-4704-89AF-74602F1EB19F@harvard.edu>
References: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com> <6D9C4F6D-53B4-4F77-AB4E-45A4BA911406@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 00:49:57 -0000

fwiw - the author of 2119 thinks that less is more when it comes to the =
use of these terms

see, as Cullen points out, Section 6

but there is a balance - for example, if you define a structure and say =
that all fields are required, it is redundant to
use MUST with each example of using the structure

Scott

On Aug 11, 2011, at 8:43 PM, Cullen Jennings wrote:

>=20
> Thanks for the detailed review - you caught some good stuff. Most of =
this makes essence but we should probably talk about usage of 2119 =
language.=20
>=20
> On Aug 9, 2011, at 16:05 , Mary Barnes wrote:
>> simple
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>=20
>> Document: draft-ietf-p2psip-base-17
>> Reviewer:  Mary Barnes=20
>> Review Date:  9 August  2011
>> IETF LC End Date: 22 July 2011
>>=20
>> Summary: Not Ready. =20
>>=20
>> Comments:
>> ----------------
>> The document is very a dense (with detailed technical information) =
and long (150 page) specification for a Peer-to-peer signaling protocol. =
 While the overall technical functionality seems fairly correct and =
thoroughly specified, the primary issue is a tremendous lack of =
normative language in the main body of the document.  Non-inclusive =
details of such are included below. =20
>=20
> The 2119 MUST/SHOULD/MAY terms are simply abbreviations for some words =
defined in 2119, and different WGs have different styles about how =
extensively they should be used. P2PSIP has obviously been on the more =
sparing side of that spectrum. This isn't to say that there aren't any =
places where it would be useful to add such language, but rather that =
our policy has been to add it principally where there is likely =
ambiguity, rather than everywhere where behavior is defined. I'll work =
thought these and see where they might help reduce the chance of a an =
implementers doing the wrong thing but in generally when we define a =
structure in something like ASN.1 or ABNF, if the structure always has a =
field X, we just use the language like ASN.1 or ABNF to indicate it =
always has that. We don't  also say it MUST be there.=20
>=20








From tony@att.com  Thu Aug 11 21:01:49 2011
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 826CB21F86D0 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 21:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.125
X-Spam-Level: 
X-Spam-Status: No, score=-106.125 tagged_above=-999 required=5 tests=[AWL=0.474, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEzeoDGJhP1E for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 21:01:48 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id C3D4621F85FF for <ietf@ietf.org>; Thu, 11 Aug 2011 21:01:44 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-11.tower-119.messagelabs.com!1313121739!33689004!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 28014 invoked from network); 12 Aug 2011 04:02:20 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-11.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Aug 2011 04:02:20 -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 p7C42j2K013114 for <ietf@ietf.org>; Fri, 12 Aug 2011 00:02:45 -0400
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 p7C42fuQ013045 for <ietf@ietf.org>; Fri, 12 Aug 2011 00:02:41 -0400
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 p7C42FVe011637 for <ietf@ietf.org>; Fri, 12 Aug 2011 00:02:15 -0400
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 p7C428sc011077 for <ietf@ietf.org>; Fri, 12 Aug 2011 00:02:10 -0400
Received: from [135.70.147.162] (vpn-135-70-147-162.vpn.mwst.att.com[135.70.147.162]) by maillennium.att.com (mailgw1) with ESMTP id <20110812040208gw100e4leme> (Authid: tony); Fri, 12 Aug 2011 04:02:08 +0000
X-Originating-IP: [135.70.147.162]
Message-ID: <4E44A5BE.3050008@att.com>
Date: Fri, 12 Aug 2011 00:02:06 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
In-Reply-To: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 04:01:49 -0000

I support publication of this RFC.

     Tony Hansen
     tony@att.com

On 8/11/2011 9:37 AM, The IESG wrote:
> The IESG has received a request from the Yet Another Mail WG (yam) to
> consider the following document:
> - 'Message Submission for Mail'
>    <draft-ietf-yam-rfc4409bis-02.txt>  as a Full 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-08-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.

From msk@cloudmark.com  Thu Aug 11 21:38:55 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3DA21F874F for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 21:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.072
X-Spam-Level: 
X-Spam-Status: No, score=-103.072 tagged_above=-999 required=5 tests=[AWL=-0.473, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6lbSi1eEsPiH for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 21:38:54 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 8611C21F874C for <ietf@ietf.org>; Thu, 11 Aug 2011 21:38:54 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Thu, 11 Aug 2011 21:39:30 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 11 Aug 2011 21:39:28 -0700
Subject: RE: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
Thread-Topic: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
Thread-Index: AcxYpKvmdUg5gajdQGmdphifdUbR9QABPvlQ
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF6E3@EXCH-C2.corp.cloudmark.com>
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E44A5BE.3050008@att.com>
In-Reply-To: <4E44A5BE.3050008@att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 04:38:55 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of T=
ony Hansen
> Sent: Thursday, August 11, 2011 9:02 PM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submi=
ssion for Mail) to Full Standard
>=20
> I support publication of this RFC.

+1, which is to say:

- I've read it
- I agree with what it says
- I can't find any reason not to move it to Full Standard
- Nice job all around

-MSK

From narten@us.ibm.com  Thu Aug 11 21:53:14 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E559321F8698 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 21:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.577
X-Spam-Level: 
X-Spam-Status: No, score=-106.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xiJb9-J70K1i for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 21:53:14 -0700 (PDT)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id EB41721F8658 for <ietf@ietf.org>; Thu, 11 Aug 2011 21:53:13 -0700 (PDT)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e37.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7C4ntq9006730 for <ietf@ietf.org>; Thu, 11 Aug 2011 22:49:55 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7C4r4lS151254 for <ietf@ietf.org>; Thu, 11 Aug 2011 22:53:04 -0600
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 p7C4r4YR014963 for <ietf@ietf.org>; Thu, 11 Aug 2011 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7C4r3Fu014953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 11 Aug 2011 22:53:04 -0600
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 p7C4r3VJ029945 for <ietf@ietf.org>; Fri, 12 Aug 2011 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p7C4r2fs029872 for ietf@ietf.org; Fri, 12 Aug 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201108120453.p7C4r2fs029872@rotala.raleigh.ibm.com>
Date: Fri, 12 Aug 2011 00:53:02 -0400
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 04:53:15 -0000

Total of 119 messages in the last 7 days.
 
script run at: Fri Aug 12 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.76% |   14 |  9.31% |    89125 | gwz@net-zen.net
  2.52% |    3 | 14.56% |   139501 | mary.ietf.barnes@gmail.com
  6.72% |    8 |  5.28% |    50602 | john-ietf@jck.com
  5.04% |    6 |  4.02% |    38456 | joelja@bogus.com
  4.20% |    5 |  3.24% |    31042 | ole@cisco.com
  3.36% |    4 |  3.16% |    30302 | sm@resistor.net
  3.36% |    4 |  3.08% |    29485 | hsantos@isdg.net
  3.36% |    4 |  2.91% |    27832 | moore@network-heretics.com
  3.36% |    4 |  2.18% |    20923 | mnot@mnot.net
  1.68% |    2 |  3.68% |    35265 | ycai@cisco.com
  2.52% |    3 |  2.52% |    24136 | jounikor@gmail.com
  2.52% |    3 |  2.03% |    19446 | rsk@gsp.org
  0.84% |    1 |  3.70% |    35426 | fluffy@cisco.com
  2.52% |    3 |  1.73% |    16549 | dougb@dougbarton.us
  2.52% |    3 |  1.67% |    16019 | mrex@sap.com
  1.68% |    2 |  1.67% |    15997 | ned+ietf@mauve.mrochek.com
  0.84% |    1 |  2.32% |    22236 | marshall.eubanks@gmail.com
  1.68% |    2 |  1.33% |    12714 | evnikita2@gmail.com
  1.68% |    2 |  1.24% |    11853 | barryleiba@computer.org
  1.68% |    2 |  1.18% |    11267 | swmike@swm.pp.se
  1.68% |    2 |  1.10% |    10525 | dhc2@dcrocker.net
  0.84% |    1 |  1.86% |    17792 | tglassey@earthlink.net
  1.68% |    2 |  0.93% |     8886 | randy@psg.com
  0.84% |    1 |  1.16% |    11154 | narten@us.ibm.com
  0.84% |    1 |  1.15% |    11061 | pk@isoc.de
  0.84% |    1 |  1.08% |    10361 | medel@globetel.com.ph
  0.84% |    1 |  0.83% |     7938 | phdgang@gmail.com
  0.84% |    1 |  0.80% |     7709 | brian.e.carpenter@gmail.com
  0.84% |    1 |  0.77% |     7339 | ihalfar@fit.vutbr.cz
  0.84% |    1 |  0.74% |     7058 | john@jck.com
  0.84% |    1 |  0.74% |     7045 | dromasca@avaya.com
  0.84% |    1 |  0.72% |     6928 | daedulus@btconnect.com
  0.84% |    1 |  0.72% |     6891 | nsb@guppylake.com
  0.84% |    1 |  0.72% |     6857 | presnick@qualcomm.com
  0.84% |    1 |  0.71% |     6834 | bob.hinden@gmail.com
  0.84% |    1 |  0.70% |     6681 | rcallon@juniper.net
  0.84% |    1 |  0.69% |     6619 | rbonica@juniper.net
  0.84% |    1 |  0.68% |     6555 | frnkblk@iname.com
  0.84% |    1 |  0.68% |     6531 | mcr@sandelman.ca
  0.84% |    1 |  0.65% |     6248 | mail@sabahattin-gucukoglu.com
  0.84% |    1 |  0.65% |     6241 | sob@harvard.edu
  0.84% |    1 |  0.65% |     6191 | stbryant@cisco.com
  0.84% |    1 |  0.62% |     5909 | ed.lewis@neustar.biz
  0.84% |    1 |  0.60% |     5743 | dean.willis@softarmor.com
  0.84% |    1 |  0.59% |     5667 | eburger@standardstrack.com
  0.84% |    1 |  0.59% |     5642 | fred@cisco.com
  0.84% |    1 |  0.58% |     5565 | msk@cloudmark.com
  0.84% |    1 |  0.58% |     5518 | pfsinoz@gmail.com
  0.84% |    1 |  0.57% |     5469 | warren@kumari.net
  0.84% |    1 |  0.56% |     5373 | vesely@tana.it
  0.84% |    1 |  0.56% |     5360 | cabo@tzi.org
  0.84% |    1 |  0.55% |     5298 | dworley@avaya.com
  0.84% |    1 |  0.54% |     5205 | adrian@olddog.co.uk
  0.84% |    1 |  0.54% |     5169 | hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com
  0.84% |    1 |  0.54% |     5154 | ynir@checkpoint.com
  0.84% |    1 |  0.54% |     5134 | julian.reschke@gmx.de
  0.84% |    1 |  0.53% |     5035 | ben@nostrum.com
  0.84% |    1 |  0.52% |     5004 | ajs@anvilwalrusden.com
  0.84% |    1 |  0.50% |     4808 | johnl@iecc.com
  0.84% |    1 |  0.48% |     4568 | stpeter@stpeter.im
  0.84% |    1 |  0.48% |     4554 | wjhns1@hardakers.net
--------+------+--------+----------+------------------------
100.00% |  119 |100.00% |   957795 | Total

From ynir@checkpoint.com  Thu Aug 11 22:25:36 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B59821F86BA for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 22:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.349
X-Spam-Level: 
X-Spam-Status: No, score=-10.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UfcSES4oE7OJ for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 22:25:36 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7772F21F8663 for <ietf@ietf.org>; Thu, 11 Aug 2011 22:25:35 -0700 (PDT)
X-CheckPoint: {4E44C68A-4-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p7C5OfsA018055;  Fri, 12 Aug 2011 08:24:41 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Fri, 12 Aug 2011 08:24:41 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "mrex@sap.com" <mrex@sap.com>
Date: Fri, 12 Aug 2011 08:24:47 +0300
Subject: Re: subject_prefix on IETF Discuss?
Thread-Topic: subject_prefix on IETF Discuss?
Thread-Index: AcxYsCK3I0Q7JRlLTnKhLwyZPScJaA==
Message-ID: <B662509F-C3E4-4684-8D22-F1ADB8E51CE8@checkpoint.com>
References: <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>
In-Reply-To: <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 05:25:36 -0000

On Aug 11, 2011, at 6:58 PM, Martin Rex wrote:

> Richard Kulawiec wrote:
>>=20
>> Let me start with a preamble: I think that those of us who choose
>> to "drink from the firehose" by subscribing to many mailing lists
>=20
> List-Id: is only useful for folks who have either lots of time on
> their hands, or want to use automatic archival and have no desire
> to actually process the email they're receiving.

Not sure why this is. I sort by the list address in the to: or cc: fields, =
but that's a limitation of my MTA.

>=20
>>=20
>> Now, to the substance of what you've said:
>>=20
>> I'm not surprised this presents difficulties: funneling all incoming
>> mail into one mailbox means that...all incoming mail is in one mailbox.
>=20
> Yes, and that is the most efficient way to perform full processing.
> I'm a simple human being that can focus his mind and his eyesight
> only on one single thing at a time, so everything has to be serialized
> anyway, and no amount of slicing and dicing the stuff will reduce
> the amount of processing -- but most of it will incur additional actions
> to open it when it is not queued in a single inbox.

I think the opposite. Suppose I'm subscribed to WebSec, TLS, PKIX and IETF.=
 There are different threads running in all 4 lists. I come to work in the =
morning, and see that I have several messages on all lists. If I read them =
one-by-one in one mailbox, I have to switch contexts for the different thre=
ads. If they're sorted into four mailboxes, I can follow one thread, and th=
en another. MUAs can try to sort by thread, but occasionally fail (when peo=
ple change subjects, like "How to use MUAs (was: subject_prefix on IETF Dis=
cuss?)", or when we get a "Re:" equivalent in some foreign language), so I =
prefer to see them sorted by date rather than grouped by threads. I'd rathe=
r make less context switches and just read mails from a single list grouped=
 together, but that's just me. You may have a different way of handing too =
much email.=

From hsantos@isdg.net  Thu Aug 11 23:23:12 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99A1A11E8088 for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 23:23:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.309
X-Spam-Level: 
X-Spam-Status: No, score=-3.309 tagged_above=-999 required=5 tests=[AWL=-0.710, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CfkFFvrAT11B for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 23:23:11 -0700 (PDT)
Received: from ntbbs.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id E13B511E807F for <ietf@ietf.org>; Thu, 11 Aug 2011 23:23:10 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1677; t=1313130169; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=8CR0C6uwMBU+BkiQK6WTXMsNz5s=; b=t21yKrRwUtVW4WrL4oJo VTC3se0PSNIRKn3+67e30ONJDM0zmcruZDC//Qn1lGBz+ZzdGtoq2qNKL+l8UE+Q tKBJOUk8aB5G9As7EwfjkhgwV2397UZRgKd1s9f2re8nwHDkh9ZUJ+DSjAyKD+JH +mwuk8hay6jsVAKPhhERSJE=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 12 Aug 2011 02:22:49 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1585642230.7798.3844; Fri, 12 Aug 2011 02:22:45 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1677; t=1313129880; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=8k42sAA Bp5s0SJNdFVrrHB1ctNTemnUvJaC9jw2ezLo=; b=f9xaAiwKyMsX4jG/2bOZ03k XwxSGgVtfGPsxFNgvoIyUrqk8amyY6BFYxeFVJVdX2Gdm2cobN3bdtpGgZ4QDBnZ 5K+qEOuO77s+p53KDXPI+iICCf/iTOYFyhxmMJDIG9/EGSwaOHvbwk4ZhZSsvF5O DlcWot6Mj8ZVde9hcAgo=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 12 Aug 2011 02:18:00 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2556918533.764.6060; Fri, 12 Aug 2011 02:17:59 -0400
Message-ID: <4E44C6F0.8030703@isdg.net>
Date: Fri, 12 Aug 2011 02:23:44 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: subject_prefix on IETF Discuss?
References: <20110811142203.GA8143@gsp.org>	<201108111558.p7BFwx04000742@fs4113.wdf.sap.corp> <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>
In-Reply-To: <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 06:23:12 -0000

Barry Leiba wrote:

> So the question really goes to the mailman people: can we get an
> option to make the prefix inclusion a subscriber option?  Each list
> would have a default behaviour, but each user could change it (just as
> I now change every list's "suppress duplicates" option when I
> subscribe to it, which makes sure my folders contain complete
> threads).  That would make everyone happy.
> 
> As long as the option goes by mailing list, and everyone has to eat
> the preference of whoever sets up the list, we'll have endless and
> non-productive arguments (like this one) about it.

+1.

But its not all waste :)

For me, reading these "user support issues" is feed for product 
improvements to see where what new sysop vs user needs are considered. 
   The Subject prefix was one of them we looked to:

    - minimize the promotion of mail tampering ideas,
    - its less needed today with newer MUAS, and
    - we have new DKIM considerations.

It first appeared be a good and easy candidate for a new user option 
to override the list setting, but when the code change requirements 
were looked at, at least for our software (independent list server and 
smtp server), it was not a feasible feature to implement without 
multiple design methods to check out and significant code change 
simply because the list server creates a single 5322 payload for a 
smart host SMTP connection multi-RCPT distribution.

I guess for an SMTP server that has built-in list distribution and has 
access to the list membership database, it can do customize payload 
per member.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From sm@resistor.net  Thu Aug 11 23:48:27 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E0621F855D for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 23:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZV4OP9FnPXC for <ietf@ietfa.amsl.com>; Thu, 11 Aug 2011 23:48:25 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A92221F855A for <ietf@ietf.org>; Thu, 11 Aug 2011 23:48:24 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7C6ms6t020504 for <ietf@ietf.org>; Thu, 11 Aug 2011 23:48:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1313131739; bh=E21wMyEfqNaDRnXqji9q/Wbs/P247+/Iws+jRyhrKRQ=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=EtGkA41E9ApryrKoM5Lg+uhaA1c18dY1+f0zkPIM4/qOE4J7QsY4/JMPkUQCkDITW 7X0whK4HHqeaUuTz0Pm67Xj3sjqLJGgmDTEv9hGA+desTudEsrqmGLqVrst8lS/z9E 5AyZSD+Ur7xqZnQt28DtYCb+4/kK9lNW056nIwCc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1313131739; bh=E21wMyEfqNaDRnXqji9q/Wbs/P247+/Iws+jRyhrKRQ=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=Y2/QUdfT5Y7prhdnpHPBP87RpiukTCJe9LYKSnWIDpUZaTYtaM5KszFMMm33IRIaL OLnVzhzTG7ZdWTwor3KtfCgJCXRsQGndlf6Tc2QoP1XWOfrfPdGBGTq2gpjJgNz3tX NfDVgRbN6BqPJ2B2IZHNg1E0gTkQne0Wz9T+NavY=
Message-Id: <6.2.5.6.2.20110811225338.0a5d8588@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 11 Aug 2011 23:29:59 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
In-Reply-To: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 06:48:27 -0000

At 06:37 11-08-2011, The IESG wrote:
>The IESG has received a request from the Yet Another Mail WG (yam) to
>consider the following document:
>- 'Message Submission for Mail'
>   <draft-ietf-yam-rfc4409bis-02.txt> as a Full 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-08-25. Exceptionally, comments may be

Please note that RFC 4956, RFC 5321 and RFC 5322 are documented as 
downward references. The protocols that they describe are 
widely-deployed, interoperable, stable, and successful, so the 
references are justified based on RFC 4897.

Although the downward references have not been explicitly called out 
in the Last Call announcement, the editors mentioned that in Appendix 
B of draft-ietf-yam-rfc4409bis-02.

Regards,
-sm

P.S. RFC 5322 is not a downward reference given that it is listed 
under Informational References. 


From jyee@afilias.info  Fri Aug 12 08:41:09 2011
Return-Path: <jyee@afilias.info>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7BC521F8661 for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 08:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.142
X-Spam-Level: 
X-Spam-Status: No, score=-6.142 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nix-RgMrdHem for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 08:41:09 -0700 (PDT)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by ietfa.amsl.com (Postfix) with ESMTP id 2592021F85C4 for <ietf@ietf.org>; Fri, 12 Aug 2011 08:41:08 -0700 (PDT)
Received: from ms6.yyz2.afilias-ops.info ([10.50.129.112] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from <jyee@afilias.info>) id 1Qrtrl-0006TG-4t for ietf@ietf.org; Fri, 12 Aug 2011 15:41:45 +0000
Received: from mail-qy0-f178.google.com ([209.85.216.178]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from <jyee@afilias.info>) id 1Qrtrl-0005Vz-7V for ietf@ietf.org; Fri, 12 Aug 2011 15:41:45 +0000
Received: by qyk30 with SMTP id 30so1833126qyk.9 for <ietf@ietf.org>; Fri, 12 Aug 2011 08:41:44 -0700 (PDT)
Received: by 10.224.196.1 with SMTP id ee1mr762795qab.109.1313163703441; Fri, 12 Aug 2011 08:41:43 -0700 (PDT)
Received: from jyee-lt.tor.afilias-int.info (tor-gateway.afilias.info [199.15.87.4]) by mx.google.com with ESMTPS id b6sm2339232qcb.11.2011.08.12.08.41.39 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 12 Aug 2011 08:41:42 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joseph Yee <jyee@afilias.info>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF6E3@EXCH-C2.corp.cloudmark.com>
Date: Fri, 12 Aug 2011 11:41:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E901AEC5-5BE4-4427-A41A-C4912E261EAF@afilias.info>
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E44A5BE.3050008@att.com> <F5833273385BB34F99288B3648C4F06F13512DF6E3@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 15:41:09 -0000

On 2011-08-12, at 12:39 AM, Murray S. Kucherawy wrote:

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Tony Hansen
>> Sent: Thursday, August 11, 2011 9:02 PM
>> To: ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message =
Submission for Mail) to Full Standard
>>=20
>> I support publication of this RFC.
>=20
> +1, which is to say:
>=20
> - I've read it
> - I agree with what it says
> - I can't find any reason not to move it to Full Standard
> - Nice job all around
>=20
> -MSK

+1 here too, followed with details:

+ I read the latest revision
+ I agree with the content too, especially about converting character =
encoding (for EAI)
+ Nothing to against from the RFC
+ Support to move it to standard

Thanks
Joseph


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


From mrex@sap.com  Fri Aug 12 12:02:05 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29AFB21F8586 for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 12:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.512
X-Spam-Level: 
X-Spam-Status: No, score=-9.512 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_BACKHAIR_33=1, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nLvh5iLrAcmd for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 12:02:01 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 6041421F8562 for <ietf@ietf.org>; Fri, 12 Aug 2011 12:02:01 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p7CJ2bjQ027984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Fri, 12 Aug 2011 21:02:37 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108121902.p7CJ2abf001229@fs4113.wdf.sap.corp>
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission
To: ietf@ietf.org
Date: Fri, 12 Aug 2011 21:02:36 +0200 (MEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 19:02:05 -0000

On 8/11/2011 9:37 AM, The IESG wrote:
> The IESG has received a request from the Yet Another Mail WG (yam) to
> consider the following document:
> - 'Message Submission for Mail'
>    <draft-ietf-yam-rfc4409bis-02.txt>  as a Full 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-08-25. 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.

I'm wondering wheter there should be an informative reference to rfc6186.

and I am concerned about the security mess around SMTP-AUTH (rfc4954)
(for which this document is not responsible, but which it also
 does not mention).

Coincidentally, we were just talking about server endpoint identification
(typically performed by TLS clients and described in rfc6125) and
how SMTP-AUTH (rfc4954) does not really distinguish two very different
usage scenarios of SMTP-AUTH (MTA<->MTA) and (MUA->MTA) and how they're
actually (ab)used today on the internet.

 e.g. http://www.ietf.org/mail-archive/web/dane/current/msg03067.html

 additional comment to that Mail, the server certificate presented
 by that Google MX-host is from a private CA (not from one known
 to the TLS X.509 PKI), and @gmail.com is _not_ using DNSSEC.


While the typical TLS server certificate for MUA->MTA transfer might be
in a better shape than the totally devastating situation for MTA<->MTA,
server discovery through MX records for MTA<->MTA and server discovery
through SRV records for Email submission (MUA->MTA) suggested by rfc6186
will preclude authentication of the server.

I believe that the current pityful state of TLS server endpoint
identification and the lack of server endpoint identification
(precluded by the MX & SRV transformations) should at least be
documented in the Security Considerations section.


-Martin


From ned+ietf@mauve.mrochek.com  Fri Aug 12 19:07:46 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE9EE11E80A8 for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 19:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2UuRRtx7H45K for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 19:07:46 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 79A9411E8096 for <ietf@ietf.org>; Fri, 12 Aug 2011 19:07:37 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4RUV52NCW013QUK@mauve.mrochek.com> for ietf@ietf.org; Fri, 12 Aug 2011 19:07:14 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 12 Aug 2011 19:07:11 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4RUV3VYA400VHKR@mauve.mrochek.com>
Date: Fri, 12 Aug 2011 19:07:04 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
In-reply-to: "Your message dated Fri, 12 Aug 2011 00:02:06 -0400" <4E44A5BE.3050008@att.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E44A5BE.3050008@att.com>
To: Tony Hansen <tony@att.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1313201138; i=@mrochek.com; bh=0/JelKCR1Q/8ayY/rQShVdXnVNpHpJQm3zCSM9pJumY=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=VqhTgQEyfyjyz2/f3UY+EpECd6Uol/NC1CKlCLJycwaWPOy63j1PNBfVAQRn4Wrqa kSLNe1mVoybEUs2HcvcPQjl+A0ggs1R8uOlfqn+gdUTSIME5aZdelnLuixBHbOE188 v8Jf4wHMd7dq6UForzfo2rqLu8JnWoo76IuXDqFM=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 02:07:46 -0000

> I support publication of this RFC.

+1

				Ned

>      Tony Hansen
>      tony@att.com

> On 8/11/2011 9:37 AM, The IESG wrote:
> > The IESG has received a request from the Yet Another Mail WG (yam) to
> > consider the following document:
> > - 'Message Submission for Mail'
> >    <draft-ietf-yam-rfc4409bis-02.txt>  as a Full 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-08-25. 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.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From ned+ietf@mauve.mrochek.com  Fri Aug 12 19:34:30 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B6D21F86BE for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 19:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NlvLGXiPe-yx for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 19:34:30 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 051C321F86BB for <ietf@ietf.org>; Fri, 12 Aug 2011 19:34:30 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4RVSH7EDC00USSK@mauve.mrochek.com> for ietf@ietf.org; Fri, 12 Aug 2011 19:34:07 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 12 Aug 2011 19:34:04 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4RVSFXGI800VHKR@mauve.mrochek.com>
Date: Fri, 12 Aug 2011 19:24:40 -0700 (PDT)
Subject: Re: subject_prefix on IETF Discuss?
In-reply-to: "Your message dated Thu, 11 Aug 2011 12:26:04 -0400" <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1
References: <20110811142203.GA8143@gsp.org> <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp> <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1313202751; i=@mrochek.com; bh=z1fSElYk3hwZxeF76cc6h5HIf4+lZqzrukb6//5Kmmo=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=tO5b5XIh5vIa8lbrpEJgdFlMMNDVsj167ehWv1469LPHP5LwpR4VGcSO/9zjMDlJI 723wMENIWoBCw+fV+65ibUFzW28+4W55pJXIqteZ/jvrWQPN1kodeKrdZNp5bZJQmj vOBZJj8gj/qsZSxYhDrO+ZTjeMqE48wqPA3PRfaA=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 02:34:30 -0000

> So the question really goes to the mailman people: can we get an
> option to make the prefix inclusion a subscriber option?

I confess to being more than a little perplexed as to why you and others think
this idea in and of itself is a useful solution to anything.

The problem with putting tags into the subject field is fundamental: The
semantics just don't match. Subject field text is routinely reused in a variety
of ways - such reuse is in fact openly condoned and encouraged by our various
email standards. And this reuse breaks tags that are necessarily bound to the
context of the original message.

For example, suppose I elect to have lists add tags to the messages I receive.
That's all fine and dandy until I decide to reply to one of those messages.
Now the tag goes right back to the list and gets redistributed to the people
who do not want it.

This problem can be ameliorated somewhat by having the list actively strip it's
own tag from messages sent to recipients that have elected not to receive the
tag, but you're still left with the problems associated with replies to
messages sent to multiple lists.

> Each list
> would have a default behaviour, but each user could change it (just as
> I now change every list's "suppress duplicates" option when I
> subscribe to it, which makes sure my folders contain complete
> threads).  That would make everyone happy.

No it won't. See above. In fact by making the presence of the tag unpredictable
it may actually make things worse.

				Ned

From moore@network-heretics.com  Fri Aug 12 20:00:44 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A095311E8086 for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 20:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.433
X-Spam-Level: 
X-Spam-Status: No, score=-3.433 tagged_above=-999 required=5 tests=[AWL=0.165,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wpe-4phQbGf for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 20:00:44 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4CD11E807E for <ietf@ietf.org>; Fri, 12 Aug 2011 20:00:41 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 96CFD207E8; Fri, 12 Aug 2011 23:01:19 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 12 Aug 2011 23:01:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=LzW j5scgrzDNsRCU0QAIC22pK5g=; b=pdrx0mqD3HCQvtQUtnuw0DWPZa4L0hWfGVw RYrM2ZFixS85vJVwuoYLPolQhWUixNpzI4fwPQYpS8dclC0+/vepiapFoJrs8CW+ jaandAvK9G2NXgv2jEG8f7te3GFodanxBAqW7bWuHn8v/7PdmhcxA00zxEjw746t Z9Tn5Em8=
X-Sasl-enc: kcvZ3URqVzHbDj5Pvr1nL24ssUfDW/hUp0lpZwFhtDpD 1313204478
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 8668E415744; Fri, 12 Aug 2011 23:01:18 -0400 (EDT)
Subject: Re: subject_prefix on IETF Discuss?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-42--110171091
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <01O4RVSFXGI800VHKR@mauve.mrochek.com>
Date: Fri, 12 Aug 2011 23:01:17 -0400
Message-Id: <FEC8790F-3268-478B-9756-7698FBA2A71C@network-heretics.com>
References: <20110811142203.GA8143@gsp.org> <201108111558.p7BFwx04000742@fs4113.wdf.sap.corp> <CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com> <01O4RVSFXGI800VHKR@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1084)
Cc: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 03:00:44 -0000

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

On Aug 12, 2011, at 10:24 PM, ned+ietf@mauve.mrochek.com wrote:

>> So the question really goes to the mailman people: can we get an
>> option to make the prefix inclusion a subscriber option?
>=20
> I confess to being more than a little perplexed as to why you and =
others think
> this idea in and of itself is a useful solution to anything.


If having it be a per-subscriber option (off by default) would aid =
migration to a world where subject tags are not commonplace and =
therefore not widely expected, that might be worth it.  Maybe having =
them off by default will encourage more use of List-ID.

I agree that the problems you mention are real.  As long as the subject =
tag were an option, lists supporting it would still need to be able to =
strip subject tags from replies.  Replies to messages sent to multiple =
lists would still be messy.

Keith


--Apple-Mail-42--110171091
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><div>On Aug 12, 2011, at 10:24 PM, <a =
href=3D"mailto:ned+ietf@mauve.mrochek.com">ned+ietf@mauve.mrochek.com</a> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
"><div><blockquote type=3D"cite">So the question really goes to the =
mailman people: can we get an<br></blockquote><blockquote =
type=3D"cite">option to make the prefix inclusion a subscriber =
option?<br></blockquote><br>I confess to being more than a little =
perplexed as to why you and others think<br>this idea in and of itself =
is a useful solution to =
anything.</div></span></blockquote></div><div><br></div>If having it be =
a per-subscriber option (off by default) would aid migration to a world =
where subject tags are not commonplace and therefore not widely =
expected, that might be worth it. &nbsp;Maybe having them off by default =
will encourage more use of List-ID.<div><br></div><div>I agree that the =
problems you mention are real. &nbsp;As long as the subject tag were an =
option, lists supporting it would still need to be able to strip subject =
tags from replies. &nbsp;Replies to messages sent to multiple lists =
would still be =
messy.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-42--110171091--

From hsantos@isdg.net  Sat Aug 13 00:04:53 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCA321F86F6 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 00:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.291
X-Spam-Level: 
X-Spam-Status: No, score=-3.291 tagged_above=-999 required=5 tests=[AWL=-0.692, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vWmxBl5v0tS for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 00:04:52 -0700 (PDT)
Received: from winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 4F7B721F85DA for <ietf@ietf.org>; Sat, 13 Aug 2011 00:04:51 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2055; t=1313219120; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=MjdW2ARY17aPKclM/2V6YyY0wcU=; b=jQqzftmVqlcgTfX+gbFk isOCVXr2d369F8lwYrHaYARZyyg19Gs8YlwAd4rIXQu8CDP5UNkyq4rdw4gq0ms9 EeWtrYHxiuR4/kBrvV7CMX3G75EoKqV1PE+6w5gRibdgC7PMQYcPdeifgmdlYv61 b2iScG9SmniixiU/ul27UG0=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 13 Aug 2011 03:05:20 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1674577979.11766.4872; Sat, 13 Aug 2011 03:05:02 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2055; t=1313218818; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=oQjVvyV FCTLG/A+NAuKFrwKW+L3I71zzo6GFzMUEXYg=; b=n+kfVXr6H77ktwgyWDuFk3c x/f/47ef12UfeGE5eVwsTrUBw3Uev6DHXNkZ+BfR9Wimljh/VCRTI+B7lhPa8ISY Otu0JisC1gqz7AOCbHX1Fsiakei9qtZG8wP1TxYdalQUkvYeBoECruEXEYQiNfql ItgiP4+6Il7dyMvW5IfM=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 13 Aug 2011 03:00:18 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2645856268.908.2528; Sat, 13 Aug 2011 03:00:17 -0400
Message-ID: <4E462254.7090302@isdg.net>
Date: Sat, 13 Aug 2011 03:05:56 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: subject_prefix on IETF Discuss?
References: <20110811142203.GA8143@gsp.org>	<201108111558.p7BFwx04000742@fs4113.wdf.sap.corp>	<CAC4RtVAKSr97gjkNhWujQK+peAdVAsYDkhq2eQZQoLygu5KG2Q@mail.gmail.com>	<01O4RVSFXGI800VHKR@mauve.mrochek.com> <FEC8790F-3268-478B-9756-7698FBA2A71C@network-heretics.com>
In-Reply-To: <FEC8790F-3268-478B-9756-7698FBA2A71C@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 07:04:53 -0000

Keith Moore wrote:
> On Aug 12, 2011, at 10:24 PM, ned+ietf@mauve.mrochek.com wrote:
> 
>>> So the question really goes to the mailman people: can we get an
>>> option to make the prefix inclusion a subscriber option?
>> I confess to being more than a little perplexed as to why you and others think
>> this idea in and of itself is a useful solution to anything.
> 
> 
> If having it be a per-subscriber option (off by default) would aid migration to 
> a world where subject tags are not commonplace and therefore not widely expected, 
> that might be worth it.  Maybe having them off by default will encourage more 
> use of List-ID.

+1

One way to view this is to focus on the central issue and why/when the 
subject tag was useful:

        The need for Discussion Groups separations

But why did this occur?

Before Offline MUA became prevalent, online group ware conferencing 
provided the separation and it was the dominant user types.  Off hand, 
there were at least five different user types or access points:

   USER1: Online (console, web, gui) portals, folders separations 
available
   USER2: Offline w/ Online access to folders using non IETF method 
(i.e. Exchange)
   USER3: Offline w/ Online access to folders using IETF IMAP standard 
method
   USER4: Offline w/ Online access to folders using IETF NNTP standard 
method
   USER5: Offline using IETF POP3 Standard but with no inherent folder 
separations

So pre 2001 USER5 who may not have a MUA with support for RFC2919 
(List-ID) or flexibility to add new headers, needed a help using an 
undesirable mail tampering idea - subject list tags.

But today, RFC 2919 is widely adopted, MUA are more flexible and DKIM 
is also adding new pressures to avoid using this Subject List tag kludge.

So if the central issue is separation, we now have three IETF Methods 
for offline users to achieve this - IMAP, NNTP and LIST-ID sorting, 
and a new DKIM standard that this kludge conflicts with.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From nick@inex.ie  Sat Aug 13 02:59:12 2011
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B4B21F87C9 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 02:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bm3-uzgyLshh for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 02:59:11 -0700 (PDT)
Received: from prometheus.inex.ie (prometheus.inex.ie [IPv6:2001:7f8:18:2::148]) by ietfa.amsl.com (Postfix) with ESMTP id AE15E21F8565 for <ietf@ietf.org>; Sat, 13 Aug 2011 02:59:10 -0700 (PDT)
Received: from prometheus.inex.ie (localhost [127.0.0.1]) by prometheus.inex.ie (Postfix) with ESMTP id 9BCA92844C for <ietf@ietf.org>; Sat, 13 Aug 2011 10:59:48 +0100 (IST)
X-Virus-Scanned: amavisd-new at inex.ie
Received: from prometheus.inex.ie ([127.0.0.1]) by prometheus.inex.ie (prometheus.inex.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mQOZbANNvvsN for <ietf@ietf.org>; Sat, 13 Aug 2011 10:59:47 +0100 (IST)
Received: from crumpet.foobar.org (unknown [IPv6:2001:4d68:2002:100:913b:e469:5664:4465]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: operations) by prometheus.inex.ie (Postfix) with ESMTPSA id C065E28443 for <ietf@ietf.org>; Sat, 13 Aug 2011 10:59:45 +0100 (IST)
Message-ID: <4E464B0E.3000005@inex.ie>
Date: Sat, 13 Aug 2011 10:59:42 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Subject prefixes
X-Enigmail-Version: 1.2
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 09:59:12 -0000

Can I humbly suggest that we create a separate working group to discuss
whether there should be a subject_prefix for emails to ietf@ietf.org?

This is an important issue for many people, and it would be unfortunate -
nay, negligent - to make a decision on the matter without due discussion,
debate and documentation.

Nick

From hsantos@isdg.net  Sat Aug 13 03:55:35 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E8421F8AAF for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 03:55:35 -0700 (PDT)
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.675, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JU5-RlxCDkA4 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 03:55:34 -0700 (PDT)
Received: from pop3.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id EB82F21F8AAA for <ietf@ietf.org>; Sat, 13 Aug 2011 03:55:33 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=675; t=1313232970; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=iBMJkmNk1wPEjdK1Rh3Uc0fBxKM=; b=tLkI19r0LwMmnuCVaHNw 1T25vmuGRC25L2ineCoc7R6Z5aJBEEe/JRB9L3tMxvuic8MSIEfibzxSfpegohgL nI4OPR5s+9ONMc1dFbRyGjBaVy4RiOudv/gBZXeIksK2mXl90HVeIHprpUQ+BNzY kVk/7ehYiHtYgK4JEV5rKKc=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 13 Aug 2011 06:56:10 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1688398248.12039.1528; Sat, 13 Aug 2011 06:55:23 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=675; t=1313232636; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=ktFBOxT Yz0pnik9nA2jGtV+hdMCcMnOGJcjg5LSv0s8=; b=vDvJu1KFMFG7vQTSkXWm6aH mpl3E8Lgqn1hcSa5hjX4Z4jbroYvJkTzQt6RlAApzyazCRx3P3yCtFn7Y+kQF1Gm JZWNz+cWjRcD8F6eHLIM1xjyMxMFQHuIWvAev9d4grcAQWy0nMthYRphLRGcu5nu cMa2sHWVVYpBefPPCA1E=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 13 Aug 2011 06:50:35 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2659674221.920.3556; Sat, 13 Aug 2011 06:50:35 -0400
Message-ID: <4E465854.8090904@isdg.net>
Date: Sat, 13 Aug 2011 06:56:20 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
Subject: Re: Subject prefixes
References: <4E464B0E.3000005@inex.ie>
In-Reply-To: <4E464B0E.3000005@inex.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 10:55:35 -0000

+1 and it should be begin with a reflection of what was then and what 
is now.

Nick Hilliard wrote:
> Can I humbly suggest that we create a separate working group to discuss
> whether there should be a subject_prefix for emails to ietf@ietf.org?
> 
> This is an important issue for many people, and it would be unfortunate -
> nay, negligent - to make a decision on the matter without due discussion,
> debate and documentation.
> 
> Nick
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From vesely@tana.it  Sat Aug 13 08:42:04 2011
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E8121F84D6 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 08:42:04 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nr76VGTCNdDO for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 08:42:03 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 6773721F84D4 for <ietf@ietf.org>; Sat, 13 Aug 2011 08:42:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1313250161; bh=7b/D08WZZ/RpbXHqbxCsrp35yV/nUdVw81Er+G8aK7o=; l=1752; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=dBU1Cq2sB0hni8fES/91Sm0LSEA0WSiWq/jE1G3Rc6Vb1RShDBe2B0YY1EJsNDKDt 3Z8qmY8oin7a8w1ba71Oid61+MwxIAn5JbmjA/70BhpYteWheMPUPFR1kxXczkjvEA xte6/Z+JrpF0/NHbMW4cC6wJCKMEKpdBEsOnciOo=
Received: from [109.115.196.40] ([109.115.196.40]) (AUTH: PLAIN 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Sat, 13 Aug 2011 17:42:40 +0200 id 00000000005DC039.000000004E469B70.00004D35
Message-ID: <4E469B63.2070408@tana.it>
Date: Sat, 13 Aug 2011 17:42:27 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission
References: <201108121902.p7CJ2abf001229@fs4113.wdf.sap.corp>
In-Reply-To: <201108121902.p7CJ2abf001229@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 15:42:04 -0000

On 12.08.2011 21:02, Martin Rex wrote:
> On 8/11/2011 9:37 AM, The IESG wrote:
>> The IESG has received a request from the Yet Another Mail WG (yam) to
>> consider the following document:
>> - 'Message Submission for Mail'
>>    <draft-ietf-yam-rfc4409bis-02.txt>  as a Full 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-08-25. 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.
> 
> I'm wondering wheter there should be an informative reference to rfc6186.

This question was one of two points raised during WGLC by Derek Diget
http://www.ietf.org/mail-archive/web/yam/current/msg00615.html

It was decided that the current deployment of SRV doesn't quite justify
supporting it in a Full Standard document.

> and I am concerned about the security mess around SMTP-AUTH (rfc4954)
> (for which this document is not responsible, but which it also
>  does not mention).

This question was raised by Chris Newman on Fri, 30 Apr 2010.
http://www.ietf.org/mail-archive/web/yam/current/msg00420.html

There was a somewhat deeper discussion, but the conclusion was the same as
yours, namely that it's not the responsibility of 4409bis, and that

   it would be a serious mistake to clutter 4409bis up with some of the
   details that have been suggested.  Even at full standard, authentication
   details are best incorporated by reference to other documents than can be
   updated when or as necessary.
              http://www.ietf.org/mail-archive/web/yam/current/msg00434.html


hth

From ned+ietf@mauve.mrochek.com  Sat Aug 13 11:45:05 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0528321F86AA for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 11:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bPfzFLzNmHF for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 11:45:04 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABC121F8663 for <ietf@ietf.org>; Sat, 13 Aug 2011 11:45:04 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4STOTH9OG010444@mauve.mrochek.com> for ietf@ietf.org; Sat, 13 Aug 2011 11:44:41 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 13 Aug 2011 11:44:39 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4STOSKQ1600VHKR@mauve.mrochek.com>
Date: Sat, 13 Aug 2011 11:29:22 -0700 (PDT)
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt>	(Reducing the	Standards Track to Two Maturity Levels) to BCP
In-reply-to: "Your message dated Sun, 07 Aug 2011 12:45:18 -0400" <420C8B2470E5AAC8A12E5740@[192.168.1.128]>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]>
To: John C Klensin <john@jck.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1313260984; i=@mrochek.com; bh=HFtXbSg7SdH8XA2MyYar3woAbVjy0NChJIRggIkc0IA=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=nQadRl2vUZEilGh/vV80W2snv0O+Y+MCArhwo5sXLQQYdtcSZxn8rdfftoCuYcrAP 5h2V2HpIYlWZTMhJNKagmCW7wMoCbh4ChNU53+z8dv5vYy9rI4p020epW7FDyZeZgs 7+Wd+Q0nx+HZ2ENvskOHopDuVn6Q1JOr8AgOiOtc=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 18:45:05 -0000

> To add one observation to SM's comment and other observations
> that the scarcity of implementation reports implies that they
> are somehow difficult...

> --On Friday, August 05, 2011 02:45 -0700 SM <sm@resistor.net>
> wrote:
 
> > I presume that the IESG will only use the following criteria
> > for advancement:
> >
> >   - two independent interoperating implementations with
> > widespread
> >     deployment and successful operational experience
> >
> >   - no errata against the specification
> >
> >   - no unused features in the specification
> >
> > And there won't be any DISCUSSes along the lines of:
> >
> >    "I don't think the implementation reports are adequate for
> > me to meet the
> >     requirements of 2026. It does not clearly identify what
> > software was used or
> >     show support of each of the individual options and
> > features."
> >
> >    "Examples througout the document make use of non-example
> > domains."
> >
> >    "The implementation report is woefully inadequate to
> > document there are
> >     interoperable implementations of all the features from two
> > different code bases."
> >
> >    "My Discuss was not addressed at all - I believe that the
> > WG ignored the
> >     spirit of the implementation report requirement - my
> > Discuss said that
> >     we should know that there are multiple implementations
> > that have
> >     handled the significant changes in the recycling of this
> > Draft Standard.
> >     The group apparently refused to update its implementation
> > report"

> An alternate hypothesis about the low numbers of implementation
> reports on file is that people try them, get responses like the
> ones SM lists above, and react with "why bother -- this is a
> waste of time that I can better spend in other ways".  And that
> is the end, not just of the report being commented on, but any
> others that could have come from that author or participant.

That pretty much nails it. We've allowed exactly these sorts of vague and
nonspecific discusses to stand, with the result that the pain of getting to
draft or full standard is seen as far greater than the gain.

The really surprising thing, frankly, is that we have as many draft and full
standards as we do. 

> While it has not been raised as a specific argument for this
> two-maturity-levels proposal, getting rid of formal
> implementation reports might, for that reason, be useful in
> getting documents advanced.  However, it does not improve the
> case for two levels instead of three and won't help if IESG
> members express the same thoughts --not in terms of
> interoperability reports but in terms of lack of conviction the
> interoperability had actually been demonstrated in the case of
> that particular spec.

Actually it does in a way. Part of the problem with going to draft is that in
addition to it being painful and difficult, when it's over you're still not
done. And you have to wait for the final step, and when you get there it's not
all that well defined, either.

Really, this is Psych 101 stuff - it's been shown over and over that immediate
gratification wins out over long term satisfaction. Our three step process
sucks most if not all of the immediate gratification out of moving to draft.

And this is why I strongly support a move to a two step process. I think
the other changes that have been proposed are also important but I'll
take what I can get.

> I note that, when RFC 4846 and what became 5742 were under
> discussion, a then-IESG member pointed out to me that, despite
> the restrictions in those documents, if something in a draft
> really offended him, he could always find a way to state his
> objections in a way that would conform to the 4846/5742 rules.
> The same comment presumably applies to presumed proofs of
> independent interoperable implementations.

I really have to wonder if the entire yes/no-obj/discuss voting model is
appropriate for document advancement. For initial approval at proposed, sure,
having the ability to "discuss" the document makes all sorts of sense. But
for subsequent steps that virtue is a lot obvious, to me at least.

				Ned

From ned+ietf@mauve.mrochek.com  Sat Aug 13 11:47:08 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5E6821F85E3 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 11:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2mG6QF6QQyFn for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 11:47:08 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 401FA21F85F2 for <ietf@ietf.org>; Sat, 13 Aug 2011 11:47:08 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4STREVMOG011W49@mauve.mrochek.com> for ietf@ietf.org; Sat, 13 Aug 2011 11:46:47 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 13 Aug 2011 11:46:44 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4STRDJ1P400VHKR@mauve.mrochek.com>
Date: Sat, 13 Aug 2011 11:45:01 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission
In-reply-to: "Your message dated Sat, 13 Aug 2011 17:42:27 +0200" <4E469B63.2070408@tana.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <201108121902.p7CJ2abf001229@fs4113.wdf.sap.corp> <4E469B63.2070408@tana.it>
To: Alessandro Vesely <vesely@tana.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1313261109; i=@mrochek.com; bh=q0UsLs2ZJV2i71nLCLbj+TIDHYYmYi2selYkBjp4qQQ=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=CaI/U4iX+wKKIQUZCb5k06EUFAVcl/ObekeXR9m3IEdt2+eabGVnIo19veXHSfsyB lxThpLk0n8cWzrpcb/5GQ8h6prpBpcSf8oQW/MyAOR+ERtn6lPsHvp6qMntpENhrHi SX42DX3NJ/ERrN8LHIdhzawHHdnxcexMyGmlucrk=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 18:47:08 -0000

> On 12.08.2011 21:02, Martin Rex wrote:
> > On 8/11/2011 9:37 AM, The IESG wrote:
> >> The IESG has received a request from the Yet Another Mail WG (yam) to
> >> consider the following document:
> >> - 'Message Submission for Mail'
> >>    <draft-ietf-yam-rfc4409bis-02.txt>  as a Full 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-08-25. 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.
> >
> > I'm wondering wheter there should be an informative reference to rfc6186.

> This question was one of two points raised during WGLC by Derek Diget
> http://www.ietf.org/mail-archive/web/yam/current/msg00615.html

> It was decided that the current deployment of SRV doesn't quite justify
> supporting it in a Full Standard document.

I really wish it were otherwise, but I find myself having to agree with this
assessment. It would be a different thing if this was just now coming up for
approval at proposed, but we're way past that.

> > and I am concerned about the security mess around SMTP-AUTH (rfc4954)
> > (for which this document is not responsible, but which it also
> >  does not mention).

> This question was raised by Chris Newman on Fri, 30 Apr 2010.
> http://www.ietf.org/mail-archive/web/yam/current/msg00420.html

> There was a somewhat deeper discussion, but the conclusion was the same as
> yours, namely that it's not the responsibility of 4409bis, and that

>    it would be a serious mistake to clutter 4409bis up with some of the
>    details that have been suggested.  Even at full standard, authentication
>    details are best incorporated by reference to other documents than can be
>    updated when or as necessary.
>               http://www.ietf.org/mail-archive/web/yam/current/msg00434.html

+1

				Ned

From brian.e.carpenter@gmail.com  Sat Aug 13 13:32:37 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4863621F8556 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 13:32:37 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXbOoH4Bogtk for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 13:32:36 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 77AD521F850E for <ietf@ietf.org>; Sat, 13 Aug 2011 13:32:36 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3243443fxe.31 for <ietf@ietf.org>; Sat, 13 Aug 2011 13:33:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Up5517hgB6fFced1hRS55RtVsuyNcMpT9i5AwKoBMCU=; b=viqFa6YCWUHl8BEVZvD8Dt+JfQ3yO5Tg3zKblQnptE9HBL7Mcdwqsj/Vub7M5bHqKR LBlbrifboOVquTBnBvyn16+r1QHWgF/8ZHTzJwGJM/MsVAf7Mhi7Vu3AII3Zyrg8hyKE dBkWoYkMHSy67inNetWrPwZxMx8XpHn14RcI0=
Received: by 10.223.56.79 with SMTP id x15mr3118493fag.130.1313267596424; Sat, 13 Aug 2011 13:33:16 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id y21sm665503faj.23.2011.08.13.13.33.12 (version=SSLv3 cipher=OTHER); Sat, 13 Aug 2011 13:33:15 -0700 (PDT)
Message-ID: <4E46DF80.9000206@gmail.com>
Date: Sun, 14 Aug 2011 08:33:04 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com>
In-Reply-To: <01O4STOSKQ1600VHKR@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 20:32:37 -0000

On 2011-08-14 06:29, ned+ietf@mauve.mrochek.com wrote:
...
> I really have to wonder if the entire yes/no-obj/discuss voting model is
> appropriate for document advancement. For initial approval at proposed, sure,
> having the ability to "discuss" the document makes all sorts of sense. But
> for subsequent steps that virtue is a lot obvious, to me at least.

s/lot/lot less/

I pretty much agree, although one form of discuss might be
reasonable: "This document needs to be recycled at Proposed
Standard because of the following *observed* interoperability
problem:...".

In other words, once we have got this BCP out (soon, please),
the IESG should update the DISCUSS criteria specifically to
narrow them for the PS->IS transition.

    Brian

From john@jlc.net  Sat Aug 13 13:42:35 2011
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22EDB21F85A1 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 13:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.547
X-Spam-Level: 
X-Spam-Status: No, score=-106.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nYBA2wZlCjb9 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 13:42:34 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 9039421F856B for <ietf@ietf.org>; Sat, 13 Aug 2011 13:42:34 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id AD0F833C25; Sat, 13 Aug 2011 16:43:15 -0400 (EDT)
Date: Sat, 13 Aug 2011 16:43:15 -0400
From: John Leslie <john@jlc.net>
To: ned+ietf@mauve.mrochek.com
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt>	(Reducing the	Standards Track to Two Maturity Levels) to BCP
Message-ID: <20110813204315.GA53261@verdi>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01O4STOSKQ1600VHKR@mauve.mrochek.com>
User-Agent: Mutt/1.4.1i
Cc: John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 20:42:35 -0000

ned+ietf@mauve.mrochek.com <ned+ietf@mauve.mrochek.com> wrote:
> 
> I really have to wonder if the entire yes/no-obj/discuss voting model
> is appropriate for document advancement. For initial approval at
> proposed, sure, having the ability to "discuss" the document makes
> all sorts of sense. But for subsequent steps that virtue is a lot
> obvious, to me at least.

   This, IMHO, is the right question: Does yes/no-obj/discuss resolve
the right issues when advancing from PS to DS?

   There is a perception, at least, that any AD can block progress to
DS (though in fact the process is more complicated, that's the way it's
perceived).

   I could somewhat-seriously suggest that the IESG shouldn't have to
vote at all on advancement to DS -- the right issues are questions of
fact which could perfectly well be delegated.

   (And wearing my Narrative-Scribe hat, I know how confusing it is
for IESG members to figure out what's expected of them when the question
is advancement of maturity level.)

--
John Leslie <john@jlc.net>

From ned+ietf@mauve.mrochek.com  Sat Aug 13 15:04:43 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9140821F85F7 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 15:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RvR4HPQiAjVu for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 15:04:43 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id E6D4D21F85F2 for <ietf@ietf.org>; Sat, 13 Aug 2011 15:04:42 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4T0OAZ1ZK00XYRQ@mauve.mrochek.com> for ietf@ietf.org; Sat, 13 Aug 2011 15:04:19 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O4CJSMR6GG00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 13 Aug 2011 15:04:16 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O4T0O9ENDS00VHKR@mauve.mrochek.com>
Date: Sat, 13 Aug 2011 15:03:46 -0700 (PDT)
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
In-reply-to: "Your message dated Sun, 14 Aug 2011 08:33:04 +1200" <4E46DF80.9000206@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <4E46DF80.9000206@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1313272961; i=@mrochek.com; bh=vWqh3fO020ZRbwFp7Ws1rgIH9MnW2qOwkPM/dGGJyYk=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=CRMeWoHVuYVW7DOR2iw+9YYJsf0Sbv5UAz71OMZJsleHpOEC0lsU2b6FZNyA0ZC2Q k/CCOlGF76HSVLPxn8/dZVD3M2o0KN5LTbmk2aNYJSftLzQkIaHdaopodxjenkxxas Xmx2XxnIJ2bAyOrdj8pxSGencdxucmPjvGQuD6Yc=
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 22:04:43 -0000

> On 2011-08-14 06:29, ned+ietf@mauve.mrochek.com wrote:
> ...
> > I really have to wonder if the entire yes/no-obj/discuss voting model is
> > appropriate for document advancement. For initial approval at proposed, sure,
> > having the ability to "discuss" the document makes all sorts of sense. But
> > for subsequent steps that virtue is a lot obvious, to me at least.

> s/lot/lot less/

Yes, sorry.

> I pretty much agree, although one form of discuss might be
> reasonable: "This document needs to be recycled at Proposed
> Standard because of the following *observed* interoperability
> problem:...".

> In other words, once we have got this BCP out (soon, please),
> the IESG should update the DISCUSS criteria specifically to
> narrow them for the PS->IS transition.

+1

				Ned

From moore@network-heretics.com  Sat Aug 13 15:07:24 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC4C21F861E for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 15:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.435
X-Spam-Level: 
X-Spam-Status: No, score=-4.435 tagged_above=-999 required=5 tests=[AWL=1.164,  BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCyweFehS5eO for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 15:07:23 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 76CD821F862F for <ietf@ietf.org>; Sat, 13 Aug 2011 15:07:23 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1BF7121A42; Sat, 13 Aug 2011 18:08:04 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 13 Aug 2011 18:08:04 -0400
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=WV/4Uv/lkCs/NlKlrBpgqJ+LzEo=; b=B6 hM70sKcAaEn11Mt/Hp4I4THghzPnncjgFj79l0gQDYeui0Kr12kVAdUK82ju+yen 2pXdM4r3G3rnNshUPdwVOdKy4P/M2QzvVwaOkivtbJqNz7VDmL1/n0S5m87oDIXU DaKeHWB2iVYIlqnKMPj84aRxLK8FEIL4HKwYrGzo8=
X-Sasl-enc: LASPra4EZSaraDc44Frt3sLiIISiaLD757PGaysT3nJY 1313273283
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E8B2E41CFBE; Sat, 13 Aug 2011 18:08:02 -0400 (EDT)
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt>	(Reducing the	Standards Track to Two Maturity Levels) to BCP
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110813204315.GA53261@verdi>
Date: Sat, 13 Aug 2011 18:08:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1084)
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Aug 2011 22:07:24 -0000

On Aug 13, 2011, at 4:43 PM, John Leslie wrote:

> ned+ietf@mauve.mrochek.com <ned+ietf@mauve.mrochek.com> wrote:
>>=20
>> I really have to wonder if the entire yes/no-obj/discuss voting model
>> is appropriate for document advancement. For initial approval at
>> proposed, sure, having the ability to "discuss" the document makes
>> all sorts of sense. But for subsequent steps that virtue is a lot
>> obvious, to me at least.
>=20
>   This, IMHO, is the right question: Does yes/no-obj/discuss resolve
> the right issues when advancing from PS to DS?

IMO, IESG members ought to be able to vote "no" if, after first voting =
"discuss" and not having the issue resolved within a well-defined amount =
of time, they still believe that the document should not progress.  That =
goes for any standards level.

(That's not to say that a single "no" vote should suffice to block =
progress of a document.)

"Discuss" is not the problem.  "Discuss" is actually a really good idea. =
 The problem is the lack of a "no" vote, which causes people to =
interpret "discuss" as if it were "no". =20

If an IESG member sees something about a document that is suspect, it's =
entirely appropriate for him or her to raise questions about it.  That's =
their job.   And if the explanation is satisfactory, or the problem is =
fixed, it's then appropriate for the vote to be changed to "no =
objection" or "yes".   But if the problem isn't fixed, and the problem =
is substantial, the IESG member ought to be able to - IMO, has an =
obligation to - vote "no".  Anything else is dishonest and =
irresponsible.   The history of engineering is full of serious accidents =
that have been caused by technical reviews being ignored due to =
political pressure.=20

Anybody can make a mistake, including IESG members.  It's okay to make =
an occasional bad review.   It's not okay to lie about that review.

Now there's a quite valid question about what kinds of objections IESG =
should be able to raise at PS vs DS or whatever.   And it's arguable =
that the criteria for PS and DS (or IS) should be different.   In =
particular, a revision of a document for DS is not an invitation to =
change the protocol, or even to fix deficiencies in the original design =
of the protocol.  I don't even think that advancement to DS should be =
considered an invitation to rewrite the document.  That's not to say =
that standards-track RFCs should never be revised, but that revising =
them should be done very conservatively (so as to make as few changes as =
possible to the text and especially organization of the document)  and =
that this should be treated separately from advancement in grade.

Keith


From dhc@dcrocker.net  Sat Aug 13 17:59:06 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B22421F8797 for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 17:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level: 
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.427,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0NYzNs615Sf for <ietf@ietfa.amsl.com>; Sat, 13 Aug 2011 17:59:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 95DE221F8715 for <ietf@ietf.org>; Sat, 13 Aug 2011 17:59:05 -0700 (PDT)
Received: from com.flipdogsolutions (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7E0xbK2016295 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 13 Aug 2011 17:59:43 -0700
Date: Sat, 13 Aug 2011 17:59:53 -0700 (PDT)
From: Dave Crocker <dhc@dcrocker.net>
To: ned+ietf@mauve.mrochek.com, Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1090638024.1.1313283602619.JavaMail.javamailuser@localhost>
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_0_1090275816.1313283593656"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 13 Aug 2011 17:59:44 -0700 (PDT)
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 00:59:06 -0000

------=_Part_0_1090275816.1313283593656
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

+1


d/
--

   Dave Crocker
   bbiw.net

   via mobile

-----Original Message-----
> I pretty much agree, although one form of discuss might be
> reasonable: "This document needs to be recycled at Proposed
> Standard because of the following *observed* interoperability
> problem:...".

> In other words, once we have got this BCP out (soon, please),
> the IESG should update the DISCUSS criteria specifically to
> narrow them for the PS->IS transit

+1

------=_Part_0_1090275816.1313283593656
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<p>+1<br/><br/><font color='#888888'><br/>d/<br/>--<br/><br/>   Dave Crocker<br/>   bbiw.net<br/><br/>   via mobile</font><br/><br/>-----Original Message-----<br/>&gt; I pretty much agree, although one form of discuss might be<br/>&gt; reasonable: "This document needs to be recycled at Proposed<br/>&gt; Standard because of the following *observed* interoperability<br/>&gt; problem:...".<br/><br/>&gt; In other words, once we have got this BCP out (soon, please),<br/>&gt; the IESG should update the DISCUSS criteria specifically to<br/>&gt; narrow them for the PS-&gt;IS transit<br/><br/>+1<br/></p>

------=_Part_0_1090275816.1313283593656--

From jari.arkko@piuha.net  Sun Aug 14 02:48:41 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2C2121F85EE for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 02:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9griO8MWT2g for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 02:48:41 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id DF28D21F8559 for <ietf@ietf.org>; Sun, 14 Aug 2011 02:48:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 89EF22CE66; Sun, 14 Aug 2011 12:49:21 +0300 (EEST)
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 h-qy2Vx4E2FO; Sun, 14 Aug 2011 12:49:20 +0300 (EEST)
Received: from www.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4C6392CCD0; Sun, 14 Aug 2011 12:49:20 +0300 (EEST)
Received: from 196.37.107.250 (SquirrelMail authenticated user jarkko) by www.piuha.net with HTTP; Sun, 14 Aug 2011 12:49:20 +0300
Message-ID: <801f7eff29c39827b97da73eeb3c38cf.squirrel@www.piuha.net>
In-Reply-To: <4E46DF80.9000206@gmail.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <4E46DF80.9000206@gmail.com>
Date: Sun, 14 Aug 2011 12:49:20 +0300
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
From: jari.arkko@piuha.net
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 09:48:41 -0000

> I pretty much agree, although one form of discuss might be
> reasonable: "This document needs to be recycled at Proposed
> Standard because of the following *observed* interoperability
> problem:...".
>
> In other words, once we have got this BCP out (soon, please),
> the IESG should update the DISCUSS criteria specifically to
> narrow them for the PS->IS transition.

I also pretty much agree, and the IESG discuss criteria document
(http://www.ietf.org/iesg/statement/discuss-criteria.html) would certainly
benefit from a respin to provide guidelines for -bis documents and
documents advancing further.

However, as with most things I don't think there are hard and fast rules.
I can imagine a very old RFC being respin or advancing where I'd want some
rework. For instance, a vulnerability that was discovered after the
orginal RFC should be described, perhaps even dealt with somehow.

Jari



From moore@network-heretics.com  Sun Aug 14 04:33:26 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89D6421F889A for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 04:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.444
X-Spam-Level: 
X-Spam-Status: No, score=-3.444 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BaideofKzrnZ for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 04:33:25 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id ADA4D21F87C9 for <ietf@ietf.org>; Sun, 14 Aug 2011 04:33:25 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 97F87223DB; Sun, 14 Aug 2011 07:34:07 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 14 Aug 2011 07:34:07 -0400
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=6uQpXFlLtxFuxJ2n7FUvGERLqzc=; b=bi ucyCwwHy5Pxbb9PvkpHD1GiGDZWmrjcxy5aV8z2pv0fwThzffBeiUXXFvpIkPudp lClsRZeibaXpbEv1VXNB8uXIIuvOQPb1X/DgBMylKdIlAjQGI6M5K8LyJ8jDv8Am eyYZEO138Tr9d+FOks9uq219b26Y3oSskWTj/EGv4=
X-Sasl-enc: u7wVL9UYlBJ7vne/GnwysQDgjJn0ejo04svcVXZKBQEE 1313321646
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 4FA35406C5F; Sun, 14 Aug 2011 07:34:06 -0400 (EDT)
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3 (Normal)
In-Reply-To: <801f7eff29c39827b97da73eeb3c38cf.squirrel@www.piuha.net>
Date: Sun, 14 Aug 2011 07:34:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A57FD9B0-6935-4BF2-80EF-10DF5ECB60C0@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <4E46DF80.9000206@gmail.com> <801f7eff29c39827b97da73eeb3c38cf.squirrel@www.piuha.net>
To: jari.arkko@piuha.net
X-Mailer: Apple Mail (2.1084)
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 11:33:26 -0000

On Aug 14, 2011, at 5:49 AM, jari.arkko@piuha.net wrote:

>> I pretty much agree, although one form of discuss might be
>> reasonable: "This document needs to be recycled at Proposed
>> Standard because of the following *observed* interoperability
>> problem:...".
>>=20
>> In other words, once we have got this BCP out (soon, please),
>> the IESG should update the DISCUSS criteria specifically to
>> narrow them for the PS->IS transition.
>=20
> I also pretty much agree, and the IESG discuss criteria document
> (http://www.ietf.org/iesg/statement/discuss-criteria.html) would =
certainly
> benefit from a respin to provide guidelines for -bis documents and
> documents advancing further.
>=20
> However, as with most things I don't think there are hard and fast =
rules.
> I can imagine a very old RFC being respin or advancing where I'd want =
some
> rework. For instance, a vulnerability that was discovered after the
> orginal RFC should be described, perhaps even dealt with somehow.

I agree that such things need to be described, but I don't think this =
description should be gated on, or wait for, advancement in grade.  The =
errata mechanism can be used to report some kinds of vulnerabilities; =
separate RFCs for others.

Right now we have this expectation that we're going to rewrite the =
entire RFC just to declare something as DS.  That is a lot of work, =
opens up a huge can of worms, imposes a large barrier to the interop =
testing that we want to encourage, and sometimes introduces confusion by =
subtly changing the original specification.

Old standards do need maintenance.   Our process doesn't really account =
for that.   It has this fiction that once a protocol gets to Full =
Standard, it's good forever - or that it needs a complete and very =
tedious rewrite and recycle from Proposed.   =20
And the current process doesn't (in practice) document the shifting =
applicability of standards over time.  I'd like to see some sort of =
changes to the process that recognize the need to periodically review =
and occasionally maintain old standards, update their applicability =
without changing the text of the document, and that allows for =
incremental updating (with change bars etc.) without changing the basic =
form of the text.

Of course the changes do need to be reviewed, and IESG is already =
over-worked.  Maybe we need review groups that are analogous to working =
groups, and a separate supervisory board for reviews.   The review =
groups and board would be limited as to what they could do with a =
standard - e.g. clarify text where ambiguity had been identified, =
document new vulnerabilities (whether security, scaling, whatever), note =
limitations in applicability.   They'd have no power to add new =
features, or maybe only when the feature was narrowly tailored to fix a =
documented problem with the older spec.  This might even lighten IESG's =
load a bit because a few existing WGs could be changed to review groups. =
 And hopefully the review supervisory board's load would be lighter than =
IESG's so it wouldn't be so hard to recruit suitable candidates for it.

Keith


From jari.arkko@piuha.net  Sun Aug 14 06:24:00 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E3121F888A for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 06:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1N7CIcdOncgo for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 06:23:59 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE3821F87D6 for <ietf@ietf.org>; Sun, 14 Aug 2011 06:23:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2991E2CE66; Sun, 14 Aug 2011 16:24:31 +0300 (EEST)
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 wWznvB5xXCo7; Sun, 14 Aug 2011 16:24:30 +0300 (EEST)
Received: from www.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E77212CCD0; Sun, 14 Aug 2011 16:24:29 +0300 (EEST)
Received: from 196.37.107.250 (SquirrelMail authenticated user jarkko) by www.piuha.net with HTTP; Sun, 14 Aug 2011 16:24:30 +0300
Message-ID: <fc4c311f19fc06e011e69c180b2253f9.squirrel@www.piuha.net>
In-Reply-To: <A57FD9B0-6935-4BF2-80EF-10DF5ECB60C0@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <4E46DF80.9000206@gmail.com> <801f7eff29c39827b97da73eeb3c38cf.squirrel@www.piuha.net> <A57FD9B0-6935-4BF2-80EF-10DF5ECB60C0@network-heretics.com>
Date: Sun, 14 Aug 2011 16:24:30 +0300
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
From: jari.arkko@piuha.net
To: "Keith Moore" <moore@network-heretics.com>
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 13:24:00 -0000

Keith,

>> However, as with most things I don't think there are hard and fast
>> rules.
>
> I agree that such things need to be described, but I don't think this
> description should be gated on, or wait for, advancement in grade.  The
> errata mechanism can be used to report some kinds of vulnerabilities;
> separate RFCs for others.
>
> Right now we have this expectation that we're going to rewrite the entire
> RFC just to declare something as DS.

I do not think we currently have that expectation. I do realize that we've
debated several cases and the need or lack thereof for additional changes.
But in general, a document that advanced is not expected to be rewritten.
At least not in my opinion. When I review -bis or -ds documents I usually
focus on the rfcdiff output between the old RFC and the new draft.

I also do acknowledge that we (the working groups and the IESG) have made
several errors in this respect, sometimes doing more than should really
have been done. But I do not think we have the expectation that all -ds
documents should be rewritten. That would be wrong.

What I tried to say above is that I dislike hard rules such as:

- We should never require a -ds document to say additional things
- We should always apply the most recent IETF approved rules (such as BCP
109 on key management) to all documents, including the -ds ones

But I do agree with you that whether a separate new RFC, editing this RFC,
errata or some other form of update should be decided on a case-by-case
basis.

Jari



From moore@network-heretics.com  Sun Aug 14 06:37:15 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4122221F84FD for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 06:37:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.445
X-Spam-Level: 
X-Spam-Status: No, score=-3.445 tagged_above=-999 required=5 tests=[AWL=0.153,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYZWt5cMERU3 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 06:37:14 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 5A6D521F84FB for <ietf@ietf.org>; Sun, 14 Aug 2011 06:37:14 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 0DDF822342; Sun, 14 Aug 2011 09:37:57 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 14 Aug 2011 09:37:57 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=3u8 ggj0XpXMf4bKGlWEbXgDC6YI=; b=GqeBXjAxzQQ6XAYKUns7IsEV4L3N5omwryW cIM/OkeGkK4Vjb9PtHn+80iYrvmKQ3g9Usli7sROP/2zLnyW6kjICJygJc8x9jRx YFTv0eyH5h56vKxHlHF5cvm11h15M/UVfbQiiPdOV3OXHu1pEd8sfnIaeDZEL1h9 WyxwH7dM=
X-Sasl-enc: e6IGQHVTS6lGUoq1tUiKCkFmYOOckEi/6N2HqFPdxNH9 1313329076
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 5CD9741D387; Sun, 14 Aug 2011 09:37:55 -0400 (EDT)
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-43-14425548
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3 (Normal)
In-Reply-To: <fc4c311f19fc06e011e69c180b2253f9.squirrel@www.piuha.net>
Date: Sun, 14 Aug 2011 09:37:54 -0400
Message-Id: <4A069185-AD61-4D42-A030-D8C32F745EC8@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <4E46DF80.9000206@gmail.com> <801f7eff29c39827b97da73eeb3c38cf.squirrel@www.piuha.net> <A57FD9B0-6935-4BF2-80EF-10DF5ECB60C0@network-heretics.com> <fc4c311f19fc06e011e69c180b2253f9.squirrel@www.piuha.net>
To: jari.arkko@piuha.net
X-Mailer: Apple Mail (2.1084)
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 13:37:15 -0000

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

On Aug 14, 2011, at 9:24 AM, jari.arkko@piuha.net wrote:

> What I tried to say above is that I dislike hard rules such as:
>=20
> - We should never require a -ds document to say additional things
> - We should always apply the most recent IETF approved rules (such as =
BCP
> 109 on key management) to all documents, including the -ds ones

I'm not sure that I agree with that.  I think that when we have an old =
standard that's widely used, it's important to document newly discovered =
limitations.  But sometimes we live with the deficiencies, and sometimes =
we do what we can to fix the protocol without breaking compatibility.   =
We shouldn't necessarily insist that everything meet current criteria.

More generally, I don't think that advancing standards to DS should =
invite special scrutiny along those lines.  I think we should regularly =
apply such scrutiny to all IETF standards, regardless of their status.   =
 If the standard no longer meets our current criteria for =
standardization, we should say so.  But that doesn't necessarily mean we =
should reclassify it as Historic or otherwise take away its status.   If =
people are still using the protocol, we can be of more service by =
maintaining the specification than by abandoning it.   We should =
enumerate the known problems, identify the known fixes or workarounds, =
identify opportunities for new fixes that haven't been developed yet.  =20=


> But I do agree with you that whether a separate new RFC, editing this =
RFC,
> errata or some other form of update should be decided on a =
case-by-case
> basis.

I agree with that as you've stated it.  But I think there should be a =
presumption that writing a new RFC is done only in extreme cases, and =
that when this is done, the document has to recycle at Proposed.   And =
I'm okay in principle with editing existing RFCs and reissuing them with =
a new number, but I wish the new ones would have change bars.  (and =
maybe, when rendered in HTML, other indications of specifically which =
text is changed).

Keith


--Apple-Mail-43-14425548
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><div>On Aug 14, 2011, at 9:24 AM, <a =
href=3D"mailto:jari.arkko@piuha.net">jari.arkko@piuha.net</a> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">What I tried =
to say above is that I dislike hard rules such as:<br><br>- We should =
never require a -ds document to say additional things<br>- We should =
always apply the most recent IETF approved rules (such as BCP<br>109 on =
key management) to all documents, including the -ds =
ones<br></span></blockquote><div><br></div>I'm not sure that I agree =
with that. &nbsp;I think that when we have an old standard that's widely =
used, it's important to document newly discovered limitations. &nbsp;But =
sometimes we live with the deficiencies, and sometimes we do what we can =
to fix the protocol without breaking compatibility. &nbsp; We shouldn't =
necessarily insist that everything meet current =
criteria.</div><div><br></div><div>More generally, I don't think that =
advancing standards to DS should invite special scrutiny along those =
lines. &nbsp;I think we should regularly apply such scrutiny to all IETF =
standards, regardless of their status. &nbsp; &nbsp;If the standard no =
longer meets our current criteria for standardization, we should say so. =
&nbsp;But that doesn't necessarily mean we should reclassify it as =
Historic or otherwise take away its status. &nbsp; If people are still =
using the protocol, we can be of more service by maintaining the =
specification than by abandoning it. &nbsp; We should enumerate the =
known problems, identify the known fixes or workarounds, identify =
opportunities for new fixes that haven't been developed yet. =
&nbsp;&nbsp;</div><div><br></div><div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">But I do =
agree with you that whether a separate new RFC, editing this =
RFC,<br>errata or some other form of update should be decided on a =
case-by-case<br>basis.</span></blockquote></div><br><div>I agree with =
that as you've stated it. &nbsp;But I think there should be a =
presumption that writing a new RFC is done only in extreme cases, and =
that when this is done, the document has to recycle at Proposed. &nbsp; =
And I'm okay in principle with editing existing RFCs and reissuing them =
with a new number, but I wish the new ones would have change bars. =
&nbsp;(and maybe, when rendered in HTML, other indications of =
specifically which text is =
changed).</div><div><br></div><div>Keith</div><div><br></div></body></html=
>=

--Apple-Mail-43-14425548--

From hsantos@isdg.net  Sun Aug 14 08:18:01 2011
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6747B21F8A64 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 08:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level: 
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[AWL=-1.119, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VjOuEGUUGVc9 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 08:18:00 -0700 (PDT)
Received: from catinthebox.net (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 49C9421F854E for <ietf@ietf.org>; Sun, 14 Aug 2011 08:17:59 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2612; t=1313335120; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=61WGSkDH9YbaYS4SgbGq+h1w5WQ=; b=Z8qtU2TANXI0BZr1Mf5/ L4iBsR3FtZsZOa283pDb9RsaMUe74lS/wIBPdq1x3AAJkUCVhZ4G9qiKTu7inUjD TyZhoglaWIDRxLYAWGRq1Wj2BhQOzlKnmkP1cmwrjDnNqgl3LE5BEw4pvpMaHgfE lc3CeQz5vn3VPcSKcQ+aXgA=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 14 Aug 2011 11:18:40 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1790574223.14034.5084; Sun, 14 Aug 2011 11:18:20 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2612; t=1313334813; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=KnHqhLs nWdOJ3CpJwa7vKhpT/4jV0P+CFTTrbuivh4A=; b=VKiamKFVdA0LXR0V0uOC48s EFHf+UNzGE5Kf5quPBilYU2m4Ucn06Po+3nHD4EOMNeFGBC2s41vcWpfei2sAtHj PihZuPoiIPlhZpArI1uM0RBXwO2t/5clTWjIeBq0QE6KUhNIsSiLSGiQcyTttg25 NeylQFu+YL7ngk1ReLrs=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 14 Aug 2011 11:13:33 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2761851112.1028.5004; Sun, 14 Aug 2011 11:13:32 -0400
Message-ID: <4E47E76D.7060408@isdg.net>
Date: Sun, 14 Aug 2011 11:19:09 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: jari.arkko@piuha.net
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com> <4E46DF80.9000206@gmail.com>	<801f7eff29c39827b97da73eeb3c38cf.squirrel@www.piuha.net>	<A57FD9B0-6935-4BF2-80EF-10DF5ECB60C0@network-heretics.com> <fc4c311f19fc06e011e69c180b2253f9.squirrel@www.piuha.net>
In-Reply-To: <fc4c311f19fc06e011e69c180b2253f9.squirrel@www.piuha.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 15:18:01 -0000

jari.arkko@piuha.net wrote:
> Keith,
> 
>>> However, as with most things I don't think there are hard and fast
>>> rules.
>> I agree that such things need to be described, but I don't think this
>> description should be gated on, or wait for, advancement in grade.  The
>> errata mechanism can be used to report some kinds of vulnerabilities;
>> separate RFCs for others.
>>
>> Right now we have this expectation that we're going to rewrite the entire
>> RFC just to declare something as DS.
> 
> I do not think we currently have that expectation. I do realize that we've
> debated several cases and the need or lack thereof for additional changes.
> But in general, a document that advanced is not expected to be rewritten.
> At least not in my opinion. When I review -bis or -ds documents I usually
> focus on the rfcdiff output between the old RFC and the new draft.
> 
> I also do acknowledge that we (the working groups and the IESG) have made
> several errors in this respect, sometimes doing more than should really
> have been done. But I do not think we have the expectation that all -ds
> documents should be rewritten. That would be wrong.

It is good to read this is recognized, especially for people who wish 
to remain on the sideline as online participants and depend on 
engineering common sense an faith among their peers and the IETF/IESG 
leaders and really don't have the time to be getting involved deeply 
in the IETF process.

I don't think anything is cut and dry, but I will note an increasing 
concern that in the name of fast tracking, politics and "who you 
know," there have been a perception of "rubber stamping" BIS work. 
Overall, not necessarily a bad thing, but serious care should be taken 
when existing base of protocol users are now asked to change again. 
When done at the expense of ignoring input as watered down concerns 
using "rough" consensus to exclude what is otherwise a less than 50%, 
but nonetheless significant weight of people, then the real losers is 
the IETF process and the IETF future. [I personally believe, the Rough 
Consensus model needs a serious review on how its applied today.]

I personally can recognize the need to move documents faster, but if 
only to serve as a reminder, it should not come at the expense of the 
long held guidelines the IETF/IESG has followed to make sure "errors" 
  are not made.  If anything, the two-maturity level proposal should 
increase the engineering expertise and scrutiny requirements for 
reviewers.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com





From housley@vigilsec.com  Sun Aug 14 09:23:29 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3DE821F8AB0 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 09:23:29 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bomS3hFYUs7y for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 09:23:29 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id DF6AF21F8A7D for <ietf@ietf.org>; Sun, 14 Aug 2011 09:23:28 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id F1A97F24067 for <ietf@ietf.org>; Sun, 14 Aug 2011 12:24:14 -0400 (EDT)
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 jNzJ4QzG0L8U for <ietf@ietf.org>; Sun, 14 Aug 2011 12:24:10 -0400 (EDT)
Received: from [192.168.2.107] (pool-96-241-176-45.washdc.fios.verizon.net [96.241.176.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 07CF9F24027 for <ietf@ietf.org>; Sun, 14 Aug 2011 12:24:14 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-08.txt>	(Reducing the	Standards Track to Two Maturity Levels) to BCP
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>
Date: Sun, 14 Aug 2011 12:24:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 16:23:29 -0000

>>> I really have to wonder if the entire yes/no-obj/discuss voting =
model
>>> is appropriate for document advancement. For initial approval at
>>> proposed, sure, having the ability to "discuss" the document makes
>>> all sorts of sense. But for subsequent steps that virtue is a lot
>>> obvious, to me at least.
>>=20
>>  This, IMHO, is the right question: Does yes/no-obj/discuss resolve
>> the right issues when advancing from PS to DS?
>=20
> IMO, IESG members ought to be able to vote "no" if, after first voting =
"discuss" and not having the issue resolved within a well-defined amount =
of time, they still believe that the document should not progress.  That =
goes for any standards level.
>=20
> (That's not to say that a single "no" vote should suffice to block =
progress of a document.)
>=20
> "Discuss" is not the problem.  "Discuss" is actually a really good =
idea.  The problem is the lack of a "no" vote, which causes people to =
interpret "discuss" as if it were "no". =20

We are a bit off topic here, at least for this subject line.

The IESG did make some changes to the voting procedures a couple of =
years ago.  The change was to make it clear that a single DISCUSS =
position could not block a document.  That is, the IESG believes in =
rough consensus too.  The current rules are available here:

   http://www.ietf.org/iesg/voting-procedures.html

Now, please return to the Last Call discussion of =
draft-housley-two-maturity-levels on this subject line.  If we want to =
discuss the IESG ballot process further, please start a new thread.

Russ=

From moore@network-heretics.com  Sun Aug 14 09:28:39 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7570621F8A91 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 09:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.446
X-Spam-Level: 
X-Spam-Status: No, score=-3.446 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cpuRRmhiyZL5 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 09:28:38 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id B214D21F8A7D for <ietf@ietf.org>; Sun, 14 Aug 2011 09:28:38 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id C7B2B22202; Sun, 14 Aug 2011 12:29:21 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 14 Aug 2011 12:29:21 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=SBK f7mt/uiSJqeq68JpF+EdbbCw=; b=NgSQDmfcMNKqDknLGxlvrIrUzlZNYCzxe6/ Il0YqGopsl0RWknHH5pkKDH07d3pbfyBxzBzCdipg8yWnvdhpcOyS74n0GkXLljW P3tpVjLc9mPfRhIJDzO2CoXwyVvncynvHwq9C00uyhiyqfvZvXSuJbBnL6oo4IVU QFlz5PeA=
X-Sasl-enc: a69DoI75ldqFgstwcFrR7Z/cirEIHLysVhma+GdQJ+Hb 1313339360
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9D1C741D4AE; Sun, 14 Aug 2011 12:29:19 -0400 (EDT)
Subject: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-44-24708886
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>
Date: Sun, 14 Aug 2011 12:29:17 -0400
Message-Id: <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 16:28:39 -0000

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

On Aug 14, 2011, at 12:24 PM, Russ Housley wrote:

> The IESG did make some changes to the voting procedures a couple of =
years ago.  The change was to make it clear that a single DISCUSS =
position could not block a document.  That is, the IESG believes in =
rough consensus too.  The current rules are available here:
>=20
>   http://www.ietf.org/iesg/voting-procedures.html

Yes, I had read those procedures recently.   It's those very procedures =
that I have a problem with.

In particular this part is particularly heinous:

If an AD cannot get cooperation from the WG and cannot enter a ballot =
position that supports sending the document forward, then the AD should =
switch to "abstain."

That's completely inappropriate.   A document reviewer should never be =
expected to pretend like he doesn't have a problem with a document.   To =
expect an AD to change his vote to "abstain" is asking him to be =
dishonest and/or shirk responsibility.=20

Keith


--Apple-Mail-44-24708886
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><div>On Aug 14, 2011, at 12:24 PM, Russ Housley =
wrote:</div><br><blockquote type=3D"cite"><div>The IESG did make some =
changes to the voting procedures a couple of years ago. &nbsp;The change =
was to make it clear that a single DISCUSS position could not block a =
document. &nbsp;That is, the IESG believes in rough consensus too. =
&nbsp;The current rules are available here:<br><br> &nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/iesg/voting-procedures.html">http://www.ietf.o=
rg/iesg/voting-procedures.html</a><br></div></blockquote><div><br></div>Ye=
s, I had read those procedures recently. &nbsp; It's those very =
procedures that I have a problem with.</div><div><br></div><div>In =
particular this part is particularly =
heinous:</div><div><br></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: Verdana, Arial, Helvetica, sans-serif; font-size: =
13px; background-color: rgb(255, 255, 255); ">If an AD cannot get =
cooperation from the WG&nbsp;</span><span class=3D"Apple-style-span" =
style=3D"font-family: Verdana, Arial, Helvetica, sans-serif; font-size: =
13px; background-color: rgb(255, 255, 255); ">and cannot enter a ballot =
position that supports sending the document forward, then the AD should =
switch to "abstain."</span></div><div><br></div><div>That's completely =
inappropriate. &nbsp; A document reviewer should never be expected to =
pretend like he doesn't have a problem with a document. &nbsp; To expect =
an AD to change his vote to "abstain" is asking him to be dishonest =
and/or shirk =
responsibility.&nbsp;</div><div><br></div><div>Keith</div><div><br></div><=
/body></html>=

--Apple-Mail-44-24708886--

From brian.e.carpenter@gmail.com  Sun Aug 14 14:09:02 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52A0C21F84E1 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGOCLFsTcfqg for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:09:01 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id CC0D421F8451 for <ietf@ietf.org>; Sun, 14 Aug 2011 14:09:01 -0700 (PDT)
Received: by pzk33 with SMTP id 33so3842127pzk.18 for <ietf@ietf.org>; Sun, 14 Aug 2011 14:09:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PhbCxzhlbBuOjvx9yxMIwBgbq9NwngGFDtik/g4uEKs=; b=WAzObQY4/RyO9ipRCer03e6N4KDdQmeYMjnkVBzMx4r4vYlfAY/aTfOBXf/SksqzW3 H8tl6F5n37xb3GxqvWDlI+qV86f3Ki8U6nJrDYrjRBUr+6a1cmn9V55rn3BOgpHoO23N jMWR3hh/Gwf4qUt3OBu1GcmJ72UbM8AQGNQBw=
Received: by 10.142.231.20 with SMTP id d20mr1523185wfh.315.1313356180456; Sun, 14 Aug 2011 14:09:40 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id l10sm2734423pbl.30.2011.08.14.14.09.37 (version=SSLv3 cipher=OTHER); Sun, 14 Aug 2011 14:09:39 -0700 (PDT)
Message-ID: <4E483990.6030905@gmail.com>
Date: Mon, 15 Aug 2011 09:09:36 +1200
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: Keith Moore <moore@network-heretics.com>
Subject: Re: IESG voting procedures
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi>	<B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>	<E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com>
In-Reply-To: <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 21:09:02 -0000

Regards
   Brian Carpenter




On 2011-08-15 04:29, Keith Moore wrote:
> On Aug 14, 2011, at 12:24 PM, Russ Housley wrote:
> 
>> The IESG did make some changes to the voting procedures a couple of years ago.  The change was to make it clear that a single DISCUSS position could not block a document.  That is, the IESG believes in rough consensus too.  The current rules are available here:
>>
>>   http://www.ietf.org/iesg/voting-procedures.html
> 
> Yes, I had read those procedures recently.   It's those very procedures that I have a problem with.
> 
> In particular this part is particularly heinous:
> 
> If an AD cannot get cooperation from the WG and cannot enter a ballot position that supports sending the document forward, then the AD should switch to "abstain."
> 
> That's completely inappropriate.   A document reviewer should never be expected to pretend like he doesn't have a problem with a document.   To expect an AD to change his vote to "abstain" is asking him to be dishonest and/or shirk responsibility. 

iirc the IESG used to call this kind of abstention "holding
one's nose", but it can't be distinguished in the ballot from
an abstention "for cause" (conflict of interest). In theory,
you can find out which applies from the history in the tracker
or from the IESG minutes.

The point is to avoid blocking a document that the WG has
consciously chosen to support, and that has no concrete,
actionable defects, just because one or two ADs simply dislike
it.

    Brian

From adrian@olddog.co.uk  Sun Aug 14 14:41:32 2011
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B10121F8754 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3apz+ysPRFhj for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:41:31 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 8025921F874F for <ietf@ietf.org>; Sun, 14 Aug 2011 14:41:31 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id p7ELaIF5002827;  Sun, 14 Aug 2011 22:36:18 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id p7ELaGpv002812 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 14 Aug 2011 22:36:17 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'Keith Moore'" <moore@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi>	<B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>	<E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>	<951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com>
In-Reply-To: <4E483990.6030905@gmail.com>
Subject: RE: IESG voting procedures
Date: Sun, 14 Aug 2011 22:42:01 +0100
Message-ID: <005c01cc5acb$05058310$0f108930$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKi/mMT2wl1auhunjRRkJCg6nQviQKQSErCAi5n1WoCSBDGcgMzx/JHATFVDlQCHimVSAHZmMvKAd+lH3kBMpB1xwISpwlSkstUORA=
Content-Language: en-gb
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 21:41:32 -0000

Both...

> > If an AD cannot get cooperation from the WG and cannot enter a ballot
position
> that supports sending the document forward, then the AD should switch to
> "abstain." 
> >
> > That's completely inappropriate.   A document reviewer should never be
> expected to pretend like he doesn't have a problem with a document.   To
expect
> an AD to change his vote to "abstain" is asking him to be dishonest and/or
shirk
> responsibility.
> 
> iirc the IESG used to call this kind of abstention "holding
> one's nose", but it can't be distinguished in the ballot from
> an abstention "for cause" (conflict of interest). In theory,
> you can find out which applies from the history in the tracker
> or from the IESG minutes.

You can tell the difference because one is a "recuse" and the other is an
"abstain"

AFAIK the process that Keith calls out has never needed to be executed. It
exists to handle deadlock which might otherwise have to wait until the make-up
to the IESG changed or until NomCom was woken from its peaceful slumber. ADs are
not universal policemen and serve the will of the community. When an AD is
clearly in the rough against the consensus of the IESG they should not have the
power to individually block the progress of work for which there is clear IETF
consensus.

Note that when an AD does abstain he usually writes a strong comment in the
datatracker explaining why he is abstaining.

Adrian


From moore@network-heretics.com  Sun Aug 14 14:42:19 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F25CA21F84CC for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.447
X-Spam-Level: 
X-Spam-Status: No, score=-3.447 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bD-af3h+JefQ for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:42:18 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id F40B921F84CA for <ietf@ietf.org>; Sun, 14 Aug 2011 14:42:17 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id AC93D20CE6; Sun, 14 Aug 2011 17:43:01 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 14 Aug 2011 17:43:01 -0400
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=q3ccm1BlCXhhmVRgdlF+uRaqp0E=; b=pO nIM30bk2bTcPyrwmBtUxiaqVswAY37ZZ9YYLADSS2vxj5hjbb8vCyTe9lxwghr0i IFrNkvXjCbFgoWPx8ofg7a1AyicmybXPR3wd+EQxL+ALJOmEdGnFCnDDR3DSlZyl 0p0SJXBy0vSWvdixpzYhkw79bmsZE3SuVV927ms9U=
X-Sasl-enc: TIe3bh/l3Lss6G9eOvcWIjH23BuP02DUpEBHEsQpIKVE 1313358181
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9B54B41D67B; Sun, 14 Aug 2011 17:43:00 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E483990.6030905@gmail.com>
Date: Sun, 14 Aug 2011 17:42:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AB3CC64-D8AE-4775-969A-CE6A25261C26@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi>	<B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>	<E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 21:42:19 -0000

On Aug 14, 2011, at 5:09 PM, Brian E Carpenter wrote:

>>   A document reviewer should never be expected to pretend like he =
doesn't have a problem with a document.   To expect an AD to change his =
vote to "abstain" is asking him to be dishonest and/or shirk =
responsibility.=20
>=20
> iirc the IESG used to call this kind of abstention "holding
> one's nose", but it can't be distinguished in the ballot from
> an abstention "for cause" (conflict of interest). In theory,
> you can find out which applies from the history in the tracker
> or from the IESG minutes.

To be fair, the current procedures do allow for a "recuse" vote, which =
handles the "conflict of interest" case.

> The point is to avoid blocking a document that the WG has
> consciously chosen to support, and that has no concrete,
> actionable defects, just because one or two ADs simply dislike
> it.

The problem with the current procedure is that sometimes a WG will be in =
denial about the existence of concrete, actionable defects, and other =
IESG members may not have the time to review the document thoroughly or =
be in a good position to do so.    Sometimes it's also the case that the =
WG is exercising poor judgment even if there aren't concrete defects, =
and sometimes there's no good and simple fix for the WG's output. =20

When this happens, it is often the case that the WG represents a narrow =
set of interests and doesn't see (or want to see) how its work creates =
problems for other legitimate interests.  Though it does happen in other =
situations.

(Admittedly, some of these cases could be considered failures of =
management - the WG should not have been allowed to make a significant =
investment into a document without there being some cross-area checking =
and other sanity checking involved.  One hopes, of course, that such =
failures are rare.   But the proper remedy to a management failure is =
NOT to approve a seriously flawed document.)

If an IESG member finds a substantial defect with a document, I don't =
think it's responsible for him to hold his nose.  I don't think it's =
responsible to expect him to label his vote "abstain".  The responsible =
thing to do is to take that defect report seriously, even when the WG =
disagrees with the IESG member's opinion (as will often be the case when =
there's no simple fix for the document/protocol, or when the simple fix =
conflicts with the WG's ambition for the protocol).

The current IESG voting process presumes that the WG's opinion should =
trump that of its reviewers in the IESG.   This makes the whole review =
process a sham, as IESG review is reduced to essentially a rubber stamp. =
 =20

When I was on IESG, a single Discuss could block a document.  I'm not =
saying that was a good thing overall, but even under those circumstances =
a stubborn WG would often get away with refusing to fix technical =
defects in its documents.   With the current procedure, it's hard to =
imagine what would convince such a WG to fix things.   The only =
remaining available remedy would seem to be an appeal to IAB.

Keith


From moore@network-heretics.com  Sun Aug 14 14:55:03 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E96821F86DD for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JheiQ2S7fbn9 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 14:55:02 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 947E221F86D0 for <ietf@ietf.org>; Sun, 14 Aug 2011 14:55:02 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 526B72247F; Sun, 14 Aug 2011 17:55:46 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 14 Aug 2011 17:55:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=V9/ xxqqglqeR3D2S7qanwF+QZvs=; b=DYecrvsvwLvGbvCqFM6iWNhduANfIyrRsiK j8riHX8iw16DlRF4M82pu1OUutgvEZdJYAyxV0hm6juRCDdQ3T6mIxisjLDauQhx i9r4o7Y1EIgTNw5BUZGNlZ+5jKhwCNdVQIZM6nTgwobe6vcnut45Z5Fu6rgbnCkz uBC3fULo=
X-Sasl-enc: wYuO9BlyL+42TqzOzi0MskxS/Aba2iAse48rPNaM04XT 1313358945
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E586841D6DB; Sun, 14 Aug 2011 17:55:44 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-45-44295300
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <005c01cc5acb$05058310$0f108930$@olddog.co.uk>
Date: Sun, 14 Aug 2011 17:55:44 -0400
Message-Id: <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi>	<B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>	<E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>	<951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk>
To: <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1084)
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 21:55:03 -0000

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

On Aug 14, 2011, at 5:42 PM, Adrian Farrel wrote:

> AFAIK the process that Keith calls out has never needed to be =
executed.

The process that I call out is any case where an IESG member is expected =
to vote abstain when he disagrees with the WG on the merits of a =
document or an appropriate fix.  Based on my own experience in IESG, I'd =
be very surprised if that never happened nowadays.

> Note that when an AD does abstain he usually writes a strong comment =
in the
> datatracker explaining why he is abstaining.

I suppose my objections can be distilled into these points:

1) it's misleading to label this as an "abstain" vote, no matter how =
it's defined in IESG procedures
2) such objections should be treated more seriously than required by the =
current process
3) anything written in the data tracker is essentially buried to the =
audience of the RFCs  (though RFC errata might work somewhat better)

I'm not saying that a single AD should be able to block a document =
indefinitely, but neither should it be presumed that the WG should =
inherently prevail in a conflict. =20

I actually think that the "rough consensus" model is not well suited for =
IESG, because IESG rarely has enough members with the kind of expertise =
needed to make that kind of judgment.   The number of IESG members who =
review a typical document and really understand its implications is =
probably around 3-4.    Most of those voting "no objection" have =
probably not read the document, at least not in depth.  So in a case =
where there's one sponsoring AD voting yes and one AD voting discuss, =
it's really close to one or two in favor against one opposed.  But the =
way IESG votes, distorts this and makes it look like many against one.=20=


Keith


--Apple-Mail-45-44295300
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><div>On Aug 14, 2011, at 5:42 PM, Adrian Farrel wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">AFAIK the =
process that Keith calls out has never needed to be executed. =
</span></blockquote><div><br></div>The process that I call out is any =
case where an IESG member is expected to vote abstain when he disagrees =
with the WG on the merits of a document or an appropriate fix. =
&nbsp;Based on my own experience in IESG, I'd be very surprised if that =
never happened nowadays.</div><div><br></div><div><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Note that =
when an AD does abstain he usually writes a strong comment in =
the<br>datatracker explaining why he is =
abstaining.<br></span></blockquote></div><br><div>I suppose my =
objections can be distilled into these =
points:</div><div><br></div><div>1) it's misleading to label this as an =
"abstain" vote, no matter how it's defined in IESG =
procedures</div><div>2) such objections should be treated more seriously =
than required by the current process</div><div>3) anything written in =
the data tracker is essentially buried to the audience of the RFCs =
&nbsp;(though RFC errata might work somewhat =
better)</div><div><br></div><div>I'm not saying that a single AD should =
be able to block a document indefinitely, but neither should it be =
presumed that the WG should inherently prevail in a conflict. =
&nbsp;</div><div><br></div><div>I actually think that the "rough =
consensus" model is not well suited for IESG, because IESG rarely has =
enough members with the kind of expertise needed to make that kind of =
judgment. &nbsp; The number of IESG members who review a typical =
document and really understand its implications is probably around 3-4. =
&nbsp; &nbsp;Most of those voting "no objection" have probably not read =
the document, at least not in depth. &nbsp;So in a case where there's =
one sponsoring AD voting yes and one AD voting discuss, it's really =
close to one or two in favor against one opposed. &nbsp;But the way IESG =
votes, distorts this and makes it look like many against =
one.&nbsp;</div><div><br></div><div>Keith</div><div><br></div></body></htm=
l>=

--Apple-Mail-45-44295300--

From mrossi@swin.edu.au  Sun Aug 14 16:39:05 2011
Return-Path: <mrossi@swin.edu.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E43E321F863E for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 16:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.782
X-Spam-Level: 
X-Spam-Status: No, score=-1.782 tagged_above=-999 required=5 tests=[AWL=0.113,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHHW5PG1zFlm for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 16:39:05 -0700 (PDT)
Received: from gpo2.cc.swin.edu.au (gpo2.cc.swin.edu.au [136.186.1.31]) by ietfa.amsl.com (Postfix) with ESMTP id 31C6D21F85FE for <ietf@ietf.org>; Sun, 14 Aug 2011 16:39:05 -0700 (PDT)
Received: from mrossi.caia.swin.edu.au (mrossi.caia.swin.edu.au [136.186.229.109]) by gpo2.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id p7ENdlCO005681 for <ietf@ietf.org>; Mon, 15 Aug 2011 09:39:48 +1000
Message-ID: <4E485CC3.3020802@swin.edu.au>
Date: Mon, 15 Aug 2011 09:39:47 +1000
From: Mattia Rossi <mrossi@swin.edu.au>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110707 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-idr-deprecate-as-sets-05.txt> (Deprecation of the use of BGP AS_SET, AS_CONFED_SET.) to Informational RFC
References: <20110811154722.11750.88395.idtracker@ietfa.amsl.com>
In-Reply-To: <20110811154722.11750.88395.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2011 23:39:06 -0000

On 12/08/2011 08:11, Randy Bush wrote:
 >> The IESG has received a request from the Inter-Domain Routing WG 
(idr) to
 >> consider the following document:
 >> - 'Deprecation of the use of BGP AS_SET, AS_CONFED_SET.'
 >>    <draft-ietf-idr-deprecate-as-sets-05.txt>  as an Informational RFC
 >
 > i have read and support this document.  AS-Sets are essentially unused,
 > the deprecation is needed for the sidr work, and their removal will make
 > many research and ops tools which run against bgp announcements easier.
 >

Writing and working with such research tools I can only support this 
document as well. In fact I'm usually ignoring AS-Sets, as their use is 
already extremely rare, and they just complicate the code.

Mat

From brian.e.carpenter@gmail.com  Sun Aug 14 17:04:08 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB9421F883A for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcYs0Ol0b7oK for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:04:08 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8FE21F86C7 for <ietf@ietf.org>; Sun, 14 Aug 2011 17:04:08 -0700 (PDT)
Received: by gwb20 with SMTP id 20so3377254gwb.31 for <ietf@ietf.org>; Sun, 14 Aug 2011 17:04:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=fu3Zyg70pcV3a8e/Ja9V+XPk2IKj206jVhJaljXfQqg=; b=MEkLR59XiT4bFp1MuyRotmxkGtAkfxcmvBR/VfQRk6zXKAVhR141Rg9p4mWpfhwGBE 7wBhGFr1p5aSCWvOMQbKkR5fV6/fufGgY1Aw1tqYw68dYVNLK5bKfDyW3Apa80iZiI4I dSbCv4pc92fF79c2B7jE3MEIq3XV70M4pVINY=
Received: by 10.151.92.12 with SMTP id u12mr4199809ybl.189.1313366692151; Sun, 14 Aug 2011 17:04:52 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id y26sm3343258ybh.16.2011.08.14.17.04.50 (version=SSLv3 cipher=OTHER); Sun, 14 Aug 2011 17:04:51 -0700 (PDT)
Message-ID: <4E48629F.2070105@gmail.com>
Date: Mon, 15 Aug 2011 12:04:47 +1200
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: Keith Moore <moore@network-heretics.com>
Subject: Re: IESG voting procedures
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi>	<B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>	<E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>	<951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com>
In-Reply-To: <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 00:04:09 -0000

1. I'm glad that the ballot now has an explicit 'recuse' option.
Sorry about that red herring in my previous message.

2. (Excuse front posting). You can call it 'abstain' or you can
call it 'no'. What it means is that the AD concerned has
objections to the document that *cannot* be fixed (anything that
can be fixed is a 'discuss'). And I think in that case, there is
no way that one or two ADs should be able to block something
because they don't like it, *unless* they can convince the rest
of the IESG that the document is harmful.

Regards
   Brian

On 2011-08-15 09:55, Keith Moore wrote:
> On Aug 14, 2011, at 5:42 PM, Adrian Farrel wrote:
> 
>> AFAIK the process that Keith calls out has never needed to be executed.
> 
> The process that I call out is any case where an IESG member is expected to vote abstain when he disagrees with the WG on the merits of a document or an appropriate fix.  Based on my own experience in IESG, I'd be very surprised if that never happened nowadays.
> 
>> Note that when an AD does abstain he usually writes a strong comment in the
>> datatracker explaining why he is abstaining.
> 
> I suppose my objections can be distilled into these points:
> 
> 1) it's misleading to label this as an "abstain" vote, no matter how it's defined in IESG procedures
> 2) such objections should be treated more seriously than required by the current process
> 3) anything written in the data tracker is essentially buried to the audience of the RFCs  (though RFC errata might work somewhat better)
> 
> I'm not saying that a single AD should be able to block a document indefinitely, but neither should it be presumed that the WG should inherently prevail in a conflict.  
> 
> I actually think that the "rough consensus" model is not well suited for IESG, because IESG rarely has enough members with the kind of expertise needed to make that kind of judgment.   The number of IESG members who review a typical document and really understand its implications is probably around 3-4.    Most of those voting "no objection" have probably not read the document, at least not in depth.  So in a case where there's one sponsoring AD voting yes and one AD voting discuss, it's really close to one or two in favor against one opposed.  But the way IESG votes, distorts this and makes it look like many against one. 
> 
> Keith
> 
> 

From moore@network-heretics.com  Sun Aug 14 17:15:39 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7967821F877F for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.45
X-Spam-Level: 
X-Spam-Status: No, score=-3.45 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PQoBs7hq0tE for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:15:38 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 9EAD621F877B for <ietf@ietf.org>; Sun, 14 Aug 2011 17:15:38 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 9CD1A21E9F; Sun, 14 Aug 2011 20:16:22 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 14 Aug 2011 20:16:22 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=tEp r0fNcgM0X6Q0kU2qtCdTXVMA=; b=qOIq5bJ4O2RsxLUnpDKghtekS9cL1bCQgxX ONdLaocQ9R1A/04LIE9HYhOkVw/C9A3sRNIKpvP4jVAiBVplC3HdhuXe+qJcl1+t Yk4aHoIdHp0rktOOB/OYVWNSNGot1FIW6vuLlQOwbZWdbiMga7nB8WfF4162aWII Q33a5Ioc=
X-Sasl-enc: E2HHSOC8jWWHsbxk1gRqhXpTXOtT/cBvgA2vm1OH3wnn 1313367381
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 66F6841D6AD; Sun, 14 Aug 2011 20:16:21 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-46-52731781
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E48629F.2070105@gmail.com>
Date: Sun, 14 Aug 2011 20:16:20 -0400
Message-Id: <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi>	<B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>	<E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>	<951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: adrian@olddog.co.uk, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 00:15:39 -0000

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

On Aug 14, 2011, at 8:04 PM, Brian E Carpenter wrote:

>  You can call it 'abstain' or you can
> call it 'no'. What it means is that the AD concerned has
> objections to the document that *cannot* be fixed (anything that
> can be fixed is a 'discuss').

That's not how I interpret the voting procedures:

If an AD cannot get cooperation from the WG and cannot enter a ballot =
position that supports sending the document forward, then the AD should =
switch to "abstain."

...which seems to say that the question is not whether the objections =
can be fixed, but rather, whether the WG is willing to   fix them.

> And I think in that case, there is
> no way that one or two ADs should be able to block something
> because they don't like it, *unless* they can convince the rest
> of the IESG that the document is harmful.

Convincing the entire IESG is a very high barrier, especially when =
typically, most of the IESG just wants the issue to go away.    It might =
happen for a significant architectural issue, perhaps, but not for an =
area-specific technical flaw.=20

(Though as I understand the rules, 1/3 of the non-recused IESG members =
can block a document by voting Abstain.  Still, that's a very high =
barrier given that in most cases 1/3 of IESG members won't even read the =
document.)

Why should a narrowly-focused working group get to hold sway unless a =
significant fraction of the IESG objects?   How does it benefit the =
Internet to gloss over technical problems found during IESG review?

(not to single you out, Brian, because I'm fairly confident that a =
significant plurality of IETF participants agree with you)

Keith


--Apple-Mail-46-52731781
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><div>On Aug 14, 2011, at 8:04 PM, Brian E Carpenter =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>&nbsp;You can call it 'abstain' or you can<br>call it =
'no'. What it means is that the AD concerned has<br>objections to the =
document that *cannot* be fixed (anything that<br>can be fixed is a =
'discuss'). </div></blockquote><div><br></div><div>That's not how I =
interpret the voting procedures:</div><div><br></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Verdana, Arial, =
Helvetica, sans-serif; font-size: 13px; background-color: rgb(255, 255, =
255); ">If an AD cannot get cooperation from the WG&nbsp;</span><span =
class=3D"Apple-style-span" style=3D"font-family: Verdana, Arial, =
Helvetica, sans-serif; font-size: 13px; background-color: rgb(255, 255, =
255); ">and cannot enter a ballot position that supports sending the =
document forward, then the AD should switch to =
"abstain."</span></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: Verdana, Arial, Helvetica, sans-serif; font-size: =
13px; background-color: rgb(255, 255, 255); =
"><br></span></div><div>...which seems to say that the question is not =
whether the objections can be fixed, but rather, whether the WG is =
willing to &nbsp; fix them.</div><br><blockquote type=3D"cite"><div>And =
I think in that case, there is<br>no way that one or two ADs should be =
able to block something<br>because they don't like it, *unless* they can =
convince the rest<br>of the IESG that the document is =
harmful.<br></div></blockquote></div><br><div>Convincing the entire IESG =
is a very high barrier, especially when typically, most of the IESG just =
wants the issue to go away. &nbsp; &nbsp;It might happen for a =
significant architectural issue, perhaps, but not for an area-specific =
technical flaw.&nbsp;</div><div><br></div><div>(Though as I understand =
the rules, 1/3 of the non-recused IESG members can block a document by =
voting Abstain. &nbsp;Still, that's a very high barrier given that in =
most cases 1/3 of IESG members won't even read the =
document.)</div><div><br></div><div>Why should a narrowly-focused =
working group get to hold sway unless a significant fraction of the IESG =
objects? &nbsp; How does it benefit the Internet to gloss over technical =
problems found during IESG review?</div><div><br></div><div>(not to =
single you out, Brian, because I'm fairly confident that a significant =
plurality of IETF participants agree with =
you)</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-46-52731781--

From barryleiba.mailing.lists@gmail.com  Sun Aug 14 17:39:24 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E358E21F86BE for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.891
X-Spam-Level: 
X-Spam-Status: No, score=-102.891 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHlKgCBBUEW4 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:39:24 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5287D21F8549 for <ietf@ietf.org>; Sun, 14 Aug 2011 17:39:24 -0700 (PDT)
Received: by gwb20 with SMTP id 20so3385326gwb.31 for <ietf@ietf.org>; Sun, 14 Aug 2011 17:40:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=IUTOqQSAzgcFMQpxJjCqMUjPztYqPPEU30dIouyOo4M=; b=au08GN6/rjh35+1Zv73IiK4fTPrk4gpfukxvHGVmEA3pD8YF/vooVNUB5qpgSPo0Lg MeJ4fRfTSCmjuiQAYvQGHpk+vQ727vVTc+sEZ0cAkICxiWDjCkQ5r48i2sJfoLsTQrNq 5kLolQTHr0ym40MmKUQcwx/jYsVbO+VXdjCYo=
MIME-Version: 1.0
Received: by 10.146.58.22 with SMTP id g22mr3270176yaa.34.1313368808224; Sun, 14 Aug 2011 17:40:08 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.181.13 with HTTP; Sun, 14 Aug 2011 17:40:08 -0700 (PDT)
In-Reply-To: <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com>
Date: Sun, 14 Aug 2011 20:40:08 -0400
X-Google-Sender-Auth: U_EB0quUVYqJ_a1fvcqf5uJlqco
Message-ID: <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com>
Subject: Re: IESG voting procedures
From: Barry Leiba <barryleiba@computer.org>
To: Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: adrian@olddog.co.uk, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 00:39:25 -0000

> Convincing the entire IESG is a very high barrier, especially when
> typically, most of the IESG just wants the issue to go away. =A0 =A0It mi=
ght
> happen for a significant architectural issue, perhaps, but not for an
> area-specific technical flaw.

Here's the point: if an AD can't get at least one or two other ADs to
read the document and agree to join in the blocking, then that AD MUST
NOT be allowed to block the document.  That's even the case if the AD
thinks she's found a serious flaw.  Because if, out of 14 others in
the IESG, not ONE other is willing to read the document, understand
the issue, and agree on it.

According to the current rules:

1. If ONE other AD places a second DISCUSS position OR enters a
comment that supports the first AD's DISCUSS, the document stays
blocked.  The "single discuss" procedure does NOT kick in.

2. If the WG still insists on pushing the document and the IESG goes
into the "alternate ballot" (which should be "alternative ballot", but
never mind that) procedure, the DISCUSSing AD still only needs TWO
other ADs to read the document and vote "no".  Three "no" votes will
maintain the block on the document.

Really, if you can't get two out of fourteen technical leaders to
agree with you, maybe you just have to accept that you're wrong.  If
things get down to such a rarely used (read: never) last-ditch
procedure, you can bet that essentially the entire IESG *will* read
the document (you might miss one or two ADs at the most, *maybe*).  If
it gets to that and you're *right* to block, you should be able to
convince two of fourteen to support you.

There is NO case in which it makes sense for a *single* person, with
no peer support or agreement, to be allowed to block a document
indefinitely, no matter HOW serious she THINKS the problem she's found
is.

Barry

From rbonica@juniper.net  Sun Aug 14 17:46:36 2011
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5472821F89A1 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level: 
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-scyaaViF9e for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 17:46:35 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id D16F721F8782 for <ietf@ietf.org>; Sun, 14 Aug 2011 17:46:33 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTkhsk+5eGGTV5UHzsOyM/RVcKQYJiulj@postini.com; Sun, 14 Aug 2011 17:47:20 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 14 Aug 2011 17:46:59 -0700
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; Sun, 14 Aug 2011 20:46:58 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, 'Keith Moore' <moore@network-heretics.com>
Date: Sun, 14 Aug 2011 20:46:56 -0400
Subject: RE: IESG voting procedures
Thread-Topic: IESG voting procedures
Thread-Index: AQKi/mMT2wl1auhunjRRkJCg6nQviQKQSErCAi5n1WoCSBDGcgMzx/JHATFVDlQCHimVSAHZmMvKAd+lH3kBMpB1xwISpwlSkstUORCAADL7sA==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D43D4FCA7A@EMBX01-WF.jnpr.net>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk>
In-Reply-To: <005c01cc5acb$05058310$0f108930$@olddog.co.uk>
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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 00:46:36 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>
> [snip]
>
> When an AD is clearly in the rough against the consensus of the IESG=20
> they should not have the power to individually block the progress of=20
> work for which there is clear IETF consensus.
>

+1

The current voting procedure is the only protection that the community has =
against an AD who has decided that his opinion trumps the expertise of the =
working group and the rest of the IESG.=20

                                                                  Ron

=20


From moore@network-heretics.com  Sun Aug 14 18:01:00 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6506911E809F for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.451
X-Spam-Level: 
X-Spam-Status: No, score=-3.451 tagged_above=-999 required=5 tests=[AWL=0.147,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lXa4Ce1fQTL8 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:00:59 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 721FD11E8094 for <ietf@ietf.org>; Sun, 14 Aug 2011 18:00:59 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8814322164; Sun, 14 Aug 2011 21:01:43 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 14 Aug 2011 21:01:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=xg8 3zooq84HxJXh8G5ZnDKIAvsE=; b=LFN4UmwGj2aRgrYjBffCMcl3csFNEHsZFzt +6LvXIwKgtiXSuiWdVOXKx17Cw+F0mFxArJjVQygkHYIcbFcFZ9TYrVHwZRpe8Qo 1K3vcPkcgTAszCmWecApiMVLupqoIL8+WW8rqcbs6yeRrUx3sTzWKCw5qA9MsBWn vGVho6Cw=
X-Sasl-enc: 8CKUA5o3ylEImVaQk8/V5ZhN+FwXaQglbSuBAwhQnzPq 1313370102
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2645241D7D8; Sun, 14 Aug 2011 21:01:42 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-47-55452032
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com>
Date: Sun, 14 Aug 2011 21:01:40 -0400
Message-Id: <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com> <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
Cc: adrian@olddog.co.uk, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 01:01:00 -0000

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


On Aug 14, 2011, at 8:40 PM, Barry Leiba wrote:

>> Convincing the entire IESG is a very high barrier, especially when
>> typically, most of the IESG just wants the issue to go away.    It =
might
>> happen for a significant architectural issue, perhaps, but not for an
>> area-specific technical flaw.
>=20
> Here's the point: if an AD can't get at least one or two other ADs to
> read the document and agree to join in the blocking, then that AD MUST
> NOT be allowed to block the document.  That's even the case if the AD
> thinks she's found a serious flaw.  Because if, out of 14 others in
> the IESG, not ONE other is willing to read the document, understand
> the issue, and agree on it.

That's also how I interpret the rules.  I just don't think that this is =
sufficient review.  I think that in practice it makes IESG more-or-less =
a rubber stamp for any issue that isn't easily fixed with small and =
often inconsequential changes to the document text.

The problem is, the ADs are very busy people, and their expertise has to =
cover a wide range of topics, so there will be few IESG members who can =
really understand a subtle issue.   Document reviews outside of one's =
subject area are very difficult and require considerable focus.   GIven =
that, even if only one AD catches a flaw in a document, there's a good =
chance (though not a certainty of course) that it's something that =
warrants more attention.   It's far more likely that no ADs will find =
the flaw because nobody really took the time to read the document =
thoroughly and to understand its implications of the document outside of =
the narrow subject area of the working group.

I understand (and agree with) the sentiment that, ultimately, one or two =
people shouldn't be able to block a document.  Nor do I want documents =
held up for trivialities as, unfortunately, sometimes happens.  But I've =
seen many cases where working groups failed to do an adequate level of =
review outside of their narrow areas of concern, and it appears that =
IESG's current rules and workload make it difficult for problems to get =
fixed after a document leaves the WG.  =20

(and people keep arguing to remove steps from our process so that there =
will be even less review after a document has progressed to Proposed...)

The only other formal level of review we have are the Last Call comments =
which, given the volume of documents that get Last Called, amounts to a =
fairly small and random chance that somebody outside the WG will happen =
to notice the proposed document action and give the document a thorough =
review.

To put the question another way:  What level of formal technical review, =
outside of a WG, best serves IETF's goals?=20

Keith


--Apple-Mail-47-55452032
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 Aug 14, 2011, at 8:40 PM, Barry Leiba wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">Convincing the entire IESG =
is a very high barrier, especially when<br></blockquote><blockquote =
type=3D"cite">typically, most of the IESG just wants the issue to go =
away. &nbsp; &nbsp;It might<br></blockquote><blockquote =
type=3D"cite">happen for a significant architectural issue, perhaps, but =
not for an<br></blockquote><blockquote type=3D"cite">area-specific =
technical flaw.<br></blockquote><br>Here's the point: if an AD can't get =
at least one or two other ADs to<br>read the document and agree to join =
in the blocking, then that AD MUST<br>NOT be allowed to block the =
document. &nbsp;That's even the case if the AD<br>thinks she's found a =
serious flaw. &nbsp;Because if, out of 14 others in<br>the IESG, not ONE =
other is willing to read the document, understand<br>the issue, and =
agree on it.<br></div></blockquote><div><br></div>That's also how I =
interpret the rules. &nbsp;I just don't think that this is sufficient =
review. &nbsp;I think that in practice it makes IESG more-or-less a =
rubber stamp for any issue that isn't easily fixed with small and often =
inconsequential changes to the document =
text.</div><div><br></div><div>The problem is, the ADs are very busy =
people, and their expertise has to cover a wide range of topics, so =
there will be few IESG members who can really understand a subtle issue. =
&nbsp; Document reviews outside of one's subject area are very difficult =
and require considerable focus. &nbsp; GIven that, even if only one AD =
catches a flaw in a document, there's a good chance (though not a =
certainty of course) that it's something that warrants more attention. =
&nbsp; It's far more likely that <i>no</i> ADs will find the flaw =
because nobody really took the time to read the document thoroughly and =
to understand its implications of the document outside of the narrow =
subject area of the working group.</div><div><br></div><div>I understand =
(and agree with) the sentiment that, ultimately, one or two people =
shouldn't be able to block a document. &nbsp;Nor do I want documents =
held up for trivialities as, unfortunately, sometimes happens. &nbsp;But =
I've seen many cases where working groups failed to do an adequate level =
of review outside of their narrow areas of concern, and it appears that =
IESG's current rules and workload make it difficult for problems to get =
fixed after a document leaves the WG. =
&nbsp;&nbsp;</div><div><br></div><div>(and people keep arguing to remove =
steps from our process so that there will be even less review after a =
document has progressed to Proposed...)</div><div><br></div><div>The =
only other formal level of review we have are the Last Call comments =
which, given the volume of documents that get Last Called, amounts to a =
fairly small and random chance that somebody outside the WG will happen =
to notice the proposed document action and give the document a thorough =
review.</div><div><br></div><div>To put the question another way: =
&nbsp;What level of formal technical review, outside of a WG, best =
serves IETF's =
goals?&nbsp;</div><br><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-47-55452032--

From moore@network-heretics.com  Sun Aug 14 18:02:53 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E3321F86D0 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.453
X-Spam-Level: 
X-Spam-Status: No, score=-3.453 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 72nWOZtcLoHn for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:02:53 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 323E221F8593 for <ietf@ietf.org>; Sun, 14 Aug 2011 18:02:53 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 4A28A22332; Sun, 14 Aug 2011 21:03:37 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 14 Aug 2011 21:03:37 -0400
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=GH+JSOvT4chQYEdNLCkftqS24aA=; b=Vy hze1uxK079wzL1K3pjLqJ6xklNPo5CUoQ/y6ODZZDKyEkCBOD6pSyZdmPm65WrCO RcL91smWchzw/gOdvymdH/xJh6X7kFkFRpHKc61czFqei0ST/rk+e7Wnxeynota/ xCYo5P5a43NjZt/z5Gi6AEl0ABoC1UZ/c007anEvM=
X-Sasl-enc: ChGzmBGhHEZJq5dra+8kS1iw11n99alJgsxW4okeo7x0 1313370216
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 4029741D64F; Sun, 14 Aug 2011 21:03:36 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D43D4FCA7A@EMBX01-WF.jnpr.net>
Date: Sun, 14 Aug 2011 21:03:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7A24536-E2E2-4533-94AC-9EB15B967AD4@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@[192.168.1.128]> <01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <13205C286662DE4387D9AF3AC30EF456D43D4FCA7A@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 01:02:53 -0000

On Aug 14, 2011, at 8:46 PM, Ronald Bonica wrote:

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>>=20
>> [snip]
>>=20
>> When an AD is clearly in the rough against the consensus of the IESG=20=

>> they should not have the power to individually block the progress of=20=

>> work for which there is clear IETF consensus.
>>=20
>=20
> +1

I don't disagree with the above.  What I disagree with is the notion =
that the rest of the overworked IESG provides adequate review.

> The current voting procedure is the only protection that the community =
has against an AD who has decided that his opinion trumps the expertise =
of the working group and the rest of the IESG.=20

It's the only protection that exists now.  But it's not the only way to =
solve the problem.

Keith


From barryleiba@gmail.com  Sun Aug 14 18:29:46 2011
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BED21F8B07 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.042
X-Spam-Level: 
X-Spam-Status: No, score=-103.042 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id utJu7vObb7DD for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:29:45 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4F721F8B08 for <ietf@ietf.org>; Sun, 14 Aug 2011 18:29:42 -0700 (PDT)
Received: by yie12 with SMTP id 12so3390944yie.31 for <ietf@ietf.org>; Sun, 14 Aug 2011 18:30:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3XEXXPJeAbvwFZVXGJVH2r9R3vfMlNrXyXEJdtzHgKs=; b=i3tIfG5ht1ZdTsdTOXvqrFTZZ1XDT4jdgKBvxEjZxNuLBnjhFatx9ybahnynOHl0zf dBgWYkm8lrv7e4AnPW0kyhW05VZyINf98g/0tKiMuTWSJ4aHHx3beU646b9GZtAtgl9l VAJpf58TgfHQ+/IHCMymEjo5uuRNJ1nvYaEqo=
MIME-Version: 1.0
Received: by 10.236.193.105 with SMTP id j69mr10757457yhn.72.1313371826252; Sun, 14 Aug 2011 18:30:26 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.207.167 with HTTP; Sun, 14 Aug 2011 18:30:25 -0700 (PDT)
In-Reply-To: <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com> <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com>
Date: Sun, 14 Aug 2011 21:30:25 -0400
X-Google-Sender-Auth: nzFAzwVMfjsgZpMmexOd83_FPZQ
Message-ID: <CALaySJ+rcXdi=CBz07o3gUgb2tq_q8ij6f6O7q-Nq4K9NAp3ww@mail.gmail.com>
Subject: Re: IESG voting procedures
From: Barry Leiba <barryleiba@computer.org>
To: Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: adrian@olddog.co.uk, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 01:29:46 -0000

> The problem is, the ADs are very busy people, and their expertise has to
> cover a wide range of topics, so there will be few IESG members who can
> really understand a subtle issue. =A0 Document reviews outside of one's
> subject area are very difficult and require considerable focus. =A0 GIven
> that, even if only one AD catches a flaw in a document, there's a good
> chance (though not a certainty of course) that it's something that warran=
ts
> more attention. =A0 It's far more likely that no ADs will find the flaw

My point isn't that I expect multiple ADs to find the same problem
initially.  What I expect to happen is that, say, Keith finds a flaw
and lodges a DISCUSS position.  It's discussed, and the WG insists
that it's not a problem and shouldn't be changed.  Keith maintains the
DISCUSS, and it's gone over on the telechat.  At the end of that,
Keith still maintains the DISCUSS.  More discussion among Keith, the
responsible AD, and the WG ensues, and it's still not resolved -- the
WG still refuses to change the spec, and Keith still maintains the
DISCUSS position.

It's at THAT stage that at least one other AD should have read the
document, read Keith's DISCUSS position, and agreed with Keith.
That's not a very high bar.  And *that* is where I say that if there's
still no one backing Keith's DISCUSS, even with his *asking* other ADs
to have a look, Keith needs to back down.

Barry

From moore@network-heretics.com  Sun Aug 14 18:35:49 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8145E8006 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level: 
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nnZ-iuoD8pzi for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 18:35:48 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 7B0545E8008 for <ietf@ietf.org>; Sun, 14 Aug 2011 18:35:48 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 9D10521C81; Sun, 14 Aug 2011 21:36:32 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 14 Aug 2011 21:36:32 -0400
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=uJFXihJo9cbklGRJFPrS3Cl+uV8=; b=Fn qeE4CBwjgUIwjRkmeBnYTg5NTQKMR1yOIGIPhaPUoRJd9V4NzDs+NMXb05nR7Dru DOByLqmYCvbq8sxNoDv5owC4PZa3SCjHVec49Ry/a98N7Dub2sbbf/bZphMovqMg aXd7X7lE7gV7YXioxA5Yd0lu0E57yF8OKp+qJXyTc=
X-Sasl-enc: sTyt7oU14sfDZ0zKTkvJzNHS+Ub3ALXGt27U8NA5H4Qz 1313372192
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 942C241D62E; Sun, 14 Aug 2011 21:36:31 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CALaySJ+rcXdi=CBz07o3gUgb2tq_q8ij6f6O7q-Nq4K9NAp3ww@mail.gmail.com>
Date: Sun, 14 Aug 2011 21:36:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5A9AF57-0763-485F-A586-284A3889C14A@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com> <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com> <CALaySJ+rcXdi=CBz07o3gUgb2tq_q8ij6f6O7q-Nq4K9NAp3ww@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
Cc: adrian@olddog.co.uk, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 01:35:49 -0000

On Aug 14, 2011, at 9:30 PM, Barry Leiba wrote:

> My point isn't that I expect multiple ADs to find the same problem
> initially.  What I expect to happen is that, say, Keith finds a flaw
> and lodges a DISCUSS position.  It's discussed, and the WG insists
> that it's not a problem and shouldn't be changed.  Keith maintains the
> DISCUSS, and it's gone over on the telechat.  At the end of that,
> Keith still maintains the DISCUSS.  More discussion among Keith, the
> responsible AD, and the WG ensues, and it's still not resolved -- the
> WG still refuses to change the spec, and Keith still maintains the
> DISCUSS position.
>=20
> It's at THAT stage that at least one other AD should have read the
> document, read Keith's DISCUSS position, and agreed with Keith.
> That's not a very high bar.  And *that* is where I say that if there's
> still no one backing Keith's DISCUSS, even with his *asking* other ADs
> to have a look, Keith needs to back down.

Disagree in two aspects:

1. It can be very difficult to get other ADs to understand issues, =
especially in areas outside their expertise, when they're mired in other =
documents.  Getting something fixed shouldn't rely on other members of =
IESG to pay attention to it.

2. Even if the document is approved over the AD's objection, I think =
it's completely unacceptable to bury the AD's technical objection.  =
Expecting the AD to change his Discuss to an Abstain is dishonesty on =
the part of the organization.

But at this point I'm repeating myself, and I don't think we're covering =
any new ground.  So I'll either just hope that this made a useful =
impression on somebody, or I'll write up an Internet-Draft.

I just think it's sad to see the level of technical review in IETF, =
which was already insufficient at the time that I was an AD, steadily =
eroding still further.

Keith


From McQuilWP@pobox.com  Sun Aug 14 22:21:19 2011
Return-Path: <McQuilWP@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13CB721F8797 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 22:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1O8iETsrnOFj for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2011 22:21:18 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFEB21F86B3 for <ietf@ietf.org>; Sun, 14 Aug 2011 22:21:16 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id B93F712DA; Mon, 15 Aug 2011 01:21:59 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=rnhfg6Pbqonb 2eeK5EISQsi9kLU=; b=q7bYUg9ENQRumf5cPk+vFCvr9DX7HR9posckvevFtydj nb6zLxEuQufdMDqMDGALBrHDTMk3UhP30LnDUh6I8omhKXSUW/HkcwxOalLRf7EF ehmcJvRNv2250/cNT7JDOFVuoMGSkbbaQjr1dY2NFo4DiZeZ8W7ra1IptlkY4I0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=nKyMmI GCzqCK95bJ+0qKrkKuh0lqQew31mBJ9TDjScEyM6UnfBwCo+f1KZW86tdvDpQ8Ce sTnBwQ1cGR3TnwsO/nRNQ5HMfPWHXe0wBHcsxnpPg03kI680TNlQPEPqpi+Ur5+F k6XI6w04b3R5qDUptEF1ArEpb0pGOGW1rhu8k=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id B0CB212D9; Mon, 15 Aug 2011 01:21:59 -0400 (EDT)
Received: from BQ07NB (unknown [70.181.252.118]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id 3B28212D7; Mon, 15 Aug 2011 01:21:59 -0400 (EDT)
Date: Sun, 14 Aug 2011 22:21:58 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <153456884.20110814222158@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: IESG voting procedures
In-Reply-To: <A5A9AF57-0763-485F-A586-284A3889C14A@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com> <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com> <CALaySJ+rcXdi=CBz07o3gUgb2tq_q8ij6f6O7q-Nq4K9NAp3ww@mail.gmail.com> <A5A9AF57-0763-485F-A586-284A3889C14A@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 801C9BE8-C6FE-11E0-9F13-1DC62E706CDE-02871704!b-pb-sasl-quonix.pobox.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 05:21:19 -0000

On Sun, 2011-08-14, Keith Moore wrote:

> 2. Even if the document is approved over the AD's objection, I
> think it's completely unacceptable to bury the AD's technical
> objection.  Expecting the AD to change his Discuss to an
> Abstain is dishonesty on the part of the organization.

It sure sounds like if the status is renamed: 

   Disagree-But-Overruled

the annoyance becomes much smaller.

(Just my 2 cents)

-- 
Bill McQuillan <McQuilWP@pobox.com>


From dromasca@avaya.com  Mon Aug 15 02:50:02 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5F6421F8B13 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 02:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.419
X-Spam-Level: 
X-Spam-Status: No, score=-103.419 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OAuHPn-WhmxI for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 02:50:00 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE2C21F8AF8 for <ietf@ietf.org>; Mon, 15 Aug 2011 02:49:59 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As8AAMjqSE7GmAcF/2dsb2JhbABAgk2VaY9Od4FAAQEBAQMSChEDOw4QAgEIDQQEAQELBgwLAQYBRQkIAQEEARIIGqEWAps0hWhfBIcwkQyLTQ
X-IronPort-AV: E=Sophos;i="4.67,373,1309752000";  d="scan'208,217";a="297512483"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 15 Aug 2011 05:50:42 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 15 Aug 2011 05:47:14 -0400
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_01CC5B30.CB1F843E"
Subject: RE: IESG voting procedures
Date: Mon, 15 Aug 2011 11:50:39 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04037E1DFD@307622ANEX5.global.avaya.com>
In-Reply-To: <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IESG voting procedures
Thread-Index: Acxa5uu19S+MOlbISRuEqCRfPDprLQAST8ew
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com><6.2.5.6.2.20110728234859.075cb888@resistor.net><B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com><6.2.5.6.2.20110804043544.084eb5c0@resistor.net><420C8B2470E5AAC8A12E5740@192.168.1.128><01O4STOSKQ1600VHKR@mauve.mrochek.com><20110813204315.GA53261@verdi><B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com><E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com><951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com><4E483990.6030905@gmail.com><005c01cc5acb$05058310$0f108930$@olddog.co.uk><645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com><4E48629F.2070105@gmail.com><AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com><CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Keith Moore" <moore@network-heretics.com>, "Barry Leiba" <barryleiba@computer.org>
Cc: adrian@olddog.co.uk, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 09:50:03 -0000

This is a multi-part message in MIME format.

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

Hi Keith,

=20

=D8  The only other formal level of review we have are the Last Call =
comments which, given the volume of documents that get Last Called, =
amounts to a fairly small and random chance that somebody outside the WG =
will happen to notice the proposed document action and give the document =
a thorough review.

=20

I do not know whether to call these 'formal' but currently all documents =
that go to Last Call also undergo three expert reviews - Gen-ART, =
Sec-DIR and OPS-DIR. According to the scope of the documents a few more =
expert reviews may be called as required by the WG, shepherd or AD - =
APPS-Dir, TSV-Dir, MIB-Doctors, DNS-Dir, etc.=20

=20

Regards,

=20

Dan

=20

=20

=20

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Keith Moore
Sent: Monday, August 15, 2011 4:02 AM
To: Barry Leiba
Cc: adrian@olddog.co.uk; IETF
Subject: Re: IESG voting procedures

=20

=20

On Aug 14, 2011, at 8:40 PM, Barry Leiba wrote:





	Convincing the entire IESG is a very high barrier, especially when

	typically, most of the IESG just wants the issue to go away.    It =
might

	happen for a significant architectural issue, perhaps, but not for an

	area-specific technical flaw.


Here's the point: if an AD can't get at least one or two other ADs to
read the document and agree to join in the blocking, then that AD MUST
NOT be allowed to block the document.  That's even the case if the AD
thinks she's found a serious flaw.  Because if, out of 14 others in
the IESG, not ONE other is willing to read the document, understand
the issue, and agree on it.

=20

That's also how I interpret the rules.  I just don't think that this is =
sufficient review.  I think that in practice it makes IESG more-or-less =
a rubber stamp for any issue that isn't easily fixed with small and =
often inconsequential changes to the document text.

=20

The problem is, the ADs are very busy people, and their expertise has to =
cover a wide range of topics, so there will be few IESG members who can =
really understand a subtle issue.   Document reviews outside of one's =
subject area are very difficult and require considerable focus.   GIven =
that, even if only one AD catches a flaw in a document, there's a good =
chance (though not a certainty of course) that it's something that =
warrants more attention.   It's far more likely that no ADs will find =
the flaw because nobody really took the time to read the document =
thoroughly and to understand its implications of the document outside of =
the narrow subject area of the working group.

=20

I understand (and agree with) the sentiment that, ultimately, one or two =
people shouldn't be able to block a document.  Nor do I want documents =
held up for trivialities as, unfortunately, sometimes happens.  But I've =
seen many cases where working groups failed to do an adequate level of =
review outside of their narrow areas of concern, and it appears that =
IESG's current rules and workload make it difficult for problems to get =
fixed after a document leaves the WG.  =20

=20

(and people keep arguing to remove steps from our process so that there =
will be even less review after a document has progressed to Proposed...)

=20

The only other formal level of review we have are the Last Call comments =
which, given the volume of documents that get Last Called, amounts to a =
fairly small and random chance that somebody outside the WG will happen =
to notice the proposed document action and give the document a thorough =
review.

=20

To put the question another way:  What level of formal technical review, =
outside of a WG, best serves IETF's goals?=20

=20

Keith

=20


------_=_NextPart_001_01CC5B30.CB1F843E
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 =
12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1593198183;
	mso-list-type:hybrid;
	mso-list-template-ids:185500130 -127376616 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
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 style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal>Hi Keith,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>=D8<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span dir=3DLTR></span>The =
only other formal level of review we have are the Last Call comments =
which, given the volume of documents that get Last Called, amounts to a =
fairly small and random chance that somebody outside the WG will happen =
to notice the proposed document action and give the document a thorough =
review.<o:p></o:p></p><p =
class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph>I do not know whether to call these =
&#8216;formal&#8217; but currently all documents that go to Last Call =
also undergo three expert reviews &#8211; Gen-ART, Sec-DIR and OPS-DIR. =
According to the scope of the documents a few more expert reviews may be =
called as required by the WG, shepherd or AD &#8211; APPS-Dir, TSV-Dir, =
MIB-Doctors, DNS-Dir, etc. <o:p></o:p></p><p =
class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph>Regards,<o:p></o:p></p><p =
class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p =
class=3DMsoListParagraph>Dan<o:p></o:p></p><p =
class=3DMsoListParagraph><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><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"'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Keith Moore<br><b>Sent:</b> Monday, August 15, 2011 4:02 =
AM<br><b>To:</b> Barry Leiba<br><b>Cc:</b> adrian@olddog.co.uk; =
IETF<br><b>Subject:</b> Re: IESG voting =
procedures<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Aug 14, 2011, at 8:40 PM, Barry Leiba wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>Convincing the entire IESG is a very high barrier, =
especially when<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>typically, most of the IESG just wants the issue to go =
away. &nbsp; &nbsp;It might<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>happen for a significant architectural issue, perhaps, =
but not for an<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>area-specific technical =
flaw.<o:p></o:p></p></blockquote><p class=3DMsoNormal><br>Here's the =
point: if an AD can't get at least one or two other ADs to<br>read the =
document and agree to join in the blocking, then that AD MUST<br>NOT be =
allowed to block the document. &nbsp;That's even the case if the =
AD<br>thinks she's found a serious flaw. &nbsp;Because if, out of 14 =
others in<br>the IESG, not ONE other is willing to read the document, =
understand<br>the issue, and agree on it.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>That's =
also how I interpret the rules. &nbsp;I just don't think that this is =
sufficient review. &nbsp;I think that in practice it makes IESG =
more-or-less a rubber stamp for any issue that isn't easily fixed with =
small and often inconsequential changes to the document =
text.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The problem is, the ADs are very busy people, and =
their expertise has to cover a wide range of topics, so there will be =
few IESG members who can really understand a subtle issue. &nbsp; =
Document reviews outside of one's subject area are very difficult and =
require considerable focus. &nbsp; GIven that, even if only one AD =
catches a flaw in a document, there's a good chance (though not a =
certainty of course) that it's something that warrants more attention. =
&nbsp; It's far more likely that <i>no</i> ADs will find the flaw =
because nobody really took the time to read the document thoroughly and =
to understand its implications of the document outside of the narrow =
subject area of the working group.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
understand (and agree with) the sentiment that, ultimately, one or two =
people shouldn't be able to block a document. &nbsp;Nor do I want =
documents held up for trivialities as, unfortunately, sometimes happens. =
&nbsp;But I've seen many cases where working groups failed to do an =
adequate level of review outside of their narrow areas of concern, and =
it appears that IESG's current rules and workload make it difficult for =
problems to get fixed after a document leaves the WG. =
&nbsp;&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>(and people keep arguing to remove steps from our =
process so that there will be even less review after a document has =
progressed to Proposed...)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The only other formal level of review we have are the =
Last Call comments which, given the volume of documents that get Last =
Called, amounts to a fairly small and random chance that somebody =
outside the WG will happen to notice the proposed document action and =
give the document a thorough review.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>To put the question another way: &nbsp;What level of =
formal technical review, outside of a WG, best serves IETF's =
goals?&nbsp;<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>Keith<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------_=_NextPart_001_01CC5B30.CB1F843E--

From moore@network-heretics.com  Mon Aug 15 04:51:59 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99EA521F8B70 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 04:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level: 
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3P5LCVmYM8a4 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 04:51:58 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6B28D21F8B6F for <ietf@ietf.org>; Mon, 15 Aug 2011 04:51:58 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 6DBA0208BC; Mon, 15 Aug 2011 07:52:43 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 15 Aug 2011 07:52:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Qxo RR3YyMJxhlX5LSd6ADGINF14=; b=qks9HfxKQOs4nzE6IUYXMJ+co53osxHN5Z0 JCIQ5sMn+ed4jwxgzbBCpr2B6P5L3CITiQ+Z9u7sXMBKYARcak5XA7Gplpp5/sSj 7gigQbVDuUsKsdFAQhcYBJH4X404dLe/KCGnPNkvUB4ijgXnA20ZKXZQ3RJDAy9+ mhMiiV8s=
X-Sasl-enc: 6uV/UOUqfy7ImJsVGWY9FG73A6iM/TEszUT4ABezouRI 1313409160
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 5DC2341D938; Mon, 15 Aug 2011 07:52:39 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-48-94507830
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04037E1DFD@307622ANEX5.global.avaya.com>
Date: Mon, 15 Aug 2011 07:52:36 -0400
Message-Id: <C9AB35BF-0E63-4AE2-83F5-91EA85771BF3@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com><6.2.5.6.2.20110728234859.075cb888@resistor.net><B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com><6.2.5.6.2.20110804043544.084eb5c0@resistor.net><420C8B2470E5AAC8A12E5740@192.168.1.128><01O4STOSKQ1600VHKR@mauve.mrochek.com><20110813204315.GA53261@verdi><B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com><E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com><951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com><4E483990.6030905@gmail.com><005c01cc5acb$05058310$0f108930$@olddog.co.uk><645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com><4E48629F.2070105@gmail.com><AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com><CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com> <EDC652A26FB23C4EB6384A4584434A04037E1DFD@307622ANEX5.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1084)
Cc: adrian@olddog.co.uk, Barry Leiba <barryleiba@computer.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 11:51:59 -0000

--Apple-Mail-48-94507830
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks for that info.  That does make me feel a bit better.

Keith

On Aug 15, 2011, at 5:50 AM, Romascanu, Dan (Dan) wrote:

> Hi Keith,
> =20
> =D8  The only other formal level of review we have are the Last Call =
comments which, given the volume of documents that get Last Called, =
amounts to a fairly small and random chance that somebody outside the WG =
will happen to notice the proposed document action and give the document =
a thorough review.
> =20
> I do not know whether to call these =91formal=92 but currently all =
documents that go to Last Call also undergo three expert reviews =96 =
Gen-ART, Sec-DIR and OPS-DIR. According to the scope of the documents a =
few more expert reviews may be called as required by the WG, shepherd or =
AD =96 APPS-Dir, TSV-Dir, MIB-Doctors, DNS-Dir, etc.
> =20
> Regards,
> =20
> Dan
> =20
> =20
> =20
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Keith Moore
> Sent: Monday, August 15, 2011 4:02 AM
> To: Barry Leiba
> Cc: adrian@olddog.co.uk; IETF
> Subject: Re: IESG voting procedures
> =20
> =20
> On Aug 14, 2011, at 8:40 PM, Barry Leiba wrote:
>=20
>=20
> Convincing the entire IESG is a very high barrier, especially when
> typically, most of the IESG just wants the issue to go away.    It =
might
> happen for a significant architectural issue, perhaps, but not for an
> area-specific technical flaw.
>=20
> Here's the point: if an AD can't get at least one or two other ADs to
> read the document and agree to join in the blocking, then that AD MUST
> NOT be allowed to block the document.  That's even the case if the AD
> thinks she's found a serious flaw.  Because if, out of 14 others in
> the IESG, not ONE other is willing to read the document, understand
> the issue, and agree on it.
> =20
> That's also how I interpret the rules.  I just don't think that this =
is sufficient review.  I think that in practice it makes IESG =
more-or-less a rubber stamp for any issue that isn't easily fixed with =
small and often inconsequential changes to the document text.
> =20
> The problem is, the ADs are very busy people, and their expertise has =
to cover a wide range of topics, so there will be few IESG members who =
can really understand a subtle issue.   Document reviews outside of =
one's subject area are very difficult and require considerable focus.   =
GIven that, even if only one AD catches a flaw in a document, there's a =
good chance (though not a certainty of course) that it's something that =
warrants more attention.   It's far more likely that no ADs will find =
the flaw because nobody really took the time to read the document =
thoroughly and to understand its implications of the document outside of =
the narrow subject area of the working group.
> =20
> I understand (and agree with) the sentiment that, ultimately, one or =
two people shouldn't be able to block a document.  Nor do I want =
documents held up for trivialities as, unfortunately, sometimes happens. =
 But I've seen many cases where working groups failed to do an adequate =
level of review outside of their narrow areas of concern, and it appears =
that IESG's current rules and workload make it difficult for problems to =
get fixed after a document leaves the WG.  =20
> =20
> (and people keep arguing to remove steps from our process so that =
there will be even less review after a document has progressed to =
Proposed...)
> =20
> The only other formal level of review we have are the Last Call =
comments which, given the volume of documents that get Last Called, =
amounts to a fairly small and random chance that somebody outside the WG =
will happen to notice the proposed document action and give the document =
a thorough review.
> =20
> To put the question another way:  What level of formal technical =
review, outside of a WG, best serves IETF's goals?=20
> =20
> Keith
> =20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-48-94507830
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Thanks for that info. &nbsp;That does make me feel a bit =
better.<div><br></div><div>Keith</div><div><br><div><div>On Aug 15, =
2011, at 5:50 AM, Romascanu, Dan (Dan) wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; ">Hi Keith,<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; text-indent: =
-0.25in; "><span style=3D"font-family: Wingdings; "><span>=D8<span =
style=3D"font: normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
dir=3D"LTR"></span>The only other formal level of review we have are the =
Last Call comments which, given the volume of documents that get Last =
Called, amounts to a fairly small and random chance that somebody =
outside the WG will happen to notice the proposed document action and =
give the document a thorough review.<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0.5in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">I do not know =
whether to call these =91formal=92 but currently all documents that go =
to Last Call also undergo three expert reviews =96 Gen-ART, Sec-DIR and =
OPS-DIR. According to the scope of the documents a few more expert =
reviews may be called as required by the WG, shepherd or AD =96 =
APPS-Dir, TSV-Dir, MIB-Doctors, DNS-Dir, etc.<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0.5in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
">Regards,<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0.5in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">Dan<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"border-top-style: none; =
border-right-style: none; border-bottom-style: none; border-width: =
initial; border-color: initial; border-left-style: solid; =
border-left-color: blue; border-left-width: 1.5pt; padding-top: 0in; =
padding-right: 0in; padding-bottom: 0in; 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: 0in; =
padding-bottom: 0in; padding-left: 0in; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; =
">From:</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; "><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">ietf-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:ietf-bounces@ietf.org=
]<span class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Keith =
Moore<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Monday, August 15, 2011 =
4:02 AM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Barry =
Leiba<br><b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:adrian@olddog.co.uk" style=3D"color: blue; =
text-decoration: underline; ">adrian@olddog.co.uk</a>; =
IETF<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: IESG voting =
procedures<o:p></o:p></span></div></div></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">On Aug 14, 2011, at 8:40 =
PM, Barry Leiba wrote:<o:p></o:p></div></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; ">Convincing the entire IESG is a very high =
barrier, especially when<o:p></o:p></div></blockquote><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt; "><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">typically, =
most of the IESG just wants the issue to go away. &nbsp; &nbsp;It =
might<o:p></o:p></div></blockquote><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; ">happen for a significant architectural =
issue, perhaps, but not for an<o:p></o:p></div></blockquote><blockquote =
style=3D"margin-top: 5pt; margin-bottom: 5pt; "><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">area-specific =
technical flaw.<o:p></o:p></div></blockquote><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><br>Here's the =
point: if an AD can't get at least one or two other ADs to<br>read the =
document and agree to join in the blocking, then that AD MUST<br>NOT be =
allowed to block the document. &nbsp;That's even the case if the =
AD<br>thinks she's found a serious flaw. &nbsp;Because if, out of 14 =
others in<br>the IESG, not ONE other is willing to read the document, =
understand<br>the issue, and agree on =
it.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">That's also how I =
interpret the rules. &nbsp;I just don't think that this is sufficient =
review. &nbsp;I think that in practice it makes IESG more-or-less a =
rubber stamp for any issue that isn't easily fixed with small and often =
inconsequential changes to the document =
text.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">The problem is, the ADs =
are very busy people, and their expertise has to cover a wide range of =
topics, so there will be few IESG members who can really understand a =
subtle issue. &nbsp; Document reviews outside of one's subject area are =
very difficult and require considerable focus. &nbsp; GIven that, even =
if only one AD catches a flaw in a document, there's a good chance =
(though not a certainty of course) that it's something that warrants =
more attention. &nbsp; It's far more likely that<span =
class=3D"Apple-converted-space">&nbsp;</span><i>no</i><span =
class=3D"Apple-converted-space">&nbsp;</span>ADs will find the flaw =
because nobody really took the time to read the document thoroughly and =
to understand its implications of the document outside of the narrow =
subject area of the working group.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">I understand (and agree with) the sentiment that, =
ultimately, one or two people shouldn't be able to block a document. =
&nbsp;Nor do I want documents held up for trivialities as, =
unfortunately, sometimes happens. &nbsp;But I've seen many cases where =
working groups failed to do an adequate level of review outside of their =
narrow areas of concern, and it appears that IESG's current rules and =
workload make it difficult for problems to get fixed after a document =
leaves the WG. &nbsp;&nbsp;<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">(and people keep arguing to remove steps from our =
process so that there will be even less review after a document has =
progressed to Proposed...)<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">The only other formal level of review we have are the =
Last Call comments which, given the volume of documents that get Last =
Called, amounts to a fairly small and random chance that somebody =
outside the WG will happen to notice the proposed document action and =
give the document a thorough review.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">To put the question another way: &nbsp;What level of =
formal technical review, outside of a WG, best serves IETF's =
goals?&nbsp;<o:p></o:p></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
">Keith<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div></div></div>_______________________________=
________________<br>Ietf mailing list<br><a href=3D"mailto:Ietf@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">Ietf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/ietf</a><br></div></span></blockqu=
ote></div><br></div></body></html>=

--Apple-Mail-48-94507830--

From narten@us.ibm.com  Mon Aug 15 05:47:50 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44EDA21F8B3C for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 05:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.401
X-Spam-Level: 
X-Spam-Status: No, score=-106.401 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6UgZmKVLOin for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 05:47:49 -0700 (PDT)
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.143]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5FD21F886A for <ietf@ietf.org>; Mon, 15 Aug 2011 05:47:49 -0700 (PDT)
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by e3.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7FCONE4029530 for <ietf@ietf.org>; Mon, 15 Aug 2011 08:24:23 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7FCmXZT196620 for <ietf@ietf.org>; Mon, 15 Aug 2011 08:48:34 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7FCmXqK002107 for <ietf@ietf.org>; Mon, 15 Aug 2011 09:48:33 -0300
Received: from cichlid.raleigh.ibm.com (sig-9-65-235-172.mts.ibm.com [9.65.235.172]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7FCmWRx002080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Aug 2011 09:48:33 -0300
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7FCmQx6005336; Mon, 15 Aug 2011 08:48:31 -0400
Message-Id: <201108151248.p7FCmQx6005336@cichlid.raleigh.ibm.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: IESG voting procedures
In-reply-to: <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com> <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com>
Comments: In-reply-to Barry Leiba <barryleiba@computer.org> message dated "Sun, 14 Aug 2011 20:40:08 -0400."
Date: Mon, 15 Aug 2011 08:48:25 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: adrian@olddog.co.uk, Keith Moore <moore@network-heretics.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 12:47:50 -0000

+1.

One single AD should never be allowed to block a document for which
there appears to be community support. If a document really has
serious problems, it is the job of the AD to rally other ADs or other
impacted community members to oppose the document. Yes, this can be
more work for an AD, but that's what they get paid the big bucks for.

And if they can't do that, that really means the AD is an outlier and
needs to step aside, no matter how strongly they feel about a topic.

Thomas

Barry Leiba <barryleiba@computer.org> writes:

> > Convincing the entire IESG is a very high barrier, especially when
> > typically, most of the IESG just wants the issue to go away. Â  Â It might
> > happen for a significant architectural issue, perhaps, but not for an
> > area-specific technical flaw.

> Here's the point: if an AD can't get at least one or two other ADs to
> read the document and agree to join in the blocking, then that AD MUST
> NOT be allowed to block the document.  That's even the case if the AD
> thinks she's found a serious flaw.  Because if, out of 14 others in
> the IESG, not ONE other is willing to read the document, understand
> the issue, and agree on it.

> According to the current rules:

> 1. If ONE other AD places a second DISCUSS position OR enters a
> comment that supports the first AD's DISCUSS, the document stays
> blocked.  The "single discuss" procedure does NOT kick in.

> 2. If the WG still insists on pushing the document and the IESG goes
> into the "alternate ballot" (which should be "alternative ballot", but
> never mind that) procedure, the DISCUSSing AD still only needs TWO
> other ADs to read the document and vote "no".  Three "no" votes will
> maintain the block on the document.

> Really, if you can't get two out of fourteen technical leaders to
> agree with you, maybe you just have to accept that you're wrong.  If
> things get down to such a rarely used (read: never) last-ditch
> procedure, you can bet that essentially the entire IESG *will* read
> the document (you might miss one or two ADs at the most, *maybe*).  If
> it gets to that and you're *right* to block, you should be able to
> convince two of fourteen to support you.

> There is NO case in which it makes sense for a *single* person, with
> no peer support or agreement, to be allowed to block a document
> indefinitely, no matter HOW serious she THINKS the problem she's found
> is.

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

From narten@us.ibm.com  Mon Aug 15 05:52:04 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 925DF21F86AA for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 05:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.417
X-Spam-Level: 
X-Spam-Status: No, score=-106.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZdm4qPlZxOt for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 05:52:04 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id 03A3921F85F1 for <ietf@ietf.org>; Mon, 15 Aug 2011 05:52:03 -0700 (PDT)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7F5FNYv016027 for <ietf@ietf.org>; Sun, 14 Aug 2011 23:15:23 -0600
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7FCpKJO156822 for <ietf@ietf.org>; Mon, 15 Aug 2011 06:51:22 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7FCpJhA026425 for <ietf@ietf.org>; Mon, 15 Aug 2011 06:51:19 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-235-172.mts.ibm.com [9.65.235.172]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7FCpIdt026296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Aug 2011 06:51:19 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7FCpGcM005356; Mon, 15 Aug 2011 08:51:17 -0400
Message-Id: <201108151251.p7FCpGcM005356@cichlid.raleigh.ibm.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: IESG voting procedures
In-reply-to: <EDC652A26FB23C4EB6384A4584434A04037E1DFD@307622ANEX5.global.avaya.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com><6.2.5.6.2.20110728234859.075cb888@resistor.net><B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com><6.2.5.6.2.20110804043544.084eb5c0@resistor.net><420C8B2470E5AAC8A12E5740@192.168.1.128><01O4STOSKQ1600VHKR@mauve.mrochek.com><20110813204315.GA53261@verdi><B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com><E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com><951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com><4E483990.6030905@gmail.com><005c01cc5acb$05058310$0f108930$@olddog.co.uk><645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com><4E48629F.2070105@gmail.com><AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com><CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com> <EDC652A26FB23C4EB6384A4584434A04037E1DFD@307622ANEX5.global.avaya.com>
Comments: In-reply-to "Romascanu, Dan (Dan)" <dromasca@avaya.com> message dated "Mon, 15 Aug 2011 11:50:39 +0200."
Date: Mon, 15 Aug 2011 08:51:16 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: adrian@olddog.co.uk, Barry Leiba <barryleiba@computer.org>, Keith Moore <moore@network-heretics.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 12:52:04 -0000

"Romascanu, Dan (Dan)" <dromasca@avaya.com> writes:

> The only other formal level of review we have are the Last Call
> comments which, given the volume of documents that get Last Called,
> amounts to a fairly small and random chance that somebody outside
> the WG will happen to notice the proposed document action and give
> the document a thorough review.

ADs can and should arm twist impacted parties to review documents that
appear to be troubled and for which approval has troubling
implications.

If an AD can't rally the community (and more specifically parties that
will be forced to implement or deploy a technology) to oppose a
problematical document, that speaks volumes to the issue.

Thoma

From dromasca@avaya.com  Mon Aug 15 05:53:09 2011
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B1921F8B7F for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 05:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.421
X-Spam-Level: 
X-Spam-Status: No, score=-103.421 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIADLqwGDBpy for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 05:53:08 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 8663221F8B7B for <ietf@ietf.org>; Mon, 15 Aug 2011 05:53:08 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtEAABAWSU7GmAcF/2dsb2JhbABAmDaPTneBQAEBAQEDEh4KPwwEAgEIDQQEAQELBgwLAQYBRQkIAQEEEwgMDqAvAptKhWhfBJg8i00
X-IronPort-AV: E=Sophos;i="4.67,374,1309752000"; d="scan'208";a="297536641"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 15 Aug 2011 08:53:53 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 15 Aug 2011 08:50:24 -0400
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: IESG voting procedures
Date: Mon, 15 Aug 2011 14:53:51 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04037E1E63@307622ANEX5.global.avaya.com>
In-Reply-To: <201108151251.p7FCpGcM005356@cichlid.raleigh.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IESG voting procedures
Thread-Index: AcxbSglxJYn4nPWUQnWxQEei2qemggAABxsw
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com><6.2.5.6.2.20110728234859.075cb888@resistor.net><B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com><6.2.5.6.2.20110804043544.084eb5c0@resistor.net><420C8B2470E5AAC8A12E5740@192.168.1.128><01O4STOSKQ1600VHKR@mauve.mrochek.com><20110813204315.GA53261@verdi><B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com><E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com><951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com><4E483990.6030905@gmail.com><005c01cc5acb$05058310$0f108930$@olddog.co.uk><645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com><4E48629F.2070105@gmail.com><AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com><CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com> <EDC652A26FB23C4EB6384A4584434A04037E1DFD@307622ANEX5.global.avaya.com> <201108151251.p7FCpGcM005356@cichlid.raleigh.ibm.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Thomas Narten" <narten@us.ibm.com>
Cc: adrian@olddog.co.uk, Barry Leiba <barryleiba@computer.org>, Keith Moore <moore@network-heretics.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 12:53:09 -0000

Hi Thomas,

The paragraph below does not belong to me. In my message I was actually
answering it.=20

Regards,

Dan



> -----Original Message-----
> From: Thomas Narten [mailto:narten@us.ibm.com]
> Sent: Monday, August 15, 2011 3:51 PM
> To: Romascanu, Dan (Dan)
> Cc: Keith Moore; Barry Leiba; adrian@olddog.co.uk; IETF
> Subject: Re: IESG voting procedures
>=20
> "Romascanu, Dan (Dan)" <dromasca@avaya.com> writes:
>=20
> > The only other formal level of review we have are the Last Call
> > comments which, given the volume of documents that get Last Called,
> > amounts to a fairly small and random chance that somebody outside
> > the WG will happen to notice the proposed document action and give
> > the document a thorough review.
>=20
> ADs can and should arm twist impacted parties to review documents that
> appear to be troubled and for which approval has troubling
> implications.
>=20
> If an AD can't rally the community (and more specifically parties that
> will be forced to implement or deploy a technology) to oppose a
> problematical document, that speaks volumes to the issue.
>=20
> Thoma

From narten@us.ibm.com  Mon Aug 15 06:04:08 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 239A121F8BA0 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 06:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.431
X-Spam-Level: 
X-Spam-Status: No, score=-106.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0VGRrWf6AMY for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 06:04:07 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 9506F21F8B9E for <ietf@ietf.org>; Mon, 15 Aug 2011 06:04:07 -0700 (PDT)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7FCncrf026173 for <ietf@ietf.org>; Mon, 15 Aug 2011 06:49:38 -0600
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7FD40DC086880 for <ietf@ietf.org>; Mon, 15 Aug 2011 07:04:20 -0600
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 p7F73xsU024716 for <ietf@ietf.org>; Mon, 15 Aug 2011 01:03:59 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-235-172.mts.ibm.com [9.65.235.172]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7F73wF3024678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Aug 2011 01:03:59 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7FD3v8t005557; Mon, 15 Aug 2011 09:03:57 -0400
Message-Id: <201108151303.p7FD3v8t005557@cichlid.raleigh.ibm.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: IESG voting procedures
In-reply-to: <EDC652A26FB23C4EB6384A4584434A04037E1E63@307622ANEX5.global.avaya.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com><6.2.5.6.2.20110728234859.075cb888@resistor.net><B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com><6.2.5.6.2.20110804043544.084eb5c0@resistor.net><420C8B2470E5AAC8A12E5740@192.168.1.128><01O4STOSKQ1600VHKR@mauve.mrochek.com><20110813204315.GA53261@verdi><B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com><E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com><951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com><4E483990.6030905@gmail.com><005c01cc5acb$05058310$0f108930$@olddog.co.uk><645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com><4E48629F.2070105@gmail.com><AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com><CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com> <EDC652A26FB23C4EB6384A4584434A04037E1DFD@307622ANEX5.global.avaya.com> <201108151251.p7FCpGcM005356@cichlid.raleigh.ibm.com> <EDC652A26FB23C4EB6384A45! 84434A04037E1E63@307622ANEX5.global.avaya.com>
Comments: In-reply-to "Romascanu, Dan (Dan)" <dromasca@avaya.com> message dated "Mon, 15 Aug 2011 14:53:51 +0200."
Date: Mon, 15 Aug 2011 09:03:57 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: adrian@olddog.co.uk, Barry Leiba <barryleiba@computer.org>, Keith Moore <moore@network-heretics.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 13:04:08 -0000

> The paragraph below does not belong to me. In my message I was actually
> answering it.

Right. My mistake. It was Keith's comments I quoted.

Sorry 'bout that.

Thomas

"Romascanu, Dan (Dan)" <dromasca@avaya.com> writes:

> Hi Thomas,

> The paragraph below does not belong to me. In my message I was actually
> answering it. 

> Regards,

> Dan



> > -----Original Message-----
> > From: Thomas Narten [mailto:narten@us.ibm.com]
> > Sent: Monday, August 15, 2011 3:51 PM
> > To: Romascanu, Dan (Dan)
> > Cc: Keith Moore; Barry Leiba; adrian@olddog.co.uk; IETF
> > Subject: Re: IESG voting procedures
> > 
> > "Romascanu, Dan (Dan)" <dromasca@avaya.com> writes:
> > 
> > > The only other formal level of review we have are the Last Call
> > > comments which, given the volume of documents that get Last Called,
> > > amounts to a fairly small and random chance that somebody outside
> > > the WG will happen to notice the proposed document action and give
> > > the document a thorough review.
> > 
> > ADs can and should arm twist impacted parties to review documents that
> > appear to be troubled and for which approval has troubling
> > implications.
> > 
> > If an AD can't rally the community (and more specifically parties that
> > will be forced to implement or deploy a technology) to oppose a
> > problematical document, that speaks volumes to the issue.
> > 
> > Thoma
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From sm@elandsys.com  Fri Aug 12 13:16:26 2011
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7E2E21F88A1 for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 13:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.67
X-Spam-Level: 
X-Spam-Status: No, score=-102.67 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzsmoHmJ-YtW for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2011 13:16:24 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by ietfa.amsl.com (Postfix) with ESMTP id 437B3228309 for <ietf@ietf.org>; Fri, 12 Aug 2011 13:16:24 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.234.186]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p7CKGsq4012528; Fri, 12 Aug 2011 13:16:59 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1313180221; bh=ewpDageVQOt6cW9wlc2f3g5UEqQ=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=aUnQRGEdrCzr4EYpPhbwWu1OTZh8t7baxiJtdGe8CpoyUyKfm1uVDPLUcRqnit8ic ANKtE37IotJrI5gXlrYBrPiVHh3BGCFdRLoqoL5J3+VkQxF6KY6oYHm6fnq4Dq1OSI RNEDAzAhea/64pma3BS000EKUqCouGZ/nI1Miq/g=
Message-Id: <6.2.5.6.2.20110812124902.098db130@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 12 Aug 2011 13:12:32 -0700
To: mrex@sap.com
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission
In-Reply-To: <201108121902.p7CJ2abf001229@fs4113.wdf.sap.corp>
References: <201108121902.p7CJ2abf001229@fs4113.wdf.sap.corp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 15 Aug 2011 07:28:12 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 20:16:27 -0000

Hi Martin,
At 12:02 12-08-2011, Martin Rex wrote:
>I'm wondering wheter there should be an informative reference to rfc6186.

That suggestion came up during the working group discussion but it 
was not retained as there wasn't any implementation report for RFC 
6186.  The editors of draft-ietf-yam-rfc4409bis-02 commented [1][2] 
about having an informative reference to RFC 6186.

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/yam/current/msg00684.html
2. http://www.ietf.org/mail-archive/web/yam/current/msg00696.html  


From ben@nostrum.com  Fri Aug 12 14:26:45 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 039F721F8802; Fri, 12 Aug 2011 14:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.438
X-Spam-Level: 
X-Spam-Status: No, score=-102.438 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kzeGOn9hbLvU; Fri, 12 Aug 2011 14:26:44 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE1121F877F; Fri, 12 Aug 2011 14:26:36 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p7CLRDnS043155 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 12 Aug 2011 16:27:14 -0500 (CDT) (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-mpls-rsvp-te-no-php-oob-mapping-08
Date: Fri, 12 Aug 2011 16:27:12 -0500
Message-Id: <37428C36-C58A-4848-80E1-8B2FA892FA9B@nostrum.com>
To: draft-ietf-mpls-rsvp-te-no-php-oob-mapping.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 15 Aug 2011 07:28:12 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 21:26:45 -0000

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

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

Document: draft-ietf-mpls-rsvp-te-no-php-oob-mapping
Reviewer: Ben Campbell
Review Date: 2011-08-12
IETF LC End Date: 2011-08-12

Summary: This document is almost ready for publication as a proposed =
standard. There are a few editorial issues and nits that should be =
considered prior to publication.


Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- Please proofread for missing articles (i.e. a, an, the)

-- idnits reports some issues, please check.

-- section 1:

It would be helpful to include an explicit definition of " =
non-Penultimate Hop Popping behavior" somewhere in the introduction.

-- section 1, paragraph 2: "P2MP"

Please expand on first mention. I see you did in the abstract, but it =
should be redone in the body.

-- section 2.2, last paragraph: "w.r.t."

Please spell out

-- section 3: First paragraph: " Addition of "non-PHP behavior" adds a =
variable of attacks on the label assigned by the Egress node. "

Is "variable" the correct word?

-- IANA Considerations:

Please include the explicit names of the registry to be changed.

-- 6.1, "[RFC 2119]"

The space between RFC and 2119 confused idnits, and may confuse other =
tools.

-- 6.1, [RFC5920]

This is an informational draft. Does the reference need to be normative?

-- general:

I am unable to read the title without thinking of this: =
http://en.wikipedia.org/wiki/Hop_on_Pop  :-)=

From hartmans@mit.edu  Mon Aug 15 10:25:33 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDBBB21F8CAB; Mon, 15 Aug 2011 10:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.899
X-Spam-Level: 
X-Spam-Status: No, score=-103.899 tagged_above=-999 required=5 tests=[AWL=-1.634, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t58oAqMT3bPq; Mon, 15 Aug 2011 10:25:32 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id F06C621F8C9E; Mon, 15 Aug 2011 10:25:31 -0700 (PDT)
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 1BF3D2014E; Mon, 15 Aug 2011 13:28:43 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6355742B7; Mon, 15 Aug 2011 13:25:58 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt> (Supporting Authentication Trailer for OSPFv3) to Proposed Standard
References: <20110719145739.5942.53564.idtracker@ietfa.amsl.com>
Date: Mon, 15 Aug 2011 13:25:58 -0400
In-Reply-To: <20110719145739.5942.53564.idtracker@ietfa.amsl.com> (The IESG's message of "Tue, 19 Jul 2011 07:57:39 -0700")
Message-ID: <tsl7h6ed1sp.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: ospf@ietf.org, karp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 17:25:33 -0000

Hi. I've reviewed the draft-ietf-ospf-auth-trailer-ospfv3-05 for
consistency with draft-ietf-karp-ospf-analysis.  KARP is chartered to
figure out what improvements we need in routing protocol
authenticationq. While draft-ietf-karp-ospf-analysis has not been
approved by the WG, I think it's fairly close to our current thinking on
what needs to be done to OSPF authentication.  I believe we should
either be consistent with that thinking or  if during the discussion we
discover that what we're doing in KARP is incorrect decide to update the
KARP document.

Based on this review I have a few recommendations for the OSPF v3
authentication trailers document.

1) The v3 authentication trailer takes a step back in the ability to
rekey security associations both from OSPF v2, from IPsec for OSPF v3
and from draft-ietf-karp-crypto-tables. At the top of page 231 of RFC
2328, OSPF v2 security associations are defined with four lifetimes:
KeyStartGenerate, KeyStartAccept, KeyStopGenerate and
KeyStopAccept. Similarly, RFC 4301 defines a lifetime value for the SAs
used by OSPFv3; in that case, whether an SA is an outbound or inbound SA
controls whether it can be used for reception, generation or both at the
current time. In the KARP crypto tables, lifetimes related to when
packets can be sent are included: SAs are deleted from the crypto table
to prevent reception. However the V3 auth trailer draft leaves this all
up to implementation defined behavior.
draft-ietf-karp-ospf-analysis indicates that we're going to remind
people of the existing OSPF requirements for keylifetimes because they
are necessary for key rollover.

I believe that draft-ietf-ospf-auth-trailer-ospfv3-05 needs to be
revised to require implementation behavior at least as flexible as
draft-ietf-karp-crypto-tables. That is, associated with each security
association is a time for when sending packets can start with a given SA
and for when it must stop. Infinity and 0 should of course be supported
for the appropriate times.

2) I notice terminology inconsistency between key identifier  and
security association identifier. This should probably be cleaned up,
although it's not that big of a deal.


3) draft-ietf-ospf-analysis says that we are going to solve related
protocol attacks. That is, we recognize that it's quite likely that some
people will use the same preshared key both for OSPF authentication and
for something else. We need to mix something into the key or hash or
something that is unlikely to appear in any other use in order to make
it cryptographically unlikely for the resulting OSPF authentication hash
to be a hash useful in some other protocol or for the hash from some
other protocol to be useful in OSPF.  This draft does not do that.  One
possible way to solve this would be to prepend a constant in front of
the key in the key preparation step or a constant in front of every
packet that gets hashed. The constant should be the same for OSPFv3 and
not used for any other purpose.


From housley@vigilsec.com  Mon Aug 15 11:17:51 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC4B21F8C07 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 11:17:51 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WisZ-GoK6hPF for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 11:17:50 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A39E021F8B95 for <ietf@ietf.org>; Mon, 15 Aug 2011 11:17:50 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 918ECF24138; Mon, 15 Aug 2011 14:18:38 -0400 (EDT)
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 s1Q3YmDPJsnk; Mon, 15 Aug 2011 14:18:35 -0400 (EDT)
Received: from [192.168.2.101] (pool-96-241-176-45.washdc.fios.verizon.net [96.241.176.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 19E1BF24042; Mon, 15 Aug 2011 14:18:38 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com>
Date: Mon, 15 Aug 2011 14:18:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B49DFF6-B16D-42A9-A9A6-33A8BECF9CDD@vigilsec.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110728234859.075cb888@resistor.net>	<B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com>	<6.2.5.6.2.20110804043544.084eb5c0@resistor.net>	<420C8B2470E5AAC8A12E5740@[192.168.1.128]>	<01O4STOSKQ1600VHKR@mauve.mrochek.com>	<20110813204315.GA53261@verdi>	<B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com>	<E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com>	<951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 18:17:51 -0000

>> And I think in that case, there is
>> no way that one or two ADs should be able to block something
>> because they don't like it, *unless* they can convince the rest
>> of the IESG that the document is harmful.
>=20
> Convincing the entire IESG is a very high barrier, especially when =
typically, most of the IESG just wants the issue to go away.    It might =
happen for a significant architectural issue, perhaps, but not for an =
area-specific technical flaw.=20

The current procedures do not require the AD that has found the flaw to =
convince the whole IESG that it is a flaw.  One other AD is sufficient,

Russ=

From housley@vigilsec.com  Mon Aug 15 11:27:34 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C55921F8C92 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 11:27:34 -0700 (PDT)
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.002, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xgYTZA3QV4HE for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 11:27:33 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 6E35721F8C7B for <ietf@ietf.org>; Mon, 15 Aug 2011 11:27:33 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id A7D20F24140; Mon, 15 Aug 2011 14:28:26 -0400 (EDT)
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 RVefxMGX0I90; Mon, 15 Aug 2011 14:28:19 -0400 (EDT)
Received: from [192.168.2.101] (pool-96-241-176-45.washdc.fios.verizon.net [96.241.176.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1A07DF24042; Mon, 15 Aug 2011 14:28:26 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-17-118249544
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com>
Date: Mon, 15 Aug 2011 14:28:18 -0400
Message-Id: <D62D41A3-C21A-4134-8AEB-7E96819A652A@vigilsec.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com> <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 18:27:34 -0000

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

Keith:

>>> Convincing the entire IESG is a very high barrier, especially when
>>> typically, most of the IESG just wants the issue to go away.    It =
might
>>> happen for a significant architectural issue, perhaps, but not for =
an
>>> area-specific technical flaw.
>>=20
>> Here's the point: if an AD can't get at least one or two other ADs to
>> read the document and agree to join in the blocking, then that AD =
MUST
>> NOT be allowed to block the document.  That's even the case if the AD
>> thinks she's found a serious flaw.  Because if, out of 14 others in
>> the IESG, not ONE other is willing to read the document, understand
>> the issue, and agree on it.
>=20
> That's also how I interpret the rules.  I just don't think that this =
is sufficient review.  I think that in practice it makes IESG =
more-or-less a rubber stamp for any issue that isn't easily fixed with =
small and often inconsequential changes to the document text.
>=20
> The problem is, the ADs are very busy people, and their expertise has =
to cover a wide range of topics, so there will be few IESG members who =
can really understand a subtle issue.   Document reviews outside of =
one's subject area are very difficult and require considerable focus.   =
GIven that, even if only one AD catches a flaw in a document, there's a =
good chance (though not a certainty of course) that it's something that =
warrants more attention.   It's far more likely that no ADs will find =
the flaw because nobody really took the time to read the document =
thoroughly and to understand its implications of the document outside of =
the narrow subject area of the working group.
>=20
> I understand (and agree with) the sentiment that, ultimately, one or =
two people shouldn't be able to block a document.  Nor do I want =
documents held up for trivialities as, unfortunately, sometimes happens. =
 But I've seen many cases where working groups failed to do an adequate =
level of review outside of their narrow areas of concern, and it appears =
that IESG's current rules and workload make it difficult for problems to =
get fixed after a document leaves the WG.  =20

My experience is that a technical flaw, even if it is a corner case, is =
acted upon by the WG.  There are rare cases where the WG has lost =
energy, but in general the WG wants to produce a quality output.  As a =
result, technical flaws are not the place where things get messy.  =
Rather, things get messy over issues that have a political component.

Russ


--Apple-Mail-17-118249544
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>Keith:</div><div><br></div><div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">Convincing the entire IESG =
is a very high barrier, especially when<br></blockquote><blockquote =
type=3D"cite">typically, most of the IESG just wants the issue to go =
away. &nbsp; &nbsp;It might<br></blockquote><blockquote =
type=3D"cite">happen for a significant architectural issue, perhaps, but =
not for an<br></blockquote><blockquote type=3D"cite">area-specific =
technical flaw.<br></blockquote><br>Here's the point: if an AD can't get =
at least one or two other ADs to<br>read the document and agree to join =
in the blocking, then that AD MUST<br>NOT be allowed to block the =
document. &nbsp;That's even the case if the AD<br>thinks she's found a =
serious flaw. &nbsp;Because if, out of 14 others in<br>the IESG, not ONE =
other is willing to read the document, understand<br>the issue, and =
agree on it.<br></div></blockquote><div><br></div>That's also how I =
interpret the rules. &nbsp;I just don't think that this is sufficient =
review. &nbsp;I think that in practice it makes IESG more-or-less a =
rubber stamp for any issue that isn't easily fixed with small and often =
inconsequential changes to the document =
text.</div><div><br></div><div>The problem is, the ADs are very busy =
people, and their expertise has to cover a wide range of topics, so =
there will be few IESG members who can really understand a subtle issue. =
&nbsp; Document reviews outside of one's subject area are very difficult =
and require considerable focus. &nbsp; GIven that, even if only one AD =
catches a flaw in a document, there's a good chance (though not a =
certainty of course) that it's something that warrants more attention. =
&nbsp; It's far more likely that <i>no</i> ADs will find the flaw =
because nobody really took the time to read the document thoroughly and =
to understand its implications of the document outside of the narrow =
subject area of the working group.</div><div><br></div><div>I understand =
(and agree with) the sentiment that, ultimately, one or two people =
shouldn't be able to block a document. &nbsp;Nor do I want documents =
held up for trivialities as, unfortunately, sometimes happens. &nbsp;But =
I've seen many cases where working groups failed to do an adequate level =
of review outside of their narrow areas of concern, and it appears that =
IESG's current rules and workload make it difficult for problems to get =
fixed after a document leaves the WG. =
&nbsp;&nbsp;</div></div></blockquote><br></div><div>My experience is =
that a technical flaw, even if it is a corner case, is acted upon by the =
WG. &nbsp;There are rare cases where the WG has lost energy, but in =
general the WG wants to produce a quality output. &nbsp;As a result, =
technical flaws are not the place where things get messy. &nbsp;Rather, =
things get messy over issues that have a political =
component.</div><div><br></div><div>Russ</div><br></body></html>=

--Apple-Mail-17-118249544--

From moore@network-heretics.com  Mon Aug 15 11:34:04 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9AF921F8C83 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 11:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.142,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbiMRLBcneQM for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 11:34:04 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id DD15521F8C82 for <ietf@ietf.org>; Mon, 15 Aug 2011 11:34:03 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 05FED22051; Mon, 15 Aug 2011 14:34:50 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 15 Aug 2011 14:34:50 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Hog g4XOHcFJxTMLapIiWND/q3d4=; b=g+UPeJH5JDR8kDXQNV4Q5yfLdA5O6P7Y3v2 FBk/Sv20Rf+iiQulpYKqFCmAOoL2ToVFSQGDnv5rqN+2WcVEVKnnqkv02RbrQ1LS bYWv4ZAuKxSfMbJG6PwAIQ21rXP+fjlPTAhInZKLSHVPt+Czn8Ig3X26lew/tYTz EDys3frE=
X-Sasl-enc: 8F02smRcPWZj2wA5YXKWGNSZI75gX0c7hsKQMF/uXzg2 1313433289
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 093A945ED57; Mon, 15 Aug 2011 14:34:48 -0400 (EDT)
Subject: Re: IESG voting procedures
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-118625566
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <D62D41A3-C21A-4134-8AEB-7E96819A652A@vigilsec.com>
Date: Mon, 15 Aug 2011 14:34:34 -0400
Message-Id: <B8EF923D-A447-4A5A-9BF5-672747749779@network-heretics.com>
References: <20110728020207.26024.73829.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110728234859.075cb888@resistor.net> <B924D1E7-42A0-44BC-8A0B-D1DB740DC188@vigilsec.com> <6.2.5.6.2.20110804043544.084eb5c0@resistor.net> <420C8B2470E5AAC8A12E5740@192.168.1.128> <01O4STOSKQ1600VHKR@mauve.mrochek.com> <20110813204315.GA53261@verdi> <B0F9FB32-2E0B-4C86-BB03-2F07D1440C3F@network-heretics.com> <E9D4ACEB-AAFA-4DDB-802E-8AD7835671D5@vigilsec.com> <951B4AD9-1021-40CB-83D1-51A5BC8C2DE9@network-heretics.com> <4E483990.6030905@gmail.com> <005c01cc5acb$05058310$0f108930$@olddog.co.uk> <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> <4E48629F.2070105@gmail.com> <AEE84035-B12A-4E60-A2E8-EA926DC3C4C8@network-heretics.com> <CAC4RtVBHAz_Wn-EG=qx+BgvvJC_3f8YxAZ2vtA+aF5B4AT8=+g@mail.gmail.com> <60B4A8FD-42CF-4B1C-A33A-4EDEE63E1F7C@network-heretics.com> <D62D41A3-C21A-4134-8AEB-7E96819A652A@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 18:34:04 -0000

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

On Aug 15, 2011, at 2:28 PM, Russ Housley wrote:

> My experience is that a technical flaw, even if it is a corner case, =
is acted upon by the WG.  There are rare cases where the WG has lost =
energy, but in general the WG wants to produce a quality output.  As a =
result, technical flaws are not the place where things get messy.  =
Rather, things get messy over issues that have a political component.

What's the difference between "issues that have a political component" =
and disagreements about whether there is a technical flaw?   Seems to me =
that people who don't want to admit that there's a technical flaw (or =
who can't easily see it from their perspective) often dismiss the issue =
as a political problem.

Keith


--Apple-Mail-1-118625566
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><div>On Aug 15, 2011, at 2:28 PM, Russ Housley wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>My =
experience is that a technical flaw, even if it is a corner case, is =
acted upon by the WG. &nbsp;There are rare cases where the WG has lost =
energy, but in general the WG wants to produce a quality output. =
&nbsp;As a result, technical flaws are not the place where things get =
messy. &nbsp;Rather, things get messy over issues that have a political =
component.</div></span></blockquote><br></div><div>What's the difference =
between "issues that have a political component" and disagreements about =
whether there is a technical flaw? &nbsp; Seems to me that people who =
don't want to admit that there's a technical flaw (or who can't easily =
see it from their perspective) often dismiss the issue as a political =
problem.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-1-118625566--

From spencer@wonderhamster.org  Mon Aug 15 15:39:49 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF2F321F8C89 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 15:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.341
X-Spam-Level: 
X-Spam-Status: No, score=-101.341 tagged_above=-999 required=5 tests=[AWL=-0.602, BAYES_20=-0.74, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6+TuysuY+k4W for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 15:39:48 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id C7CB021F8C75 for <ietf@ietf.org>; Mon, 15 Aug 2011 15:39:48 -0700 (PDT)
Received: from S73602b ([50.58.7.243]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MLv7s-1QwQI84A4S-008Xzs; Mon, 15 Aug 2011 18:40:34 -0400
Message-ID: <4827963E94554ED9A4D510E0F3C29EB8@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: <ietf@ietf.org>
References: <20110811222013.3869.45041.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-eggert-successful-bar-bof-05.txt> (Considerationsfor Having a Successful "Bar BOF" Side Meeting) to Informational RFC
Date: Mon, 15 Aug 2011 17:40:31 -0500
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.6109
X-Provags-ID: V02:K0:DJrPSbtITXKUWmoA9/kLfv0g/aqPyytu65klKowUL7D Ol/JvhcyecVxZPfjoLfvqVF1dXC9wiToPX6hU7UqGoR++ABr7F raaG4EkxhVM5jgf7YOOKAxM8ahCbC+tfEnSYJbJVQ+XCfIT3Bo v7++Cqq7ZA+bFcJn0QIIENGILv5x6PTj+gR0vgLl+NdPLpPGt8 BgXRqYODH64/s4P3XSkv6YZ5vqquW5gVrOXUxkerUQ=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 22:39:49 -0000

I have been looking at various revisions of this draft since -00. I'm glad 
Lars did the first version during IETF 77, and I'm glad that Lars and 
Gonzalo kept working on it.

I think it's important guidance for the community. I think it's on the right 
track. I think it could reasonably be published in its current form.

I have some suggestions.

Frivolous: I TOTALLY get the "don't call it a Bar BOF" thing. I've also seen 
the confusion that results from any sentence that includes the words "Bar 
BOF", and it might even be worth pointing out that even IESG members and IAB 
members drop the "Bar" in conversations from time to time, especially during 
IETF week, resulting in even more confusion. "Side Meeting" could work, but 
it covers a lot more than the kind of "pre-charter planning meetings" you 
guys are talking about for most of the document, and you have access to a 
community of thousands of creative people - could you think of a better 
name? If the search space you're dealing with requires references to 
alcohol, just ask Hadriel Kaplan for a suggestion. He came up with MARTINI 
... :D

More seriously: We're now more than two years into the implementation of the 
RAI DISPATCH process, and RAI DISPATCH has a lot to do with "bringing new 
proposals" into RAI. It seems odd that there's no guidance specific to RAI 
DISPATCH, especially because the current revision also talks about working 
group "ad hoc" meetings, which RAI DISPATCH often uses. It might be helpful 
to mention something about the RAI DISPATCH process - either in this 
document, or in another that deals specifically with working group "ad hoc" 
meetings. And, actually, the discussion of working group "ad hoc" meetings 
seems to have parachuted into the last paragraph of Section 2, with little 
in the title or abstract that would lead anyone to suspect that it might be 
hiding there ... so maybe moving it to its own, very small, document would 
be helpful.

Minor suggestions:

In Section 2, there's a discussion of "tourists". It might be helpful to 
distinguish between the times when you WANT "tourists" - when you're asking 
the entire IETF community for input - and the times when you DON'T - when 
you're trying to wordsmith a charter, etc. The text describes the second 
case nicely; I'm just suggesting that you you include a sentence on the 
first case, and say "you need to hear from the entire community at the right 
time, but your side meeting probably isn't the right time".

Also in Section 2, where you give the "don't count bodies" warning, you 
might also add that people come to meetings about proposals for new work 
just to make sure that the proposal isn't going off-track in ways they care 
about - and if it's not, that's fine, they aren't interested in DOING the 
work, so they disappear. So the area directors know not to count them as 
"interested", too.

Somewhere in Section 2, it would be worth noting that collecting large 
groups of people in "side meetings" tends to result in larger proposed 
working group charters, which makes it harder to get chartered. The IESG has 
not had a problem with charters that were too limited in scope coming out of 
side meetings, at least not since I joined the IAB ...

Section 3 contains this text:

   Many routinely say "yes" to every
   incoming request as long as there are meeting rooms available (and
   there are typically lots of meeting rooms available).

I'm betting that the parenthetical should be "available, outside of normal 
working group meeting slots".

Section 3 contains a sad tail of woe about an area director being trapped in 
a hotel for a few days during IETF 77, but I'm thinking area directors are 
going to be trapped in hotels for a few days during IETF weeks, whether 
there are side meetings scheduled during meals or not.

There might be a few points conflated here - (1) my understanding is that 
most area directors are trying to dodge "side meetings", because the very 
presence of an area director signals "gee, Gonzalo came, he must be 
interested, and if he's interested, he'll approve us as a working group 
soon!" - if the area directors ARE dodging side meetings, you might say 
that, so everyone has realistic expectations; (2) "if you schedule a side 
meeting during a meal break, everyone there will be missing a meal unless 
you go to a restaurant like we told you", and (3) "if you schedule a side 
meeting that looks like a BOF during a meal break, you won't fit into most 
restaurants, so have a small side meeting and go to a restaurant like we 
told you" :-)

In Section 4, when you're describing the problems of holding side meetings 
that are indistinguishable from IETF working group meetings, you might 
include the point that we've seen situations where people think the work has 
already been chartered, even making press announcements about that. No one 
makes the same mistake when you meet in a restaurant!

Also in Section 4, where you say

   Finally, some organizers may find
   the process to apply for an official BOF too complex, and so decide
   to simply mimic one.

I don't think complexity has anything to do with it - some people request a 
BOF, get turned down, request an IETF working group meeting-style "side 
meeting", and have the same meeting they had been planning with the same 
agenda they had put toether in the same room where the BOF would have been 
held. I think it's worth saying that ...

In Section 6 on IPR, it might be useful to point out that these side 
meetings are building support for your proposal, and the right time to tell 
your potential supporters about IPR is NOT after they support you and the 
working group has been chartered ... it's great to observe the rules, but 
it's even better if you know that not observing the rules *fails*.

Also in Section 6, this text doesn't parse for me:

   Informally, the above makes it appropriate, in order to provide a
   pointer to the relevant policies, to announce the "Note Well" text
   [NOTEWELL] in all such meetings.

and I think the problem is that I don't understand what "Informally" means 
in this context. 


From hartmans@mit.edu  Mon Aug 15 16:46:19 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB7711E80F7 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 16:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.881
X-Spam-Level: 
X-Spam-Status: No, score=-103.881 tagged_above=-999 required=5 tests=[AWL=-1.616, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3G0bYSl5rJB7 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 16:46:19 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 378FB11E80EB for <ietf@ietf.org>; Mon, 15 Aug 2011 16:46:18 -0700 (PDT)
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 ED9C8203A2; Mon, 15 Aug 2011 19:49:26 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 04AA142B7; Mon, 15 Aug 2011 19:46:42 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org
Subject: Re: [Ietf-krb-wg] Last Call: <draft-ietf-krb-wg-otp-preauth-18.txt> (OTP Pre-authentication) to Proposed Standard
References: <20110815145220.16779.50055.idtracker@ietfa.amsl.com>
Date: Mon, 15 Aug 2011 19:46:41 -0400
In-Reply-To: <20110815145220.16779.50055.idtracker@ietfa.amsl.com> (The IESG's message of "Mon, 15 Aug 2011 07:52:20 -0700")
Message-ID: <tslobzq9r1a.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-krb-wg@anl.gov
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 23:46:19 -0000

Hi.
Just around the time  that this document was sent to the IESG, a
discussion started surrounding the nonce text in this draft in the
Kerberos working group.
All the participants seemed to agree that the discussion was
non-blocking: if consensus on a change was not found before ietf last
call  ended, then the existing text would stand.
So, I did not ask our AD to block the draft.

However, the Kerberos working group did reach a consensus on new text.
We'd like to propose to the IETF that

The text in section 4.1 is changed from:
        
        This nonce string MUST be as long as the longest key length of
        the symmetric key types that the KDC supports and MUST be chosen
        randomly.

to

        This nonce string MUST contain a randomly chosen component at
        least as long as the armor key length.


The KDC can then compose a nonce out of a random component and a
timestamp.



This change has already reached consensus within the working group. If
there are no objections (especially including objections from our AD)
I'll ask the authors to make this change. If there are objections then
our AD will judge consensus as usual.

Sam hartman
Kerberos Co-chair

From stephen.farrell@cs.tcd.ie  Mon Aug 15 16:54:19 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE4421F8CCF for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 16:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpiATMHjkuj4 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 16:54:18 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4DA21F8CCD for <ietf@ietf.org>; Mon, 15 Aug 2011 16:54:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 1F276171CC3; Tue, 16 Aug 2011 00:54:57 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1313452495; bh=MOOHYO16NpzH9q TvOJfqbbLX9uwV5R4dDpvbwPVepGc=; b=mJ1iSUdt4m0UpHQ64f1DyRGmT6XL3o xwqLS6xxayW8IWacEEaZdpLztnrXGJbQx5FNESKctjge3hTGPmrXVgGrGB2ySGmA z7hvaxPKm+FQ/N/yvl68W2tiVwUVefT7WU5pEkL7v81I140oh+b8RXi0+B9LGtX7 ECFy0jORcbKvFOCgjyrmZdfKRpe+EWdwLJpblXH96MS5FzmhLpmLHyuqM87fsDpB f3DOma4vlbqmFGZZEZo9NKQNAqOgpFHQQfFVIgaXi/xa9LNtWTEw6ZE5GPxVjniC AtVynF1x+lwpUBpgq9Z+0qYVJjVSckVGyyMtoX8xJrJSsUFXEnSEdUWQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 3kl0S51LuqhX; Tue, 16 Aug 2011 00:54:55 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.46.24.115]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A9619171CC2; Tue, 16 Aug 2011 00:54:53 +0100 (IST)
Message-ID: <4E49B1CD.2070507@cs.tcd.ie>
Date: Tue, 16 Aug 2011 00:54:53 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [Ietf-krb-wg] Last Call: <draft-ietf-krb-wg-otp-preauth-18.txt> (OTP Pre-authentication) to Proposed Standard
References: <20110815145220.16779.50055.idtracker@ietfa.amsl.com> <tslobzq9r1a.fsf@mit.edu>
In-Reply-To: <tslobzq9r1a.fsf@mit.edu>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf-krb-wg@anl.gov, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 23:54:19 -0000

Hi Sam,

No problem here. Seems sensible either way to me and a little
better with the new text if that's what the WG prefer. I'd say
make the change when processing any other IETF LC comments.

S.

On 16/08/11 00:46, Sam Hartman wrote:
> Hi.
> Just around the time  that this document was sent to the IESG, a
> discussion started surrounding the nonce text in this draft in the
> Kerberos working group.
> All the participants seemed to agree that the discussion was
> non-blocking: if consensus on a change was not found before ietf last
> call  ended, then the existing text would stand.
> So, I did not ask our AD to block the draft.
> 
> However, the Kerberos working group did reach a consensus on new text.
> We'd like to propose to the IETF that
> 
> The text in section 4.1 is changed from:
>         
>         This nonce string MUST be as long as the longest key length of
>         the symmetric key types that the KDC supports and MUST be chosen
>         randomly.
> 
> to
> 
>         This nonce string MUST contain a randomly chosen component at
>         least as long as the armor key length.
> 
> 
> The KDC can then compose a nonce out of a random component and a
> timestamp.
> 
> 
> 
> This change has already reached consensus within the working group. If
> there are no objections (especially including objections from our AD)
> I'll ask the authors to make this change. If there are objections then
> our AD will judge consensus as usual.
> 
> Sam hartman
> Kerberos Co-chair
> _______________________________________________
> ietf-krb-wg mailing list
> ietf-krb-wg@lists.anl.gov
> https://lists.anl.gov/mailman/listinfo/ietf-krb-wg
> 

From mary.ietf.barnes@gmail.com  Mon Aug 15 17:52:46 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9349421F8A7B for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 17:52:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.097
X-Spam-Level: 
X-Spam-Status: No, score=-104.097 tagged_above=-999 required=5 tests=[AWL=0.900, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  J_CHICKENPOX_56=0.6, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SUg-5rnvaJMM for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 17:52:42 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E921121F8A70 for <ietf@ietf.org>; Mon, 15 Aug 2011 17:52:41 -0700 (PDT)
Received: by vxi29 with SMTP id 29so5369760vxi.31 for <ietf@ietf.org>; Mon, 15 Aug 2011 17:53:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d3oO3hzVvoF57NbJ+6lAmUEykdk9aQk1DUvZGvfmkCk=; b=cHM+TFGvvQJK6pWiXLq3Xzizi7oFz7hqxREAb29vWHHh/cBh8y8yi6Q4v8DlDUr4cq peMZQ/9Mzy1rTfClIw6mnu0BJ4A9fAjefkxcRau3ZBPMMXS8dYAthSQiA4v+AILfWM+C GUROITXBpUu8r5uP5QdHSI7fIaMB521WPFMpI=
MIME-Version: 1.0
Received: by 10.52.173.208 with SMTP id bm16mr4308210vdc.49.1313456008501; Mon, 15 Aug 2011 17:53:28 -0700 (PDT)
Received: by 10.52.160.71 with HTTP; Mon, 15 Aug 2011 17:53:28 -0700 (PDT)
In-Reply-To: <6D9C4F6D-53B4-4F77-AB4E-45A4BA911406@cisco.com>
References: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com> <6D9C4F6D-53B4-4F77-AB4E-45A4BA911406@cisco.com>
Date: Mon, 15 Aug 2011 19:53:28 -0500
Message-ID: <CAHBDyN5MY1AXxN+kv5gjdYXArhimogZfC9sVojE+RTSYbpKzxA@mail.gmail.com>
Subject: Re: Gen-ART Review: Last Call <draft-ietf-p2psip-base-17.txt>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec5196dddd09a9d04aa94cec1
Cc: IETF-Discussion list <ietf@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 00:52:46 -0000

--bcaec5196dddd09a9d04aa94cec1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Cullen,

Responses inline below [MB].

Mary.

On Thu, Aug 11, 2011 at 7:43 PM, Cullen Jennings <fluffy@cisco.com> wrote:

>
> Thanks for the detailed review - you caught some good stuff. Most of this
> makes essence but we should probably talk about usage of 2119 language.
>
> On Aug 9, 2011, at 16:05 , Mary Barnes wrote:
> > simple
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > Document: draft-ietf-p2psip-base-17
> > Reviewer:  Mary Barnes
> > Review Date:  9 August  2011
> > IETF LC End Date: 22 July 2011
> >
> > Summary: Not Ready.
> >
> > Comments:
> > ----------------
> > The document is very a dense (with detailed technical information) and
> long (150 page) specification for a Peer-to-peer signaling protocol.  Whi=
le
> the overall technical functionality seems fairly correct and thoroughly
> specified, the primary issue is a tremendous lack of normative language i=
n
> the main body of the document.  Non-inclusive details of such are include=
d
> below.
>
> The 2119 MUST/SHOULD/MAY terms are simply abbreviations for some words
> defined in 2119, and different WGs have different styles about how
> extensively they should be used.

[MB] In my experience it's not so much different WGs as it is the IESG.
 I've had to do much of what I am recommending to get docs agreed in WGs as
well as by the IESG.   [/MB]

> P2PSIP has obviously been on the more sparing side of that spectrum. This
> isn't to say that there aren't any places where it would be useful to add
> such language, but rather that our policy has been to add it principally
> where there is likely ambiguity, rather than everywhere where behavior is
> defined. I'll work thought these and see where they might help reduce the
> chance of a an implementers doing the wrong thing but in generally when w=
e
> define a structure in something like ASN.1 or ABNF, if the structure alwa=
ys
> has a field X, we just use the language like ASN.1 or ABNF to indicate it
> always has that. We don't  also say it MUST be there.


> >
> > Major Issues:
> > -------------------
> >
> > General:
> > --There is a fair number of cases where normative language should be
> used.  I have detailed some (but certainly not all)  instances where it i=
s
> lacking with proposed rewording.  I have also noted cases where it is use=
d
> (lower case) where it could be confused with needing normative language a=
nd
> where it isn't necessary and there are some cases where it's just not cle=
ar.
> I consider these major since it can impact interoperability and could lea=
d
> developers to not implement key functionality.
> >
> > --There is also little or no normative language for the majority of the
> elements in the structures - i.e., the reader has to assume which element=
s
> are mandatory and which are optional and it's not always clear.   For
> example, rather than saying "Field x contains blah", it should say "Field=
 x
> MUST contain blah" and rather than "The contents of the message will be x=
, y
> and z", it should say something like "The message MUST (or SHOULD) contai=
n
> x, y and z".  I have not detailed the places where this is necessary in m=
ost
> cases.  The authors should review the detailed definition for each of the
> messages.
> >
>
> However, the syntax actually tells you whether a field is mandatory or no=
t.
> I.e.,
> there is a "select/case" syntax for indicating optional fields (and some
> fields are
> variable length). So I don't think it's really ambiguous in the general
> case whether
> a field need be present.
>
> With that said, this seems like something that would be better discussed
> real time - I may be missing the point on some of these. When would be a
> good time to have a call?
>
[MB] I'll ping you offline to setup a time to chat. [/MB]

>
> > --The message names are used inconsistently.  The IANA registry has the
> message codes all lower case.  There are places in the examples and the b=
ody
> of the document where the _req part is missing, there is no "_", the firs=
t
> letters are Upper case, etc.  The messages are also used in a general sen=
se
> - e.g., "MUST perform an Attach", which should really be stated as "MUST
> send an attach_req message)
>
> Well, it's the Attach is much more than sending a attach_req and we found
> that trying to add more just make the document even longer and harder to
> understand than it currently is. We been pretty careful about the case as
> some systems auto generate code out the the structures in the draft. I'm
> glad to walk through these and figure them out with you. That said, these
> have been changed various times and it's hard to find them all so there
> could certainly be a mistakes in this.
>
[MB] That's fine - perhaps adding a definition that the term "Attach" is an
entire procedure that includes the sending of an attach_req along with othe=
r
related functionality.   [/MB]

>
>
> >
> > Major - Detailed:
> >
> > - Sections 32.1, 3.2.2 and 3.3: lots of changes needed to reword using
> normative language.
> >
> > - Section 3.4, last paragraph: Needs to be reworded normatively and mor=
e
> precisely. It's really not clear to me what the required behavior is as i=
t
> first says it needs to (which I'm not sure is a SHOULD or is REQUIRED to)
> maintain connections to all the peers near and enough others.., but how m=
uch
> is "enough".   Also, what is meant by the "specified link set" - is that
> referring to all the nearby peers or the peers+enough others?  Or is this
> more clearly (and normatively) specified elsewhere, such that a reference
> could be added
>
> All of section 3 is overview and not meant to have the normative
> descriptions which happen in the later sections.
>
[MB] No problem as long as there is normative behavior as required
elsewhere.  I did not get a chance to double check this (I did spend the
better part of 3+ days just to make a first pass detailed review of the
doc). [/MB]

>
> >
> > - Section 4.2: needs normative language - i.e.:
> > --"Each Usage needs to =85" ->  "Each Usage MUST=85"
>
> This gets into the whole 2119 usage of words in requirements. Right here =
we
> are writing requirements for what future RFC needs to include.
>
[MB] I just had in mind RFC 3265 and the fact that there is normative
behavior for other "usages" (i.e., event packages).  [/MB]

>
> >
> > - Section 5.1.1: Bullet items need normative language
> > -- 1st bullet: It's also  not clear what the its are in "it passes it
> up".  I think it should be "the node passes the message up to the upper
> layers".   However, this probably needs to be normative language - i.e.,
> "the node MUST pass the message to the upper layers".  The same applies t=
o
> the third bullet.
> > --bullet 2:  "the message is destined for this node and is passed up=85=
" ->
> "the message is destined for this node and MUST be passed=85.,
>
> members of the WG objected to MUST level mandating of how the actually
> server software was architected. Note this passing up a level is not abou=
t
> anything to do with what happens on the wire. See section 6 of 2119 which
> pretty much says not to use MUST this way.
>
[MB] Then, the question becomes whether this text is even needed at all -
i.e., why would it necessarily be "passed to an "upper layer" ?  [/MB]

>
> >
> > - Section 5.1.2:
> > -- Paragraphs 5, 6, 7 and 8 need to be reworded to have normative
> statements.
>
> Let's talk on the phone - I'm not seeing the issue here.
>
[MB] There is alot of inconsistency in these sections.  There are paragraph=
s
with no normative language followed by those with normative - it seems text
was added at different times. I'm happy to mail you my marked up hardcopy s=
o
you can see the areas of concern that I haven't detailed. [/MB]

>
> > -- Last paragraph (9) mixes normative text with in an example. The
> normative text needs to be separated from the example
>
> seriously? I'm just not getting how this will help make it more
> interoperable but again, glad to change if we can figure out a real
> improvement.
>
[MB] The use of normative language isn't appropriate in examples.  As long
as the normative behavior is elsewhere, then I just suggest to rewrite the
example without the normative language. [/MB]

>
> > - e.g., split some of the sentences into the normative behavior and the=
n
> the example.
> >
> > -Section 5.2.1 is totally inconsistent with the use of normative langua=
ge
> (i.e., lower case occurrences and lack of KEY words) - shouldn't the
> following be normative statements something like the following:
> > -- First paragraph:
> > ---First sentence:  "a node constructs" -> "a node MUST construct".
> > --- 3rd sentence: "resulting message will use the normal overlay routin=
g"
> -> "resulting message MUST use the normal overlay routing"
> > --- 4th sentence: "The node can also" ->  "The node MAY also"
> > -- Third paragraph:
> > --- 3rd sentence: "a single request can also" -> "a single request MAY
> also"
> > -- Fourth paragraph:
> > --- 1st sentence: this could be interpreted as normative:  "Because
> messages may" ->  "Because messages can"
> 2119 is very clear it refers to MAY and not may. I really don't know what
> word is best here but ignoring 2119, which word looks better "may" or "ca=
n"
> for this sentence?
>

[MB] My concern here is that the use of the terms I suggest makes it a whol=
e
lot easier to avoid any confusion.  I've made these same changes to
documents before  (based upon other reviews) and felt that it is helpful.  =
I
would also think that using these terms makes it a whole lot easier for the
RFC editor.   [/MB]

>
> > --- 3rd sentence:  "the request is retransmitted" ->  "the request MUST
> be retransmitted"
> >
>
> This all looks like internal software design to help
>
[MB] Retransmission sounds like protocol to me. [/MB]

>
> > -Section 5.3.2:
> > -- General: some of the contents of the structure have normative langua=
ge
> and others don't.  There is some normative behavior defined for these fie=
lds
> later, so perhaps adding section references as you do for some fields wou=
ld
> be helpful.
> >
> > For example:
> > --"overlay": shouldn't this be normative:  "the overlay name is hashed
> with SHA-1" -> "the overlay name MUST be hashed with SHA-1"
> > --"destination_list": seems like some of this should be normative?
> >
> > -Section 5.3.2.1:
> > --1st paragraph: shouldn't this be normative?
> > "the configuration document has a sequence number" ->  "the configurati=
on
> document MUST contain a sequence number"
> > -- 1st paragraph, last sentence: "may"  -> "can"
> >
> > -Section 5.3.2.2:
> > --Paragraph after the 1st structure:  Shouldn't this be stated
> normatively since it is described how the structure MUST be handled
> depending upon the contents?
> > --Paragraph after second structure, suggest the following changes:
> > ---"the generation counters should" ->  "the generation counters SHOULD=
"
> > ---"An implementation could use.." -> "An implementation MAY use=85"
> > ---"the node confirms that the generation counter matches" -> "the node
> MUST confirm that the generation counter matches"
> > ---"If it does not match, it is silently dropped." -> "If it does not
> match, it MUST be silently dropped."
> >
> > -Section 5.3.3.1:
> > --1st para: "a request returns" -> "a request MUST return"
> > --1st para: "then the message code is the response code that matches th=
e
> request" ->
> > "then the message code MUST be set to the response code that matches th=
e
> request"
> > --2nd para: "message code is set" ->  "message code MUST be set"
> >
> > -Section 5.3.4 - needs normative language:
> > --1st paragraph after GenericCertificate structure:
> > ---"All signatures are formatted" -> "Alls signatures MUST be formatted=
"
> > ---"The input structure=85varies.." ->  "The input structure =85 MAY va=
ry=85"
> >
> > -Section 5.4.1: "need to be described" -> "MUST be described"
> >
> > -Section 5.4.2-Section 7.  These sections need to be carefully reviewed
> and updated appropriately with normative text.  [ I have marks up for pag=
es
> 55-102 where normative language is needed if someone wants those scanned =
and
> forwarded - I'm just too lazy to type them all out.]
> >
> > - Section 8:  There is only one actual normative word used in this
> section!  There is a lc "should" that ought to be "SHOULD".  I don't know=
 if
> the authors assumed that the normative language in TURN was sufficient, b=
ut
> I do not believe that is the case as it leaves the normative behavior to =
be
> inferred by the reader/implementor. Rather than rewrite the whole section
> myself, the authors need to review carefully. For example, there are "nee=
ds
> to", which likely are really and lots of present tense statements (e.g.,
> "The address of the peer is stored=85"), which ought to be MUSTs or SHOUL=
Ds.
> >
> > - Section 9.2:  seems like this needs normative language. Suggest the
> following:
> > OLD:
> >    For this Chord based topology plugin, the size of the Resource-ID is
> >    128 bits.  The hash of a Resource-ID is computed using SHA-1
> >    [RFC3174]then truncating the SHA-1 result to the most significant 12=
8
> >    bits.
> > NEW:
> >    For Chord-RELOAD, the size of the Resource-ID MUST be
> >    128 bits.  The hash of a Resource-ID MUST be computed using SHA-1
> >    [RFC3174].  The SHA-1 result MUST be truncated to the most significa=
nt
> >    128 bits.
> >
> > - Section 9.3: Needs normative language.
> > OLD:
> >    If a peer is not responsible for a Resource-ID k, but is directly
> >    connected to a node with Node-ID k, then it routes the message to
> >    that node.  Otherwise, it routes the request to the peer in the
> >    routing table that has the largest Node-ID that is in the interval
> >    between the peer and k.  If no such node is found, it finds the
> >    smallest Node-Id that is greater than k and routes the message to
> >    that node.
> > NEW:
> >    If a peer is not responsible for a Resource-ID k, but is directly
> >    connected to a node with Node-ID k, then it MUST route the message t=
o
> >    that node.  Otherwise, it MUST route the request to the peer in the
> >    routing table that has the largest Node-ID that is in the interval
> >    between the peer and k.  If no such node is found, it MUST find the
> >    smallest Node-Id that is greater than k and MUST route the message t=
o
> >    that node.
> >
> > - Section 9.4: Needs normative language.
> >
> > - Section 9.5: While this section does have a fair amount of normative
> language, it is still lacking in a few cases:
> > --Item 2.:  "should" -> "SHOULD"
> > --Item 5.:  "The AP sends the response=85" -> "The AP MUST send the
> response=85"
> > --1st paragraph after list: "=85can directly connect=85" -> "MAY direct=
ly
> connect"
> > --2nd paragraph after list: "it can still populate" -> "it MAY still
> populate"
> > --2nd paragraph after list: the description of the use of PING should b=
e
> reworded with normative language (I'll leave that exercise to the authors=
)
> > --3rd paragraph after the list:  "JP simply sends" -> "JP MUST send"
> >
> > - Section 9.7.1:
> > --1st para:  ".., it then sends=85" -> ".., it then MUST send =85"
> > --3rd para: needs normative language
> > OLD:
> >    In no event does
> >    an attempt to reestablish connectivity with a lost neighbor allow th=
e
> >    peer to remain in the neighbor table.
> > NEW:
> >    In the case of
> >    an attempt to reestablish connectivity with a lost neighbor, the pee=
r
> >    MUST not remain in the neighbor table.
> > OR:
> >    In the case of
> >    an attempt to reestablish connectivity with a lost neighbor, the pee=
r
> >    MUST be removed from the neighbor table.
> > -- 4th para: "should" -> "SHOULD" (2 cases),  "use Pings" -> "MUST use
> Pings"
> >
> > -Section 9.7.2:
> > --1st para:  "..the failed peer are removed.." -> "=85the failed peer M=
UST
> be removed.."
> > --2nd para:  "=85the peer initiates=85" -> "=85the peer MUST initiate..=
"
> >
> > -Section 9.7.3:
> > --1st para after list:  "is needed" -> "is REQUIRED"
> > --3rd para after list:  "the peer sends an Update" -> "the peer MUST se=
nd
> an Update"
> >
> > -Section 9.7.4.4:  Needs a scrub for normative language
> >
> > -Section 9.9: Needs a scrub for normative language.
> >
> > -Section 10.1: General: Needs a lot of work to be specified using
> normative language.  The majority of the configuration elements are not
> specified using normative language - for example, terms such as permitted=
,
> allowed, valid are used in statements rather than normative language
> > or they are indicative of the need for normative language.  A specific
> example is in the definition for "clients-permitted":
> >
> > OLD:
> >       This element represents whether clients are
> >       permitted or whether all nodes must be peers.  If it is set to
> >       "true" or absent, this indicates that clients are permitted.  If
> >       it is set to "false" then nodes are not allowed to remain clients
> >       after the initial join.
> >
> > NEW:
> >       This element represents whether clients are
> >       permitted or whether all nodes need to be peers.  If clients
> >       are permitted, the element MUST be set to "true" or absent.
> >       If the nodes are not allowed to remain clients after the
> >       initial join, the element MUST be set to "false".
> >
> > --Section 10.1 - 4th para after the element list states that "All of th=
e
> non optional values MUST be provided".  However, the list of elements in =
the
> previous paragraph are not specifically identified as non optional.  I th=
ink
> the first 3 are mandatory.  So, I would suggest to re-word the 3rd paragr=
aph
> as follows and delete the 1st sentence in the 4th paragraph noted above:
> > OLD:
> >    In addition, the kind element contains the following elements:
> >    max-count:  the maximum number of values which members of the overla=
y
> >       must support.
> >    data-model:  the data model to be used.
> >    max-size:  the maximum size of individual values.
> >    access-control:  the access control model to be used.
> >    max-node-multiple:  This is optional and only used when the access
> >       control is NODE-MULTIPLE.  This indicates the maximum value for
> >       the i counter.  This is an integer greater than 0.
> >
> > NEW:
> >    In addition, the kind element MUST contain the following elements:
> >    max-count:  the maximum number of values which members of the overla=
y
> >       must support.
> >    data-model:  the data model to be used.
> >    max-size:  the maximum size of individual values.
> >    access-control:  the access control model to be used.
> >
> >    The kind element MAY also contain the following element:
> >    max-node-multiple:  if the access control is NODE-MULTIPLE,
> >       this element MAY be included. This indicates the maximum value fo=
r
> >       the i counter.  It MUST be an integer greater than 0.
> >
> > --Section 10.1, next to last para: There's no normative language, but i=
t
> seems there should be since it is specifying specification computations a=
nd
> encoding that I believe are required.
> >
> > - Section 10.2:  Needs more normative language:
> >
> > -- 2nd para:
> > OLD: This value is provided by the user or some other out of band
> >      provisioning mechanism.
> >
> > NEW: This value MUST be provided by the user or some other out of band
> >      provisioning mechanism."
> >
> > -- 3rd para:
> > OLD:
> >    Once an address and URL for the configuration server is determined,
> >    the peer forms an HTTPS connection to that IP address.
> > NEW:
> >    Once an address and URL for the configuration server is determined,
> >    the peer MUST form an HTTPS connection to that IP address.
> >
> > -- 4th para:  "which replaces" ->  "which MUST replace"
> >
> > -- 5th para:  "nodes obtain the" -> "nodes MUST obtain the"
> >
> > - Section 10.3:
> > -- 3rd para:  "is performed" -> "MUST be performed".
> > -- 3rd para: Bullets need to be modified to normative.
> > -- 4th para: "the certificate contains" -> "the certificate MUST contai=
n"
> > -- para after 2nd set of bullets:  needs normative language.
> > -- 2nd para after 2nd set of bullets:  "The node then reads=85" ->  "Th=
e
> node MUST then use=85"
> >
> > - Section 10.5:
> > --Second para: "the joining node first forms" -> "the joining node MUST
> first form"
> > --3rd para:  text uses the phrase "it can note the Node-ID in the
> response and use this Node-ID to start sending requests".  It's not clear
> whether the use of the Node-ID is a MAY or a MUST.
> >
> > - Section 12. I'm assuming that the security directorate has reviewed
> this in detail, thus my focus in reviewing this section was on general
> understanding. The biggest issues is that there is NO normative language =
at
> all in the security section.  As in other sections, terms like "need",
> "are/is used/sent, etc.",  "ensure", lower case reserved words rather tha=
n
> upper case, etc. are used when normative language ought to have been used=
.
> >
> >
> > - Section 13. IANA Registrations:
> > - General: there seem to be several registries for which the
> usage/requirement is unclear as there's no mention of such in the body of
> the document.  In general, references to the sections in the document
> describing the information included in the registries would be more than
> helpful.
> >
> > - Section 13.5: Creates a RELOAD Application Registry, but the use and
> need for such isn't described elsewhere in the document
>
> Section 5.5.2.1 defines the usage of this and contains the text
>
>      A 16-bit application-id as defined in the Section 13.5.  This
>      number represents the IANA registered application that is going to
>      send data on this connection.


[MB] Okay. I missed that - sorry - I thought I searched the text and
couldn't find it. [/MB]

>


> >
> > - Section 13.12. Forwarding Options Registry. SEction 5.3.2.3 seems to
> define three flags for the Forwarding options type, so it's not clear to =
me
> why this registry has just "invalid" and "reserved"
> >
>
> The registry is for the ForwardingOptionsType code points and not the
> flags. Any new forwarding option could use any of these flags. The flags
> only indicate who needs to understand the the forwarding option.
>
[MB] Maybe add some text around that. [/MB]

>
> >
> > - Section 13.15:  Defines/registers a RELOAD URI schema but there is no
> mention of this URI anywhere else in the document.  In what context is it
> used?
>
> It would be used by other specifications that use Reload. It's not used
> inside of reload itself. Folks wanted it defined here so we kept it
> consistent and other specs could use the URI.
>
[MB] Maybe add some text around that. [/MB]

>
> >
> >
> > Minor  Issues:
> > ---------------------
> >
> > - Section 1.2.1, 2nd paragraph: I don't understand the example as to wh=
y
> a single application requires multiple usages - i.e, why voicemail?  Isn'=
t
> the intent to say that an application might need to use both SIP and XMPP=
 -
> i.e., you wouldn't define a "usage" for an application, would you?
> storing voicemail in the DHT would require a different usage than the typ=
e
> of rendezvous service of XMPP or SIP
>
> >
> > - Section 2. Some of the definitions use terms that are not yet defined=
,
> so that's not particularly helpful - i.e,. Attach and Update are used. In
> some cases (e.g., Connection Table), you could just delete the statement
> with the reference.
> >
>
> I'm not sure how to resolve this. I agree that by the time we get to the
> definition, if you have not read the rest of the document, the sentence, =
"
> This includes nodes with which Attach handshakes have
>      been done but which have not sent any Updates." does not currently
> mean something that you can understand. But after reading the document, t=
his
> sense helps clear up something implementors were confused about so I
> definitely don't want to loose it. I'd like to fix this but not sure what
> you are suggesting. Are you suggesting just saying in these terms are
> defined later with a forward reference and leaving the sentence there?
>
[MB] Yes. I think a forward reference would be extremely helpful.  Per my
comment about alphabetizing below, the same concept applies.  While folks
will likely need to work from both a hard and softcopy to review this
document (as I did while reviewing), I think it should be possible to read =
a
hardcopy.  In particular given that this document will require multiple
reads to really get things.  [/MB]

>
>
> > - Section 3.3, last paragraph.  Add a reference to 5.4.2.4  after
> "RouteQuery method"
> >
> > - Section 5.1: "If any of these are incorrect=85"  - need to specify wh=
at
> qualifies as "incorrect" - is it wrong formatting, invalid header field
> > value, etc.?
> >
> > - Section 5.1.2:
> > --1st paragraph: I have no idea what the "other three cases" references=
.
> >
> > - Section 5.2: "may be configured" -> "can be configured",  "alternativ=
e
> > routing algorithms may be selected" -> "alternative routing algorithms
> MAY be selected"
> >
> > - Section 5.3:  The three parts of the messages are listed and the last
> sentence says that "The following sections describe the format of each pa=
rt
> of the message", but there are 4 sub-sections in 5.3, with the first sect=
ion
> NOT describing one of the three parts of the messages.  I suggest to stri=
ke
> that last sentence and just put references to the sections in the list it=
ems
> for each of the three messages.
> >
> > -Section 5.3.3:
> > --"critical" description:  "Whether this extension must be.." "Whether
> this extension needs to be=85"
> >
> > -Section 5.3.4:  1st para after certificate structure:  "may contain" -=
>
> "MAY contain"
> >
> > -Section 5.5: It would be helpful to highlight that foundation, priorit=
y
> and type are based on ICE, in particular since ICE is not discussed until
> the subsequent section - e.g., "the foundation production" -> "the ICE
> foundation production".
> >
> > - Section 5.6:
> > -- The last three paragraphs are confusing.
> > ---In particular, it's not clear what algorithms are being referenced i=
n
> this sentence:
> >   "We will first define each of these algorithms, then
> >    define overlay link protocols that use them."
> > --- In the note paragraph, I believe "These protocols have been chosen=
=85"
> is referring to the three overlay link protocols supported by RELOAD per
> this document.
> > ---The Note to implementors paragraph seems out of context
> > --- Per my next comment, I suggest to move the detailed discussion of
> future overlay link protocols to the appendix, so some of this text may b=
e
> relevant only to that.
> >
> > -Section 5.6.1:  I suggest that the sub-sections in this section be mov=
ed
> to an appendix and a reference to such be added.
> >
> > -Section 5.6.3.1.1, next to the last paragraph:
> > "when a link may be failing" -> "when a link might be failing"
> >
> > - Section 9.1: While this is an overview, it seems to me that some of
> this is describing normative behavior (that I don't see specified else).
>  Per the general comment, I would reword the first sentence as follows:
> > OLD:
> >    The algorithm described here is a modified version of the Chord
> >    algorithm.
> > NEW:
> >     The algorithm described here, Chord-RELOAD is a modified version
> >     of the Chord algorithm.
> >
> > - Section 10.3, 1st para:  "required" -> "REQUIRED"
> >
> > - Section 10.3.1, last sentence: "must"  -> "MUST"
> >
> > - Section 10.4, 1st para, last sentence: "should use" -> "SHOULD use"
> >
> > - Section 11 - examples:
> > --General - there are no detailed messages shown anywhere for the
> examples. There should be at least one, in particular given the comment
> above about the RELOAD URI that is registered, but not mentioned anywhere
> else in the document.
> > --first example (see my nit below about the examples not being numbered
> or labeled in any way):  The third sentence says that "It gets routed to =
the
> admitting peer (AP), yet the flow shows that the message first gets route=
d
> to the PP and then onto AP. It would be helpful if that were clarified.
> > -  Also (general), the text mentions the use of ICE.  It's not clear to
> me exactly where in the flow that happens - it would be good to annotate
> such (i.e., in a similar manner as the TLS is illustrated).
> > - next to the last example (text on page 131, diagram on page 132): I'm
> quite confused as the text states that JP has received an update from AP =
and
> thus now knows APs predecessors, which are also JP's predecessors, so JP
> Attaches to them. However, the diagram does not show JP getting an Update
> from AP and it shows JP doing Updates to PPP and PP rather than Attaches =
(as
> the text suggests).
> >
> > - Section 13.10. Overlay link types: These specific string types are no=
t
> used elsewhere in the document.  Suggest that a reference to 5.6 be added
> and these particular strings be included in parenthesis after the items i=
n
> the list.
>
> makes sense
>
>
> >
> >
> > - Section 13.16, Security considerations portion:
> > -- The first sentence doesn't make sense. Did you mean?
> >    "This media type is typically not used to
> >    transport information that needs to be kept confidential,
> >    however, there are cases where the integrity of the information is
> >    important."
>
> yes - that is much better - this text was added late and received little
> review
>
> > -- "then the contents of the file need to be=85" -> "then the contents =
of
> the file MUST be =85"
> >
> >
> >
> > Nits:
> > -----
> > - General: kind is sometimes "Kind" and sometimes "kind".  The former i=
s
> more readable and highlights it as a reserved word.
>
>  Seems reasonable
>
> >
> > - Section 2.
> > --General: It would be helpful if the terms were alphabetized.
>
> this is easy to do but complicates the forward reference problem. Thought=
s
> on what is best?
>
[MB] See my comment above - I think a note that term x is defined below is
fine. If they're alphabetized the unknown term is easy to fine. [/MB]

>
> > --Node: "We use the term "Node" to refer to =85" -> "Refers to =85"
> >
> > - Section 3.2:
> > -- 2nd para, last sentence:  "refer such" -> "refer to such"
> that needs to b fixed
>
> > -- 3rd para, 1st sentence:  "concept" -> "entity"
> >
> > - Section 4.1.4,
> (this is section 4.1.1 for others reading this)
>
> > 4th paragraph: I'm still not getting the applicability of voicemail as =
a
> RELOAD Kind (per the reference also in section 1.2.1).  I guess you are
> talking about a voicemail message (in this case) and a server or applicat=
ion
> in section 1.2.1?   Voicemail just does not seem like an obvious example =
to
> me.
>
> All it is trying to say is the size of a storing the audio for a voicemai=
l
> in the overlay is much larger than saving a link. Note that several peopl=
e
> in the WG think it is nuts to try and save a full voice message in the
> overlay and several others think the opposite. This argument was avoid by
> explicitly mention in this draft the example of voicemail.
>
> >
> > - Section 5.1.1, last bullet:  "In that case,=85" ->  "In the latter ca=
se,
> =85"
> make sense
>
>
> >
> > - Section 5.1.2:
> > -- 2nd para:  "arrange" -> "ensure",  "This may be arranged" -> "This c=
an
> be arranged=85"
> make sense
>
> > -- 3rd para (1st after bullets): It's not clear that A=85E is a set of
> ordered nodes in the example. I would suggest to reword as:
> > OLD:
> >    As an example of the first strategy, if node D
> > NEW:
> >   Consider an example with nodes A, B, C, D and E, respectively.  If
> >   node D=85.
> ok
>
> >
> > - Section 5.3.1.1: First two sentences can be reworded more succinctly =
-
> you're not really providing definitions here, put rather describing the
> > the syntax for and providing examples illustrative of the presentation
> language.
> >
> > OLD:
> >    The following definitions are used throughout RELOAD and so are
> >    defined here.
>
> we really are defining opaque and true and false here
>
> > They also provide a convenient introduction to how to
> >    read the presentation language.
> > NEW:
> >    This section provides an introduction to the presentation language
> >    used throughout RELOAD.
> >
> > - Section 5.3.3.1: Error_Data_Too_Old is duplicated.
> that's embarrassing :-)
>
> >
> > - Section 5.5.1.6: Add references for SCTP and DCCP.
> >
> > - Section 6.4.1.3:  The reference to "this Version" is superfluous.
> Propose the following change:
> > OLD:
> >    This version of RELOAD (unlike previous versions) does not have an
> >    explicit Remove operation.
> > NEW:
> >    RELOAD does not have an explicit Remove operation.
>
> make sense
>
> >
> > - Section 9: General. The first sentence states that the algorithm
> defined here is referred to as "chord-reload", however, subsequent sectio=
ns
> don't seem to use that term.
>
> uh, that should have been upper case in this section.
>
> >  It would be more clear if that term was used. And, really, it would be
> more consistent to use the term Chord-RELOAD. However, this should also b=
e
> consistent with the IANA-Registration which has CHORD-RELOAD.
> >
> > - Section 9.7.4.3, 3rd para:
> > -- Remove "Note to implementers".  Text already highlights that the tex=
t
> is specific to implementations.
> > -- "may be found" -> "can be found"
> >
> > - Section 9.8:  "For this topology plugin" -> "For Chord-RELOAD"
> >
> > - Section 10.2, 2nd para:  "determines" -> "determining"
> needs to be fixed
>
> >
> > - Section 11:
> > - General: there are no labels for any of the call flows, so it's not
> always clear what the text is referring to.  In general, I think the text
> precedes the flow.
> > - "abbreviation" -> "abbreviations"
> needs to be fixed
>
> >
> > - Section 13.16:
> > --Interoperability considerations:  "knows" -> "known"
> needs to be fixed
>
> >
> > - Section 14: "provied" -> "provided"
> needs to be fixed
> >
> > - Appendix C: Delete now - it's totally useless as is.
> make sense
>
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>
>

--bcaec5196dddd09a9d04aa94cec1
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Cullen,<div><br></div><div>Responses inline below [MB]. =A0</div><div><br><=
/div><div>Mary.<br><br><div class=3D"gmail_quote">On Thu, Aug 11, 2011 at 7=
:43 PM, Cullen Jennings <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@cisc=
o.com">fluffy@cisco.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;"><br>
Thanks for the detailed review - you caught some good stuff. Most of this m=
akes essence but we should probably talk about usage of 2119 language.<br>
<br>
On Aug 9, 2011, at 16:05 , Mary Barnes wrote:<br>
&gt; simple<br>
<div class=3D"im">&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
&gt;<br>
&gt; Document: draft-ietf-p2psip-base-17<br>
&gt; Reviewer: =A0Mary Barnes<br>
&gt; Review Date: =A09 August =A02011<br>
&gt; IETF LC End Date: 22 July 2011<br>
&gt;<br>
&gt; Summary: Not Ready.<br>
&gt;<br>
&gt; Comments:<br>
&gt; ----------------<br>
&gt; The document is very a dense (with detailed technical information) and=
 long (150 page) specification for a Peer-to-peer signaling protocol. =A0Wh=
ile the overall technical functionality seems fairly correct and thoroughly=
 specified, the primary issue is a tremendous lack of normative language in=
 the main body of the document. =A0Non-inclusive details of such are includ=
ed below.<br>

<br>
</div>The 2119 MUST/SHOULD/MAY terms are simply abbreviations for some word=
s defined in 2119, and different WGs have different styles about how extens=
ively they should be used. </blockquote><div>[MB] In my experience it&#39;s=
 not so much different WGs as it is the IESG. =A0I&#39;ve had to do much of=
 what I am recommending to get docs agreed in WGs as well as by the IESG. =
=A0 [/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">P2PSIP has obviously been on the more spari=
ng side of that spectrum. This isn&#39;t to say that there aren&#39;t any p=
laces where it would be useful to add such language, but rather that our po=
licy has been to add it principally where there is likely ambiguity, rather=
 than everywhere where behavior is defined. I&#39;ll work thought these and=
 see where they might help reduce the chance of a an implementers doing the=
 wrong thing but in generally when we define a structure in something like =
ASN.1 or ABNF, if the structure always has a field X, we just use the langu=
age like ASN.1 or ABNF to indicate it always has that. We don&#39;t =A0also=
 say it MUST be there.=A0</blockquote>
<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>
&gt;<br>
&gt; Major Issues:<br>
&gt; -------------------<br>
&gt;<br>
&gt; General:<br>
&gt; --There is a fair number of cases where normative language should be u=
sed. =A0I have detailed some (but certainly not all) =A0instances where it =
is lacking with proposed rewording. =A0I have also noted cases where it is =
used (lower case) where it could be confused with needing normative languag=
e and where it isn&#39;t necessary and there are some cases where it&#39;s =
just not clear. I consider these major since it can impact interoperability=
 and could lead developers to not implement key functionality.<br>

&gt;<br>
&gt; --There is also little or no normative language for the majority of th=
e elements in the structures - i.e., the reader has to assume which element=
s are mandatory and which are optional and it&#39;s not always clear. =A0 F=
or example, rather than saying &quot;Field x contains blah&quot;, it should=
 say &quot;Field x MUST contain blah&quot; and rather than &quot;The conten=
ts of the message will be x, y and z&quot;, it should say something like &q=
uot;The message MUST (or SHOULD) contain x, y and z&quot;. =A0I have not de=
tailed the places where this is necessary in most cases. =A0The authors sho=
uld review the detailed definition for each of the messages.<br>

&gt;<br>
<br>
</div>However, the syntax actually tells you whether a field is mandatory o=
r not. I.e.,<br>
there is a &quot;select/case&quot; syntax for indicating optional fields (a=
nd some fields are<br>
variable length). So I don&#39;t think it&#39;s really ambiguous in the gen=
eral case whether<br>
a field need be present.<br>
<br>
With that said, this seems like something that would be better discussed re=
al time - I may be missing the point on some of these. When would be a good=
 time to have a call?<br></blockquote><div>[MB] I&#39;ll ping you offline t=
o setup a time to chat. [/MB]=A0</div>
<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>
&gt; --The message names are used inconsistently. =A0The IANA registry has =
the message codes all lower case. =A0There are places in the examples and t=
he body of the document where the _req part is missing, there is no &quot;_=
&quot;, the first letters are Upper case, etc. =A0The messages are also use=
d in a general sense - e.g., &quot;MUST perform an Attach&quot;, which shou=
ld really be stated as &quot;MUST send an attach_req message)<br>

<br>
</div>Well, it&#39;s the Attach is much more than sending a attach_req and =
we found that trying to add more just make the document even longer and har=
der to understand than it currently is. We been pretty careful about the ca=
se as some systems auto generate code out the the structures in the draft. =
I&#39;m glad to walk through these and figure them out with you. That said,=
 these have been changed various times and it&#39;s hard to find them all s=
o there could certainly be a mistakes in this.<br>
</blockquote><div>[MB] That&#39;s fine - perhaps adding a definition that t=
he term &quot;Attach&quot; is an entire procedure that includes the sending=
 of an attach_req along with other related functionality. =A0 [/MB]=A0</div=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
<br>
&gt;<br>
&gt; Major - Detailed:<br>
&gt;<br>
&gt; - Sections 32.1, 3.2.2 and 3.3: lots of changes needed to reword using=
 normative language.<br>
<div class=3D"im">&gt;<br>
&gt; - Section 3.4, last paragraph: Needs to be reworded normatively and mo=
re precisely. It&#39;s really not clear to me what the required behavior is=
 as it first says it needs to (which I&#39;m not sure is a SHOULD or is REQ=
UIRED to) maintain connections to all the peers near and enough others.., b=
ut how much is &quot;enough&quot;. =A0 Also, what is meant by the &quot;spe=
cified link set&quot; - is that referring to all the nearby peers or the pe=
ers+enough others? =A0Or is this more clearly (and normatively) specified e=
lsewhere, such that a reference could be added<br>

<br>
</div>All of section 3 is overview and not meant to have the normative desc=
riptions which happen in the later sections.<br></blockquote><div>[MB] No p=
roblem as long as there is normative behavior as required elsewhere. =A0I d=
id not get a chance to double check this (I did spend the better part of 3+=
 days just to make a first pass detailed review of the doc). [/MB]=A0</div>
<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>
&gt;<br>
&gt; - Section 4.2: needs normative language - i.e.:<br>
&gt; --&quot;Each Usage needs to =85&quot; -&gt; =A0&quot;Each Usage MUST=
=85&quot;<br>
<br>
</div>This gets into the whole 2119 usage of words in requirements. Right h=
ere we are writing requirements for what future RFC needs to include.<br></=
blockquote><div>[MB] I just had in mind RFC 3265 and the fact that there is=
 normative behavior for other &quot;usages&quot; (i.e., event packages). =
=A0[/MB]</div>
<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>
&gt;<br>
&gt; - Section 5.1.1: Bullet items need normative language<br>
&gt; -- 1st bullet: It&#39;s also =A0not clear what the its are in &quot;it=
 passes it up&quot;. =A0I think it should be &quot;the node passes the mess=
age up to the upper layers&quot;. =A0 However, this probably needs to be no=
rmative language - i.e., &quot;the node MUST pass the message to the upper =
layers&quot;. =A0The same applies to the third bullet.<br>

&gt; --bullet 2: =A0&quot;the message is destined for this node and is pass=
ed up=85&quot; -&gt; &quot;the message is destined for this node and MUST b=
e passed=85.,<br>
<br>
</div>members of the WG objected to MUST level mandating of how the actuall=
y server software was architected. Note this passing up a level is not abou=
t anything to do with what happens on the wire. See section 6 of 2119 which=
 pretty much says not to use MUST this way.<br>
</blockquote><div>[MB] Then, the question becomes whether this text is even=
 needed at all - i.e., why would it necessarily be &quot;passed to an &quot=
;upper layer&quot; ? =A0[/MB]=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im"><br>
&gt;<br>
&gt; - Section 5.1.2:<br>
&gt; -- Paragraphs 5, 6, 7 and 8 need to be reworded to have normative stat=
ements.<br>
<br>
</div>Let&#39;s talk on the phone - I&#39;m not seeing the issue here.<br><=
/blockquote><div>[MB] There is alot of inconsistency in these sections. =A0=
There are paragraphs with no normative language followed by those with norm=
ative - it seems text was added at different times. I&#39;m happy to mail y=
ou my marked up hardcopy so you can see the areas of concern that I haven&#=
39;t detailed. [/MB]</div>
<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>
&gt; -- Last paragraph (9) mixes normative text with in an example. The nor=
mative text needs to be separated from the example<br>
<br>
</div>seriously? I&#39;m just not getting how this will help make it more i=
nteroperable but again, glad to change if we can figure out a real improvem=
ent.<br></blockquote><div>[MB] The use of normative language isn&#39;t appr=
opriate in examples. =A0As long as the normative behavior is elsewhere, the=
n I just suggest to rewrite the example without the normative language. [/M=
B]</div>
<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>
&gt; - e.g., split some of the sentences into the normative behavior and th=
en the example.<br>
&gt;<br>
&gt; -Section 5.2.1 is totally inconsistent with the use of normative langu=
age (i.e., lower case occurrences and lack of KEY words) - shouldn&#39;t th=
e following be normative statements something like the following:<br>
&gt; -- First paragraph:<br>
&gt; ---First sentence: =A0&quot;a node constructs&quot; -&gt; &quot;a node=
 MUST construct&quot;.<br>
&gt; --- 3rd sentence: &quot;resulting message will use the normal overlay =
routing&quot; -&gt; &quot;resulting message MUST use the normal overlay rou=
ting&quot;<br>
&gt; --- 4th sentence: &quot;The node can also&quot; -&gt; =A0&quot;The nod=
e MAY also&quot;<br>
&gt; -- Third paragraph:<br>
&gt; --- 3rd sentence: &quot;a single request can also&quot; -&gt; &quot;a =
single request MAY also&quot;<br>
&gt; -- Fourth paragraph:<br>
&gt; --- 1st sentence: this could be interpreted as normative: =A0&quot;Bec=
ause messages may&quot; -&gt; =A0&quot;Because messages can&quot;<br>
</div>2119 is very clear it refers to MAY and not may. I really don&#39;t k=
now what word is best here but ignoring 2119, which word looks better &quot=
;may&quot; or &quot;can&quot; for this sentence?<br></blockquote><div>
<br></div><div>[MB] My concern here is that the use of the terms I suggest =
makes it a whole lot easier to avoid any confusion. =A0I&#39;ve made these =
same changes to documents before =A0(based upon other reviews) and felt tha=
t it is helpful. =A0I would also think that using these terms makes it a wh=
ole lot easier for the RFC editor. =A0 [/MB]=A0</div>
<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>
&gt; --- 3rd sentence: =A0&quot;the request is retransmitted&quot; -&gt; =
=A0&quot;the request MUST be retransmitted&quot;<br>
&gt;<br>
<br>
</div>This all looks like internal software design to help<br></blockquote>=
<div>[MB] Retransmission sounds like protocol to me. [/MB]=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex;">

<div><div></div><div class=3D"h5"><br>
&gt; -Section 5.3.2:<br>
&gt; -- General: some of the contents of the structure have normative langu=
age and others don&#39;t. =A0There is some normative behavior defined for t=
hese fields later, so perhaps adding section references as you do for some =
fields would be helpful.<br>

&gt;<br>
&gt; For example:<br>
&gt; --&quot;overlay&quot;: shouldn&#39;t this be normative: =A0&quot;the o=
verlay name is hashed with SHA-1&quot; -&gt; &quot;the overlay name MUST be=
 hashed with SHA-1&quot;<br>
&gt; --&quot;destination_list&quot;: seems like some of this should be norm=
ative?<br>
&gt;<br>
&gt; -Section <a href=3D"http://5.3.2.1" target=3D"_blank">5.3.2.1</a>:<br>
&gt; --1st paragraph: shouldn&#39;t this be normative?<br>
&gt; &quot;the configuration document has a sequence number&quot; -&gt; =A0=
&quot;the configuration document MUST contain a sequence number&quot;<br>
&gt; -- 1st paragraph, last sentence: &quot;may&quot; =A0-&gt; &quot;can&qu=
ot;<br>
&gt;<br>
&gt; -Section <a href=3D"http://5.3.2.2" target=3D"_blank">5.3.2.2</a>:<br>
&gt; --Paragraph after the 1st structure: =A0Shouldn&#39;t this be stated n=
ormatively since it is described how the structure MUST be handled dependin=
g upon the contents?<br>
&gt; --Paragraph after second structure, suggest the following changes:<br>
&gt; ---&quot;the generation counters should&quot; -&gt; =A0&quot;the gener=
ation counters SHOULD&quot;<br>
&gt; ---&quot;An implementation could use..&quot; -&gt; &quot;An implementa=
tion MAY use=85&quot;<br>
&gt; ---&quot;the node confirms that the generation counter matches&quot; -=
&gt; &quot;the node MUST confirm that the generation counter matches&quot;<=
br>
&gt; ---&quot;If it does not match, it is silently dropped.&quot; -&gt; &qu=
ot;If it does not match, it MUST be silently dropped.&quot;<br>
&gt;<br>
&gt; -Section <a href=3D"http://5.3.3.1" target=3D"_blank">5.3.3.1</a>:<br>
&gt; --1st para: &quot;a request returns&quot; -&gt; &quot;a request MUST r=
eturn&quot;<br>
&gt; --1st para: &quot;then the message code is the response code that matc=
hes the request&quot; -&gt;<br>
&gt; &quot;then the message code MUST be set to the response code that matc=
hes the request&quot;<br>
&gt; --2nd para: &quot;message code is set&quot; -&gt; =A0&quot;message cod=
e MUST be set&quot;<br>
&gt;<br>
&gt; -Section 5.3.4 - needs normative language:<br>
&gt; --1st paragraph after GenericCertificate structure:<br>
&gt; ---&quot;All signatures are formatted&quot; -&gt; &quot;Alls signature=
s MUST be formatted&quot;<br>
&gt; ---&quot;The input structure=85varies..&quot; -&gt; =A0&quot;The input=
 structure =85 MAY vary=85&quot;<br>
&gt;<br>
&gt; -Section 5.4.1: &quot;need to be described&quot; -&gt; &quot;MUST be d=
escribed&quot;<br>
&gt;<br>
&gt; -Section 5.4.2-Section 7. =A0These sections need to be carefully revie=
wed and updated appropriately with normative text. =A0[ I have marks up for=
 pages 55-102 where normative language is needed if someone wants those sca=
nned and forwarded - I&#39;m just too lazy to type them all out.]<br>

&gt;<br>
&gt; - Section 8: =A0There is only one actual normative word used in this s=
ection! =A0There is a lc &quot;should&quot; that ought to be &quot;SHOULD&q=
uot;. =A0I don&#39;t know if the authors assumed that the normative languag=
e in TURN was sufficient, but I do not believe that is the case as it leave=
s the normative behavior to be inferred by the reader/implementor. Rather t=
han rewrite the whole section myself, the authors need to review carefully.=
 For example, there are &quot;needs to&quot;, which likely are really and l=
ots of present tense statements (e.g., &quot;The address of the peer is sto=
red=85&quot;), which ought to be MUSTs or SHOULDs.<br>

&gt;<br>
&gt; - Section 9.2: =A0seems like this needs normative language. Suggest th=
e following:<br>
&gt; OLD:<br>
&gt; =A0 =A0For this Chord based topology plugin, the size of the Resource-=
ID is<br>
&gt; =A0 =A0128 bits. =A0The hash of a Resource-ID is computed using SHA-1<=
br>
&gt; =A0 =A0[RFC3174]then truncating the SHA-1 result to the most significa=
nt 128<br>
&gt; =A0 =A0bits.<br>
&gt; NEW:<br>
&gt; =A0 =A0For Chord-RELOAD, the size of the Resource-ID MUST be<br>
&gt; =A0 =A0128 bits. =A0The hash of a Resource-ID MUST be computed using S=
HA-1<br>
&gt; =A0 =A0[RFC3174]. =A0The SHA-1 result MUST be truncated to the most si=
gnificant<br>
&gt; =A0 =A0128 bits.<br>
&gt;<br>
&gt; - Section 9.3: Needs normative language.<br>
&gt; OLD:<br>
&gt; =A0 =A0If a peer is not responsible for a Resource-ID k, but is direct=
ly<br>
&gt; =A0 =A0connected to a node with Node-ID k, then it routes the message =
to<br>
&gt; =A0 =A0that node. =A0Otherwise, it routes the request to the peer in t=
he<br>
&gt; =A0 =A0routing table that has the largest Node-ID that is in the inter=
val<br>
&gt; =A0 =A0between the peer and k. =A0If no such node is found, it finds t=
he<br>
&gt; =A0 =A0smallest Node-Id that is greater than k and routes the message =
to<br>
&gt; =A0 =A0that node.<br>
&gt; NEW:<br>
&gt; =A0 =A0If a peer is not responsible for a Resource-ID k, but is direct=
ly<br>
&gt; =A0 =A0connected to a node with Node-ID k, then it MUST route the mess=
age to<br>
&gt; =A0 =A0that node. =A0Otherwise, it MUST route the request to the peer =
in the<br>
&gt; =A0 =A0routing table that has the largest Node-ID that is in the inter=
val<br>
&gt; =A0 =A0between the peer and k. =A0If no such node is found, it MUST fi=
nd the<br>
&gt; =A0 =A0smallest Node-Id that is greater than k and MUST route the mess=
age to<br>
&gt; =A0 =A0that node.<br>
&gt;<br>
&gt; - Section 9.4: Needs normative language.<br>
&gt;<br>
&gt; - Section 9.5: While this section does have a fair amount of normative=
 language, it is still lacking in a few cases:<br>
&gt; --Item 2.: =A0&quot;should&quot; -&gt; &quot;SHOULD&quot;<br>
&gt; --Item 5.: =A0&quot;The AP sends the response=85&quot; -&gt; &quot;The=
 AP MUST send the response=85&quot;<br>
&gt; --1st paragraph after list: &quot;=85can directly connect=85&quot; -&g=
t; &quot;MAY directly connect&quot;<br>
&gt; --2nd paragraph after list: &quot;it can still populate&quot; -&gt; &q=
uot;it MAY still populate&quot;<br>
&gt; --2nd paragraph after list: the description of the use of PING should =
be reworded with normative language (I&#39;ll leave that exercise to the au=
thors)<br>
&gt; --3rd paragraph after the list: =A0&quot;JP simply sends&quot; -&gt; &=
quot;JP MUST send&quot;<br>
&gt;<br>
&gt; - Section 9.7.1:<br>
&gt; --1st para: =A0&quot;.., it then sends=85&quot; -&gt; &quot;.., it the=
n MUST send =85&quot;<br>
&gt; --3rd para: needs normative language<br>
&gt; OLD:<br>
&gt; =A0 =A0In no event does<br>
&gt; =A0 =A0an attempt to reestablish connectivity with a lost neighbor all=
ow the<br>
&gt; =A0 =A0peer to remain in the neighbor table.<br>
&gt; NEW:<br>
&gt; =A0 =A0In the case of<br>
&gt; =A0 =A0an attempt to reestablish connectivity with a lost neighbor, th=
e peer<br>
&gt; =A0 =A0MUST not remain in the neighbor table.<br>
&gt; OR:<br>
&gt; =A0 =A0In the case of<br>
&gt; =A0 =A0an attempt to reestablish connectivity with a lost neighbor, th=
e peer<br>
&gt; =A0 =A0MUST be removed from the neighbor table.<br>
&gt; -- 4th para: &quot;should&quot; -&gt; &quot;SHOULD&quot; (2 cases), =
=A0&quot;use Pings&quot; -&gt; &quot;MUST use Pings&quot;<br>
&gt;<br>
&gt; -Section 9.7.2:<br>
&gt; --1st para: =A0&quot;..the failed peer are removed..&quot; -&gt; &quot=
;=85the failed peer MUST be removed..&quot;<br>
&gt; --2nd para: =A0&quot;=85the peer initiates=85&quot; -&gt; &quot;=85the=
 peer MUST initiate..&quot;<br>
&gt;<br>
&gt; -Section 9.7.3:<br>
&gt; --1st para after list: =A0&quot;is needed&quot; -&gt; &quot;is REQUIRE=
D&quot;<br>
&gt; --3rd para after list: =A0&quot;the peer sends an Update&quot; -&gt; &=
quot;the peer MUST send an Update&quot;<br>
&gt;<br>
&gt; -Section <a href=3D"http://9.7.4.4" target=3D"_blank">9.7.4.4</a>: =A0=
Needs a scrub for normative language<br>
&gt;<br>
&gt; -Section 9.9: Needs a scrub for normative language.<br>
&gt;<br>
&gt; -Section 10.1: General: Needs a lot of work to be specified using norm=
ative language. =A0The majority of the configuration elements are not speci=
fied using normative language - for example, terms such as permitted, allow=
ed, valid are used in statements rather than normative language<br>

&gt; or they are indicative of the need for normative language. =A0A specif=
ic example is in the definition for &quot;clients-permitted&quot;:<br>
&gt;<br>
&gt; OLD:<br>
&gt; =A0 =A0 =A0 This element represents whether clients are<br>
&gt; =A0 =A0 =A0 permitted or whether all nodes must be peers. =A0If it is =
set to<br>
&gt; =A0 =A0 =A0 &quot;true&quot; or absent, this indicates that clients ar=
e permitted. =A0If<br>
&gt; =A0 =A0 =A0 it is set to &quot;false&quot; then nodes are not allowed =
to remain clients<br>
&gt; =A0 =A0 =A0 after the initial join.<br>
&gt;<br>
&gt; NEW:<br>
&gt; =A0 =A0 =A0 This element represents whether clients are<br>
&gt; =A0 =A0 =A0 permitted or whether all nodes need to be peers. =A0If cli=
ents<br>
&gt; =A0 =A0 =A0 are permitted, the element MUST be set to &quot;true&quot;=
 or absent.<br>
&gt; =A0 =A0 =A0 If the nodes are not allowed to remain clients after the<b=
r>
&gt; =A0 =A0 =A0 initial join, the element MUST be set to &quot;false&quot;=
.<br>
&gt;<br>
&gt; --Section 10.1 - 4th para after the element list states that &quot;All=
 of the non optional values MUST be provided&quot;. =A0However, the list of=
 elements in the previous paragraph are not specifically identified as non =
optional. =A0I think the first 3 are mandatory. =A0So, I would suggest to r=
e-word the 3rd paragraph as follows and delete the 1st sentence in the 4th =
paragraph noted above:<br>

&gt; OLD:<br>
&gt; =A0 =A0In addition, the kind element contains the following elements:<=
br>
&gt; =A0 =A0max-count: =A0the maximum number of values which members of the=
 overlay<br>
&gt; =A0 =A0 =A0 must support.<br>
&gt; =A0 =A0data-model: =A0the data model to be used.<br>
&gt; =A0 =A0max-size: =A0the maximum size of individual values.<br>
&gt; =A0 =A0access-control: =A0the access control model to be used.<br>
&gt; =A0 =A0max-node-multiple: =A0This is optional and only used when the a=
ccess<br>
&gt; =A0 =A0 =A0 control is NODE-MULTIPLE. =A0This indicates the maximum va=
lue for<br>
&gt; =A0 =A0 =A0 the i counter. =A0This is an integer greater than 0.<br>
&gt;<br>
&gt; NEW:<br>
&gt; =A0 =A0In addition, the kind element MUST contain the following elemen=
ts:<br>
&gt; =A0 =A0max-count: =A0the maximum number of values which members of the=
 overlay<br>
&gt; =A0 =A0 =A0 must support.<br>
&gt; =A0 =A0data-model: =A0the data model to be used.<br>
&gt; =A0 =A0max-size: =A0the maximum size of individual values.<br>
&gt; =A0 =A0access-control: =A0the access control model to be used.<br>
&gt;<br>
&gt; =A0 =A0The kind element MAY also contain the following element:<br>
&gt; =A0 =A0max-node-multiple: =A0if the access control is NODE-MULTIPLE,<b=
r>
&gt; =A0 =A0 =A0 this element MAY be included. This indicates the maximum v=
alue for<br>
&gt; =A0 =A0 =A0 the i counter. =A0It MUST be an integer greater than 0.<br=
>
&gt;<br>
&gt; --Section 10.1, next to last para: There&#39;s no normative language, =
but it seems there should be since it is specifying specification computati=
ons and encoding that I believe are required.<br>
&gt;<br>
&gt; - Section 10.2: =A0Needs more normative language:<br>
&gt;<br>
&gt; -- 2nd para:<br>
&gt; OLD: This value is provided by the user or some other out of band<br>
&gt; =A0 =A0 =A0provisioning mechanism.<br>
&gt;<br>
&gt; NEW: This value MUST be provided by the user or some other out of band=
<br>
&gt; =A0 =A0 =A0provisioning mechanism.&quot;<br>
&gt;<br>
&gt; -- 3rd para:<br>
&gt; OLD:<br>
&gt; =A0 =A0Once an address and URL for the configuration server is determi=
ned,<br>
&gt; =A0 =A0the peer forms an HTTPS connection to that IP address.<br>
&gt; NEW:<br>
&gt; =A0 =A0Once an address and URL for the configuration server is determi=
ned,<br>
&gt; =A0 =A0the peer MUST form an HTTPS connection to that IP address.<br>
&gt;<br>
&gt; -- 4th para: =A0&quot;which replaces&quot; -&gt; =A0&quot;which MUST r=
eplace&quot;<br>
&gt;<br>
&gt; -- 5th para: =A0&quot;nodes obtain the&quot; -&gt; &quot;nodes MUST ob=
tain the&quot;<br>
&gt;<br>
&gt; - Section 10.3:<br>
&gt; -- 3rd para: =A0&quot;is performed&quot; -&gt; &quot;MUST be performed=
&quot;.<br>
&gt; -- 3rd para: Bullets need to be modified to normative.<br>
&gt; -- 4th para: &quot;the certificate contains&quot; -&gt; &quot;the cert=
ificate MUST contain&quot;<br>
&gt; -- para after 2nd set of bullets: =A0needs normative language.<br>
&gt; -- 2nd para after 2nd set of bullets: =A0&quot;The node then reads=85&=
quot; -&gt; =A0&quot;The node MUST then use=85&quot;<br>
&gt;<br>
&gt; - Section 10.5:<br>
&gt; --Second para: &quot;the joining node first forms&quot; -&gt; &quot;th=
e joining node MUST first form&quot;<br>
&gt; --3rd para: =A0text uses the phrase &quot;it can note the Node-ID in t=
he response and use this Node-ID to start sending requests&quot;. =A0It&#39=
;s not clear whether the use of the Node-ID is a MAY or a MUST.<br>
&gt;<br>
&gt; - Section 12. I&#39;m assuming that the security directorate has revie=
wed this in detail, thus my focus in reviewing this section was on general =
understanding. The biggest issues is that there is NO normative language at=
 all in the security section. =A0As in other sections, terms like &quot;nee=
d&quot;, &quot;are/is used/sent, etc.&quot;, =A0&quot;ensure&quot;, lower c=
ase reserved words rather than upper case, etc. are used when normative lan=
guage ought to have been used.<br>

&gt;<br>
&gt;<br>
&gt; - Section 13. IANA Registrations:<br>
&gt; - General: there seem to be several registries for which the usage/req=
uirement is unclear as there&#39;s no mention of such in the body of the do=
cument. =A0In general, references to the sections in the document describin=
g the information included in the registries would be more than helpful.<br=
>

&gt;<br>
&gt; - Section 13.5: Creates a RELOAD Application Registry, but the use and=
 need for such isn&#39;t described elsewhere in the document<br>
<br>
</div></div>Section 5.5.2.1 defines the usage of this and contains the text=
<br>
<br>
 =A0 =A0 =A0A 16-bit application-id as defined in the Section 13.5. =A0This=
<br>
 =A0 =A0 =A0number represents the IANA registered application that is going=
 to<br>
 =A0 =A0 =A0send data on this connection.</blockquote><div><br></div><div>[=
MB] Okay. I missed that - sorry - I thought I searched the text and couldn&=
#39;t find it. [/MB]</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br>
&gt;<br>
&gt; - Section 13.12. Forwarding Options Registry. SEction 5.3.2.3 seems to=
 define three flags for the Forwarding options type, so it&#39;s not clear =
to me why this registry has just &quot;invalid&quot; and &quot;reserved&quo=
t;<br>

&gt;<br>
<br>
</div>The registry is for the ForwardingOptionsType code points and not the=
 flags. Any new forwarding option could use any of these flags. The flags o=
nly indicate who needs to understand the the forwarding option.<br></blockq=
uote>
<div>[MB] Maybe add some text around that. [/MB]=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
<div class=3D"im"><br>
&gt;<br>
&gt; - Section 13.15: =A0Defines/registers a RELOAD URI schema but there is=
 no mention of this URI anywhere else in the document. =A0In what context i=
s it used?<br>
<br>
</div>It would be used by other specifications that use Reload. It&#39;s no=
t used inside of reload itself. Folks wanted it defined here so we kept it =
consistent and other specs could use the URI.<br></blockquote><div>[MB] May=
be add some text around that. [/MB]=A0</div>
<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>
&gt;<br>
&gt;<br>
&gt; Minor =A0Issues:<br>
&gt; ---------------------<br>
&gt;<br>
&gt; - Section 1.2.1, 2nd paragraph: I don&#39;t understand the example as =
to why a single application requires multiple usages - i.e, why voicemail? =
=A0Isn&#39;t the intent to say that an application might need to use both S=
IP and XMPP - i.e., you wouldn&#39;t define a &quot;usage&quot; for an appl=
ication, would you?<br>

</div>storing voicemail in the DHT would require a different usage than the=
 type of rendezvous service of XMPP or SIP<br>
<div class=3D"im"><br>
&gt;<br>
&gt; - Section 2. Some of the definitions use terms that are not yet define=
d, so that&#39;s not particularly helpful - i.e,. Attach and Update are use=
d. In some cases (e.g., Connection Table), you could just delete the statem=
ent with the reference.<br>

&gt;<br>
<br>
</div>I&#39;m not sure how to resolve this. I agree that by the time we get=
 to the definition, if you have not read the rest of the document, the sent=
ence, &quot; This includes nodes with which Attach handshakes have<br>

 =A0 =A0 =A0been done but which have not sent any Updates.&quot; does not c=
urrently mean something that you can understand. But after reading the docu=
ment, this sense helps clear up something implementors were confused about =
so I definitely don&#39;t want to loose it. I&#39;d like to fix this but no=
t sure what you are suggesting. Are you suggesting just saying in these ter=
ms are defined later with a forward reference and leaving the sentence ther=
e?<br>
</blockquote><div>[MB] Yes. I think a forward reference would be extremely =
helpful. =A0Per my comment about alphabetizing below, the same concept appl=
ies. =A0While folks will likely need to work from both a hard and softcopy =
to review this document (as I did while reviewing), I think it should be po=
ssible to read a hardcopy. =A0In particular given that this document will r=
equire multiple reads to really get things. =A0[/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<div><div></div><div class=3D"h5"><br>
<br>
&gt; - Section 3.3, last paragraph. =A0Add a reference to 5.4.2.4 =A0after =
&quot;RouteQuery method&quot;<br>
&gt;<br>
&gt; - Section 5.1: &quot;If any of these are incorrect=85&quot; =A0- need =
to specify what qualifies as &quot;incorrect&quot; - is it wrong formatting=
, invalid header field<br>
&gt; value, etc.?<br>
&gt;<br>
&gt; - Section 5.1.2:<br>
&gt; --1st paragraph: I have no idea what the &quot;other three cases&quot;=
 references.<br>
&gt;<br>
&gt; - Section 5.2: &quot;may be configured&quot; -&gt; &quot;can be config=
ured&quot;, =A0&quot;alternative<br>
&gt; routing algorithms may be selected&quot; -&gt; &quot;alternative routi=
ng algorithms MAY be selected&quot;<br>
&gt;<br>
&gt; - Section 5.3: =A0The three parts of the messages are listed and the l=
ast sentence says that &quot;The following sections describe the format of =
each part of the message&quot;, but there are 4 sub-sections in 5.3, with t=
he first section NOT describing one of the three parts of the messages. =A0=
I suggest to strike that last sentence and just put references to the secti=
ons in the list items for each of the three messages.<br>

&gt;<br>
&gt; -Section 5.3.3:<br>
&gt; --&quot;critical&quot; description: =A0&quot;Whether this extension mu=
st be..&quot; &quot;Whether this extension needs to be=85&quot;<br>
&gt;<br>
&gt; -Section 5.3.4: =A01st para after certificate structure: =A0&quot;may =
contain&quot; -&gt; &quot;MAY contain&quot;<br>
&gt;<br>
&gt; -Section 5.5: It would be helpful to highlight that foundation, priori=
ty and type are based on ICE, in particular since ICE is not discussed unti=
l the subsequent section - e.g., &quot;the foundation production&quot; -&gt=
; &quot;the ICE foundation production&quot;.<br>

&gt;<br>
&gt; - Section 5.6:<br>
&gt; -- The last three paragraphs are confusing.<br>
&gt; ---In particular, it&#39;s not clear what algorithms are being referen=
ced in this sentence:<br>
&gt; =A0 &quot;We will first define each of these algorithms, then<br>
&gt; =A0 =A0define overlay link protocols that use them.&quot;<br>
&gt; --- In the note paragraph, I believe &quot;These protocols have been c=
hosen=85&quot; is referring to the three overlay link protocols supported b=
y RELOAD per this document.<br>
&gt; ---The Note to implementors paragraph seems out of context<br>
&gt; --- Per my next comment, I suggest to move the detailed discussion of =
future overlay link protocols to the appendix, so some of this text may be =
relevant only to that.<br>
&gt;<br>
&gt; -Section 5.6.1: =A0I suggest that the sub-sections in this section be =
moved to an appendix and a reference to such be added.<br>
&gt;<br>
&gt; -Section 5.6.3.1.1, next to the last paragraph:<br>
&gt; &quot;when a link may be failing&quot; -&gt; &quot;when a link might b=
e failing&quot;<br>
&gt;<br>
&gt; - Section 9.1: While this is an overview, it seems to me that some of =
this is describing normative behavior (that I don&#39;t see specified else)=
. =A0Per the general comment, I would reword the first sentence as follows:=
<br>

&gt; OLD:<br>
&gt; =A0 =A0The algorithm described here is a modified version of the Chord=
<br>
&gt; =A0 =A0algorithm.<br>
&gt; NEW:<br>
&gt; =A0 =A0 The algorithm described here, Chord-RELOAD is a modified versi=
on<br>
&gt; =A0 =A0 of the Chord algorithm.<br>
&gt;<br>
&gt; - Section 10.3, 1st para: =A0&quot;required&quot; -&gt; &quot;REQUIRED=
&quot;<br>
&gt;<br>
&gt; - Section 10.3.1, last sentence: &quot;must&quot; =A0-&gt; &quot;MUST&=
quot;<br>
&gt;<br>
&gt; - Section 10.4, 1st para, last sentence: &quot;should use&quot; -&gt; =
&quot;SHOULD use&quot;<br>
&gt;<br>
&gt; - Section 11 - examples:<br>
&gt; --General - there are no detailed messages shown anywhere for the exam=
ples. There should be at least one, in particular given the comment above a=
bout the RELOAD URI that is registered, but not mentioned anywhere else in =
the document.<br>

&gt; --first example (see my nit below about the examples not being numbere=
d or labeled in any way): =A0The third sentence says that &quot;It gets rou=
ted to the admitting peer (AP), yet the flow shows that the message first g=
ets routed to the PP and then onto AP. It would be helpful if that were cla=
rified.<br>

&gt; - =A0Also (general), the text mentions the use of ICE. =A0It&#39;s not=
 clear to me exactly where in the flow that happens - it would be good to a=
nnotate such (i.e., in a similar manner as the TLS is illustrated).<br>
&gt; - next to the last example (text on page 131, diagram on page 132): I&=
#39;m quite confused as the text states that JP has received an update from=
 AP and thus now knows APs predecessors, which are also JP&#39;s predecesso=
rs, so JP Attaches to them. However, the diagram does not show JP getting a=
n Update from AP and it shows JP doing Updates to PPP and PP rather than At=
taches (as the text suggests).<br>

&gt;<br>
&gt; - Section 13.10. Overlay link types: These specific string types are n=
ot used elsewhere in the document. =A0Suggest that a reference to 5.6 be ad=
ded and these particular strings be included in parenthesis after the items=
 in the list.<br>

<br>
</div></div>makes sense<br>
<div class=3D"im"><br>
<br>
&gt;<br>
&gt;<br>
&gt; - Section 13.16, Security considerations portion:<br>
&gt; -- The first sentence doesn&#39;t make sense. Did you mean?<br>
&gt; =A0 =A0&quot;This media type is typically not used to<br>
&gt; =A0 =A0transport information that needs to be kept confidential,<br>
&gt; =A0 =A0however, there are cases where the integrity of the information=
 is<br>
&gt; =A0 =A0important.&quot;<br>
<br>
</div>yes - that is much better - this text was added late and received lit=
tle review<br>
<div class=3D"im"><br>
&gt; -- &quot;then the contents of the file need to be=85&quot; -&gt; &quot=
;then the contents of the file MUST be =85&quot;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Nits:<br>
&gt; -----<br>
&gt; - General: kind is sometimes &quot;Kind&quot; and sometimes &quot;kind=
&quot;. =A0The former is more readable and highlights it as a reserved word=
.<br>
<br>
</div>=A0Seems reasonable<br>
<div class=3D"im"><br>
&gt;<br>
&gt; - Section 2.<br>
&gt; --General: It would be helpful if the terms were alphabetized.<br>
<br>
</div>this is easy to do but complicates the forward reference problem. Tho=
ughts on what is best?<br></blockquote><div>[MB] See my comment above - I t=
hink a note that term x is defined below is fine. If they&#39;re alphabetiz=
ed the unknown term is easy to fine. [/MB]=A0</div>
<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>
&gt; --Node: &quot;We use the term &quot;Node&quot; to refer to =85&quot; -=
&gt; &quot;Refers to =85&quot;<br>
&gt;<br>
&gt; - Section 3.2:<br>
&gt; -- 2nd para, last sentence: =A0&quot;refer such&quot; -&gt; &quot;refe=
r to such&quot;<br>
</div>that needs to b fixed<br>
<div class=3D"im"><br>
&gt; -- 3rd para, 1st sentence: =A0&quot;concept&quot; -&gt; &quot;entity&q=
uot;<br>
&gt;<br>
&gt; - Section 4.1.4,<br>
</div>(this is section 4.1.1 for others reading this)<br>
<div class=3D"im"><br>
&gt; 4th paragraph: I&#39;m still not getting the applicability of voicemai=
l as a RELOAD Kind (per the reference also in section 1.2.1). =A0I guess yo=
u are talking about a voicemail message (in this case) and a server or appl=
ication in section 1.2.1? =A0 Voicemail just does not seem like an obvious =
example to me.<br>

<br>
</div>All it is trying to say is the size of a storing the audio for a voic=
email in the overlay is much larger than saving a link. Note that several p=
eople in the WG think it is nuts to try and save a full voice message in th=
e overlay and several others think the opposite. This argument was avoid by=
 explicitly mention in this draft the example of voicemail.<br>

<div class=3D"im"><br>
&gt;<br>
&gt; - Section 5.1.1, last bullet: =A0&quot;In that case,=85&quot; -&gt; =
=A0&quot;In the latter case, =85&quot;<br>
</div>make sense<br>
<div class=3D"im"><br>
<br>
&gt;<br>
&gt; - Section 5.1.2:<br>
&gt; -- 2nd para: =A0&quot;arrange&quot; -&gt; &quot;ensure&quot;, =A0&quot=
;This may be arranged&quot; -&gt; &quot;This can be arranged=85&quot;<br>
</div>make sense<br>
<div class=3D"im"><br>
&gt; -- 3rd para (1st after bullets): It&#39;s not clear that A=85E is a se=
t of ordered nodes in the example. I would suggest to reword as:<br>
&gt; OLD:<br>
&gt; =A0 =A0As an example of the first strategy, if node D<br>
&gt; NEW:<br>
&gt; =A0 Consider an example with nodes A, B, C, D and E, respectively. =A0=
If<br>
&gt; =A0 node D=85.<br>
</div>ok<br>
<div class=3D"im"><br>
&gt;<br>
&gt; - Section <a href=3D"http://5.3.1.1" target=3D"_blank">5.3.1.1</a>: Fi=
rst two sentences can be reworded more succinctly - you&#39;re not really p=
roviding definitions here, put rather describing the<br>
&gt; the syntax for and providing examples illustrative of the presentation=
 language.<br>
&gt;<br>
&gt; OLD:<br>
&gt; =A0 =A0The following definitions are used throughout RELOAD and so are=
<br>
&gt; =A0 =A0defined here.<br>
<br>
</div>we really are defining opaque and true and false here<br>
<div class=3D"im"><br>
&gt; They also provide a convenient introduction to how to<br>
&gt; =A0 =A0read the presentation language.<br>
&gt; NEW:<br>
&gt; =A0 =A0This section provides an introduction to the presentation langu=
age<br>
&gt; =A0 =A0used throughout RELOAD.<br>
&gt;<br>
&gt; - Section <a href=3D"http://5.3.3.1" target=3D"_blank">5.3.3.1</a>: Er=
ror_Data_Too_Old is duplicated.<br>
</div>that&#39;s embarrassing :-)<br>
<div class=3D"im"><br>
&gt;<br>
&gt; - Section <a href=3D"http://5.5.1.6" target=3D"_blank">5.5.1.6</a>: Ad=
d references for SCTP and DCCP.<br>
&gt;<br>
&gt; - Section <a href=3D"http://6.4.1.3" target=3D"_blank">6.4.1.3</a>: =
=A0The reference to &quot;this Version&quot; is superfluous. Propose the fo=
llowing change:<br>
&gt; OLD:<br>
&gt; =A0 =A0This version of RELOAD (unlike previous versions) does not have=
 an<br>
&gt; =A0 =A0explicit Remove operation.<br>
&gt; NEW:<br>
&gt; =A0 =A0RELOAD does not have an explicit Remove operation.<br>
<br>
</div>make sense<br>
<div class=3D"im"><br>
&gt;<br>
&gt; - Section 9: General. The first sentence states that the algorithm def=
ined here is referred to as &quot;chord-reload&quot;, however, subsequent s=
ections don&#39;t seem to use that term.<br>
<br>
</div>uh, that should have been upper case in this section.<br>
<div class=3D"im"><br>
&gt; =A0It would be more clear if that term was used. And, really, it would=
 be more consistent to use the term Chord-RELOAD. However, this should also=
 be consistent with the IANA-Registration which has CHORD-RELOAD.<br>
&gt;<br>
&gt; - Section 9.7.4.3, 3rd para:<br>
&gt; -- Remove &quot;Note to implementers&quot;. =A0Text already highlights=
 that the text is specific to implementations.<br>
&gt; -- &quot;may be found&quot; -&gt; &quot;can be found&quot;<br>
&gt;<br>
&gt; - Section 9.8: =A0&quot;For this topology plugin&quot; -&gt; &quot;For=
 Chord-RELOAD&quot;<br>
&gt;<br>
&gt; - Section 10.2, 2nd para: =A0&quot;determines&quot; -&gt; &quot;determ=
ining&quot;<br>
</div>needs to be fixed<br>
<div class=3D"im"><br>
&gt;<br>
&gt; - Section 11:<br>
&gt; - General: there are no labels for any of the call flows, so it&#39;s =
not always clear what the text is referring to. =A0In general, I think the =
text precedes the flow.<br>
&gt; - &quot;abbreviation&quot; -&gt; &quot;abbreviations&quot;<br>
</div>needs to be fixed<br>
<div class=3D"im"><br>
&gt;<br>
&gt; - Section 13.16:<br>
&gt; --Interoperability considerations: =A0&quot;knows&quot; -&gt; &quot;kn=
own&quot;<br>
</div>needs to be fixed<br>
<br>
&gt;<br>
&gt; - Section 14: &quot;provied&quot; -&gt; &quot;provided&quot;<br>
needs to be fixed<br>
<div class=3D"im">&gt;<br>
&gt; - Appendix C: Delete now - it&#39;s totally useless as is.<br>
</div>make sense<br>
<div><div></div><div class=3D"h5"><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>
</div></div></blockquote></div><br></div>

--bcaec5196dddd09a9d04aa94cec1--

From mary.ietf.barnes@gmail.com  Mon Aug 15 17:55:44 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A79228308 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 17:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.415
X-Spam-Level: 
X-Spam-Status: No, score=-103.415 tagged_above=-999 required=5 tests=[AWL=0.183, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VNPHAipme6fR for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 17:55:43 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 29FB8228307 for <ietf@ietf.org>; Mon, 15 Aug 2011 17:55:43 -0700 (PDT)
Received: by vxi29 with SMTP id 29so5371294vxi.31 for <ietf@ietf.org>; Mon, 15 Aug 2011 17:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1s69lVo3O8tG4cKg890vL9+psRbJteV8pvgU9e0uQ5w=; b=sD2f/jxjOmsTvrZIedb8EwPOUzDzN1nCckIgLUemnN0g5a0Fd/m5lvvI1g7XcwApyP GUSmGcppYjLGSL9GP7wJ5A1GB9BIihcmaalmHRcZBmdcPyHIQ+12JLoTNZ2XU5p4lM+2 qRyIy8tZJQ4RrZ1SeE/GHnL50a85s+Npv5Gzw=
MIME-Version: 1.0
Received: by 10.52.173.208 with SMTP id bm16mr4310119vdc.49.1313456189902; Mon, 15 Aug 2011 17:56:29 -0700 (PDT)
Received: by 10.52.160.71 with HTTP; Mon, 15 Aug 2011 17:56:29 -0700 (PDT)
In-Reply-To: <6AC691A0-2E6C-4704-89AF-74602F1EB19F@harvard.edu>
References: <CAHBDyN47xqCP=irYZ7bV97W2dqvPKW8giMAW+_A8UYJ3W05K+w@mail.gmail.com> <6D9C4F6D-53B4-4F77-AB4E-45A4BA911406@cisco.com> <6AC691A0-2E6C-4704-89AF-74602F1EB19F@harvard.edu>
Date: Mon, 15 Aug 2011 19:56:29 -0500
Message-ID: <CAHBDyN7hPbLTKsSJaz+mjTOJ8s9+GbkmxuhKPOMFZatnF-MEuA@mail.gmail.com>
Subject: Re: Gen-ART Review: Last Call <draft-ietf-p2psip-base-17.txt>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Scott O. Bradner" <sob@harvard.edu>
Content-Type: multipart/alternative; boundary=bcaec5196ddda08dd704aa94d917
Cc: Cullen Jennings <fluffy@cisco.com>, IETF-Discussion list <ietf@ietf.org>, draft-ietf-p2psip-base.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 00:55:44 -0000

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

Someone might want to point this out to the IESG then, as that has not been
my recent experience.  Not even for structures or definition of elements -
it was suggested that the use of the terms mandatory and optional (which I
thought was quite precise when defining data elements) needed to be reworded
using 2119 language.  Perhaps, I should have pushed back, but I did not
think it was worth the effort.

Mary.

On Thu, Aug 11, 2011 at 7:50 PM, Scott O. Bradner <sob@harvard.edu> wrote:

> fwiw - the author of 2119 thinks that less is more when it comes to the use
> of these terms
>
> see, as Cullen points out, Section 6
>
> but there is a balance - for example, if you define a structure and say
> that all fields are required, it is redundant to
> use MUST with each example of using the structure
>
> Scott
>
> On Aug 11, 2011, at 8:43 PM, Cullen Jennings wrote:
>
> >
> > Thanks for the detailed review - you caught some good stuff. Most of this
> makes essence but we should probably talk about usage of 2119 language.
> >
> > On Aug 9, 2011, at 16:05 , Mary Barnes wrote:
> >> simple
> >> =======================================================================
> >>
> >> Document: draft-ietf-p2psip-base-17
> >> Reviewer:  Mary Barnes
> >> Review Date:  9 August  2011
> >> IETF LC End Date: 22 July 2011
> >>
> >> Summary: Not Ready.
> >>
> >> Comments:
> >> ----------------
> >> The document is very a dense (with detailed technical information) and
> long (150 page) specification for a Peer-to-peer signaling protocol.  While
> the overall technical functionality seems fairly correct and thoroughly
> specified, the primary issue is a tremendous lack of normative language in
> the main body of the document.  Non-inclusive details of such are included
> below.
> >
> > The 2119 MUST/SHOULD/MAY terms are simply abbreviations for some words
> defined in 2119, and different WGs have different styles about how
> extensively they should be used. P2PSIP has obviously been on the more
> sparing side of that spectrum. This isn't to say that there aren't any
> places where it would be useful to add such language, but rather that our
> policy has been to add it principally where there is likely ambiguity,
> rather than everywhere where behavior is defined. I'll work thought these
> and see where they might help reduce the chance of a an implementers doing
> the wrong thing but in generally when we define a structure in something
> like ASN.1 or ABNF, if the structure always has a field X, we just use the
> language like ASN.1 or ABNF to indicate it always has that. We don't  also
> say it MUST be there.
> >
>
>
>
>
>
>
>
>

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

Someone might want to point this out to the IESG then, as that has not been=
 my recent experience. =A0Not even for structures or definition of elements=
 - it was suggested that the use of the terms mandatory and optional (which=
 I thought was quite precise when defining data elements) needed to be rewo=
rded using 2119 language. =A0Perhaps, I should have pushed back, but I did =
not think it was worth the effort. =A0<div>
<div><br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Thu, Aug =
11, 2011 at 7:50 PM, Scott O. Bradner <span dir=3D"ltr">&lt;<a href=3D"mail=
to:sob@harvard.edu">sob@harvard.edu</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex;">
fwiw - the author of 2119 thinks that less is more when it comes to the use=
 of these terms<br>
<br>
see, as Cullen points out, Section 6<br>
<br>
but there is a balance - for example, if you define a structure and say tha=
t all fields are required, it is redundant to<br>
use MUST with each example of using the structure<br>
<font color=3D"#888888"><br>
Scott<br>
</font><div><div></div><div class=3D"h5"><br>
On Aug 11, 2011, at 8:43 PM, Cullen Jennings wrote:<br>
<br>
&gt;<br>
&gt; Thanks for the detailed review - you caught some good stuff. Most of t=
his makes essence but we should probably talk about usage of 2119 language.=
<br>
&gt;<br>
&gt; On Aug 9, 2011, at 16:05 , Mary Barnes wrote:<br>
&gt;&gt; simple<br>
&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
>
&gt;&gt;<br>
&gt;&gt; Document: draft-ietf-p2psip-base-17<br>
&gt;&gt; Reviewer: =A0Mary Barnes<br>
&gt;&gt; Review Date: =A09 August =A02011<br>
&gt;&gt; IETF LC End Date: 22 July 2011<br>
&gt;&gt;<br>
&gt;&gt; Summary: Not Ready.<br>
&gt;&gt;<br>
&gt;&gt; Comments:<br>
&gt;&gt; ----------------<br>
&gt;&gt; The document is very a dense (with detailed technical information)=
 and long (150 page) specification for a Peer-to-peer signaling protocol. =
=A0While the overall technical functionality seems fairly correct and thoro=
ughly specified, the primary issue is a tremendous lack of normative langua=
ge in the main body of the document. =A0Non-inclusive details of such are i=
ncluded below.<br>

&gt;<br>
&gt; The 2119 MUST/SHOULD/MAY terms are simply abbreviations for some words=
 defined in 2119, and different WGs have different styles about how extensi=
vely they should be used. P2PSIP has obviously been on the more sparing sid=
e of that spectrum. This isn&#39;t to say that there aren&#39;t any places =
where it would be useful to add such language, but rather that our policy h=
as been to add it principally where there is likely ambiguity, rather than =
everywhere where behavior is defined. I&#39;ll work thought these and see w=
here they might help reduce the chance of a an implementers doing the wrong=
 thing but in generally when we define a structure in something like ASN.1 =
or ABNF, if the structure always has a field X, we just use the language li=
ke ASN.1 or ABNF to indicate it always has that. We don&#39;t =A0also say i=
t MUST be there.<br>

&gt;<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div></div>

--bcaec5196ddda08dd704aa94d917--

From yaakov_s@rad.com  Tue Aug 16 00:26:41 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A57421F8B12 for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 00:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mn8ehSSiqfSt for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 00:26:40 -0700 (PDT)
Received: from antivir2.rad.co.il (mx2-q.rad.co.il [80.74.100.144]) by ietfa.amsl.com (Postfix) with ESMTP id AF2FD21F8B16 for <ietf@ietf.org>; Tue, 16 Aug 2011 00:26:39 -0700 (PDT)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir2.rad.co.il with ESMTP; 16 Aug 2011 10:27:25 +0300
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; Tue, 16 Aug 2011 10:29:27 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0289.001; Tue, 16 Aug 2011 10:29:27 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: FW: [PWE3] Last Call: <draft-ietf-pwe3-mpls-tp-gal-in-pw-01.txt> (Using	the	Generic Associated Channel Label for Pseudowire in	MPLS-TP) to Proposed Standard
Thread-Topic: [PWE3] Last Call: <draft-ietf-pwe3-mpls-tp-gal-in-pw-01.txt> (Using	the	Generic Associated Channel Label for Pseudowire in	MPLS-TP) to Proposed Standard
Thread-Index: AQHMWSVoDB7zMKxfwkqSOY+VjORTc5UfEOjw
Date: Tue, 16 Aug 2011 07:29:26 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903E9B12E@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 07:26:41 -0000

I am not sure how this document moved so quickly from its status as content=
ious WG document=20
to being laid before the IESG for consideration,
but I don't believe we ever received answers to serious questions regarding=
 backwards compatibility.

The draft claims to solve the following problem :
   According to the MPLS-TP requirement document [RFC5654], it is=20
   necessary that MPLS-TP mechanisms and capabilities be able to=20
   interoperate with the existing IETF MPLS [RFC3031] and IETF PWE3=20
   [RFC3985] architectures appropriate.

Whatever "architectures appropriate" means ...
(another sign of the haste with which this was prepared.)

However, it accomplishes exactly the opposite.=20
It breaks interoperability with existing PW implementations.

The true goal of the draft appears a bit later on :
   The inconsistency between the usage of the GAL with MPLS PWs and=20
   MPLS-TP PWs may cause unnecessary implementation differences and is=20
   in disagreement with the MPLS-TP requirements.

Accordingly, the draft allows PWs to indicate the associated channel by usi=
ng the GAL,
(i.e., making it a generic associated channel, rather than a PW associated =
channel).
This indeed enhances interoperability with all the (presently nonexistent) =
MPLS-TP implementations,
but completely breaks interoperability with the very broad installed base o=
f PW implementations.

Why is this the case ?
The draft mandates the GAL appearing at the bottom of stack
   In MPLS-TP, the GAL MUST be used with packets on a G-ACh on=20
   LSPs, Concatenated Segments of LSPs, and with Sections, and=20
   MAY be used with PWs. It MUST always be at the bottom of the=20
   label stack (i.e., S bit set to 1).

Bottom of stack has been the label position of the PW label for many years,
and this position is mandated by multiple RFCs, e.g. 3985 and 4447
   Note that the PW label must always
   be at the bottom of the packet's label stack.

Present PW implementations receiving the PW label with stack bit cleared,
and a GAL at the bottom position will choke and, at best, discard the packe=
t.
At worst, the GAL may coincide with a legitimate PW label, and the customer=
 will be
flooded with garbage.

This issue can not be avoided by limiting the use of this technique to "new=
" MPLS-TP
based scenarios, since PWs can be set up to cross from MPLS-TP domains into=
 traditional ones.


Y(J)S



-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of The=
 IESG
Sent: Friday, August 12, 2011 22:24
To: IETF-Announce
Cc: pwe3@ietf.org
Subject: [PWE3] Last Call: <draft-ietf-pwe3-mpls-tp-gal-in-pw-01.txt> (Usin=
g the Generic Associated Channel Label for Pseudowire in MPLS-TP) to Propos=
ed Standard


The IESG has received a request from the Pseudowire Emulation Edge to
Edge WG (pwe3) to consider the following document:
- 'Using the Generic Associated Channel Label for Pseudowire in MPLS-TP'
  <draft-ietf-pwe3-mpls-tp-gal-in-pw-01.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-08-26. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes the requirements for using the Generic
   Associated Channel Label (GAL) in Pseudowires (PWs) in MPLS-TP
   networks, and provides an update to the description of GAL usage in
   [RFC5586] by removing the restriction that is imposed on using GAL
   for PWs especially in MPLS-TP environments.


From ron.even.tlv@gmail.com  Tue Aug 16 00:36:16 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8B621F8B7E; Tue, 16 Aug 2011 00:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8l8jYzd6VtQW; Tue, 16 Aug 2011 00:36:15 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B6FAD21F8B79; Tue, 16 Aug 2011 00:36:13 -0700 (PDT)
Received: by wyg8 with SMTP id 8so4573717wyg.31 for <multiple recipients>; Tue, 16 Aug 2011 00:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=sq5eGhHUgBCdB4nzOm6DDOa5cG3C1jdrOL3FmajqF74=; b=KfpBGw4jT2jLYIY3DR9xCzy1rfXxxTPdsRDjKEA2HEgHR1YyxBWNGjnsupxfLVO4yu WIiP+XeVH5r1+BYiWOOe3Wyj2zycMKCONXYj4MS1yuCgietdDZMK5dia9neybkwv0IUQ R03sTOueE3udzfeftpX3f4fOogXJdUZluTIt8=
Received: by 10.216.69.77 with SMTP id m55mr4148110wed.11.1313480216273; Tue, 16 Aug 2011 00:36:56 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-178-13-148.red.bezeqint.net [79.178.13.148]) by mx.google.com with ESMTPS id y52sm141166wec.21.2011.08.16.00.36.52 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 16 Aug 2011 00:36:55 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-bmwg-igp-dataplane-conv-meth.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-bmwg-igp-dataplane-conv-meth-23
Date: Tue, 16 Aug 2011 10:36:12 +0300
Message-ID: <4e4a1e17.ca3ed80a.4704.0750@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0182_01CC5C00.54BE8830"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acxb5xxvfOU2tNjKRxSOCqASB0eHpg==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 07:36:16 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0182_01CC5C00.54BE8830
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

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

Document: draft-ietf-bmwg-igp-dataplane-conv-meth-23

Reviewer: Roni Even

Review Date: 2011-8-16

IETF LC End Date: 2011-8-19

IESG Telechat date: 

 

Summary: This draft is ready for publication as an informational RFC.  

 

Major issues:

 

Minor issues:

 

I find that the document provides in depth testing procedures and reporting.
What I think may be helpful is a recommendation about how many times to
repeat each of the tests to get more accurate results. Is there any
experience.

Maybe it will be good to have some text on experience from actual testing
that were done based on the document.

 

Nits/editorial comments:  

 

I noticed that the issue of normative references was discussed and I had
similar observation since the references in the terminology section are
normative and Po11t is in draft forms. Did you consider why they are
normative and not informative.

 


------=_NextPart_000_0182_01CC5C00.54BE8830
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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-ietf-bmwg-igp-dataplane-conv-meth-23<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date: 2011&#8211;8&#8211;16<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2011&#8211;8&#8211;19<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an informational RFC.&nbsp; =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I find =
that the document provides in depth testing procedures and reporting. =
What I think may be helpful is a recommendation about how many times to =
repeat each of the tests to get more accurate results. Is there any =
experience.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Maybe it =
will be good to have some text on experience from actual testing that =
were done based on the document.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:&nbsp; <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I noticed =
that the issue of normative references was discussed and I had similar =
observation since the references in the terminology section are =
normative and </span><a name=3Dref-Po11t><span lang=3DEN =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Po11t</span=
></a><span lang=3DEN =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> =
is</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> in draft =
forms. Did you consider why they are normative and not =
informative.<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0182_01CC5C00.54BE8830--


From mrex@sap.com  Tue Aug 16 08:07:58 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F6021F8B6E for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 08:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.01
X-Spam-Level: 
X-Spam-Status: No, score=-10.01 tagged_above=-999 required=5 tests=[AWL=0.239,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSxcFV3bYjQd for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 08:07:57 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 6D06A21F8B6B for <ietf@ietf.org>; Tue, 16 Aug 2011 08:07:57 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p7GF8hkC013257 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 16 Aug 2011 17:08:43 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108161508.p7GF8gOO004166@fs4113.wdf.sap.corp>
Subject: Re: IESG voting procedures
To: moore@network-heretics.com (Keith Moore)
Date: Tue, 16 Aug 2011 17:08:42 +0200 (MEST)
In-Reply-To: <645AFB89-1F26-4F07-B821-770CDF5DB2D3@network-heretics.com> from "Keith Moore" at Aug 14, 11 05:55:44 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 15:07:58 -0000

Keith Moore wrote:
> 
> I actually think that the "rough consensus" model is not well suited for
> IESG, because IESG rarely has enough members with the kind of expertise
> needed to make that kind of judgment.   The number of IESG members who
> review a typical document and really understand its implications is
> probably around 3-4.    Most of those voting "no objection" have
> probably not read the document, at least not in depth.  So in a case
> where there's one sponsoring AD voting yes and one AD voting discuss,
> it's really close to one or two in favor against one opposed.  But the
> way IESG votes, distorts this and makes it look like many against one.


While I agree to your later observation that some IESG ballots are
more like 1:1 or 2:1 (because of the many "no objection"s), I still
think that "rough consensus" should work for the IESG as well, and
primarily because of the "issue resolution process" that it requires,
rather than every IESG member being or becoming a technical expert
on each particular subject.


I believe that a certain "technical leadership" is desirable
_and_ possible, and dismissing "rough consensus" and as well of
some other mentioned ideas would reduce the IESG function to a
mostly clerical one.


IMHO the current ballot rules, especially those for standards action,
are not very well suited for corner cases, and they can (and sometimes
do) fail in an unsafe fashion.  I would appreciate if they would be
adjusted to fail in a safe fashion.


One of the corner cases being discussed is when there is active
dissent within the IESG, and how to cope with it.  I'm not sure
that there really is a problem.  The assertion that has been made
is that publishing a document (or approving a standards action)
would be the "safe" failure mode, and I'm violently opposed to
such a concept.  If there is a problem, fix the issue resolution
process.  Adjusting the ballot rules to ignore dissent seems like
a bad idea to me.


A somewhat different issue, which I am actually more concerned about,
is the unsafe failure in the lack-of-support situation.  Why do we
make it so hard to IESG to let a document "die"?  One single "yes"
and otherwise just "recuded" and "no objection" does not make
a very good safeguard.  It would seem much more sensible to require
at least two ADs to provide a "yes"--which means that they should
have performed some level of independent review of the document
the document writeups and at least parts of controversial discussion
(if that exists).  Or alternatively, leave at 1 "yes", but make the
responsible AD always recused for documents for which they requested
an IETF LC.


The issue is, if there is strong dissent, put the burden to resolve
the dissent or to convince at least two IESG members that remaining
dissent after issue resultion it is unjustified, on the document
submittor(s) rather than leaving the burden on the IESG alone,
as a procedural safeguard.


-Martin

From ghudson@mit.edu  Mon Aug 15 08:22:15 2011
Return-Path: <ghudson@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7B6A21F8BEC for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 08:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qx1A7zyB9Ona for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2011 08:22:15 -0700 (PDT)
Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by ietfa.amsl.com (Postfix) with ESMTP id 2958121F8BCB for <ietf@ietf.org>; Mon, 15 Aug 2011 08:22:15 -0700 (PDT)
X-AuditID: 1209190f-b7b44ae000000a24-5d-4e49393b12f8
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 0C.31.02596.B39394E4; Mon, 15 Aug 2011 11:20:27 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id p7FFMweU002252 for <ietf@ietf.org>; Mon, 15 Aug 2011 11:22:58 -0400
Received: from [192.168.1.4] (pool-173-48-218-114.bstnma.fios.verizon.net [173.48.218.114]) (authenticated bits=0) (User authenticated as ghudson@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p7FFMsRi018955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 15 Aug 2011 11:22:58 -0400 (EDT)
Subject: Re: [Ietf-krb-wg] Last Call: <draft-ietf-krb-wg-otp-preauth-18.txt> (OTP	Pre-authentication) to Proposed Standard
From: Greg Hudson <ghudson@MIT.EDU>
To: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <20110815145220.16779.50055.idtracker@ietfa.amsl.com>
References: <20110815145220.16779.50055.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 15 Aug 2011 11:22:54 -0400
Message-ID: <1313421774.16540.51.camel@t410>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrAIsWRmVeSWpSXmKPExsUixCmqrWtt6eln8LVF0+LZxvksDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKeHnvNHPBIY6Kq1uOsTUwnmPrYuTkkBAwkZjauI0VwhaTuHBv PVCci0NIYB+jxNzVX9ghnCOMEl/3PWKEcD4xSWyZe58FpEVYoE7i2OQ9TCA2m4CyxMGz38Di IkD2gZk3wMZyCjhJnF/4F2gsB1Czo8TTWY4gYWYBTYnW7b/ZQWwWAVWJQ2f3grXyCuhINKx9 zQhSzisgKPF3hzDEcdISs3v+MUG0yktsfzuHeQKjwCwkk2YhdMxCUrWAkXkVo2xKbpVubmJm TnFqsm5xcmJeXmqRrolebmaJXmpK6SZGcEBK8u9g/HZQ6RCjAAejEg/vinfufkKsiWXFlbmH GCU5mJREeU9YePoJ8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuGdaQSU401JrKxKLcqHSUlzsCiJ 8zbucPATEkhPLEnNTk0tSC2CycpwcChJ8P4HGSpYlJqeWpGWmVOCkGbi4AQZzgM0nA2khre4 IDG3ODMdIn+KUVFKnFcQGPNCAiCJjNI8uF5YwnjFKA70ijDvHpB2HmCyget+BTSYCWjwrV0e IINLEhFSUg2MLWFTf0ftMcl/k52suVbAyYwvJb3BJSX1779/bFOFhFkWrD91Te8cp/33Z1qB t6x3LFv5ZP18rc4lhwxDtDMXvDxed+Srw90ZNRcePA4NeJkb0CfZE3nW+twRZlvNz3Lzvq+4 IHT5dLHCk39fus8f+HM2+3ppaP2WubeOSDY2fEqTO7PLZIXCZCWW4oxEQy3mouJEAFfKMRLz AgAA
X-Mailman-Approved-At: Tue, 16 Aug 2011 08:44:34 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2011 15:22:16 -0000

I have a last-call comment about the KDC-generated nonce used in 4-pass
mode.  I would like the text in section 3.2 changed from:

        This nonce string MUST be as long as the longest key length of
        the symmetric key types that the KDC supports and MUST be chosen
        randomly.

to:

        This nonce string MUST contain a randomly chosen component at
        least as long as the armor key length.

This change was previously discussed in the working group and appears to
be non-controversial there; see
https://lists.anl.gov/pipermail/ietf-krb-wg/2011-August/009549.html and
replies by Sam, Gareth, and Henry.

A brief justification: this change will allow KDCs to encode a timestamp
into the nonce, allowing them to determine recentness of PA-OTP-REQUESTs
without using cookies.  A KDC can still use cookies or a replay cache to
ensure the non-replay of PA-OTP-REQUESTs if desired.  The client key
used to encrypt the nonce is always of the same enctype as the armor
key, so there is no need to refer to other key types supported by the
KDC.



From Alexander.Vainshtein@ecitele.com  Tue Aug 16 06:25:35 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 407EE21F8AD3 for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 06:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.713
X-Spam-Level: 
X-Spam-Status: No, score=-1.713 tagged_above=-999 required=5 tests=[AWL=0.488,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lh9nCPAXkg1V for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 06:25:35 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.130]) by ietfa.amsl.com (Postfix) with ESMTP id 90E8921F8ABD for <ietf@ietf.org>; Tue, 16 Aug 2011 06:25:34 -0700 (PDT)
Received: from [85.158.139.83:37724] by server-7.bemta-5.messagelabs.com id 31/3B-21792-5FF6A4E4; Tue, 16 Aug 2011 13:26:13 +0000
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-12.tower-182.messagelabs.com!1313501173!14692832!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [147.234.242.235]
Received: (qmail 1916 invoked from network); 16 Aug 2011 13:26:13 -0000
Received: from ilptbmg02-out.ecitele.com (HELO ilptbmg02.ecitele.com) (147.234.242.235) by server-12.tower-182.messagelabs.com with SMTP; 16 Aug 2011 13:26:13 -0000
X-AuditID: 93eaf2e8-b7b3eae00000414f-ad-4e4a692ed2ba
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Messaging Gateway) with SMTP id 5C.7D.16719.E296A4E4; Tue, 16 Aug 2011 15:57:18 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 16 Aug 2011 16:26:12 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 16 Aug 2011 16:26:10 +0300
Subject: IETF Last Call comment on  draft-ietf-pwe3-gal-in-pw
Thread-Topic: IETF Last Call comment on  draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxcGBA21vETQ27uTwSWVgNiuD48+A==
Message-ID: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.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_A3C5DF08D38B6049839A6F553B331C760111EFA07C5FILPTMAIL02e_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA3VTa0gUURTu7sxukzkxrWteF39MExU91rTnSq5EYViR2YOKKGycve2O7cxs O2O4SSUhPbSXGIUWPmIrM0OSkkiJkgwyo7IfitUWKmEWUZv2gMpmdtKEaH59c77HPfdyDoGZ 35qsBC8qyCeyHsYUgZf0hwZsc/iV6Qn13bj9zbUK3N514bLRfjx0HV+CpQUC3w0ZYEs+SGZF UVJYBdFOJHMOJsPH72Y5P0PzTgeTyNBeD8shAYmKg2G9XiQ6mZQI+p8vWZXxIo1ETnLyosvB rFi/xma3L0iyJTIp06YkzlscscHNyzSyCSzvoQUky6wL0Wpl+3XMHeofNHqrN+UWPK3C8sHt VYVgHAGp+bD8aAHQ8ST4JFhn0rCZagSwrGFjIYhQ8WkAaw63j9UIE+WA9VdehkUWagq8U9pp 1EQYdQ+DfQWBMIFTU2FL7f2wIUo1DDwM/DEshZ3nBw06jocN1TfwQkAQJLUWdh/O08pAbeJr a21YglExsKu3wqA3R8FA02NMx9Hwbc8vo66Phi8O1QFdL8HCb8HwsSQ1ET4o7cV1fSy8W92J nwSWslGxZaMsZaMsen02rGwMmXQ8C16seocN47Y7PYbR9UowtgbE8h6vkiW4EubapBwlHnG8 gjwonpOEeqDPSd9N8LxtRjOgCMBEkhncinSzkd0t+4VmEEsYmGhyjLQy3TwhS3L63azszvTl eJDcDCCBMRYS7FA50sn69yCfNEylqg9djFnHc5I6kaKSOS8h4f8/TAxZxL1fbaZc6hTuRMiL fMM5cQTBQHKfdvxEH3Kh3B28R/lLG4hxWhuRahuSpiFlLyvIvEvnW8Fkawx5RiMojXDniCNe bUP2Dw0N9YMY9dJRpF9TRar7M+LuV4MNanDXrTQtWN2QEcqaD+xkDfORsBiKv7TkDtI95xad MOdmJ+U3rtv64V5T9omFl26N7+ibfaBDmPsz6ZRl0Lnn7Hxj8sC2a7+KSxyPtmc9tgaXTF+7 MxgbtUxaahf2lUtxqWuWfw5iVTVZV3+0V1ob9r4+X8E9O7h5V14R9fKY8im0LK/1Qt6ru0m7 +OxFRyYxuOxmE2diPpn9DbtAghf8AwAA
X-Mailman-Approved-At: Tue, 16 Aug 2011 08:44:34 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Prashant Desai <Prashant.Desai@ecitele.com>, Andrew Sergeev <Andrew.Sergeev@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Robert Rennison <Robert.Rennison@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 13:25:35 -0000

--_000_A3C5DF08D38B6049839A6F553B331C760111EFA07C5FILPTMAIL02e_
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable

Hi all,

I would like to raise the following issue with regard to draft-ietf-pwe3-gal=
-in-pw<http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?in=
clude_text=3D1>: controversy vs. draft-ietf-pwe3-fat-pw<http://datatracker.i=
etf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1> with regard to bottom-=
of-stack position.

As stated in the Introduction, this draft removes the restriction imposed by=
 RFC 5586 on usage of Generic Associated Channel Label (GAL) in PWs. The cor=
responding text Section 4.2 of RFC 5586 states:
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenat=
ed Segments of LSPs, and with Sections, and MUST NOT be used with PWs.  It M=
UST always be at the bottom of the label stack    (i.e., S bit set to 1).

draft-ietf-pwe3-gal-in-pw proposed to replace the original text in RFC 5586=
 with the following

In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenat=
ed Segments of LSPs, and with Sections, and MAY be used with PWs. It MUST al=
ways be at the bottom of the label stack (i.e., S bit set to 1).

I.e.,  while removing this restriction of 5586, it does not modify its requi=
rement for the GAL being always at the bottom of the label stack.

At the same draft-ietf-pwe3-fat-pw (currently also in the IESG review) reser=
ves the bottom of the PW stack for the PW flow labels, e.g., in Section 1.1:

This document describes a method of adding an additional label stack entry (=
LSE) at the bottom of stack in order to facilitate the load balancing of the=
 flows within a PW over the available ECMPs.

One could argue that draft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseud=
owires, and that MPLS-TP does not use ECMP. IMHO and FWIW,
such an argument, were it presented, would be highly problematic, because:


1.       RFC 5960 (which defines the MPLS-TP data plane) did not define any=
 differences between the PW data plane in IP/MPLS and MPLS-TP.

2.       One of the most popular scenarios for using multi-segment pseudowir=
es is the case when an edge-to-edge service emulation crosses multiple IP/MP=
LS and MPLS-TP domains. In these scenarios, the flow label of draft-ietf-pwe=
3-fat-pw (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain) wo=
uld potentially compete with GAL (inserted by a T-PE at the edge of an MPLS-=
TP domain, e.g., for relying a PW status message that it has received over a=
 Targeted LDP session from the IP/MPLS domain to a static PW status message=
 to cross the MPLS-TP domain) for the bottom-of-stack position.

The issue I am raising Is not new. It has been actively discussed on the PWE=
3 mailing list with regard to adoption of draft-nadeau-pwe3-vccv-2 as a WG d=
ocument, with arguments  for both the flow label and GAL taking the bottom-o=
f-the-stack position. But, to the best of my understanding, consensus on thi=
s issue has not been reached.

Hopefully this comment will be useful.

Regards,
     Sasha



This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


--_000_A3C5DF08D38B6049839A6F553B331C760111EFA07C5FILPTMAIL02e_
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-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xm=
lns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://w=
ww.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=3D"te=
xt/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Wor=
d 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:0cm;
	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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2102606236;
	mso-list-type:hybrid;
	mso-list-template-ids:-1265364888 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;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vlin=
k=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi all,<o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would l=
ike to raise the following issue with regard to <a href=3D"http://datatracke=
r.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?include_text=3D1">draft-ie=
tf-pwe3-gal-in-pw</a>: controversy vs. <a href=3D"http://datatracker.ietf.or=
g/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1">draft-ietf-pwe3-fat-pw</a> w=
ith regard to bottom-of-stack position.<o:p></o:p></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As stated in the Introduction, this=
 draft removes the restriction imposed by RFC 5586 on usage of Generic Assoc=
iated Channel Label (GAL) in PWs. The corresponding text Section 4.2 of RFC=
 5586 states:<o:p></o:p></p><p class=3DMsoNormal style=3D'margin-left:36.0pt=
;line-height:14.4pt'><span style=3D'font-size:10.0pt;font-family:"Courier Ne=
w"'>In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concat=
enated Segments of LSPs, and with Sections, and MUST NOT be used with PWs.&n=
bsp; It MUST always be at the bottom of the label stack &nbsp;&nbsp;&nbsp;(i=
.e., S bit set to 1).</span><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><p class=3DMsoNormal>draft-ietf-pwe3-gal-in-pw proposed to replace=
 the original text in RFC 5586 with the following<o:p></o:p></p><p class=3DM=
soNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'margin-left:36.0=
pt;line-height:14.4pt'><span style=3D'font-size:10.0pt;font-family:"Courier=
 New"'>In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Con=
catenated Segments of LSPs, and with Sections, and MAY be used with PWs. It=
 MUST always be at the bottom of the label stack (i.e., S bit set to 1).<o:p=
></o:p></span></p><p class=3DMsoNormal style=3D'line-height:14.4pt'><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal style=3D'line-height:14.4pt'>I.e., &nbsp;while remov=
ing this restriction of 5586, it does not modify its requirement for the GAL=
 being always at the bottom of the label stack. <o:p></o:p></p><p class=3DMs=
oNormal style=3D'line-height:14.4pt'><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al style=3D'line-height:14.4pt'>At the same draft-ietf-pwe3-fat-pw (currentl=
y also in the IESG review) reserves the bottom of the PW stack for the PW fl=
ow labels, e.g., in Section 1.1:<o:p></o:p></p><p class=3DMsoNormal style=3D=
'line-height:14.4pt'><o:p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'marg=
in-left:36.0pt;line-height:14.4pt'><span style=3D'font-size:10.0pt;font-fami=
ly:"Courier New"'>This document describes a method of adding an additional l=
abel stack entry (LSE) at the bottom of stack in order to facilitate the loa=
d balancing of the flows within a PW over the available ECMPs.&nbsp; </span>=
<o:p></o:p></p><p class=3DMsoNormal style=3D'line-height:14.4pt'><o:p>&nbsp;=
</o:p></p><p class=3DMsoNormal style=3D'line-height:14.4pt'>One could argue=
 that draft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseudowires, and tha=
t MPLS-TP does not use ECMP. IMHO and FWIW, <o:p></o:p></p><p class=3DMsoNor=
mal style=3D'line-height:14.4pt'>such an argument, were it presented, would=
 be highly problematic, because:<o:p></o:p></p><p class=3DMsoNormal style=3D=
'line-height:14.4pt'><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph style=
=3D'text-indent:-18.0pt;line-height:14.4pt;mso-list:l0 level1 lfo1'><![if !s=
upportLists]><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Ti=
mes New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]=
><span dir=3DLTR></span>RFC 5960 (which defines the MPLS-TP data plane) did=
 not define any differences between the PW data plane in IP/MPLS and MPLS-TP=
. <o:p></o:p></p><p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;li=
ne-height:14.4pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span style=
=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]><span dir=3DLTR></span>=
One of the most popular scenarios for using multi-segment pseudowires is the=
 case when an edge-to-edge service emulation crosses multiple IP/MPLS and MP=
LS-TP domains. In these scenarios, the flow label of draft-ietf-pwe3-fat-pw=
 (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain) would pote=
ntially compete with GAL (inserted by a T-PE at the edge of an MPLS-TP domai=
n, e.g., for relying a PW status message that it has received over a Targete=
d LDP session from the IP/MPLS domain to a static PW status message to cross=
 the MPLS-TP domain) for the bottom-of-stack position. <o:p></o:p></p><p cla=
ss=3DMsoNormal style=3D'line-height:14.4pt'><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal style=3D'line-height:14.4pt'>The issue I am raising Is not new. It=
 has been actively discussed on the PWE3 mailing list with regard to adoptio=
n of draft-nadeau-pwe3-vccv-2 as a WG document, with arguments &nbsp;for bot=
h the flow label and GAL taking the bottom-of-the-stack position. But, to th=
e best of my understanding, consensus on this issue has not been reached.<o:=
p></o:p></p><p class=3DMsoNormal style=3D'line-height:14.4pt'><o:p>&nbsp;</o=
:p></p><p class=3DMsoNormal>Hopefully this comment will be useful.<o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Regards,=
<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p>
This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.
</p>
</body></html>
--_000_A3C5DF08D38B6049839A6F553B331C760111EFA07C5FILPTMAIL02e_--

From stpeter@stpeter.im  Tue Aug 16 12:10:34 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13A9811E809F for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 12:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.618
X-Spam-Level: 
X-Spam-Status: No, score=-102.618 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A7Z+ujIkgpSs for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 12:10:33 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 73DA711E808B for <ietf@ietf.org>; Tue, 16 Aug 2011 12:10:33 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 900DA4150D; Tue, 16 Aug 2011 13:13:12 -0600 (MDT)
Message-ID: <4E4AC0D2.8080203@stpeter.im>
Date: Tue, 16 Aug 2011 13:11:14 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Spencer Dawkins <spencer@wonderhamster.org>
Subject: Re: Last Call: <draft-eggert-successful-bar-bof-05.txt> (Considerationsfor Having a Successful "Bar BOF" Side Meeting) to Informational RFC
References: <20110811222013.3869.45041.idtracker@ietfa.amsl.com> <4827963E94554ED9A4D510E0F3C29EB8@china.huawei.com>
In-Reply-To: <4827963E94554ED9A4D510E0F3C29EB8@china.huawei.com>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 19:10:34 -0000

On 8/15/11 4:40 PM, Spencer Dawkins wrote:
> I have been looking at various revisions of this draft since -00. I'm
> glad Lars did the first version during IETF 77, and I'm glad that Lars
> and Gonzalo kept working on it.
> 
> I think it's important guidance for the community. I think it's on the
> right track. I think it could reasonably be published in its current form.
> 
> I have some suggestions.
> 
> Frivolous: I TOTALLY get the "don't call it a Bar BOF" thing.

Keeping with the natural human tendency to fixate on the frivolous, I'll
take the bait.

"Hey boss, I need to go to the IETF meeting in Taipei, we're holding a
BoF about Technology X." "Is that a real BoF or a bar BoF?" "Just a BoF,
you'll authorize the travel, right?"

"We're holding a BoF this week on Technology X." "Sounds interesting,
but I don't see it on the schedule. Is that a real BoF or a bar BoF?"
"It's a bar BoF, but sorry, no bar!"

"Mr. AD, we deserve to have a BoF about Technology X. We've already held
two bar BoFs so it's time for the real deal. You'll approve the request,
right?"

Etc.

Worst of all, usually there's no bar involved at all! :)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From rbarnes@bbn.com  Tue Aug 16 13:43:15 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F07921F8A56 for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 13:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.527
X-Spam-Level: 
X-Spam-Status: No, score=-106.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yiIcmY2QpNEb for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 13:43:14 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id D025C21F8A4D for <ietf@ietf.org>; Tue, 16 Aug 2011 13:43:14 -0700 (PDT)
Received: from ros-dhcp192-1-51-76.bbn.com ([192.1.51.76]:62359) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1QtQUV-0006wd-Qr for ietf@ietf.org; Tue, 16 Aug 2011 16:44:04 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Last Call: <draft-ietf-grow-geomrt-04.txt> (Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) routing information export format with geo-location extensions) to Proposed Standard
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <20110812152329.25815.3338.idtracker@ietfa.amsl.com>
Date: Tue, 16 Aug 2011 16:44:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A2C569D-5D6A-4A20-A252-E76B29B1227D@bbn.com>
References: <20110812152329.25815.3338.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 20:43:15 -0000

It would be helpful to clarify the relationship between this work and =
other IETF work on geolocation, namely GEOPRIV [RFC6280].  I don't think =
there's a huge change required, but a simple paragraph could be helpful; =
suggested text is below.

The first question is what role a geomrt router plays in the GEOPRIV =
system. Given that a GeoMRT router is receiving location (somehow) from =
peers and sending it back out, one could argue that it's a Location =
Server, and thus needs to both (1) obey, and (2) forward any privacy =
rules attached to a location object.  I wouldn't say it's a Viewer, =
since it's preserving the location information as location information; =
I would think of a Viewer as something that's going to use the location =
to do something else, like Yelp or OpenTable, or even a location-based =
routing system (I hear they exist for DTNs).

So in principle, location objects from which a geomrt router builds a =
geomrt object could have rules attached that give less than full access, =
and in that case, GEOPRIV would call for those rules to be sent along =
with the location info in the geomrt object.

Now, there are two ways to respond to this situation:
1. Add privacy/rules fields to geomrt
2. Require that location info that feeds into a geomrt object not have =
rules attached (i.e., it must be public)

ISTM that the latter approach makes more sense for this document, since =
this format is largely intended for low-risk, publication-style =
information sharing.  Suggested text (probably in Security =
Considerations):
"
The GEOPRIV architecture requires that rules attached to a location =
object be transmitted alongside the location information in the object.  =
If a router adds location to an MRT object based on GEOPRIV location =
objects, then it would have to include rules as well.  Since the MRT =
geolocation format does not include fields to carry privacy rules, each =
location entry in an MRT object is assigned the following default =
privacy rules [RFC4119]:
-- retransmission-allowed: True
-- retention-expires: 100 years from timestamp of the MRT object
-- ruleset-reference: Empty
-- note-well: Empty
Location information derived from a location object with more =
restrictive rules MUST NOT be included in an MRT object unless there are =
non-technical measures in place  that enforce and communicate the =
constraints on the use of the location information in the MRT object =
(e.g., contractual agreements between peers).

Location information that originates from sources other than GEOPRIV =
location objects (e.g., GPS chips, emails from peers) does not have the =
same formal requirements, but should nonetheless be handled as =
potentially private information requiring the  permission of the source =
before publication.
"


On Aug 12, 2011, at 11:23 AM, The IESG wrote:

>=20
> The IESG has received a request from the Global Routing Operations WG
> (grow) to consider the following document:
> - 'Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP)
>   routing information export format with geo-location extensions'
>  <draft-ietf-grow-geomrt-04.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-08-26. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document updates the Multi-threaded Routing Toolkit (MRT) =
export
>   format for Border Gateway Protocol (BGP) routing information by
>   extending it to include optional terrestrial coordinates of a BGP
>   Collector and its BGP Peers.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From mrex@sap.com  Tue Aug 16 14:00:46 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C245721F8B08 for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 14:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.514
X-Spam-Level: 
X-Spam-Status: No, score=-9.514 tagged_above=-999 required=5 tests=[AWL=-0.265, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_BACKHAIR_33=1, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqwBgAonD5a3 for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 14:00:46 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id B290521F8B00 for <ietf@ietf.org>; Tue, 16 Aug 2011 14:00:45 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p7GL1WOA023608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 16 Aug 2011 23:01:32 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108162101.p7GL1VrP025475@fs4113.wdf.sap.corp>
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission
To: ned+ietf@mauve.mrochek.com
Date: Tue, 16 Aug 2011 23:01:31 +0200 (MEST)
In-Reply-To: <01O4STRDJ1P400VHKR@mauve.mrochek.com> from "ned+ietf@mauve.mrochek.com" at Aug 13, 11 11:45:01 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org, vesely@tana.it
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 21:00:46 -0000

ned+ietf@mauve.mrochek.com wrote:
> 
> > On 12.08.2011 21:02, Martin Rex wrote:
> > >
> > > I'm wondering wheter there should be an informative reference to rfc6186.
> 
> > This question was one of two points raised during WGLC by Derek Diget
> > http://www.ietf.org/mail-archive/web/yam/current/msg00615.html
> 
> > It was decided that the current deployment of SRV doesn't quite justify
> > supporting it in a Full Standard document.
> 
> I really wish it were otherwise, but I find myself having to agree with this
> assessment. It would be a different thing if this was just now coming up for
> approval at proposed, but we're way past that.

Security-wise, the SRV record suggested by rfc6196 seems to create
additional security problems, so I would also not like to see it being
"adopted" as is.  :-/



> 
> > > and I am concerned about the security mess around SMTP-AUTH (rfc4954)
> > > (for which this document is not responsible, but which it also
> > >  does not mention).
> 
> > This question was raised by Chris Newman on Fri, 30 Apr 2010.
> > http://www.ietf.org/mail-archive/web/yam/current/msg00420.html
> 
> > There was a somewhat deeper discussion, but the conclusion was the same as
> > yours, namely that it's not the responsibility of 4409bis, and that
> 
> >    it would be a serious mistake to clutter 4409bis up with some of the
> >    details that have been suggested.  Even at full standard, authentication
> >    details are best incorporated by reference to other documents than can be
> >    updated when or as necessary.
> >               http://www.ietf.org/mail-archive/web/yam/current/msg00434.html
> 
> +1

While I fully agree that it is sensible to relegate (and fix) the
authentication to a different document, I currently see this:

http://tools.ietf.org/html/draft-ietf-yam-rfc4409bis-02#section-7

   | AUTH             | Authentication   |    MUST   | [SMTP-AUTH]     |


And it somehow feels wrong to exhibit an ostrich-like behaviour about
the current mess around SMTP-AUTH in the security considerations section.


The traditional mail delivery service by SMTP is very similar to IP itself,
a good-faith best-effort approach of multiple cooperating entities.
Adding robust security to MTA<->MTA links will be extremely difficult.

As long as an active attacker can force inter-MTA SMTP delivery to be
performed without TLS the (scalable) security remains at good-faith
best-effort level, even if there was DNSSEC available, all relevant
records signed, even something like a "HASTLS" DNS RR defined and used
for SMTP, it is still up to the SMTP MTA clients all over world to
actually use those records and refuse to talk to active MITMs.

The SMTPS MUA->MTA connection differs in that it often uses an
explicit, server-specific configuration for TLS, without automatic
fallback to non-TLS.

The real situation in practise may sometimes be a little different, though.
During last year, I newly set up EMail accounts for two relatives with a
freemail provider (both were using 3 year old Notebooks running Windows XP)
and when configuring Mail delivery for Outlook Express via SMTPS, I received
a warning popup with a complaint about a mismatch of the server cert,
but *NO* possibility to look at the TLS server cert and no details as
to which particular attributes were compared or what exactly did not match.


I believe it would be sensible to describe the desired authentication model
for MUA->MTA in more detail, beyond the mere reference of [SMTP-AUTH]
in section 4.3 of the current document:

http://tools.ietf.org/html/draft-ietf-yam-rfc4409bis-02#section-4.3


-Martin

From terry.manderson@icann.org  Tue Aug 16 17:52:55 2011
Return-Path: <terry.manderson@icann.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 454AF21F8997 for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 17:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.517
X-Spam-Level: 
X-Spam-Status: No, score=-106.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5qbWq8sqotd for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 17:52:54 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id 8785421F888A for <ietf@ietf.org>; Tue, 16 Aug 2011 17:52:54 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Tue, 16 Aug 2011 17:53:44 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: "Richard L. Barnes" <rbarnes@bbn.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 16 Aug 2011 17:53:41 -0700
Subject: Re: Last Call: <draft-ietf-grow-geomrt-04.txt> (Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) routing information export format with geo-location extensions) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-grow-geomrt-04.txt> (Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) routing information export format with geo-location extensions) to Proposed Standard
Thread-Index: AcxcVUvxD4rp8wXmRMKUy+2KegsfgQAIs9QB
Message-ID: <CA714E35.19498%terry.manderson@icann.org>
In-Reply-To: <8A2C569D-5D6A-4A20-A252-E76B29B1227D@bbn.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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 00:52:55 -0000

Hi Richard,=20

Thanks for reading and reviewing.

There should be no rules attached to the location data in the GEOMRT format=
,
and as you point out there is (in MRT) no way to communicate these rule if
they were to exist.

That said, and augmenting your text only slightly, I will add the following
as a new 'Privacy Considerations' section of draft-ietf-grow-geomrt.

---

The GEOPRIV [RFC6280] architecture requires that privacy rules attached to =
a
location object be transmitted alongside the location information in the
object. If a BGP Collector adds location coordinates to an MRT record based
on GEOPRIV location objects, then it would have to include privacy rules as
well. Since the MRT geo-location format does support the the provision of
privacy rules, each location entry in an MRT object is assigned the
following default privacy rules [RFC4119]:

-- retransmission-allowed: True
-- retention-expires: 100 years from timestamp of the MRT object
-- ruleset-reference: Empty
-- note-well: Empty

Location information derived from a location object with more restrictive
privacy rules MUST NOT be included in a MRT geo-location record unless ther=
e
are non-technical measures in place that enforce and communicate the
constraints on the use of the location information in the MRT geo-location
format (e.g., contractual agreements between peers).

---

This supports the text in the security considerations section, but I think
it deserves its own section.

Ok with you?

Cheers
Terry

On 17/08/11 6:44 AM, "Richard L. Barnes" <rbarnes@bbn.com> wrote:

> It would be helpful to clarify the relationship between this work and oth=
er
> IETF work on geolocation, namely GEOPRIV [RFC6280].  I don't think there'=
s a
> huge change required, but a simple paragraph could be helpful; suggested =
text
> is below.
>=20
> The first question is what role a geomrt router plays in the GEOPRIV syst=
em.
> Given that a GeoMRT router is receiving location (somehow) from peers and
> sending it back out, one could argue that it's a Location Server, and thu=
s
> needs to both (1) obey, and (2) forward any privacy rules attached to a
> location object.  I wouldn't say it's a Viewer, since it's preserving the
> location information as location information; I would think of a Viewer a=
s
> something that's going to use the location to do something else, like Yel=
p or
> OpenTable, or even a location-based routing system (I hear they exist for
> DTNs).
>=20
> So in principle, location objects from which a geomrt router builds a geo=
mrt
> object could have rules attached that give less than full access, and in =
that
> case, GEOPRIV would call for those rules to be sent along with the locati=
on
> info in the geomrt object.
>=20
> Now, there are two ways to respond to this situation:
> 1. Add privacy/rules fields to geomrt
> 2. Require that location info that feeds into a geomrt object not have ru=
les
> attached (i.e., it must be public)
>=20
> ISTM that the latter approach makes more sense for this document, since t=
his
> format is largely intended for low-risk, publication-style information
> sharing.  Suggested text (probably in Security Considerations):
> "
> The GEOPRIV architecture requires that rules attached to a location objec=
t be
> transmitted alongside the location information in the object.  If a route=
r
> adds location to an MRT object based on GEOPRIV location objects, then it
> would have to include rules as well.  Since the MRT geolocation format do=
es
> not include fields to carry privacy rules, each location entry in an MRT
> object is assigned the following default privacy rules [RFC4119]:
> -- retransmission-allowed: True
> -- retention-expires: 100 years from timestamp of the MRT object
> -- ruleset-reference: Empty
> -- note-well: Empty
> Location information derived from a location object with more restrictive
> rules MUST NOT be included in an MRT object unless there are non-technica=
l
> measures in place  that enforce and communicate the constraints on the us=
e of
> the location information in the MRT object (e.g., contractual agreements
> between peers).
>=20
> Location information that originates from sources other than GEOPRIV loca=
tion
> objects (e.g., GPS chips, emails from peers) does not have the same forma=
l
> requirements, but should nonetheless be handled as potentially private
> information requiring the  permission of the source before publication.
> "
>=20
>=20
> On Aug 12, 2011, at 11:23 AM, The IESG wrote:
>=20
>>=20
>> The IESG has received a request from the Global Routing Operations WG
>> (grow) to consider the following document:
>> - 'Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP)
>>   routing information export format with geo-location extensions'
>>  <draft-ietf-grow-geomrt-04.txt> as a Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2011-08-26. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>   This document updates the Multi-threaded Routing Toolkit (MRT) export
>>   format for Border Gateway Protocol (BGP) routing information by
>>   extending it to include optional terrestrial coordinates of a BGP
>>   Collector and its BGP Peers.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rbarnes@bbn.com  Tue Aug 16 18:15:14 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EBAC5E8006 for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 18:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.57
X-Spam-Level: 
X-Spam-Status: No, score=-106.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gh1q2bUTuPN for <ietf@ietfa.amsl.com>; Tue, 16 Aug 2011 18:15:13 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 8C21C5E8004 for <ietf@ietf.org>; Tue, 16 Aug 2011 18:15:13 -0700 (PDT)
Received: from [128.89.255.121] (port=62987 helo=[192.168.1.13]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1QtUjh-0009UA-V7; Tue, 16 Aug 2011 21:16:02 -0400
Subject: Re: Last Call: <draft-ietf-grow-geomrt-04.txt> (Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) routing information export format with geo-location extensions) to Proposed Standard
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: <CA714E35.19498%terry.manderson@icann.org>
Date: Tue, 16 Aug 2011 21:16:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <08D6F380-FD08-4238-A4DD-6E32203D879F@bbn.com>
References: <CA714E35.19498%terry.manderson@icann.org>
To: Terry Manderson <terry.manderson@icann.org>
X-Mailer: Apple Mail (2.1082)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 01:15:14 -0000

Sounds good to me!  Thanks,
--Richard


On Aug 16, 2011, at 8:53 PM, Terry Manderson wrote:

> Hi Richard,=20
>=20
> Thanks for reading and reviewing.
>=20
> There should be no rules attached to the location data in the GEOMRT =
format,
> and as you point out there is (in MRT) no way to communicate these =
rule if
> they were to exist.
>=20
> That said, and augmenting your text only slightly, I will add the =
following
> as a new 'Privacy Considerations' section of draft-ietf-grow-geomrt.
>=20
> ---
>=20
> The GEOPRIV [RFC6280] architecture requires that privacy rules =
attached to a
> location object be transmitted alongside the location information in =
the
> object. If a BGP Collector adds location coordinates to an MRT record =
based
> on GEOPRIV location objects, then it would have to include privacy =
rules as
> well. Since the MRT geo-location format does support the the provision =
of
> privacy rules, each location entry in an MRT object is assigned the
> following default privacy rules [RFC4119]:
>=20
> -- retransmission-allowed: True
> -- retention-expires: 100 years from timestamp of the MRT object
> -- ruleset-reference: Empty
> -- note-well: Empty
>=20
> Location information derived from a location object with more =
restrictive
> privacy rules MUST NOT be included in a MRT geo-location record unless =
there
> are non-technical measures in place that enforce and communicate the
> constraints on the use of the location information in the MRT =
geo-location
> format (e.g., contractual agreements between peers).
>=20
> ---
>=20
> This supports the text in the security considerations section, but I =
think
> it deserves its own section.
>=20
> Ok with you?
>=20
> Cheers
> Terry
>=20
> On 17/08/11 6:44 AM, "Richard L. Barnes" <rbarnes@bbn.com> wrote:
>=20
>> It would be helpful to clarify the relationship between this work and =
other
>> IETF work on geolocation, namely GEOPRIV [RFC6280].  I don't think =
there's a
>> huge change required, but a simple paragraph could be helpful; =
suggested text
>> is below.
>>=20
>> The first question is what role a geomrt router plays in the GEOPRIV =
system.
>> Given that a GeoMRT router is receiving location (somehow) from peers =
and
>> sending it back out, one could argue that it's a Location Server, and =
thus
>> needs to both (1) obey, and (2) forward any privacy rules attached to =
a
>> location object.  I wouldn't say it's a Viewer, since it's preserving =
the
>> location information as location information; I would think of a =
Viewer as
>> something that's going to use the location to do something else, like =
Yelp or
>> OpenTable, or even a location-based routing system (I hear they exist =
for
>> DTNs).
>>=20
>> So in principle, location objects from which a geomrt router builds a =
geomrt
>> object could have rules attached that give less than full access, and =
in that
>> case, GEOPRIV would call for those rules to be sent along with the =
location
>> info in the geomrt object.
>>=20
>> Now, there are two ways to respond to this situation:
>> 1. Add privacy/rules fields to geomrt
>> 2. Require that location info that feeds into a geomrt object not =
have rules
>> attached (i.e., it must be public)
>>=20
>> ISTM that the latter approach makes more sense for this document, =
since this
>> format is largely intended for low-risk, publication-style =
information
>> sharing.  Suggested text (probably in Security Considerations):
>> "
>> The GEOPRIV architecture requires that rules attached to a location =
object be
>> transmitted alongside the location information in the object.  If a =
router
>> adds location to an MRT object based on GEOPRIV location objects, =
then it
>> would have to include rules as well.  Since the MRT geolocation =
format does
>> not include fields to carry privacy rules, each location entry in an =
MRT
>> object is assigned the following default privacy rules [RFC4119]:
>> -- retransmission-allowed: True
>> -- retention-expires: 100 years from timestamp of the MRT object
>> -- ruleset-reference: Empty
>> -- note-well: Empty
>> Location information derived from a location object with more =
restrictive
>> rules MUST NOT be included in an MRT object unless there are =
non-technical
>> measures in place  that enforce and communicate the constraints on =
the use of
>> the location information in the MRT object (e.g., contractual =
agreements
>> between peers).
>>=20
>> Location information that originates from sources other than GEOPRIV =
location
>> objects (e.g., GPS chips, emails from peers) does not have the same =
formal
>> requirements, but should nonetheless be handled as potentially =
private
>> information requiring the  permission of the source before =
publication.
>> "
>>=20
>>=20
>> On Aug 12, 2011, at 11:23 AM, The IESG wrote:
>>=20
>>>=20
>>> The IESG has received a request from the Global Routing Operations =
WG
>>> (grow) to consider the following document:
>>> - 'Multi-threaded Routing Toolkit (MRT) Border Gateway Protocol =
(BGP)
>>>  routing information export format with geo-location extensions'
>>> <draft-ietf-grow-geomrt-04.txt> as a Proposed Standard
>>>=20
>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>> final comments on this action. Please send substantive comments to =
the
>>> ietf@ietf.org mailing lists by 2011-08-26. Exceptionally, comments =
may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>=20
>>> Abstract
>>>=20
>>>=20
>>>  This document updates the Multi-threaded Routing Toolkit (MRT) =
export
>>>  format for Border Gateway Protocol (BGP) routing information by
>>>  extending it to include optional terrestrial coordinates of a BGP
>>>  Collector and its BGP Peers.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/
>>>=20
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-grow-geomrt/
>>>=20
>>>=20
>>> No IPR declarations have been submitted directly on this I-D.
>>>=20
>>>=20
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20


From john-ietf@jck.com  Wed Aug 17 01:37:28 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0678F21F8559 for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 01:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHYFW1HSkEeb for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 01:37:27 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id D7EB121F853E for <ietf@ietf.org>; Wed, 17 Aug 2011 01:37:26 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qtbdg-000LJ3-Tl for ietf@ietf.org; Wed, 17 Aug 2011 04:38:17 -0400
Date: Wed, 17 Aug 2011 04:38:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-eggert-successful-bar-bof-05.txt>	(Considerationsfor Having a Successful "Bar BOF" Side Meeting)	to Informational RFC
Message-ID: <7801A7BACF0B939148F5BA83@PST.JCK.COM>
In-Reply-To: <4827963E94554ED9A4D510E0F3C29EB8@china.huawei.com>
References: <20110811222013.3869.45041.idtracker@ietfa.amsl.com> <4827963E94554ED9A4D510E0F3C29EB8@china.huawei.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 08:37:28 -0000

I think this is a nice document, with many useful suggestions
and insights.  I think it would make a great ION if we still had
IONs, a fine IESG statement, or perhaps an I-D that was reissued
every 5 1/2 months to keep it active.  The more I think about
it, the less I like the idea of publishing it as an RFC.

The problem is that RFCs are forever.  RFCs subjected to IETF
Last Call and published in the IETF Stream --especially ones
that advise on IETF processes-- are also official, at least in
the sense of representing some level of community consensus and
IESG approval.  Publishing this document in the RFC Series runs
a considerable risk of causing (or at least reinforcing) exactly
the situation the it argues against -- creating a permanent
structure of meetings for which "informal" is as much of a
misnomer as "bar BOF" has become.

I also note that we hold, or try to hold, a lot of "side
meetings" that don't fall anywhere on the "Bar BOF" - "pre BOF
or pre Charter" spectrum.  They include some directorate
meetings, ADs meeting with WG Chairs, WG Chairs meeting with
authors, various design team meetings, extra IAB, IESG or IAOC
meetings, meeting related to parts of the RFC Editor function,
and so on for what is probably a rather long list.  Those
meetings draw on the same resources as the types of meetings
discussed in the document and those resources are not unlimited.


Let me give two examples of the problem with the understanding
that there are more:

	* If we have an official-looking, cast-in-RFC-stone,
	discussion of what "success" means for an informal
	meeting, it means that the IETF has established success
	criteria for a meeting type that we simultaneously claim
	is not part of the WG-formation or consensus processes.
	One really can't have it both ways and, in that sense,
	the document reinforces the "first you need a mailing
	list, then a Bar-BOF (sic) or two, then a "real" BOF (or
	two), ..." trend.
	
	* The draft says "Quiet restaurants are not hard to find
	and many offer private dining rooms..." (Section 3,
	paragraph 2).  Well, that depends on the venue.  We've
	certainly met in places where quiet restaurants _are_
	hard to find (at least anywhere near the meeting
	location) and in places (not necessarily the same ones)
	in which the number of private dining rooms near the
	meeting location is not nearly sufficient to accommodate
	the number of side meetings (see extended definition
	above) that people want to hold.  If anyone wants to add
	whining about how the IAOC didn't choose a venue with a
	sufficient nearby supply of quiet restaurants with
	private dining rooms to the regular cycles of complaints
	about venue choices, this document's recommendations
	would be a good place to start.  

	Presumably we don't want to put the IESG or the
	Secretariat into the business or allocating, or
	refereeing, priorities for informal meeting spaces
	either... but, again, that is exactly the direction in
	which this draft seems to take us.

Again, this doesn't make the draft any less useful as good
advice; it merely argues against publishing it as an RFC,
especially in the IETF Stream.


If the IESG wants to stop the worst parts of the problem, it
needs to verify community support and then put its collective
foot down.  IMO, any of the following would be of help:

(1) Set an application cutoff for allocations of IETF space for
pre-charter informal meetings before the cutoff for BOF
requests, thereby eliminating one issue that does not appear to
be mentioned in the I-D: use of Bar-BOFs by people who couldn't
get their acts together to make a timely and satisfactory BOF
request.

(2) Just say "no".  Once upon a time, we had a relatively strict
rule against any IETF-related open (or semi-open, or publicly
announced)  meetings in the IETF venue unless those meetings
were either on the agenda or a formal IETF group.  That was in
the time when Bar-BoFs (and Bar-Design-Teams, and
Bar-other-things) were held in Bars, with Bar-sized groups, and
those were not considered meetings of any type.   We could do
that again -- forcing pre-charter meetings into other venues
would at least reinforce the message that they weren't WG
meetings of unchartered WGs.

(3) Get rid of the "two BOF" rule, replacing it with criteria
that simply made it harder to get a BOF approved, and harder to
get a WG proposal taken seriously, the more face to face
meetings it took to get it organized.   One of the causes of "WG
in disguise"-style pre-charter meetings appears to be a
combination of fear of hitting the two BOF limit and deciding to
hold regular meetings despite not being able to get a WG charter
or BOF proposal together that would satisfy the IESG.

(4) Make it clear that any claims of consensus arising from an
informal meeting would not only be ignored, but would cause BOF
or WG proposals from the leadership of that information meeting
to be discarded on the grounds that the people were clueless and
incapable of working within the IETF.   Taking these "unofficial
BOF" discussions seriously merely reinforces their misuse.

best,
   john



From evnikita2@gmail.com  Wed Aug 17 09:19:51 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA7E21F8B6F for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 09:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.459
X-Spam-Level: 
X-Spam-Status: No, score=-3.459 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbnDDqEdXiCy for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 09:19:50 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1340821F8B51 for <ietf@ietf.org>; Wed, 17 Aug 2011 09:19:45 -0700 (PDT)
Received: by fxe6 with SMTP id 6so820430fxe.31 for <ietf@ietf.org>; Wed, 17 Aug 2011 09:20:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=k/gI7RpuFiVdzuQOL6Kc2uhXPL2lqBS0eQGAJlb0Kv0=; b=xMrXpKgt7XbPi63T5FmncVD4puHALV59+aW7ffJZTu6SxIutr3WtIFj7LcU9SXvLlA UAtTFboLYtZFAX/XLpA0WoGnw9uFvtuR25C4RZG0riLZD8JdpFp3TVW2BgLhvH2c6ISW N1Bfbd2fmOQvCa5xDdd8AgQv15jPjYbrZtaOY=
Received: by 10.223.100.71 with SMTP id x7mr1646518fan.18.1313598037030; Wed, 17 Aug 2011 09:20:37 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id c7sm1006274fac.36.2011.08.17.09.20.34 (version=SSLv3 cipher=OTHER); Wed, 17 Aug 2011 09:20:35 -0700 (PDT)
Message-ID: <4E4BEA77.4070606@gmail.com>
Date: Wed, 17 Aug 2011 19:21:11 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [yam] Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
In-Reply-To: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 16:19:51 -0000

My 2 pence:

I did finally manage to read the document and I support its 
publication.  The only minor comment:

>     The table in Table 1 has been corrected (reference for NO-SOLICITING)
>     and extended (ATRN, DELIVERBY, CONPEM, and CONNEG).  The registry
>     should be updated to reflect the changed and new entries.  Entries in
>     the registry that do not appear in the table above are correct and
>     should not be altered.

IANA commented that it should be clear that "the registry" refers to 
SMTP Service Extensions 
(http://www.iana.org/assignments/mail-parameters); but the registry 
there seems to have other format compared to Table 1:

>     +------------------+------------------+-----------+-----------------+
>     | Keyword          | Name             | Submissio | Reference       |
>     |                  |                  | n         |                 |

please compare with

> Keywords             Description                         Reference    Note

So how is this table going to be incorporated in the aforementioned 
registry?

<thinking off-topic="yes">There is the equivalence of English 
collocation "two pence" in Russian and Ukrainian, that are "pjat' 
kopeek" and "pjat' kopijok", respectively, and are translated as "five 
kopecks".  One kopeck is 1/100 of ruble or hryvnia; one penny is 1/100 
of pound; respectively one penny is nearly 13 Ukrainian kopecks and 
nearly 50 Russian kopecks.  So, when saying this in Ukrainian or 
Russian, I actually make a contribution which less that one said in 
English :-).</thinking>

Mykyta Yevstifeyev

11.08.2011 16:37, The IESG wrote:
> The IESG has received a request from the Yet Another Mail WG (yam) to
> consider the following document:
> - 'Message Submission for Mail'
>    <draft-ietf-yam-rfc4409bis-02.txt>  as a Full Standard

From Alexander.Vainshtein@ecitele.com  Tue Aug 16 10:01:58 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D55321F8B52; Tue, 16 Aug 2011 10:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=1.954,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pRcUwzioRWUm; Tue, 16 Aug 2011 10:01:57 -0700 (PDT)
Received: from mail21.messagelabs.com (mail21.messagelabs.com [85.158.143.35]) by ietfa.amsl.com (Postfix) with SMTP id 4F3AB21F8B47; Tue, 16 Aug 2011 10:01:56 -0700 (PDT)
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-11.tower-21.messagelabs.com!1313514149!40800009!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [147.234.242.235]
Received: (qmail 5681 invoked from network); 16 Aug 2011 17:02:29 -0000
Received: from ilptbmg02-out.ecitele.com (HELO ilptbmg02.ecitele.com) (147.234.242.235) by server-11.tower-21.messagelabs.com with SMTP; 16 Aug 2011 17:02:29 -0000
X-AuditID: 93eaf2e8-b7b3eae00000414f-8f-4e4a9becf855
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Messaging Gateway) with SMTP id CB.CF.16719.CEB9A4E4; Tue, 16 Aug 2011 19:33:48 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 16 Aug 2011 20:02:41 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 16 Aug 2011 20:02:20 +0300
Subject: RE: IETF Last Call comment on  draft-ietf-pwe3-gal-in-pw
Thread-Topic: IETF Last Call comment on  draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxcGBA21vETQ27uTwSWVgNiuD48+AAHMfDU
Message-ID: <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.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_A3C5DF08D38B6049839A6F553B331C760111EF7BD443ILPTMAIL02e_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA3VTa0gUURTmzszarDkxu2Vet4hprEBjZbcXG7lhRWRSZlv0IwobZ6+7U7sz 284YWlDaA3tq71IDzSzyEabZgx5U/jCUoCexaAWRRZlEiVH9KLuzUyZE99d3z/ed7xzuPYcm raUjbLQkaygsCwE+JpY60ts/YO+rzMxynO1Jcb1trqJcXWfrTK7S/lYqncyorf1OZIPVRSBN kGVFEzTEeZEquvnssLRJEAt5TvK6eSfPhQKCiIJI1ty8EAoh2cvPjeX+OWlYJskckkXFK8k+ N794xTK7yzVztt3Jz52S5Jw+J3alX1I5ZA8KUoALIlUVfIjDkXWtpL/yeT0R+ril4NX27aYi UObfC8w0ZGfAoztLYgw8Fj582YRxLG1lbwDYcOSJybgcB7DjW19UFcO6YUvDiygewybBO+WR qIhkrxKwpOopqRMUOxneHziHMU2PZufBxvYlhn4+jNR8IQw8DXY/uhX1YdjlsPrlPZOOrRg/ Li6mdGxmPfDH4EBUA3B3Xzsbo7kkmwC7eqoIo2sW1t58QBo4Hr5//dNk6OPh85ImYOgV2HRl 9+9aFthR3kMZ+kR493yEOgjGVgyzrRiWUjEsxYinwsixozEGngrPnf5AGtgOT/5so4bHq8GI epAoBUJabtDnmGZX8rVUJEoaCqBUUQm2AGOA3l0D3feT2wBLAz6OWbw7M8tqEjaphcE2kEgT fDyztRqHRuUq3kK/oPpzwvkBpLYBSJP8GAbkYY7xCoWbUVj5Qy3EH3CItI0UFTyqspYz3eH4 /4VPYPaJfUutrA+P5waEQij8x2c8TfOQaT6NS1jCyIcK8qSA9pcmaLPeRhxu47yuYdSQEFQl n8F3Ajv9obuqHVgpWZGRLYEha7CI1UX+fHnIR1+jbYODg70gAT/AaOaNbhWHl2zIqRcXIXCR rusZehG8RkOUrQj4Lhes96jgouNtR3r1maTGjAWcp8H8+fXKFk/6pwPitVxeWGMp8WizdjRv rFuYfWFinWdAs+3fStSVFrCJez+mH+6NfHqTtSTzxPViR/yllEVXuPa1AJo7V427fSavf5ez ZtypsmdxlgkCnZbDTMzpnHRMfJhcZnFXtu7JffeqladUv+BMIcOq8As0QBzmIQQAAA==
X-Mailman-Approved-At: Wed, 17 Aug 2011 10:38:05 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 17:01:58 -0000

--_000_A3C5DF08D38B6049839A6F553B331C760111EF7BD443ILPTMAIL02e_
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable

Hi all,
After having sent out my comments I've noticed that the specific example to=
 illustrate the need to combine GAL and "flow label" was inaccurate.

A more relevant example would look like following (I do not include a diagra=
m, but it can be easily provided if necessary)

 1.  A MS-PW:
    *   Starts at an S-PE that resides at the edge of an MPLS-TP domain (no=
 ECMP)
    *   Crosses this domain and enters an IP/MPLS domain with ECMP enabled u=
sing a T-PE that resides at the age of these two domains
    *   Leaves this domain and enters a 2nd MPLS-TP domain (using the 2nd T-=
PE)
    *   Terminates on another S-PE at the edge of the 2nd MPLS-TP domain
 2.  The operator intends to improve traffic distribution in the IP/MPLS dom=
ain, hence he enables insertion and discard of "flow labels" at the two S-PE=
s. Note that:
    *   This does not violate the MPLS-TP restriction on ECMP: ECMP does not=
 happen in he MPLS-TP domains
    *   T-PEs do not even have to be aware of flow labels
 3.  The operator also intends to operate some end-to-end OAM for this MS-PW=
 using "GAL-in-PW". This results in a conflict since both GAL and "flow labe=
l" are defined (in the corresponding drafts) as bottom of stack.



IMHO this describes a realistic scenario where the two drafts are in controv=
ersy.

Regards,
     Sasha
________________________________
From: mpls-bounces@ietf.org [mpls-bounces@ietf.org] On Behalf Of Alexander V=
ainshtein [Alexander.Vainshtein@ecitele.com]
Sent: Tuesday, August 16, 2011 4:26 PM
To: ietf@ietf.org
Cc: mpls@ietf.org; Vladimir Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren=
 Gal; John Shirron; Rotem Cohen
Subject: [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw

Hi all,

I would like to raise the following issue with regard to draft-ietf-pwe3-gal=
-in-pw<http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?in=
clude_text=3D1>: controversy vs. draft-ietf-pwe3-fat-pw<http://datatracker.i=
etf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1> with regard to bottom-=
of-stack position.

As stated in the Introduction, this draft removes the restriction imposed by=
 RFC 5586 on usage of Generic Associated Channel Label (GAL) in PWs. The cor=
responding text Section 4.2 of RFC 5586 states:
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenat=
ed Segments of LSPs, and with Sections, and MUST NOT be used with PWs.  It M=
UST always be at the bottom of the label stack    (i.e., S bit set to 1).

draft-ietf-pwe3-gal-in-pw proposed to replace the original text in RFC 5586=
 with the following

In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenat=
ed Segments of LSPs, and with Sections, and MAY be used with PWs. It MUST al=
ways be at the bottom of the label stack (i.e., S bit set to 1).

I.e.,  while removing this restriction of 5586, it does not modify its requi=
rement for the GAL being always at the bottom of the label stack.

At the same draft-ietf-pwe3-fat-pw (currently also in the IESG review) reser=
ves the bottom of the PW stack for the PW flow labels, e.g., in Section 1.1:

This document describes a method of adding an additional label stack entry (=
LSE) at the bottom of stack in order to facilitate the load balancing of the=
 flows within a PW over the available ECMPs.

One could argue that draft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseud=
owires, and that MPLS-TP does not use ECMP. IMHO and FWIW,
such an argument, were it presented, would be highly problematic, because:


1.       RFC 5960 (which defines the MPLS-TP data plane) did not define any=
 differences between the PW data plane in IP/MPLS and MPLS-TP.

2.       One of the most popular scenarios for using multi-segment pseudowir=
es is the case when an edge-to-edge service emulation crosses multiple IP/MP=
LS and MPLS-TP domains. In these scenarios, the flow label of draft-ietf-pwe=
3-fat-pw (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain) wo=
uld potentially compete with GAL (inserted by a T-PE at the edge of an MPLS-=
TP domain, e.g., for relying a PW status message that it has received over a=
 Targeted LDP session from the IP/MPLS domain to a static PW status message=
 to cross the MPLS-TP domain) for the bottom-of-stack position.

The issue I am raising Is not new. It has been actively discussed on the PWE=
3 mailing list with regard to adoption of draft-nadeau-pwe3-vccv-2 as a WG d=
ocument, with arguments  for both the flow label and GAL taking the bottom-o=
f-the-stack position. But, to the best of my understanding, consensus on thi=
s issue has not been reached.

Hopefully this comment will be useful.

Regards,
     Sasha


This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


--_000_A3C5DF08D38B6049839A6F553B331C760111EF7BD443ILPTMAIL02e_
Content-Type: text/html; charset="iso-8859-1"
content-transfer-encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-1=
">
<style>@font-face {
	font-family: Calibri;
}
@page WordSection1 {margin: 72.0pt 90.0pt 72.0pt 90.0pt; }
P.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
	MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.MsoListParagraph {
	MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 1=
1pt
}
LI.MsoListParagraph {
	MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 1=
1pt
}
DIV.MsoListParagraph {
	MARGIN: 0cm 0cm 0pt 36pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 1=
1pt
}
SPAN.EmailStyle17 {
	FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext
}
.MsoChpDefault {
	
}
DIV.WordSection1 {
	
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</style>
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.7600.16821">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" ocsi=3D"x">
<div style=3D"FONT-FAMILY: Times New Roman; DIRECTION: ltr; COLOR: #000000;=
 FONT-SIZE: 16px">
<div>Hi all,</div>
<div><font face=3D"times new roman">After having sent out my comments I've n=
oticed that the specific example to illustrate the need to combine GAL and &=
quot;flow label&quot; was inaccurate.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">A more relevant example would look like<=
a></a> following (I do not include a diagram, but it can be easily provided=
 if necessary)</font></div>
<ol>
<li><font face=3D"times new roman">A MS-PW:</font>
<ul style=3D"FONT-FAMILY: Times New Roman; FONT-SIZE: 12pt">
<li><font face=3D"times new roman">Starts at an S-PE that resides at the edg=
e of an MPLS-TP domain (no ECMP)</font>
</li><li><font face=3D"times new roman">Crosses this domain and enters an IP=
/MPLS domain with ECMP enabled using a T-PE that resides at the age of these=
 two domains</font>
</li><li><font face=3D"times new roman">Leaves this domain and enters a 2nd=
 MPLS-TP domain (using the 2nd T-PE)</font>
</li><li><font face=3D"times new roman">Terminates on another S-PE at&nbsp;t=
he<a></a> edge of the 2nd MPLS-TP domain</font></li></ul>
</li><li><font face=3D"times new roman">The operator intends to improve traf=
fic distribution in the IP/MPLS domain, hence he enables&nbsp;insertion<a></=
a> and discard of &quot;flow labels&quot; at the two S-PEs. Note that:</font=
>
<ul style=3D"FONT-FAMILY: Times New Roman; FONT-SIZE: 12pt">
<li><font face=3D"times new roman">This does not violate the MPLS-TP restric=
tion on ECMP: ECMP does not happen in he MPLS-TP domains</font>
</li><li><font face=3D"times new roman">T-PEs do not even have to be aware o=
f flow labels</font></li></ul>
</li><li><font face=3D"times new roman">The operator also intends to operate=
 some end-to-end OAM for this MS-PW using &quot;GAL-in-PW&quot;. This result=
s in a conflict since both GAL and &quot;flow label&quot; are defined (in th=
e&nbsp;corresponding<a></a> drafts) as bottom of stack.</font></li></ol>
<p><font face=3D"times new roman"></font>&nbsp;</p>
<div dir=3D"ltr"><font color=3D"#000000" size=3D"3" face=3D"Times New Roman"=
>IMHO this describes a realistic scenario where the two drafts are in contro=
versy.</font></div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman">Regards,</font></div>
<div dir=3D"ltr"><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sas=
ha</font></div>
<div style=3D"DIRECTION: ltr" id=3D"divRpF541204">
<hr tabindex=3D"-1">
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><b>From:</b> mpls-bounces=
@ietf.org [mpls-bounces@ietf.org] On Behalf Of Alexander Vainshtein [Alexand=
er.Vainshtein@ecitele.com]<br>
<b>Sent:</b> Tuesday, August 16, 2011 4:26 PM<br>
<b>To:</b> ietf@ietf.org<br>
<b>Cc:</b> mpls@ietf.org; Vladimir Kleiner; Idan Kaspit; Mishael Wexler; pwe=
3; Oren Gal; John Shirron; Rotem Cohen<br>
<b>Subject:</b> [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw<b=
r>
</font><br>
</div>
<div></div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I would like to raise the following issue with regard=
 to <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-i=
n-pw/?include_text=3D1" target=3D"_blank">
draft-ietf-pwe3-gal-in-pw</a>: controversy vs. <a href=3D"http://datatracker=
.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1" target=3D"_blank">
draft-ietf-pwe3-fat-pw</a> with regard to bottom-of-stack position.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">As stated in the Introduction, this draft removes the=
 restriction imposed by RFC 5586 on usage of Generic Associated Channel Labe=
l (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586 states:</p>
<p style=3D"LINE-HEIGHT: 14.4pt; MARGIN-LEFT: 36pt" class=3D"MsoNormal"><spa=
n style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">In MPLS-TP, the GAL=
 MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs=
, and with Sections, and MUST NOT be
 used with PWs.&nbsp; It MUST always be at the bottom of the label stack &nb=
sp;&nbsp;&nbsp;(i.e., S bit set to 1).</span></p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">draft-ietf-pwe3-gal-in-pw proposed to replace the ori=
ginal text in RFC 5586 with the following</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt; MARGIN-LEFT: 36pt" class=3D"MsoNormal"><spa=
n style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">In MPLS-TP, the GAL=
 MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs=
, and with Sections, and MAY be used
 with PWs. It MUST always be at the bottom of the label stack (i.e., S bit s=
et to 1).</span></p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal"><span style=3D"FONT-FAM=
ILY: 'Courier New'; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">I.e., &nbsp;while remov=
ing this restriction of 5586, it does not modify its requirement for the GAL=
 being always at the bottom of the label stack.
</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">At the same draft-ietf-=
pwe3-fat-pw (currently also in the IESG review) reserves the bottom of the P=
W stack for the PW flow labels, e.g., in Section 1.1:</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt; MARGIN-LEFT: 36pt" class=3D"MsoNormal"><spa=
n style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">This document descri=
bes a method of adding an additional label stack entry (LSE) at the bottom o=
f stack in order to facilitate the
 load balancing of the flows within a PW over the available ECMPs.&nbsp; </s=
pan></p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">One could argue that dr=
aft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseudowires, and that MPLS-T=
P does not use ECMP. IMHO and FWIW,
</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">such an argument, were=
 it presented, would be highly problematic, because:</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt; TEXT-INDENT: -18pt" class=3D"MsoListParagra=
ph"><span>1.<span style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
</span></span><span dir=3D"ltr"></span>RFC 5960 (which defines the MPLS-TP d=
ata plane) did not define any differences between the PW data plane in IP/MP=
LS and MPLS-TP.
</p>
<p style=3D"LINE-HEIGHT: 14.4pt; TEXT-INDENT: -18pt" class=3D"MsoListParagra=
ph"><span>2.<span style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;
</span></span><span dir=3D"ltr"></span>One of the most popular scenarios for=
 using multi-segment pseudowires is the case when an edge-to-edge service em=
ulation crosses multiple IP/MPLS and MPLS-TP domains. In these scenarios, th=
e flow label of draft-ietf-pwe3-fat-pw
 (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain) would pote=
ntially compete with GAL (inserted by a T-PE at the edge of an MPLS-TP domai=
n, e.g., for relying a PW status message that it has received over a Targete=
d LDP session from the IP/MPLS
 domain to a static PW status message to cross the MPLS-TP domain) for the b=
ottom-of-stack position.
</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">The issue I am raising=
 Is not new. It has been actively discussed on the PWE3 mailing list with re=
gard to adoption of draft-nadeau-pwe3-vccv-2 as a WG document, with argument=
s &nbsp;for both the flow label and GAL
 taking the bottom-of-the-stack position. But, to the best of my understandi=
ng, consensus on this issue has not been reached.</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Hopefully this comment will be useful.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Regards,</p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</p>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<p>This e-mail message is intended for the recipient only and contains infor=
mation which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If=
 you have received this transmission in error, please inform us by e-mail, p=
hone or fax, and then delete
 the original and all copies thereof. </p>
</div>
</div>
<p>
This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.
</p>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C760111EF7BD443ILPTMAIL02e_--

From pabloisnot@gmail.com  Tue Aug 16 14:16:59 2011
Return-Path: <pabloisnot@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BACA11E80A1; Tue, 16 Aug 2011 14:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.627
X-Spam-Level: 
X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=0.971,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEtAR9AImzN6; Tue, 16 Aug 2011 14:16:58 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id E16E221F8B5A; Tue, 16 Aug 2011 14:16:57 -0700 (PDT)
Received: by qwc23 with SMTP id 23so265773qwc.31 for <multiple recipients>; Tue, 16 Aug 2011 14:17:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ITT/6udhCCGAqO5aSgr4ZoRMsNlOdvUOXhtaOVWhGhA=; b=urcvgw4wORqEeb/c7eWNPWHzcNLuQhWQWBroRoGEmsnpShxhq32d/t4+Qs+rk1iawe e9xvZImcIer4sUrhGXiC1liDuYvgwpsX2mXZfRyH9Ls6PL6jDFB2E4YAnK52SIzbR3dt XrpwZBYj7/I8+ASf09EcsphQzY2itNO1DiEgY=
MIME-Version: 1.0
Received: by 10.224.202.196 with SMTP id ff4mr208023qab.391.1313529466826; Tue, 16 Aug 2011 14:17:46 -0700 (PDT)
Received: by 10.224.45.146 with HTTP; Tue, 16 Aug 2011 14:17:46 -0700 (PDT)
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>
Date: Tue, 16 Aug 2011 17:17:46 -0400
Message-ID: <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com>
Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
From: Pablo Frank <pabloisnot@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: multipart/alternative; boundary=20cf300fb42d45b07d04aaa5e901
X-Mailman-Approved-At: Wed, 17 Aug 2011 10:38:05 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 21:16:59 -0000

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

I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS domain
in the middle segment, you're no longer in an MPLS-TP environment and so the
GAL is not required to be BOS.  During that middle segment, the PW flow
label would be placed below the GAL and above the GACh.  It gets removed
when it hits the S-PE that switches you back into the MPLS-TP environment.
 In other words, whether you're in an MPLS-TP environment is determined
segment by segment in a MS-PW.

Pablo

On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein <
Alexander.Vainshtein@ecitele.com> wrote:

>  Hi all,
> After having sent out my comments I've noticed that the specific example to
> illustrate the need to combine GAL and "flow label" was inaccurate.
>
> A more relevant example would look like following (I do not include a
> diagram, but it can be easily provided if necessary)
>
>    1. A MS-PW:
>       - Starts at an S-PE that resides at the edge of an MPLS-TP domain
>       (no ECMP)
>       - Crosses this domain and enters an IP/MPLS domain with ECMP enabled
>       using a T-PE that resides at the age of these two domains
>       - Leaves this domain and enters a 2nd MPLS-TP domain (using the 2nd
>       T-PE)
>       - Terminates on another S-PE at the edge of the 2nd MPLS-TP domain
>    2. The operator intends to improve traffic distribution in the IP/MPLS
>    domain, hence he enables insertion and discard of "flow labels" at the
>    two S-PEs. Note that:
>       - This does not violate the MPLS-TP restriction on ECMP: ECMP does
>       not happen in he MPLS-TP domains
>       - T-PEs do not even have to be aware of flow labels
>    3. The operator also intends to operate some end-to-end OAM for this
>    MS-PW using "GAL-in-PW". This results in a conflict since both GAL and "flow
>    label" are defined (in the corresponding drafts) as bottom of stack.
>
>
> IMHO this describes a realistic scenario where the two drafts are in
> controversy.
>
> Regards,
>      Sasha
>  ------------------------------
> *From:* mpls-bounces@ietf.org [mpls-bounces@ietf.org] On Behalf Of
> Alexander Vainshtein [Alexander.Vainshtein@ecitele.com]
> *Sent:* Tuesday, August 16, 2011 4:26 PM
> *To:* ietf@ietf.org
> *Cc:* mpls@ietf.org; Vladimir Kleiner; Idan Kaspit; Mishael Wexler; pwe3;
> Oren Gal; John Shirron; Rotem Cohen
> *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
>
>   Hi all,
>
>
>
> I would like to raise the following issue with regard to
> draft-ietf-pwe3-gal-in-pw<http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?include_text=1>:
> controversy vs. draft-ietf-pwe3-fat-pw<http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=1>with regard to bottom-of-stack position.
>
>
>
> As stated in the Introduction, this draft removes the restriction imposed
> by RFC 5586 on usage of Generic Associated Channel Label (GAL) in PWs. The
> corresponding text Section 4.2 of RFC 5586 states:
>
> In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
> Concatenated Segments of LSPs, and with Sections, and MUST NOT be used with
> PWs.  It MUST always be at the bottom of the label stack    (i.e., S bit set
> to 1).
>
>
>
> draft-ietf-pwe3-gal-in-pw proposed to replace the original text in RFC 5586
> with the following
>
>
>
> In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
> Concatenated Segments of LSPs, and with Sections, and MAY be used with PWs.
> It MUST always be at the bottom of the label stack (i.e., S bit set to 1).
>
>
>
> I.e.,  while removing this restriction of 5586, it does not modify its
> requirement for the GAL being always at the bottom of the label stack.
>
>
>
> At the same draft-ietf-pwe3-fat-pw (currently also in the IESG review)
> reserves the bottom of the PW stack for the PW flow labels, e.g., in Section
> 1.1:
>
>
>
> This document describes a method of adding an additional label stack entry
> (LSE) at the bottom of stack in order to facilitate the load balancing of
> the flows within a PW over the available ECMPs.
>
>
>
> One could argue that draft-ietf-pwe3-gal-in-pw only applies to MPLS-TP
> pseudowires, and that MPLS-TP does not use ECMP. IMHO and FWIW,
>
> such an argument, were it presented, would be highly problematic, because:
>
>
>
> 1.       RFC 5960 (which defines the MPLS-TP data plane) did not define
> any differences between the PW data plane in IP/MPLS and MPLS-TP.
>
> 2.       One of the most popular scenarios for using multi-segment
> pseudowires is the case when an edge-to-edge service emulation crosses
> multiple IP/MPLS and MPLS-TP domains. In these scenarios, the flow label of
> draft-ietf-pwe3-fat-pw (inserted by a flow-aware T-PE at the edge of an
> IP/MPLS domain) would potentially compete with GAL (inserted by a T-PE at
> the edge of an MPLS-TP domain, e.g., for relying a PW status message that it
> has received over a Targeted LDP session from the IP/MPLS domain to a static
> PW status message to cross the MPLS-TP domain) for the bottom-of-stack
> position.
>
>
>
> The issue I am raising Is not new. It has been actively discussed on the
> PWE3 mailing list with regard to adoption of draft-nadeau-pwe3-vccv-2 as a
> WG document, with arguments  for both the flow label and GAL taking the
> bottom-of-the-stack position. But, to the best of my understanding,
> consensus on this issue has not been reached.
>
>
>
> Hopefully this comment will be useful.
>
>
>
> Regards,
>
>      Sasha
>
>
>
> This e-mail message is intended for the recipient only and contains
> information which is CONFIDENTIAL and which may be proprietary to ECI
> Telecom. If you have received this transmission in error, please inform us
> by e-mail, phone or fax, and then delete the original and all copies
> thereof.
>
> This e-mail message is intended for the recipient only and contains
> information which is CONFIDENTIAL and which may be proprietary to ECI
> Telecom. If you have received this transmission in error, please inform us
> by e-mail, phone or fax, and then delete the original and all copies
> thereof.
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>

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

I think it&#39;s okay because as the PW crosses the ECMP-enabled IP/MPLS do=
main in the middle segment, you&#39;re no longer in an MPLS-TP environment =
and so the GAL is not required to be BOS. =A0During that middle segment, th=
e PW flow label would be placed below the GAL and above the GACh. =A0It get=
s removed when it hits the S-PE that switches you back into the MPLS-TP env=
ironment. =A0In other words, whether you&#39;re in an MPLS-TP environment i=
s determined segment by segment in a MS-PW.<div>
<br></div><div>Pablo<br><br><div class=3D"gmail_quote">On Tue, Aug 16, 2011=
 at 1:02 PM, Alexander Vainshtein <span dir=3D"ltr">&lt;<a href=3D"mailto:A=
lexander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.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 lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div style=3D"font-family:Times New Roman;direction:ltr;color:#000000;font-=
size:16px">
<div>Hi all,</div>
<div><font face=3D"times new roman">After having sent out my comments I&#39=
;ve noticed that the specific example to illustrate the need to combine GAL=
 and &quot;flow label&quot; was inaccurate.</font></div>
<div><font face=3D"times new roman"></font>=A0</div>
<div><font face=3D"times new roman">A more relevant example would look like=
<a></a> following (I do not include a diagram, but it can be easily provide=
d if necessary)</font></div>
<ol>
<li><font face=3D"times new roman">A MS-PW:</font>
<ul style=3D"font-family:Times New Roman;font-size:12pt">
<li><font face=3D"times new roman">Starts at an S-PE that resides at the ed=
ge of an MPLS-TP domain (no ECMP)</font>
</li><li><font face=3D"times new roman">Crosses this domain and enters an I=
P/MPLS domain with ECMP enabled using a T-PE that resides at the age of the=
se two domains</font>
</li><li><font face=3D"times new roman">Leaves this domain and enters a 2nd=
 MPLS-TP domain (using the 2nd T-PE)</font>
</li><li><font face=3D"times new roman">Terminates on another S-PE at=A0the=
<a></a> edge of the 2nd MPLS-TP domain</font></li></ul>
</li><li><font face=3D"times new roman">The operator intends to improve tra=
ffic distribution in the IP/MPLS domain, hence he enables=A0insertion<a></a=
> and discard of &quot;flow labels&quot; at the two S-PEs. Note that:</font=
>
<ul style=3D"font-family:Times New Roman;font-size:12pt">
<li><font face=3D"times new roman">This does not violate the MPLS-TP restri=
ction on ECMP: ECMP does not happen in he MPLS-TP domains</font>
</li><li><font face=3D"times new roman">T-PEs do not even have to be aware =
of flow labels</font></li></ul>
</li><li><font face=3D"times new roman">The operator also intends to operat=
e some end-to-end OAM for this MS-PW using &quot;GAL-in-PW&quot;. This resu=
lts in a conflict since both GAL and &quot;flow label&quot; are defined (in=
 the=A0corresponding<a></a> drafts) as bottom of stack.</font></li>
</ol>
<p><font face=3D"times new roman"></font>=A0</p>
<div dir=3D"ltr"><font color=3D"#000000" size=3D"3" face=3D"Times New Roman=
">IMHO this describes a realistic scenario where the two drafts are in cont=
roversy.</font></div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>=A0</div>
<div dir=3D"ltr"><font face=3D"times new roman">Regards,</font></div>
<div dir=3D"ltr"><font face=3D"times new roman">=A0=A0=A0=A0 Sasha</font></=
div>
<div style=3D"direction:ltr">
<hr>
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><b>From:</b> <a href=3D"=
mailto:mpls-bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a> [=
<a href=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank">mpls-bounces@iet=
f.org</a>] On Behalf Of Alexander Vainshtein [<a href=3D"mailto:Alexander.V=
ainshtein@ecitele.com" target=3D"_blank">Alexander.Vainshtein@ecitele.com</=
a>]<br>

<b>Sent:</b> Tuesday, August 16, 2011 4:26 PM<br>
<b>To:</b> <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org=
</a><br>
<b>Cc:</b> <a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org=
</a>; Vladimir Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John S=
hirron; Rotem Cohen<br>
<b>Subject:</b> [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw<=
br>
</font><br>
</div>
<div></div>
<div>
<div>
<p class=3D"MsoNormal">Hi all,</p>
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">I would like to raise the following issue with regar=
d to <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal=
-in-pw/?include_text=3D1" target=3D"_blank">
draft-ietf-pwe3-gal-in-pw</a>: controversy vs. <a href=3D"http://datatracke=
r.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1" target=3D"_blank">
draft-ietf-pwe3-fat-pw</a> with regard to bottom-of-stack position.</p>
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">As stated in the Introduction, this draft removes th=
e restriction imposed by RFC 5586 on usage of Generic Associated Channel La=
bel (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586 states:</p=
>

<p style=3D"line-height:14.4pt;margin-left:36pt" class=3D"MsoNormal"><span =
style=3D"font-family:&#39;Courier New&#39;;font-size:10pt">In MPLS-TP, the =
GAL MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of =
LSPs, and with Sections, and MUST NOT be
 used with PWs.=A0 It MUST always be at the bottom of the label stack =A0=
=A0=A0(i.e., S bit set to 1).</span></p>
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">draft-ietf-pwe3-gal-in-pw proposed to replace the or=
iginal text in RFC 5586 with the following</p>
<p class=3D"MsoNormal">=A0</p>
<p style=3D"line-height:14.4pt;margin-left:36pt" class=3D"MsoNormal"><span =
style=3D"font-family:&#39;Courier New&#39;;font-size:10pt">In MPLS-TP, the =
GAL MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of =
LSPs, and with Sections, and MAY be used
 with PWs. It MUST always be at the bottom of the label stack (i.e., S bit =
set to 1).</span></p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal"><span style=3D"font-fam=
ily:&#39;Courier New&#39;;font-size:10pt"></span>=A0</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">I.e., =A0while removing=
 this restriction of 5586, it does not modify its requirement for the GAL b=
eing always at the bottom of the label stack.
</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">=A0</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">At the same draft-ietf-=
pwe3-fat-pw (currently also in the IESG review) reserves the bottom of the =
PW stack for the PW flow labels, e.g., in Section 1.1:</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">=A0</p>
<p style=3D"line-height:14.4pt;margin-left:36pt" class=3D"MsoNormal"><span =
style=3D"font-family:&#39;Courier New&#39;;font-size:10pt">This document de=
scribes a method of adding an additional label stack entry (LSE) at the bot=
tom of stack in order to facilitate the
 load balancing of the flows within a PW over the available ECMPs.=A0 </spa=
n></p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">=A0</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">One could argue that dr=
aft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseudowires, and that MPLS-=
TP does not use ECMP. IMHO and FWIW,
</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">such an argument, were =
it presented, would be highly problematic, because:</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">=A0</p>
<p style=3D"line-height:14.4pt"><span>1.<span style=3D"font:7pt &#39;Times =
New Roman&#39;">=A0=A0=A0=A0=A0=A0
</span></span><span dir=3D"ltr"></span>RFC 5960 (which defines the MPLS-TP =
data plane) did not define any differences between the PW data plane in IP/=
MPLS and MPLS-TP.
</p>
<p style=3D"line-height:14.4pt"><span>2.<span style=3D"font:7pt &#39;Times =
New Roman&#39;">=A0=A0=A0=A0=A0=A0
</span></span><span dir=3D"ltr"></span>One of the most popular scenarios fo=
r using multi-segment pseudowires is the case when an edge-to-edge service =
emulation crosses multiple IP/MPLS and MPLS-TP domains. In these scenarios,=
 the flow label of draft-ietf-pwe3-fat-pw
 (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain) would pot=
entially compete with GAL (inserted by a T-PE at the edge of an MPLS-TP dom=
ain, e.g., for relying a PW status message that it has received over a Targ=
eted LDP session from the IP/MPLS
 domain to a static PW status message to cross the MPLS-TP domain) for the =
bottom-of-stack position.
</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">=A0</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">The issue I am raising =
Is not new. It has been actively discussed on the PWE3 mailing list with re=
gard to adoption of draft-nadeau-pwe3-vccv-2 as a WG document, with argumen=
ts =A0for both the flow label and GAL
 taking the bottom-of-the-stack position. But, to the best of my understand=
ing, consensus on this issue has not been reached.</p>
<p style=3D"line-height:14.4pt" class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">Hopefully this comment will be useful.</p>
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">Regards,</p>
<p class=3D"MsoNormal">=A0=A0=A0=A0 Sasha</p>
<p class=3D"MsoNormal">=A0</p>
</div>
<p>This e-mail message is intended for the recipient only and contains info=
rmation which is CONFIDENTIAL and which may be proprietary to ECI Telecom. =
If you have received this transmission in error, please inform us by e-mail=
, phone or fax, and then delete
 the original and all copies thereof. </p>
</div>
</div>
<p>
This e-mail message is intended for the recipient only and contains informa=
tion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If =
you have received this transmission in error, please inform us by e-mail, p=
hone or fax, and then delete the original and all copies thereof.
</p>
</div>

<br>_______________________________________________<br>
pwe3 mailing list<br>
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/pwe3</a><br>
<br></blockquote></div><br></div>

--20cf300fb42d45b07d04aaa5e901--

From davari@broadcom.com  Tue Aug 16 14:24:11 2011
Return-Path: <davari@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1805B11E80AB; Tue, 16 Aug 2011 14:24:11 -0700 (PDT)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ncQkFkN9WeZE; Tue, 16 Aug 2011 14:24:07 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id E56CA11E8085; Tue, 16 Aug 2011 14:24:06 -0700 (PDT)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Tue, 16 Aug 2011 14:29:56 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Tue, 16 Aug 2011 14:24:41 -0700
From: "Shahram Davari" <davari@broadcom.com>
To: "Pablo Frank" <pabloisnot@gmail.com>, "Alexander Vainshtein" <Alexander.Vainshtein@ecitele.com>
Date: Tue, 16 Aug 2011 14:24:39 -0700
Subject: RE: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Topic: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxcWgC3iJ/eCK3bTEKpvSbExjfcvQAAKyWQ
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD6A932A5AFE5@SJEXCHCCR02.corp.ad.broadcom.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com> <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com>
In-Reply-To: <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 62543EDE3KO6562533-01-01
Content-Type: multipart/alternative; boundary=_000_2C2F1EBA8050E74EA81502D5740B4BD6A932A5AFE5SJEXCHCCR02co_
X-Mailman-Approved-At: Wed, 17 Aug 2011 10:38:05 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 21:24:11 -0000

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

Pablo,

This is not acceptable. Are you suggesting an LSR to pop a label that is no=
t to of the stack? I can assure you 99.99% of HW out there can't do this.

Thx
SD

From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Pab=
lo Frank
Sent: Tuesday, August 16, 2011 2:18 PM
To: Alexander Vainshtein
Cc: mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit; Mishael We=
xler; pwe3; Oren Gal; John Shirron; Rotem Cohen
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in=
-pw

I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS domain=
 in the middle segment, you're no longer in an MPLS-TP environment and so t=
he GAL is not required to be BOS.  During that middle segment, the PW flow =
label would be placed below the GAL and above the GACh.  It gets removed wh=
en it hits the S-PE that switches you back into the MPLS-TP environment.  I=
n other words, whether you're in an MPLS-TP environment is determined segme=
nt by segment in a MS-PW.

Pablo
On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein <Alexander.Vainshtein=
@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Hi all,
After having sent out my comments I've noticed that the specific example to=
 illustrate the need to combine GAL and "flow label" was inaccurate.

A more relevant example would look like following (I do not include a diagr=
am, but it can be easily provided if necessary)

 1.  A MS-PW:

    *   Starts at an S-PE that resides at the edge of an MPLS-TP domain (no=
 ECMP)
    *   Crosses this domain and enters an IP/MPLS domain with ECMP enabled =
using a T-PE that resides at the age of these two domains
    *   Leaves this domain and enters a 2nd MPLS-TP domain (using the 2nd T=
-PE)
    *   Terminates on another S-PE at the edge of the 2nd MPLS-TP domain

 1.  The operator intends to improve traffic distribution in the IP/MPLS do=
main, hence he enables insertion and discard of "flow labels" at the two S-=
PEs. Note that:

    *   This does not violate the MPLS-TP restriction on ECMP: ECMP does no=
t happen in he MPLS-TP domains
    *   T-PEs do not even have to be aware of flow labels

 1.  The operator also intends to operate some end-to-end OAM for this MS-P=
W using "GAL-in-PW". This results in a conflict since both GAL and "flow la=
bel" are defined (in the corresponding drafts) as bottom of stack.


IMHO this describes a realistic scenario where the two drafts are in contro=
versy.

Regards,
     Sasha
________________________________
From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mpls-bounces@iet=
f.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Alexander Vainshtein [Ale=
xander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>]
Sent: Tuesday, August 16, 2011 4:26 PM
To: ietf@ietf.org<mailto:ietf@ietf.org>
Cc: mpls@ietf.org<mailto:mpls@ietf.org>; Vladimir Kleiner; Idan Kaspit; Mis=
hael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
Subject: [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Hi all,

I would like to raise the following issue with regard to draft-ietf-pwe3-ga=
l-in-pw<http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?=
include_text=3D1>: controversy vs. draft-ietf-pwe3-fat-pw<http://datatracke=
r.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1> with regard to bot=
tom-of-stack position.

As stated in the Introduction, this draft removes the restriction imposed b=
y RFC 5586 on usage of Generic Associated Channel Label (GAL) in PWs. The c=
orresponding text Section 4.2 of RFC 5586 states:
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatena=
ted Segments of LSPs, and with Sections, and MUST NOT be used with PWs.  It=
 MUST always be at the bottom of the label stack    (i.e., S bit set to 1).

draft-ietf-pwe3-gal-in-pw proposed to replace the original text in RFC 5586=
 with the following

In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatena=
ted Segments of LSPs, and with Sections, and MAY be used with PWs. It MUST =
always be at the bottom of the label stack (i.e., S bit set to 1).

I.e.,  while removing this restriction of 5586, it does not modify its requ=
irement for the GAL being always at the bottom of the label stack.

At the same draft-ietf-pwe3-fat-pw (currently also in the IESG review) rese=
rves the bottom of the PW stack for the PW flow labels, e.g., in Section 1.=
1:

This document describes a method of adding an additional label stack entry =
(LSE) at the bottom of stack in order to facilitate the load balancing of t=
he flows within a PW over the available ECMPs.

One could argue that draft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseu=
dowires, and that MPLS-TP does not use ECMP. IMHO and FWIW,
such an argument, were it presented, would be highly problematic, because:


1.       RFC 5960 (which defines the MPLS-TP data plane) did not define any=
 differences between the PW data plane in IP/MPLS and MPLS-TP.

2.       One of the most popular scenarios for using multi-segment pseudowi=
res is the case when an edge-to-edge service emulation crosses multiple IP/=
MPLS and MPLS-TP domains. In these scenarios, the flow label of draft-ietf-=
pwe3-fat-pw (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain=
) would potentially compete with GAL (inserted by a T-PE at the edge of an =
MPLS-TP domain, e.g., for relying a PW status message that it has received =
over a Targeted LDP session from the IP/MPLS domain to a static PW status m=
essage to cross the MPLS-TP domain) for the bottom-of-stack position.

The issue I am raising Is not new. It has been actively discussed on the PW=
E3 mailing list with regard to adoption of draft-nadeau-pwe3-vccv-2 as a WG=
 document, with arguments  for both the flow label and GAL taking the botto=
m-of-the-stack position. But, to the best of my understanding, consensus on=
 this issue has not been reached.

Hopefully this comment will be useful.

Regards,
     Sasha


This e-mail message is intended for the recipient only and contains informa=
tion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If =
you have received this transmission in error, please inform us by e-mail, p=
hone or fax, and then delete the original and all copies thereof.

This e-mail message is intended for the recipient only and contains informa=
tion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If =
you have received this transmission in error, please inform us by e-mail, p=
hone or fax, and then delete the original and all copies thereof.

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


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:698551489;
	mso-list-template-ids:171464274;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Pablo,<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'>This is not acceptable. Are you suggesting an L=
SR to pop a label that is not to of the stack? I can assure you 99.99% of H=
W out there can&#8217;t do this.<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thx<o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>SD<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;b=
order-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNorm=
al><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Fr=
om:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif"'> mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] <b>On Behalf Of=
 </b>Pablo Frank<br><b>Sent:</b> Tuesday, August 16, 2011 2:18 PM<br><b>To:=
</b> Alexander Vainshtein<br><b>Cc:</b> mpls@ietf.org; ietf@ietf.org; Vladi=
mir Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rot=
em Cohen<br><b>Subject:</b> Re: [mpls] [PWE3] IETF Last Call comment on dra=
ft-ietf-pwe3-gal-in-pw<o:p></o:p></span></p></div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p><p class=3DMsoNormal>I think it's okay because as the PW c=
rosses the ECMP-enabled IP/MPLS domain in the middle segment, you're no lon=
ger in an MPLS-TP environment and so the GAL is not required to be BOS. &nb=
sp;During that middle segment, the PW flow label would be placed below the =
GAL and above the GACh. &nbsp;It gets removed when it hits the S-PE that sw=
itches you back into the MPLS-TP environment. &nbsp;In other words, whether=
 you're in an MPLS-TP environment is determined segment by segment in a MS-=
PW.<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div=
><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Pablo<o:p></o:p></p><d=
iv><p class=3DMsoNormal>On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshte=
in &lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainsh=
tein@ecitele.com</a>&gt; wrote:<o:p></o:p></p><div><div><div><p class=3DMso=
Normal><span style=3D'color:black'>Hi all,<o:p></o:p></span></p></div><div>=
<p class=3DMsoNormal><span style=3D'color:black'>After having sent out my c=
omments I've noticed that the specific example to illustrate the need to co=
mbine GAL and &quot;flow label&quot; was inaccurate.<o:p></o:p></span></p><=
/div><div><p class=3DMsoNormal><span style=3D'color:black'>&nbsp;<o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span style=3D'color:black'>A m=
ore relevant example would look like following (I do not include a diagram,=
 but it can be easily provided if necessary)<o:p></o:p></span></p></div><ol=
 start=3D1 type=3D1><li class=3DMsoNormal style=3D'color:black;mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>A MS-PW: <o=
:p></o:p></li></ol><ol start=3D1 type=3D1><ul type=3Dcircle><li class=3DMso=
Normal style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto;mso-list:l0 level2 lfo1'>Starts at an S-PE that resides at the edge of =
an MPLS-TP domain (no ECMP) <o:p></o:p></li><li class=3DMsoNormal style=3D'=
color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 =
level2 lfo1'>Crosses this domain and enters an IP/MPLS domain with ECMP ena=
bled using a T-PE that resides at the age of these two domains <o:p></o:p><=
/li><li class=3DMsoNormal style=3D'color:black;mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;mso-list:l0 level2 lfo1'>Leaves this domain and ente=
rs a 2nd MPLS-TP domain (using the 2nd T-PE) <o:p></o:p></li><li class=3DMs=
oNormal style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:=
auto;mso-list:l0 level2 lfo1'>Terminates on another S-PE at&nbsp;the edge o=
f the 2nd MPLS-TP domain<o:p></o:p></li></ul></ol><ol start=3D2 type=3D1><l=
i class=3DMsoNormal style=3D'color:black;mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto;mso-list:l0 level1 lfo1'>The operator intends to improve t=
raffic distribution in the IP/MPLS domain, hence he enables&nbsp;insertion =
and discard of &quot;flow labels&quot; at the two S-PEs. Note that: <o:p></=
o:p></li></ol><ol start=3D2 type=3D1><ul type=3Dcircle><li class=3DMsoNorma=
l style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l0 level2 lfo1'>This does not violate the MPLS-TP restriction on EC=
MP: ECMP does not happen in he MPLS-TP domains <o:p></o:p></li><li class=3D=
MsoNormal style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto;mso-list:l0 level2 lfo1'>T-PEs do not even have to be aware of flow =
labels<o:p></o:p></li></ul></ol><ol start=3D3 type=3D1><li class=3DMsoNorma=
l style=3D'color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;m=
so-list:l0 level1 lfo1'>The operator also intends to operate some end-to-en=
d OAM for this MS-PW using &quot;GAL-in-PW&quot;. This results in a conflic=
t since both GAL and &quot;flow label&quot; are defined (in the&nbsp;corres=
ponding drafts) as bottom of stack.<o:p></o:p></li></ol><p><span style=3D'c=
olor:black'>&nbsp;<o:p></o:p></span></p><div><p class=3DMsoNormal><span sty=
le=3D'color:black'>IMHO this describes a realistic scenario where the two d=
rafts are in controversy.<o:p></o:p></span></p></div><div><p class=3DMsoNor=
mal><span style=3D'color:black'>&nbsp;<o:p></o:p></span></p></div><div><p c=
lass=3DMsoNormal><span style=3D'color:black'>Regards,<o:p></o:p></span></p>=
</div><div><p class=3DMsoNormal><span style=3D'color:black'>&nbsp;&nbsp;&nb=
sp;&nbsp; Sasha<o:p></o:p></span></p></div><div><div class=3DMsoNormal alig=
n=3Dcenter style=3D'text-align:center'><span style=3D'color:black'><hr size=
=3D2 width=3D"100%" align=3Dcenter></span></div><p class=3DMsoNormal style=
=3D'margin-bottom:12.0pt'><b><span style=3D'font-size:10.0pt;font-family:"T=
ahoma","sans-serif";color:black'>From:</span></b><span style=3D'font-size:1=
0.0pt;font-family:"Tahoma","sans-serif";color:black'> <a href=3D"mailto:mpl=
s-bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a> [<a href=3D=
"mailto:mpls-bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a>]=
 On Behalf Of Alexander Vainshtein [<a href=3D"mailto:Alexander.Vainshtein@=
ecitele.com" target=3D"_blank">Alexander.Vainshtein@ecitele.com</a>]<br><b>=
Sent:</b> Tuesday, August 16, 2011 4:26 PM<br><b>To:</b> <a href=3D"mailto:=
ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a><br><b>Cc:</b> <a href=3D=
"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>; Vladimir Kleine=
r; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen<b=
r><b>Subject:</b> [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-p=
w</span><span style=3D'color:black'><o:p></o:p></span></p></div><div><div><=
p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:=
auto'><span style=3D'color:black'>Hi all,<o:p></o:p></span></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span=
 style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal sty=
le=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'co=
lor:black'>I would like to raise the following issue with regard to <a href=
=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?incl=
ude_text=3D1" target=3D"_blank">draft-ietf-pwe3-gal-in-pw</a>: controversy =
vs. <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-pw/?incl=
ude_text=3D1" target=3D"_blank">draft-ietf-pwe3-fat-pw</a> with regard to b=
ottom-of-stack position.<o:p></o:p></span></p><p class=3DMsoNormal style=3D=
'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:b=
lack'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:black'>As sta=
ted in the Introduction, this draft removes the restriction imposed by RFC =
5586 on usage of Generic Associated Channel Label (GAL) in PWs. The corresp=
onding text Section 4.2 of RFC 5586 states:<o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;ma=
rgin-left:.5in;line-height:14.4pt'><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New";color:black'>In MPLS-TP, the GAL MUST be used with packet=
s on a G-ACh on LSPs, Concatenated Segments of LSPs, and with Sections, and=
 MUST NOT be used with PWs.&nbsp; It MUST always be at the bottom of the la=
bel stack &nbsp;&nbsp;&nbsp;(i.e., S bit set to 1).</span><span style=3D'co=
lor:black'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:black'>&nbsp;<=
o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;=
mso-margin-bottom-alt:auto'><span style=3D'color:black'>draft-ietf-pwe3-gal=
-in-pw proposed to replace the original text in RFC 5586 with the following=
<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto=
;mso-margin-bottom-alt:auto'><span style=3D'color:black'>&nbsp;<o:p></o:p><=
/span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-=
bottom-alt:auto;margin-left:.5in;line-height:14.4pt'><span style=3D'font-si=
ze:10.0pt;font-family:"Courier New";color:black'>In MPLS-TP, the GAL MUST b=
e used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs, and =
with Sections, and MAY be used with PWs. It MUST always be at the bottom of=
 the label stack (i.e., S bit set to 1).</span><span style=3D'color:black'>=
<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto=
;mso-margin-bottom-alt:auto;line-height:14.4pt'><span style=3D'color:black'=
>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-a=
lt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'><span style=3D'color=
:black'>I.e., &nbsp;while removing this restriction of 5586, it does not mo=
dify its requirement for the GAL being always at the bottom of the label st=
ack. <o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt=
:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'><span style=3D'color:b=
lack'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-=
top-alt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'><span style=3D'=
color:black'>At the same draft-ietf-pwe3-fat-pw (currently also in the IESG=
 review) reserves the bottom of the PW stack for the PW flow labels, e.g., =
in Section 1.1:<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'><span style=
=3D'color:black'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal style=3D'=
mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;line-he=
ight:14.4pt'><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>This document describes a method of adding an additional label sta=
ck entry (LSE) at the bottom of stack in order to facilitate the load balan=
cing of the flows within a PW over the available ECMPs.&nbsp; </span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'><span=
 style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal sty=
le=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt=
'><span style=3D'color:black'>One could argue that draft-ietf-pwe3-gal-in-p=
w only applies to MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. =
IMHO and FWIW, <o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'><span style=
=3D'color:black'>such an argument, were it presented, would be highly probl=
ematic, because:<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'><span style=
=3D'color:black'>&nbsp;<o:p></o:p></span></p><p style=3D'line-height:14.4pt=
'><span style=3D'color:black'>1.</span><span style=3D'font-size:7.0pt;color=
:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style=3D'color:bl=
ack'>RFC 5960 (which defines the MPLS-TP data plane) did not define any dif=
ferences between the PW data plane in IP/MPLS and MPLS-TP. <o:p></o:p></spa=
n></p><p style=3D'line-height:14.4pt'><span style=3D'color:black'>2.</span>=
<span style=3D'font-size:7.0pt;color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; </span><span style=3D'color:black'>One of the most popular scenarios =
for using multi-segment pseudowires is the case when an edge-to-edge servic=
e emulation crosses multiple IP/MPLS and MPLS-TP domains. In these scenario=
s, the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-aware T-PE =
at the edge of an IP/MPLS domain) would potentially compete with GAL (inser=
ted by a T-PE at the edge of an MPLS-TP domain, e.g., for relying a PW stat=
us message that it has received over a Targeted LDP session from the IP/MPL=
S domain to a static PW status message to cross the MPLS-TP domain) for the=
 bottom-of-stack position. <o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:14.4pt'>=
<span style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNorma=
l style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:1=
4.4pt'><span style=3D'color:black'>The issue I am raising Is not new. It ha=
s been actively discussed on the PWE3 mailing list with regard to adoption =
of draft-nadeau-pwe3-vccv-2 as a WG document, with arguments &nbsp;for both=
 the flow label and GAL taking the bottom-of-the-stack position. But, to th=
e best of my understanding, consensus on this issue has not been reached.<o=
:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;m=
so-margin-bottom-alt:auto;line-height:14.4pt'><span style=3D'color:black'>&=
nbsp;<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt=
:auto;mso-margin-bottom-alt:auto'><span style=3D'color:black'>Hopefully thi=
s comment will be useful.<o:p></o:p></span></p><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'colo=
r:black'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:black'>Reg=
ards,<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-margin-top-alt=
:auto;mso-margin-bottom-alt:auto'><span style=3D'color:black'>&nbsp;&nbsp;&=
nbsp;&nbsp; Sasha<o:p></o:p></span></p><p class=3DMsoNormal style=3D'mso-ma=
rgin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'color:black'>&=
nbsp;<o:p></o:p></span></p></div><p><span style=3D'color:black'>This e-mail=
 message is intended for the recipient only and contains information which =
is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have re=
ceived this transmission in error, please inform us by e-mail, phone or fax=
, and then delete the original and all copies thereof. <o:p></o:p></span></=
p></div></div><p>This e-mail message is intended for the recipient only and=
 contains information which is CONFIDENTIAL and which may be proprietary to=
 ECI Telecom. If you have received this transmission in error, please infor=
m us by e-mail, phone or fax, and then delete the original and all copies t=
hereof. <o:p></o:p></p></div><p class=3DMsoNormal style=3D'margin-bottom:12=
.0pt'><br>_______________________________________________<br>pwe3 mailing l=
ist<br><a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br><a href=3D"htt=
ps://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">https://www.ietf=
.org/mailman/listinfo/pwe3</a><o:p></o:p></p></div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p></div></div></body></html>=

--_000_2C2F1EBA8050E74EA81502D5740B4BD6A932A5AFE5SJEXCHCCR02co_--


From pabloisnot@gmail.com  Tue Aug 16 15:20:00 2011
Return-Path: <pabloisnot@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E55CE21F8AF7; Tue, 16 Aug 2011 15:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.715
X-Spam-Level: 
X-Spam-Status: No, score=-2.715 tagged_above=-999 required=5 tests=[AWL=0.883,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQytu4G42jX5; Tue, 16 Aug 2011 15:19:59 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 2B6A721F8AF3; Tue, 16 Aug 2011 15:19:59 -0700 (PDT)
Received: by qyk35 with SMTP id 35so289966qyk.10 for <multiple recipients>; Tue, 16 Aug 2011 15:20:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GG1lOBxwpsd7UFLZSspPo1lXsfxrI/lHsHEH1A7ID0U=; b=SNlKeYhCerYsH14CVDZZoG+RAKtIkihV3vXj90shhKUWSZ3frc5d/wdpqogYs8O5Da D5I7deS1kHxfFx6tPt881OmXxyxD5QvyX6pxGj1SRVHjmBkBlifQaab5D90/uE7938aV 8gnILAjAzNWshqjGR94n92zdDjamCNJNf6s+s=
MIME-Version: 1.0
Received: by 10.224.200.202 with SMTP id ex10mr279993qab.241.1313533248220; Tue, 16 Aug 2011 15:20:48 -0700 (PDT)
Received: by 10.224.45.146 with HTTP; Tue, 16 Aug 2011 15:20:48 -0700 (PDT)
In-Reply-To: <2C2F1EBA8050E74EA81502D5740B4BD6A932A5AFE5@SJEXCHCCR02.corp.ad.broadcom.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com> <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <2C2F1EBA8050E74EA81502D5740B4BD6A932A5AFE5@SJEXCHCCR02.corp.ad.broadcom.com>
Date: Tue, 16 Aug 2011 18:20:48 -0400
Message-ID: <CAGEmCZzaGxg9CVfddb6oZZXgqdThZ4EsBEMg0s7jMpCvFQCOSw@mail.gmail.com>
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
From: Pablo Frank <pabloisnot@gmail.com>
To: Shahram Davari <davari@broadcom.com>
Content-Type: multipart/alternative; boundary=20cf300faf91a92e0904aaa6ca8c
X-Mailman-Approved-At: Wed, 17 Aug 2011 10:38:05 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2011 22:20:01 -0000

--20cf300faf91a92e0904aaa6ca8c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

My mistake.  Flow-labels are used end-to-end in a multi-segment pseudowire.
 I suppose the flow label can easily be ignored when it crosses the MPLS-TP
segments but that does create the conflict that Sasha is pointing out.

Pablo

On Tue, Aug 16, 2011 at 5:24 PM, Shahram Davari <davari@broadcom.com> wrote=
:

> Pablo,****
>
> ** **
>
> This is not acceptable. Are you suggesting an LSR to pop a label that is
> not to of the stack? I can assure you 99.99% of HW out there can=92t do t=
his.
> ****
>
> ** **
>
> Thx****
>
> SD****
>
> ** **
>
> *From:* mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] *On Behalf O=
f
> *Pablo Frank
> *Sent:* Tuesday, August 16, 2011 2:18 PM
> *To:* Alexander Vainshtein
> *Cc:* mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit; Mishae=
l
> Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> *Subject:* Re: [mpls] [PWE3] IETF Last Call comment on
> draft-ietf-pwe3-gal-in-pw****
>
> ** **
>
> I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS doma=
in
> in the middle segment, you're no longer in an MPLS-TP environment and so =
the
> GAL is not required to be BOS.  During that middle segment, the PW flow
> label would be placed below the GAL and above the GACh.  It gets removed
> when it hits the S-PE that switches you back into the MPLS-TP environment=
.
>  In other words, whether you're in an MPLS-TP environment is determined
> segment by segment in a MS-PW.****
>
> ** **
>
> Pablo****
>
> On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein <
> Alexander.Vainshtein@ecitele.com> wrote:****
>
> Hi all,****
>
> After having sent out my comments I've noticed that the specific example =
to
> illustrate the need to combine GAL and "flow label" was inaccurate.****
>
>  ****
>
> A more relevant example would look like following (I do not include a
> diagram, but it can be easily provided if necessary)****
>
>    1. A MS-PW: ****
>
>
>    - Starts at an S-PE that resides at the edge of an MPLS-TP domain (no
>       ECMP) ****
>       - Crosses this domain and enters an IP/MPLS domain with ECMP enable=
d
>       using a T-PE that resides at the age of these two domains ****
>       - Leaves this domain and enters a 2nd MPLS-TP domain (using the 2nd
>       T-PE) ****
>       - Terminates on another S-PE at the edge of the 2nd MPLS-TP domain*=
*
>       **
>
>
>    1. The operator intends to improve traffic distribution in the IP/MPLS
>    domain, hence he enables insertion and discard of "flow labels" at the=
 two
>    S-PEs. Note that: ****
>
>
>    - This does not violate the MPLS-TP restriction on ECMP: ECMP does not
>       happen in he MPLS-TP domains ****
>       - T-PEs do not even have to be aware of flow labels****
>
>
>    1. The operator also intends to operate some end-to-end OAM for this
>    MS-PW using "GAL-in-PW". This results in a conflict since both GAL and=
 "flow
>    label" are defined (in the corresponding drafts) as bottom of stack.**=
*
>    *
>
>  ****
>
> IMHO this describes a realistic scenario where the two drafts are in
> controversy.****
>
>  ****
>
> Regards,****
>
>      Sasha****
> ------------------------------
>
> *From:* mpls-bounces@ietf.org [mpls-bounces@ietf.org] On Behalf Of
> Alexander Vainshtein [Alexander.Vainshtein@ecitele.com]
> *Sent:* Tuesday, August 16, 2011 4:26 PM
> *To:* ietf@ietf.org
> *Cc:* mpls@ietf.org; Vladimir Kleiner; Idan Kaspit; Mishael Wexler; pwe3;
> Oren Gal; John Shirron; Rotem Cohen
> *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw****
>
> Hi all,****
>
>  ****
>
> I would like to raise the following issue with regard to
> draft-ietf-pwe3-gal-in-pw<http://datatracker.ietf.org/doc/draft-ietf-pwe3=
-mpls-tp-gal-in-pw/?include_text=3D1>:
> controversy vs. draft-ietf-pwe3-fat-pw<http://datatracker.ietf.org/doc/dr=
aft-ietf-pwe3-fat-pw/?include_text=3D1>with regard to bottom-of-stack posit=
ion.
> ****
>
>  ****
>
> As stated in the Introduction, this draft removes the restriction imposed
> by RFC 5586 on usage of Generic Associated Channel Label (GAL) in PWs. Th=
e
> corresponding text Section 4.2 of RFC 5586 states:****
>
> In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
> Concatenated Segments of LSPs, and with Sections, and MUST NOT be used wi=
th
> PWs.  It MUST always be at the bottom of the label stack    (i.e., S bit =
set
> to 1).****
>
>  ****
>
> draft-ietf-pwe3-gal-in-pw proposed to replace the original text in RFC 55=
86
> with the following****
>
>  ****
>
> In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
> Concatenated Segments of LSPs, and with Sections, and MAY be used with PW=
s.
> It MUST always be at the bottom of the label stack (i.e., S bit set to 1)=
.
> ****
>
>  ****
>
> I.e.,  while removing this restriction of 5586, it does not modify its
> requirement for the GAL being always at the bottom of the label stack. **=
*
> *
>
>  ****
>
> At the same draft-ietf-pwe3-fat-pw (currently also in the IESG review)
> reserves the bottom of the PW stack for the PW flow labels, e.g., in Sect=
ion
> 1.1:****
>
>  ****
>
> This document describes a method of adding an additional label stack entr=
y
> (LSE) at the bottom of stack in order to facilitate the load balancing of
> the flows within a PW over the available ECMPs.  ****
>
>  ****
>
> One could argue that draft-ietf-pwe3-gal-in-pw only applies to MPLS-TP
> pseudowires, and that MPLS-TP does not use ECMP. IMHO and FWIW, ****
>
> such an argument, were it presented, would be highly problematic, because=
:
> ****
>
>  ****
>
> 1.       RFC 5960 (which defines the MPLS-TP data plane) did not define
> any differences between the PW data plane in IP/MPLS and MPLS-TP. ****
>
> 2.       One of the most popular scenarios for using multi-segment
> pseudowires is the case when an edge-to-edge service emulation crosses
> multiple IP/MPLS and MPLS-TP domains. In these scenarios, the flow label =
of
> draft-ietf-pwe3-fat-pw (inserted by a flow-aware T-PE at the edge of an
> IP/MPLS domain) would potentially compete with GAL (inserted by a T-PE at
> the edge of an MPLS-TP domain, e.g., for relying a PW status message that=
 it
> has received over a Targeted LDP session from the IP/MPLS domain to a sta=
tic
> PW status message to cross the MPLS-TP domain) for the bottom-of-stack
> position. ****
>
>  ****
>
> The issue I am raising Is not new. It has been actively discussed on the
> PWE3 mailing list with regard to adoption of draft-nadeau-pwe3-vccv-2 as =
a
> WG document, with arguments  for both the flow label and GAL taking the
> bottom-of-the-stack position. But, to the best of my understanding,
> consensus on this issue has not been reached.****
>
>  ****
>
> Hopefully this comment will be useful.****
>
>  ****
>
> Regards,****
>
>      Sasha****
>
>  ****
>
> This e-mail message is intended for the recipient only and contains
> information which is CONFIDENTIAL and which may be proprietary to ECI
> Telecom. If you have received this transmission in error, please inform u=
s
> by e-mail, phone or fax, and then delete the original and all copies
> thereof. ****
>
> This e-mail message is intended for the recipient only and contains
> information which is CONFIDENTIAL and which may be proprietary to ECI
> Telecom. If you have received this transmission in error, please inform u=
s
> by e-mail, phone or fax, and then delete the original and all copies
> thereof. ****
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3****
>
> ** **
>

--20cf300faf91a92e0904aaa6ca8c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>My mistake. =A0Flow-labels are used end-to-end in a multi-segment pseu=
dowire. =A0I suppose the flow label can easily be ignored when it crosses t=
he MPLS-TP segments but that does create the conflict that Sasha is pointin=
g out.</div>
<div><br></div><div>Pablo</div><div><div><br><div class=3D"gmail_quote">On =
Tue, Aug 16, 2011 at 5:24 PM, Shahram Davari <span dir=3D"ltr">&lt;<a href=
=3D"mailto:davari@broadcom.com">davari@broadcom.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex;">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;color:#1F497D">Pablo,<u></u><u></u></sp=
an></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D=
"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">This =
is not acceptable. Are you suggesting an LSR to pop a label that is not to =
of the stack? I can assure you 99.99% of HW out there can=92t do this.<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><u></=
u>=A0<u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0=
pt;color:#1F497D">Thx<u></u><u></u></span></p><p class=3D"MsoNormal"><span =
style=3D"font-size:11.0pt;color:#1F497D">SD<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><u></=
u>=A0<u></u></span></p><div style=3D"border:none;border-top:solid #B5C4DF 1=
.0pt;padding:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span style=3D"fo=
nt-size:10.0pt">From:</span></b><span style=3D"font-size:10.0pt"> <a href=
=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:mpls-bounces@ietf.org" target=3D"_blank">mpls-=
bounces@ietf.org</a>] <b>On Behalf Of </b>Pablo Frank<br>
<b>Sent:</b> Tuesday, August 16, 2011 2:18 PM<br><b>To:</b> Alexander Vains=
htein<br><b>Cc:</b> <a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls=
@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf=
.org</a>; Vladimir Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; Jo=
hn Shirron; Rotem Cohen<br>
<b>Subject:</b> Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3=
-gal-in-pw<u></u><u></u></span></p></div><p class=3D"MsoNormal"><u></u>=A0<=
u></u></p><p class=3D"MsoNormal">I think it&#39;s okay because as the PW cr=
osses the ECMP-enabled IP/MPLS domain in the middle segment, you&#39;re no =
longer in an MPLS-TP environment and so the GAL is not required to be BOS. =
=A0During that middle segment, the PW flow label would be placed below the =
GAL and above the GACh. =A0It gets removed when it hits the S-PE that switc=
hes you back into the MPLS-TP environment. =A0In other words, whether you&#=
39;re in an MPLS-TP environment is determined segment by segment in a MS-PW=
.<u></u><u></u></p>
<div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=3D"Mso=
Normal" style=3D"margin-bottom:12.0pt">Pablo<u></u><u></u></p><div><p class=
=3D"MsoNormal">On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein &lt;<a=
 href=3D"mailto:Alexander.Vainshtein@ecitele.com" target=3D"_blank">Alexand=
er.Vainshtein@ecitele.com</a>&gt; wrote:<u></u><u></u></p>
<div><div><div><p class=3D"MsoNormal"><span style=3D"color:black">Hi all,<u=
></u><u></u></span></p></div><div><p class=3D"MsoNormal"><span style=3D"col=
or:black">After having sent out my comments I&#39;ve noticed that the speci=
fic example to illustrate the need to combine GAL and &quot;flow label&quot=
; was inaccurate.<u></u><u></u></span></p>
</div><div><p class=3D"MsoNormal"><span style=3D"color:black">=A0<u></u><u>=
</u></span></p></div><div><p class=3D"MsoNormal"><span style=3D"color:black=
">A more relevant example would look like following (I do not include a dia=
gram, but it can be easily provided if necessary)<u></u><u></u></span></p>
</div><ol start=3D"1" type=3D"1"><li class=3D"MsoNormal" style=3D"color:bla=
ck">A MS-PW: <u></u><u></u></li></ol><ol start=3D"1" type=3D"1"><ul type=3D=
"circle"><li class=3D"MsoNormal" style=3D"color:black">Starts at an S-PE th=
at resides at the edge of an MPLS-TP domain (no ECMP) <u></u><u></u></li>
<li class=3D"MsoNormal" style=3D"color:black">Crosses this domain and enter=
s an IP/MPLS domain with ECMP enabled using a T-PE that resides at the age =
of these two domains <u></u><u></u></li><li class=3D"MsoNormal" style=3D"co=
lor:black">
Leaves this domain and enters a 2nd MPLS-TP domain (using the 2nd T-PE) <u>=
</u><u></u></li><li class=3D"MsoNormal" style=3D"color:black">Terminates on=
 another S-PE at=A0the edge of the 2nd MPLS-TP domain<u></u><u></u></li></u=
l>
</ol><ol start=3D"2" type=3D"1"><li class=3D"MsoNormal" style=3D"color:blac=
k">The operator intends to improve traffic distribution in the IP/MPLS doma=
in, hence he enables=A0insertion and discard of &quot;flow labels&quot; at =
the two S-PEs. Note that: <u></u><u></u></li>
</ol><ol start=3D"2" type=3D"1"><ul type=3D"circle"><li class=3D"MsoNormal"=
 style=3D"color:black">This does not violate the MPLS-TP restriction on ECM=
P: ECMP does not happen in he MPLS-TP domains <u></u><u></u></li><li class=
=3D"MsoNormal" style=3D"color:black">
T-PEs do not even have to be aware of flow labels<u></u><u></u></li></ul></=
ol><ol start=3D"3" type=3D"1"><li class=3D"MsoNormal" style=3D"color:black"=
>The operator also intends to operate some end-to-end OAM for this MS-PW us=
ing &quot;GAL-in-PW&quot;. This results in a conflict since both GAL and &q=
uot;flow label&quot; are defined (in the=A0corresponding drafts) as bottom =
of stack.<u></u><u></u></li>
</ol><p><span style=3D"color:black">=A0<u></u><u></u></span></p><div><p cla=
ss=3D"MsoNormal"><span style=3D"color:black">IMHO this describes a realisti=
c scenario where the two drafts are in controversy.<u></u><u></u></span></p=
></div>
<div><p class=3D"MsoNormal"><span style=3D"color:black">=A0<u></u><u></u></=
span></p></div><div><p class=3D"MsoNormal"><span style=3D"color:black">Rega=
rds,<u></u><u></u></span></p></div><div><p class=3D"MsoNormal"><span style=
=3D"color:black">=A0=A0=A0=A0 Sasha<u></u><u></u></span></p>
</div><div><div class=3D"MsoNormal" align=3D"center" style=3D"text-align:ce=
nter"><span style=3D"color:black"><hr size=3D"2" width=3D"100%" align=3D"ce=
nter"></span></div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b=
><span style=3D"font-size:10.0pt;color:black">From:</span></b><span style=
=3D"font-size:10.0pt;color:black"> <a href=3D"mailto:mpls-bounces@ietf.org"=
 target=3D"_blank">mpls-bounces@ietf.org</a> [<a href=3D"mailto:mpls-bounce=
s@ietf.org" target=3D"_blank">mpls-bounces@ietf.org</a>] On Behalf Of Alexa=
nder Vainshtein [<a href=3D"mailto:Alexander.Vainshtein@ecitele.com" target=
=3D"_blank">Alexander.Vainshtein@ecitele.com</a>]<br>
<b>Sent:</b> Tuesday, August 16, 2011 4:26 PM<br><b>To:</b> <a href=3D"mail=
to:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a><br><b>Cc:</b> <a href=
=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a>; Vladimir Kle=
iner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohe=
n<br>
<b>Subject:</b> [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw<=
/span><span style=3D"color:black"><u></u><u></u></span></p></div><div><div>=
<p class=3D"MsoNormal"><span style=3D"color:black">Hi all,<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=A0<u></u><u></u></span>=
</p><p class=3D"MsoNormal"><span style=3D"color:black">I would like to rais=
e the following issue with regard to <a href=3D"http://datatracker.ietf.org=
/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?include_text=3D1" target=3D"_blank"=
>draft-ietf-pwe3-gal-in-pw</a>: controversy vs. <a href=3D"http://datatrack=
er.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1" target=3D"_blank"=
>draft-ietf-pwe3-fat-pw</a> with regard to bottom-of-stack position.<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=A0<u></u><u></u></span>=
</p><p class=3D"MsoNormal"><span style=3D"color:black">As stated in the Int=
roduction, this draft removes the restriction imposed by RFC 5586 on usage =
of Generic Associated Channel Label (GAL) in PWs. The corresponding text Se=
ction 4.2 of RFC 5586 states:<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in;line-height:14.4pt"><span =
style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">=
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatena=
ted Segments of LSPs, and with Sections, and MUST NOT be used with PWs.=A0 =
It MUST always be at the bottom of the label stack =A0=A0=A0(i.e., S bit se=
t to 1).</span><span style=3D"color:black"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=A0<u></u><u></u></span>=
</p><p class=3D"MsoNormal"><span style=3D"color:black">draft-ietf-pwe3-gal-=
in-pw proposed to replace the original text in RFC 5586 with the following<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=A0<u></u><u></u></span>=
</p><p class=3D"MsoNormal" style=3D"margin-left:.5in;line-height:14.4pt"><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:bla=
ck">In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Conca=
tenated Segments of LSPs, and with Sections, and MAY be used with PWs. It M=
UST always be at the bottom of the label stack (i.e., S bit set to 1).</spa=
n><span style=3D"color:black"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"color:bl=
ack">=A0<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"line-heigh=
t:14.4pt"><span style=3D"color:black">I.e., =A0while removing this restrict=
ion of 5586, it does not modify its requirement for the GAL being always at=
 the bottom of the label stack. <u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"color:bl=
ack">=A0<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"line-heigh=
t:14.4pt"><span style=3D"color:black">At the same draft-ietf-pwe3-fat-pw (c=
urrently also in the IESG review) reserves the bottom of the PW stack for t=
he PW flow labels, e.g., in Section 1.1:<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"color:bl=
ack">=A0<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"margin-lef=
t:.5in;line-height:14.4pt"><span style=3D"font-size:10.0pt;font-family:&quo=
t;Courier New&quot;;color:black">This document describes a method of adding=
 an additional label stack entry (LSE) at the bottom of stack in order to f=
acilitate the load balancing of the flows within a PW over the available EC=
MPs.=A0 </span><span style=3D"color:black"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"color:bl=
ack">=A0<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"line-heigh=
t:14.4pt"><span style=3D"color:black">One could argue that draft-ietf-pwe3-=
gal-in-pw only applies to MPLS-TP pseudowires, and that MPLS-TP does not us=
e ECMP. IMHO and FWIW, <u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"color:bl=
ack">such an argument, were it presented, would be highly problematic, beca=
use:<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"line-height:14=
.4pt">
<span style=3D"color:black">=A0<u></u><u></u></span></p><p style=3D"line-he=
ight:14.4pt"><span style=3D"color:black">1.</span><span style=3D"font-size:=
7.0pt;color:black">=A0=A0=A0=A0=A0=A0 </span><span style=3D"color:black">RF=
C 5960 (which defines the MPLS-TP data plane) did not define any difference=
s between the PW data plane in IP/MPLS and MPLS-TP. <u></u><u></u></span></=
p>
<p style=3D"line-height:14.4pt"><span style=3D"color:black">2.</span><span =
style=3D"font-size:7.0pt;color:black">=A0=A0=A0=A0=A0=A0 </span><span style=
=3D"color:black">One of the most popular scenarios for using multi-segment =
pseudowires is the case when an edge-to-edge service emulation crosses mult=
iple IP/MPLS and MPLS-TP domains. In these scenarios, the flow label of dra=
ft-ietf-pwe3-fat-pw (inserted by a flow-aware T-PE at the edge of an IP/MPL=
S domain) would potentially compete with GAL (inserted by a T-PE at the edg=
e of an MPLS-TP domain, e.g., for relying a PW status message that it has r=
eceived over a Targeted LDP session from the IP/MPLS domain to a static PW =
status message to cross the MPLS-TP domain) for the bottom-of-stack positio=
n. <u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"color:bl=
ack">=A0<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"line-heigh=
t:14.4pt"><span style=3D"color:black">The issue I am raising Is not new. It=
 has been actively discussed on the PWE3 mailing list with regard to adopti=
on of draft-nadeau-pwe3-vccv-2 as a WG document, with arguments =A0for both=
 the flow label and GAL taking the bottom-of-the-stack position. But, to th=
e best of my understanding, consensus on this issue has not been reached.<u=
></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"color:bl=
ack">=A0<u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"colo=
r:black">Hopefully this comment will be useful.<u></u><u></u></span></p><p =
class=3D"MsoNormal">
<span style=3D"color:black">=A0<u></u><u></u></span></p><p class=3D"MsoNorm=
al"><span style=3D"color:black">Regards,<u></u><u></u></span></p><p class=
=3D"MsoNormal"><span style=3D"color:black">=A0=A0=A0=A0 Sasha<u></u><u></u>=
</span></p><p class=3D"MsoNormal">
<span style=3D"color:black">=A0<u></u><u></u></span></p></div><p><span styl=
e=3D"color:black">This e-mail message is intended for the recipient only an=
d contains information which is CONFIDENTIAL and which may be proprietary t=
o ECI Telecom. If you have received this transmission in error, please info=
rm us by e-mail, phone or fax, and then delete the original and all copies =
thereof. <u></u><u></u></span></p>
</div></div><p>This e-mail message is intended for the recipient only and c=
ontains information which is CONFIDENTIAL and which may be proprietary to E=
CI Telecom. If you have received this transmission in error, please inform =
us by e-mail, phone or fax, and then delete the original and all copies the=
reof. <u></u><u></u></p>
</div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>___________=
____________________________________<br>pwe3 mailing list<br><a href=3D"mai=
lto:pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org</a><br><a href=3D"https:=
//www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">https://www.ietf.or=
g/mailman/listinfo/pwe3</a><u></u><u></u></p>
</div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div></div></block=
quote></div><br></div></div>

--20cf300faf91a92e0904aaa6ca8c--

From Alexander.Vainshtein@ecitele.com  Tue Aug 16 20:48:40 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E54C711E80BF; Tue, 16 Aug 2011 20:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.079
X-Spam-Level: 
X-Spam-Status: No, score=-3.079 tagged_above=-999 required=5 tests=[AWL=1.523,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KY8gU7eWTAM; Tue, 16 Aug 2011 20:48:39 -0700 (PDT)
Received: from mail174.messagelabs.com (mail174.messagelabs.com [85.158.138.51]) by ietfa.amsl.com (Postfix) with SMTP id 66E2411E8083; Tue, 16 Aug 2011 20:48:38 -0700 (PDT)
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-15.tower-174.messagelabs.com!1313552966!21858990!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [147.234.242.235]
Received: (qmail 20992 invoked from network); 17 Aug 2011 03:49:26 -0000
Received: from ilptbmg02-out.ecitele.com (HELO ilptbmg02.ecitele.com) (147.234.242.235) by server-15.tower-174.messagelabs.com with SMTP; 17 Aug 2011 03:49:26 -0000
X-AuditID: 93eaf2e8-b7b3eae00000414f-d7-4e4b337fde9f
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Messaging Gateway) with SMTP id FB.61.16719.F733B4E4; Wed, 17 Aug 2011 06:20:31 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 17 Aug 2011 06:49:25 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Pablo Frank <pabloisnot@gmail.com>
Date: Wed, 17 Aug 2011 06:46:37 +0300
Subject: RE: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Topic: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxcWehnDCf52OvWSKeoT404R1SjwAANmj+G
Message-ID: <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com>
In-Reply-To: <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@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_A3C5DF08D38B6049839A6F553B331C760111EF7BD445ILPTMAIL02e_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA3VTWUwTURT1daZliowZi5UHUVPHKEEti0BSozUkihQXxPVDTXRsn+1IO1M7 A6F+SGNcMVEQBKnGiqIRNVANJrIYlbgEJIEvQxD8kbiUGiNRCNFQZxgFEuP7Ou+ec++5ubmX wHSXohIIlhORh2OctCYarwgNfzf60jfmpXZW4KYP9wO4qe9mvdpUPfRKYzo33IRn4ZZm/0CU pa5uTJWv2u0DqxmO40VGRAYbEqxmOt/DFjFWL21gbWY6jTa4nYwVuRAnmmnG7UacjV4Tbfjn rZZkLGdAnJW3sZzdTOdu32I0mTJXGtPoNUsWpaWvit7hYAUDMroY1mlwIUFg7MggRfY3YY6b T46r3Q1VoNj3sB73gV9HS4GWgFQGrC5/qVHwXNjzrlHC0YSOagWw8nVQrXyqAAz/aJtQaSgz fHB3YALPoZbAhvIaIIswqlcFg7XXgUzg1GI40Pp9QhRL5cDzt24DJcECa250RJUCQsIr4GDY LYdJaissv3Lmj9k7AK92tGEyoZWIkcffJnKB1N5o5z2VjDEqDvYNBlRK2xSsa+vGFKyHn9+P qxW9HvafagSyF0bx8H6tVvGaDTtqBnFFHg+f3e7Fy8Bc/7Sq/qkM/7QMRZIMey9WahS8DN6q HcIUbISXxtvx6fFrIOoOiGedbvGAy566wsgXisnIyorIiZKtvOsBUFbp0yPwtiupHVAEoGPI 3NMb8nRqpkjwutpBPKGi9WTzyo15ulkHeJvXwQiOfZ5CJxLaASQweg65DkgcaWO8R5CH/0tl S/MvxxJmWnlpaTlxX3pq6v8/dBx51hrerKPs0noWIORGnr915hEEDcntsv1sD7Kj4oOsU5yi VYRWbiNGaqNE1pCCm3EJrF3hO4GRGHobeAl0OMdzKCGO7JFFlCxyFHKTdeSDKolEIiEQJw0g lmyRVTHSuU1WCkkmKsmkr8Uim0hnNEkl+ID+U3BBc0n2DUvB86fHHPWWlPM7lx462pg/utZW sDDY3d+VGRu6t2n8RPAw982/PpQ4o64v6/q2yxG6KfvN11yRtGt/pvQHln/c+2KhmPjwcm5G UbfrZPhJ8Muu/OSk9MBIMbdnbeFI1cCY9nNxlr7rTWS4J+V0mTc4lBSfc+Xr/As0LjiYtKWY R2B+AyEke08rBAAA
X-Mailman-Approved-At: Wed, 17 Aug 2011 10:38:05 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 03:48:41 -0000

--_000_A3C5DF08D38B6049839A6F553B331C760111EF7BD445ILPTMAIL02e_
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable

Pablo,
Sorry, but I think you're wrong. Only T-PE can insert the flow label (becaus=
e only T=3DPE can be "flow-aware"). S-PE simply performs swap on PW label.

Regards,
     Sasha

________________________________
From: Pablo Frank [pabloisnot@gmail.com]
Sent: Wednesday, August 17, 2011 12:17 AM
To: Alexander Vainshtein
Cc: ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit; Mishael Wex=
ler; pwe3; Oren Gal; John Shirron; Rotem Cohen
Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw

I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS domain=
 in the middle segment, you're no longer in an MPLS-TP environment and so th=
e GAL is not required to be BOS.  During that middle segment, the PW flow la=
bel would be placed below the GAL and above the GACh.  It gets removed when=
 it hits the S-PE that switches you back into the MPLS-TP environment.  In o=
ther words, whether you're in an MPLS-TP environment is determined segment b=
y segment in a MS-PW.

Pablo

On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein <Alexander.Vainshtein@=
ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Hi all,
After having sent out my comments I've noticed that the specific example to=
 illustrate the need to combine GAL and "flow label" was inaccurate.

A more relevant example would look like following (I do not include a diagra=
m, but it can be easily provided if necessary)

 1.  A MS-PW:
    *   Starts at an S-PE that resides at the edge of an MPLS-TP domain (no=
 ECMP)
    *   Crosses this domain and enters an IP/MPLS domain with ECMP enabled u=
sing a T-PE that resides at the age of these two domains
    *   Leaves this domain and enters a 2nd MPLS-TP domain (using the 2nd T-=
PE)
    *   Terminates on another S-PE at the edge of the 2nd MPLS-TP domain
 2.  The operator intends to improve traffic distribution in the IP/MPLS dom=
ain, hence he enables insertion and discard of "flow labels" at the two S-PE=
s. Note that:
    *   This does not violate the MPLS-TP restriction on ECMP: ECMP does not=
 happen in he MPLS-TP domains
    *   T-PEs do not even have to be aware of flow labels
 3.  The operator also intends to operate some end-to-end OAM for this MS-PW=
 using "GAL-in-PW". This results in a conflict since both GAL and "flow labe=
l" are defined (in the corresponding drafts) as bottom of stack.



IMHO this describes a realistic scenario where the two drafts are in controv=
ersy.

Regards,
     Sasha
________________________________
From: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mpls-bounces@ietf=
.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Alexander Vainshtein [Alexa=
nder.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>]
Sent: Tuesday, August 16, 2011 4:26 PM
To: ietf@ietf.org<mailto:ietf@ietf.org>
Cc: mpls@ietf.org<mailto:mpls@ietf.org>; Vladimir Kleiner; Idan Kaspit; Mish=
ael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
Subject: [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw

Hi all,

I would like to raise the following issue with regard to draft-ietf-pwe3-gal=
-in-pw<http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?in=
clude_text=3D1>: controversy vs. draft-ietf-pwe3-fat-pw<http://datatracker.i=
etf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1> with regard to bottom-=
of-stack position.

As stated in the Introduction, this draft removes the restriction imposed by=
 RFC 5586 on usage of Generic Associated Channel Label (GAL) in PWs. The cor=
responding text Section 4.2 of RFC 5586 states:
In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenat=
ed Segments of LSPs, and with Sections, and MUST NOT be used with PWs.  It M=
UST always be at the bottom of the label stack    (i.e., S bit set to 1).

draft-ietf-pwe3-gal-in-pw proposed to replace the original text in RFC 5586=
 with the following

In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs, Concatenat=
ed Segments of LSPs, and with Sections, and MAY be used with PWs. It MUST al=
ways be at the bottom of the label stack (i.e., S bit set to 1).

I.e.,  while removing this restriction of 5586, it does not modify its requi=
rement for the GAL being always at the bottom of the label stack.

At the same draft-ietf-pwe3-fat-pw (currently also in the IESG review) reser=
ves the bottom of the PW stack for the PW flow labels, e.g., in Section 1.1:

This document describes a method of adding an additional label stack entry (=
LSE) at the bottom of stack in order to facilitate the load balancing of the=
 flows within a PW over the available ECMPs.

One could argue that draft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseud=
owires, and that MPLS-TP does not use ECMP. IMHO and FWIW,
such an argument, were it presented, would be highly problematic, because:


1.       RFC 5960 (which defines the MPLS-TP data plane) did not define any=
 differences between the PW data plane in IP/MPLS and MPLS-TP.

2.       One of the most popular scenarios for using multi-segment pseudowir=
es is the case when an edge-to-edge service emulation crosses multiple IP/MP=
LS and MPLS-TP domains. In these scenarios, the flow label of draft-ietf-pwe=
3-fat-pw (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain) wo=
uld potentially compete with GAL (inserted by a T-PE at the edge of an MPLS-=
TP domain, e.g., for relying a PW status message that it has received over a=
 Targeted LDP session from the IP/MPLS domain to a static PW status message=
 to cross the MPLS-TP domain) for the bottom-of-stack position.

The issue I am raising Is not new. It has been actively discussed on the PWE=
3 mailing list with regard to adoption of draft-nadeau-pwe3-vccv-2 as a WG d=
ocument, with arguments  for both the flow label and GAL taking the bottom-o=
f-the-stack position. But, to the best of my understanding, consensus on thi=
s issue has not been reached.

Hopefully this comment will be useful.

Regards,
     Sasha


This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.

This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.

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




This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


--_000_A3C5DF08D38B6049839A6F553B331C760111EF7BD445ILPTMAIL02e_
Content-Type: text/html; charset="iso-8859-1"
content-transfer-encoding: quoted-printable

<html dir=3D"ltr"><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-1=
">
<meta name=3D"GENERATOR" content=3D"MSHTML 8.00.7600.16821">
<style id=3D"owaTempEditStyle"></style><style title=3D"owaParaStyle"><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi=3D"x">
<div style=3D"FONT-FAMILY: Times New Roman; DIRECTION: ltr; COLOR: #000000;=
 FONT-SIZE: 16px">
<div>Pablo,</div>
<div><font face=3D"times new roman">Sorry, but I think you're wrong. Only T-=
PE can insert the flow label (because only T=3DPE can be &quot;flow-aware&qu=
ot;). S-PE&nbsp;simply<a></a>&nbsp;performs<a></a> swap on PW label.</font><=
/div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">Regards,</font></div>
<div><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</font></d=
iv>
<div dir=3D"ltr"><font color=3D"#000000" size=3D"3" face=3D"Times New Roman"=
></font>&nbsp;</div>
<div style=3D"DIRECTION: ltr" id=3D"divRpF227146">
<hr tabindex=3D"-1">
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><b>From:</b> Pablo Frank=
 [pabloisnot@gmail.com]<br>
<b>Sent:</b> Wednesday, August 17, 2011 12:17 AM<br>
<b>To:</b> Alexander Vainshtein<br>
<b>Cc:</b> ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit; Mish=
ael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen<br>
<b>Subject:</b> Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-=
pw<br>
</font><br>
</div>
<div></div>
<div>I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS do=
main in the middle segment, you're no longer in an MPLS-TP environment and s=
o the GAL is not required to be BOS. &nbsp;During that middle segment, the P=
W flow label would be placed below
 the GAL and above the GACh. &nbsp;It gets removed when it hits the S-PE tha=
t switches you back into the MPLS-TP environment. &nbsp;In other words, whet=
her you're in an MPLS-TP environment is determined segment by segment in a M=
S-PW.
<div><br>
</div>
<div>Pablo<br>
<br>
<div class=3D"gmail_quote">On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainsh=
tein <span dir=3D"ltr">
&lt;<a href=3D"mailto:Alexander.Vainshtein@ecitele.com">Alexander.Vainshtein=
@ecitele.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex;=
 PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div lang=3D"EN-US">
<div style=3D"FONT-FAMILY: Times New Roman; DIRECTION: ltr; COLOR: #000000;=
 FONT-SIZE: 16px">
<div>Hi all,</div>
<div><font face=3D"times new roman">After having sent out my comments I've n=
oticed that the specific example to illustrate the need to combine GAL and &=
quot;flow label&quot; was inaccurate.</font></div>
<div><font face=3D"times new roman"></font>&nbsp;</div>
<div><font face=3D"times new roman">A more relevant example would look like<=
a></a> following (I do not include a diagram, but it can be easily provided=
 if necessary)</font></div>
<ol>
<li><font face=3D"times new roman">A MS-PW:</font>
<ul style=3D"FONT-FAMILY: Times New Roman; FONT-SIZE: 12pt">
<li><font face=3D"times new roman">Starts at an S-PE that resides at the edg=
e of an MPLS-TP domain (no ECMP)</font>
</li><li><font face=3D"times new roman">Crosses this domain and enters an IP=
/MPLS domain with ECMP enabled using a T-PE that resides at the age of these=
 two domains</font>
</li><li><font face=3D"times new roman">Leaves this domain and enters a 2nd=
 MPLS-TP domain (using the 2nd T-PE)</font>
</li><li><font face=3D"times new roman">Terminates on another S-PE at&nbsp;t=
he<a></a> edge of the 2nd MPLS-TP domain</font></li></ul>
</li><li><font face=3D"times new roman">The operator intends to improve traf=
fic distribution in the IP/MPLS domain, hence he enables&nbsp;insertion<a></=
a> and discard of &quot;flow labels&quot; at the two S-PEs. Note that:</font=
>
<ul style=3D"FONT-FAMILY: Times New Roman; FONT-SIZE: 12pt">
<li><font face=3D"times new roman">This does not violate the MPLS-TP restric=
tion on ECMP: ECMP does not happen in he MPLS-TP domains</font>
</li><li><font face=3D"times new roman">T-PEs do not even have to be aware o=
f flow labels</font></li></ul>
</li><li><font face=3D"times new roman">The operator also intends to operate=
 some end-to-end OAM for this MS-PW using &quot;GAL-in-PW&quot;. This result=
s in a conflict since both GAL and &quot;flow label&quot; are defined (in th=
e&nbsp;corresponding<a></a> drafts) as bottom of stack.</font>
</li></ol>
<p><font face=3D"times new roman"></font>&nbsp;</p>
<div dir=3D"ltr"><font color=3D"#000000" size=3D"3" face=3D"Times New Roman"=
>IMHO this describes a realistic scenario where the two drafts are in contro=
versy.</font></div>
<div dir=3D"ltr"><font face=3D"times new roman"></font>&nbsp;</div>
<div dir=3D"ltr"><font face=3D"times new roman">Regards,</font></div>
<div dir=3D"ltr"><font face=3D"times new roman">&nbsp;&nbsp;&nbsp;&nbsp; Sas=
ha</font></div>
<div style=3D"DIRECTION: ltr">
<hr>
<font color=3D"#000000" size=3D"2" face=3D"Tahoma"><b>From:</b> <a href=3D"m=
ailto:mpls-bounces@ietf.org">
mpls-bounces@ietf.org</a> [<a href=3D"mailto:mpls-bounces@ietf.org">mpls-bou=
nces@ietf.org</a>] On Behalf Of Alexander Vainshtein [<a href=3D"mailto:Alex=
ander.Vainshtein@ecitele.com">Alexander.Vainshtein@ecitele.com</a>]<br>
<b>Sent:</b> Tuesday, August 16, 2011 4:26 PM<br>
<b>To:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a>; Vladimir Klei=
ner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen<=
br>
<b>Subject:</b> [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw<b=
r>
</font><br>
</div>
<div></div>
<div>
<div>
<p class=3D"MsoNormal">Hi all,</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I would like to raise the following issue with regard=
 to <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-i=
n-pw/?include_text=3D1" target=3D"_blank">
draft-ietf-pwe3-gal-in-pw</a>: controversy vs. <a href=3D"http://datatracker=
.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=3D1" target=3D"_blank">
draft-ietf-pwe3-fat-pw</a> with regard to bottom-of-stack position.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">As stated in the Introduction, this draft removes the=
 restriction imposed by RFC 5586 on usage of Generic Associated Channel Labe=
l (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586 states:</p>
<p style=3D"LINE-HEIGHT: 14.4pt; MARGIN-LEFT: 36pt" class=3D"MsoNormal"><spa=
n style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">In MPLS-TP, the GAL=
 MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs=
, and with Sections, and MUST NOT be
 used with PWs.&nbsp; It MUST always be at the bottom of the label stack &nb=
sp;&nbsp;&nbsp;(i.e., S bit set to 1).</span></p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">draft-ietf-pwe3-gal-in-pw proposed to replace the ori=
ginal text in RFC 5586 with the following</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt; MARGIN-LEFT: 36pt" class=3D"MsoNormal"><spa=
n style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">In MPLS-TP, the GAL=
 MUST be used with packets on a G-ACh on LSPs, Concatenated Segments of LSPs=
, and with Sections, and MAY be used
 with PWs. It MUST always be at the bottom of the label stack (i.e., S bit s=
et to 1).</span></p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal"><span style=3D"FONT-FAM=
ILY: 'Courier New'; FONT-SIZE: 10pt"></span>&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">I.e., &nbsp;while remov=
ing this restriction of 5586, it does not modify its requirement for the GAL=
 being always at the bottom of the label stack.
</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">At the same draft-ietf-=
pwe3-fat-pw (currently also in the IESG review) reserves the bottom of the P=
W stack for the PW flow labels, e.g., in Section 1.1:</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt; MARGIN-LEFT: 36pt" class=3D"MsoNormal"><spa=
n style=3D"FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt">This document descri=
bes a method of adding an additional label stack entry (LSE) at the bottom o=
f stack in order to facilitate the
 load balancing of the flows within a PW over the available ECMPs.&nbsp; </s=
pan></p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">One could argue that dr=
aft-ietf-pwe3-gal-in-pw only applies to MPLS-TP pseudowires, and that MPLS-T=
P does not use ECMP. IMHO and FWIW,
</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">such an argument, were=
 it presented, would be highly problematic, because:</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt"><span>1.<span style=3D"FONT: 7pt 'Times New=
 Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><span dir=3D"ltr"></span>RFC 5960 (which defines the MPLS-TP d=
ata plane) did not define any differences between the PW data plane in IP/MP=
LS and MPLS-TP.
</p>
<p style=3D"LINE-HEIGHT: 14.4pt"><span>2.<span style=3D"FONT: 7pt 'Times New=
 Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><span dir=3D"ltr"></span>One of the most popular scenarios for=
 using multi-segment pseudowires is the case when an edge-to-edge service em=
ulation crosses multiple IP/MPLS and MPLS-TP domains. In these scenarios, th=
e flow label of draft-ietf-pwe3-fat-pw
 (inserted by a flow-aware T-PE at the edge of an IP/MPLS domain) would pote=
ntially compete with GAL (inserted by a T-PE at the edge of an MPLS-TP domai=
n, e.g., for relying a PW status message that it has received over a Targete=
d LDP session from the IP/MPLS
 domain to a static PW status message to cross the MPLS-TP domain) for the b=
ottom-of-stack position.
</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">The issue I am raising=
 Is not new. It has been actively discussed on the PWE3 mailing list with re=
gard to adoption of draft-nadeau-pwe3-vccv-2 as a WG document, with argument=
s &nbsp;for both the flow label and GAL
 taking the bottom-of-the-stack position. But, to the best of my understandi=
ng, consensus on this issue has not been reached.</p>
<p style=3D"LINE-HEIGHT: 14.4pt" class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Hopefully this comment will be useful.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Regards,</p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp; Sasha</p>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<p>This e-mail message is intended for the recipient only and contains infor=
mation which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If=
 you have received this transmission in error, please inform us by e-mail, p=
hone or fax, and then delete
 the original and all copies thereof. </p>
</div>
</div>
<p>This e-mail message is intended for the recipient only and contains infor=
mation which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If=
 you have received this transmission in error, please inform us by e-mail, p=
hone or fax, and then delete
 the original and all copies thereof. </p>
</div>
<br>
_______________________________________________<br>
pwe3 mailing list<br>
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/pwe3</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<p>
This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.
</p>
</body>
</html>

--_000_A3C5DF08D38B6049839A6F553B331C760111EF7BD445ILPTMAIL02e_--

From sm@resistor.net  Wed Aug 17 22:00:43 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EABE911E808F for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 22:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YbB3yF0cm6U for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 22:00:43 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0AA611E8087 for <ietf@ietf.org>; Wed, 17 Aug 2011 22:00:42 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7I51RGI016540; Wed, 17 Aug 2011 22:01:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1313643693; bh=3aR0gInIz3jahRwkibRv8XIoAGZWD/Jvs6q53gk7jlY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=vGc021SQPOnLWT+o39kvgy8sQBQ+AMrekEwJKnQ+Q/8yzItTQdXa//OjV9x4IPiM/ 6JzbTGM1a2Otd+ev8oHwVQYMFdrOh6rP+ZUZaAB8OMj3hpFt6QIryeyqQ4rG2zb9AG qa2anqv2u+cVI7JIF2JqtChcdvIXrtBNtxbeZeOw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1313643693; bh=3aR0gInIz3jahRwkibRv8XIoAGZWD/Jvs6q53gk7jlY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=1kYO+mbl7bk6NLK+BYTs8xI+OjmOZvelIZw1a4t7bMlB3rF79oDpbuA7DLbkI/NWm VR9/ObTCEhPJsTfvR4iDNj9Sd391C+Tuk7hrKC9GcosKsmKQEBlkjlI9tPM1MxIJ1k ahaCXalv350XBaSWngtU17IipGtDb/YGrruD1QO8=
Message-Id: <6.2.5.6.2.20110817145359.09c4d0f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 17 Aug 2011 21:14:53 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-eggert-successful-bar-bof-05.txt>	(Considerationsfor Having a Successful "Bar BOF" Side Meeting)	to Informational RFC
In-Reply-To: <7801A7BACF0B939148F5BA83@PST.JCK.COM>
References: <20110811222013.3869.45041.idtracker@ietfa.amsl.com> <4827963E94554ED9A4D510E0F3C29EB8@china.huawei.com> <7801A7BACF0B939148F5BA83@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 05:00:44 -0000

At 01:38 17-08-2011, John C Klensin wrote:
>The problem is that RFCs are forever.  RFCs subjected to IETF
>Last Call and published in the IETF Stream --especially ones
>that advise on IETF processes-- are also official, at least in
>the sense of representing some level of community consensus and
>IESG approval.  Publishing this document in the RFC Series runs
>a considerable risk of causing (or at least reinforcing) exactly
>the situation the it argues against -- creating a permanent
>structure of meetings for which "informal" is as much of a
>misnomer as "bar BOF" has become.

What's problematic is saying that the document represents IETF 
Consensus as it is going to misinterpreted and end up encouraging an 
IETF trilogy.  It wouldn't be the authors' fault; it's more about no 
longer having an appropriate path for publishing well-written 
documents such as draft-eggert-successful-bar-bof.

>Let me give two examples of the problem with the understanding
>that there are more:
>
>         * If we have an official-looking, cast-in-RFC-stone,
>         discussion of what "success" means for an informal
>         meeting, it means that the IETF has established success
>         criteria for a meeting type that we simultaneously claim
>         is not part of the WG-formation or consensus processes.
>         One really can't have it both ways and, in that sense,
>         the document reinforces the "first you need a mailing
>         list, then a Bar-BOF (sic) or two, then a "real" BOF (or
>         two), ..." trend.

This is where the FYI would have been useful.  The document discusses 
about an IETF matter, Bar BoFs without drinks [sic].  Publishing it 
in another stream would be a "political" decision.  Explaining how to 
hold informal meetings formalizes such events.  With the "Note Well" 
(Section 6), the meeting is far from an informal one.

I suggest removing Section 6 as that topic is BCP material.

>(2) Just say "no".  Once upon a time, we had a relatively strict
>rule against any IETF-related open (or semi-open, or publicly
>announced)  meetings in the IETF venue unless those meetings
>were either on the agenda or a formal IETF group.  That was in
>the time when Bar-BoFs (and Bar-Design-Teams, and
>Bar-other-things) were held in Bars, with Bar-sized groups, and
>those were not considered meetings of any type.   We could do
>that again -- forcing pre-charter meetings into other venues
>would at least reinforce the message that they weren't WG
>meetings of unchartered WGs.

Yes.

>(4) Make it clear that any claims of consensus arising from an
>informal meeting would not only be ignored, but would cause BOF
>or WG proposals from the leadership of that information meeting
>to be discarded on the grounds that the people were clueless and
>incapable of working within the IETF.   Taking these "unofficial
>BOF" discussions seriously merely reinforces their misuse.

Yes.

At 15:40 15-08-2011, Spencer Dawkins wrote:
>Section 3 contains a sad tail of woe about an area director being 
>trapped in a hotel for a few days during IETF 77, but I'm thinking 
>area directors are going to be trapped in hotels for a few days 
>during IETF weeks, whether there are side meetings scheduled during 
>meals or not.

Area Directors could find some peace by pushing these meetings 
outside confined IETF space.

>you might say that, so everyone has realistic expectations; (2) "if 
>you schedule a side meeting during a meal break, everyone there will 
>be missing a meal unless you go to a restaurant like we told you", 
>and (3) "if you schedule a side meeting that looks like a BOF during 
>a meal break, you won't fit into most restaurants, so have a small 
>side meeting and go to a restaurant like we told you" :-)

Yes.

Fred Baker once raised a concern about "a lack of regard for people's 
health and time".  He suggested having a web page entitled "Poorly 
Planned Meetings" for them.  Dave Crocker  pointed out that even with 
the excellent title suggested, the web page will move these 
activities down the slippery slope of formality.

Melinda Shore commented on an extreme example, the clouds thing, 
where they wanted a working group before they even had anything to 
work on.  Jelte Jansen mentioned that if you make it more official, 
you'll only extend the process, which will result in another level of 
meetings, and even fuller schedules.  Paul Hoffman mentioned that 
"the number of scheduled-but-ad-hoc BoFs that had fleshed-out ideas 
but no drafts was distressing".  Peter Saint-Andre pointed out that 
"the number of WG sessions (which are ostensibly scheduled for the 
purpose of "working") in which folks have not read the drafts or
otherwise prepared themselves to actively contribute is also 
distressingly high".

Yoav Nir mentioned "formalizing that a bunch of people throwing ideas 
around (the "true" bar BoF) is not a good thing".  Joel Halpern 
mentioned a suggestion that was made to him: part of the problem is 
that some folks can not figure out how to socialize their ideas.

Regards,
-sm 


From Rolf.Winter@neclab.eu  Wed Aug 17 23:57:37 2011
Return-Path: <Rolf.Winter@neclab.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D04C921F8570; Wed, 17 Aug 2011 23:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.428
X-Spam-Level: 
X-Spam-Status: No, score=-102.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCQ0nNkN2anr; Wed, 17 Aug 2011 23:57:37 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id C44D621F8565; Wed, 17 Aug 2011 23:57:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 34DDF2800032C; Thu, 18 Aug 2011 08:58:29 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office.hd)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGQ0oifzVq5K; Thu, 18 Aug 2011 08:58:29 +0200 (CEST)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 17791280001AA; Thu, 18 Aug 2011 08:58:14 +0200 (CEST)
Received: from Polydeuces.office.hd ([169.254.3.194]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Thu, 18 Aug 2011 08:58:14 +0200
From: Rolf Winter <Rolf.Winter@neclab.eu>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLS	On-demand	Connectivity Verification and Route Tracing) to	Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLS	On-demand	Connectivity Verification and Route Tracing) to	Proposed Standard
Thread-Index: AQHMWC0Ywr0I1Kz6gkW/M9/KtmFRppUiNvaQ
Date: Thu, 18 Aug 2011 06:58:13 +0000
Message-ID: <791AD3077F94194BB2BDD13565B6295D1D05F07B@Polydeuces.office.hd>
References: <20110811134542.25435.61281.idtracker@ietfa.amsl.com>
In-Reply-To: <20110811134542.25435.61281.idtracker@ietfa.amsl.com>
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: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 06:57:37 -0000

Hi,

I have made this comment before, I just want to make sure it is not lost. T=
his draft is proposing a way to specify the length of sub-TLVs that is inco=
nsistent with RFC 4379. I believe it would be better to align this with 437=
9 as the draft is updating it and I see no technical reason why this should=
 be done differently from 4379.=20

Best,

Rolf

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


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: Donnerstag, 11. August 2011 15:46
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt>
> (MPLS On-demand Connectivity Verification and Route Tracing) to
> Proposed Standard
>=20
>=20
> The IESG has received a request from the Multiprotocol Label Switching
> WG
> (mpls) to consider the following document:
> - 'MPLS On-demand Connectivity Verification and Route Tracing'
>   <draft-ietf-mpls-tp-on-demand-cv-06.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-08-25. Exceptionally, comments may
> be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>    Label Switched Path Ping (LSP-Ping) is an existing and widely
>    deployed Operations, Administration and Maintenance (OAM) mechanism
>    for Multi-Protocol Label Switching (MPLS) Label Switched Paths
>    (LSPs).  This document describes extensions to LSP-Ping so that LSP-
>    Ping can be used for On-demand Connectivity Verification of MPLS
>    Transport Profile (MPLS-TP) LSPs and Pseudowires.  This document
> also
>    clarifies procedures to be used for processing the related OAM
>    packets.  Further, it describes procedures for using LSP-Ping to
>    perform Connectivity Verification and Route Tracing functions in
>    MPLS-TP networks.  Finally this document updates RFC 4379 by adding
> a
>    new address type and requesting an IANA registry.
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From mrex@sap.com  Thu Aug 18 07:48:19 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F0ED21F8AE6 for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 07:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.014
X-Spam-Level: 
X-Spam-Status: No, score=-10.014 tagged_above=-999 required=5 tests=[AWL=0.235, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1Sx2xGwKcio for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 07:48:18 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0EAD921F8B22 for <ietf@ietf.org>; Thu, 18 Aug 2011 07:48:15 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p7IEn12K005579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Aug 2011 16:49:01 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201108181449.p7IEn01V017849@fs4113.wdf.sap.corp>
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message
To: sm+ietf@elandsys.com (S Moonesamy)
Date: Thu, 18 Aug 2011 16:49:00 +0200 (MEST)
In-Reply-To: <6.2.5.6.2.20110818002509.09c79708@resistor.net> from "S Moonesamy" at Aug 18, 11 02:27:38 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 14:48:19 -0000

S Moonesamy wrote:
> 
> Martin Rex wrote:
> >
> > I believe it would be sensible to describe the desired authentication model
> > for MUA->MTA in more detail, beyond the mere reference of [SMTP-AUTH]
> > in section 4.3 of the current document:
> 
> The intent is to publish the document as a Full Standard.  As much as 
> it may be sensible to describe the desired authentication model, it 
> had to be shown that changes would contribute in a substantial and
> substantive way to the quality and comprehensibility of the
> specification as that was the guideline given to working group
> participants.  If you would like to recommend additional text,
> I suggest sending a message to the YAM mailing list.

It seems that I've been confused by the seperation of authentications
client->server and server->client into distinct protocol extensions,
i.e. SMTP-AUTH (rfc4954) for client->server, and the optional SMTP
service extension SMTP-TLS (STARTTLS, rfc3207) for server->client. 

The "mess" I was refering to is about the (factual lack of) server
endpoint identification in SMTP-TLS for the server->client authentication.

I'm sorry.

-Martin


From evnikita2@gmail.com  Thu Aug 18 08:13:15 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D54AA21F8B04 for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 08:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.461
X-Spam-Level: 
X-Spam-Status: No, score=-3.461 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99UkE3+2Ujbz for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 08:13:15 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id C34AF21F8B03 for <ietf@ietf.org>; Thu, 18 Aug 2011 08:13:12 -0700 (PDT)
Received: by fxe6 with SMTP id 6so1491474fxe.31 for <ietf@ietf.org>; Thu, 18 Aug 2011 08:14:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VPCku/HdRayhAgg1r4vlrabNhE4qSHlLSvsC0Pd5CHI=; b=HDWBG0GzhioL0dVHTu5j6mbhIenfT86KdNft/Z4lu77GdI+nibULI8WQMs+GARXRvX VBv9+ZAWa77r4IdV/p2sIbYsz17Wm+ZYjfYRd4jP/0+fLlSwgn6Hu3iWsmR4ERQMy4rW zNZVLM3UffkRMr1b1Oup7n3IV62tlM9XZB4/w=
Received: by 10.223.76.202 with SMTP id d10mr1243037fak.106.1313680446393; Thu, 18 Aug 2011 08:14:06 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id w16sm1798462fah.44.2011.08.18.08.14.01 (version=SSLv3 cipher=OTHER); Thu, 18 Aug 2011 08:14:02 -0700 (PDT)
Message-ID: <4E4D2C5E.3000205@gmail.com>
Date: Thu, 18 Aug 2011 18:14:38 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [yam] Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E4BEA77.4070606@gmail.com> <6.2.5.6.2.20110817232216.0b6efc50@resistor.net>
In-Reply-To: <6.2.5.6.2.20110817232216.0b6efc50@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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 15:13:15 -0000

18.08.2011 10:06, S Moonesamy wrote:
> Hi Mykyta,
> At 09:21 17-08-2011, Mykyta Yevstifeyev wrote:
>> IANA commented that it should be clear that "the registry" refers to 
>> SMTP Service
>> Extensions (http://www.iana.org/assignments/mail-parameters); but the 
>> registry there
>
> From the write-up:
>
> The entry in the SMTP Service Extensions registry for RFC 4409 should 
> be updated to reference this document. The reference for Submit (RFC 
> 2476) should be updated to point to this document. The registry should 
> be updated to reflect the changed and new entries in Section 7.
>
> "the registry" in the above should be read as "the SMTP Service 
> Extensions registry".
>
>> seems to have other format compared to Table 1:
>>
>>>     
>>> +------------------+------------------+-----------+-----------------+
>>>     | Keyword          | Name             | Submissio | 
>>> Reference       |
>>>     |                  |                  | n         
>>> |                 |
>>
>> please compare with
>>
>>> Keywords             Description                         
>>> Reference    Note
>>
>> So how is this table going to be incorporated in the aforementioned 
>> registry?
>
> The following extract is from Section 7.1 of RFC 2476:
>
>    RFC   Name             Submission  Reference
>    ----  ---------------  ----------  ------------------
>    2197  Pipelining         SHOULD    [PIPELINING]
>    2034  Error Codes        SHOULD    [CODES-EXTENSION]
>    1985  ETRN              MUST NOT   [ETRN]
>
> This is from Section 7.1 of RFC 4409:
>
> Keyword        Name                        Submission  Reference
> ----------     --------------------------  ----------  ----------------
> PIPELINING     Pipelining                    SHOULD    [PIPELINING]
> ENHANCEDSTATUSCODES  Enhanced Status Codes   SHOULD    [CODES-EXTENSION]
> ETRN           Extended Turn                 MUST NOT  [ETRN]
>
> And finally from Section 7.1 of draft-ietf-yam-rfc4409bis-02:
>
>
>    | Keyword          | Name             | Submissio | Reference       |
>    |                  |                  | n         |                 |
>    +------------------+------------------+-----------+-----------------+
>    | PIPELINING       | Pipelining       |   SHOULD  | [PIPELINING]    |
>    | ENHANCEDSTATUSCO | Enhanced Status  |   SHOULD  | [CODES-EXTENSIO |
>    | DES              | Codes            |           | N]              |
>    | ETRN             | Extended Turn    |  MUST NOT | [ETRN]          |
>
> The table has been in two previous RFCs.  It was not a problem then.

Neither RFC 2476 nor RFC 4409 asked IANA to make changes according to 
the contents of these tables; but this draft does.  4409 and its 
predecessor just mentioned which are eligible for use with submission.

Mykyta

> It should not be a problem now.  Section 10 of the draft mentions how 
> the table is going to be incorporated.  The document editors will 
> follow up on this editorial matter.
>
> Regards,
> S. Moonesamy
>


From lmartini@cisco.com  Wed Aug 17 11:57:44 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF9821F8A56; Wed, 17 Aug 2011 11:57:44 -0700 (PDT)
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_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id el+or8lu+69g; Wed, 17 Aug 2011 11:57:43 -0700 (PDT)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by ietfa.amsl.com (Postfix) with ESMTP id 0027D21F87FA; Wed, 17 Aug 2011 11:57:42 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p7HIw78g021987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2011 12:58:11 -0600 (MDT)
Message-ID: <4E4C0F3F.8010700@cisco.com>
Date: Wed, 17 Aug 2011 12:58:07 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 18 Aug 2011 08:30:34 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Pablo Frank <pabloisnot@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 18:57:44 -0000

The solution is quite simple:

"Flow Labels MUST not be used in an MPLS-TP environment."

Luca





On 08/16/11 21:46, Alexander Vainshtein wrote:
> Pablo,
> Sorry, but I think you're wrong. Only T-PE can insert the flow label
> (because only T=PE can be "flow-aware"). S-PE simply performs swap on
> PW label.
>  
> Regards,
>      Sasha
>  
> ------------------------------------------------------------------------
> *From:* Pablo Frank [pabloisnot@gmail.com]
> *Sent:* Wednesday, August 17, 2011 12:17 AM
> *To:* Alexander Vainshtein
> *Cc:* ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit;
> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> *Subject:* Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
>
> I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS
> domain in the middle segment, you're no longer in an MPLS-TP
> environment and so the GAL is not required to be BOS.  During that
> middle segment, the PW flow label would be placed below the GAL and
> above the GACh.  It gets removed when it hits the S-PE that switches
> you back into the MPLS-TP environment.  In other words, whether you're
> in an MPLS-TP environment is determined segment by segment in a MS-PW.
>
> Pablo
>
> On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein
> <Alexander.Vainshtein@ecitele.com
> <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
>
>     Hi all,
>     After having sent out my comments I've noticed that the specific
>     example to illustrate the need to combine GAL and "flow label" was
>     inaccurate.
>      
>     A more relevant example would look like following (I do not
>     include a diagram, but it can be easily provided if necessary)
>
>      1. A MS-PW:
>           * Starts at an S-PE that resides at the edge of an MPLS-TP
>             domain (no ECMP)
>           * Crosses this domain and enters an IP/MPLS domain with ECMP
>             enabled using a T-PE that resides at the age of these two
>             domains
>           * Leaves this domain and enters a 2nd MPLS-TP domain (using
>             the 2nd T-PE)
>           * Terminates on another S-PE at the edge of the 2nd MPLS-TP
>             domain
>      2. The operator intends to improve traffic distribution in the
>         IP/MPLS domain, hence he enables insertion and discard of
>         "flow labels" at the two S-PEs. Note that:
>           * This does not violate the MPLS-TP restriction on ECMP:
>             ECMP does not happen in he MPLS-TP domains
>           * T-PEs do not even have to be aware of flow labels
>      3. The operator also intends to operate some end-to-end OAM for
>         this MS-PW using "GAL-in-PW". This results in a conflict since
>         both GAL and "flow label" are defined (in the corresponding
>         drafts) as bottom of stack.
>
>      
>
>     IMHO this describes a realistic scenario where the two drafts are
>     in controversy.
>      
>     Regards,
>          Sasha
>     ------------------------------------------------------------------------
>     *From:* mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>
>     [mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>] On Behalf
>     Of Alexander Vainshtein [Alexander.Vainshtein@ecitele.com
>     <mailto:Alexander.Vainshtein@ecitele.com>]
>     *Sent:* Tuesday, August 16, 2011 4:26 PM
>     *To:* ietf@ietf.org <mailto:ietf@ietf.org>
>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; Vladimir Kleiner; Idan
>     Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>     *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
>
>     Hi all,
>
>      
>
>     I would like to raise the following issue with regard to
>     draft-ietf-pwe3-gal-in-pw
>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?include_text=1>:
>     controversy vs. draft-ietf-pwe3-fat-pw
>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=1>
>     with regard to bottom-of-stack position.
>
>      
>
>     As stated in the Introduction, this draft removes the restriction
>     imposed by RFC 5586 on usage of Generic Associated Channel Label
>     (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586 states:
>
>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
>     Concatenated Segments of LSPs, and with Sections, and MUST NOT be
>     used with PWs.  It MUST always be at the bottom of the label stack
>        (i.e., S bit set to 1).
>
>      
>
>     draft-ietf-pwe3-gal-in-pw proposed to replace the original text in
>     RFC 5586 with the following
>
>      
>
>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
>     Concatenated Segments of LSPs, and with Sections, and MAY be used
>     with PWs. It MUST always be at the bottom of the label stack
>     (i.e., S bit set to 1).
>
>      
>
>     I.e.,  while removing this restriction of 5586, it does not modify
>     its requirement for the GAL being always at the bottom of the
>     label stack.
>
>      
>
>     At the same draft-ietf-pwe3-fat-pw (currently also in the IESG
>     review) reserves the bottom of the PW stack for the PW flow
>     labels, e.g., in Section 1.1:
>
>      
>
>     This document describes a method of adding an additional label
>     stack entry (LSE) at the bottom of stack in order to facilitate
>     the load balancing of the flows within a PW over the available
>     ECMPs. 
>
>      
>
>     One could argue that draft-ietf-pwe3-gal-in-pw only applies to
>     MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. IMHO and
>     FWIW,
>
>     such an argument, were it presented, would be highly problematic,
>     because:
>
>      
>
>     1.       RFC 5960 (which defines the MPLS-TP data plane) did not
>     define any differences between the PW data plane in IP/MPLS and
>     MPLS-TP.
>
>     2.       One of the most popular scenarios for using multi-segment
>     pseudowires is the case when an edge-to-edge service emulation
>     crosses multiple IP/MPLS and MPLS-TP domains. In these scenarios,
>     the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-aware
>     T-PE at the edge of an IP/MPLS domain) would potentially compete
>     with GAL (inserted by a T-PE at the edge of an MPLS-TP domain,
>     e.g., for relying a PW status message that it has received over a
>     Targeted LDP session from the IP/MPLS domain to a static PW status
>     message to cross the MPLS-TP domain) for the bottom-of-stack
>     position.
>
>      
>
>     The issue I am raising Is not new. It has been actively discussed
>     on the PWE3 mailing list with regard to adoption of
>     draft-nadeau-pwe3-vccv-2 as a WG document, with arguments  for
>     both the flow label and GAL taking the bottom-of-the-stack
>     position. But, to the best of my understanding, consensus on this
>     issue has not been reached.
>
>      
>
>     Hopefully this comment will be useful.
>
>      
>
>     Regards,
>
>          Sasha
>
>      
>
>     This e-mail message is intended for the recipient only and
>     contains information which is CONFIDENTIAL and which may be
>     proprietary to ECI Telecom. If you have received this transmission
>     in error, please inform us by e-mail, phone or fax, and then
>     delete the original and all copies thereof.
>
>     This e-mail message is intended for the recipient only and
>     contains information which is CONFIDENTIAL and which may be
>     proprietary to ECI Telecom. If you have received this transmission
>     in error, please inform us by e-mail, phone or fax, and then
>     delete the original and all copies thereof.
>
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pwe3
>
>
> This e-mail message is intended for the recipient only and contains
> information which is CONFIDENTIAL and which may be proprietary to ECI
> Telecom. If you have received this transmission in error, please
> inform us by e-mail, phone or fax, and then delete the original and
> all copies thereof.
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From zali@cisco.com  Wed Aug 17 12:45:00 2011
Return-Path: <zali@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF9E1F0C35; Wed, 17 Aug 2011 12:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1+62OcmquWRy; Wed, 17 Aug 2011 12:44:58 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 051BB21F8C0E; Wed, 17 Aug 2011 12:44:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=zali@cisco.com; l=37725; q=dns/txt; s=iport; t=1313610350; x=1314819950; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=+Lkhm9MxQQDkyFhHEjxS4Q143qbUXa8EVb3cROe0R6c=; b=FVx5k5Lua+wejbXr4FG5NOJyTLkP0CTpPURcOlxjHnIOvCX5rg3w/QkT UwSHeb5pXlEdfUJwE0BV6hqsVEWV08zAV2bGuGziSpFcsRNkW8BJnu9l7 UfQoC4PUprKMw+TWyPOIUUfE/WuhmzrirqllAT4iAPyJOr/tDqqrhvSxI 0=;
X-Files: draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09.txt : 23746
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtcAAFwZTE6tJV2c/2dsb2JhbAA4Cpkaj1h3gTkHAQEBAQMSAQcCFDcGBQcMBAIBCBEDAQEBCwYXAQYBAUQJCAEBBAESCAEZh1KXbwGfDIMngkJfBIdgkEiLfg
X-IronPort-AV: E=Sophos;i="4.68,240,1312156800";  d="txt'?scan'208";a="14069215"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP; 17 Aug 2011 19:45:49 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p7HJjnJq029563;  Wed, 17 Aug 2011 19:45:49 GMT
Received: from xmb-rcd-103.cisco.com ([72.163.62.145]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 17 Aug 2011 14:45:49 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CC5D16.43A0FB7A"
Subject: RE: Gen-ART LC Review of draft-ietf-mpls-rsvp-te-no-php-oob-mapping-08
Date: Wed, 17 Aug 2011 14:45:47 -0500
Message-ID: <7CC717E2F49DAA4A827DA3FEA237111B05AEA2CC@XMB-RCD-103.cisco.com>
In-Reply-To: <37428C36-C58A-4848-80E1-8B2FA892FA9B@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART LC Review of draft-ietf-mpls-rsvp-te-no-php-oob-mapping-08
Thread-Index: AcxZNtcgrP2hvy8KTtCSepjHDf/SFQDxrDnQ
References: <37428C36-C58A-4848-80E1-8B2FA892FA9B@nostrum.com>
From: "Zafar Ali (zali)" <zali@cisco.com>
To: "Ben Campbell" <ben@nostrum.com>, <draft-ietf-mpls-rsvp-te-no-php-oob-mapping.all@tools.ietf.org>
X-OriginalArrivalTime: 17 Aug 2011 19:45:49.0701 (UTC) FILETIME=[43EA8B50:01CC5D16]
X-Mailman-Approved-At: Thu, 18 Aug 2011 08:30:34 -0700
Cc: gen-art@ietf.org, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 19:45:00 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CC5D16.43A0FB7A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear Ben-=20

Many thanks to your detailed review. I have addressed all your comments
in the enclosed version. Please see in-line for details.=20

Thanks

Regards ... Zafar=20

> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Friday, August 12, 2011 5:27 PM
> To: draft-ietf-mpls-rsvp-te-no-php-oob-mapping.all@tools.ietf.org
> Cc: The IETF; gen-art@ietf.org Review Team
> Subject: Gen-ART LC Review of draft-ietf-mpls-rsvp-te-no-php-oob-
> mapping-08
>=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-mpls-rsvp-te-no-php-oob-mapping
> Reviewer: Ben Campbell
> Review Date: 2011-08-12
> IETF LC End Date: 2011-08-12
>=20
> Summary: This document is almost ready for publication as a proposed
> standard. There are a few editorial issues and nits that should be
> considered prior to publication.
>=20
>=20
> Major issues:
>=20
> None
>=20
> Minor issues:
>=20
> None
>=20
> Nits/editorial comments:
>=20
> -- Please proofread for missing articles (i.e. a, an, the)
>=20

Opps, I failed my English test again ;-) I did proofread the document
and have tried to fix the articles to best of my ability. Certainly look
forward to help from RFC editor, if I may please.=20

BTW I always struggle which one of the following is (more) correct:

"An RSVP-TE LSP" vs. "A RSVP-TE LSP"

Document uses "an RSVP-TE LSP".

> -- idnits reports some issues, please check.
>=20

I have cleaned up all idnits in the enclosed version, as follows:

idnits 2.12.12=20

tmp/draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
=20
------------------------------------------------------------------------
----

     No issues found here.

  Checking nits according to
http://www.ietf.org/id-info/1id-guidelines.txt:
=20
------------------------------------------------------------------------
----

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/checklist :
=20
------------------------------------------------------------------------
----

     No issues found here.

  Miscellaneous warnings:
=20
------------------------------------------------------------------------
----

     No issues found here.

  Checking references for intended status: Proposed Standard
=20
------------------------------------------------------------------------
----

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  -- Possible downref: Normative reference to a draft: ref.
'ATTRIBUTE-BNF'=20


     Summary: 0 errors (**), 0 warnings (=3D=3D), 1 comment (--).

n.b. We have ignored one comment, as 'ATTRIBUTE-BNF' needs to be
normative reference.=20

> -- section 1:
>=20
> It would be helpful to include an explicit definition of " non-
> Penultimate Hop Popping behavior" somewhere in the introduction.

We have added it in the enclosed version (v9).=20

>=20
> -- section 1, paragraph 2: "P2MP"
>=20
> Please expand on first mention. I see you did in the abstract, but it
> should be redone in the body.
>=20

We have added RSVP-TE point-to-multipoint (P2MP) in the introduction
too.=20

> -- section 2.2, last paragraph: "w.r.t."
>=20
> Please spell out
>=20

Spelled out.=20

> -- section 3: First paragraph: " Addition of "non-PHP behavior" adds a
> variable of attacks on the label assigned by the Egress node. "
>=20
> Is "variable" the correct word?
>=20

It seems to describe the sentence well. We are open to any suggestion.=20

> -- IANA Considerations:
>=20
> Please include the explicit names of the registry to be changed.
>=20

Added Resource Reservation Protocol-Traffic Engineering (RSVP-TE)
Parameters registry=20

> -- 6.1, "[RFC 2119]"
>=20
> The space between RFC and 2119 confused idnits, and may confuse other
> tools.
>=20

Adrian also pointed out this. It is fixed in the enclosed version.=20

> -- 6.1, [RFC5920]
>=20
> This is an informational draft. Does the reference need to be
normative?
>=20

Adrian also pointed out this. It is fixed in the enclosed version.

> -- general:
>=20
> I am unable to read the title without thinking of this:
> http://en.wikipedia.org/wiki/Hop_on_Pop  :-)

LOL :)=20

------_=_NextPart_001_01CC5D16.43A0FB7A
Content-Type: text/plain;
	name="draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09.txt
Content-Disposition: attachment;
	filename="draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09.txt"

ICAgTVBMUyBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBaLiBBbGkgDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgRy4gU3dhbGxvdyANCiAgIEludGVybmV0IERyYWZ0ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBDaXNjbyBTeXN0ZW1zLCBJbmMuIA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFIu
IEFnZ2Fyd2FsICANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgSnVuaXBlciBOZXR3b3JrcyANCiAgIEludGVuZGVkIHN0YXR1czogU3RhbmRh
cmQgVHJhY2sgICAgICAgICAgICAgICAgICAgICAgIEF1Z3VzdCAxNywgMjAxMSANCiAgIEV4cGly
ZXM6IEZlYnJ1YXJ5IDE2LCAyMDEyIA0KICANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICANCiAgICAgICBOb24gUGVudWx0aW1hdGUgSG9wIFBvcHBpbmcgQmVoYXZpb3Ig
YW5kIG91dC1vZi1iYW5kIG1hcHBpbmcgZm9yIA0KICAgICAgICAgICAgICAgICAgICAgICAgIFJT
VlAtVEUgTGFiZWwgU3dpdGNoZWQgUGF0aHMgDQogICAgICAgICAgICAgICBkcmFmdC1pZXRmLW1w
bHMtcnN2cC10ZS1uby1waHAtb29iLW1hcHBpbmctMDkudHh0IA0KCg0KCiAgIFN0YXR1cyBvZiB0
aGlzIE1lbW8gDQoKDQogICBUaGlzIEludGVybmV0LURyYWZ0IGlzIHN1Ym1pdHRlZCBpbiBmdWxs
IGNvbmZvcm1hbmNlIHdpdGggdGhlDQogICBwcm92aXNpb25zIG9mIEJDUCA3OCBhbmQgQkNQIDc5
Lg0KDQogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1lbnRzIG9mIHRoZSBJbnRl
cm5ldCBFbmdpbmVlcmluZw0KICAgVGFzayBGb3JjZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIg
Z3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUNCiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVy
bmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtDQogICBEcmFmdHMgaXMg
YXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly4NCg0KICAgSW50
ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBz
aXggbW9udGhzDQogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQg
Ynkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUg
dG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2UNCiAgIG1hdGVyaWFsIG9yIHRvIGNp
dGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiINCg0KICAgVGhpcyBJbnRl
cm5ldC1EcmFmdCB3aWxsIGV4cGlyZSBvbiBGZWJydWFyeSAxNiwgMjAxMi4NCg0KICAgICAgIA0K
ICAgQ29weXJpZ2h0IE5vdGljZSANCiAgICAgICANCgogICBDb3B5cmlnaHQgKGMpIDIwMTEgSUVU
RiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGUNCiAgIGRvY3VtZW50IGF1
dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLg0KDQogICBUaGlzIGRvY3VtZW50IGlzIHN1Ympl
Y3QgdG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsDQogICBQcm92aXNpb25zIFJl
bGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzDQogICAoaHR0cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGlj
ZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2YNCiAgIHB1YmxpY2F0aW9uIG9mIHRo
aXMgZG9jdW1lbnQuICBQbGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50cw0KICAgY2FyZWZ1bGx5
LCBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmljdGlvbnMgd2l0aCByZXNw
ZWN0DQogICB0byB0aGlzIGRvY3VtZW50LiAgQ29kZSBDb21wb25lbnRzIGV4dHJhY3RlZCBmcm9t
IHRoaXMgZG9jdW1lbnQgbXVzdA0KICAgaW5jbHVkZSBTaW1wbGlmaWVkIEJTRCBMaWNlbnNlIHRl
eHQgYXMgZGVzY3JpYmVkIGluIFNlY3Rpb24gNC5lIG9mDQogICB0aGUgVHJ1c3QgTGVnYWwgUHJv
dmlzaW9ucyBhbmQgYXJlIHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMNCiAgIGRlc2NyaWJl
ZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZS4gICAgDQoNCiAgICAgICAgICAgICAgICAg
ICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDIwMTIgICAgICAgICAgICAgICBbUGFnZSAxXSANCiAg
ICAMDQoKCgoKCgogICBJbnRlcm5ldC1EcmFmdCAgICAgZHJhZnQtaWV0Zi1tcGxzLXJzdnAtdGUt
bm8tcGhwLW9vYi1tYXBwaW5nLTA5LnR4dCANCiAgICAgICANCgogICBUaGlzIGRvY3VtZW50IG1h
eSBjb250YWluIG1hdGVyaWFsIGZyb20gSUVURiBEb2N1bWVudHMgb3IgSUVURg0KICAgQ29udHJp
YnV0aW9ucyBwdWJsaXNoZWQgb3IgbWFkZSBwdWJsaWNseSBhdmFpbGFibGUgYmVmb3JlIE5vdmVt
YmVyDQogICAxMCwgMjAwOC4gIFRoZSBwZXJzb24ocykgY29udHJvbGxpbmcgdGhlIGNvcHlyaWdo
dCBpbiBzb21lIG9mIHRoaXMNCiAgIG1hdGVyaWFsIG1heSBub3QgaGF2ZSBncmFudGVkIHRoZSBJ
RVRGIFRydXN0IHRoZSByaWdodCB0byBhbGxvdw0KICAgbW9kaWZpY2F0aW9ucyBvZiBzdWNoIG1h
dGVyaWFsIG91dHNpZGUgdGhlIElFVEYgU3RhbmRhcmRzIFByb2Nlc3MuDQogICBXaXRob3V0IG9i
dGFpbmluZyBhbiBhZGVxdWF0ZSBsaWNlbnNlIGZyb20gdGhlIHBlcnNvbihzKSBjb250cm9sbGlu
Zw0KICAgdGhlIGNvcHlyaWdodCBpbiBzdWNoIG1hdGVyaWFscywgdGhpcyBkb2N1bWVudCBtYXkg
bm90IGJlIG1vZGlmaWVkDQogICBvdXRzaWRlIHRoZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLCBh
bmQgZGVyaXZhdGl2ZSB3b3JrcyBvZiBpdCBtYXkNCiAgIG5vdCBiZSBjcmVhdGVkIG91dHNpZGUg
dGhlIElFVEYgU3RhbmRhcmRzIFByb2Nlc3MsIGV4Y2VwdCB0byBmb3JtYXQNCiAgIGl0IGZvciBw
dWJsaWNhdGlvbiBhcyBhbiBSRkMgb3IgdG8gdHJhbnNsYXRlIGl0IGludG8gbGFuZ3VhZ2VzIG90
aGVyDQogICB0aGFuIEVuZ2xpc2guIA0KCiAgICAgICANCiAgIEFic3RyYWN0IA0KCiAgIFRoZXJl
IGFyZSBtYW55IGRlcGxveW1lbnQgc2NlbmFyaW9zIHdoaWNoIHJlcXVpcmUgRWdyZXNzIExhYmVs
IA0KICAgU3dpdGNoaW5nIFJvdXRlciAoTFNSKSB0byByZWNlaXZlIGJpbmRpbmcgb2YgdGhlIFJl
c291cmNlIA0KICAgUmVzZXJWYXRpb24gUHJvdG9jb2wgVHJhZmZpYyBFbmdpbmVlcmVkIChSU1ZQ
LVRFKSBMYWJlbCBTd2l0Y2hlZCANCiAgIFBhdGggKExTUCkgdG8gYW4gYXBwbGljYXRpb24sIGFu
ZCBwYXlsb2FkIGlkZW50aWZpY2F0aW9uLCB1c2luZyANCiAgIHNvbWUgIm91dC1vZi1iYW5kIiAo
T09CKSBtZWNoYW5pc20uIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyANCiAgIHByb3RvY29sIG1lY2hh
bmlzbXMgdG8gYWRkcmVzcyB0aGlzIHJlcXVpcmVtZW50LiBUaGUgcHJvY2VkdXJlcyANCiAgIGRl
c2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50IGFyZSBlcXVhbGx5IGFwcGxpY2FibGUgZm9yIHBvaW50
LXRvLQ0KICAgcG9pbnQgKFAyUCkgYW5kIHBvaW50LXRvLW11bHRpcG9pbnQgKFAyTVApIExTUHMu
IA0KICAgICAgIA0KICAgQ29udmVudGlvbnMgdXNlZCBpbiB0aGlzIGRvY3VtZW50IA0KCiAgICAg
IFRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAi
U0hBTEwgDQogICAgICBOT1QiLCAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQi
LCAiTUFZIiwgYW5kIA0KICAgICAgIk9QVElPTkFMIiBpbiB0aGlzIGRvY3VtZW50IGFyZSB0byBi
ZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW4gDQogICAgICBSRkMgMjExOSBbUkZDMjExOV0u
IA0KCiAgIFRhYmxlIG9mIENvbnRlbnRzIA0KCiAgICAgICANCiAgICAgIENvcHlyaWdodCBOb3Rp
Y2UgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjEgDQogICAg
ICAxLiBJbnRyb2R1Y3Rpb24gLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4zIA0KICAgICAgMi4gUlNWUC1URSBzaWduYWxpbmcgZXh0ZW5zaW9ucyAuLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uNCANCiAgICAgICAgIDIuMS4gU2lnbmFsaW5nIG5vbi1Q
SFAgYmVoYXZpb3IgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjQgDQogICAgICAgICAyLjIu
IFNpZ25hbGluZyBPT0IgTWFwcGluZyBJbmRpY2F0aW9uIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi41
IA0KICAgICAgICAgMi4zLiBSZWxhdGlvbnNoaXAgYmV0d2VlbiBPT0IgYW5kIG5vbi1QSFAgZmxh
Z3MgLi4uLi4uLi4uLi4uNyANCiAgICAgICAgIDIuNC4gRWdyZXNzIFByb2NlZHVyZSBmb3IgbGFi
ZWwgYmluZGluZyAuLi4uLi4uLi4uLi4uLi4uLi4uLjcgDQogICAgICAzLiBTZWN1cml0eSBDb25z
aWRlcmF0aW9ucyAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi44IA0KICAgICAg
NC4gSUFOQSBDb25zaWRlcmF0aW9ucyAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uOCANCiAgICAgICAgIDQuMS4gQXR0cmlidXRlIEZsYWdzIGZvciBMU1BfQVRUUklCVVRF
UyBvYmplY3QgLi4uLi4uLi4uLi4uLjggDQogICAgICAgICA0LjIuIE5ldyBSU1ZQIGVycm9yIHN1
Yi1jb2RlIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi45ICAgICAgICAgICAgICAgICAg
ICAgICAgIA0KICAgICAgICAgICAgICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgICAgICAg
IEV4cGlyZXMgRmVicnVhcnkgMjAxMiAgICAgICAgICAgICAgICAgIFtQYWdlIDJdIA0KICAgICAg
IAwNCgoKCgoKCiAgIEludGVybmV0LURyYWZ0ICAgICBkcmFmdC1pZXRmLW1wbHMtcnN2cC10ZS1u
by1waHAtb29iLW1hcHBpbmctMDkudHh0IA0KDQogICAgICA1LiBBY2tub3dsZWRnbWVudHMgLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi45IA0KICAgICAgNi4gUmVm
ZXJlbmNlcyAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
OSANCiAgICAgICAgIDYuMS4gTm9ybWF0aXZlIFJlZmVyZW5jZXMgLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLjkgDQogICAgICAgICA2LjIuIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMg
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjEwIA0KICAgICAgIA0KICAgMS4gSW50cm9k
dWN0aW9uIA0KCiAgIFdoZW4gUmVzb3VyY2UgUmVzZXJWYXRpb24gUHJvdG9jb2wgVHJhZmZpYyBF
bmdpbmVlcmVkIChSU1ZQLVRFKSANCiAgIGlzIHVzZWQgZm9yIGFwcGxpY2F0aW9ucyBsaWtlIE11
bHRpY2FzdCBWaXJ0dWFsIFByaXZhdGUgTmV0d29yayANCiAgIChNVlBOKSBbTVZQTl0gYW5kIFZp
cnR1YWwgUHJpdmF0ZSBMQU4gU2VydmljZSAoVlBMUykgW1JGQzQ3NjFdLCANCiAgIGFuIEVncmVz
cyBMYWJlbCBTd2l0Y2hpbmcgUm91dGVyIChMU1IpIHJlY2VpdmVzIHRoZSBiaW5kaW5nIG9mIA0K
ICAgdGhlIFJTVlAtVEUgTGFiZWwgU3dpdGNoZWQgUGF0aCAoTFNQKSB0byBhbiBhcHBsaWNhdGlv
biwgYW5kIA0KICAgcGF5bG9hZCBpZGVudGlmaWNhdGlvbiwgdXNpbmcgYW4gIm91dC1vZi1iYW5k
IiAoT09CKSBtZWNoYW5pc20gDQogICAoZS5nLiwgdXNpbmcgQm9yZGVyIEdhdGV3YXkgUHJvdG9j
b2wgKEJHUCkpLiBJbiBzdWNoIGNhc2VzLCB0aGUgDQogICBFZ3Jlc3MgTFNSIGNhbm5vdCBtYWtl
IGNvcnJlY3QgZm9yd2FyZGluZyBkZWNpc2lvbiB1bnRpbCBzdWNoIE9PQiANCiAgIG1hcHBpbmcg
aW5mb3JtYXRpb24gaXMgcmVjZWl2ZWQuIEZ1cnRoZXJtb3JlLCBpbiBvcmRlciB0byBhcHBseSAN
CiAgIHRoZSBiaW5kaW5nIGluZm9ybWF0aW9uLCB0aGUgRWdyZXNzIExTUiBuZWVkcyB0byBpZGVu
dGlmeSB0aGUgDQogICBpbmNvbWluZyBMU1Agb24gd2hpY2ggdHJhZmZpYyBpcyBjb21pbmcuIFRo
ZXJlZm9yZSwgbm9uIA0KICAgUGVudWx0aW1hdGUgSG9wIFBvcHBpbmcgKG5vbi1QSFApIGJlaGF2
aW9yIGlzIHJlcXVpcmVkIHRvIGFwcGx5IA0KICAgT09CIG1hcHBpbmcuIE5vbi1QSFAgYmVoYXZp
b3IgcmVxdWlyZXMgdGhlIGVncmVzcyBMU1JzIHRvIGFzc2lnbg0KICAgYSBub24tTlVMTCBsYWJl
bCBmb3IgdGhlIExTUCBiZWluZyBzaWduYWxlZC4gDQogICAgDQogICBUaGVyZSBhcmUgb3RoZXIg
YXBwbGljYXRpb25zIHRoYXQgcmVxdWlyZSBub24tUEhQIGJlaGF2aW9yLiBXaGVuIA0KICAgUlNW
UC1URSBwb2ludC10by1tdWx0aXBvaW50IChQMk1QKSBMU1BzIGFyZSB1c2VkIHRvIGNhcnJ5IElQ
IA0KICAgbXVsdGljYXN0IHRyYWZmaWMgbm9uLVBIUCBiZWhhdmlvciBlbmFibGVzIGEgbGVhZiBM
U1IgdG8gaWRlbnRpZnkgDQogICB0aGUgUDJNUCBURSBMU1AsIG9uIHdoaWNoIHRyYWZmaWMgaXMg
cmVjZWl2ZWQuIEhlbmNlIHRoZSBlZ3Jlc3MgDQogICBMU1IgY2FuIGRldGVybWluZSB3aGV0aGVy
IHRyYWZmaWMgaXMgcmVjZWl2ZWQgb24gdGhlIGV4cGVjdGVkIFAyTVAgDQogICBMU1AgYW5kIGRp
c2NhcmQgdHJhZmZpYyB0aGF0IGlzIG5vdCByZWNlaXZlZCBvbiB0aGUgZXhwZWN0ZWQgUDJNUCAN
CiAgIExTUC4gTm9uLVBIUCBiZWhhdmlvciBpcyBhbHNvIHJlcXVpcmVkIHRvIGRldGVybWluZSB0
aGUgY29udGV4dCBvZiANCiAgIHVwc3RyZWFtIGFzc2lnbmVkIGxhYmVscyB3aGVuIHRoZSBjb250
ZXh0IGlzIGEgTVBMUyBMU1AuIE5vbi1QSFAgDQogICBiZWhhdmlvciBtYXkgYWxzbyBiZSByZXF1
aXJlZCBmb3IgTVBMUy1UUCBMU1BzIFtSRkM1OTIxXS4gDQogICAgICAgDQogICBUaGlzIGRvY3Vt
ZW50IGRlZmluZXMgdHdvIG5ldyBmbGFncyBpbiB0aGUgQXR0cmlidXRlcyBGbGFncyBUTFYgDQog
ICBvZiB0aGUgTFNQX0FUVFJJQlVURVMgb2JqZWN0IGRlZmluZWQgaW4gW1JGQzU0MjBdOiBvbmUg
ZmxhZyBmb3IgDQogICBjb21tdW5pY2F0aW9uIG9mIG5vbi1QSFAgYmVoYXZpb3IsIGFuZCBvbmUg
ZmxhZyB0byBpbmRpY2F0ZSB0aGF0IA0KICAgdGhlIGJpbmRpbmcgb2YgdGhlIExTUCB0byBhbiBh
cHBsaWNhdGlvbiBhbmQgcGF5bG9hZCBpZGVudGlmaWVyIA0KICAgKHBheWxvYWQtSWQpIG5lZWRz
IHRvIGJlIGxlYXJuZWQgdmlhIGFuIG91dC1vZi1iYW5kIG1hcHBpbmcgDQogICBtZWNoYW5pc20u
IEFzIHRoZXJlIGlzIG9uZS10by1vbmUgY29ycmVzcG9uZGVuY2UgYmV0d2VlbiBiaXRzIGluIA0K
ICAgdGhlIEF0dHJpYnV0ZSBGbGFncyBUTFYgYW5kIHRoZSBSUk8gQXR0cmlidXRlcyBzdWJvYmpl
Y3QsIA0KICAgY29ycmVzcG9uZGluZyBmbGFncyB0byBiZSBjYXJyaWVkIGluIFJSTyBBdHRyaWJ1
dGVzIHN1Ym9iamVjdCBhcmUgDQogICBhbHNvIGRlZmluZWQuICANCiAgICAgICANCiAgIFRoZSBw
cm9jZWR1cmVzIGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50IGFyZSBlcXVhbGx5IGFwcGxpY2Fi
bGUgDQogICBmb3IgUDJQIGFuZCBQMk1QIExTUHMuIFNwZWNpZmljYXRpb24gb2YgdGhlIE9PQiBj
b21tdW5pY2F0aW9uIA0KICAgbWVjaGFuaXNtKHMpIGlzIGJleW9uZCB0aGUgc2NvcGUgb2YgdGhp
cyBkb2N1bWVudC4gIA0KCgoNCiAgICAgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBGZWJydWFy
eSAyMDEyICAgICAgICAgICAgICAgICAgW1BhZ2UgM10gDQogICAgICAgDA0KCgoKCgoKICAgSW50
ZXJuZXQtRHJhZnQgICAgIGRyYWZ0LWlldGYtbXBscy1yc3ZwLXRlLW5vLXBocC1vb2ItbWFwcGlu
Zy0wOS50eHQgDQogICAgICAgDQoKICAgMi4gUlNWUC1URSBzaWduYWxpbmcgZXh0ZW5zaW9ucyAN
CgogICBUaGlzIHNlY3Rpb24gZGVzY3JpYmVzIHRoZSBzaWduYWxpbmcgZXh0ZW5zaW9ucyByZXF1
aXJlZCB0byANCiAgIGFkZHJlc3MgdGhlIGFib3ZlLW1lbnRpb25lZCByZXF1aXJlbWVudHMuICAN
CgogICAyLjEuIFNpZ25hbGluZyBub24tUEhQIGJlaGF2aW9yIA0KCiAgIEluIG9yZGVyIHRvIHJl
cXVlc3Qgbm9uLVBIUCBiZWhhdmlvciBmb3IgYW4gUlNWUC1URSBMU1AsIHRoaXMgDQogICBkb2N1
bWVudCBkZWZpbmVzIGEgbmV3IGZsYWcgaW4gdGhlIEF0dHJpYnV0ZXMgRmxhZ3MgVExWIG9mIHRo
ZSANCiAgIExTUF9BVFRSSUJVVEVTIG9iamVjdCBkZWZpbmVkIGluIFtSRkM1NDIwXTogDQogICAg
ICAgDQoKICAgQml0IE51bWJlciAodG8gYmUgYXNzaWduZWQgYnkgSUFOQSk6IG5vbi1QSFAgYmVo
YXZpb3IgcmVxdWVzdGVkIGZsYWcuICANCgogICBJbiBvcmRlciB0byBpbmRpY2F0ZSB0byB0aGUg
SW5ncmVzcyBMU1IgdGhhdCB0aGUgRWdyZXNzIExTUiANCiAgIHJlY29nbml6ZXMgdGhlICJub24t
UEhQIGJlaGF2aW9yIHJlcXVlc3RlZCBmbGFnIiwgdGhlIGZvbGxvd2luZyANCiAgIG5ldyBiaXQg
aXMgZGVmaW5lZCBpbiB0aGUgRmxhZ3MgZmllbGQgb2YgdGhlIFJlY29yZCBSb3V0ZSBvYmplY3Qg
DQogICAoUlJPKSBBdHRyaWJ1dGVzIHN1Ym9iamVjdDogIA0KICAgICAgIA0KICAgQml0IE51bWJl
ciAoc2FtZSBhcyBiaXQgbnVtYmVyIGFzc2lnbmVkIGZvciBub24tUEhQIGJlaGF2aW9yIA0KICAg
cmVxdWVzdGVkIGZsYWcpOiBOb24tUEhQIGJlaGF2aW9yIGFja25vd2xlZGdlbWVudCBmbGFnLiAN
CgogICBBbiBJbmdyZXNzIExTUiBzZXRzIHRoZSAibm9uLVBIUCBiZWhhdmlvciByZXF1ZXN0ZWQg
ZmxhZyIgdG8gDQogICBzaWduYWwgdGhlIGVncmVzcyBMU1JzIFNIT1VMRCBhc3NpZ24gbm9uLU5V
TEwgbGFiZWwgZm9yIHRoZSBMU1AgDQogICBiZWluZyBzaWduYWxlZC4gIFRoaXMgZmxhZyBNVVNU
IE5PVCBiZSBtb2RpZmllZCBieSBhbnkgb3RoZXIgTFNScyANCiAgIGluIHRoZSBuZXR3b3JrLiBM
U1JzIG90aGVyIHRoYW4gdGhlIEVncmVzcyBMU1JzIFNIT1VMRCBpZ25vcmUgDQogICB0aGlzIGZs
YWcuICANCiAgICAgICANCiAgIElmIGFuIGVncmVzcyBMU1IgcmVjZWl2aW5nIHRoZSBQYXRoIG1l
c3NhZ2UsIHN1cHBvcnRzIHRoZSANCiAgIExTUF9BVFRSSUJVVEVTIG9iamVjdCBhbmQgdGhlIEF0
dHJpYnV0ZXMgRmxhZ3MgVExWLCBhbmQgYWxzbyANCiAgIHJlY29nbml6ZXMgdGhlICJub24tUEhQ
IGJlaGF2aW9yIHJlcXVlc3RlZCBmbGFnIiwgaXQgTVVTVCANCiAgIGFsbG9jYXRlIGEgbm9uLU5V
TEwgbG9jYWwgbGFiZWwuIFRoZSBlZ3Jlc3MgTFNSIE1VU1QgYWxzbyBzZXQgdGhlIA0KICAgIk5v
bi1QSFAgYmVoYXZpb3IgYWNrbm93bGVkZ2VtZW50IGZsYWciIGluIHRoZSBGbGFncyBmaWVsZCBv
ZiB0aGUgDQogICBSUk8gQXR0cmlidXRlIHN1Ym9iamVjdC4gIA0KICAgICAgIA0KICAgSWYgdGhl
IGVncmVzcyBMU1IgIA0KCiAgIC0gc3VwcG9ydHMgdGhlIExTUF9BVFRSSUJVVEVTIG9iamVjdCBi
dXQgZG9lcyBub3QgcmVjb2duaXplIHRoZSANCiAgICAgQXR0cmlidXRlcyBGbGFncyBUTFY7IG9y
ICANCgogICAtIHN1cHBvcnRzIHRoZSBMU1BfQVRUUklCVVRFUyBvYmplY3QgYW5kIHJlY29nbml6
ZSB0aGUgQXR0cmlidXRlcyANCiAgICAgRmxhZ3MgVExWLCBidXQgZG9lcyBub3QgcmVjb2duaXpl
IHRoZSAibm9uLVBIUCBiZWhhdmlvciByZXF1ZXN0ZWQgDQogICAgIGZsYWciOyAgDQoKCg0KICAg
ICAgICAgICAgICAgICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDIwMTIgICAgICAgICAgICAgICAg
ICBbUGFnZSA0XSANCiAgICAgICAMDQoKCgoKCgogICBJbnRlcm5ldC1EcmFmdCAgICAgZHJhZnQt
aWV0Zi1tcGxzLXJzdnAtdGUtbm8tcGhwLW9vYi1tYXBwaW5nLTA5LnR4dCANCiAgICAgICANCgog
ICB0aGVuIGl0IHNpbGVudGx5IGlnbm9yZXMgdGhpcyByZXF1ZXN0IGFjY29yZGluZyB0byB0aGUg
cHJvY2Vzc2luZyANCiAgIHJ1bGVzIG9mIFtSRkM1NDIwXS4gIA0KICAgICAgICAgIA0KCiAgIEFu
IGluZ3Jlc3MgTFNSIHJlcXVlc3Rpbmcgbm9uLVBIUCBiZWhhdmlvciBTSE9VTEQgZXhhbWluZSAi
Tm9uLQ0KICAgUEhQIGJlaGF2aW9yIGFja25vd2xlZGdlbWVudCBmbGFnIiBpbiB0aGUgRmxhZ3Mg
ZmllbGQgb2YgdGhlIFJSTyANCiAgIEF0dHJpYnV0ZSBzdWJvYmplY3QgYW5kIE1BWSBzZW5kIGEg
UGF0aCBUZWFyIHRvIHRoZSBFZ3Jlc3Mgd2hpY2ggDQogICBoYXMgbm90IHNldCB0aGUgIk5vbi1Q
SFAgYmVoYXZpb3IgYWNrbm93bGVkZ2VtZW50IGZsYWciLiBBbiANCiAgIGluZ3Jlc3MgTFNSIHJl
cXVlc3Rpbmcgbm9uLVBIUCBiZWhhdmlvciBNQVkgYWxzbyBleGFtaW5lIHRoZSANCiAgIGxhYmVs
IHZhbHVlIGNvcnJlc3BvbmRpbmcgdG8gdGhlIEVncmVzcyBMU1IocykgaW4gdGhlIFJSTywgYW5k
IA0KICAgTUFZIHNlbmQgYSBQYXRoIFRlYXIgdG8gdGhlIEVncmVzcyB3aGljaCBhc3NpZ25zIGEg
TnVsbCBsYWJlbCANCiAgIHZhbHVlLiAgDQoKICAgV2hlbiBzaWduYWxpbmcgYSBQMk1QIExTUCwg
YSBzb3VyY2Ugbm9kZSBtYXkgd2lzaCB0byBzb2xpY2l0IA0KICAgaW5kaXZpZHVhbCByZXNwb25z
ZSB0byB0aGUgIm5vbi1QSFAgYmVoYXZpb3IgcmVxdWVzdGVkIGZsYWciIGZyb20gDQogICB0aGUg
bGVhZiBub2Rlcy4gR2l2ZW4gdGhlIGNvbnN0cmFpbnRzIG9uIGhvdyB0aGUgTFNQX0FUVFJJQlVU
RVMgbWF5IA0KICAgYmUgY2FycmllZCBpbiBQYXRoIGFuZCBSZXN2IE1lc3NhZ2VzIGFjY29yZGlu
ZyB0byBSRkM1NDIwLCBpbiANCiAgIHRoaXMgc2l0dWF0aW9uIHRoZSBzb3VyY2Ugbm9kZSBNVVNU
IHVzZSBhIHNlcGFyYXRlIFBhdGggbWVzc2FnZSBmb3IgDQogICBlYWNoIGxlYWYgaW4gbmV0d29y
a3Mgd2hlcmUgW0FUVFJJQlVURS1CTkZdIGlzIG5vdCBzdXBwb3J0ZWQuICBJbiANCiAgIG5ldHdv
cmtzIHdpdGggW0FUVFJJQlVURS1CTkZdIGRlcGxveWVkIGVpdGhlciBzZXBhcmF0ZSBQYXRoIA0K
ICAgbWVzc2FnZSBmb3IgZWFjaCBsZWFmIG9yIG11bHRpcGxlIGxlYWZzIHBlciBQYXRoIG1lc3Nh
Z2UgTUFZIGJlIA0KICAgdXNlZCBieSB0aGUgc291cmNlIG5vZGUuICAgICANCg0KICAgMi4yLiBT
aWduYWxpbmcgT09CIE1hcHBpbmcgSW5kaWNhdGlvbiANCgogICBUaGlzIGRvY3VtZW50IGRlZmlu
ZXMgYSBzaW5nbGUgZmxhZyB0byBpbmRpY2F0ZSB0aGF0IHRoZSBub3JtYWwgDQogICBiaW5kaW5n
IG1lY2hhbmlzbSBvZiBhbiBSU1ZQIHNlc3Npb24gaXMgb3ZlcnJpZGRlbi4gIFRoZSBhY3R1YWwg
DQogICBvdXQtb2YtYmFuZCBtYXBwaW5ncyBhcmUgYmV5b25kIHRoZSBzY29wZSBvZiB0aGlzIGRv
Y3VtZW50LiAgVGhlICAgICAgDQogICBmbGFnIGlzIGNhcnJpZWQgaW4gdGhlIEF0dHJpYnV0ZXMg
RmxhZ3MgVExWIG9mIHRoZSBMU1BfQVRUUklCVVRFUyANCiAgIG9iamVjdCBkZWZpbmVkIGluIFtS
RkM1NDIwXSBhbmQgaXMgZGVmaW5lZCBhcyBmb2xsb3dzOiAgDQoNCiAgIEJpdCBOdW1iZXIgKHRv
IGJlIGFzc2lnbmVkIGJ5IElBTkEpOiBPT0IgbWFwcGluZyBpbmRpY2F0aW9uIGZsYWcuICANCgog
ICBJbiBvcmRlciB0byBpbmRpY2F0ZSB0byB0aGUgSW5ncmVzcyBMU1IgdGhhdCB0aGUgRWdyZXNz
IExTUiANCiAgIHJlY29nbml6ZXMgdGhlICJPT0IgbWFwcGluZyBpbmRpY2F0aW9uIGZsYWciLCB0
aGUgZm9sbG93aW5nIG5ldyANCiAgIGJpdCBpcyBkZWZpbmVkIGluIHRoZSBGbGFncyBmaWVsZCBv
ZiB0aGUgUmVjb3JkIFJvdXRlIG9iamVjdCANCiAgIChSUk8pIEF0dHJpYnV0ZXMgc3Vib2JqZWN0
OiAgDQogICAgICAgDQogICBCaXQgTnVtYmVyIChzYW1lIGFzIGJpdCBudW1iZXIgYXNzaWduZWQg
Zm9yIE9PQiBtYXBwaW5nIA0KICAgaW5kaWNhdGlvbiBmbGFnKTogT09CIG1hcHBpbmcgYWNrbm93
bGVkZ2VtZW50IGZsYWcuICANCgoNCiAgICAgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBGZWJy
dWFyeSAyMDEyICAgICAgICAgICAgICAgICAgW1BhZ2UgNV0gDQogICAgICAgDA0KCgoKCgoKICAg
SW50ZXJuZXQtRHJhZnQgICAgIGRyYWZ0LWlldGYtbXBscy1yc3ZwLXRlLW5vLXBocC1vb2ItbWFw
cGluZy0wOS50eHQgDQogICAgICAgDQoKICAgQW4gSW5ncmVzcyBMU1Igc2V0cyB0aGUgT09CIG1h
cHBpbmcgaW5kaWNhdGlvbiBmbGFnIHRvIHNpZ25hbCB0aGUgDQogICBFZ3Jlc3MgTFNSIHRoYXQg
YmluZGluZyBvZiBSU1ZQLVRFIExTUCB0byBhbiBhcHBsaWNhdGlvbiBhbmQgDQogICBwYXlsb2Fk
IGlkZW50aWZpY2F0aW9uIGlzIGJlaW5nIHNpZ25hbGVkIG91dC1vZi1iYW5kLiBUaGlzIGZsYWcg
DQogICBNVVNUIE5PVCBiZSBtb2RpZmllZCBieSBhbnkgb3RoZXIgTFNScyBpbiB0aGUgbmV0d29y
ay4gTFNScw0KICAgb3RoZXIgdGhhbiB0aGUgRWdyZXNzIExTUnMgU0hPVUxEIGlnbm9yZSB0aGlz
IGZsYWcuICANCiANCiAgIFdoZW4gYW4gRWdyZXNzIExTUiB3aGljaCBzdXBwb3J0cyB0aGUgIk9P
QiBtYXBwaW5nIGluZGljYXRpb24gDQogICBmbGFnIiwgcmVjZWl2ZXMgYSBQYXRoIG1lc3NhZ2Ug
d2l0aCB0aGF0IGZsYWcgc2V0LCB0aGUgRWdyZXNzIExTUiANCiAgIE1VU1Qgc2V0IHRoZSAiT09C
IG1hcHBpbmcgYWNrbm93bGVkZ2VtZW50IGZsYWciIGluIHRoZSBGbGFncyANCiAgIGZpZWxkIG9m
IHRoZSBSUk8gQXR0cmlidXRlIHN1Ym9iamVjdC4gVGhlIHJlc3Qgb2YgdGhlIFJTVlAgDQogICBz
aWduYWxpbmcgcHJvY2VlZHMgYXMgbm9ybWFsLiAgSG93ZXZlciwgdGhlIExTUiBNVVNUIGhhdmUg
DQogICByZWNlaXZlZCB0aGUgT09CIG1hcHBpbmcgYmVmb3JlIGFjY2VwdGluZyB0cmFmZmljIG9u
IHRoZSBMU1AuICANCiAgIFRoaXMgaW1wbGllcyB0aGF0IHRoZSBFZ3Jlc3MgTFNSIE1VU1QgTk9U
IHNldHVwIGZvcndhcmRpbmcgc3RhdGUgDQogICBmb3IgdGhlIExTUCBiZWZvcmUgaXQgcmVjZWl2
ZXMgdGhlIE9PQiBtYXBwaW5nLiAgDQogICAgICAgDQogICBOb3RlIHRoYXQgdGhlIHBheWxvYWQg
aW5mb3JtYXRpb24gU0hPVUxEIGJlIHN1cHBsaWVkIGJ5IHRoZSBPT0IgDQogICBtYXBwaW5nLiBJ
ZiB0aGUgZWdyZXNzIExTUiByZWNlaXZlcyB0aGUgcGF5bG9hZCBpbmZvcm1hdGlvbiBmcm9tIA0K
ICAgT09CIG1hcHBpbmcgdGhlbiB0aGUgTFNSIE1VU1QgaWdub3JlIEwzUElEIGluIHRoZSBMYWJl
bCBSZXF1ZXN0IA0KICAgT2JqZWN0IFtSRkMzMjA5XS4gDQogICAgDQogICAgDQogICBJZiB0aGUg
ZWdyZXNzIExTUiAgDQoKICAgLSBzdXBwb3J0cyB0aGUgTFNQX0FUVFJJQlVURVMgb2JqZWN0IGJ1
dCBkb2VzIG5vdCByZWNvZ25pemUgdGhlIA0KICAgICBBdHRyaWJ1dGVzIEZsYWdzIFRMVjsgb3Ig
IA0KCiAgIC0gc3VwcG9ydHMgdGhlIExTUF9BVFRSSUJVVEVTIG9iamVjdCBhbmQgcmVjb2duaXpl
cyB0aGUgDQogICAgIEF0dHJpYnV0ZXMgRmxhZ3MgVExWLCBidXQgZG9lcyBub3QgcmVjb2duaXpl
IHRoZSAiT09CIG1hcHBpbmcgDQogICAgIGluZGljYXRpb24gZmxhZyI7IA0KCiAgIHRoZW4gaXQg
c2lsZW50bHkgaWdub3JlcyB0aGlzIHJlcXVlc3QgYWNjb3JkaW5nIHRvIHRoZSBwcm9jZXNzaW5n
IA0KICAgcnVsZXMgb2YgW1JGQzU0MjBdLiAgDQogICAgICAgDQoKICAgQW4gaW5ncmVzcyBMU1Ig
cmVxdWVzdGluZyBPT0IgbWFwcGluZyBTSE9VTEQgZXhhbWluZSAiT09CIG1hcHBpbmcgDQogICBh
Y2tub3dsZWRnZW1lbnQgZmxhZyIgaW4gdGhlIEZsYWdzIGZpZWxkIG9mIHRoZSBSUk8gQXR0cmli
dXRlIA0KICAgc3Vib2JqZWN0IGFuZCBNQVkgc2VuZCBhIFBhdGggVGVhciB0byB0aGUgRWdyZXNz
IHdoaWNoIGhhcyBub3QgDQogICBzZXQgdGhlICJPT0IgbWFwcGluZyBhY2tub3dsZWRnZW1lbnQg
ZmxhZyIuICANCgogICBXaGVuIHNpZ25hbGluZyBhIFAyTVAgTFNQLCBhIHNvdXJjZSBub2RlIG1h
eSB3aXNoIHRvIHNvbGljaXQgDQogICBpbmRpdmlkdWFsIHJlc3BvbnNlIHRvIHRoZSAiT09CIG1h
cHBpbmcgaW5kaWNhdGlvbiBmbGFnIiBmcm9tIHRoZQ0KICAgdGhlIGxlYWYgbm9kZXMuIEdpdmVu
IHRoZSBjb25zdHJhaW50cyBvbiBob3cgdGhlIExTUF9BVFRSSUJVVEVTIA0KICAgbWF5IGJlIGNh
cnJpZWQgaW4gUGF0aCBhbmQgUmVzdiBNZXNzYWdlcyBhY2NvcmRpbmcgdG8gUkZDNTQyMCwgaW4g
DQogICB0aGlzIHNpdHVhdGlvbiB0aGUgc291cmNlIG5vZGUgTVVTVCB1c2UgYSBzZXBhcmF0ZSBQ
YXRoIG1lc3NhZ2UgZm9yIA0KICAgZWFjaCBsZWFmIGluIG5ldHdvcmtzIHdoZXJlIFtBVFRSSUJV
VEUtQk5GXSBpcyBub3Qgc3VwcG9ydGVkLiAgSW4gDQoNCiAgICAgICAgICAgICAgICAgICAgICAg
RXhwaXJlcyBGZWJydWFyeSAyMDEyICAgICAgICAgICAgICAgICAgW1BhZ2UgNl0gDQogICAgICAg
DA0KCgoKCgoKICAgSW50ZXJuZXQtRHJhZnQgICAgIGRyYWZ0LWlldGYtbXBscy1yc3ZwLXRlLW5v
LXBocC1vb2ItbWFwcGluZy0wOS50eHQgDQogICAgICAgDQoKICAgbmV0d29ya3Mgd2l0aCBbQVRU
UklCVVRFLUJORl0gZGVwbG95ZWQgZWl0aGVyIHNlcGFyYXRlIFBhdGggDQogICBtZXNzYWdlIGZv
ciBlYWNoIGxlYWYgb3IgbXVsdGlwbGUgbGVhZnMgcGVyIFBhdGggbWVzc2FnZSBNQVkgYmUgDQog
ICB1c2VkIGJ5IHRoZSBzb3VyY2Ugbm9kZS4gDQogICAgICAgDQogICBJbiBkZXBsb3lpbmcgYXBw
bGljYXRpb25zIHdoZXJlIEVncmVzcyBMU1IgcmVjZWl2ZXMgdGhlIGJpbmRpbmcgDQogICBvZiB0
aGUgUlNWUC1URSBMU1AgdG8gYW4gYXBwbGljYXRpb24sIGFuZCBwYXlsb2FkIGlkZW50aWZpY2F0
aW9uLCANCiAgIHVzaW5nIE9PQiBtZWNoYW5pc20sIGl0IGlzIGltcG9ydGFudCB0byByZWNvZ25p
emUgdGhhdCB0aGUgT09CIA0KICAgbWFwcGluZyBpcyBzZW50IGFzeW5jaHJvbm91c2x5IHdpdGgg
cmVzcGVjdCB0byB0aGUgc2lnbmFsaW5nIG9mIA0KICAgUlNWUC1URSBMU1AuIEVncmVzcyBMU1Ig
b25seSBpbnN0YWxscyBmb3J3YXJkaW5nIHN0YXRlIGZvciB0aGUgTFNQICANCiAgIGFmdGVyIGl0
IHJlY2VpdmVzIHRoZSBPT0IgbWFwcGluZy4gSW4gZGVwbG95aW5nIGFwcGxpY2F0aW9ucyB1c2lu
ZyANCiAgIE9PQiBtZWNoYW5pc20sIGFuIEluZ3Jlc3MgTFNSIG1heSBuZWVkIHRvIGtub3cgd2hl
biB0aGUgRWdyZXNzIGlzIA0KICAgcHJvcGVybHkgc2V0dXAgZm9yIGZvcndhcmRpbmcgKGkuZS4s
IGhhcyByZWNlaXZlZCB0aGUgT09CIG1hcHBpbmcpLiANCiAgIEhvdyB0aGUgSW5ncmVzcyBMU1Ig
ZGV0ZXJtaW5lcyB0aGF0IHRoZSBMU1IgaXMgcHJvcGVybHkgc2V0dXAgZm9yIA0KICAgZm9yd2Fy
ZGluZyBhdCB0aGUgRWdyZXNzIExTUiBpcyBiZXlvbmQgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1l
bnQuIA0KICAgTm9uZXRoZWxlc3MsIGlmIHRoZSBPT0IgbWFwcGluZyBpcyBub3QgcmVjZWl2ZWQg
YnkgdGhlIEVncmVzcyBMU1IgDQogICB3aXRoaW4gYSByZWFzb25hYmxlIHRpbWUsIHRoZSBwcm9j
ZWR1cmUgZGVmaW5lZCBpbiBzZWN0aW9uIDIuNCB0byANCiAgIHRlYXIgZG93biB0aGUgTFNQIGlz
IGZvbGxvd2VkLiAgIA0KICAgICAgIA0KCiAgIDIuMy4gUmVsYXRpb25zaGlwIGJldHdlZW4gT09C
IGFuZCBub24tUEhQIGZsYWdzIA0KCiAgICJOb24tUEhQIGJlaGF2aW9yIGRlc2lyZWQiIGFuZCAi
T09CIG1hcHBpbmcgaW5kaWNhdGlvbiIgZmxhZ3MgY2FuIA0KICAgYXBwZWFyIGFuZCBiZSBwcm9j
ZXNzZWQgaW5kZXBlbmRlbnRseSBvZiBlYWNoIG90aGVyLiBIb3dldmVyLCBhcyANCiAgIG1lbnRp
b25lZCBlYXJsaWVyLCBpbiB0aGUgY29udGV4dCBvZiB0aGUgYXBwbGljYXRpb25zIGRpc2N1c3Nl
ZCBpbiANCiAgIHRoaXMgZG9jdW1lbnQsIE9PQiBtYXBwaW5nIHJlcXVpcmVzIG5vbi1QSFAgYmVo
YXZpb3IuIEFuIEluZ3Jlc3MgDQogICBMU1IgcmVxdWVzdGluZyB0aGUgT09CIG1hcHBpbmcgTUFZ
IGFsc28gc2V0IHRoZSAibm9uLVBIUCBiZWhhdmlvciANCiAgIHJlcXVlc3RlZCBmbGFnIiBpbiB0
aGUgTFNQX0FUVFJJQlVURVMgb2JqZWN0IGluIHRoZSBQYXRoIG1lc3NhZ2UuICANCgogICAyLjQu
IEVncmVzcyBQcm9jZWR1cmUgZm9yIGxhYmVsIGJpbmRpbmcgDQoKICAgUlNWUC1URSBzaWduYWxp
bmcgY29tcGxldGlvbiBhbmQgdGhlIE9PQiBtYXBwaW5nIGluZm9ybWF0aW9uIA0KICAgcmVjZXB0
aW9uIGhhcHBlbiBhc3luY2hyb25vdXNseSBhdCB0aGUgRWdyZXNzLiBBcyBtZW50aW9uZWQgaW4g
DQogICBTZWN0aW9uIDIuMiwgRWdyZXNzIHdhaXRzIGZvciB0aGUgT09CIG1hcHBpbmcgYmVmb3Jl
IGFjY2VwdGluZyANCiAgIHRyYWZmaWMgb24gdGhlIExTUC4gTm9uZXRoZWxlc3MsIE1QTFMgT0FN
IG1lY2hhbmlzbXMsIGUuZy4sIExTUCANCiAgIFBpbmcgYW5kIFRyYWNlIHJvdXRlIGFzIGRlZmlu
ZWQgaW4gW1JGQzQzNzldLCBbUDJNUC1PQU1dLCBhcmUgDQogICBleHBlY3RlZCB0byB3b3JrIGlu
ZGVwZW5kZW50IG9mIE9PQiBtYXBwaW5nIGxlYXJuaW5nIHByb2Nlc3MuICANCiAgICAgICAgDQog
ICBJbiBvcmRlciB0byBhdm9pZCB1bm5lY2Vzc2FyeSB1c2Ugb2YgdGhlIHJlc291cmNlcyBhbmQg
cG9zc2libGUgDQogICBibGFjay1ob2xpbmcgb2YgdHJhZmZpYywgYW4gRWdyZXNzIExTUiBNQVkg
c2VuZCBhIFBhdGggRXJyb3IgDQogICBtZXNzYWdlIGlmIHRoZSBPT0IgbWFwcGluZyBpbmZvcm1h
dGlvbiBpcyBub3QgcmVjZWl2ZWQgd2l0aGluIGEgDQogICByZWFzb25hYmxlIHRpbWUuIFRoaXMg
UGF0aCBFcnJvciBtZXNzYWdlIFNIT1VMRCBpbmNsdWRlIHRoZSBlcnJvciANCiAgIGNvZGUvc3Vi
LWNvZGUgIk5vdGlmeSBFcnJvci8gbm8gT09CIG1hcHBpbmcgcmVjZWl2ZWQiIGZvciBhbGwgDQog
ICBhZmZlY3RlZCBMU1BzLiBJZiBub3RpZnkgcmVxdWVzdCB3YXMgaW5jbHVkZWQgd2hlbiB0aGUg
TFNQIHdhcyANCiAgIGluaXRpYWxseSBzZXR1cCwgTm90aWZ5IG1lc3NhZ2UgKGFzIGRlZmluZWQg
aW4gW1JGQzM0NzNdKSBNQVkgDQogICBhbHNvIGJlIHVzZWQgZm9yIGRlbGl2ZXJ5IG9mIHRoaXMg
aW5mb3JtYXRpb24gdG8gdGhlIEluZ3Jlc3MgTFNSLiANCiAgIEFuIEVncmVzcyBMU1IgTUFZIGlt
cGxlbWVudCBhIGNsZWFudXAgdGltZXIgZm9yIHRoaXMgcHVycG9zZS4gVGhlIA0KDQogICAgICAg
ICAgICAgICAgICAgICAgIEV4cGlyZXMgRmVicnVhcnkgMjAxMiAgICAgICAgICAgICAgICAgIFtQ
YWdlIDddIA0KICAgICAgIAwNCgoKCgoKCiAgIEludGVybmV0LURyYWZ0ICAgICBkcmFmdC1pZXRm
LW1wbHMtcnN2cC10ZS1uby1waHAtb29iLW1hcHBpbmctMDkudHh0IA0KDQogICB0aW1lLW91dCB2
YWx1ZSBpcyBhIGxvY2FsIGRlY2lzaW9uIGF0IHRoZSBFZ3Jlc3MsIHdpdGggYSANCiAgIFJFQ09N
TUVOREVEIGRlZmF1bHQgdmFsdWUgb2YgNjAgc2Vjb25kcy4gIA0KCiAgIDMuIFNlY3VyaXR5IENv
bnNpZGVyYXRpb25zIA0KCiAgIEFkZGl0aW9uIG9mICJub24tUEhQIGJlaGF2aW9yIiBhZGRzIGEg
dmFyaWFibGUgb2YgYXR0YWNrcyBvbiB0aGUgDQogICBsYWJlbCBhc3NpZ25lZCBieSB0aGUgRWdy
ZXNzIG5vZGUuIEFzIGNoYW5nZSBpbiB0aGUgdmFsdWUgb2YgdGhlIA0KICAgZWdyZXNzIGxhYmVs
IHJlcG9ydGVkIGluIHRoZSBSUk8gY2FuIGNhdXNlIHRoZSBMU1AgdG8gYmUgdG9ybiANCiAgIGRv
d24sIGFkZGl0aW9uYWwgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgZm9yIHByb3RlY3RpbmcgbGFi
ZWwgDQogICBhc3NpZ25lZCBieSB0aGUgRWdyZXNzIG5vZGUgYXJlIHJlcXVpcmVkLiBTZWN1cml0
eSBtZWNoYW5pc21zIGFzIA0KICAgaWRlbnRpZmllZCBpbiBbUkZDNTkyMF0sIFtSRkMyMjA1XSwg
W1JGQzMyMDldLCBbUkZDMzQ3M10sIA0KICAgW1JGQzU0MjBdIGFuZCBbUkZDNDg3NV0gY2FuIGJl
IHVzZWQgZm9yIHRoaXMgcHVycG9zZS4gVGhpcyANCiAgIGRvY3VtZW50IGRvZXMgbm90IGludHJv
ZHVjZSBhbnkgYWRkaXRpb25hbCBzZWN1cml0eSBpc3N1ZXMgYWJvdmUgDQogICB0aG9zZSBpZGVu
dGlmaWVkIGluIFtSRkM1OTIwXSwgW1JGQzIyMDVdLCBbUkZDMzIwOV0sIFtSRkMzNDczXSwgDQog
ICBbUkZDNTQyMF0gYW5kIFtSRkM0ODc1XS4gICAgIA0KICAgIA0KICAgNC4gSUFOQSBDb25zaWRl
cmF0aW9ucyANCgoNCiAgIFRoZSBmb2xsb3dpbmcgY2hhbmdlcyB0byB0aGUgUmVzb3VyY2UgUmVz
ZXJ2YXRpb24gUHJvdG9jb2wtVHJhZmZpYyANCiAgIEVuZ2luZWVyaW5nIChSU1ZQLVRFKSBQYXJh
bWV0ZXJzIHJlZ2lzdHJ5IGFyZSByZXF1aXJlZC4gDQoNCiAgIDQuMS4gQXR0cmlidXRlIEZsYWdz
IGZvciBMU1BfQVRUUklCVVRFUyBvYmplY3QgDQoKICAgVGhlIGZvbGxvd2luZyBuZXcgZmxhZ3Mg
YXJlIGRlZmluZWQgZm9yIHRoZSBBdHRyaWJ1dGVzIEZsYWdzIFRMViANCiAgIGluIHRoZSBMU1Bf
QVRUUklCVVRFUyBvYmplY3QuICBUaGUgbnVtZXJpYyB2YWx1ZXMgYXJlIHRvIGJlIA0KICAgYXNz
aWduZWQgYnkgSUFOQS4gDQogICBvICBOb24tUEhQIGJlaGF2aW9yIGZsYWc6DQogICBUaGlzIGZs
YWdzIGlzIHVzZWQgaW4gdGhlIEF0dHJpYnV0ZXMgRmxhZ3MgVExWIGluIGEgUGF0aCBtZXNzYWdl
LiANCiAgIFRoZSBmbGFncyBoYXZlIGNvcnJlc3BvbmRpbmcgbmV3IGZsYWcgdG8gYmUgdXNlZCBp
biB0aGUgUlJPIA0KICAgQXR0cmlidXRlcyBzdWJvYmplY3QuIEFzIHBlciBbUkZDNTQyMF0sIHRo
ZSBiaXQgbnVtYmVyaW5nIGluIHRoZSANCiAgIEF0dHJpYnV0ZSBGbGFncyBUTFYgYW5kIHRoZSBS
Uk8gQXR0cmlidXRlcyBzdWJvYmplY3QgaXMgDQogICBpZGVudGljYWwuIFRoYXQgaXMsIHRoZSBz
YW1lIGF0dHJpYnV0ZSBpcyBpbmRpY2F0ZWQgYnkgdGhlIHNhbWUNCiAgIGJpdCBpbiBib3RoIHBs
YWNlcy4gVGhpcyBmbGFnIGlzIG5vdCBhbGxvd2VkIGluIHRoZSBBdHRyaWJ1dGVzIA0KICAgRmxh
Z3MgVExWIGluIGEgUmVzdiBtZXNzYWdlLiBTcGVjaWZpY2FsbHksIEF0dHJpYnV0ZXMgb2YgdGhp
cyANCiAgIGZsYWcgYXJlIGFzIGZvbGxvd3M6ICANCgogICAgICAgICAtIEJpdCBOdW1iZXI6IFRv
IGJlIGFzc2lnbmVkIGJ5IElBTkEuIA0KCiAgICAgICAgIC0gQXR0cmlidXRlIGZsYWcgY2Fycmll
ZCBpbiBQYXRoIG1lc3NhZ2U6IFllcyANCgogICAgICAgICAtIEF0dHJpYnV0ZSBmbGFnIGNhcnJp
ZWQgaW4gUmVzdiBtZXNzYWdlOiBObyANCgogICAgICAgICAtIEF0dHJpYnV0ZSBmbGFnIGNhcnJp
ZWQgaW4gUlJPIG1lc3NhZ2U6IFllcyANCgoNCiAgICAgICAgICAgICAgICAgICAgICAgRXhwaXJl
cyBGZWJydWFyeSAyMDEyICAgICAgICAgICAgICAgICAgW1BhZ2UgOF0gDQogICAgICAgDA0KCgoK
CgoKICAgSW50ZXJuZXQtRHJhZnQgICAgIGRyYWZ0LWlldGYtbXBscy1yc3ZwLXRlLW5vLXBocC1v
b2ItbWFwcGluZy0wOS50eHQgDQogICAgICAgDQoKICAgIA0KCiAgIG8gIE9PQiBtYXBwaW5nIGZs
YWc6ICAgDQoKICAgVGhpcyBmbGFncyBpcyB1c2VkIGluIHRoZSBBdHRyaWJ1dGVzIEZsYWdzIFRM
ViBpbiBhIFBhdGggbWVzc2FnZS4gDQogICBUaGUgZmxhZ3MgaGF2ZSBjb3JyZXNwb25kaW5nIG5l
dyBmbGFnIHRvIGJlIHVzZWQgaW4gdGhlIFJSTyANCiAgIEF0dHJpYnV0ZXMgc3Vib2JqZWN0LiBB
cyBwZXIgW1JGQzU0MjBdLCB0aGUgYml0IG51bWJlcmluZyBpbiB0aGUgDQogICBBdHRyaWJ1dGUg
RmxhZ3MgVExWIGFuZCB0aGUgUlJPIEF0dHJpYnV0ZXMgc3Vib2JqZWN0IGlzIA0KICAgaWRlbnRp
Y2FsLiBUaGF0IGlzLCB0aGUgc2FtZSBhdHRyaWJ1dGUgaXMgaW5kaWNhdGVkIGJ5IHRoZSBzYW1l
IA0KICAgYml0IGluIGJvdGggcGxhY2VzLiBUaGlzIGZsYWcgaXMgbm90IGFsbG93ZWQgaW4gdGhl
IEF0dHJpYnV0ZXMgDQogICBGbGFncyBUTFYgaW4gYSBSZXN2IG1lc3NhZ2UuIFNwZWNpZmljYWxs
eSwgQXR0cmlidXRlcyBvZiB0aGlzIA0KICAgZmxhZyBhcmUgYXMgZm9sbG93czogIA0KCiAgICAg
ICAgIC0gQml0IE51bWJlcjogVG8gYmUgYXNzaWduZWQgYnkgSUFOQS4gDQoKICAgICAgICAgLSBB
dHRyaWJ1dGUgZmxhZyBjYXJyaWVkIGluIFBhdGggbWVzc2FnZTogWWVzIA0KCiAgICAgICAgIC0g
QXR0cmlidXRlIGZsYWcgY2FycmllZCBpbiBSZXN2IG1lc3NhZ2U6IE5vIA0KCiAgICAgICAgIC0g
QXR0cmlidXRlIGZsYWcgY2FycmllZCBpbiBSUk8gbWVzc2FnZTogWWVzICANCgogICA0LjIuIE5l
dyBSU1ZQIGVycm9yIHN1Yi1jb2RlICANCgogICBGb3IgRXJyb3IgQ29kZSA9IDI1ICJOb3RpZnkg
RXJyb3IiIChzZWUgW1JGQzMyMDldKSB0aGUgZm9sbG93aW5nIA0KICAgc3ViLWNvZGUgaXMgZGVm
aW5lZC4gDQogICAgICAgDQogICAgICAgICAgICBTdWItY29kZSAgICAgICAgICAgICAgICAgICAg
VmFsdWUgDQogICAgICAgICAgICAtLS0tLS0tLSAgICAgICAgICAgICAgICAgICAgLS0tLS0gDQog
ICAgICAgDQogICAgICAgICAgICBObyBPT0IgbWFwcGluZyByZWNlaXZlZCAgICAgdG8gYmUgYXNz
aWduZWQgYnkgSUFOQS4gIA0KICAgICAgIA0KCiAgIDUuIEFja25vd2xlZGdtZW50cyANCgogICBU
aGUgYXV0aG9ycyB3b3VsZCBsaWtlIHRvIHRoYW5rIFlha292IFJla2h0ZXIgZm9yIGhpcyBzdWdn
ZXN0aW9ucyANCiAgIG9uIHRoZSBkcmFmdC4gICANCgogICAgDQogICA2LiBSZWZlcmVuY2VzIA0K
CiAgIDYuMS4gTm9ybWF0aXZlIFJlZmVyZW5jZXMgDQoKICAgW1JGQzIxMTldIEJyYWRuZXIsIFMu
LCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0ZSAgICAgICAgICAgICAgICAg
DQogICAgICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjExOSwgTWFy
Y2ggMTk5Ny4NCiAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICAgICAgICAgICAgRXhwaXJl
cyBGZWJydWFyeSAyMDEyICAgICAgICAgICAgICAgICAgW1BhZ2UgOV0gDQogICAgICAgDA0KCgoK
CgoKICAgSW50ZXJuZXQtRHJhZnQgICAgIGRyYWZ0LWlldGYtbXBscy1yc3ZwLXRlLW5vLXBocC1v
b2ItbWFwcGluZy0wOS50eHQgDQogICAgICAgDQoKICAgW1JGQzU0MjBdIEEuIEZhcnJlbCwgRC4g
UGFwYWRpbWl0cmlvdSwgSi4gUC4gVmFzc2V1ciBhbmQgQS4gDQogICAgICAgICAgICAgQXl5YW5n
YXIsICJFbmNvZGluZyBvZiBBdHRyaWJ1dGVzIGZvciBNdWx0aXByb3RvY29sIA0KICAgICAgICAg
ICAgIExhYmVsIFN3aXRjaGluZyAoTVBMUykgTGFiZWwgU3dpdGNoZWQgUGF0aCAoTFNQKSANCiAg
ICAgICAgICAgICBFc3RhYmxpc2htZW50IFVzaW5nIFJTVlAtVEUiLCBSRkMgNTQyMCwgRmVicnVh
cnkgMjAwNi4gDQoKICAgW1JGQzMyMDldIEQuIEF3ZHVjaGUsIEwuIEJlcmdlciwgRC4gR2FuLCBU
LiBMaSwgVi4gU3Jpbml2YXNhbiwgDQogICAgICAgICAgICAgYW5kIEcuIFN3YWxsb3csICJSU1ZQ
LVRFOiBFeHRlbnNpb25zIHRvIFJTVlAgZm9yIExTUCANCiAgICAgICAgICAgICBUdW5uZWxzIiwg
UkZDIDMyMDksIERlY2VtYmVyIDIwMDEuIA0KCiAgIFtSRkM0ODc1XSBSLiBBZ2dhcndhbCwgRC4g
UGFwYWRpbWl0cmlvdSwgUy4gWWFzdWthd2EsIGV0IGFsLCANCiAgICAgICAgICAgICAiRXh0ZW5z
aW9ucyB0byBSU1ZQLVRFIGZvciBQb2ludC10by1NdWx0aXBvaW50IFRFIA0KICAgICAgICAgICAg
IExTUHMiLCBSRkMgNDg3NS4gDQoKICAgW1JGQzM0NzNdIEJlcmdlciwgTC4sIEVkLiwgIkdlbmVy
YWxpemVkIE11bHRpLVByb3RvY29sIExhYmVsIA0KICAgICAgICAgICAgIFN3aXRjaGluZyAoR01Q
TFMpIFNpZ25hbGluZyBSZXNvdXJjZSBSZXNlclZhdGlvbiANCiAgICAgICAgICAgICBQcm90b2Nv
bC1UcmFmZmljIEVuZ2luZWVyaW5nIChSU1ZQLVRFKSBFeHRlbnNpb25zIiwgUkZDIA0KICAgICAg
ICAgICAgIDM0NzMsIEphbnVhcnkgMjAwMy4uIA0KCiAgIFtSRkMyMjA1XSBSLiBCcmFkZW4sIEVk
LiwgIlJlc291cmNlIFJlU2VyVmF0aW9uIFByb3RvY29sIChSU1ZQKSAtDQogICAgICAgICAgICAg
LSBWZXJzaW9uIDEgRnVuY3Rpb25hbCBTcGVjaWZpY2F0aW9uIiwgUkZDIDIyMDUsIA0KICAgICAg
ICAgICAgIFNlcHRlbWJlciAxOTk3LiAgIA0KCiAgIFtBVFRSSUJVVEUtQk5GXSBCZXJnZXIsIEwu
IGFuZCBTd2FsbG93LCBHLiwgIkxTUCBBdHRyaWJ1dGVzIFJlbGF0ZWQNCiAgICAgICAgICAgICBS
b3V0aW5nIEJhY2t1cy1OYXVyIEZvcm0iLCBkcmFmdC1pZXRmLWNjYW1wLWF0dHJpYnV0ZS0NCiAg
ICAgICAgICAgICBibmYsIHdvcmsgaW4gcHJvZ3Jlc3MuDQogICAgDQogICA2LjIuIEluZm9ybWF0
aXZlIFJlZmVyZW5jZXMgDQoKICAgW01WUE5dIEUuIFJvc2VuLCBSLiBBZ2dhcndhbCBldCBhbCwg
Ik11bHRpY2FzdCBpbiBNUExTL0JHUCBJUCANCiAgICAgICAgICBWUE5zIiwgZHJhZnQtaWV0Zi1s
M3Zwbi0yNTQ3YmlzLW1jYXN0LTEwLnR4dCwgd29yayBpbiANCiAgICAgICAgICBwcm9ncmVzcy4g
IA0KCiAgIFtSRkM0NzYxXSBLb21wZWxsYSwgSy4sIEVkLiwgYW5kIFkuIFJla2h0ZXIsIEVkLiwg
IlZpcnR1YWwgDQogICAgICAgICAgICAgUHJpdmF0ZSBMQU4gU2VydmljZSAoVlBMUykgVXNpbmcg
QkdQIGZvciBBdXRvLURpc2NvdmVyeSANCiAgICAgICAgICAgICBhbmQgU2lnbmFsaW5nIiwgUkZD
IDQ3NjEsIEphbnVhcnkgMjAwNy4gICANCgogICBbUkZDNTkyMV0gTS4gQm9jY2ksIFMuIEJyeWFu
dCwgZXQgYWwsICJBIEZyYW1ld29yayBmb3IgICAgICAgICAgICAgICANCiAgICAgICAgICAgICBN
UExTIGluIFRyYW5zcG9ydCBOZXR3b3JrcyIsIFJGQyA1OTIxLCBKYW51YXJ5IDIwMDcuIA0KCiAg
IFtSRkM1OTIwXSBMLiBGYW5nLCBFZC4sICJTZWN1cml0eSBGcmFtZXdvcmsgZm9yIE1QTFMgYW5k
IEdNUExTIA0KICAgICAgICAgICAgIE5ldHdvcmtzIiwgUkZDIDU5MjAsIEp1bHkgMjAxMC4NCgoK
ICAgICAgICAgICAgICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgICAgICAgIEV4cGlyZXMg
RmVicnVhcnkgMjAxMiAgICAgICAgICAgICAgICAgIFtQYWdlIDEwXSANCiAgICAgICAMDQoKCgoK
CgogICBJbnRlcm5ldC1EcmFmdCAgICAgZHJhZnQtaWV0Zi1tcGxzLXJzdnAtdGUtbm8tcGhwLW9v
Yi1tYXBwaW5nLTA5LnR4dCANCiAgICAgICANCgogICBbUkZDNDM3OV0gSy4gS29tcGVsbGEsIGFu
ZCBHLiBTd2FsbG93LCAiRGV0ZWN0aW5nIE11bHRpLVByb3RvY29sIA0KICAgICAgICAgICAgIExh
YmVsIFN3aXRjaGVkIChNUExTKSBEYXRhIFBsYW5lIEZhaWx1cmVzIiwgUkZDIDQzNzksIA0KICAg
ICAgICAgICAgIEZlYnJ1YXJ5IDIwMDYuDQogICBbUDJNUC1PQU1dIFMuIFNheGVuYSwgRWQuLCBH
LiBTd2FsbG93LCBaLiBBbGksIEEuIEZhcnJlbCwgUy4gDQogICAgICAgICAgICAgWWFzdWthd2Es
IFQuIE5hZGVhdSwgIkRldGVjdGluZyBEYXRhIFBsYW5lIEZhaWx1cmVzIGluIA0KICAgICAgICAg
ICAgIFBvaW50LXRvLU11bHRpcG9pbnQgTXVsdGlwcm90b2NvbCBMYWJlbCBTd2l0Y2hpbmcgDQog
ICAgICAgICAgICAgKE1QTFMpIC0gRXh0ZW5zaW9ucyB0byBMU1AgUGluZyIsIGRyYWZ0LWlldGYt
bXBscy1wMm1wLQ0KICAgICAgICAgICAgIGxzcC1waW5nLTE3LnR4dCwgd29yayBpbiBwcm9ncmVz
cy4gDQoKDQogICBBdXRob3IncyBBZGRyZXNzZXMgDQoKICAgICAgIA0KICAgICAgWmFmYXIgQWxp
IA0KICAgICAgQ2lzY28gU3lzdGVtcywgSW5jLiANCiAgICAgIEVtYWlsOiB6YWxpQGNpc2NvLmNv
bSANCiAgICAgICANCiAgICAgIEdlb3JnZSBTd2FsbG93IA0KICAgICAgQ2lzY28gU3lzdGVtcywg
SW5jLiANCiAgICAgIEVtYWlsOiBzd2FsbG93QGNpc2NvLmNvbSANCiAgICAgICANCiAgICAgIFJh
aHVsIEFnZ2Fyd2FsIA0KICAgICAgSnVuaXBlciBOZXR3b3JrcyANCiAgICAgIHJhaHVsQGp1bmlw
ZXIubmV0IA0KICAgICAgICAgICAgICAgICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDIwMTIgICAg
ICAgICAgICAgICAgICBbUGFnZSAxMV0gDQogICAgICAgDA==

------_=_NextPart_001_01CC5D16.43A0FB7A--

From jdrake@juniper.net  Thu Aug 18 07:02:14 2011
Return-Path: <jdrake@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381BA21F874E; Thu, 18 Aug 2011 07:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.812
X-Spam-Level: 
X-Spam-Status: No, score=-5.812 tagged_above=-999 required=5 tests=[AWL=0.187,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XmF2cZsHkpEZ; Thu, 18 Aug 2011 07:02:13 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3B70F21F86AC; Thu, 18 Aug 2011 07:02:11 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTk0bj4rsKEUJkaPyBfHbtDM5sNhWP44O@postini.com; Thu, 18 Aug 2011 07:03:07 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Thu, 18 Aug 2011 07:00:16 -0700
From: John E Drake <jdrake@juniper.net>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Luca Martini <lmartini@cisco.com>
Date: Thu, 18 Aug 2011 07:00:14 -0700
Subject: RE: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Topic: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxdD9cSGREkAFVzQWqJ2mkm3HQMwQATb/YRABP7P3A=
Message-ID: <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>,  <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>,  <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 18 Aug 2011 08:30:34 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 14:02:14 -0000

Sasha,

I completely agree with your recommendations:

- releasing the bottom-of-stack requirement on GAL

- making use of the statement in RFC 5586 that if GAL is encountered in a p=
acket then G-ACh header MUST be present immediately after the bottom of the=
 label stack (and not immediately after GAL)

- specifying that ECMP on labeled packets MUST ignore reserved labels

Thanks,

John

Sent from my iPhone

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
> Alexander Vainshtein
> Sent: Wednesday, August 17, 2011 9:52 PM
> To: Luca Martini
> Cc: mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit;
> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-
> gal-in-pw
>=20
> Luca and all,
> I have not found the statement you've proposed in draft-ietf-pwe3-fat-
> pw-06. Instead, it contans the following text in Section 8.5 "
> Applicability to MPLS-TP":
>=20
> <quote>
>    The flow aware transport of a PW reorders packets, therefore MUST
> NOT be
>    deployed in a network conforming to the MPLS-TP unless these
> integrity requirements
>    specified in the SLA can be satisfied.
> <end quote>
>=20
> (In the -07 version this text is repeated but followed by an incomplete
> statement " In a" immediately followed by the heading of Section 8.6.
> Since this addition is difficult to parse, I will ignore it for the
> moment.)
>=20
> IMHO and FWIW this means that prohibition on using flow aware PW in
> MPLS-TP environments is conditional on meeting specific SLA
> requirements for the service. So I think that the use case I've
> presented still holds.
>=20
> Please note also that, regardless of the restriction in draft-ietf-
> pwe3-fat-pw, be it conditional or absolute, usage of flow labels in an
> MPLS-TP domain would be perfectly safe if ECMP (i.e., hashing of the
> label stack and taking one of multiple NHLFEs for the given incoming
> label in the ILM) were not used in this domain, e.g., by associating
> exactly one ILM entry with each incoming label in the ILM. And since
> MPLS-TP is supposed to carry not just PW clients but also IP ones, I
> would expect that this would be the case in any MPLS-TP deployment.
>=20
> I also think that releasing one restriction (on using GAL in PWs) at
> the expense of making another, conditional one (on usage of flow labels
> in MPLS-TP environments) absolute is not the most appropriate method
> for resolving technical issues. IMHO and FWIW better way to resolve the
> problem would be by:
>=20
> - releasing the bottom-of-stack requirement on GAL
> - making use of the statement in RFC 5586 that if GAL is encountered in
> a packet then G-ACh header MUST be present immediately after the bottom
> of the label stack (and not immediately after GAL)
> - specifying that ECMP on labeled packets MUST ignore reserved labels.
>=20
> I think that these considerations have been presented already in the
> discussion on draft-nadeau-pwe-vccv-2.
>=20
> Of course it would be even better if we could agree on transition to
> universal usage of the CW and VCCV Type  1 in PWs. But this is a
> different story.
>=20
> Regards,
> Sasha
> ____________________________________
> From: Luca Martini [lmartini@cisco.com]
> Sent: Wednesday, August 17, 2011 9:58 PM
> To: Alexander Vainshtein
> Cc: Pablo Frank; mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan
> Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
>=20
> The solution is quite simple:
>=20
> "Flow Labels MUST not be used in an MPLS-TP environment."
>=20
> Luca
>=20
>=20
>=20
>=20
>=20
> On 08/16/11 21:46, Alexander Vainshtein wrote:
> > Pablo,
> > Sorry, but I think you're wrong. Only T-PE can insert the flow label
> > (because only T=3DPE can be "flow-aware"). S-PE simply performs swap on
> > PW label.
> >
> > Regards,
> >      Sasha
> >
> > ---------------------------------------------------------------------
> ---
> > *From:* Pablo Frank [pabloisnot@gmail.com]
> > *Sent:* Wednesday, August 17, 2011 12:17 AM
> > *To:* Alexander Vainshtein
> > *Cc:* ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit;
> > Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> > *Subject:* Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-
> in-pw
> >
> > I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS
> > domain in the middle segment, you're no longer in an MPLS-TP
> > environment and so the GAL is not required to be BOS.  During that
> > middle segment, the PW flow label would be placed below the GAL and
> > above the GACh.  It gets removed when it hits the S-PE that switches
> > you back into the MPLS-TP environment.  In other words, whether
> you're
> > in an MPLS-TP environment is determined segment by segment in a MS-
> PW.
> >
> > Pablo
> >
> > On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein
> > <Alexander.Vainshtein@ecitele.com
> > <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
> >
> >     Hi all,
> >     After having sent out my comments I've noticed that the specific
> >     example to illustrate the need to combine GAL and "flow label"
> was
> >     inaccurate.
> >
> >     A more relevant example would look like following (I do not
> >     include a diagram, but it can be easily provided if necessary)
> >
> >      1. A MS-PW:
> >           * Starts at an S-PE that resides at the edge of an MPLS-TP
> >             domain (no ECMP)
> >           * Crosses this domain and enters an IP/MPLS domain with
> ECMP
> >             enabled using a T-PE that resides at the age of these two
> >             domains
> >           * Leaves this domain and enters a 2nd MPLS-TP domain (using
> >             the 2nd T-PE)
> >           * Terminates on another S-PE at the edge of the 2nd MPLS-TP
> >             domain
> >      2. The operator intends to improve traffic distribution in the
> >         IP/MPLS domain, hence he enables insertion and discard of
> >         "flow labels" at the two S-PEs. Note that:
> >           * This does not violate the MPLS-TP restriction on ECMP:
> >             ECMP does not happen in he MPLS-TP domains
> >           * T-PEs do not even have to be aware of flow labels
> >      3. The operator also intends to operate some end-to-end OAM for
> >         this MS-PW using "GAL-in-PW". This results in a conflict
> since
> >         both GAL and "flow label" are defined (in the corresponding
> >         drafts) as bottom of stack.
> >
> >
> >
> >     IMHO this describes a realistic scenario where the two drafts are
> >     in controversy.
> >
> >     Regards,
> >          Sasha
> >     -----------------------------------------------------------------
> -------
> >     *From:* mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>
> >     [mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>] On Behalf
> >     Of Alexander Vainshtein [Alexander.Vainshtein@ecitele.com
> >     <mailto:Alexander.Vainshtein@ecitele.com>]
> >     *Sent:* Tuesday, August 16, 2011 4:26 PM
> >     *To:* ietf@ietf.org <mailto:ietf@ietf.org>
> >     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; Vladimir Kleiner;
> Idan
> >     Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> >     *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-
> in-pw
> >
> >     Hi all,
> >
> >
> >
> >     I would like to raise the following issue with regard to
> >     draft-ietf-pwe3-gal-in-pw
> >     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-
> pw/?include_text=3D1>:
> >     controversy vs. draft-ietf-pwe3-fat-pw
> >     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-
> pw/?include_text=3D1>
> >     with regard to bottom-of-stack position.
> >
> >
> >
> >     As stated in the Introduction, this draft removes the restriction
> >     imposed by RFC 5586 on usage of Generic Associated Channel Label
> >     (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586
> states:
> >
> >     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
> >     Concatenated Segments of LSPs, and with Sections, and MUST NOT be
> >     used with PWs.  It MUST always be at the bottom of the label
> stack
> >        (i.e., S bit set to 1).
> >
> >
> >
> >     draft-ietf-pwe3-gal-in-pw proposed to replace the original text
> in
> >     RFC 5586 with the following
> >
> >
> >
> >     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
> >     Concatenated Segments of LSPs, and with Sections, and MAY be used
> >     with PWs. It MUST always be at the bottom of the label stack
> >     (i.e., S bit set to 1).
> >
> >
> >
> >     I.e.,  while removing this restriction of 5586, it does not
> modify
> >     its requirement for the GAL being always at the bottom of the
> >     label stack.
> >
> >
> >
> >     At the same draft-ietf-pwe3-fat-pw (currently also in the IESG
> >     review) reserves the bottom of the PW stack for the PW flow
> >     labels, e.g., in Section 1.1:
> >
> >
> >
> >     This document describes a method of adding an additional label
> >     stack entry (LSE) at the bottom of stack in order to facilitate
> >     the load balancing of the flows within a PW over the available
> >     ECMPs.
> >
> >
> >
> >     One could argue that draft-ietf-pwe3-gal-in-pw only applies to
> >     MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. IMHO and
> >     FWIW,
> >
> >     such an argument, were it presented, would be highly problematic,
> >     because:
> >
> >
> >
> >     1.       RFC 5960 (which defines the MPLS-TP data plane) did not
> >     define any differences between the PW data plane in IP/MPLS and
> >     MPLS-TP.
> >
> >     2.       One of the most popular scenarios for using multi-
> segment
> >     pseudowires is the case when an edge-to-edge service emulation
> >     crosses multiple IP/MPLS and MPLS-TP domains. In these scenarios,
> >     the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-
> aware
> >     T-PE at the edge of an IP/MPLS domain) would potentially compete
> >     with GAL (inserted by a T-PE at the edge of an MPLS-TP domain,
> >     e.g., for relying a PW status message that it has received over a
> >     Targeted LDP session from the IP/MPLS domain to a static PW
> status
> >     message to cross the MPLS-TP domain) for the bottom-of-stack
> >     position.
> >
> >
> >
> >     The issue I am raising Is not new. It has been actively discussed
> >     on the PWE3 mailing list with regard to adoption of
> >     draft-nadeau-pwe3-vccv-2 as a WG document, with arguments  for
> >     both the flow label and GAL taking the bottom-of-the-stack
> >     position. But, to the best of my understanding, consensus on this
> >     issue has not been reached.
> >
> >
> >
> >     Hopefully this comment will be useful.
> >
> >
> >
> >     Regards,
> >
> >          Sasha
> >
> >
> >
> >     This e-mail message is intended for the recipient only and
> >     contains information which is CONFIDENTIAL and which may be
> >     proprietary to ECI Telecom. If you have received this
> transmission
> >     in error, please inform us by e-mail, phone or fax, and then
> >     delete the original and all copies thereof.
> >
> >     This e-mail message is intended for the recipient only and
> >     contains information which is CONFIDENTIAL and which may be
> >     proprietary to ECI Telecom. If you have received this
> transmission
> >     in error, please inform us by e-mail, phone or fax, and then
> >     delete the original and all copies thereof.
> >
> >
> >     _______________________________________________
> >     pwe3 mailing list
> >     pwe3@ietf.org <mailto:pwe3@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/pwe3
> >
> >
> > This e-mail message is intended for the recipient only and contains
> > information which is CONFIDENTIAL and which may be proprietary to ECI
> > Telecom. If you have received this transmission in error, please
> > inform us by e-mail, phone or fax, and then delete the original and
> > all copies thereof.
> >
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>=20
> This e-mail message is intended for the recipient only and contains
> information which is CONFIDENTIAL and which may be proprietary to ECI
> Telecom. If you have received this transmission in error, please inform
> us by e-mail, phone or fax, and then delete the original and all copies
> thereof.
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From Alexander.Vainshtein@ecitele.com  Wed Aug 17 21:51:41 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C115E8004 for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 21:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level: 
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[AWL=1.098,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6, MIME_QP_LONG_LINE=1.396,  RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9xhEjh7yf72 for <ietf@ietfa.amsl.com>; Wed, 17 Aug 2011 21:51:40 -0700 (PDT)
Received: from mail21.messagelabs.com (mail21.messagelabs.com [85.158.143.35]) by ietfa.amsl.com (Postfix) with SMTP id C82A05E8003 for <ietf@ietf.org>; Wed, 17 Aug 2011 21:51:39 -0700 (PDT)
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-6.tower-21.messagelabs.com!1313643122!34996405!3
X-Originating-IP: [147.234.242.235]
X-StarScan-Version: 6.3.6; banners=-,-,-
Received: (qmail 6523 invoked from network); 18 Aug 2011 04:52:13 -0000
Received: from ilptbmg02-out.ecitele.com (HELO ilptbmg02.ecitele.com) (147.234.242.235) by server-6.tower-21.messagelabs.com with SMTP; 18 Aug 2011 04:52:13 -0000
X-AuditID: 93eaf2e8-b7b3eae00000414f-ae-4e4c93c6d087
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg02.ecitele.com (Symantec Messaging Gateway) with SMTP id 05.71.16719.6C39C4E4; Thu, 18 Aug 2011 07:23:35 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Thu, 18 Aug 2011 07:52:27 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Luca Martini <lmartini@cisco.com>
Date: Thu, 18 Aug 2011 07:52:19 +0300
Subject: RE: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Topic: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxdD9cSGREkAFVzQWqJ2mkm3HQMwQATb/YR
Message-ID: <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>,  <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>, <4E4C0F3F.8010700@cisco.com>
In-Reply-To: <4E4C0F3F.8010700@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA2VTf2wMWRy/NzO7O12dy7NV+7pB5saPpGrZKjLCivQfK9oqFeQSrbH7bnfY nVk7U7EIzUkIEkqpdJH6US31K3qSotxRqWodLjmSqtY/mlaXiNSPUrRmzOn1cu+vz3ufz+f7 ee/l+6VJW7/ZQYuSiiOSEOTMVqok3vPWeackK8dVfS2V77xYTvFdbV8sfOvJ0yb+4ItGM7+7 5xI11+TZ/+miyXMl1m7xVFR8JHLJn4vAbEGSZFVQMevDitfN5UbEdYI3yrGiz82lc2w4KHhx CEuqmxPCYSz5uDlW9n9rtiYTJRZLXtknSn43Nz9voZPnp890pnNzJoxNz5hlXRIQFRY7Q4IY ZENYUQQ/ZrWTlZfIQM+dYkv4+LL1R473morA48ydIIFGcBr6o/OeycAj0V9PL5h3Aittg3UA 1TZ8tBibUoAa2+NAV5mhG9WcaTfreAQcj87f+gR0EQn7CdS59W9CJyiNKK16adFxEpyH9lSe AobBg8pONFkMPBWVHDpH6piBi9C76gOUjm3wNoFeN2TrOAGmoru3Gr9pgHa93uaz3+qT0I5a O8oJ49oQVVx7QBo4GXU/6zcZ+mTUtv0CMPST0NG6HrOB01DlsRf/5A5HTWUdlOFNQTdPtVDF wB4bEhEbYo8NsceG2I8CqhqkiMGwuirkd011yoXqZOwVVRzEk71yqAYY3fP8MnjyZ2o9gDTg EpmWrgU5NpOwTomG6kEKTXDJTG9ZVo7tx1WyLxoQlEBBpDCIlXqAaJIbwWxjNY7xCdENOCJ/ p3jtp/eSjmFeWetTSS3IcLn+s+HszC7vy2wb9GuttwbjMI58t46iaQ4x1/XE4RHsx+t/EYPq vzRBJ+jJiVryDV3DKGEhpIh+g28GTnpHx93bwEZJsoQddgbGNBHURYFCabCOPjZbBgYG4sCu vTmJ6dNLJWpDNVgproUQWkjrVY8eoo3IIOUoAqdrPxfk5f20MWNf4Per3bubnvQvG7O8qvic u/T66vtvZvje/rDixqGmV/aRBx5louxMf/6DrDF1v1XGub4Vexf35eZvTmLH5U8c3bLlsZWo +bV1XHPt8ykQPnRE1276kGbnq13lKxvb9ueljeoeu2epq2JRsmOKueFwF6HIhVU13e/zOUoJ COkTyYgifAVO/Ut1EQQAAA==
X-Mailman-Approved-At: Thu, 18 Aug 2011 08:30:34 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Pablo Frank <pabloisnot@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 04:51:41 -0000

Luca and all,
I have not found the statement you've proposed in draft-ietf-pwe3-fat-pw-06.=
 Instead, it contans the following text in Section 8.5 " Applicability to MP=
LS-TP":

<quote>
   The flow aware transport of a PW reorders packets, therefore MUST NOT be
   deployed in a network conforming to the MPLS-TP unless these integrity re=
quirements 
   specified in the SLA can be satisfied.
<end quote>

(In the -07 version this text is repeated but followed by an incomplete stat=
ement " In a" immediately followed by the heading of Section 8.6. Since this=
 addition is difficult to parse, I will ignore it for the moment.)

IMHO and FWIW this means that prohibition on using flow aware PW in MPLS-TP=
 environments is conditional on meeting specific SLA requirements for the se=
rvice. So I think that the use case I've presented still holds.

Please note also that, regardless of the restriction in draft-ietf-pwe3-fat-=
pw, be it conditional or absolute, usage of flow labels in an MPLS-TP domain=
 would be perfectly safe if ECMP (i.e., hashing of the label stack and takin=
g one of multiple NHLFEs for the given incoming label in the ILM) were not u=
sed in this domain, e.g., by associating exactly one ILM entry with each inc=
oming label in the ILM. And since MPLS-TP is supposed to carry not just PW c=
lients but also IP ones, I would expect that this would be the case in any M=
PLS-TP deployment.

I also think that releasing one restriction (on using GAL in PWs) at the exp=
ense of making another, conditional one (on usage of flow labels in MPLS-TP=
 environments) absolute is not the most appropriate method for resolving tec=
hnical issues. IMHO and FWIW better way to resolve the problem would be by:

- releasing the bottom-of-stack requirement on GAL 
- making use of the statement in RFC 5586 that if GAL is encountered in a pa=
cket then G-ACh header MUST be present immediately after the bottom of the l=
abel stack (and not immediately after GAL)
- specifying that ECMP on labeled packets MUST ignore reserved labels.

I think that these considerations have been presented already in the discuss=
ion on draft-nadeau-pwe-vccv-2. 

Of course it would be even better if we could agree on transition to univers=
al usage of the CW and VCCV Type  1 in PWs. But this is a different story.

Regards,
Sasha
____________________________________
From: Luca Martini [lmartini@cisco.com]
Sent: Wednesday, August 17, 2011 9:58 PM
To: Alexander Vainshtein
Cc: Pablo Frank; mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit=
; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw

The solution is quite simple:

"Flow Labels MUST not be used in an MPLS-TP environment."

Luca





On 08/16/11 21:46, Alexander Vainshtein wrote:
> Pablo,
> Sorry, but I think you're wrong. Only T-PE can insert the flow label
> (because only T=3DPE can be "flow-aware"). S-PE simply performs swap on
> PW label.
>
> Regards,
>      Sasha
>
> ------------------------------------------------------------------------
> *From:* Pablo Frank [pabloisnot@gmail.com]
> *Sent:* Wednesday, August 17, 2011 12:17 AM
> *To:* Alexander Vainshtein
> *Cc:* ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit;
> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> *Subject:* Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
>
> I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS
> domain in the middle segment, you're no longer in an MPLS-TP
> environment and so the GAL is not required to be BOS.  During that
> middle segment, the PW flow label would be placed below the GAL and
> above the GACh.  It gets removed when it hits the S-PE that switches
> you back into the MPLS-TP environment.  In other words, whether you're
> in an MPLS-TP environment is determined segment by segment in a MS-PW.
>
> Pablo
>
> On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein
> <Alexander.Vainshtein@ecitele.com
> <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
>
>     Hi all,
>     After having sent out my comments I've noticed that the specific
>     example to illustrate the need to combine GAL and "flow label" was
>     inaccurate.
>
>     A more relevant example would look like following (I do not
>     include a diagram, but it can be easily provided if necessary)
>
>      1. A MS-PW:
>           * Starts at an S-PE that resides at the edge of an MPLS-TP
>             domain (no ECMP)
>           * Crosses this domain and enters an IP/MPLS domain with ECMP
>             enabled using a T-PE that resides at the age of these two
>             domains
>           * Leaves this domain and enters a 2nd MPLS-TP domain (using
>             the 2nd T-PE)
>           * Terminates on another S-PE at the edge of the 2nd MPLS-TP
>             domain
>      2. The operator intends to improve traffic distribution in the
>         IP/MPLS domain, hence he enables insertion and discard of
>         "flow labels" at the two S-PEs. Note that:
>           * This does not violate the MPLS-TP restriction on ECMP:
>             ECMP does not happen in he MPLS-TP domains
>           * T-PEs do not even have to be aware of flow labels
>      3. The operator also intends to operate some end-to-end OAM for
>         this MS-PW using "GAL-in-PW". This results in a conflict since
>         both GAL and "flow label" are defined (in the corresponding
>         drafts) as bottom of stack.
>
>
>
>     IMHO this describes a realistic scenario where the two drafts are
>     in controversy.
>
>     Regards,
>          Sasha
>     ----------------------------------------------------------------------=
--
>     *From:* mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>
>     [mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>] On Behalf
>     Of Alexander Vainshtein [Alexander.Vainshtein@ecitele.com
>     <mailto:Alexander.Vainshtein@ecitele.com>]
>     *Sent:* Tuesday, August 16, 2011 4:26 PM
>     *To:* ietf@ietf.org <mailto:ietf@ietf.org>
>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; Vladimir Kleiner; Idan
>     Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>     *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
>
>     Hi all,
>
>
>
>     I would like to raise the following issue with regard to
>     draft-ietf-pwe3-gal-in-pw
>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-pw/?in=
clude_text=3D1>:
>     controversy vs. draft-ietf-pwe3-fat-pw
>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-pw/?include_text=
=3D1>
>     with regard to bottom-of-stack position.
>
>
>
>     As stated in the Introduction, this draft removes the restriction
>     imposed by RFC 5586 on usage of Generic Associated Channel Label
>     (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586 states:
>
>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
>     Concatenated Segments of LSPs, and with Sections, and MUST NOT be
>     used with PWs.  It MUST always be at the bottom of the label stack
>        (i.e., S bit set to 1).
>
>
>
>     draft-ietf-pwe3-gal-in-pw proposed to replace the original text in
>     RFC 5586 with the following
>
>
>
>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
>     Concatenated Segments of LSPs, and with Sections, and MAY be used
>     with PWs. It MUST always be at the bottom of the label stack
>     (i.e., S bit set to 1).
>
>
>
>     I.e.,  while removing this restriction of 5586, it does not modify
>     its requirement for the GAL being always at the bottom of the
>     label stack.
>
>
>
>     At the same draft-ietf-pwe3-fat-pw (currently also in the IESG
>     review) reserves the bottom of the PW stack for the PW flow
>     labels, e.g., in Section 1.1:
>
>
>
>     This document describes a method of adding an additional label
>     stack entry (LSE) at the bottom of stack in order to facilitate
>     the load balancing of the flows within a PW over the available
>     ECMPs.
>
>
>
>     One could argue that draft-ietf-pwe3-gal-in-pw only applies to
>     MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. IMHO and
>     FWIW,
>
>     such an argument, were it presented, would be highly problematic,
>     because:
>
>
>
>     1.       RFC 5960 (which defines the MPLS-TP data plane) did not
>     define any differences between the PW data plane in IP/MPLS and
>     MPLS-TP.
>
>     2.       One of the most popular scenarios for using multi-segment
>     pseudowires is the case when an edge-to-edge service emulation
>     crosses multiple IP/MPLS and MPLS-TP domains. In these scenarios,
>     the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-aware
>     T-PE at the edge of an IP/MPLS domain) would potentially compete
>     with GAL (inserted by a T-PE at the edge of an MPLS-TP domain,
>     e.g., for relying a PW status message that it has received over a
>     Targeted LDP session from the IP/MPLS domain to a static PW status
>     message to cross the MPLS-TP domain) for the bottom-of-stack
>     position.
>
>
>
>     The issue I am raising Is not new. It has been actively discussed
>     on the PWE3 mailing list with regard to adoption of
>     draft-nadeau-pwe3-vccv-2 as a WG document, with arguments  for
>     both the flow label and GAL taking the bottom-of-the-stack
>     position. But, to the best of my understanding, consensus on this
>     issue has not been reached.
>
>
>
>     Hopefully this comment will be useful.
>
>
>
>     Regards,
>
>          Sasha
>
>
>
>     This e-mail message is intended for the recipient only and
>     contains information which is CONFIDENTIAL and which may be
>     proprietary to ECI Telecom. If you have received this transmission
>     in error, please inform us by e-mail, phone or fax, and then
>     delete the original and all copies thereof.
>
>     This e-mail message is intended for the recipient only and
>     contains information which is CONFIDENTIAL and which may be
>     proprietary to ECI Telecom. If you have received this transmission
>     in error, please inform us by e-mail, phone or fax, and then
>     delete the original and all copies thereof.
>
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pwe3
>
>
> This e-mail message is intended for the recipient only and contains
> information which is CONFIDENTIAL and which may be proprietary to ECI
> Telecom. If you have received this transmission in error, please
> inform us by e-mail, phone or fax, and then delete the original and
> all copies thereof.
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


From sm@elandsys.com  Thu Aug 18 02:30:24 2011
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A13721F856D for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 02:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.623
X-Spam-Level: 
X-Spam-Status: No, score=-102.623 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ViSf4tandC7K for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 02:30:22 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by ietfa.amsl.com (Postfix) with ESMTP id 69AF921F86A9 for <ietf@ietf.org>; Thu, 18 Aug 2011 02:30:22 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.235.24]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p7I9V0tl018209; Thu, 18 Aug 2011 02:31:10 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1313659872; bh=47DLt3wvmrzpvTurFWRg0QXQzRQ=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=JYHfo/sVVWgvsfuy2Y40le7nHNsQGR5TNRB0brKCQWA87VAzskJ5GYMHO+FaGtJh5 6eXZR8z4xt6lbVGQ7dan5NTxjVsIlnN3n7zUvauNZZiP53K3+6RNOUNiHgNrwRdtzQ T6K9N2LzOEKl/VM9DD1y9S2qSg8w4FXmt7nRV6d8=
Message-Id: <6.2.5.6.2.20110818002509.09c79708@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 18 Aug 2011 02:27:38 -0700
To: mrex@sap.com
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission
In-Reply-To: <201108162101.p7GL1VrP025475@fs4113.wdf.sap.corp>
References: <01O4STRDJ1P400VHKR@mauve.mrochek.com> <201108162101.p7GL1VrP025475@fs4113.wdf.sap.corp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Thu, 18 Aug 2011 08:30:34 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 09:30:24 -0000

Hi Martin,
At 14:01 16-08-2011, Martin Rex wrote:
>Security-wise, the SRV record suggested by rfc6196 seems to create
>additional security problems, so I would also not like to see it being
>"adopted" as is.  :-/

The YAM working group participants did not point to any security 
problem in RFC 6186.  A reading of the YAM mailing list archive would 
make it clear that nobody disliked RFC 6186.  There was a 
pre-evaluation of RFC 4409 (see 
draft-ietf-yam-4409bis-submit-pre-evaluation-00).  As there seem to 
be some confusion when the term "downref" is mentioned, I'll put the 
question as follows:

   Could the reference for RFC 6186 be mentioned in
   draft-ietf-yam-4409bis-submit-pre-evaluation-00?

If the above question is too stringent, let's try a simpler one:

   Is there any documentation about implementations of RFC 6186?

Given that nobody came forward to point to any documentation, there 
wasn't any reason to spend more time on the question.

>While I fully agree that it is sensible to relegate (and fix) the
>authentication to a different document, I currently see this:
>
>http://tools.ietf.org/html/draft-ietf-yam-rfc4409bis-02#section-7
>
>    | AUTH             | Authentication   |    MUST   | [SMTP-AUTH]     |
>
>
>And it somehow feels wrong to exhibit an ostrich-like behaviour about
>the current mess around SMTP-AUTH in the security considerations section.

RFC 4954 is authoritative for SMTP AUTH.  If there is a mess around 
SMTP AUTH and it has to be fixed, the best place to do so is in a 
revision of RFC 4954.  This draft is more about the separation of 
submission and relay of messages.

>I believe it would be sensible to describe the desired authentication model
>for MUA->MTA in more detail, beyond the mere reference of [SMTP-AUTH]
>in section 4.3 of the current document:

The intent is to publish the document as a Full Standard.  As much as 
it may be sensible to describe the desired authentication model, it 
had to be shown that changes would
contribute in a substantial and substantive way to the quality and 
comprehensibility of the specification as that was the guideline 
given to working group participants.  If you would like to recommend 
additional text, I suggest sending a message to the YAM mailing list.

If there are any questions that have not addressed to your 
satisfaction, please let me know so that I can bring it to the 
attention of the working group.

Regards,
S. Moonesamy 


From sm@elandsys.com  Thu Aug 18 02:30:24 2011
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD0FE21F86A9 for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 02:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.622
X-Spam-Level: 
X-Spam-Status: No, score=-102.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XoTVjWE8rY9C for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 02:30:22 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by ietfa.amsl.com (Postfix) with ESMTP id 69A6421F863E for <ietf@ietf.org>; Thu, 18 Aug 2011 02:30:22 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.235.24]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p7I9V0tj018209; Thu, 18 Aug 2011 02:31:05 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1313659869; bh=8J2Xcr+d5qsDfrwx7e8+P9ffif8=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=cQlw1qPmOBBcfg7QlQ1vWe9+PdPg1KFzJaCgHVmoD8Sq+nsb3dLI1ITB1SwDH7J4d idSE8Fd9HKMKQpb5d2MpOv/pG5a3imL2hhww/6PYXYOEKku7ZgOoWzFlTqpswJPtrp R7RhA89ttwnklEICK6ngg2F/J05G/uoAI2KQ/ZnM=
Message-Id: <6.2.5.6.2.20110817232216.0b6efc50@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 18 Aug 2011 00:06:21 -0700
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [yam] Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
In-Reply-To: <4E4BEA77.4070606@gmail.com>
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E4BEA77.4070606@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Thu, 18 Aug 2011 08:30:34 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 09:30:24 -0000

Hi Mykyta,
At 09:21 17-08-2011, Mykyta Yevstifeyev wrote:
>IANA commented that it should be clear that "the registry" refers to 
>SMTP Service
>Extensions (http://www.iana.org/assignments/mail-parameters); but 
>the registry there

 From the write-up:

The entry in the SMTP Service Extensions registry for RFC 4409 should 
be updated to reference this document. The reference for Submit (RFC 
2476) should be updated to point to this document. The registry 
should be updated to reflect the changed and new entries in Section 7.

"the registry" in the above should be read as "the SMTP Service 
Extensions registry".

>seems to have other format compared to Table 1:
>
>>     +------------------+------------------+-----------+-----------------+
>>     | Keyword          | Name             | Submissio | Reference       |
>>     |                  |                  | n         |                 |
>
>please compare with
>
>>Keywords             Description                         Reference    Note
>
>So how is this table going to be incorporated in the aforementioned registry?

The following extract is from Section 7.1 of RFC 2476:

    RFC   Name             Submission  Reference
    ----  ---------------  ----------  ------------------
    2197  Pipelining         SHOULD    [PIPELINING]
    2034  Error Codes        SHOULD    [CODES-EXTENSION]
    1985  ETRN              MUST NOT   [ETRN]

This is from Section 7.1 of RFC 4409:

Keyword        Name                        Submission  Reference
----------     --------------------------  ----------  ----------------
PIPELINING     Pipelining                    SHOULD    [PIPELINING]
ENHANCEDSTATUSCODES  Enhanced Status Codes   SHOULD    [CODES-EXTENSION]
ETRN           Extended Turn                 MUST NOT  [ETRN]

And finally from Section 7.1 of draft-ietf-yam-rfc4409bis-02:


    | Keyword          | Name             | Submissio | Reference       |
    |                  |                  | n         |                 |
    +------------------+------------------+-----------+-----------------+
    | PIPELINING       | Pipelining       |   SHOULD  | [PIPELINING]    |
    | ENHANCEDSTATUSCO | Enhanced Status  |   SHOULD  | [CODES-EXTENSIO |
    | DES              | Codes            |           | N]              |
    | ETRN             | Extended Turn    |  MUST NOT | [ETRN]          |

The table has been in two previous RFCs.  It was not a problem 
then.  It should not be a problem now.  Section 10 of the draft 
mentions how the table is going to be incorporated.  The document 
editors will follow up on this editorial matter.

Regards,
S. Moonesamy 


From hartmans@mit.edu  Thu Aug 18 14:26:14 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 139F021F8B44 for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 14:26:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.851
X-Spam-Level: 
X-Spam-Status: No, score=-103.851 tagged_above=-999 required=5 tests=[AWL=-1.586, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7qhHMMi0uXm for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 14:26:13 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDCF21F8B3F for <ietf@ietf.org>; Thu, 18 Aug 2011 14:26:13 -0700 (PDT)
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 57F16202B2; Thu, 18 Aug 2011 17:29:32 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 4CB7742B7; Thu, 18 Aug 2011 17:27:03 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Simon Josefsson <simon@josefsson.org>
Subject: Re: AD review of draft-ietf-krb-wg-otp-preauth
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org>
Date: Thu, 18 Aug 2011 17:27:03 -0400
In-Reply-To: <87r54iihbb.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 18 Aug 2011 22:40:56 +0200")
Message-ID: <tslaab62yxk.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-krb-wg@lists.anl.gov, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, gareth.richards@rsa.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 21:26:14 -0000

>>>>> "Simon" == Simon Josefsson <simon@josefsson.org> writes:

    Simon> Sam Hartman <hartmans-ietf@mit.edu> writes:
    >> Actually, I have a question about interoperability here.
    >> 
    >> It's my assumption that a client of this specification needs to
    >> implement basically all the options:
    >> 
    >> * encrypted OTP values and values used for key derivation *
    >> separate pins and pins that are together * at least 4 pass mode
    >> 
    >> So that the server has flexibility to implement what its OTP
    >> token requires.
    >> 
    >> Are people assuming that it is acceptable to implement a client
    >> that only implements the facilities needed by one particular OTP
    >> token?

    Simon> Yes, and I believe that is unavoidable -- there is no way to
    Simon> properly test all features of any implementation without
    Simon> having some OTP token that excercises each feature.

OK.  That makes me very uncomfortable.  As an individual I'd prefer that
this draft not be published without a mandatory-to-implement subset.
My assumption was that the client needed to implement everything.
If that's not globally held I think we have much more work to do.

Please consider this an individual last call comment, not as a comment
as a chair.

From narten@us.ibm.com  Thu Aug 18 21:52:18 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9908E21F854F for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 21:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.58
X-Spam-Level: 
X-Spam-Status: No, score=-106.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mDJZ4IpwwJjl for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 21:52:18 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 03B2121F855B for <ietf@ietf.org>; Thu, 18 Aug 2011 21:52:17 -0700 (PDT)
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7J4bsia021228 for <ietf@ietf.org>; Thu, 18 Aug 2011 22:37:54 -0600
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7J4r4Na191566 for <ietf@ietf.org>; Thu, 18 Aug 2011 22:53:04 -0600
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 p7IMqae3002775 for <ietf@ietf.org>; Thu, 18 Aug 2011 16:52:36 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7IMqaY2002770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 18 Aug 2011 16:52:36 -0600
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 p7J4r2AM003884 for <ietf@ietf.org>; Fri, 19 Aug 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p7J4r2F7003841 for ietf@ietf.org; Fri, 19 Aug 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201108190453.p7J4r2F7003841@rotala.raleigh.ibm.com>
Date: Fri, 19 Aug 2011 00:53:02 -0400
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 04:52:18 -0000

Total of 88 messages in the last 7 days.
 
script run at: Fri Aug 19 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 14.77% |   13 | 14.40% |   134750 | moore@network-heretics.com
  4.55% |    4 |  9.28% |    86802 | alexander.vainshtein@ecitele.com
  2.27% |    2 | 10.15% |    94952 | mary.ietf.barnes@gmail.com
  5.68% |    5 |  3.58% |    33460 | ned+ietf@mauve.mrochek.com
  4.55% |    4 |  3.45% |    32242 | narten@us.ibm.com
  4.55% |    4 |  3.16% |    29570 | hsantos@isdg.net
  2.27% |    2 |  5.38% |    50385 | pabloisnot@gmail.com
  4.55% |    4 |  2.76% |    25833 | mrex@sap.com
  3.41% |    3 |  2.57% |    24022 | housley@vigilsec.com
  1.14% |    1 |  4.57% |    42796 | zali@cisco.com
  3.41% |    3 |  2.18% |    20413 | brian.e.carpenter@gmail.com
  3.41% |    3 |  2.11% |    19744 | sm+ietf@elandsys.com
  3.41% |    3 |  2.02% |    18896 | hartmans-ietf@mit.edu
  2.27% |    2 |  2.82% |    26434 | dromasca@avaya.com
  1.14% |    1 |  3.35% |    31393 | davari@broadcom.com
  2.27% |    2 |  2.02% |    18939 | rbarnes@bbn.com
  2.27% |    2 |  1.71% |    16016 | sm@resistor.net
  2.27% |    2 |  1.55% |    14508 | evnikita2@gmail.com
  2.27% |    2 |  1.53% |    14362 | barryleiba@computer.org
  2.27% |    2 |  1.33% |    12407 | jari.arkko@piuha.net
  1.14% |    1 |  1.92% |    17924 | jdrake@juniper.net
  1.14% |    1 |  1.62% |    15202 | ron.even.tlv@gmail.com
  1.14% |    1 |  1.40% |    13124 | lmartini@cisco.com
  1.14% |    1 |  1.13% |    10564 | spencer@wonderhamster.org
  1.14% |    1 |  1.12% |    10442 | terry.manderson@icann.org
  1.14% |    1 |  0.99% |     9224 | john-ietf@jck.com
  1.14% |    1 |  0.93% |     8709 | yaakov_s@rad.com
  1.14% |    1 |  0.87% |     8150 | rolf.winter@neclab.eu
  1.14% |    1 |  0.74% |     6895 | stephen.farrell@cs.tcd.ie
  1.14% |    1 |  0.72% |     6719 | ghudson@mit.edu
  1.14% |    1 |  0.69% |     6486 | mcquilwp@pobox.com
  1.14% |    1 |  0.68% |     6396 | adrian@olddog.co.uk
  1.14% |    1 |  0.68% |     6361 | ynir@checkpoint.com
  1.14% |    1 |  0.67% |     6284 | vesely@tana.it
  1.14% |    1 |  0.65% |     6090 | tony@att.com
  1.14% |    1 |  0.64% |     5969 | jyee@afilias.info
  1.14% |    1 |  0.63% |     5933 | dhc@dcrocker.net
  1.14% |    1 |  0.63% |     5904 | rbonica@juniper.net
  1.14% |    1 |  0.63% |     5896 | ben@nostrum.com
  1.14% |    1 |  0.59% |     5521 | stpeter@stpeter.im
  1.14% |    1 |  0.57% |     5327 | john@jlc.net
  1.14% |    1 |  0.54% |     5098 | nick@inex.ie
  1.14% |    1 |  0.52% |     4891 | mrossi@swin.edu.au
  1.14% |    1 |  0.51% |     4784 | msk@cloudmark.com
--------+------+--------+----------+------------------------
100.00% |   88 |100.00% |   935817 | Total

From hartmans@mit.edu  Fri Aug 19 07:47:24 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74FC721F8610 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 07:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.823
X-Spam-Level: 
X-Spam-Status: No, score=-103.823 tagged_above=-999 required=5 tests=[AWL=-1.558, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wz9lH7G6rEkv for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 07:47:24 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC1721F85E3 for <ietf@ietf.org>; Fri, 19 Aug 2011 07:47:23 -0700 (PDT)
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 ABB7C2034A; Fri, 19 Aug 2011 10:50:39 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E127342B7; Fri, 19 Aug 2011 10:48:09 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Greg Hudson <ghudson@MIT.EDU>
Subject: Re: [Ietf-krb-wg] AD review of draft-ietf-krb-wg-otp-preauth
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org> <tslaab62yxk.fsf@mit.edu> <B1371F619AB0A94C9AC73CF2E475485B038C492C53@MX11A.corp.emc.com> <1313763070.16540.128.camel@t410>
Date: Fri, 19 Aug 2011 10:48:09 -0400
In-Reply-To: <1313763070.16540.128.camel@t410> (Greg Hudson's message of "Fri,  19 Aug 2011 10:11:10 -0400")
Message-ID: <tsl4o1dzcd2.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: "simon@josefsson.org" <simon@josefsson.org>, "ietf-krb-wg@lists.anl.gov" <ietf-krb-wg@lists.anl.gov>, "hartmans-ietf@MIT.EDU" <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "gareth.richards@rsa.com" <gareth.richards@rsa.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 14:47:24 -0000

>>>>> "Greg" == Greg Hudson <ghudson@MIT.EDU> writes:
87
    Greg> On Fri, 2011-08-19 at 08:53 -0400, gareth.richards@rsa.com wrote:
    >> I had always thought the same way as Sam, that clients would be
    >> required to implement all of the options since there appears to
    >> be no other way for them to support different disconnected token
    >> types.  The specification was intended to be token independent
    >> and the assumption was always that the clients would also be.

    Greg> I agree, at least at the general level and for disconnected
    Greg> tokens.  (Does nextOTP make any sense for disconnected
    Greg> tokens?)

I think you prompt the person to hit the next value button

From moore@network-heretics.com  Fri Aug 19 09:25:10 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A90E821F8862 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 09:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhHhydA+oGBw for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 09:25:10 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0105D21F884C for <ietf@ietf.org>; Fri, 19 Aug 2011 09:25:09 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 708C02038D for <ietf@ietf.org>; Fri, 19 Aug 2011 12:26:06 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Fri, 19 Aug 2011 12:26:06 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:content-transfer-encoding:message-id :references:to; s=smtpout; bh=HA/SmycZvTMp5sal+17CvXgYUAg=; b=I+ UZk35m5GV7ufVKaCcsXoSZ/NpqSoTaGpEjCVjG7dYQwgs8/Zc43toUDqeeKfnn6E M1wKJokQXh7Yern3dOYTuf5Yo8ISr01DMZ3q77J2Yeym4dLQxVTKlbwT0w9bHclJ GUxbl8WOanL7/RCdOVV4sbPAytiST/ZcDRS5QN3As=
X-Sasl-enc: P3ckaKHD3yXWCmvlI2NYahiPE0LjJytA30UY7W95gj3v 1313771166
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id CFB1488020B; Fri, 19 Aug 2011 12:26:05 -0400 (EDT)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110819161025.15887.78808.idtracker@ietfa.amsl.com>
Date: Fri, 19 Aug 2011 12:25:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7372AF7E-0981-4A3D-898E-97FB139C9B98@network-heretics.com>
References: <20110819161025.15887.78808.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 16:25:10 -0000

I recommend that the address block be published in the document when it =
becomes an RFC.

It's also arguable that 6to4 implementations should recognize addresses =
from the assigned prefix and disable 6to4 when configured with such =
addresses.

The document could perhaps make it clearer that this prefix is intended =
for assignment by access providers and not, e.g., by enterprise networks =
or for use in interconnection between private networks.

Keith


From hartmans@mit.edu  Fri Aug 19 09:27:14 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2796521F8538 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 09:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.81
X-Spam-Level: 
X-Spam-Status: No, score=-103.81 tagged_above=-999 required=5 tests=[AWL=-1.545, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54fwxlLbbJUz for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 09:27:13 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id AB99321F8531 for <ietf@ietf.org>; Fri, 19 Aug 2011 09:27:13 -0700 (PDT)
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 E087A20184; Fri, 19 Aug 2011 12:30:33 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 17C8542B7; Fri, 19 Aug 2011 12:28:04 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: <gareth.richards@rsa.com>
Subject: Re: [Ietf-krb-wg] AD review of draft-ietf-krb-wg-otp-preauth
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org> <tslaab62yxk.fsf@mit.edu> <B1371F619AB0A94C9AC73CF2E475485B038C492C53@MX11A.corp.emc.com> <1313763070.16540.128.camel@t410> <tsl4o1dzcd2.fsf@mit.edu> <B1371F619AB0A94C9AC73CF2E475485B038C492CF3@MX11A.corp.emc.com>
Date: Fri, 19 Aug 2011 12:28:04 -0400
In-Reply-To: <B1371F619AB0A94C9AC73CF2E475485B038C492CF3@MX11A.corp.emc.com> (gareth richards's message of "Fri, 19 Aug 2011 11:49:38 -0400")
Message-ID: <tsl8vqpxt63.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: simon@josefsson.org, ietf-krb-wg@lists.anl.gov, hartmans-ietf@mit.edu, ghudson@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 16:27:14 -0000

My take as an individual is that most of the people who have read the
draft and commented here read it the same way.  It's up to the AD to
decide if things are clear enough but I'm not pushing for any specific
change and would be happy if no change were made on this point.  I would
not push back against any clarity the AD or IESG request in this space.

From ole@cisco.com  Fri Aug 19 10:52:14 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481FA21F8834 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 10:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4w4MN95wqjn for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 10:52:13 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 6412721F87D9 for <ietf@ietf.org>; Fri, 19 Aug 2011 10:52:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=690; q=dns/txt; s=iport; t=1313776391; x=1314985991; h=date:from:reply-to:to:subject:message-id:mime-version; bh=t7dzx1oyAwopYVcI5Sltow5I1Qyz0HPBZ8dj3e0Zg3o=; b=bRNeSmhDDtLkHvEveo0w/SMlW2s5V2PiqTCnHvwojhLwVOlbnq73uahQ oq8j0rujRMBSC5WnoTt/Jbpc0FOs/XHE/dgt7HLzIiZTyHJAhmTJHFPuG odhdAE0kbTIBbKWB7FtypPSGjgMDtxivcbsyFDB1ejrzwXSK+fsnNil1h 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAECiTk6rRDoJ/2dsb2JhbAA/A6gNd4FZAQIBJIF9EyKHU5hzgSMBgyYPAY4UjSuDQYMHBIdgkD+Ea4ce
X-IronPort-AV: E=Sophos;i="4.68,251,1312156800"; d="scan'208";a="14763515"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-2.cisco.com with ESMTP; 19 Aug 2011 17:53:10 +0000
Received: from [10.21.73.5] ([10.21.73.5]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7JHrA9a011078 for <ietf@ietf.org>; Fri, 19 Aug 2011 17:53:10 GMT
Date: Fri, 19 Aug 2011 10:53:09 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: A "Must See" in Taipei
Message-ID: <alpine.OSX.2.01.1108191048420.3367@rabdullah.local>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 17:52:14 -0000

Our next meeting venue is located adjacent to Taipei 101, which was 
for a while the world's tallest building, see:

http://en.wikipedia.org/wiki/Taipei_101

When you are in Taipei, please make sure to go up to the observation 
floor and take a look at the 660 tonne tuned mass damper. You can
see it in action here during an earthquake:

http://www.youtube.com/watch?v=NYSgd1XSZXc

The observation floor has rather spectacular views of Taipei too!

Enjoy,

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


From sm@elandsys.com  Thu Aug 18 12:57:09 2011
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E41CE21F8AD1 for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 12:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.621
X-Spam-Level: 
X-Spam-Status: No, score=-102.621 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEczExqvMcof for <ietf@ietfa.amsl.com>; Thu, 18 Aug 2011 12:57:07 -0700 (PDT)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by ietfa.amsl.com (Postfix) with ESMTP id D0ACB21F8AD2 for <ietf@ietf.org>; Thu, 18 Aug 2011 12:57:07 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.234.114]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id p7IJvo1t003558; Thu, 18 Aug 2011 12:57:55 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1313697477; bh=K99qXyoT14oCSYr/ltxs2WwbVWo=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Df6cXgEaC7RNfwTOksZlffNRYYIrKAHWrUyCV9YOqIsn5UcRmxWguhcONBTrDQ0az beL3cIC468BnEhnyNAXzKI5GeYQg9hs6pQulOWG4CbwBRKv3J/5pM7DcmSER7/9vxG 2rWnoVhAkqjQbAvg+NrLnVCPgK4qN8u8zjnIS2w4=
Message-Id: <6.2.5.6.2.20110818092216.0b5b72a8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 18 Aug 2011 12:30:12 -0700
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [yam] Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
In-Reply-To: <4E4D2C5E.3000205@gmail.com>
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E4BEA77.4070606@gmail.com> <6.2.5.6.2.20110817232216.0b6efc50@resistor.net> <4E4D2C5E.3000205@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Fri, 19 Aug 2011 11:19:48 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2011 19:57:10 -0000

Hi Mykyta,
At 08:14 18-08-2011, Mykyta Yevstifeyev wrote:
>Neither RFC 2476 nor RFC 4409 asked IANA to make changes according 
>to the contents of these tables; but this draft does.  4409 and its 
>predecessor just mentioned which are eligible for use with submission.

I'll discuss this matter with the document editors at the end of the 
Last Call.  The working group will obviously be consulted about the 
matter.  I'll copy the message to you.

As a personal comment, it would be a bad idea for me to raise this as 
a serious concern.  The document editors would yell at me; the 
working group would petition the Area Director to fire me. :-)  In 
the IETF, everyone will tell that you have the right to view this as 
a serious concern.  What they won't tell you is that it is also a way 
to squander your goodwill.

Regards,
S. Moonesamy 


From mach.chen@huawei.com  Fri Aug 19 02:49:33 2011
Return-Path: <mach.chen@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA2FB21F89BA; Fri, 19 Aug 2011 02:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.109
X-Spam-Level: 
X-Spam-Status: No, score=-5.109 tagged_above=-999 required=5 tests=[AWL=1.490,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kfz4KGiHNMPA; Fri, 19 Aug 2011 02:49:32 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 85AB521F880C; Fri, 19 Aug 2011 02:49:32 -0700 (PDT)
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 <0LQ6001GU5ZVBK@szxga03-in.huawei.com>; Fri, 19 Aug 2011 17:50:19 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LQ600KX65ZIAW@szxga03-in.huawei.com>; Fri, 19 Aug 2011 17:50:19 +0800 (CST)
Received: from 172.24.2.119 (EHLO szxeml203-edg.china.huawei.com) ([172.24.2.119])	by szxrg02-dlp.huawei.com (MOS 4.1.9-GA FastPath queued) with ESMTP id ADH94227; Fri, 19 Aug 2011 17:50:18 +0800 (CST)
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 19 Aug 2011 17:50:05 +0800
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.30]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0270.001; Fri, 19 Aug 2011 17:50:13 +0800
Date: Fri, 19 Aug 2011 09:50:12 +0000
From: Mach Chen <mach.chen@huawei.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLS On-demand	Connectivity Verification and Route Tracing) to	Proposed Standard
In-reply-to: <20110811134542.25435.61281.idtracker@ietfa.amsl.com>
X-Originating-IP: [10.110.98.106]
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Message-id: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE207D35A25@SZXEML511-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLS On-demand	Connectivity Verification and Route Tracing) to	Proposed Standard
Thread-index: AQHMWC0XLpqRn09c6Uexe4DdaHqk3JUj9YJA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <20110811134542.25435.61281.idtracker@ietfa.amsl.com>
X-Mailman-Approved-At: Fri, 19 Aug 2011 11:19:48 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Nitin Bahadur <nitinb@juniper.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 09:49:33 -0000

Hi,

One question about the difference of the encapsulation modes between CV and Route Tracing.

In Section 3, there are three encapsulation modes for on-demand CV: "LSP-Ping with IP encapsulation", "On-demand CV with IP encapsulation, over ACH" and "Non-IP based On-demand CV, using ACH", but for On-demand Route Tracing (in section 4), there are only two modes: "On-demand LSP Route Tracing with IP encapsulation" and "Non-IP based On-demand LSP Route Tracing, using ACH". Seems that there should be "On-demand LSP Route Tracing with IP encapsulation, over ACH" accordingly. What's reason behind this? Or maybe I missed something.

Best regards,
Mach

> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: Thursday, August 11, 2011 9:46 PM
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLS
> On-demand Connectivity Verification and Route Tracing) to Proposed Standard
> 
> 
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'MPLS On-demand Connectivity Verification and Route Tracing'
>   <draft-ietf-mpls-tp-on-demand-cv-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
> ietf@ietf.org mailing lists by 2011-08-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
>    Label Switched Path Ping (LSP-Ping) is an existing and widely
>    deployed Operations, Administration and Maintenance (OAM) mechanism
>    for Multi-Protocol Label Switching (MPLS) Label Switched Paths
>    (LSPs).  This document describes extensions to LSP-Ping so that LSP-
>    Ping can be used for On-demand Connectivity Verification of MPLS
>    Transport Profile (MPLS-TP) LSPs and Pseudowires.  This document also
>    clarifies procedures to be used for processing the related OAM
>    packets.  Further, it describes procedures for using LSP-Ping to
>    perform Connectivity Verification and Route Tracing functions in
>    MPLS-TP networks.  Finally this document updates RFC 4379 by adding a
>    new address type and requesting an IANA registry.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From gareth.richards@rsa.com  Fri Aug 19 05:52:34 2011
Return-Path: <gareth.richards@rsa.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57C3D21F8AE1 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 05:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JGZQB09KN2B for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 05:52:33 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id BA88721F8A58 for <ietf@ietf.org>; Fri, 19 Aug 2011 05:52:33 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7JCrSNQ010740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Aug 2011 08:53:28 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 19 Aug 2011 08:53:23 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.221.56.110]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7JCrLNh016393; Fri, 19 Aug 2011 08:53:21 -0400
Received: from MX11A.corp.emc.com ([169.254.1.161]) by mxhub24.corp.emc.com ([128.221.56.110]) with mapi; Fri, 19 Aug 2011 08:53:21 -0400
From: <gareth.richards@rsa.com>
To: <hartmans-ietf@mit.edu>, <simon@josefsson.org>
Date: Fri, 19 Aug 2011 08:53:19 -0400
Subject: RE: AD review of draft-ietf-krb-wg-otp-preauth
Thread-Topic: AD review of draft-ietf-krb-wg-otp-preauth
Thread-Index: Acxd7akM0mainPM1TgqwXUNOWuFLZgAgFyaA
Message-ID: <B1371F619AB0A94C9AC73CF2E475485B038C492C53@MX11A.corp.emc.com>
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org> <tslaab62yxk.fsf@mit.edu>
In-Reply-To: <tslaab62yxk.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
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 19 Aug 2011 11:19:48 -0700
Cc: ietf-krb-wg@lists.anl.gov, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 12:52:34 -0000

>     >> Actually, I have a question about interoperability here.
>     >>
>     >> It's my assumption that a client of this specification needs to
>     >> implement basically all the options:
>     >>
>     >> * encrypted OTP values and values used for key derivation *
>     >> separate pins and pins that are together * at least 4 pass mode
>     >>
>     >> So that the server has flexibility to implement what its OTP
>     >> token requires.
>     >>
>     >> Are people assuming that it is acceptable to implement a client
>     >> that only implements the facilities needed by one particular OTP
>     >> token?
>
>     Simon> Yes, and I believe that is unavoidable -- there is no way to
>     Simon> properly test all features of any implementation without
>     Simon> having some OTP token that excercises each feature.
>
> OK.  That makes me very uncomfortable.  As an individual I'd prefer
> that
> this draft not be published without a mandatory-to-implement subset.
> My assumption was that the client needed to implement everything.
> If that's not globally held I think we have much more work to do.
>
> Please consider this an individual last call comment, not as a comment
> as a chair.

I had always thought the same way as Sam, that clients would be required to=
 implement all of the options since there appears to be no other way for th=
em to support different disconnected token types.  The specification was in=
tended to be token independent and the assumption was always that the clien=
ts would also be.

--Gareth

From ghudson@mit.edu  Fri Aug 19 07:10:27 2011
Return-Path: <ghudson@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C48C21F8ACA for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 07:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.034
X-Spam-Level: 
X-Spam-Status: No, score=-5.034 tagged_above=-999 required=5 tests=[AWL=-1.435, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhGQvfHUHvgZ for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 07:10:26 -0700 (PDT)
Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU [18.7.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 7925C21F8AF8 for <ietf@ietf.org>; Fri, 19 Aug 2011 07:10:26 -0700 (PDT)
X-AuditID: 12074424-b7bcaae000000a05-a4-4e4e6f32b517
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id D0.45.02565.23F6E4E4; Fri, 19 Aug 2011 10:12:02 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id p7JEBHdK007089;  Fri, 19 Aug 2011 10:11:17 -0400
Received: from [192.168.1.4] (pool-173-48-218-114.bstnma.fios.verizon.net [173.48.218.114]) (authenticated bits=0) (User authenticated as ghudson@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p7JEBA3c023150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Aug 2011 10:11:12 -0400 (EDT)
Subject: Re: [Ietf-krb-wg] AD review of draft-ietf-krb-wg-otp-preauth
From: Greg Hudson <ghudson@MIT.EDU>
To: "gareth.richards@rsa.com" <gareth.richards@rsa.com>
In-Reply-To: <B1371F619AB0A94C9AC73CF2E475485B038C492C53@MX11A.corp.emc.com>
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org> <tslaab62yxk.fsf@mit.edu> <B1371F619AB0A94C9AC73CF2E475485B038C492C53@MX11A.corp.emc.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 19 Aug 2011 10:11:10 -0400
Message-ID: <1313763070.16540.128.camel@t410>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCKsWRmVeSWpSXmKPExsUixCmqrGuU7+dn0LJI2GLVwVfsFl/bHrBZ vJ86jcni2cb5LBb3tlxid2D1WLLkJ5PHzDMX2T3mTpjC6HHy3VUWj5VTT7MHsEZx2aSk5mSW pRbp2yVwZTS0rmAquMRW8bvlOGsD40rWLkZODgkBE4nuac0sELaYxIV769lAbCGBfYwSK196 dzFyAdkbGCU27LzNAuHcY5K42zcRrFtYwFViT8cHMJtNQFni4NlvYJNEBMwlPrTdYgKxmQVu Mkq0zowHsTkFfCT23r3ABDGom0ni3f1FjBBFmhKt23+zdzFycLAIqErc7TcFCfMK6Erc/TSf BSTMKyAo8XeHMMSh0hKze/5BjZeX2P52DvMERsFZSAbNQuiYhaRqASPzKkbZlNwq3dzEzJzi 1GTd4uTEvLzUIl1zvdzMEr3UlNJNjKDAZ3dR2cHYfEjpEKMAB6MSD+8HDV8/IdbEsuLK3EOM khxMSqK8kdl+fkJ8SfkplRmJxRnxRaU5qcWHGCU4mJVEeFsjgHK8KYmVValF+TApaQ4WJXFe m50OfkIC6YklqdmpqQWpRTBZGQ4OJQnejDygRsGi1PTUirTMnBKENBMHJ8hwHqDhi0FqeIsL EnOLM9Mh8qcYFaXEeUtAEgIgiYzSPLheWGJ6xSgO9IowbypIFQ8wqcF1vwIazAQ0WGqXD8jg kkSElFQD45ztRXer/n8ojU00uqXp3Z0u8FF9u+hF6zq3OYU2QSd3eTDf3VdWfUp/57H9i9xW sFl1pTJ1dd56u0hzgeXxKbU1Px58KN4hXcp13tbmh9etXCfPZ25BSv/crjAvvcEiHcla0vqb V/zC05uV6xb91TQJ2bBd1ebK7HX3tppOl52UdIuPTUrgqRJLcUaioRZzUXEiAMRty+onAwAA
X-Mailman-Approved-At: Fri, 19 Aug 2011 11:19:48 -0700
Cc: "simon@josefsson.org" <simon@josefsson.org>, "ietf-krb-wg@lists.anl.gov" <ietf-krb-wg@lists.anl.gov>, "hartmans-ietf@MIT.EDU" <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 14:10:27 -0000

On Fri, 2011-08-19 at 08:53 -0400, gareth.richards@rsa.com wrote:
> I had always thought the same way as Sam, that clients would be
> required to implement all of the options since there appears to be no
> other way for them to support different disconnected token types.  The
> specification was intended to be token independent and the assumption
> was always that the clients would also be.

I agree, at least at the general level and for disconnected tokens.
(Does nextOTP make any sense for disconnected tokens?)

As for testing: you can unit-test client code using faked-up KDC
responses without a real token of the given type.  With only unit tests
there's always a risk that you will verify the wrong thing (i.e. not the
behavior you need to get a new token type working), but I think that
risk is acceptable in this case.



From gareth.richards@rsa.com  Fri Aug 19 08:49:00 2011
Return-Path: <gareth.richards@rsa.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B66C21F8AEC for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 08:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAaiYtnHObYx for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 08:48:59 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 82ABC21F8A36 for <ietf@ietf.org>; Fri, 19 Aug 2011 08:48:59 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7JFnsXL022468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Aug 2011 11:49:54 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 19 Aug 2011 11:49:42 -0400
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7JFne9M020740; Fri, 19 Aug 2011 11:49:41 -0400
Received: from MX11A.corp.emc.com ([169.254.1.161]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Fri, 19 Aug 2011 11:49:40 -0400
From: <gareth.richards@rsa.com>
To: <hartmans-ietf@mit.edu>, <ghudson@mit.edu>
Date: Fri, 19 Aug 2011 11:49:38 -0400
Subject: RE: [Ietf-krb-wg] AD review of draft-ietf-krb-wg-otp-preauth
Thread-Topic: [Ietf-krb-wg] AD review of draft-ietf-krb-wg-otp-preauth
Thread-Index: Acxefxb6FCM1JfjeSN2UJ+XdZIlH0AACE3AA
Message-ID: <B1371F619AB0A94C9AC73CF2E475485B038C492CF3@MX11A.corp.emc.com>
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org> <tslaab62yxk.fsf@mit.edu> <B1371F619AB0A94C9AC73CF2E475485B038C492C53@MX11A.corp.emc.com> <1313763070.16540.128.camel@t410> <tsl4o1dzcd2.fsf@mit.edu>
In-Reply-To: <tsl4o1dzcd2.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
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 19 Aug 2011 11:19:48 -0700
Cc: simon@josefsson.org, ietf-krb-wg@lists.anl.gov, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 15:49:00 -0000

>
> >>>>> "Greg" =3D=3D Greg Hudson <ghudson@MIT.EDU> writes:
> 87
>     Greg> On Fri, 2011-08-19 at 08:53 -0400, gareth.richards@rsa.com
> wrote:
>     >> I had always thought the same way as Sam, that clients would be
>     >> required to implement all of the options since there appears to
>     >> be no other way for them to support different disconnected token
>     >> types.  The specification was intended to be token independent
>     >> and the assumption was always that the clients would also be.
>
>     Greg> I agree, at least at the general level and for disconnected
>     Greg> tokens.  (Does nextOTP make any sense for disconnected
>     Greg> tokens?)
>
> I think you prompt the person to hit the next value button

Yes, that's the idea.  If the "nextOTP" flag is set then the client should =
prompt the user for the next value and use it in a second authentication re=
quest.

From hotz@jpl.nasa.gov  Fri Aug 19 10:21:29 2011
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A93D21F8B91 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 10:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Yg6e9c636Om for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 10:21:28 -0700 (PDT)
Received: from mail.jpl.nasa.gov (sentrion3.jpl.nasa.gov [128.149.139.109]) by ietfa.amsl.com (Postfix) with ESMTP id C2AB021F8B36 for <ietf@ietf.org>; Fri, 19 Aug 2011 10:21:28 -0700 (PDT)
Received: from dhcp-137-79-179-111.jpl.nasa.gov (dhcp-137-79-179-111.jpl.nasa.gov [137.79.179.111]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7JHMOL2007887 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Fri, 19 Aug 2011 10:22:24 -0700
Subject: Re: [Ietf-krb-wg] AD review of draft-ietf-krb-wg-otp-preauth
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <tsl4o1dzcd2.fsf@mit.edu>
Date: Fri, 19 Aug 2011 10:22:23 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <4AEC6A7F-0300-45B4-A284-731AC7699EBC@jpl.nasa.gov>
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org> <tslaab62yxk.fsf@mit.edu> <B1371F619AB0A94C9AC73CF2E475485B038C492C53@MX11A.corp.emc.com> <1313763070.16540.128.camel@t410> <tsl4o1dzcd2.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1084)
X-Source-IP: dhcp-137-79-179-111.jpl.nasa.gov [137.79.179.111]
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Fri, 19 Aug 2011 11:19:48 -0700
Cc: "simon@josefsson.org" <simon@josefsson.org>, "ietf-krb-wg@lists.anl.gov" <ietf-krb-wg@lists.anl.gov>, Greg Hudson <ghudson@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 17:21:29 -0000

On Aug 19, 2011, at 7:48 AM, Sam Hartman wrote:

>>>>>> "Greg" == Greg Hudson <ghudson@MIT.EDU> writes:
> 87
>    Greg> On Fri, 2011-08-19 at 08:53 -0400, gareth.richards@rsa.com wrote:
>>> I had always thought the same way as Sam, that clients would be
>>> required to implement all of the options since there appears to
>>> be no other way for them to support different disconnected token
>>> types.  The specification was intended to be token independent
>>> and the assumption was always that the clients would also be.
> 
>    Greg> I agree, at least at the general level and for disconnected
>    Greg> tokens.  (Does nextOTP make any sense for disconnected
>    Greg> tokens?)
> 
> I think you prompt the person to hit the next value button

Or else wait for the time to roll-over to the next.

------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu




From jmabdp@gmail.com  Fri Aug 19 11:33:50 2011
Return-Path: <jmabdp@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EF4B11E80A3; Fri, 19 Aug 2011 11:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.32
X-Spam-Level: 
X-Spam-Status: No, score=-3.32 tagged_above=-999 required=5 tests=[AWL=0.278,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UgeUubusG1Pq; Fri, 19 Aug 2011 11:33:49 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 70F2011E80A1; Fri, 19 Aug 2011 11:33:49 -0700 (PDT)
Received: by yxj17 with SMTP id 17so1239385yxj.31 for <multiple recipients>; Fri, 19 Aug 2011 11:34:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=iDgkaoFQwOxceOXos4NScG8uhr8bMtGXBK3GKGVTcqI=; b=fNlm/7MQq5swSvEsapNMuj0019iibP+vb7wgeuwrVpLLWRdCg5NXmauZ6NZD81iZ0v DYXov3rt6g2UE2JNrXjbVvKO8VPGuU0zEpgOXQRlIL/p8hbZdEbjeBWfMsUbw5wx9Yk3 Z7PgKCDuLUHkcW2IMFXisOU3Z6x3vfM19epyg=
MIME-Version: 1.0
Received: by 10.236.161.227 with SMTP id w63mr451207yhk.57.1313778883754; Fri, 19 Aug 2011 11:34:43 -0700 (PDT)
Received: by 10.236.30.34 with HTTP; Fri, 19 Aug 2011 11:34:43 -0700 (PDT)
Date: Fri, 19 Aug 2011 20:34:43 +0200
Message-ID: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com>
Subject: IDNA and Multilingual Internet issues and vocabulary after IDNA2008
From: jean-michel bernier de portzamparc <jmabdp@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf305e21dfadf9fa04aadffbcc
Cc: vip@icann.org, IDNA update work <idna-update@alvestrand.no>, internet users contributing group <iucg@ietf.org>, happiana@ietf.org, precis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 18:33:50 -0000

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

IDNA2008 has introduced the need for post IDNA2008 protocol and technology
adaptations in different areas. Several mailing lists are working on such
adaptations. There is a need they know the others' targets and they use the
same terminology with the same meaning.

To that end we have compiled charters and drafts, terminology definitions
and propositions from the different souces involved: IAB, IETF/WG/IDNA2008,
IETF/WG/PRECIS, ICANN/WG/VIP, UNICODE, IUCG, IUTF, ALFA, IANA and Unicode.
The file is http://iucg.org/wiki/IDNS_Common_Glossary.

At this stage we would like to continue compiling suggestions to add to this
document in order to have a comprehensive consolidation of ideas and terms.
Once inputs are stabilized, I will sort all the terms towards an update of
the IANA terminology file. I hope it could help reaching consensuses more
easily if we speak the same language.

Portzamparc

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

IDNA2008 has introduced the need for post IDNA2008 protocol and technology =
adaptations in different areas. Several mailing lists are working on such a=
daptations. There is a need they know the others&#39; targets and they use =
the same terminology with the same meaning.<br>
<br>To that end we have compiled charters and drafts, terminology definitio=
ns and propositions from the different souces involved: IAB, IETF/WG/IDNA20=
08, IETF/WG/PRECIS, ICANN/WG/VIP, UNICODE, IUCG, IUTF, ALFA, IANA and Unico=
de. The file is <a href=3D"http://iucg.org/wiki/IDNS_Common_Glossary">http:=
//iucg.org/wiki/IDNS_Common_Glossary</a>.<br>
<br>At this stage we would like to continue compiling suggestions to add to=
 this document in order to have a comprehensive consolidation of ideas and =
terms. Once inputs are stabilized, I will sort all the terms towards an upd=
ate of the IANA terminology file. I hope it could help reaching consensuses=
 more easily if we speak the same language. <br>
<br>Portzamparc<br><div style=3D"visibility: hidden; left: -5000px; positio=
n: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px=
; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; t=
ext-align: left; line-height: 130%;" id=3D"avg_ls_inline_popup">
</div>

--20cf305e21dfadf9fa04aadffbcc--

From moore@network-heretics.com  Fri Aug 19 13:36:22 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 722C911E80CD for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 13:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.142,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLVPZ4zQkfvE for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 13:36:21 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDC811E80C6 for <ietf@ietf.org>; Fri, 19 Aug 2011 13:36:21 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id D94BD20CBB for <ietf@ietf.org>; Fri, 19 Aug 2011 16:37:18 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 19 Aug 2011 16:37:18 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:message-id:references:to; s=smtpout; bh=JaZXJq rFYbbte8Kq+7F54Gfgd1M=; b=dPOwxSDe6tmGy+MC11WdfGqw6jiOQECWUui6aH h95JGKdHodRWHh+FxEo3Z6Yp+JqluC2v24UVysRIS5Dv8s5WXnz7Pm8lTkn50Ezj ueowJlj2NV4z+gLudIGtfOQ7g+MALT7GFkqiAsbCHqfcNfXLytPiqOYmqzGbtdOa yt5lc=
X-Sasl-enc: EgPwHHq8Ew3z0Fe7Pm77viqgA8dYLAN8QTHCafc0Ezbm 1313786237
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 602448E0125; Fri, 19 Aug 2011 16:37:17 -0400 (EDT)
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-29-471574055
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
Date: Fri, 19 Aug 2011 16:37:02 -0400
Message-Id: <F56ECE28-71C6-4AFC-B7C6-DDFFABFCFA61@network-heretics.com>
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 20:36:22 -0000

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

I support publication of some document like this one.  Suggestions for =
clarification to this document:

1. (section 2 in general) I think it's vague for this document to claim =
that it "updates" earlier documents as if it's changing the text of =
those documents.  The reader is left with only a vague impression of =
what is still in place from those documents and what has changed.

I suggest that the language in this draft be changed to first state each =
new or revised requirement, and then state how this changes =
recommendations/requirements stated in earlier documents.

2. section 2, page 4 reads:

   implementation details.  Rather, it is intended to ensure that those
   using RFC1812 as a guideline for IP implementations understand that
   IP nodes SHOULD NOT support IPv4 only, and that they should use the
   other informative references in this document as a companion
   guideline for proper IPv6 implementations.

suggest instead:

   implementation details.  Rather, it is intended to ensure that those
   using RFC1812 as a guideline for IP implementations understand that
   IP nodes SHOULD support IPv6 in addition to any support provided for=20=

   IPv4, and that they should use the other informative references in=20
   this document as a companion guideline for proper IPv6 =
implementations.
  =20
reason: to me "SHOULD NOT support IPv4 only" seems potentially =
confusing.

3.  section 2, page 5 reads:

   New IP implementations MUST support IPv6.

   Current IP implementations SHOULD support IPv6.

In general, it's meaningless to impose a requirement on current =
implementations of anything.  Also, it's not clear what is meant by "new =
implementations" - does this mean completely new implementations, or =
revisions of existing implementations?

Suggest that this be restated.  e.g.  "Host and router IP =
implementations MUST support IPv6; to support only IPv4 is =
insufficient."

4. also section 2, page 5:=20

   IPv6 support MUST be equivalent or better in quality and
   functionality when compared to IPv4 support in an IP
   implementation.

This statement could be taken too broadly, e.g. as applying to service =
offerings rather than just host and router implementations.  Suggest =
instead:

   Support for the IPv6 protocol in hosts and routers MUST=20
   be equivalent or better in quality and functionality when=20
   compared to IPv4 support in the same products.

Even then, this strikes me as problematic.  Should an implementation =
that cannot provide support for every IPv6 feature (perhaps because of =
inherent differences between IPv4 and IPv6, or because some feature =
hasn't yet been updated to support IPv6) be expected to remove features =
from its IPv4 stack so that its IPv6 stack is "equivalent or better"?=20

At the very least, I think the MUST should be a SHOULD.

Keith


--Apple-Mail-29-471574055
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
support publication of some document like this one. &nbsp;Suggestions =
for clarification to this document:<div><br></div><div>1. (section 2 in =
general) I think it's vague for this document to claim that it "updates" =
earlier documents as if it's changing the text&nbsp;of those documents. =
&nbsp;The reader is left with only a vague impression of what is still =
in place from those documents and what has =
changed.</div><div><br></div><div>I suggest that the language in this =
draft be changed to first state each new or revised requirement, and =
then state how this changes recommendations/requirements stated in =
earlier documents.</div><div><div><br></div><div>2. section 2, page 4 =
reads:</div><div><br></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: arial, helvetica, clean, sans-serif; font-size: =
13px; line-height: 16px; "><pre style=3D"font-family: monospace; =
line-height: 1.2em; margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">   implementation details.  Rather, it is =
intended to ensure that those
   using RFC1812 as a guideline for IP implementations understand that
   IP nodes SHOULD NOT support IPv4 only, and that they should use the
   other informative references in this document as a companion
   guideline for proper IPv6 =
implementations.</pre></span><div><br></div><div>suggest =
instead:</div><div><br></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: arial, helvetica, clean, sans-serif; font-size: =
13px; line-height: 16px; "><pre style=3D"font-family: monospace; =
line-height: 1.2em; margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">   implementation details.  Rather, it is =
intended to ensure that those
   using RFC1812 as a guideline for IP implementations understand that
   IP nodes SHOULD support IPv6 in addition to any support provided =
for&nbsp;</pre></span><span class=3D"Apple-style-span" =
style=3D"font-family: monospace; font-size: 13px; line-height: 15px; =
white-space: pre; ">   IPv4, and that they should use the other =
informative references in&nbsp;</span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; font-size: =
13px; line-height: 15px; white-space: pre; ">   this document =
</span><span class=3D"Apple-style-span" style=3D"font-family: arial, =
helvetica, clean, sans-serif; font-size: 13px; line-height: 16px; =
"></span><span class=3D"Apple-style-span" style=3D"font-family: =
monospace; font-size: 13px; line-height: 15px; white-space: pre; ">as a =
companion guideline for proper IPv6 implementations.</span><span =
class=3D"Apple-style-span" style=3D"font-size: 13px; line-height: 16px; =
"><pre style=3D"font-family: monospace; line-height: 1.2em; margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">   =
</pre><pre style=3D"line-height: 1.2em; margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><font =
class=3D"Apple-style-span" face=3D"Helvetica">reason: to me "SHOULD NOT =
support IPv4 only" seems potentially =
confusing.</font></pre></span><div><br></div></div><div>3. &nbsp;section =
2, page 5 reads:</div><div><br></div><div><span class=3D"Apple-style-span"=
 style=3D"font-family: arial, helvetica, clean, sans-serif; font-size: =
13px; line-height: 16px; "><pre style=3D"font-family: monospace; =
line-height: 1.2em; margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">   New IP implementations MUST support IPv6.
</pre><div><br></div></span></div><div><span class=3D"Apple-style-span" =
style=3D"font-size: 13px; line-height: 16px; "><pre style=3D"font-family: =
monospace; line-height: 1.2em; margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">   Current IP implementations =
SHOULD support IPv6.
</pre></span><div><br></div>In general, it's meaningless to impose a =
requirement on current implementations of anything. &nbsp;Also, it's not =
clear what is meant by "new implementations" - does this mean completely =
new implementations, or revisions of existing =
implementations?</div><div><br></div><div>Suggest that this be restated. =
&nbsp;e.g. &nbsp;"Host and router IP implementations MUST support IPv6; =
to support only IPv4 is insufficient."</div><div><br></div><div>4. also =
section 2, page 5:&nbsp;</div><div><br></div><div><span =
class=3D"Apple-style-span" style=3D"font-size: 13px; line-height: 16px; =
"><pre style=3D"font-family: monospace; line-height: 1.2em; margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">   IPv6 =
support MUST be equivalent or better in quality and
   functionality when compared to IPv4 support in an IP</pre><pre =
style=3D"font-family: monospace; line-height: 1.2em; margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">   =
implementation.
</pre><pre style=3D"font-family: monospace; line-height: 1.2em; =
margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: =
0px; "><br></pre></span><span class=3D"Apple-style-span" =
style=3D"font-size: 13px; line-height: 15px; white-space: pre;">This =
statement could be taken too broadly,</span>&nbsp;e.g. as applying to =
service offerings rather than just host and router implementations. =
&nbsp;Suggest instead:</div><div><br></div><div><span =
class=3D"Apple-style-span" style=3D"font-size: 13px; line-height: 16px; =
"><pre style=3D"font-family: monospace; line-height: 1.2em; margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">   =
Support for the IPv6 protocol in hosts and routers MUST&nbsp;</pre><pre =
style=3D"font-family: monospace; line-height: 1.2em; margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">   be =
equivalent or better in quality and functionality =
when&nbsp;</pre></span><span class=3D"Apple-style-span" =
style=3D"font-size: 13px; line-height: 16px; "><pre style=3D"font-family: =
monospace; line-height: 1.2em; margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">   compared to IPv4 support in =
the same products.</pre></span><span class=3D"Apple-style-span" =
style=3D"font-size: 13px; line-height: 16px; =
"><div><br></div></span><span class=3D"Apple-style-span" =
style=3D"font-size: 13px; line-height: 16px; "><pre style=3D"line-height: =
1.2em; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica">Even then, this strikes me as problematic.  Should an =
implementation that cannot provide support for every IPv6 feature =
(perhaps because of inherent differences between IPv4 and IPv6, or =
because some feature hasn't yet been updated to support IPv6) be =
expected to remove features from its IPv4 stack so that its IPv6 stack =
is "equivalent or better"? </font></pre><pre style=3D"line-height: =
1.2em; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica"><br></font></pre><pre style=3D"line-height: 1.2em; =
margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: =
0px; "><font class=3D"Apple-style-span" face=3D"Helvetica">At the very =
least, I think the MUST should be a SHOULD.</font></pre><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica"><br></font></pre><pre style=3D"line-height: 1.2em; =
margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: =
0px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica">Keith</font></pre><pre style=3D"line-height: 1.2em; =
margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: =
0px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica"><br></font></pre></span></div></div></div></body></html=
>=

--Apple-Mail-29-471574055--

From john-ietf@jck.com  Fri Aug 19 13:37:30 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7BD411E80D5; Fri, 19 Aug 2011 13:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AmnfPlVO22jr; Fri, 19 Aug 2011 13:37:30 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id EDE2E11E80C6; Fri, 19 Aug 2011 13:37:29 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QuVpf-000NLX-Dj; Fri, 19 Aug 2011 16:38:23 -0400
X-Vipre-Scanned: 0061E3E00027E30061E52D-TDI
Date: Fri, 19 Aug 2011 16:38:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: jean-michel bernier de portzamparc <jmabdp@gmail.com>
Subject: Re: IDNA and Multilingual Internet issues and vocabulary after IDNA2008
Message-ID: <86E32E259DD17E1166516052@localhost>
In-Reply-To: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com>
References: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.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@ietf.org>, precis@ietf.org, happiana@ietf.org, IDNA update work <idna-update@alvestrand.no>, internet users contributing group <iucg@ietf.org>, vip@icann.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 20:37:31 -0000

--On Friday, August 19, 2011 20:34 +0200 jean-michel bernier de
portzamparc <jmabdp@gmail.com> wrote:

> IDNA2008 has introduced the need for post IDNA2008 protocol
> and technology adaptations in different areas. Several mailing
> lists are working on such adaptations. There is a need they
> know the others' targets and they use the same terminology
> with the same meaning.
 
> To that end we have compiled charters and drafts, terminology
> definitions and propositions from the different souces
> involved: IAB, IETF/WG/IDNA2008, IETF/WG/PRECIS, ICANN/WG/VIP,
> UNICODE, IUCG, IUTF, ALFA, IANA and Unicode. The file is
> http://iucg.org/wiki/IDNS_Common_Glossary.
>...

I'm sorry, but I've had enough of this.

I hesitate to admit that I have read far enough into that
document to have noticed, lest by doing so I add credibility to
it.  However, I observed that it contains rather large blocks of
text excerpted from other materials without any specific
attribution or acknowledgment.  Those materials include several
RFCs and draft-ietf-appsawg-rfc3536bis.  I am an author or major
contributor on several of those.  Especially since I had asked
earlier that any compendium of this sort list terms covered in
other documents, comment on them as you thought appropriate, but
incorporate the definitions themselves only by reference, this
appears to be a willful and deliberate violation of copyrights
held by the IETF Trust and of my copyrights.  The published IETF
Trust terms require explicit licenses for this type of reuse of
non-code elements of RFCs; these definitions are not code.
Those rules either apply to I-Ds as well or you need permission
from the I-D authors for non-IETF uses.  I, at least, have not
given that permission.  I believe the material on your web page
also infringes the copyrights of others, but they will have to
speak for themselves.

The Trustees of the IETF Trust and other rights-holders will
need to speak for themselves but, at least for materials in
which I have rights under relevant copyright law, please
consider this a request to take the document down and to do so
immediately.

I also request that you supply addresses for IUCG, IUTF, ALFA,
and for yourself and any other individuals or organizations that
are included by reference in your use of "we" in the statement
"To that end we have compiled..." so that copyright holders who
believe that the document infringes their rights can have legal
documents delivered and served should they so desire.

Thank you.
   John Klensin

p.s. if this note falls into the hands of any attorneys with
appropriate credentials to practice intellectual property law in
France who would be interested in pursuing an action in this
matter for a portion of any proceeds (the balance to go to
charity) should contact me.



From ron.even.tlv@gmail.com  Fri Aug 19 14:20:25 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 373C621F8BA7; Fri, 19 Aug 2011 14:20:25 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-fAr4-v8LoU; Fri, 19 Aug 2011 14:20:24 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B989D21F8BA6; Fri, 19 Aug 2011 14:20:23 -0700 (PDT)
Received: by wyg8 with SMTP id 8so2811067wyg.31 for <multiple recipients>; Fri, 19 Aug 2011 14:21:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:content-language:thread-index; bh=JoxAWJmO5z3NTMtrSmwhVI/JbvM8PSevJ3xg6+7xhWI=; b=wsLUWcSpTJs+Z32opsDqnAInGVA1yxngriYDJpAkoUTTVkOI6ja5V4XOWg2XAwchNN 8HIuuIBPyS1eCt3RsE7HybOZGQGsPPW4I2wRX0/qM8hh0EV5wBe5G/YfjpVu6uVT0JHX zCnVA4/Or6E4jmsPaz+F+fiapkSrBldGujqSI=
Received: by 10.216.177.212 with SMTP id d62mr138115wem.51.1313788880797; Fri, 19 Aug 2011 14:21:20 -0700 (PDT)
Received: from windows8d787f9 ([109.65.33.161]) by mx.google.com with ESMTPS id a43sm2429303wed.4.2011.08.19.14.21.16 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 19 Aug 2011 14:21:19 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-grow-geomrt.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-grow-geomrt-05
Date: Sat, 20 Aug 2011 00:20:50 +0300
Message-ID: <4e4ed3cf.c13fd80a.7e84.ffffa326@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AB_01CC5ECF.07888350"
X-Mailer: Microsoft Office Outlook 12.0
Content-language: en-us
Thread-index: AcwD6wbOwmqW7fASSRiM+pToVKF8Pg==
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 21:20:25 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00AB_01CC5ECF.07888350
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

 

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

 

Document: draft-ietf-grow-geomrt-05

Reviewer: Roni Even

Review Date:2011-8-20

IETF LC End Date: 2011-8-26

IESG Telechat date: 2011-8-25

 

Summary: This draft is ready for publication as a standard track RFC.

 

Major issues:

 

 

Minor issues:

 

 

 

Nits/editorial comments:

 

1.       Section 5 "This section is to aide" should be "aid"

2.       Section 6 "does not support the the" delete the second "the"

 

 

 

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.h11
	{mso-style-name:h11;
	font-family:"Courier New";
	font-weight:bold;}
.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:901602645;
	mso-list-type:hybrid;
	mso-list-template-ids:986983972 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1090463919;
	mso-list-type:hybrid;
	mso-list-template-ids:-1044579784 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-ietf-grow-geomrt-05<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2011&#8211;8&#8211;20<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2011&#8211;8&#8211;26<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2011-8-25<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as a standard track =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section 5 =
&quot;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>This =
section is to aide&quot; should be &quot;aid&quot;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section 6 =
&quot;does not support the the&quot; delete the second =
&quot;the&quot;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00AB_01CC5ECF.07888350--


From peter@denic.de  Fri Aug 19 14:29:12 2011
Return-Path: <peter@denic.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695C921F8BC4 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 14:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srEN7BXLe6Gk for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 14:29:11 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id 40F5721F8BC3 for <ietf@ietf.org>; Fri, 19 Aug 2011 14:29:11 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QuWdh-0002uu-Un; Fri, 19 Aug 2011 23:30:05 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QuWdh-0000Ng-QD; Fri, 19 Aug 2011 23:30:05 +0200
Date: Fri, 19 Aug 2011 23:30:05 +0200
From: Peter Koch <pk@ISOC.DE>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
Message-ID: <20110819213005.GD25053@x27.adm.denic.de>
References: <20110819161025.15887.78808.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110819161025.15887.78808.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 21:29:12 -0000

On Fri, Aug 19, 2011 at 09:10:25AM -0700, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IANA Reserved IPv4 Prefix for Shared Transition Space'
>   <draft-weil-shared-transition-space-request-03.txt> as an Informational
> RFC

I am a bit confused about the exact purpose of this last call and would appreciate
some guidance by the IESG and/or IAB how to read this in context.
It appears the draft is meant to gauge consensus as per the communication
archived at
<http://www.iab.org/documents/correspondence-reports-documents/2011-2/response-to-arins-request-for-guidance-regarding-draft-policy-arin-2011-5/>.

However, all the content and discussion is essentially deferred to
draft-bdgks-arin-shared-transition-space-01.txt, which has a status of "I-D Exists",
is not subject to this Last Call and is, to my surprise, an Informative Reference
in the draft under consideration.

content/nits:

o draft-bdgks-arin-shared-transition-space-01.txt would have to be elevated 
  to a normative reference, with all consequences

o the document should have operational considerations as in RFC 1918,
  regarding the leakage of addresses in IP headers and elsewhere (cf. "AS112")

o the document does not discuss the risk of the new address space being
  absorbed as a simple addition to RFC1918 space

o the Security considerations are non existent, especially given the
  long experience with actual and perceived threats connected to RFC 1918
  address space

o the document would have to change its perspective to as if the address
  range had already been assigned (no more "proposes" language).

o the document ought to expand used acronyms and add references to IETF
  or other documents, e.g., for CGN, CPE, and other terms

o without any judgement re: the "B", this document should aim at BCP status
  since it would have to give (more detailed) instructions what and what
  not to do with the assigned/allocated address.

o RFC 2119 would have to be elevated to a normative reference

o add reference to RFC 6319

Quite frankly, without taking any position on the actual proposal, these
bullet items suggest the draft is not ready for publication.

-Peter

From sm@resistor.net  Fri Aug 19 14:41:06 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D1411E80D3 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 14:41:06 -0700 (PDT)
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.285, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i3MaB8dPY7yn for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 14:41:04 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D2CED11E80B9 for <ietf@ietf.org>; Fri, 19 Aug 2011 14:41:04 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7JLftcT016264 for <ietf@ietf.org>; Fri, 19 Aug 2011 14:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1313790121; bh=wp0sI6xgQsciSvGk1kvjaXqfWoZZwr7vJDGGQOwPlsA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=IKMtRlKcYMBIUMxNyu9R4exmjfvCu+XcCqRwU0v/v1YX8jGNka9S9dFDUTmUkm/0Q Gc3icw89Hxj2n8P7TMbhmVuIahrIGhMUqzFJ+rwpwakRQCsmj+CsSz8xF+HtEHmzjw kczayQYoQSuQ5wYTC0Q3WTkkCZ8c9z6swVGAu3zM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1313790121; bh=wp0sI6xgQsciSvGk1kvjaXqfWoZZwr7vJDGGQOwPlsA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=3HmM02lBAH6ZDuwnJCWkw1s73PmzKK3d+k0yGzNXSq6z+NGVdyIG4vQnmlydY+I4S KH00l7eOz8HLCEOH2bmyjkvf8Hgv+3oMkQNk3T7+WmrbIXoxXDo6CwSz+IoCIn7+/f kKMRsKGz+BQ2IxpGlyWSNdIH7unoeP8Gs1Ioly0s=
Message-Id: <6.2.5.6.2.20110819111507.09a77b18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 19 Aug 2011 14:42:07 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
In-Reply-To: <20110819161025.15887.78808.idtracker@ietfa.amsl.com>
References: <20110819161025.15887.78808.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 21:41:06 -0000

At 09:10 19-08-2011, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IANA Reserved IPv4 Prefix for Shared Transition Space'
>   <draft-weil-shared-transition-space-request-03.txt> as an Informational
>RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2011-09-16. Exceptionally, comments may be

Making such an allocation through a document which is not intended 
for the Standards Track is highly unusual.  Last year I raised a 
concern in a non-IETF mailing list about making IPv4 allocations 
using "RFC required" as there will be more economic pressure for 
process end-run as the world gets to the odds and ends of IPv4 
addresses.  I don't see any text that fits under protocol assignment 
(see RFC 2860) in draft-weil-shared-transition-space-request-03.  In 
fact, the Security Considerations section mentions that the "memo 
does not define any protocol".

The draft only mentions an applicability and justification for Shared 
Transition Space and references 
draft-bdgks-arin-shared-transition-space-00.  While the policy fits 
under RIR community processes, it does not fit under allocations made 
for technical specifications.  Publishing this document on the 
grounds that the ARIN wants it is not a good enough reason.  Will 
ARIN be "donating" the /10 IPv4 address space to IANA for it to make 
this allocation?

The draft mentions that:

   "Network equipment manufacturers MUST NOT use the
    assigned block in default or example device configurations."

As the IPv4 address block is not specified in the document, the above 
requirement cannot be followed.  The expectation that the IPv4 
address block will only be used by Infrastructure Providers is 
optimistic.  RFC 5735 covers Special Use IPv4 Addresses.  This 
document should update the BCP.

A proposal similar to this one was discussed in a V6OPS meeting in 
Asia.  If my reading is correct, it did not gain consensus.  The 
proposal gets discussed in North America in
OPSAWG and it gains consensus.  BTW, this draft contains only 220 
lines, including boilerplate and it has five authors.

Regards,
-sm 


From hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com  Fri Aug 19 15:23:19 2011
Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C224F21F8B90 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 15:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.76
X-Spam-Level: 
X-Spam-Status: No, score=-102.76 tagged_above=-999 required=5 tests=[AWL=0.339, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MFi7Q0Z67nam for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 15:23:19 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5071021F8B88 for <ietf@ietf.org>; Fri, 19 Aug 2011 15:23:19 -0700 (PDT)
Received: by pzk33 with SMTP id 33so9238705pzk.18 for <ietf@ietf.org>; Fri, 19 Aug 2011 15:24:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WbZiunRKvtQ4fcGLgn25Zc+8maVW2gQI92Nw5fH0eKk=; b=Ic5zMG5faBYDpkI/8x439IaDarzoGEa3BOwx1wGj9TDk1+LIE2EiHLqNnPaW4Krk5V BT9yAqzpUXtzI3s4SoiiNY2qJghOH9krAmJ0Ttwgvo4fCsYxndxGr73wpSiaDAy5OVrK lACH6nDmar81DsqaPgx+QOG6Bh94Uc35rD0aI=
Received: by 10.143.60.19 with SMTP id n19mr130627wfk.241.1313792657136; Fri, 19 Aug 2011 15:24:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.98.5 with HTTP; Fri, 19 Aug 2011 15:23:57 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20110819111507.09a77b18@resistor.net>
References: <20110819161025.15887.78808.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110819111507.09a77b18@resistor.net>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Sat, 20 Aug 2011 00:23:57 +0200
Message-ID: <CAHhFybrJ__eYyso81Y93mgpGBfXQXpHMSC-kFWfTvdxfvgvLJg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 22:23:19 -0000

On 19 August 2011 23:42, SM wrote:

> RFC 5735 covers Special Use IPv4 Addresses.

BTW, some days ago the "errata system" informed me that a rather old
nit about class E in RFC 3330 made it to "held for document update",
but I think RFC 5735 already did that, cf. RFC 3330 eid 1436.

The I-D discussed here mainly consists of an informative reference
to another I-D.bdgks-arin-shared-transition-space-01, and the latter
mentions class E in section 2.2.3.

Is nobody going to use these 268,435,455 "free" IPs waiting for IETF
experiments?

-Frank

From brian.e.carpenter@gmail.com  Fri Aug 19 16:05:23 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96D7411E8087 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 16:05:23 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTUljAkSeOtV for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 16:05:23 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id D687511E8082 for <ietf@ietf.org>; Fri, 19 Aug 2011 16:05:22 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2448492fxe.31 for <ietf@ietf.org>; Fri, 19 Aug 2011 16:06:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wXsqT6I4k7+tMPAb4FAFkqppBwMXfAErbVYr4GTSEfE=; b=KTN1P1zOq53tCbZzH0IcrAFSUmV0rDSw6S8mnWaPIM0M007QXT9eXeruV1sxK3gxOJ 3EQKPZy9gKZMPRagPXSGztUTa9wtayIXMinEqXJ4II8ZaWr8uk9oYthyjnSSWznNm5aO D457NXfRqwtnjd1QnG5eR/m6Y9eTd9bwDT9uQ=
Received: by 10.223.99.91 with SMTP id t27mr369912fan.56.1313795178011; Fri, 19 Aug 2011 16:06:18 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id b14sm2924731fab.43.2011.08.19.16.06.14 (version=SSLv3 cipher=OTHER); Fri, 19 Aug 2011 16:06:17 -0700 (PDT)
Message-ID: <4E4EEC56.2010705@gmail.com>
Date: Sat, 20 Aug 2011 11:05:58 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
References: <20110819161025.15887.78808.idtracker@ietfa.amsl.com> <20110819213005.GD25053@x27.adm.denic.de>
In-Reply-To: <20110819213005.GD25053@x27.adm.denic.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Peter Koch <pk@ISOC.DE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 23:05:23 -0000

On 2011-08-20 09:30, Peter Koch wrote:
...
> o draft-bdgks-arin-shared-transition-space-01.txt would have to be elevated 
>   to a normative reference, with all consequences

I don't think this is really required; it is after all an
explanatory document. However, I do think that *if* draft-weil-
is to be published, draft-bdgks needs to be published
simultaneously. Therefore, I think that synchronised Last Calls
are needed.

I have previously argued against draft-weil on the OPSAWG list
and lost, so I will not repeat that argument here. However, if
it is to proceed, then some of my WGLC comments have not yet
been fixed:

>> At the very minimum, if draft-weil is to proceed, it should describe the
>> phase-out plan for the proposed prefix (i.e. the phase-out plan for CGN
>> deployment). One approach to that is documented in RFC 6264.

The authors didn't agree with that comment, but since this is
essentially an operational matter, I think they are wrong. If
the IETF sticks its nose into RIR matters in this way (as the
IAB has concluded that we should*), then we should do a complete
job.

>> It is strange that draft-weil doesn't reference RFC 6319 and RFC 6269.

In other words, draft-weil doesn't recognise the
counter-arguments. That seems wrong to me.

   Brian Carpenter

*
http://www.iab.org/documents/correspondence-reports-documents/2011-2/response-to-arins-request-for-guidance-regarding-draft-policy-arin-2011-5/

From brian.e.carpenter@gmail.com  Fri Aug 19 16:14:36 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3045221F8B3D; Fri, 19 Aug 2011 16:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.593
X-Spam-Level: 
X-Spam-Status: No, score=-103.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDUI1SL4v8mF; Fri, 19 Aug 2011 16:14:35 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 459AA21F8B2D; Fri, 19 Aug 2011 16:14:35 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2451482fxe.31 for <multiple recipients>; Fri, 19 Aug 2011 16:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=eWAWsUL7qjefJDbMfj+WATTKqv5S/19Rimk0vmLXXf4=; b=CdueHvFMQCpEovvQCibJ/naB4TlYaOeAv6UptNLDLyU0pltMA13sESEdUzfOJd32dP RfL/JRGi34OAD+/JLezxu6a7Es99QZmPFVTPb02ckmBu1aAm2nYmeUevG5SOajdstgul fJPUYWe7jBPtqgFZc1s1Hr3G7v8/366n0b0t8=
Received: by 10.223.61.211 with SMTP id u19mr363326fah.102.1313795732624; Fri, 19 Aug 2011 16:15:32 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id e5sm2004430fah.11.2011.08.19.16.15.29 (version=SSLv3 cipher=OTHER); Fri, 19 Aug 2011 16:15:31 -0700 (PDT)
Message-ID: <4E4EEE8C.6050102@gmail.com>
Date: Sat, 20 Aug 2011 11:15:24 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
In-Reply-To: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: int-area@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 23:14:36 -0000

I fully support this document. It could be tuned in the way
Keith suggested, but basically it is a Good Thing.

Regards
   Brian Carpenter

From jmabdp@gmail.com  Fri Aug 19 16:29:37 2011
Return-Path: <jmabdp@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B86E621F8BB5; Fri, 19 Aug 2011 16:29:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.39
X-Spam-Level: 
X-Spam-Status: No, score=-3.39 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AOppMIyQVDKQ; Fri, 19 Aug 2011 16:29:36 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD7F21F8BB3; Fri, 19 Aug 2011 16:29:36 -0700 (PDT)
Received: by gxk19 with SMTP id 19so2969607gxk.31 for <multiple recipients>; Fri, 19 Aug 2011 16:30:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bDtZ87gCGU5Ld0SX4Z51Vhzy4vLLw+qH27l4v4RpR5M=; b=Le5uOTPgLV57apMcuTvk+07U/tCLIpcA65kpEzyi0rZE4J+dLUGgIwhLIxgzUgFLIT 5VJFSCEsdhU/t5DqadVlDXuTY0FLwLNX/uhfLpOtGCGLj2nULohiJ1zZG1+TA0WLIGvt XvrUieV8j5nYz2pI0L96BsAZIMXqI44gOZW4U=
MIME-Version: 1.0
Received: by 10.236.195.73 with SMTP id o49mr2317287yhn.23.1313796633300; Fri, 19 Aug 2011 16:30:33 -0700 (PDT)
Received: by 10.236.30.34 with HTTP; Fri, 19 Aug 2011 16:30:33 -0700 (PDT)
In-Reply-To: <86E32E259DD17E1166516052@localhost>
References: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com> <86E32E259DD17E1166516052@localhost>
Date: Sat, 20 Aug 2011 01:30:33 +0200
Message-ID: <CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com>
Subject: Re: IDNA and Multilingual Internet issues and vocabulary after IDNA2008
From: jean-michel bernier de portzamparc <jmabdp@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=20cf305e2505a28e5704aae41d70
Cc: IETF <ietf@ietf.org>, precis@ietf.org, happiana@ietf.org, IDNA update work <idna-update@alvestrand.no>, internet users contributing group <iucg@ietf.org>, vip@icann.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 23:29:37 -0000

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

Dear Mr. Klensin,

"we" are Internet and IETF users. This makes a pretty large community. There
are three ways one can do it:

- in surviving with what we (do not) get. Very large part of our community.
- in hacking the internet from the outside on behalf of our right to protect
ourselves from digital ecosystem pollution risks. Small part of our
community.
- in trying to cooperate with you guys and help your inside work with our
outside perspective. Microscopic part of our community. Guess why? Please
read the begining of your mail.

We do it because Jefsey convinced a few of us and the IETF Chair that it had
to be tried. However, if the inside Internet is made of individual's and
ISOC's copyrights and cannot even be discussed and helped, Jefsey will soon
be alone!

Please respond: the ball is your field. Tell me: are we wrong trying to work
in the open, liaise with the IETF and carry a lot of work to be able to
answer you, the happiana, the PRECIS, the VIP people in a consistant way,
also with other open works?


This being said you perfectly know that this

2011/8/19 John C Klensin <john-ietf@jck.com>

> without any specific
> attribution or acknowledgment.  Those materials include several
> RFCs and draft-ietf-appsawg-rfc3536bis.


is wrong. Your name, your RFCs etc. are quoted as such. We do not publish,
we try to draft a pertinent mail to you!


> I am an author or major
> contributor on several of those.  Especially since I had asked
> earlier that any compendium of this sort list terms covered in
> other documents, comment on them as you thought appropriate,


This is correct. But to respond to you, a lot of work must be carried.
Beginning with an enlarged scope to other intricate real needs you did not
consider yet.

Portzamparc

BTW I am not French, I am Breton!

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

Dear Mr. Klensin,<br><br>&quot;we&quot; are Internet and IETF users. This m=
akes a pretty large community. There are three ways one can do it:<br><br>-=
 in surviving with what we (do not) get. Very large part of our community.<=
br>
- in hacking the internet from the outside on behalf of our right to protec=
t ourselves from digital ecosystem pollution risks. Small part of our commu=
nity.<br>- in trying to cooperate with you guys and help your inside work w=
ith our outside perspective. Microscopic part of our community. Guess why? =
Please read the begining of your mail. <br>
<br>We do it because Jefsey convinced a few of us and the IETF Chair that i=
t had to be tried. However, if the inside Internet is made of individual&#3=
9;s and ISOC&#39;s copyrights and cannot even be discussed and helped, Jefs=
ey will soon be alone!<br>
<br>Please respond: the ball is your field. Tell me: are we wrong trying to=
 work in the open, liaise with the IETF and carry a lot of work to be able =
to answer you, the happiana, the PRECIS, the VIP people in a consistant way=
, also with other open works? <br>
<br><br>This being said you perfectly know that this<br><br><div class=3D"g=
mail_quote">2011/8/19 John C Klensin <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:john-ietf@jck.com">john-ietf@jck.com</a>&gt;</span><br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
without any specific<br>
attribution or acknowledgment. =A0Those materials include several<br>
RFCs and draft-ietf-appsawg-rfc3536bis. =A0</blockquote><div><br>is wrong. =
Your name, your RFCs etc. are quoted as such. We do not publish, we try to =
draft a pertinent mail to you!<br>=A0<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 2=
04, 204); padding-left: 1ex;">
I am an author or major<br>
contributor on several of those. =A0Especially since I had asked<br>
earlier that any compendium of this sort list terms covered in<br>
other documents, comment on them as you thought appropriate, </blockquote><=
div><br>This is correct. But to respond to you, a lot of work must be carri=
ed. <br>Beginning with an enlarged scope to other intricate real needs you =
did not consider yet.<br>
</div><br><div>Portzamparc<br><br>BTW I am not French, I am Breton!<br><br>=
<br><br><br><br><br></div></div><br><div style=3D"visibility: hidden; left:=
 -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px=
; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; f=
ont-size: 10px; text-align: left; line-height: 130%;" id=3D"avg_ls_inline_p=
opup">
</div>

--20cf305e2505a28e5704aae41d70--

From mfberny@gmail.com  Fri Aug 19 17:20:43 2011
Return-Path: <mfberny@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D58D821F8B21; Fri, 19 Aug 2011 17:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m3tKNboOaOnS; Fri, 19 Aug 2011 17:20:42 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8DCF321F8745; Fri, 19 Aug 2011 17:20:42 -0700 (PDT)
Received: by yie12 with SMTP id 12so2989493yie.31 for <multiple recipients>; Fri, 19 Aug 2011 17:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SSrJxSjUJSjWqKO0GuXt75BvOAQ/rTt0k70PZsJ5Mcc=; b=N/ekk7QVkR8oDapgT0n7Yn0cUwfG1I7IaWo7oTj4E4H3INGClgvWj95hAQP8uhH6wQ yG8rUU8cgSfT1JibucWSQsAKVPTr8Mn9KqP6Dz84yk7tRr8BKgw/VKCYcXefodGCXeMf SJcqKlUghKUN0qewlkCmxZmSEq/079Gzf+ha0=
MIME-Version: 1.0
Received: by 10.236.154.199 with SMTP id h47mr2317008yhk.81.1313799699543; Fri, 19 Aug 2011 17:21:39 -0700 (PDT)
Received: by 10.236.138.164 with HTTP; Fri, 19 Aug 2011 17:21:39 -0700 (PDT)
In-Reply-To: <CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com>
References: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com> <86E32E259DD17E1166516052@localhost> <CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com>
Date: Sat, 20 Aug 2011 02:21:39 +0200
Message-ID: <CAL-6tfUgmHp8TRqTTTB8M8GV0zhJQ60G2O+4ug8yMitqphcBkQ@mail.gmail.com>
Subject: Re: [iucg] IDNA and Multilingual Internet issues and vocabulary after IDNA2008
From: Marie-France Berny <mfberny@gmail.com>
To: internet users contributing group <iucg@ietf.org>
Content-Type: multipart/alternative; boundary=20cf303f6c8a65b54804aae4d4a7
Cc: IETF <ietf@ietf.org>, happiana@ietf.org, precis@ietf.org, IDNA update work <idna-update@alvestrand.no>, John C Klensin <john-ietf@jck.com>, vip@icann.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Aug 2011 00:20:44 -0000

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

Hi! John,
This seems to be a pretty odd point of yours!  As if every IETF mail had to
list the copyrights of every text or concept it works on or with.

We only are interested in an adequate and coherent multilinguistic
terminology at the IANA. At the end of the day if you want to publish it
under your name you welcome.

I introduced what I hope will close this: WIKI RFC 3271 with an appropriate
comment.

http://idna2010.org
The text John Klensin refers to is the working wiki page:

 *IDNS Common Glossary <http://iucg.org/wiki/IDNS_Common_Glossary>*


 Marie-France

2011/8/20 jean-michel bernier de portzamparc <jmabdp@gmail.com>

> Dear Mr. Klensin,
>
> "we" are Internet and IETF users. This makes a pretty large community.
> There are three ways one can do it:
>
> - in surviving with what we (do not) get. Very large part of our community.
> - in hacking the internet from the outside on behalf of our right to
> protect ourselves from digital ecosystem pollution risks. Small part of our
> community.
> - in trying to cooperate with you guys and help your inside work with our
> outside perspective. Microscopic part of our community. Guess why? Please
> read the begining of your mail.
>
> We do it because Jefsey convinced a few of us and the IETF Chair that it
> had to be tried. However, if the inside Internet is made of individual's and
> ISOC's copyrights and cannot even be discussed and helped, Jefsey will soon
> be alone!
>
> Please respond: the ball is your field. Tell me: are we wrong trying to
> work in the open, liaise with the IETF and carry a lot of work to be able to
> answer you, the happiana, the PRECIS, the VIP people in a consistant way,
> also with other open works?
>
>
> This being said you perfectly know that this
>
> 2011/8/19 John C Klensin <john-ietf@jck.com>
>
>> without any specific
>> attribution or acknowledgment.  Those materials include several
>> RFCs and draft-ietf-appsawg-rfc3536bis.
>
>
> is wrong. Your name, your RFCs etc. are quoted as such. We do not publish,
> we try to draft a pertinent mail to you!
>
>
>> I am an author or major
>> contributor on several of those.  Especially since I had asked
>> earlier that any compendium of this sort list terms covered in
>> other documents, comment on them as you thought appropriate,
>
>
> This is correct. But to respond to you, a lot of work must be carried.
> Beginning with an enlarged scope to other intricate real needs you did not
> consider yet.
>
> Portzamparc
>
> BTW I am not French, I am Breton!
>
>
>
>
>
>
>
>
> _______________________________________________
> iucg mailing list
> iucg@ietf.org
> https://www.ietf.org/mailman/listinfo/iucg
>
>

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

Hi! John,<br>
This seems to be a pretty odd point of yours!=A0 As if every IETF mail had =
to=20
list the copyrights of every text or concept it works on or with.<br><br>
We only are interested in an adequate and coherent multilinguistic terminol=
ogy at the IANA. At=20
the end of the day if you want to publish it under your name you=20
welcome.<br><br>
I introduced what I hope will close this: WIKI RFC 3271 with an appropriate=
 comment. <br>
<br>
<a href=3D"http://idna2010.org">http://idna2010.org</a><br>
The text John Klensin refers to is the working wiki page: <br>
<table>
<tbody><tr></tr><tr><td>
  <br>
</td><td valign=3D"top">
<p><b><a href=3D"http://iucg.org/wiki/IDNS_Common_Glossary" title=3D"IDNS C=
ommon Glossary">IDNS Common Glossary</a></b></p></td></tr></tbody>
</table>
<table height=3D"10" width=3D"14">
<tbody><tr></tr><tr><td><br></td><td valign=3D"top"><br></td></tr></tbody>
</table>
Marie-France<br><br><div class=3D"gmail_quote">2011/8/20 jean-michel bernie=
r de portzamparc <span dir=3D"ltr">&lt;<a href=3D"mailto:jmabdp@gmail.com" =
target=3D"_blank">jmabdp@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dear Mr. Klensin,<br><br>&quot;we&quot; are =
Internet and IETF users. This makes a pretty large community. There are thr=
ee ways one can do it:<br>

<br>- in surviving with what we (do not) get. Very large part of our commun=
ity.<br>
- in hacking the internet from the outside on behalf of our right to protec=
t ourselves from digital ecosystem pollution risks. Small part of our commu=
nity.<br>- in trying to cooperate with you guys and help your inside work w=
ith our outside perspective. Microscopic part of our community. Guess why? =
Please read the begining of your mail. <br>


<br>We do it because Jefsey convinced a few of us and the IETF Chair that i=
t had to be tried. However, if the inside Internet is made of individual&#3=
9;s and ISOC&#39;s copyrights and cannot even be discussed and helped, Jefs=
ey will soon be alone!<br>


<br>Please respond: the ball is your field. Tell me: are we wrong trying to=
 work in the open, liaise with the IETF and carry a lot of work to be able =
to answer you, the happiana, the PRECIS, the VIP people in a consistant way=
, also with other open works? <br>


<br><br>This being said you perfectly know that this<br><br><div class=3D"g=
mail_quote"><div>2011/8/19 John C Klensin <span dir=3D"ltr">&lt;<a href=3D"=
mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</span=
><br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
without any specific<br>
attribution or acknowledgment. =A0Those materials include several<br>
RFCs and draft-ietf-appsawg-rfc3536bis. =A0</blockquote></div><div><br>is w=
rong. Your name, your RFCs etc. are quoted as such. We do not publish, we t=
ry to draft a pertinent mail to you!<br>=A0<br></div><div><blockquote class=
=3D"gmail_quote" style=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rg=
b(204, 204, 204);padding-left:1ex">


I am an author or major<br>
contributor on several of those. =A0Especially since I had asked<br>
earlier that any compendium of this sort list terms covered in<br>
other documents, comment on them as you thought appropriate, </blockquote><=
/div><div><br>This is correct. But to respond to you, a lot of work must be=
 carried. <br>Beginning with an enlarged scope to other intricate real need=
s you did not consider yet.<br>


</div><br><div>Portzamparc<br><br>BTW I am not French, I am Breton!<br><br>=
<br><br><br><br><br></div></div><br><div style=3D"padding:0px;margin-left:0=
px;margin-top:0px;overflow:hidden;word-wrap:break-word;color:black;font-siz=
e:10px;text-align:left;line-height:130%">


</div>
<br>_______________________________________________<br>
iucg mailing list<br>
<a href=3D"mailto:iucg@ietf.org" target=3D"_blank">iucg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/iucg" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/iucg</a><br>
<br></blockquote></div><br><div style=3D"padding:0px;margin-left:0px;margin=
-top:0px;overflow:hidden;word-wrap:break-word;color:black;font-size:10px;te=
xt-align:left;line-height:130%">
</div>
<div style=3D"visibility: hidden; left: -5000px; position: absolute; z-inde=
x: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden;=
 word-wrap: break-word; color: black; font-size: 10px; text-align: left; li=
ne-height: 130%;" id=3D"avg_ls_inline_popup">
</div>

--20cf303f6c8a65b54804aae4d4a7--

From michel@arneill-py.sacramento.ca.us  Fri Aug 19 19:53:51 2011
Return-Path: <michel@arneill-py.sacramento.ca.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A04C921F8AF5 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 19:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.853
X-Spam-Level: 
X-Spam-Status: No, score=-0.853 tagged_above=-999 required=5 tests=[AWL=-1.188, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rCg95hgQ8Qhd for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 19:53:51 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 02A3321F8AD6 for <ietf@ietf.org>; Fri, 19 Aug 2011 19:53:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: [iucg] IDNA and Multilingual Internet issues and vocabulary afterIDNA2008
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 19 Aug 2011 19:54:48 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF695@newserver.arneill-py.local>
In-Reply-To: <CAL-6tfUgmHp8TRqTTTB8M8GV0zhJQ60G2O+4ug8yMitqphcBkQ@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: [iucg] IDNA and Multilingual Internet issues and vocabulary afterIDNA2008
Thread-index: AcxezyTi0J5B1unvReedn/TeTS82SgAE42yA
References: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com><86E32E259DD17E1166516052@localhost><CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com> <CAL-6tfUgmHp8TRqTTTB8M8GV0zhJQ60G2O+4ug8yMitqphcBkQ@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "IETF" <ietf@ietf.org>, "John C Klensin" <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 02:53:51 -0000

[trimmed the cross-post To... field]

John,

In case it was not clear, I encourage you do consider who you are
dealing with on this issue: the sock puppets of JFC Morfin. These
individuals are well-known for their disruptive tactics and their
amazing capabilities at generating rectal discomfort (*) especially for
the French IETFers who do not like the idea of being remotely associated
with them (although I do not even remotely suggest that anyone does, the
possibility does exist).

Please don't feed the trolls.

Thanks
Michel

(*) I hope that the AD who introduced this wording to me in private
recently will have smile.

m.


From dhc@dcrocker.net  Fri Aug 19 22:07:19 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3631D21F8B0E for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 22:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.176
X-Spam-Level: 
X-Spam-Status: No, score=-6.176 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8x2=0.246]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ml1L-tXufK6L for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 22:07:18 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7A35421F8610 for <ietf@ietf.org>; Fri, 19 Aug 2011 22:07:17 -0700 (PDT)
Received: from [192.168.1.7] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7K588Hu003126 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 19 Aug 2011 22:08:14 -0700
References: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com><86E32E259DD17E1166516052@localhost><CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com> <CAL-6tfUgmHp8TRqTTTB8M8GV0zhJQ60G2O+4ug8yMitqphcBkQ@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF695@newserver.arneill-py.local>
User-Agent: K-9 Mail for Android
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF695@newserver.arneill-py.local>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----6HYFJ7QKGT5Y693144GFH1DYB8KQ4X"
Subject: =?UTF-8?Q?RE=3A_=5Biucg=5D_IDNA_and_Multilingual_Inter?= =?UTF-8?Q?net_issues_and_vocabulary=09afterIDNA2008?=
From: Dave Crocker <dhc@dcrocker.net>
Date: Fri, 19 Aug 2011 22:08:09 -0700
To: Michel Py <michel@arneill-py.sacramento.ca.us>, IETF <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>
Message-ID: <3e99fc5a-b3cc-47de-837c-0fa4ee79f206@email.android.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 19 Aug 2011 22:08:14 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Aug 2011 05:07:19 -0000

------6HYFJ7QKGT5Y693144GFH1DYB8KQ4X
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

+10

/d

--
Dave Crocker
bbiw.net

via mobile

_____________________________________________
From: Michel Py <michel@arneill-py.sacramento.ca.us>
Sent: Fri Aug 19 19:54:48 PDT 2011
To: IETF <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>
Subject: RE: [iucg] IDNA and Multilingual Internet issues and vocabulary	afterIDNA2008


[trimmed the cross-post To... field]

John,

In case it was not clear, I encourage you do consider who you are
dealing with on this issue: the sock puppets of JFC Morfin. These
individuals are well-known for their disruptive tactics and their
amazing capabilities at generating rectal discomfort (*) especially for
the French IETFers who do not like the idea of being remotely associated
with them (although I do not even remotely suggest that anyone does, the
possibility does exist).

Please don't feed the trolls.

Thanks
Michel

(*) I hope that the AD who introduced this wording to me in private
recently will have smile.

m.

_____________________________________________

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

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

<html><head></head><body>+10<br>
<br>
/d<br>
<br>
--<br>
   Dave Crocker<br>
   <a href="http://bbiw.net">bbiw.net</a><br>
<br>
   via mobile<br><br><div style='font-size:10.0pt;font-family:"Tahoma","sans-serif";padding:3.0pt 0in 0in 0in'>
<hr style='border:none;border-top:solid #B5C4DF 1.0pt'>
<b>From:</b> Michel Py &lt;michel@arneill-py.sacramento.ca.us&gt;<br>
<b>Sent:</b> Fri Aug 19 19:54:48 PDT 2011<br>
<b>To:</b> IETF &lt;ietf@ietf.org&gt;, John C Klensin &lt;john-ietf@jck.com&gt;<br>
<b>Subject:</b> RE: [iucg] IDNA and Multilingual Internet issues and vocabulary	afterIDNA2008<br>
</div>
<br>
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: monospace">[trimmed the cross-post To... field]<br /><br />John,<br /><br />In case it was not clear, I encourage you do consider who you are<br />dealing with on this issue: the sock puppets of JFC Morfin. These<br />individuals are well-known for their disruptive tactics and their<br />amazing capabilities at generating rectal discomfort (*) especially for<br />the French IETFers who do not like the idea of being remotely associated<br />with them (although I do not even remotely suggest that anyone does, the<br />possibility does exist).<br /><br />Please don't feed the trolls.<br /><br />Thanks<br />Michel<br /><br />(*) I hope that the AD who introduced this wording to me in private<br />recently will have smile.<br /><br />m.<br /><br /><hr /><br />Ietf mailing list<br />Ietf@ietf.org<br /><a href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a><br
/></pre></body></html>
------6HYFJ7QKGT5Y693144GFH1DYB8KQ4X--


From mfberny@gmail.com  Sat Aug 20 00:43:40 2011
Return-Path: <mfberny@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3A321F8AEA for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 00:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJy5qszSDmai for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 00:43:40 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1552721F8AB9 for <ietf@ietf.org>; Sat, 20 Aug 2011 00:43:39 -0700 (PDT)
Received: by yie12 with SMTP id 12so3143874yie.31 for <ietf@ietf.org>; Sat, 20 Aug 2011 00:44:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1xcNdd4FJUwIpK561RIKqlUAhzeqmbS05aDmqvwWFRA=; b=K57juVaznfkTnQykWcfycJDWCmjmO7rvlE/7AiO1BBIFBYZ/k/OnEjJ5oMT+BKkQJg 2TyNMiC90ro5o1n/Y14sDLk4jzjHjupePuTgRh1CkXb6uhth1a0dRon9DOjBd+1HnkZX u4QA5NGR66k2Xa+qzE7BjOvHcf79aJatzkuIQ=
MIME-Version: 1.0
Received: by 10.236.78.104 with SMTP id f68mr1379097yhe.47.1313826278731; Sat, 20 Aug 2011 00:44:38 -0700 (PDT)
Received: by 10.236.138.164 with HTTP; Sat, 20 Aug 2011 00:44:38 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF695@newserver.arneill-py.local>
References: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com> <86E32E259DD17E1166516052@localhost> <CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com> <CAL-6tfUgmHp8TRqTTTB8M8GV0zhJQ60G2O+4ug8yMitqphcBkQ@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF695@newserver.arneill-py.local>
Date: Sat, 20 Aug 2011 09:44:38 +0200
Message-ID: <CAL-6tfW1ot-YUJJYAaDhsE0Fnct9470LN2kpA_99exuxWOsQxQ@mail.gmail.com>
Subject: Re: [iucg] IDNA and Multilingual Internet issues and vocabulary afterIDNA2008
From: Marie-France Berny <mfberny@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=20cf300fa9e5a3f14d04aaeb04f7
Cc: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 07:43:40 -0000

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

Cher Michel,

2011/8/20 Michel Py <michel@arneill-py.sacramento.ca.us>

> [trimmed the cross-post To... field]
>
> John,
>
> In case it was not clear, I encourage you do consider who you are
> dealing with on this issue: the sock puppets of JFC Morfin. These
> individuals are well-known


as "Jefsey's Disciples", or "JEDI"s :-)


> for their disruptive tactics and their
> amazing capabilities at generating rectal discomfort (*)


If this is not an "ad personam"!!!
Beware, the disease usually diagnoses mental rigidity


> especially for
> the French IETFers who do not like the idea of being remotely associated
> with them (although I do not even remotely suggest that anyone does, the
> possibility does exist).
>

Selon la formule consacr=E9e : "tais-toi et travaille !".You welcome to hel=
p
the French language being properly supported. At least the ICANN/WG/VIP jus=
t
tries that.

We are just IETF users. I know, as everywhere, the user is the problem!

Sorry for this smile at your architechnical comment:

Please don't feed the trolls.
>

 you are right!

Marie-France

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

Cher Michel,<br><br><div class=3D"gmail_quote">2011/8/20 Michel Py <span di=
r=3D"ltr">&lt;<a href=3D"mailto:michel@arneill-py.sacramento.ca.us">michel@=
arneill-py.sacramento.ca.us</a>&gt;</span><br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
;">
[trimmed the cross-post To... field]<br>
<br>
John,<br>
<br>
In case it was not clear, I encourage you do consider who you are<br>
dealing with on this issue: the sock puppets of JFC Morfin. These<br>
individuals are well-known</blockquote><div><br>as &quot;Jefsey&#39;s Disci=
ples&quot;, or &quot;JEDI&quot;s :-) <br>=A0<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;">
 for their disruptive tactics and their<br>
amazing capabilities at generating rectal discomfort (*)</blockquote><div><=
br>If this is not an &quot;ad personam&quot;!!!<br>Beware, the disease usua=
lly diagnoses mental rigidity<br>=A0<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 20=
4, 204); padding-left: 1ex;">
 especially for<br>
the French IETFers who do not like the idea of being remotely associated<br=
>
with them (although I do not even remotely suggest that anyone does, the<br=
>
possibility does exist).<br></blockquote><div><br>Selon la formule consacr=
=E9e : &quot;tais-toi et travaille !&quot;.You welcome to help the French l=
anguage being properly supported. At least the ICANN/WG/VIP just tries that=
.<br>
<br>We are just IETF users. I know, as everywhere, the user is the problem!=
<br><br>Sorry for this smile at your architechnical comment:<br><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;">
Please don&#39;t feed the trolls.<br></blockquote><div><br>=A0you are right=
!<br><br>Marie-France<br></div></div><br><div style=3D"visibility: hidden; =
left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left=
: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: bla=
ck; font-size: 10px; text-align: left; line-height: 130%;" id=3D"avg_ls_inl=
ine_popup">
</div>

--20cf300fa9e5a3f14d04aaeb04f7--

From alexey.melnikov@isode.com  Sat Aug 20 10:44:52 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D48E921F8906; Sat, 20 Aug 2011 10:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.785
X-Spam-Level: 
X-Spam-Status: No, score=-102.785 tagged_above=-999 required=5 tests=[AWL=-0.186, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3lroV4IeDD3B; Sat, 20 Aug 2011 10:44:52 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 1B05421F8876; Sat, 20 Aug 2011 10:44:52 -0700 (PDT)
Received: from [188.29.11.66] (188.29.11.66.threembb.co.uk [188.29.11.66])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Tk=yywALhIu-@rufus.isode.com>; Sat, 20 Aug 2011 18:45:50 +0100
Message-ID: <4E4FF2C2.8080606@isode.com>
Date: Sat, 20 Aug 2011 18:45:38 +0100
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: draft-jesske-dispatch-update3326-reason-responses.all@tools.ietf.org
Subject: Gen-ART LC review of draft-jesske-dispatch-update3326-reason-responses-05
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Aug 2011 17:44:52 -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-jesske-dispatch-update3326-reason-responses-05

Reviewer: Alexey Melnikov

Review Date:2011-08-20

IETF LC End Date: 2011-09-08

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


From alexey.melnikov@isode.com  Sat Aug 20 10:48:48 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA89C21F861A for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 10:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.773
X-Spam-Level: 
X-Spam-Status: No, score=-102.773 tagged_above=-999 required=5 tests=[AWL=-0.174, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8n7SsI81F94f for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 10:48:48 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 4700F21F85FF for <ietf@ietf.org>; Sat, 20 Aug 2011 10:48:48 -0700 (PDT)
Received: from [188.29.11.66] (188.29.11.66.threembb.co.uk [188.29.11.66])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Tk=zuAALhAjI@rufus.isode.com>; Sat, 20 Aug 2011 18:49:46 +0100
Message-ID: <4E4FF3AF.6070006@isode.com>
Date: Sat, 20 Aug 2011 18:49:35 +0100
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" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt>  (Message Submission for Mail) to Full Standard
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com> <4E44A5BE.3050008@att.com> <F5833273385BB34F99288B3648C4F06F13512DF6E3@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF6E3@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <klensin@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 17:48:48 -0000

Murray S. Kucherawy wrote:

> +1, which is to say:
>
>- I've read it
>- I agree with what it says
>- I can't find any reason not to move it to Full Standard
>- Nice job all around
>  
>
Well said, so +1 for all of the above.

One pedantic nit:

8.4.  Transfer Encode

   The MSA MAY apply transfer encoding to the message according to MIME
   conventions, if needed and not harmful to the MIME type.

Shouldn't this be "media type"?


From sm@resistor.net  Sat Aug 20 11:17:34 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C658F21F85C4 for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 11:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.279
X-Spam-Level: 
X-Spam-Status: No, score=-102.279 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c0CYcKZYQS6I for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 11:17:33 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28CEB21F85B8 for <ietf@ietf.org>; Sat, 20 Aug 2011 11:17:33 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7KIIG5C022797 for <ietf@ietf.org>; Sat, 20 Aug 2011 11:18:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1313864308; bh=XthD4K2h1HL/x/f1CeRMnOIYlZ1yKOfpRs6LwMlgmQ0=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=0sz7z4cCfyDYmUtj7K6/UzdoGSFY58uBnfdVCKYpcG4F2j+nkEaiJTO5z50tyjWFj iznutqrWRIqI6rN6mEI081g/gUsAQ01d1Rz+rT5nl1dql6aHThCS4D1Ztq5yJochqW A1upVGSokdCg3pvJhLA29ysiDDnj053SFveHzhoo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1313864308; bh=XthD4K2h1HL/x/f1CeRMnOIYlZ1yKOfpRs6LwMlgmQ0=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=QNtfK72gNNaNGPyrf3tt/oNeGLemg1UwNIjAbtRUwNZoaZeZmii5/SG+FEn9fCTde R1+zSuNuENJAezEv2K1GCIpcvUHERt3XOFVRBIuiqgB5VwphTA8ibNxmDlKchOt0tw c8NSCZ00TRDNhQ7xd1cHvczcoojWe+0VI3dEzoDY=
Message-Id: <6.2.5.6.2.20110820031053.0a551ca8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 20 Aug 2011 11:11:58 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
In-Reply-To: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 18:17:34 -0000

At 11:33 19-08-2011, The IESG wrote:
>The IESG has received a request from the Internet Area Working Group WG
>(intarea) to consider the following document:
>- 'IPv6 Support Required for all IP-capable nodes'
>   <draft-ietf-intarea-ipv6-required-01.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-09-02. Exceptionally, comments may be

 From Section 1:

   "However, due to the success of the Internet in finding new and
    innovative uses for IP networking, billions of hosts are now
    connected via the Internet and requiring unique addressing."

That sounds like the requirement for unique addressing is a 
problem.  The draft mentions that demand has lead to the exhaustion 
of the IANA global pool of unique IPv4 addresses.  Should the above 
be read as "requiring unique IPv4 addressing"?

   "The exhaustion of IPv4 and the continued growth of the internet
     worldwide has created the driver for widespread IPv6 deployment."

As a nit, that should be "exhaustion of the IANA IPv4 global pool".

   "However, the IPv6 deployment necessary to reduce reliance on IPv4 has
    been hampered by a lack of ubiquitous hardware and software support
    throughout the industry."

Quoting RFC 5218:

   'The lack of a value chain can make it difficult for a new protocol to
    progress from implementation to deployment to use.  While the term
    "chicken-and-egg" problem is sometimes used to describe the lack of a
    value chain, the lack of implementation, deployment, or use is not
    the cause of failure, it is merely a symptom.'

The assertion that the problem is a lack of ubiquitous hardware and 
software support throughout the industry is incorrect.  It is the 
lack of the value chain that has hampered IPv6 deployment.

   'Many vendors, especially in the consumer space have continued to
    view IPv6 support as optional. Even today they are still selling
    "IP capable" or "Internet Capable" devices which are not IPv6-capable,
    which has continued to push out the point at which the natural hardware
    refresh cycle will significantly increase IPv6 support in the average
    home or enterprise network.'

Many vendors in the consumer space such as Internet Service Providers 
still view IPv6 support as optional.  They are still pushing the 
"Internet" as an IPv4 medium only.  Considering that I am living on 
an IPV6 island, let's see whether the following domains would accept 
my messages:

   icann.org
   ietf.org
   itu.int

Let's push this further by sampling domains in recent RFCs:

   cisco.com
   ericsson.com
   alcatel-lucent.com
   nttv6.net
   juniper.net
   nokia.com
   huawei.com
   us.ibm.com
   microsoft.com
   orange-ftgroup.com

For anyone who doesn't want the bother to figure it out, the answer is two.

Even if the average home gets an IPv6-capable device, that would not 
get it any further due to last-mile issues.  The ISP probably forgot 
to include RFC 2460 support as part of its requirements.  Now, you 
can understand why "they" (not referring to any specific group) find 
it difficult to wean off 32-bit integers.

   "For the same reason that the average consumer is not making a
    purchasing decision based on the presence of IPv6 support in
    their Internet-capable devices and services, consumers are
    unlikely to replace their still-functional Internet-capable
    devices simply to add IPv6 support - they don't know or don't
    care about IPv6, they simply want their devices to work as
    advertised."

Consumers are likely to replace their still-functioning 
Internet-capable device if they perceive that it will help them 
fulfill a "want".  Anyway, let's get to the meat of the draft.

 From Section 2:

   'Updates [RFC1812], especially sections 1, 2, and 4 which use the
    generic "IP" synonymously with the more specific "IPv4."  Since
    RFC1812 is an IPv4 router specification, the generic use of IP in
    this standard may cause confusion as IP is redefined to mean IPv4 +
    IPv6.'

The title of RFC 1812 is "Requirements for IP Version 4 
Routers".  The update proposed in this draft causes even more 
confusion as it is unclear what text is being updated in RFC 1812.

   'Updates [RFC1122] to clarify that this document, especially in
    section 3, primarily discusses IPv4 where it uses the more generic
    term "IP" and is no longer a complete definition of "IP" or the
    Internet Protocol suite by itself.'

This second update is again confusing as text does not get updated 
"for example".  As the intended status of this draft is Proposed 
Standard, there is a presumption that if it is going to update STD 3, 
it will do so clearly.

   'Updates [RFC4084] to move "Version Support" from Section 4,
    "Additional Terminology" to Section 2, "General Terminology." This
    is to reflect the idea that version support is now critical to
    defining the types of IP service, especially with respect to Full
    Internet Connectivity."

I don't consider this as a valid reason to update BCP 104.  The 
"document provides a list of terms and definitions that may be 
helpful to providers, consumers, and, potentially, regulators in 
clarifying the type and character of services being offered".  Moving 
version support from Section 4 to Section 2 does not make the 
document more helpful.  I get blank stares when I ask about "IP 
dresses".  I have yet to find out what will happen when I ask about 
"IP sex dresses".

Seriously, BCPs, in general, are about what's happening in the wild 
and not IETF wishful thinking.  If you are going to take a RFC 
written for a wider audience and stick an "Updated by" into it, the 
reader might not see the change.

   "Rather than update the existing IPv4 protocol specification standards
    to include IPv6, IETF has defined a completely separate set of
    standalone documents which cover IPv6."

Was there a reason for that?

   "From a practical perspective, the requirements proposed by this draft
    mean that:

       New IP implementations MUST support IPv6."

draft-ietf-intarea-ipv6-required-01 has an informative reference to 
RFC 2460.  Do I have to understand what IPv6 is about if it is 
required that my new IP implementation supports it?

BTW, this draft has nine pages and four authors.  The 162-page draft 
I read recently has five authors.  "If there is a desire to 
demonstrate how many companies are interested in this spec, a simple 
acknowledgment section can accomplish the same thing".

I do not support the publication of this document as a RFC.  It 
attempts to update old RFCs which are well-written in a confusing 
manner.  The draft comes out as a statement about "IPv6-required" 
instead of a Proposed Standard.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Sat Aug 20 16:48:53 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C13A21F8610 for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 16:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.584
X-Spam-Level: 
X-Spam-Status: No, score=-103.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPm-e2zkJy8y for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 16:48:52 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDD921F85B9 for <ietf@ietf.org>; Sat, 20 Aug 2011 16:48:52 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2880598fxe.31 for <ietf@ietf.org>; Sat, 20 Aug 2011 16:49:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bLi2MrpFyFhYDW0/EKuf4S3jKAjDcNvk0qB3fh5Huwg=; b=qI5Nrr4UJ+LP+u2R8yYfuonVVLWIAh/sLZfvml9xjcVFH+7V5YYPu3RyFPJ1wyAPzq ma6PMmWGV0HxfUlXg8JgFJ3NirBrpNxxB3lHaYvqhi8gp0T3sEOmUkzDIbv/Ir2d6Y/Q j0XqpX8gRmKZb0A/4clasovvpPRPR8nRaeCTk=
Received: by 10.223.58.131 with SMTP id g3mr1310201fah.99.1313884192551; Sat, 20 Aug 2011 16:49:52 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id b14sm3793074fab.19.2011.08.20.16.49.47 (version=SSLv3 cipher=OTHER); Sat, 20 Aug 2011 16:49:50 -0700 (PDT)
Message-ID: <4E504816.2080604@gmail.com>
Date: Sun, 21 Aug 2011 11:49:42 +1200
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: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6	Support Required for all IP-capable nodes) to Proposed Standard
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110820031053.0a551ca8@resistor.net>
In-Reply-To: <6.2.5.6.2.20110820031053.0a551ca8@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 23:48:53 -0000

Hi Subramanian,

I think most of your comments will be dealt with by
wordsmithing,  but...

On 2011-08-21 06:11, SM wrote:
...
> From Section 2:
> 
>   'Updates [RFC1812], especially sections 1, 2, and 4 which use the
>    generic "IP" synonymously with the more specific "IPv4."  Since
>    RFC1812 is an IPv4 router specification, the generic use of IP in
>    this standard may cause confusion as IP is redefined to mean IPv4 +
>    IPv6.'
> 
> The title of RFC 1812 is "Requirements for IP Version 4 Routers".  The
> update proposed in this draft causes even more confusion as it is
> unclear what text is being updated in RFC 1812.

It't quite clear to me, but we could spell it out: s/IP/IPv4/.

>   'Updates [RFC1122] to clarify that this document, especially in
>    section 3, primarily discusses IPv4 where it uses the more generic
>    term "IP" and is no longer a complete definition of "IP" or the
>    Internet Protocol suite by itself.'
> 
> This second update is again confusing as text does not get updated "for
> example".  As the intended status of this draft is Proposed Standard,
> there is a presumption that if it is going to update STD 3, it will do
> so clearly.

Ditto.

>   'Updates [RFC4084] to move "Version Support" from Section 4,
>    "Additional Terminology" to Section 2, "General Terminology." This
>    is to reflect the idea that version support is now critical to
>    defining the types of IP service, especially with respect to Full
>    Internet Connectivity."
> 
> I don't consider this as a valid reason to update BCP 104.  The
> "document provides a list of terms and definitions that may be helpful
> to providers, consumers, and, potentially, regulators in clarifying the
> type and character of services being offered".  Moving version support
> from Section 4 to Section 2 does not make the document more helpful.  

Yes it does. It clarifies, for consumer organizations for
example, the IPv6 is not additional technology but is part of
any general IP service.

I
> get blank stares when I ask about "IP dresses".  I have yet to find out
> what will happen when I ask about "IP sex dresses".
> 
> Seriously, BCPs, in general, are about what's happening in the wild and
> not IETF wishful thinking.  

They are about the best practices that the IETF wishes were
being used in the wild.

If you are going to take a RFC written for a
> wider audience and stick an "Updated by" into it, the reader might not
> see the change.

Of course - we have that problem every time we update any RFC.
It is quite orthogonal to the question whether we *should*
update the RFC.

> 
>   "Rather than update the existing IPv4 protocol specification standards
>    to include IPv6, IETF has defined a completely separate set of
>    standalone documents which cover IPv6."
> 
> Was there a reason for that?

Yes. Because IPv4 has no address extensibility, it was
impossible to update it for larger addresses. That has been
known since 1981 or thereabouts.

   Brian

From ajs@anvilwalrusden.com  Sat Aug 20 20:24:06 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC4721F8593; Sat, 20 Aug 2011 20:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id METDR6gzIqWP; Sat, 20 Aug 2011 20:24:06 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id E865E21F8560; Sat, 20 Aug 2011 20:23:56 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 000B31ECB41D; Sun, 21 Aug 2011 03:24:57 +0000 (UTC)
Date: Sat, 20 Aug 2011 23:24:49 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: jefsey <jefsey@jefsey.com>
Subject: Re: [precis] Path towards a multilingalization IUse referent
Message-ID: <20110821032449.GA39963@shinkuro.com>
References: <7.0.1.0.2.20110821003129.0da01218@jefsey.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7.0.1.0.2.20110821003129.0da01218@jefsey.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IETF Discussion <ietf@ietf.org>, precis@ietf.org, happiana@ietf.org, "idna-update@alvestrand.no work" <idna-update@alvestrand.no>, iucg@ietf.org, John C Klensin <john-ietf@jck.com>, vip@icann.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Aug 2011 03:24:06 -0000

Dear colleagues,

I did not read the rest of the message past what I quote below, becase
it did not seem to me that the structure of the message would answer
the question I pose.  Therefore, I make a request:

On Sun, Aug 21, 2011 at 01:08:29AM +0200, jefsey wrote:
> However, the Internet MUST be supported by a
> network/human oriented universal semiotic system.

I would like a defence of that claim.  Speaking entirely personally, I
don't believe it.

We shape our technology, but our technology also shapes us.  There is
nothing intrinsic about "green" meaning "go".  There is nothing about
the universe that causes time zones (which is different from saying
"differences in the apparent time of dawn and dusk").  Yet we all,
techno-literate that we are, take these bits of cultural dreck and
make them true.  Moreover, we adjust to them -- somehow finding it
more convenient to say, "Darkness falls earlier," than to say, "The
time on the clock is wrong."

It is, in my personal opinion, completely foolish to imagine that
Internet names -- which are, by their nature at the time of
registration and lookup, even if not for the user, completely devoid
of cultural context -- can ever be made completely user-centric.
Users will have to learn some things, and some of those things will be
"Internet names are a little different, & have strange restrictive
rules."  More importantly, while I am not one of those people in the
thrall of the conceptual scheme (cf. Davidson), I think it is
preposterous to suggest that we will come up with a universal semiotic
system given the limitations of the DNS and the way that denoting
works in different linguistic traditions.

I believe we can come up with some useful conventions that will work
most of the time, for most people.  I believe that these will strain
the rules of every writing system on the planet, in much the way that
"ns1" strains English writing rules.  I am incredulous at the
suggestion that the Internet needs a "network/human oriented universal
semiotic system," both because I don't believe it and because I
believe that humans (and especially human language) are much more
resilient than that.

Best regards,

Andrew

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From sm@resistor.net  Sun Aug 21 00:10:24 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9C4921F851F for <ietf@ietfa.amsl.com>; Sun, 21 Aug 2011 00:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5y7cXwsg9GT for <ietf@ietfa.amsl.com>; Sun, 21 Aug 2011 00:10:19 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D41E721F84CB for <ietf@ietf.org>; Sun, 21 Aug 2011 00:10:16 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7L7AwN7012962; Sun, 21 Aug 2011 00:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1313910666; bh=XM/161Rv7UKkUHVH+wtgu0ap9cCuTw0K21jJdh/S8Yk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=3OhSIIvlwdIyYzLjBfMyZb3MLQ9qjCgboiUirrSmJYBe1Lth279NtXLaUOe8+Q7RL nTTbLrOD0D3/2UMd4unlXxiGZGv9Gb7oK6X2wWOPdRw1hWpQ7dCfk8rMLOze02s7QE q6A5BfZRU770VYmkZVK9z+WgDSeBWuYDOClIGxbA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1313910666; bh=XM/161Rv7UKkUHVH+wtgu0ap9cCuTw0K21jJdh/S8Yk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=cbQmQ6m5r1fkzmd+MAUQnibmYYkDxl+MohpiZ9SGp4llQLrzhfEb89mJNjivu75HO zocMCpzcsfT9Dn8ifJszmfWIINUwQbNu4T9k0MIZCNcOOc2VUzM0JpLP8Prc2/RuUq jrOACF9TMLJ9ui+lcg87/uMZRHwO1EsRGroOTUQU=
Message-Id: <6.2.5.6.2.20110820182242.09b4c238@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 21 Aug 2011 00:02:21 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6	Support Required for all IP-capable nodes) to Proposed Standard
In-Reply-To: <4E504816.2080604@gmail.com>
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110820031053.0a551ca8@resistor.net> <4E504816.2080604@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Aug 2011 07:10:24 -0000

Hi Brian,
At 16:49 20-08-2011, Brian E Carpenter wrote:
>I think most of your comments will be dealt with by
>wordsmithing,  but...

See comments below.

>It't quite clear to me, but we could spell it out: s/IP/IPv4/.

That's clearer.

>Yes it does. It clarifies, for consumer organizations for
>example, the IPv6 is not additional technology but is part of
>any general IP service.

Section 2 of RFC 4084  lists the primary IP service terms:

  (a) Web connectivity

  (b) Client connectivity only, without a public address

  (c) Client only, public address

  (d) Firewalled Internet Connectivity

  (e) Full Internet Connectivity


And with the proposed update:

(f) Version support.

       Does the service include IPv4 support only, both IPv4 and IPv6
       support, or IPv6 support only?

I don't think that it makes sense as it stands.  If you want to 
wordsmith this, you could go with:

  (f) IPv4 Internet Connectivity.

       This service provides the user IPv4 Internet connectivity, with
       one or more static public IPv4 addresses.  Dynamic IPv4 addresses
       that are long-lived enough to make operating servers practical
       without highly dynamic DNS entries are possible, provided that
       they are not characterized as "dynamic" to third parties.

  (g)  IPv6 Internet Connectivity.

       This service provides the user/consumer IPv6 Internet connectivity,
       with at least a /60 IPv6 prefix.  Dynamic IPv6 addressing that are
       long-lived enough to make operating servers practical
       without highly dynamic DNS entries are possible, provided that
       they are not characterized as "dynamic" to third parties.

Note: The above sub-section would need some more work as a host can 
do with one IPv6 address whereas a home user could get an IPv6 
prefix.  I used a /60 prefix.  Some people may view a /56 as more 
appropriate.  The sub-section could be broken into two, one for users 
and the other one for consumers.

  (h)  Full Internet Connectivity.

       This service provides the user with both IPv4 Internet Connectivity
       and IPv6 Internet Connectivity.

>They are about the best practices that the IETF wishes were
>being used in the wild.

Then it should be expected that there will be a wide disconnect 
between what the document says and what is happening in the wild.  In 
essence, if there is no motivation to adhere to some semblance of 
reality, the IETF's wishes will remain best wishes.

>Of course - we have that problem every time we update any RFC.
>It is quite orthogonal to the question whether we *should*
>update the RFC.

Most RFCs are not written for a wider audience.

>Yes. Because IPv4 has no address extensibility, it was
>impossible to update it for larger addresses. That has been
>known since 1981 or thereabouts.

And that is probably why it did not make sense to update the IPv4 
specifications to point to IPv6 specifications.  In my opinion, it 
also does not make sense to do likewise with those old RFCs.  The 
Abstract Section mentions that:

    "this document deprecates the concept that an IP-capable node MAY
     support IPv4 _only_, and redefines an IP-capable node as one which
     supports either IPv6 _only_ or IPv4/IPv6 dual-stack."

IPv6 node requirements are defined in RFC 4294.  It's merely an 
informative reference in draft-ietf-intarea-ipv6-required-01.  The 
discussion about IPV4 address pool exhaustion (Section 1) is a 
distraction from a definition of an IP-capable node.  If the 
intention is to push for IPv6 support in all nodes so that an IP node 
is ubiquitous with IPv4 and IPv6, it would be helpful to have a clear 
and concise document about that.  I do not view concise as saying 
"MUST support IPv6" and be done with it.  The document would state 
which technical specifications an IP-capable mode must support.

Regards,
-sm

1. http://www.6ip.cu/documentos-cuba/R140-08.pdf 


From brian.e.carpenter@gmail.com  Sun Aug 21 15:58:06 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC1EF21F86AC for <ietf@ietfa.amsl.com>; Sun, 21 Aug 2011 15:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.595
X-Spam-Level: 
X-Spam-Status: No, score=-103.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EA43Jp5Z6Yii for <ietf@ietfa.amsl.com>; Sun, 21 Aug 2011 15:58:06 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4CBA621F86B6 for <ietf@ietf.org>; Sun, 21 Aug 2011 15:58:06 -0700 (PDT)
Received: by ywm21 with SMTP id 21so3464804ywm.31 for <ietf@ietf.org>; Sun, 21 Aug 2011 15:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ap94FJYNKPpyUxQzAKKaG7N/4AwVEAfRofx4Azas85E=; b=Qm2j4j7+pZWDTDlnRxHOZrY/FNUf7q0/lcQtaL+HwOWyjBxfhE4mJ6EBqpnENYHyV0 TjREIkfo8aD4We7t3HDBl26mfLPHQXv1IKtsZPKp+6lYfhanIALeXqKs5DE8XSZbSrt7 +Q9MjaSNqi1INV+WMU/1e+kYc68rh9ZwjHky0=
Received: by 10.236.139.169 with SMTP id c29mr9917331yhj.122.1313967549487; Sun, 21 Aug 2011 15:59:09 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id e21sm2945166yhn.7.2011.08.21.15.59.07 (version=SSLv3 cipher=OTHER); Sun, 21 Aug 2011 15:59:08 -0700 (PDT)
Message-ID: <4E518DB7.8020400@gmail.com>
Date: Mon, 22 Aug 2011 10:59:03 +1200
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: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6	Support Required for all IP-capable nodes) to Proposed Standard
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110820031053.0a551ca8@resistor.net> <4E504816.2080604@gmail.com> <6.2.5.6.2.20110820182242.09b4c238@resistor.net>
In-Reply-To: <6.2.5.6.2.20110820182242.09b4c238@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Aug 2011 22:58:07 -0000

On 2011-08-21 19:02, SM wrote:
> Hi Brian,

...
> IPv6 node requirements are defined in RFC 4294.  It's merely an
> informative reference in draft-ietf-intarea-ipv6-required-01.  The
> discussion about IPV4 address pool exhaustion (Section 1) is a
> distraction from a definition of an IP-capable node.  If the intention
> is to push for IPv6 support in all nodes so that an IP node is
> ubiquitous with IPv4 and IPv6, it would be helpful to have a clear and
> concise document about that.  I do not view concise as saying "MUST
> support IPv6" and be done with it.  The document would state which
> technical specifications an IP-capable mode must support.

That is the role of draft-ietf-6man-node-req-bis (which, if
approved, will obsolete RFC 4294). There are practical reasons
why both of these documents are Informational, and thefore would
require special arguments to be cited normatively.

   Brian

From daedulus@btconnect.com  Mon Aug 22 01:13:41 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4A4F21F8906 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 01:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level: 
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[AWL=-1.317, BAYES_40=-0.185, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwjjXOto-rce for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 01:13:40 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id DAA1E21F8880 for <ietf@ietf.org>; Mon, 22 Aug 2011 01:13:39 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr10.btconnect.com with SMTP id EAB35250; Mon, 22 Aug 2011 09:13:30 +0100 (BST)
Message-ID: <005b01cc609a$7e9ab540$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110820031053.0a551ca8@resistor.net>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
Date: Mon, 22 Aug 2011 09:09:47 +0200
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.4E520FAA.006A, actions=tag
X-Junkmail-Premium-Raw: score=9/50, refid=2.7.2:2011.8.22.70314:17:9.535, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, TO_IN_SUBJECT, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1200_1299, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS, NO_URI_FOUND
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020D.4E520FF2.00F6,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 08:13:41 -0000

I find this document utterly bizarre and think it would seriously damage the
Internet to publish it.

The idea that ipv6 should be regarded as normal, as of equal standing to ipv4 is
fine, the sort of statement that the IAB should make, or have made, as an RFC or
in some other form.

But this I-D claims
" Updates [RFC1122] to clarify that this document, especially in
   section 3, primarily discusses IPv4 where it uses the more generic
   term "IP" and is no longer a complete definition of "IP" or the
   Internet Protocol suite by itself.  "

IPv4 is a phenomenal success, and RFC1122 is a key part of that.  IPv4 was a
confused jumble, as IPv6 is now, and RFC1122, with another two or so I-Ds, cut
through the cruft and rendered it usable.  IPv6 desparately needs an equivalent
to RFC1122, as a trawl of the v6ops list archives shows, and clearly this I-D is
never going to be it, but claiming that this I-D provides an update to RFC1122,
coupled
with its title, gives the message that there is not going to be such an I-D;
IPv6 will remain a confused jumble (and so is unlikely ever to emulate the
success of IPv4).

Bin it.

Tom Petch


----- Original Message -----


From hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com  Mon Aug 22 05:08:38 2011
Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF0D921F8B2E for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 05:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.796
X-Spam-Level: 
X-Spam-Status: No, score=-102.796 tagged_above=-999 required=5 tests=[AWL=0.303, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vGcjfNKe6uHo for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 05:08:38 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAE121F8B19 for <ietf@ietf.org>; Mon, 22 Aug 2011 05:08:38 -0700 (PDT)
Received: by pzk33 with SMTP id 33so16551403pzk.18 for <ietf@ietf.org>; Mon, 22 Aug 2011 05:09:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=1da0mkXvPc5NA2evojry2oCXP7vRSigyHkS+6MSCuxg=; b=kkLejl7PmTP68R1ALDQ79Ro8MFDIIHyVhJYPvtfHkJePgQ7sT2NxF0kKX8X1VKbWDv yz9ONQnVytDIJFcESHzRMOmgYf5KCIQLyQDl1+YGcln1WobJo+sgRUIjqwIYYZT4WYfB HK4Mzk/7sStLsoizlmfCoEJfm661vgX62oenE=
Received: by 10.68.6.200 with SMTP id d8mr44318pba.90.1314014983098; Mon, 22 Aug 2011 05:09:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.98.5 with HTTP; Mon, 22 Aug 2011 05:09:23 -0700 (PDT)
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Mon, 22 Aug 2011 14:09:23 +0200
Message-ID: <CAHhFybrTaLGODUpR38KKKT-g4kkWkYRqXePMvezm0a8BpwPj2w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 12:08:38 -0000

Nothing is wrong in BCP 104, it needs no "updated by" moving the definition
of the term "version support" from one of its sections to another section.

-Frank

From wesley.george@twcable.com  Mon Aug 22 06:59:15 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A9F21F8B4C for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 06:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.081
X-Spam-Level: 
X-Spam-Status: No, score=-0.081 tagged_above=-999 required=5 tests=[AWL=0.382,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0GES3HsP+fS5 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 06:59:14 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 1E9F721F8B4A for <ietf@ietf.org>; Mon, 22 Aug 2011 06:59:14 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,409,1309752000"; d="scan'208";a="264758940"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 22 Aug 2011 09:58:30 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 22 Aug 2011 10:00:18 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
Date: Mon, 22 Aug 2011 10:00:16 -0400
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
Thread-Index: Acxg09IqB2/cipb/TSGesGiy/CIcFQ==
Message-ID: <34E4F50CAFA10349A41E0756550084FB0D557028@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-intarea-ipv6-required@tools.ietf.org" <draft-ietf-intarea-ipv6-required@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 13:59:15 -0000

From: Keith Moore <moore@network-heretics.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Sup=
port Required for all IP-capable nodes) to Proposed Standard

I support publication of some document like this one. Suggestions for clari=
fication to this document:

1. (section 2 in general) I think it's vague for this document to claim tha=
t it "updates" earlier documents as if it's changing the text of those docu=
ments.
The reader is left with only a vague impression of what is still in place f=
rom those documents and what has changed.

I suggest that the language in this draft be changed to first state each ne=
w or revised requirement, and then state how this changes
recommendations/requirements stated in earlier documents.
__________
WEG] We received similar feedback in the intarea last call, the "Updates...=
" language in section two is an attempt to do this clarification and is far=
 more specific than the 00 version. It was attempting to note that rather t=
han updating the details of the technical specs, it was pointing out that I=
P as generic could mean IPv4 or IPv6, but these documents are clearly IPv4 =
documents. Think of it as equivalent to %s/IP/IPv4/g. Since it appears that=
 this was not completely successful, I'd appreciate more specific feedback =
or text suggestions to make it better.

2. section 2, page 4 reads:

reason: to me "SHOULD NOT support IPv4 only" seems potentially confusing.
__________
WEG] agree, will fix in next rev.

3. section 2, page 5 reads:

New IP implementations MUST support IPv6.

Current IP implementations SHOULD support IPv6.

In general, it's meaningless to impose a requirement on current implementat=
ions of anything.
____________
WEG] This is why it's a SHOULD instead of a MUST. Also, generally this docu=
ment is saying "the IETF recommends that you support IPv6" so it seems a ga=
p to leave out current implementations. This is also why the last paragraph=
 in section 2 is there - we realize that there are going to be limitations =
to this and are trying to be pragmatic.

 Also, it's not clear what is meant by "new implementations" -
does this mean completely new implementations, or revisions of existing imp=
lementations?
____________
WEG] I'm wondering if it actually matters in this context? They both need t=
o support IPv6, which is why both requirements are there. Ultimately, this =
is going to be open to interpretation by implementers regardless of how it =
is worded. Since the IETF has no control over what they decide to do, if th=
ey choose to interpret their implementation as not new and therefore covere=
d by the SHOULD instead of the MUST, IETF has no recourse if they disagree =
with that interpretation.
That said, I am certainly open to additional text to clarify what "new impl=
ementations" are vs "current implementations" if you believe that it'll be =
helpful.

Suggest that this be restated. e.g. "Host and router IP implementations MUS=
T support IPv6; to support only IPv4 is insufficient."
____________
WEG] This may be a way to solve. We'll consider in the revision.

4. also section 2, page 5:

IPv6 support MUST be equivalent or better in quality and
functionality when compared to IPv4 support in an IP
implementation.

This statement could be taken too broadly, e.g. as applying to service offe=
rings rather than just host and router implementations.
_____________
WEG] It was intended to be taken as broadly as possible. It's not necessari=
ly limited to host and router implementations, though that is indeed its pr=
imary focus. How is it a bad thing if a service offering interprets this to=
 mean that the IETF recommends that they support IPv6?


Suggest instead:
Support for the IPv6 protocol in hosts and routers MUST
be equivalent or better in quality and functionality when
compared to IPv4 support in the same products.

Even then, this strikes me as problematic. Should an implementation that ca=
nnot provide support for every IPv6 feature (perhaps because of inherent
differences between IPv4 and IPv6, or because some feature hasn't yet been =
updated to support IPv6) be expected to remove features from its IPv4 stack=
 so that
its IPv6 stack is "equivalent or better"?
______________
WEG] For what it's worth, I'm aware of several businesses that are using la=
nguage similar to this in their vendor requirements documents. Basically, m=
aking it incumbent on the implementer to ensure that their gear supports fe=
atures in both IPv4 and IPv6 rather than calling out specific features and =
thus risking missing some. So, I think the answer to your question is that =
it's a business decision on the part of the implementer. Some of the very e=
arly comments we received on this draft indicated a concern that people wou=
ld implement the bare minimum IPv6 support and call it a day, making it mos=
tly useless by comparison because it was so limited in functionality. This =
more generic text was chosen to cover this concern without getting us ratho=
led into a discussion about whether (for example) NAT is required in IPv6 b=
ecause it's supported in IPv4 today. The larger discussion about feature pa=
rity in IPv4 vs IPv6 is a good bit longer I think, but we'd be willing to d=
iscuss it briefly in this draft if you think it would be useful. Perhaps:
        In this context, IPv4-IPv6
      feature parity is the absence of gaps where functionality exists
      in IPv4 but has no equivalent in IPv6.  Note that this does not
      mean a direct 1:1 relationship where every feature that exists in
      IPv4 will exist in IPv6.  This is because IPv6 eliminates the need
      for some features that exist in IPv4, IPv4 supports some features
      that are no longer in use, and some existing IPv4 features are
      integrated into other parts of IPv6.  In addition, as new features
      and implementations take advantage of the differences between IPv6
      and IPv4, it is expected that IPv6 will surpass IPv4 and feature
      parity will begin to swing in the other direction as the decision
      is made not to implement certain features and protocols with
      specific support for IPv4.


At the very least, I think the MUST should be a SHOULD.
__________
WEG] would any of the above clarification change your mind? I think droppin=
g this to a SHOULD leaves a much larger opening for incomplete IPv6 impleme=
ntations.

Thanks for the comments,
Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From hotz@jpl.nasa.gov  Fri Aug 19 13:16:26 2011
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05CFB21F8B76 for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 13:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RivWojWmlFYO for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 13:16:25 -0700 (PDT)
Received: from mail.jpl.nasa.gov (smtp.jpl.nasa.gov [128.149.139.105]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA9821F8B75 for <ietf@ietf.org>; Fri, 19 Aug 2011 13:16:25 -0700 (PDT)
Received: from dhcp-137-79-179-111.jpl.nasa.gov (dhcp-137-79-179-111.jpl.nasa.gov [137.79.179.111]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7JKHITb025800 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Fri, 19 Aug 2011 13:17:20 -0700
Subject: Re: [Ietf-krb-wg] AD review of draft-ietf-krb-wg-otp-preauth
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <tslaab62yxk.fsf@mit.edu>
Date: Fri, 19 Aug 2011 13:17:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3A0053D-A6DB-4938-A8B2-70B50BFB3B99@jpl.nasa.gov>
References: <4E47FEAC.50005@cs.tcd.ie> <B1371F619AB0A94C9AC73CF2E475485B038C492431@MX11A.corp.emc.com> <tsl39h086qh.fsf@mit.edu> <87r54iihbb.fsf@latte.josefsson.org> <tslaab62yxk.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>, Simon Josefsson <simon@josefsson.org>
X-Mailer: Apple Mail (2.1084)
X-Source-IP: dhcp-137-79-179-111.jpl.nasa.gov [137.79.179.111]
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Mon, 22 Aug 2011 07:16:43 -0700
Cc: "ietf-krb-wg@lists.anl.gov list \(ietf-krb-wg@lists.anl.gov\)" <ietf-krb-wg@lists.anl.gov>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 20:16:26 -0000

I don't believe any of my desirements justifies holding up publication.

Practically speaking, I'm most interested in the "disconnected" case.  =
It should also be the easiest to test thoroughly.  I also believe the =
draft is good enough for this case.  I would very much like to see =
client code capable of handling it widely deployed so I don't have to.

I would like to see some indication that the specification is sufficient =
for some realistic connected token, but I'm not sure I'm qualified to =
judge that.  I have not been looking at that case.  (Yubikey doesn't =
count.)

I would also like some better indication that the pin change stuff can =
work, but I expect pin changes to be "out of band" for anything I'm =
currently contemplating deploying.  If no one else volunteers, I can =
probably look at that again within the next few weeks.

> I'm thinking it would be useful to at least work out how a =
interoperable
> profile of one OTP mechanism such as HOTP would work.  I have some
> cycles to work on such a profile, but I would need help (any takers?).

Glad to help.  No promises about speed of turnaround for my feedback, =
but please CC me at least.
------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu


From lmartini@cisco.com  Fri Aug 19 13:16:37 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61A9021F8B76; Fri, 19 Aug 2011 13:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5LKnnGO8qcLr; Fri, 19 Aug 2011 13:16:36 -0700 (PDT)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by ietfa.amsl.com (Postfix) with ESMTP id 3923B21F8B75; Fri, 19 Aug 2011 13:16:36 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p7JKHM6o002114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Aug 2011 14:17:22 -0600 (MDT)
Message-ID: <4E4EC4D2.3070603@cisco.com>
Date: Fri, 19 Aug 2011 14:17:22 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>, <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 22 Aug 2011 07:16:43 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 20:16:37 -0000

John,


I would like to  let applications decide how they design the use of the gal.

So I would propose a simple change , that will move any discussions to
the specific applications:

The next text would be as follows:



-  Section 4.2. (GAL Applicability and Usage) in [RFC5586], the
      original text:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MUST NOT be used with PWs. It MUST always be at the bottom of
          the label stack (i.e., S bit set to 1). However, in other MPLS
          environments, this document places no restrictions on where
          the GAL may appear within the label stack or its use with PWs.

      is replaced by:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MAY be used with PWs.



Does this work ?
Thanks.
Luca






On 08/18/11 08:00, John E Drake wrote:
> Sasha,
>
> I completely agree with your recommendations:
>
> - releasing the bottom-of-stack requirement on GAL
>
> - making use of the statement in RFC 5586 that if GAL is encountered in a packet then G-ACh header MUST be present immediately after the bottom of the label stack (and not immediately after GAL)
>
> - specifying that ECMP on labeled packets MUST ignore reserved labels
>
> Thanks,
>
> John
>
> Sent from my iPhone
>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of
>> Alexander Vainshtein
>> Sent: Wednesday, August 17, 2011 9:52 PM
>> To: Luca Martini
>> Cc: mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit;
>> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>> Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-
>> gal-in-pw
>>
>> Luca and all,
>> I have not found the statement you've proposed in draft-ietf-pwe3-fat-
>> pw-06. Instead, it contans the following text in Section 8.5 "
>> Applicability to MPLS-TP":
>>
>> <quote>
>>    The flow aware transport of a PW reorders packets, therefore MUST
>> NOT be
>>    deployed in a network conforming to the MPLS-TP unless these
>> integrity requirements
>>    specified in the SLA can be satisfied.
>> <end quote>
>>
>> (In the -07 version this text is repeated but followed by an incomplete
>> statement " In a" immediately followed by the heading of Section 8.6.
>> Since this addition is difficult to parse, I will ignore it for the
>> moment.)
>>
>> IMHO and FWIW this means that prohibition on using flow aware PW in
>> MPLS-TP environments is conditional on meeting specific SLA
>> requirements for the service. So I think that the use case I've
>> presented still holds.
>>
>> Please note also that, regardless of the restriction in draft-ietf-
>> pwe3-fat-pw, be it conditional or absolute, usage of flow labels in an
>> MPLS-TP domain would be perfectly safe if ECMP (i.e., hashing of the
>> label stack and taking one of multiple NHLFEs for the given incoming
>> label in the ILM) were not used in this domain, e.g., by associating
>> exactly one ILM entry with each incoming label in the ILM. And since
>> MPLS-TP is supposed to carry not just PW clients but also IP ones, I
>> would expect that this would be the case in any MPLS-TP deployment.
>>
>> I also think that releasing one restriction (on using GAL in PWs) at
>> the expense of making another, conditional one (on usage of flow labels
>> in MPLS-TP environments) absolute is not the most appropriate method
>> for resolving technical issues. IMHO and FWIW better way to resolve the
>> problem would be by:
>>
>> - releasing the bottom-of-stack requirement on GAL
>> - making use of the statement in RFC 5586 that if GAL is encountered in
>> a packet then G-ACh header MUST be present immediately after the bottom
>> of the label stack (and not immediately after GAL)
>> - specifying that ECMP on labeled packets MUST ignore reserved labels.
>>
>> I think that these considerations have been presented already in the
>> discussion on draft-nadeau-pwe-vccv-2.
>>
>> Of course it would be even better if we could agree on transition to
>> universal usage of the CW and VCCV Type  1 in PWs. But this is a
>> different story.
>>
>> Regards,
>> Sasha
>> ____________________________________
>> From: Luca Martini [lmartini@cisco.com]
>> Sent: Wednesday, August 17, 2011 9:58 PM
>> To: Alexander Vainshtein
>> Cc: Pablo Frank; mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan
>> Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>> Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
>>
>> The solution is quite simple:
>>
>> "Flow Labels MUST not be used in an MPLS-TP environment."
>>
>> Luca
>>
>>
>>
>>
>>
>> On 08/16/11 21:46, Alexander Vainshtein wrote:
>>> Pablo,
>>> Sorry, but I think you're wrong. Only T-PE can insert the flow label
>>> (because only T=PE can be "flow-aware"). S-PE simply performs swap on
>>> PW label.
>>>
>>> Regards,
>>>      Sasha
>>>
>>> ---------------------------------------------------------------------
>> ---
>>> *From:* Pablo Frank [pabloisnot@gmail.com]
>>> *Sent:* Wednesday, August 17, 2011 12:17 AM
>>> *To:* Alexander Vainshtein
>>> *Cc:* ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit;
>>> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>> *Subject:* Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-
>> in-pw
>>> I think it's okay because as the PW crosses the ECMP-enabled IP/MPLS
>>> domain in the middle segment, you're no longer in an MPLS-TP
>>> environment and so the GAL is not required to be BOS.  During that
>>> middle segment, the PW flow label would be placed below the GAL and
>>> above the GACh.  It gets removed when it hits the S-PE that switches
>>> you back into the MPLS-TP environment.  In other words, whether
>> you're
>>> in an MPLS-TP environment is determined segment by segment in a MS-
>> PW.
>>> Pablo
>>>
>>> On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein
>>> <Alexander.Vainshtein@ecitele.com
>>> <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
>>>
>>>     Hi all,
>>>     After having sent out my comments I've noticed that the specific
>>>     example to illustrate the need to combine GAL and "flow label"
>> was
>>>     inaccurate.
>>>
>>>     A more relevant example would look like following (I do not
>>>     include a diagram, but it can be easily provided if necessary)
>>>
>>>      1. A MS-PW:
>>>           * Starts at an S-PE that resides at the edge of an MPLS-TP
>>>             domain (no ECMP)
>>>           * Crosses this domain and enters an IP/MPLS domain with
>> ECMP
>>>             enabled using a T-PE that resides at the age of these two
>>>             domains
>>>           * Leaves this domain and enters a 2nd MPLS-TP domain (using
>>>             the 2nd T-PE)
>>>           * Terminates on another S-PE at the edge of the 2nd MPLS-TP
>>>             domain
>>>      2. The operator intends to improve traffic distribution in the
>>>         IP/MPLS domain, hence he enables insertion and discard of
>>>         "flow labels" at the two S-PEs. Note that:
>>>           * This does not violate the MPLS-TP restriction on ECMP:
>>>             ECMP does not happen in he MPLS-TP domains
>>>           * T-PEs do not even have to be aware of flow labels
>>>      3. The operator also intends to operate some end-to-end OAM for
>>>         this MS-PW using "GAL-in-PW". This results in a conflict
>> since
>>>         both GAL and "flow label" are defined (in the corresponding
>>>         drafts) as bottom of stack.
>>>
>>>
>>>
>>>     IMHO this describes a realistic scenario where the two drafts are
>>>     in controversy.
>>>
>>>     Regards,
>>>          Sasha
>>>     -----------------------------------------------------------------
>> -------
>>>     *From:* mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>
>>>     [mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>] On Behalf
>>>     Of Alexander Vainshtein [Alexander.Vainshtein@ecitele.com
>>>     <mailto:Alexander.Vainshtein@ecitele.com>]
>>>     *Sent:* Tuesday, August 16, 2011 4:26 PM
>>>     *To:* ietf@ietf.org <mailto:ietf@ietf.org>
>>>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; Vladimir Kleiner;
>> Idan
>>>     Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>>     *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-gal-
>> in-pw
>>>     Hi all,
>>>
>>>
>>>
>>>     I would like to raise the following issue with regard to
>>>     draft-ietf-pwe3-gal-in-pw
>>>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-in-
>> pw/?include_text=1>:
>>>     controversy vs. draft-ietf-pwe3-fat-pw
>>>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-
>> pw/?include_text=1>
>>>     with regard to bottom-of-stack position.
>>>
>>>
>>>
>>>     As stated in the Introduction, this draft removes the restriction
>>>     imposed by RFC 5586 on usage of Generic Associated Channel Label
>>>     (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586
>> states:
>>>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
>>>     Concatenated Segments of LSPs, and with Sections, and MUST NOT be
>>>     used with PWs.  It MUST always be at the bottom of the label
>> stack
>>>        (i.e., S bit set to 1).
>>>
>>>
>>>
>>>     draft-ietf-pwe3-gal-in-pw proposed to replace the original text
>> in
>>>     RFC 5586 with the following
>>>
>>>
>>>
>>>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on LSPs,
>>>     Concatenated Segments of LSPs, and with Sections, and MAY be used
>>>     with PWs. It MUST always be at the bottom of the label stack
>>>     (i.e., S bit set to 1).
>>>
>>>
>>>
>>>     I.e.,  while removing this restriction of 5586, it does not
>> modify
>>>     its requirement for the GAL being always at the bottom of the
>>>     label stack.
>>>
>>>
>>>
>>>     At the same draft-ietf-pwe3-fat-pw (currently also in the IESG
>>>     review) reserves the bottom of the PW stack for the PW flow
>>>     labels, e.g., in Section 1.1:
>>>
>>>
>>>
>>>     This document describes a method of adding an additional label
>>>     stack entry (LSE) at the bottom of stack in order to facilitate
>>>     the load balancing of the flows within a PW over the available
>>>     ECMPs.
>>>
>>>
>>>
>>>     One could argue that draft-ietf-pwe3-gal-in-pw only applies to
>>>     MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. IMHO and
>>>     FWIW,
>>>
>>>     such an argument, were it presented, would be highly problematic,
>>>     because:
>>>
>>>
>>>
>>>     1.       RFC 5960 (which defines the MPLS-TP data plane) did not
>>>     define any differences between the PW data plane in IP/MPLS and
>>>     MPLS-TP.
>>>
>>>     2.       One of the most popular scenarios for using multi-
>> segment
>>>     pseudowires is the case when an edge-to-edge service emulation
>>>     crosses multiple IP/MPLS and MPLS-TP domains. In these scenarios,
>>>     the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-
>> aware
>>>     T-PE at the edge of an IP/MPLS domain) would potentially compete
>>>     with GAL (inserted by a T-PE at the edge of an MPLS-TP domain,
>>>     e.g., for relying a PW status message that it has received over a
>>>     Targeted LDP session from the IP/MPLS domain to a static PW
>> status
>>>     message to cross the MPLS-TP domain) for the bottom-of-stack
>>>     position.
>>>
>>>
>>>
>>>     The issue I am raising Is not new. It has been actively discussed
>>>     on the PWE3 mailing list with regard to adoption of
>>>     draft-nadeau-pwe3-vccv-2 as a WG document, with arguments  for
>>>     both the flow label and GAL taking the bottom-of-the-stack
>>>     position. But, to the best of my understanding, consensus on this
>>>     issue has not been reached.
>>>
>>>
>>>
>>>     Hopefully this comment will be useful.
>>>
>>>
>>>
>>>     Regards,
>>>
>>>          Sasha
>>>
>>>
>>>
>>>     This e-mail message is intended for the recipient only and
>>>     contains information which is CONFIDENTIAL and which may be
>>>     proprietary to ECI Telecom. If you have received this
>> transmission
>>>     in error, please inform us by e-mail, phone or fax, and then
>>>     delete the original and all copies thereof.
>>>
>>>     This e-mail message is intended for the recipient only and
>>>     contains information which is CONFIDENTIAL and which may be
>>>     proprietary to ECI Telecom. If you have received this
>> transmission
>>>     in error, please inform us by e-mail, phone or fax, and then
>>>     delete the original and all copies thereof.
>>>
>>>
>>>     _______________________________________________
>>>     pwe3 mailing list
>>>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>>>     https://www.ietf.org/mailman/listinfo/pwe3
>>>
>>>
>>> This e-mail message is intended for the recipient only and contains
>>> information which is CONFIDENTIAL and which may be proprietary to ECI
>>> Telecom. If you have received this transmission in error, please
>>> inform us by e-mail, phone or fax, and then delete the original and
>>> all copies thereof.
>>>
>>>
>>>
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>> This e-mail message is intended for the recipient only and contains
>> information which is CONFIDENTIAL and which may be proprietary to ECI
>> Telecom. If you have received this transmission in error, please inform
>> us by e-mail, phone or fax, and then delete the original and all copies
>> thereof.
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls


From jdrake@juniper.net  Fri Aug 19 13:53:45 2011
Return-Path: <jdrake@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A55F11E8089; Fri, 19 Aug 2011 13:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.814
X-Spam-Level: 
X-Spam-Status: No, score=-5.814 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcPUviMXFZR0; Fri, 19 Aug 2011 13:53:42 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 9C93911E8094; Fri, 19 Aug 2011 13:53:40 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTk7Nc34UT0Ewmjd5ycPk+O8koU+zWBwe@postini.com; Fri, 19 Aug 2011 13:54:40 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Fri, 19 Aug 2011 13:53:22 -0700
From: John E Drake <jdrake@juniper.net>
To: Luca Martini <lmartini@cisco.com>
Date: Fri, 19 Aug 2011 13:53:19 -0700
Subject: RE: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Topic: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxerQwml9gxAd1LS9KD218PXkUzlgABISdA
Message-ID: <5E893DB832F57341992548CDBB333163A0ACE3EB8C@EMBX01-HQ.jnpr.net>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>,  <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>,  <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net> <4E4EC4D2.3070603@cisco.com>
In-Reply-To: <4E4EC4D2.3070603@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 22 Aug 2011 07:16:43 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 20:53:45 -0000

Luca,

So, you are considering weighted ECMP, with FAT and entropy label, to be an=
 application?  We are also releasing the GAL to float until it finds its pr=
oper level within the MPLS label stack?

Thanks,

John

Sent from my iPhone


> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Friday, August 19, 2011 1:17 PM
> To: John E Drake
> Cc: Alexander Vainshtein; mpls@ietf.org; ietf@ietf.org; Vladimir
> Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron;
> Rotem Cohen
> Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-
> gal-in-pw
>
> John,
>
>
> I would like to  let applications decide how they design the use of the
> gal.
>
> So I would propose a simple change , that will move any discussions to
> the specific applications:
>
> The next text would be as follows:
>
>
>
> -  Section 4.2. (GAL Applicability and Usage) in [RFC5586], the
>       original text:
>
>           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>           LSPs, Concatenated Segments of LSPs, and with Sections, and
>           MUST NOT be used with PWs. It MUST always be at the bottom of
>           the label stack (i.e., S bit set to 1). However, in other
> MPLS
>           environments, this document places no restrictions on where
>           the GAL may appear within the label stack or its use with
> PWs.
>
>       is replaced by:
>
>           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>           LSPs, Concatenated Segments of LSPs, and with Sections, and
>           MAY be used with PWs.
>
>
>
> Does this work ?
> Thanks.
> Luca
>
>
>
>
>
>
> On 08/18/11 08:00, John E Drake wrote:
> > Sasha,
> >
> > I completely agree with your recommendations:
> >
> > - releasing the bottom-of-stack requirement on GAL
> >
> > - making use of the statement in RFC 5586 that if GAL is encountered
> in a packet then G-ACh header MUST be present immediately after the
> bottom of the label stack (and not immediately after GAL)
> >
> > - specifying that ECMP on labeled packets MUST ignore reserved labels
> >
> > Thanks,
> >
> > John
> >
> > Sent from my iPhone
> >
> >> -----Original Message-----
> >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
> Of
> >> Alexander Vainshtein
> >> Sent: Wednesday, August 17, 2011 9:52 PM
> >> To: Luca Martini
> >> Cc: mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit;
> >> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> >> Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-
> pwe3-
> >> gal-in-pw
> >>
> >> Luca and all,
> >> I have not found the statement you've proposed in draft-ietf-pwe3-
> fat-
> >> pw-06. Instead, it contans the following text in Section 8.5 "
> >> Applicability to MPLS-TP":
> >>
> >> <quote>
> >>    The flow aware transport of a PW reorders packets, therefore MUST
> >> NOT be
> >>    deployed in a network conforming to the MPLS-TP unless these
> >> integrity requirements
> >>    specified in the SLA can be satisfied.
> >> <end quote>
> >>
> >> (In the -07 version this text is repeated but followed by an
> incomplete
> >> statement " In a" immediately followed by the heading of Section
> 8.6.
> >> Since this addition is difficult to parse, I will ignore it for the
> >> moment.)
> >>
> >> IMHO and FWIW this means that prohibition on using flow aware PW in
> >> MPLS-TP environments is conditional on meeting specific SLA
> >> requirements for the service. So I think that the use case I've
> >> presented still holds.
> >>
> >> Please note also that, regardless of the restriction in draft-ietf-
> >> pwe3-fat-pw, be it conditional or absolute, usage of flow labels in
> an
> >> MPLS-TP domain would be perfectly safe if ECMP (i.e., hashing of the
> >> label stack and taking one of multiple NHLFEs for the given incoming
> >> label in the ILM) were not used in this domain, e.g., by associating
> >> exactly one ILM entry with each incoming label in the ILM. And since
> >> MPLS-TP is supposed to carry not just PW clients but also IP ones, I
> >> would expect that this would be the case in any MPLS-TP deployment.
> >>
> >> I also think that releasing one restriction (on using GAL in PWs) at
> >> the expense of making another, conditional one (on usage of flow
> labels
> >> in MPLS-TP environments) absolute is not the most appropriate method
> >> for resolving technical issues. IMHO and FWIW better way to resolve
> the
> >> problem would be by:
> >>
> >> - releasing the bottom-of-stack requirement on GAL
> >> - making use of the statement in RFC 5586 that if GAL is encountered
> in
> >> a packet then G-ACh header MUST be present immediately after the
> bottom
> >> of the label stack (and not immediately after GAL)
> >> - specifying that ECMP on labeled packets MUST ignore reserved
> labels.
> >>
> >> I think that these considerations have been presented already in the
> >> discussion on draft-nadeau-pwe-vccv-2.
> >>
> >> Of course it would be even better if we could agree on transition to
> >> universal usage of the CW and VCCV Type  1 in PWs. But this is a
> >> different story.
> >>
> >> Regards,
> >> Sasha
> >> ____________________________________
> >> From: Luca Martini [lmartini@cisco.com]
> >> Sent: Wednesday, August 17, 2011 9:58 PM
> >> To: Alexander Vainshtein
> >> Cc: Pablo Frank; mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner;
> Idan
> >> Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> >> Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-
> in-pw
> >>
> >> The solution is quite simple:
> >>
> >> "Flow Labels MUST not be used in an MPLS-TP environment."
> >>
> >> Luca
> >>
> >>
> >>
> >>
> >>
> >> On 08/16/11 21:46, Alexander Vainshtein wrote:
> >>> Pablo,
> >>> Sorry, but I think you're wrong. Only T-PE can insert the flow
> label
> >>> (because only T=3DPE can be "flow-aware"). S-PE simply performs swap
> on
> >>> PW label.
> >>>
> >>> Regards,
> >>>      Sasha
> >>>
> >>> -------------------------------------------------------------------
> --
> >> ---
> >>> *From:* Pablo Frank [pabloisnot@gmail.com]
> >>> *Sent:* Wednesday, August 17, 2011 12:17 AM
> >>> *To:* Alexander Vainshtein
> >>> *Cc:* ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit;
> >>> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
> >>> *Subject:* Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-
> gal-
> >> in-pw
> >>> I think it's okay because as the PW crosses the ECMP-enabled
> IP/MPLS
> >>> domain in the middle segment, you're no longer in an MPLS-TP
> >>> environment and so the GAL is not required to be BOS.  During that
> >>> middle segment, the PW flow label would be placed below the GAL and
> >>> above the GACh.  It gets removed when it hits the S-PE that
> switches
> >>> you back into the MPLS-TP environment.  In other words, whether
> >> you're
> >>> in an MPLS-TP environment is determined segment by segment in a MS-
> >> PW.
> >>> Pablo
> >>>
> >>> On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein
> >>> <Alexander.Vainshtein@ecitele.com
> >>> <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
> >>>
> >>>     Hi all,
> >>>     After having sent out my comments I've noticed that the
> specific
> >>>     example to illustrate the need to combine GAL and "flow label"
> >> was
> >>>     inaccurate.
> >>>
> >>>     A more relevant example would look like following (I do not
> >>>     include a diagram, but it can be easily provided if necessary)
> >>>
> >>>      1. A MS-PW:
> >>>           * Starts at an S-PE that resides at the edge of an MPLS-
> TP
> >>>             domain (no ECMP)
> >>>           * Crosses this domain and enters an IP/MPLS domain with
> >> ECMP
> >>>             enabled using a T-PE that resides at the age of these
> two
> >>>             domains
> >>>           * Leaves this domain and enters a 2nd MPLS-TP domain
> (using
> >>>             the 2nd T-PE)
> >>>           * Terminates on another S-PE at the edge of the 2nd MPLS-
> TP
> >>>             domain
> >>>      2. The operator intends to improve traffic distribution in the
> >>>         IP/MPLS domain, hence he enables insertion and discard of
> >>>         "flow labels" at the two S-PEs. Note that:
> >>>           * This does not violate the MPLS-TP restriction on ECMP:
> >>>             ECMP does not happen in he MPLS-TP domains
> >>>           * T-PEs do not even have to be aware of flow labels
> >>>      3. The operator also intends to operate some end-to-end OAM
> for
> >>>         this MS-PW using "GAL-in-PW". This results in a conflict
> >> since
> >>>         both GAL and "flow label" are defined (in the corresponding
> >>>         drafts) as bottom of stack.
> >>>
> >>>
> >>>
> >>>     IMHO this describes a realistic scenario where the two drafts
> are
> >>>     in controversy.
> >>>
> >>>     Regards,
> >>>          Sasha
> >>>     ---------------------------------------------------------------
> --
> >> -------
> >>>     *From:* mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>
> >>>     [mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>] On
> Behalf
> >>>     Of Alexander Vainshtein [Alexander.Vainshtein@ecitele.com
> >>>     <mailto:Alexander.Vainshtein@ecitele.com>]
> >>>     *Sent:* Tuesday, August 16, 2011 4:26 PM
> >>>     *To:* ietf@ietf.org <mailto:ietf@ietf.org>
> >>>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; Vladimir Kleiner;
> >> Idan
> >>>     Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem
> Cohen
> >>>     *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-
> gal-
> >> in-pw
> >>>     Hi all,
> >>>
> >>>
> >>>
> >>>     I would like to raise the following issue with regard to
> >>>     draft-ietf-pwe3-gal-in-pw
> >>>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-
> in-
> >> pw/?include_text=3D1>:
> >>>     controversy vs. draft-ietf-pwe3-fat-pw
> >>>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-
> >> pw/?include_text=3D1>
> >>>     with regard to bottom-of-stack position.
> >>>
> >>>
> >>>
> >>>     As stated in the Introduction, this draft removes the
> restriction
> >>>     imposed by RFC 5586 on usage of Generic Associated Channel
> Label
> >>>     (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586
> >> states:
> >>>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> LSPs,
> >>>     Concatenated Segments of LSPs, and with Sections, and MUST NOT
> be
> >>>     used with PWs.  It MUST always be at the bottom of the label
> >> stack
> >>>        (i.e., S bit set to 1).
> >>>
> >>>
> >>>
> >>>     draft-ietf-pwe3-gal-in-pw proposed to replace the original text
> >> in
> >>>     RFC 5586 with the following
> >>>
> >>>
> >>>
> >>>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
> LSPs,
> >>>     Concatenated Segments of LSPs, and with Sections, and MAY be
> used
> >>>     with PWs. It MUST always be at the bottom of the label stack
> >>>     (i.e., S bit set to 1).
> >>>
> >>>
> >>>
> >>>     I.e.,  while removing this restriction of 5586, it does not
> >> modify
> >>>     its requirement for the GAL being always at the bottom of the
> >>>     label stack.
> >>>
> >>>
> >>>
> >>>     At the same draft-ietf-pwe3-fat-pw (currently also in the IESG
> >>>     review) reserves the bottom of the PW stack for the PW flow
> >>>     labels, e.g., in Section 1.1:
> >>>
> >>>
> >>>
> >>>     This document describes a method of adding an additional label
> >>>     stack entry (LSE) at the bottom of stack in order to facilitate
> >>>     the load balancing of the flows within a PW over the available
> >>>     ECMPs.
> >>>
> >>>
> >>>
> >>>     One could argue that draft-ietf-pwe3-gal-in-pw only applies to
> >>>     MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. IMHO
> and
> >>>     FWIW,
> >>>
> >>>     such an argument, were it presented, would be highly
> problematic,
> >>>     because:
> >>>
> >>>
> >>>
> >>>     1.       RFC 5960 (which defines the MPLS-TP data plane) did
> not
> >>>     define any differences between the PW data plane in IP/MPLS and
> >>>     MPLS-TP.
> >>>
> >>>     2.       One of the most popular scenarios for using multi-
> >> segment
> >>>     pseudowires is the case when an edge-to-edge service emulation
> >>>     crosses multiple IP/MPLS and MPLS-TP domains. In these
> scenarios,
> >>>     the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-
> >> aware
> >>>     T-PE at the edge of an IP/MPLS domain) would potentially
> compete
> >>>     with GAL (inserted by a T-PE at the edge of an MPLS-TP domain,
> >>>     e.g., for relying a PW status message that it has received over
> a
> >>>     Targeted LDP session from the IP/MPLS domain to a static PW
> >> status
> >>>     message to cross the MPLS-TP domain) for the bottom-of-stack
> >>>     position.
> >>>
> >>>
> >>>
> >>>     The issue I am raising Is not new. It has been actively
> discussed
> >>>     on the PWE3 mailing list with regard to adoption of
> >>>     draft-nadeau-pwe3-vccv-2 as a WG document, with arguments  for
> >>>     both the flow label and GAL taking the bottom-of-the-stack
> >>>     position. But, to the best of my understanding, consensus on
> this
> >>>     issue has not been reached.
> >>>
> >>>
> >>>
> >>>     Hopefully this comment will be useful.
> >>>
> >>>
> >>>
> >>>     Regards,
> >>>
> >>>          Sasha
> >>>
> >>>
> >>>
> >>>     This e-mail message is intended for the recipient only and
> >>>     contains information which is CONFIDENTIAL and which may be
> >>>     proprietary to ECI Telecom. If you have received this
> >> transmission
> >>>     in error, please inform us by e-mail, phone or fax, and then
> >>>     delete the original and all copies thereof.
> >>>
> >>>     This e-mail message is intended for the recipient only and
> >>>     contains information which is CONFIDENTIAL and which may be
> >>>     proprietary to ECI Telecom. If you have received this
> >> transmission
> >>>     in error, please inform us by e-mail, phone or fax, and then
> >>>     delete the original and all copies thereof.
> >>>
> >>>
> >>>     _______________________________________________
> >>>     pwe3 mailing list
> >>>     pwe3@ietf.org <mailto:pwe3@ietf.org>
> >>>     https://www.ietf.org/mailman/listinfo/pwe3
> >>>
> >>>
> >>> This e-mail message is intended for the recipient only and contains
> >>> information which is CONFIDENTIAL and which may be proprietary to
> ECI
> >>> Telecom. If you have received this transmission in error, please
> >>> inform us by e-mail, phone or fax, and then delete the original and
> >>> all copies thereof.
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Ietf mailing list
> >>> Ietf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/ietf
> >> This e-mail message is intended for the recipient only and contains
> >> information which is CONFIDENTIAL and which may be proprietary to
> ECI
> >> Telecom. If you have received this transmission in error, please
> inform
> >> us by e-mail, phone or fax, and then delete the original and all
> copies
> >> thereof.
> >>
> >> _______________________________________________
> >> mpls mailing list
> >> mpls@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mpls


From lmartini@cisco.com  Fri Aug 19 14:08:19 2011
Return-Path: <lmartini@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7621F0C46; Fri, 19 Aug 2011 14:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.179
X-Spam-Level: 
X-Spam-Status: No, score=-2.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENWOP9XxIHjK; Fri, 19 Aug 2011 14:08:18 -0700 (PDT)
Received: from napoleon.monoski.com (napoleon.monoski.com [70.90.113.113]) by ietfa.amsl.com (Postfix) with ESMTP id DF1FF1F0C44; Fri, 19 Aug 2011 14:08:17 -0700 (PDT)
Received: from confusion.monoski.com (confusion.monoski.com [209.245.27.2]) (authenticated bits=0) by napoleon.monoski.com (8.13.8/8.13.8) with ESMTP id p7JL9Cp4006137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Aug 2011 15:09:12 -0600 (MDT)
Message-ID: <4E4ED0F8.3050003@cisco.com>
Date: Fri, 19 Aug 2011 15:09:12 -0600
From: Luca Martini <lmartini@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>, <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net> <4E4EC4D2.3070603@cisco.com> <5E893DB832F57341992548CDBB333163A0ACE3EB8C@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A0ACE3EB8C@EMBX01-HQ.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 22 Aug 2011 07:16:43 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 21:08:19 -0000

On 08/19/11 14:53, John E Drake wrote:
> Luca,
>
> So, you are considering weighted ECMP, with FAT and entropy label, to be an application?  We are also releasing the GAL to float until it finds its proper level within the MPLS label stack?
Yes. It certainly addresses a specific problem that is only a concern in
some networks.
Maybe as application I meant the specific technology documents. For
example if an OAM method needs to use the GAL for a specific purpose it
should specify it there, without us putting restrictions in a generic
way in this document.

As for the float part, I consider the GAL to be a simple Flag that says
" following the MPLS label stack , you will find a GACh construct , and
not an IP packet"

In MPLS the default is to have an IP packet, unless a different meaning
is bound to the label by the control plane. Thsi is the reason we needed
the GAL in the first place for the MPLS-TP environment , where IP is not
used.

Thanks,
Luca

> Thanks,
>
> John
>
> Sent from my iPhone
>
>
>> -----Original Message-----
>> From: Luca Martini [mailto:lmartini@cisco.com]
>> Sent: Friday, August 19, 2011 1:17 PM
>> To: John E Drake
>> Cc: Alexander Vainshtein; mpls@ietf.org; ietf@ietf.org; Vladimir
>> Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron;
>> Rotem Cohen
>> Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-
>> gal-in-pw
>>
>> John,
>>
>>
>> I would like to  let applications decide how they design the use of the
>> gal.
>>
>> So I would propose a simple change , that will move any discussions to
>> the specific applications:
>>
>> The next text would be as follows:
>>
>>
>>
>> -  Section 4.2. (GAL Applicability and Usage) in [RFC5586], the
>>       original text:
>>
>>           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>>           LSPs, Concatenated Segments of LSPs, and with Sections, and
>>           MUST NOT be used with PWs. It MUST always be at the bottom of
>>           the label stack (i.e., S bit set to 1). However, in other
>> MPLS
>>           environments, this document places no restrictions on where
>>           the GAL may appear within the label stack or its use with
>> PWs.
>>
>>       is replaced by:
>>
>>           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>>           LSPs, Concatenated Segments of LSPs, and with Sections, and
>>           MAY be used with PWs.
>>
>>
>>
>> Does this work ?
>> Thanks.
>> Luca
>>
>>
>>
>>
>>
>>
>> On 08/18/11 08:00, John E Drake wrote:
>>> Sasha,
>>>
>>> I completely agree with your recommendations:
>>>
>>> - releasing the bottom-of-stack requirement on GAL
>>>
>>> - making use of the statement in RFC 5586 that if GAL is encountered
>> in a packet then G-ACh header MUST be present immediately after the
>> bottom of the label stack (and not immediately after GAL)
>>> - specifying that ECMP on labeled packets MUST ignore reserved labels
>>>
>>> Thanks,
>>>
>>> John
>>>
>>> Sent from my iPhone
>>>
>>>> -----Original Message-----
>>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf
>> Of
>>>> Alexander Vainshtein
>>>> Sent: Wednesday, August 17, 2011 9:52 PM
>>>> To: Luca Martini
>>>> Cc: mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit;
>>>> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>>> Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-
>> pwe3-
>>>> gal-in-pw
>>>>
>>>> Luca and all,
>>>> I have not found the statement you've proposed in draft-ietf-pwe3-
>> fat-
>>>> pw-06. Instead, it contans the following text in Section 8.5 "
>>>> Applicability to MPLS-TP":
>>>>
>>>> <quote>
>>>>    The flow aware transport of a PW reorders packets, therefore MUST
>>>> NOT be
>>>>    deployed in a network conforming to the MPLS-TP unless these
>>>> integrity requirements
>>>>    specified in the SLA can be satisfied.
>>>> <end quote>
>>>>
>>>> (In the -07 version this text is repeated but followed by an
>> incomplete
>>>> statement " In a" immediately followed by the heading of Section
>> 8.6.
>>>> Since this addition is difficult to parse, I will ignore it for the
>>>> moment.)
>>>>
>>>> IMHO and FWIW this means that prohibition on using flow aware PW in
>>>> MPLS-TP environments is conditional on meeting specific SLA
>>>> requirements for the service. So I think that the use case I've
>>>> presented still holds.
>>>>
>>>> Please note also that, regardless of the restriction in draft-ietf-
>>>> pwe3-fat-pw, be it conditional or absolute, usage of flow labels in
>> an
>>>> MPLS-TP domain would be perfectly safe if ECMP (i.e., hashing of the
>>>> label stack and taking one of multiple NHLFEs for the given incoming
>>>> label in the ILM) were not used in this domain, e.g., by associating
>>>> exactly one ILM entry with each incoming label in the ILM. And since
>>>> MPLS-TP is supposed to carry not just PW clients but also IP ones, I
>>>> would expect that this would be the case in any MPLS-TP deployment.
>>>>
>>>> I also think that releasing one restriction (on using GAL in PWs) at
>>>> the expense of making another, conditional one (on usage of flow
>> labels
>>>> in MPLS-TP environments) absolute is not the most appropriate method
>>>> for resolving technical issues. IMHO and FWIW better way to resolve
>> the
>>>> problem would be by:
>>>>
>>>> - releasing the bottom-of-stack requirement on GAL
>>>> - making use of the statement in RFC 5586 that if GAL is encountered
>> in
>>>> a packet then G-ACh header MUST be present immediately after the
>> bottom
>>>> of the label stack (and not immediately after GAL)
>>>> - specifying that ECMP on labeled packets MUST ignore reserved
>> labels.
>>>> I think that these considerations have been presented already in the
>>>> discussion on draft-nadeau-pwe-vccv-2.
>>>>
>>>> Of course it would be even better if we could agree on transition to
>>>> universal usage of the CW and VCCV Type  1 in PWs. But this is a
>>>> different story.
>>>>
>>>> Regards,
>>>> Sasha
>>>> ____________________________________
>>>> From: Luca Martini [lmartini@cisco.com]
>>>> Sent: Wednesday, August 17, 2011 9:58 PM
>>>> To: Alexander Vainshtein
>>>> Cc: Pablo Frank; mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner;
>> Idan
>>>> Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>>> Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-
>> in-pw
>>>> The solution is quite simple:
>>>>
>>>> "Flow Labels MUST not be used in an MPLS-TP environment."
>>>>
>>>> Luca
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 08/16/11 21:46, Alexander Vainshtein wrote:
>>>>> Pablo,
>>>>> Sorry, but I think you're wrong. Only T-PE can insert the flow
>> label
>>>>> (because only T=PE can be "flow-aware"). S-PE simply performs swap
>> on
>>>>> PW label.
>>>>>
>>>>> Regards,
>>>>>      Sasha
>>>>>
>>>>> -------------------------------------------------------------------
>> --
>>>> ---
>>>>> *From:* Pablo Frank [pabloisnot@gmail.com]
>>>>> *Sent:* Wednesday, August 17, 2011 12:17 AM
>>>>> *To:* Alexander Vainshtein
>>>>> *Cc:* ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan Kaspit;
>>>>> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>>>> *Subject:* Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-
>> gal-
>>>> in-pw
>>>>> I think it's okay because as the PW crosses the ECMP-enabled
>> IP/MPLS
>>>>> domain in the middle segment, you're no longer in an MPLS-TP
>>>>> environment and so the GAL is not required to be BOS.  During that
>>>>> middle segment, the PW flow label would be placed below the GAL and
>>>>> above the GACh.  It gets removed when it hits the S-PE that
>> switches
>>>>> you back into the MPLS-TP environment.  In other words, whether
>>>> you're
>>>>> in an MPLS-TP environment is determined segment by segment in a MS-
>>>> PW.
>>>>> Pablo
>>>>>
>>>>> On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein
>>>>> <Alexander.Vainshtein@ecitele.com
>>>>> <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
>>>>>
>>>>>     Hi all,
>>>>>     After having sent out my comments I've noticed that the
>> specific
>>>>>     example to illustrate the need to combine GAL and "flow label"
>>>> was
>>>>>     inaccurate.
>>>>>
>>>>>     A more relevant example would look like following (I do not
>>>>>     include a diagram, but it can be easily provided if necessary)
>>>>>
>>>>>      1. A MS-PW:
>>>>>           * Starts at an S-PE that resides at the edge of an MPLS-
>> TP
>>>>>             domain (no ECMP)
>>>>>           * Crosses this domain and enters an IP/MPLS domain with
>>>> ECMP
>>>>>             enabled using a T-PE that resides at the age of these
>> two
>>>>>             domains
>>>>>           * Leaves this domain and enters a 2nd MPLS-TP domain
>> (using
>>>>>             the 2nd T-PE)
>>>>>           * Terminates on another S-PE at the edge of the 2nd MPLS-
>> TP
>>>>>             domain
>>>>>      2. The operator intends to improve traffic distribution in the
>>>>>         IP/MPLS domain, hence he enables insertion and discard of
>>>>>         "flow labels" at the two S-PEs. Note that:
>>>>>           * This does not violate the MPLS-TP restriction on ECMP:
>>>>>             ECMP does not happen in he MPLS-TP domains
>>>>>           * T-PEs do not even have to be aware of flow labels
>>>>>      3. The operator also intends to operate some end-to-end OAM
>> for
>>>>>         this MS-PW using "GAL-in-PW". This results in a conflict
>>>> since
>>>>>         both GAL and "flow label" are defined (in the corresponding
>>>>>         drafts) as bottom of stack.
>>>>>
>>>>>
>>>>>
>>>>>     IMHO this describes a realistic scenario where the two drafts
>> are
>>>>>     in controversy.
>>>>>
>>>>>     Regards,
>>>>>          Sasha
>>>>>     ---------------------------------------------------------------
>> --
>>>> -------
>>>>>     *From:* mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>
>>>>>     [mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>] On
>> Behalf
>>>>>     Of Alexander Vainshtein [Alexander.Vainshtein@ecitele.com
>>>>>     <mailto:Alexander.Vainshtein@ecitele.com>]
>>>>>     *Sent:* Tuesday, August 16, 2011 4:26 PM
>>>>>     *To:* ietf@ietf.org <mailto:ietf@ietf.org>
>>>>>     *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; Vladimir Kleiner;
>>>> Idan
>>>>>     Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem
>> Cohen
>>>>>     *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-
>> gal-
>>>> in-pw
>>>>>     Hi all,
>>>>>
>>>>>
>>>>>
>>>>>     I would like to raise the following issue with regard to
>>>>>     draft-ietf-pwe3-gal-in-pw
>>>>>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-
>> in-
>>>> pw/?include_text=1>:
>>>>>     controversy vs. draft-ietf-pwe3-fat-pw
>>>>>     <http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-
>>>> pw/?include_text=1>
>>>>>     with regard to bottom-of-stack position.
>>>>>
>>>>>
>>>>>
>>>>>     As stated in the Introduction, this draft removes the
>> restriction
>>>>>     imposed by RFC 5586 on usage of Generic Associated Channel
>> Label
>>>>>     (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586
>>>> states:
>>>>>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>> LSPs,
>>>>>     Concatenated Segments of LSPs, and with Sections, and MUST NOT
>> be
>>>>>     used with PWs.  It MUST always be at the bottom of the label
>>>> stack
>>>>>        (i.e., S bit set to 1).
>>>>>
>>>>>
>>>>>
>>>>>     draft-ietf-pwe3-gal-in-pw proposed to replace the original text
>>>> in
>>>>>     RFC 5586 with the following
>>>>>
>>>>>
>>>>>
>>>>>     In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>> LSPs,
>>>>>     Concatenated Segments of LSPs, and with Sections, and MAY be
>> used
>>>>>     with PWs. It MUST always be at the bottom of the label stack
>>>>>     (i.e., S bit set to 1).
>>>>>
>>>>>
>>>>>
>>>>>     I.e.,  while removing this restriction of 5586, it does not
>>>> modify
>>>>>     its requirement for the GAL being always at the bottom of the
>>>>>     label stack.
>>>>>
>>>>>
>>>>>
>>>>>     At the same draft-ietf-pwe3-fat-pw (currently also in the IESG
>>>>>     review) reserves the bottom of the PW stack for the PW flow
>>>>>     labels, e.g., in Section 1.1:
>>>>>
>>>>>
>>>>>
>>>>>     This document describes a method of adding an additional label
>>>>>     stack entry (LSE) at the bottom of stack in order to facilitate
>>>>>     the load balancing of the flows within a PW over the available
>>>>>     ECMPs.
>>>>>
>>>>>
>>>>>
>>>>>     One could argue that draft-ietf-pwe3-gal-in-pw only applies to
>>>>>     MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. IMHO
>> and
>>>>>     FWIW,
>>>>>
>>>>>     such an argument, were it presented, would be highly
>> problematic,
>>>>>     because:
>>>>>
>>>>>
>>>>>
>>>>>     1.       RFC 5960 (which defines the MPLS-TP data plane) did
>> not
>>>>>     define any differences between the PW data plane in IP/MPLS and
>>>>>     MPLS-TP.
>>>>>
>>>>>     2.       One of the most popular scenarios for using multi-
>>>> segment
>>>>>     pseudowires is the case when an edge-to-edge service emulation
>>>>>     crosses multiple IP/MPLS and MPLS-TP domains. In these
>> scenarios,
>>>>>     the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-
>>>> aware
>>>>>     T-PE at the edge of an IP/MPLS domain) would potentially
>> compete
>>>>>     with GAL (inserted by a T-PE at the edge of an MPLS-TP domain,
>>>>>     e.g., for relying a PW status message that it has received over
>> a
>>>>>     Targeted LDP session from the IP/MPLS domain to a static PW
>>>> status
>>>>>     message to cross the MPLS-TP domain) for the bottom-of-stack
>>>>>     position.
>>>>>
>>>>>
>>>>>
>>>>>     The issue I am raising Is not new. It has been actively
>> discussed
>>>>>     on the PWE3 mailing list with regard to adoption of
>>>>>     draft-nadeau-pwe3-vccv-2 as a WG document, with arguments  for
>>>>>     both the flow label and GAL taking the bottom-of-the-stack
>>>>>     position. But, to the best of my understanding, consensus on
>> this
>>>>>     issue has not been reached.
>>>>>
>>>>>
>>>>>
>>>>>     Hopefully this comment will be useful.
>>>>>
>>>>>
>>>>>
>>>>>     Regards,
>>>>>
>>>>>          Sasha
>>>>>
>>>>>
>>>>>
>>>>>     This e-mail message is intended for the recipient only and
>>>>>     contains information which is CONFIDENTIAL and which may be
>>>>>     proprietary to ECI Telecom. If you have received this
>>>> transmission
>>>>>     in error, please inform us by e-mail, phone or fax, and then
>>>>>     delete the original and all copies thereof.
>>>>>
>>>>>     This e-mail message is intended for the recipient only and
>>>>>     contains information which is CONFIDENTIAL and which may be
>>>>>     proprietary to ECI Telecom. If you have received this
>>>> transmission
>>>>>     in error, please inform us by e-mail, phone or fax, and then
>>>>>     delete the original and all copies thereof.
>>>>>
>>>>>
>>>>>     _______________________________________________
>>>>>     pwe3 mailing list
>>>>>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>>>>>     https://www.ietf.org/mailman/listinfo/pwe3
>>>>>
>>>>>
>>>>> This e-mail message is intended for the recipient only and contains
>>>>> information which is CONFIDENTIAL and which may be proprietary to
>> ECI
>>>>> Telecom. If you have received this transmission in error, please
>>>>> inform us by e-mail, phone or fax, and then delete the original and
>>>>> all copies thereof.
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Ietf mailing list
>>>>> Ietf@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ietf
>>>> This e-mail message is intended for the recipient only and contains
>>>> information which is CONFIDENTIAL and which may be proprietary to
>> ECI
>>>> Telecom. If you have received this transmission in error, please
>> inform
>>>> us by e-mail, phone or fax, and then delete the original and all
>> copies
>>>> thereof.
>>>>
>>>> _______________________________________________
>>>> mpls mailing list
>>>> mpls@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mpls
>


From tnadeau@lucidvision.com  Sat Aug 20 05:33:56 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43D3221F86DE; Sat, 20 Aug 2011 05:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.275
X-Spam-Level: 
X-Spam-Status: No, score=-2.275 tagged_above=-999 required=5 tests=[AWL=-0.276, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3z1S6T2nnU55; Sat, 20 Aug 2011 05:33:55 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id BB79321F8634; Sat, 20 Aug 2011 05:33:54 -0700 (PDT)
Received: from [192.168.1.104] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 73A1A1D91DA2; Sat, 20 Aug 2011 08:34:53 -0400 (EDT)
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <4E4ED0F8.3050003@cisco.com>
Date: Sat, 20 Aug 2011 08:34:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <004110D7-3F29-4D1C-9C50-F5053AF408CB@lucidvision.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>, <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net> <4E4EC4D2.3070603@cisco.com> <5E893DB832F57341992548CDBB333163A0ACE3EB8C@EMBX01-HQ.jnpr.net> <4E4ED0F8.3050003@cisco.com>
To: Luca Martini <lmartini@cisco.com>
X-Mailer: Apple Mail (2.1244.3)
X-Mailman-Approved-At: Mon, 22 Aug 2011 07:16:43 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, "mpls@ietf.org" <mpls@ietf.org>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2011 12:33:56 -0000

On Aug 19, 2011, at 5:09 PM, Luca Martini wrote:

> On 08/19/11 14:53, John E Drake wrote:
>> Luca,
>>=20
>> So, you are considering weighted ECMP, with FAT and entropy label, to =
be an application?  We are also releasing the GAL to float until it =
finds its proper level within the MPLS label stack?
> Yes. It certainly addresses a specific problem that is only a concern =
in
> some networks.
> Maybe as application I meant the specific technology documents. For
> example if an OAM method needs to use the GAL for a specific purpose =
it
> should specify it there, without us putting restrictions in a generic
> way in this document.
>=20
> As for the float part, I consider the GAL to be a simple Flag that =
says
> " following the MPLS label stack , you will find a GACh construct , =
and
> not an IP packet"

	This makes a lot of sense to me as it makes sure that the =
specific applications use the GAL as needed. This document should just =
lay out the generic rules for using it, but not preclude its use by some =
application we have not through of yet down the road by making rules =
that are too narrow.

	--Tom


> In MPLS the default is to have an IP packet, unless a different =
meaning
> is bound to the label by the control plane. Thsi is the reason we =
needed
> the GAL in the first place for the MPLS-TP environment , where IP is =
not
> used.
>=20
> Thanks,
> Luca
>=20
>> Thanks,
>>=20
>> John
>>=20
>> Sent from my iPhone
>>=20
>>=20
>>> -----Original Message-----
>>> From: Luca Martini [mailto:lmartini@cisco.com]
>>> Sent: Friday, August 19, 2011 1:17 PM
>>> To: John E Drake
>>> Cc: Alexander Vainshtein; mpls@ietf.org; ietf@ietf.org; Vladimir
>>> Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron;
>>> Rotem Cohen
>>> Subject: Re: [mpls] [PWE3] IETF Last Call comment on =
draft-ietf-pwe3-
>>> gal-in-pw
>>>=20
>>> John,
>>>=20
>>>=20
>>> I would like to  let applications decide how they design the use of =
the
>>> gal.
>>>=20
>>> So I would propose a simple change , that will move any discussions =
to
>>> the specific applications:
>>>=20
>>> The next text would be as follows:
>>>=20
>>>=20
>>>=20
>>> -  Section 4.2. (GAL Applicability and Usage) in [RFC5586], the
>>>      original text:
>>>=20
>>>          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>>>          LSPs, Concatenated Segments of LSPs, and with Sections, and
>>>          MUST NOT be used with PWs. It MUST always be at the bottom =
of
>>>          the label stack (i.e., S bit set to 1). However, in other
>>> MPLS
>>>          environments, this document places no restrictions on where
>>>          the GAL may appear within the label stack or its use with
>>> PWs.
>>>=20
>>>      is replaced by:
>>>=20
>>>          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>>>          LSPs, Concatenated Segments of LSPs, and with Sections, and
>>>          MAY be used with PWs.
>>>=20
>>>=20
>>>=20
>>> Does this work ?
>>> Thanks.
>>> Luca
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> On 08/18/11 08:00, John E Drake wrote:
>>>> Sasha,
>>>>=20
>>>> I completely agree with your recommendations:
>>>>=20
>>>> - releasing the bottom-of-stack requirement on GAL
>>>>=20
>>>> - making use of the statement in RFC 5586 that if GAL is =
encountered
>>> in a packet then G-ACh header MUST be present immediately after the
>>> bottom of the label stack (and not immediately after GAL)
>>>> - specifying that ECMP on labeled packets MUST ignore reserved =
labels
>>>>=20
>>>> Thanks,
>>>>=20
>>>> John
>>>>=20
>>>> Sent from my iPhone
>>>>=20
>>>>> -----Original Message-----
>>>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On =
Behalf
>>> Of
>>>>> Alexander Vainshtein
>>>>> Sent: Wednesday, August 17, 2011 9:52 PM
>>>>> To: Luca Martini
>>>>> Cc: mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner; Idan Kaspit;
>>>>> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>>>> Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-
>>> pwe3-
>>>>> gal-in-pw
>>>>>=20
>>>>> Luca and all,
>>>>> I have not found the statement you've proposed in draft-ietf-pwe3-
>>> fat-
>>>>> pw-06. Instead, it contans the following text in Section 8.5 "
>>>>> Applicability to MPLS-TP":
>>>>>=20
>>>>> <quote>
>>>>>   The flow aware transport of a PW reorders packets, therefore =
MUST
>>>>> NOT be
>>>>>   deployed in a network conforming to the MPLS-TP unless these
>>>>> integrity requirements
>>>>>   specified in the SLA can be satisfied.
>>>>> <end quote>
>>>>>=20
>>>>> (In the -07 version this text is repeated but followed by an
>>> incomplete
>>>>> statement " In a" immediately followed by the heading of Section
>>> 8.6.
>>>>> Since this addition is difficult to parse, I will ignore it for =
the
>>>>> moment.)
>>>>>=20
>>>>> IMHO and FWIW this means that prohibition on using flow aware PW =
in
>>>>> MPLS-TP environments is conditional on meeting specific SLA
>>>>> requirements for the service. So I think that the use case I've
>>>>> presented still holds.
>>>>>=20
>>>>> Please note also that, regardless of the restriction in =
draft-ietf-
>>>>> pwe3-fat-pw, be it conditional or absolute, usage of flow labels =
in
>>> an
>>>>> MPLS-TP domain would be perfectly safe if ECMP (i.e., hashing of =
the
>>>>> label stack and taking one of multiple NHLFEs for the given =
incoming
>>>>> label in the ILM) were not used in this domain, e.g., by =
associating
>>>>> exactly one ILM entry with each incoming label in the ILM. And =
since
>>>>> MPLS-TP is supposed to carry not just PW clients but also IP ones, =
I
>>>>> would expect that this would be the case in any MPLS-TP =
deployment.
>>>>>=20
>>>>> I also think that releasing one restriction (on using GAL in PWs) =
at
>>>>> the expense of making another, conditional one (on usage of flow
>>> labels
>>>>> in MPLS-TP environments) absolute is not the most appropriate =
method
>>>>> for resolving technical issues. IMHO and FWIW better way to =
resolve
>>> the
>>>>> problem would be by:
>>>>>=20
>>>>> - releasing the bottom-of-stack requirement on GAL
>>>>> - making use of the statement in RFC 5586 that if GAL is =
encountered
>>> in
>>>>> a packet then G-ACh header MUST be present immediately after the
>>> bottom
>>>>> of the label stack (and not immediately after GAL)
>>>>> - specifying that ECMP on labeled packets MUST ignore reserved
>>> labels.
>>>>> I think that these considerations have been presented already in =
the
>>>>> discussion on draft-nadeau-pwe-vccv-2.
>>>>>=20
>>>>> Of course it would be even better if we could agree on transition =
to
>>>>> universal usage of the CW and VCCV Type  1 in PWs. But this is a
>>>>> different story.
>>>>>=20
>>>>> Regards,
>>>>> Sasha
>>>>> ____________________________________
>>>>> From: Luca Martini [lmartini@cisco.com]
>>>>> Sent: Wednesday, August 17, 2011 9:58 PM
>>>>> To: Alexander Vainshtein
>>>>> Cc: Pablo Frank; mpls@ietf.org; ietf@ietf.org; Vladimir Kleiner;
>>> Idan
>>>>> Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>>>> Subject: Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-
>>> in-pw
>>>>> The solution is quite simple:
>>>>>=20
>>>>> "Flow Labels MUST not be used in an MPLS-TP environment."
>>>>>=20
>>>>> Luca
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On 08/16/11 21:46, Alexander Vainshtein wrote:
>>>>>> Pablo,
>>>>>> Sorry, but I think you're wrong. Only T-PE can insert the flow
>>> label
>>>>>> (because only T=3DPE can be "flow-aware"). S-PE simply performs =
swap
>>> on
>>>>>> PW label.
>>>>>>=20
>>>>>> Regards,
>>>>>>     Sasha
>>>>>>=20
>>>>>> =
-------------------------------------------------------------------
>>> --
>>>>> ---
>>>>>> *From:* Pablo Frank [pabloisnot@gmail.com]
>>>>>> *Sent:* Wednesday, August 17, 2011 12:17 AM
>>>>>> *To:* Alexander Vainshtein
>>>>>> *Cc:* ietf@ietf.org; mpls@ietf.org; Vladimir Kleiner; Idan =
Kaspit;
>>>>>> Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem Cohen
>>>>>> *Subject:* Re: [PWE3] IETF Last Call comment on draft-ietf-pwe3-
>>> gal-
>>>>> in-pw
>>>>>> I think it's okay because as the PW crosses the ECMP-enabled
>>> IP/MPLS
>>>>>> domain in the middle segment, you're no longer in an MPLS-TP
>>>>>> environment and so the GAL is not required to be BOS.  During =
that
>>>>>> middle segment, the PW flow label would be placed below the GAL =
and
>>>>>> above the GACh.  It gets removed when it hits the S-PE that
>>> switches
>>>>>> you back into the MPLS-TP environment.  In other words, whether
>>>>> you're
>>>>>> in an MPLS-TP environment is determined segment by segment in a =
MS-
>>>>> PW.
>>>>>> Pablo
>>>>>>=20
>>>>>> On Tue, Aug 16, 2011 at 1:02 PM, Alexander Vainshtein
>>>>>> <Alexander.Vainshtein@ecitele.com
>>>>>> <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
>>>>>>=20
>>>>>>    Hi all,
>>>>>>    After having sent out my comments I've noticed that the
>>> specific
>>>>>>    example to illustrate the need to combine GAL and "flow label"
>>>>> was
>>>>>>    inaccurate.
>>>>>>=20
>>>>>>    A more relevant example would look like following (I do not
>>>>>>    include a diagram, but it can be easily provided if necessary)
>>>>>>=20
>>>>>>     1. A MS-PW:
>>>>>>          * Starts at an S-PE that resides at the edge of an MPLS-
>>> TP
>>>>>>            domain (no ECMP)
>>>>>>          * Crosses this domain and enters an IP/MPLS domain with
>>>>> ECMP
>>>>>>            enabled using a T-PE that resides at the age of these
>>> two
>>>>>>            domains
>>>>>>          * Leaves this domain and enters a 2nd MPLS-TP domain
>>> (using
>>>>>>            the 2nd T-PE)
>>>>>>          * Terminates on another S-PE at the edge of the 2nd =
MPLS-
>>> TP
>>>>>>            domain
>>>>>>     2. The operator intends to improve traffic distribution in =
the
>>>>>>        IP/MPLS domain, hence he enables insertion and discard of
>>>>>>        "flow labels" at the two S-PEs. Note that:
>>>>>>          * This does not violate the MPLS-TP restriction on ECMP:
>>>>>>            ECMP does not happen in he MPLS-TP domains
>>>>>>          * T-PEs do not even have to be aware of flow labels
>>>>>>     3. The operator also intends to operate some end-to-end OAM
>>> for
>>>>>>        this MS-PW using "GAL-in-PW". This results in a conflict
>>>>> since
>>>>>>        both GAL and "flow label" are defined (in the =
corresponding
>>>>>>        drafts) as bottom of stack.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    IMHO this describes a realistic scenario where the two drafts
>>> are
>>>>>>    in controversy.
>>>>>>=20
>>>>>>    Regards,
>>>>>>         Sasha
>>>>>>    =
---------------------------------------------------------------
>>> --
>>>>> -------
>>>>>>    *From:* mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>
>>>>>>    [mpls-bounces@ietf.org <mailto:mpls-bounces@ietf.org>] On
>>> Behalf
>>>>>>    Of Alexander Vainshtein [Alexander.Vainshtein@ecitele.com
>>>>>>    <mailto:Alexander.Vainshtein@ecitele.com>]
>>>>>>    *Sent:* Tuesday, August 16, 2011 4:26 PM
>>>>>>    *To:* ietf@ietf.org <mailto:ietf@ietf.org>
>>>>>>    *Cc:* mpls@ietf.org <mailto:mpls@ietf.org>; Vladimir Kleiner;
>>>>> Idan
>>>>>>    Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem
>>> Cohen
>>>>>>    *Subject:* [mpls] IETF Last Call comment on draft-ietf-pwe3-
>>> gal-
>>>>> in-pw
>>>>>>    Hi all,
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    I would like to raise the following issue with regard to
>>>>>>    draft-ietf-pwe3-gal-in-pw
>>>>>>    <http://datatracker.ietf.org/doc/draft-ietf-pwe3-mpls-tp-gal-
>>> in-
>>>>> pw/?include_text=3D1>:
>>>>>>    controversy vs. draft-ietf-pwe3-fat-pw
>>>>>>    <http://datatracker.ietf.org/doc/draft-ietf-pwe3-fat-
>>>>> pw/?include_text=3D1>
>>>>>>    with regard to bottom-of-stack position.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    As stated in the Introduction, this draft removes the
>>> restriction
>>>>>>    imposed by RFC 5586 on usage of Generic Associated Channel
>>> Label
>>>>>>    (GAL) in PWs. The corresponding text Section 4.2 of RFC 5586
>>>>> states:
>>>>>>    In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>>> LSPs,
>>>>>>    Concatenated Segments of LSPs, and with Sections, and MUST NOT
>>> be
>>>>>>    used with PWs.  It MUST always be at the bottom of the label
>>>>> stack
>>>>>>       (i.e., S bit set to 1).
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    draft-ietf-pwe3-gal-in-pw proposed to replace the original =
text
>>>>> in
>>>>>>    RFC 5586 with the following
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
>>> LSPs,
>>>>>>    Concatenated Segments of LSPs, and with Sections, and MAY be
>>> used
>>>>>>    with PWs. It MUST always be at the bottom of the label stack
>>>>>>    (i.e., S bit set to 1).
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    I.e.,  while removing this restriction of 5586, it does not
>>>>> modify
>>>>>>    its requirement for the GAL being always at the bottom of the
>>>>>>    label stack.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    At the same draft-ietf-pwe3-fat-pw (currently also in the IESG
>>>>>>    review) reserves the bottom of the PW stack for the PW flow
>>>>>>    labels, e.g., in Section 1.1:
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    This document describes a method of adding an additional label
>>>>>>    stack entry (LSE) at the bottom of stack in order to =
facilitate
>>>>>>    the load balancing of the flows within a PW over the available
>>>>>>    ECMPs.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    One could argue that draft-ietf-pwe3-gal-in-pw only applies to
>>>>>>    MPLS-TP pseudowires, and that MPLS-TP does not use ECMP. IMHO
>>> and
>>>>>>    FWIW,
>>>>>>=20
>>>>>>    such an argument, were it presented, would be highly
>>> problematic,
>>>>>>    because:
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    1.       RFC 5960 (which defines the MPLS-TP data plane) did
>>> not
>>>>>>    define any differences between the PW data plane in IP/MPLS =
and
>>>>>>    MPLS-TP.
>>>>>>=20
>>>>>>    2.       One of the most popular scenarios for using multi-
>>>>> segment
>>>>>>    pseudowires is the case when an edge-to-edge service emulation
>>>>>>    crosses multiple IP/MPLS and MPLS-TP domains. In these
>>> scenarios,
>>>>>>    the flow label of draft-ietf-pwe3-fat-pw (inserted by a flow-
>>>>> aware
>>>>>>    T-PE at the edge of an IP/MPLS domain) would potentially
>>> compete
>>>>>>    with GAL (inserted by a T-PE at the edge of an MPLS-TP domain,
>>>>>>    e.g., for relying a PW status message that it has received =
over
>>> a
>>>>>>    Targeted LDP session from the IP/MPLS domain to a static PW
>>>>> status
>>>>>>    message to cross the MPLS-TP domain) for the bottom-of-stack
>>>>>>    position.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    The issue I am raising Is not new. It has been actively
>>> discussed
>>>>>>    on the PWE3 mailing list with regard to adoption of
>>>>>>    draft-nadeau-pwe3-vccv-2 as a WG document, with arguments  for
>>>>>>    both the flow label and GAL taking the bottom-of-the-stack
>>>>>>    position. But, to the best of my understanding, consensus on
>>> this
>>>>>>    issue has not been reached.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    Hopefully this comment will be useful.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    Regards,
>>>>>>=20
>>>>>>         Sasha
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>    This e-mail message is intended for the recipient only and
>>>>>>    contains information which is CONFIDENTIAL and which may be
>>>>>>    proprietary to ECI Telecom. If you have received this
>>>>> transmission
>>>>>>    in error, please inform us by e-mail, phone or fax, and then
>>>>>>    delete the original and all copies thereof.
>>>>>>=20
>>>>>>    This e-mail message is intended for the recipient only and
>>>>>>    contains information which is CONFIDENTIAL and which may be
>>>>>>    proprietary to ECI Telecom. If you have received this
>>>>> transmission
>>>>>>    in error, please inform us by e-mail, phone or fax, and then
>>>>>>    delete the original and all copies thereof.
>>>>>>=20
>>>>>>=20
>>>>>>    _______________________________________________
>>>>>>    pwe3 mailing list
>>>>>>    pwe3@ietf.org <mailto:pwe3@ietf.org>
>>>>>>    https://www.ietf.org/mailman/listinfo/pwe3
>>>>>>=20
>>>>>>=20
>>>>>> This e-mail message is intended for the recipient only and =
contains
>>>>>> information which is CONFIDENTIAL and which may be proprietary to
>>> ECI
>>>>>> Telecom. If you have received this transmission in error, please
>>>>>> inform us by e-mail, phone or fax, and then delete the original =
and
>>>>>> all copies thereof.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> Ietf mailing list
>>>>>> Ietf@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/ietf
>>>>> This e-mail message is intended for the recipient only and =
contains
>>>>> information which is CONFIDENTIAL and which may be proprietary to
>>> ECI
>>>>> Telecom. If you have received this transmission in error, please
>>> inform
>>>>> us by e-mail, phone or fax, and then delete the original and all
>>> copies
>>>>> thereof.
>>>>>=20
>>>>> _______________________________________________
>>>>> mpls mailing list
>>>>> mpls@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mpls
>>=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20


From venkatflex@gmail.com  Sun Aug 21 10:47:03 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99D7B21F84FA; Sun, 21 Aug 2011 10:47:03 -0700 (PDT)
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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ji9weItRxZR; Sun, 21 Aug 2011 10:47:03 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE4D21F8A58; Sun, 21 Aug 2011 10:47:02 -0700 (PDT)
Received: by wyg8 with SMTP id 8so3610145wyg.31 for <multiple recipients>; Sun, 21 Aug 2011 10:48:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=/L2suulNsECkbrsfoSiVIDooYcdZFhEqVFAuhFY6mr8=; b=eWmXmbi6og8Pc9aNyqcFAOipVlbJZ78AQXAebI0+bKhE0AYrkyqxyQ8sEY6tpxmCHH mrpI/lieaKaAsKzdTiEKFHBnXFlhkVPhDQFrDp3+SzWMXKuJF8+eEbnW0EkXlV+iPd1B /aedpZVgovKLnintjGkhUpQihwYiQ5JkPyoUU=
MIME-Version: 1.0
Received: by 10.216.168.198 with SMTP id k48mr1217351wel.109.1313948884362; Sun, 21 Aug 2011 10:48:04 -0700 (PDT)
Received: by 10.216.164.131 with HTTP; Sun, 21 Aug 2011 10:48:04 -0700 (PDT)
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE207D35A25@SZXEML511-MBS.china.huawei.com>
References: <20110811134542.25435.61281.idtracker@ietfa.amsl.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE207D35A25@SZXEML511-MBS.china.huawei.com>
Date: Sun, 21 Aug 2011 13:48:04 -0400
Message-ID: <CALXanX+Kh+eS9ho=C674UzNkGNmy5psLNbUP+U91fH1Xx=WTjA@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLS On-demand Connectivity Verification and Route Tracing) to Proposed Standard
From: venkatesan mahalingam <venkatflex@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>,  "mpls@ietf.org" <mpls@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 22 Aug 2011 07:16:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Aug 2011 17:47:03 -0000

Hi,

I don't see any TLVs defined for performing the on-demand CV operation
on MPLS -TP Sections. Is this intentional?

and

Co-routed bidirectional tunnel identifier:
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
      Node_ID::Tunnel_Num}::LSP_Num
Associated bidirectional tunnel identifier:
A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
      Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}

How does Static LSP Sub-TLV address the need of two LSP_Nums of
associated bidirectional tunnel?

Am I missing something?

Thanks,
Venkat.

On Fri, Aug 19, 2011 at 5:50 AM, Mach Chen <mach.chen@huawei.com> wrote:
> Hi,
>
> One question about the difference of the encapsulation modes between CV a=
nd Route Tracing.
>
> In Section 3, there are three encapsulation modes for on-demand CV: "LSP-=
Ping with IP encapsulation", "On-demand CV with IP encapsulation, over ACH"=
 and "Non-IP based On-demand CV, using ACH", but for On-demand Route Tracin=
g (in section 4), there are only two modes: "On-demand LSP Route Tracing wi=
th IP encapsulation" and "Non-IP based On-demand LSP Route Tracing, using A=
CH". Seems that there should be "On-demand LSP Route Tracing with IP encaps=
ulation, over ACH" accordingly. What's reason behind this? Or maybe I misse=
d something.
>
> Best regards,
> Mach
>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of =
The
>> IESG
>> Sent: Thursday, August 11, 2011 9:46 PM
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPL=
S
>> On-demand Connectivity Verification and Route Tracing) to Proposed Stand=
ard
>>
>>
>> The IESG has received a request from the Multiprotocol Label Switching W=
G
>> (mpls) to consider the following document:
>> - 'MPLS On-demand Connectivity Verification and Route Tracing'
>> =A0 <draft-ietf-mpls-tp-on-demand-cv-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
>> ietf@ietf.org mailing lists by 2011-08-25. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>> =A0 =A0Label Switched Path Ping (LSP-Ping) is an existing and widely
>> =A0 =A0deployed Operations, Administration and Maintenance (OAM) mechani=
sm
>> =A0 =A0for Multi-Protocol Label Switching (MPLS) Label Switched Paths
>> =A0 =A0(LSPs). =A0This document describes extensions to LSP-Ping so that=
 LSP-
>> =A0 =A0Ping can be used for On-demand Connectivity Verification of MPLS
>> =A0 =A0Transport Profile (MPLS-TP) LSPs and Pseudowires. =A0This documen=
t also
>> =A0 =A0clarifies procedures to be used for processing the related OAM
>> =A0 =A0packets. =A0Further, it describes procedures for using LSP-Ping t=
o
>> =A0 =A0perform Connectivity Verification and Route Tracing functions in
>> =A0 =A0MPLS-TP networks. =A0Finally this document updates RFC 4379 by ad=
ding a
>> =A0 =A0new address type and requesting an IANA registry.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

From venkatflex@gmail.com  Sun Aug 21 11:56:47 2011
Return-Path: <venkatflex@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 026C021F877F; Sun, 21 Aug 2011 11:56:47 -0700 (PDT)
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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id md0z6c78TCDn; Sun, 21 Aug 2011 11:56:46 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3864B21F86B6; Sun, 21 Aug 2011 11:56:45 -0700 (PDT)
Received: by wyg8 with SMTP id 8so3632652wyg.31 for <multiple recipients>; Sun, 21 Aug 2011 11:57:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=ZSo/zxStqp58HOzi7qsFD8dT1dAwINYcueszdGL4sPk=; b=LM4foh/UyMMOQoK/0iVII/8W/HVnCeOIQE/6/vLXmTc5BO9pd8SveHk6i/ig3wsz2R e3SrnurLqYFacRo6oZA3L66dQDKpWeta17984SYZ+OZjtFTyt+F172G/ahbTJY7tcVlU YWjqTcpSBCIPaLj65plBSK3cR6VuqtzPf0+YI=
MIME-Version: 1.0
Received: by 10.216.188.207 with SMTP id a57mr1232363wen.94.1313953067180; Sun, 21 Aug 2011 11:57:47 -0700 (PDT)
Received: by 10.216.164.131 with HTTP; Sun, 21 Aug 2011 11:57:47 -0700 (PDT)
In-Reply-To: <CALXanX+Kh+eS9ho=C674UzNkGNmy5psLNbUP+U91fH1Xx=WTjA@mail.gmail.com>
References: <20110811134542.25435.61281.idtracker@ietfa.amsl.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE207D35A25@SZXEML511-MBS.china.huawei.com> <CALXanX+Kh+eS9ho=C674UzNkGNmy5psLNbUP+U91fH1Xx=WTjA@mail.gmail.com>
Date: Sun, 21 Aug 2011 14:57:47 -0400
Message-ID: <CALXanXKnAc3w6vLKR-BHmOKNRxpO_oafznozueujBnnN6r8MZQ@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLS On-demand Connectivity Verification and Route Tracing) to Proposed Standard
From: venkatesan mahalingam <venkatflex@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>,  "mpls@ietf.org" <mpls@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 22 Aug 2011 07:16:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Aug 2011 18:56:47 -0000

Eric,

Don't you feel that uniformity should be maintained on AGI field
representation for on-demand and proactive OAM operations?

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   AGI Type    |  AGI Length   |      AGI Value                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ~                    AGI  Value (contd.)                        ~
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

draft-ietf-mpls-tp-cc-cv-rdi-06, section 3.5.3. PW Endpoint MEP-ID and
draft-ietf-mpls-tp-on-demand-cv-06, section 2.3.2.  Static Pseudowire
Sub-TLV conflict in representing the AGI field.

Why are we not following this generic format for representing the AGI field=
?

Am I missing something?

Thanks,
Venkat.

Re: [mpls] Need clarification on draft-ietf-mpls-tp-on-demand-cv-05

To: binny jeshan <binnyjeshan at gmail.com>, "mpls at ietf.org" <mpls
at ietf.org>
Subject: Re: [mpls] Need clarification on draft-ietf-mpls-tp-on-demand-cv-0=
5
From: Eric Gray <eric.gray at ericsson.com>
Date: Thu, 11 Aug 2011 07:03:09 -0400
Accept-language: en-US
Acceptlanguage: en-US
Cc: Ross Callon <rcallon at juniper.net>, MPLS-TP ad hoc team
<ahmpls-tp at lists.itu.int>, "draft-ietf-mpls-tp-on-demand-cv at
tools.ietf.org" <draft-ietf-mpls-tp-on-demand-cv at tools.ietf.org>
Delivered-to: mpls at ietfa.amsl.com
In-reply-to: <CAHcPYOzo1vO_ThspndrZwf-X8JAf2b0Mr1SGp7mL2HfN_OxRNw at
mail.gmail.com>
List-archive: <http://www.ietf.org/mail-archive/web/mpls>
List-help: <mailto:mpls-request@ietf.org?subject=3Dhelp>
List-id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-post: <mailto:mpls@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/mpls>,
<mailto:mpls-request@ietf.org?subject=3Dsubscribe>
List-unsubscribe: <https://www.ietf.org/mailman/options/mpls>,
<mailto:mpls-request@ietf.org?subject=3Dunsubscribe>
References: <CAHcPYOzo1vO_ThspndrZwf-X8JAf2b0Mr1SGp7mL2HfN_OxRNw at
mail.gmail.com>
Thread-index: AcxAZ8Iuor4OYFULT7mPiL+c0YrKTgXrKqiA
Thread-topic: Need clarification on draft-ietf-mpls-tp-on-demand-cv-05
Binny,

    We discussed this in detail.  Superficially, this seemed like a great i=
dea,
with precedents in the CC/CV/RDI draft.

    The issues we ran into include:
1) the Static PW ID TLV is already a sub-TLV; there are issues and a very
    undesirable precedent associated with creating a sub-TLV for a sub-TLV.
2) the flexibility associated with inheriting the type code also poses a ri=
sk;
    we cannot know in advance what other AGI types might be invented in
    the future, and whether or not it would make sense in then existing TP
    implementations to support generally the new type(s) as part of the
    Static PW Identifier Sub-TLV.

    What we decided to do was to change the name of the field to "Service
Identifier" - which will be an unsigned integer and which may contain a typ=
e
0x01 AGI, for example.  Because it is an unsigned integer, it may also be
used to contain anything smaller than 64 bits.

    The flexibility to support other AGI types still exists, should it beco=
me
necessary to do so.  In that event, we could define additional Static PW
Sub-TLV type(s) to support any AGI type(s) that make sense at that time.

    Thanks for your thoughtful and thought-provoking input! We appreciate
your putting time into reviewing our draft...

--
Eric

On Sun, Aug 21, 2011 at 1:48 PM, venkatesan mahalingam
<venkatflex@gmail.com> wrote:
> Hi,
>
> I don't see any TLVs defined for performing the on-demand CV operation
> on MPLS -TP Sections. Is this intentional?
>
> and
>
> Co-routed bidirectional tunnel identifier:
> A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
> =A0 =A0 =A0Node_ID::Tunnel_Num}::LSP_Num
> Associated bidirectional tunnel identifier:
> A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
> =A0 =A0 =A0Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
>
> How does Static LSP Sub-TLV address the need of two LSP_Nums of
> associated bidirectional tunnel?
>
> Am I missing something?
>
> Thanks,
> Venkat.
>
> On Fri, Aug 19, 2011 at 5:50 AM, Mach Chen <mach.chen@huawei.com> wrote:
>> Hi,
>>
>> One question about the difference of the encapsulation modes between CV =
and Route Tracing.
>>
>> In Section 3, there are three encapsulation modes for on-demand CV: "LSP=
-Ping with IP encapsulation", "On-demand CV with IP encapsulation, over ACH=
" and "Non-IP based On-demand CV, using ACH", but for On-demand Route Traci=
ng (in section 4), there are only two modes: "On-demand LSP Route Tracing w=
ith IP encapsulation" and "Non-IP based On-demand LSP Route Tracing, using =
ACH". Seems that there should be "On-demand LSP Route Tracing with IP encap=
sulation, over ACH" accordingly. What's reason behind this? Or maybe I miss=
ed something.
>>
>> Best regards,
>> Mach
>>
>>> -----Original Message-----
>>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of=
 The
>>> IESG
>>> Sent: Thursday, August 11, 2011 9:46 PM
>>> To: IETF-Announce
>>> Cc: mpls@ietf.org
>>> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MP=
LS
>>> On-demand Connectivity Verification and Route Tracing) to Proposed Stan=
dard
>>>
>>>
>>> The IESG has received a request from the Multiprotocol Label Switching =
WG
>>> (mpls) to consider the following document:
>>> - 'MPLS On-demand Connectivity Verification and Route Tracing'
>>> =A0 <draft-ietf-mpls-tp-on-demand-cv-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
>>> ietf@ietf.org mailing lists by 2011-08-25. Exceptionally, comments may =
be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>> =A0 =A0Label Switched Path Ping (LSP-Ping) is an existing and widely
>>> =A0 =A0deployed Operations, Administration and Maintenance (OAM) mechan=
ism
>>> =A0 =A0for Multi-Protocol Label Switching (MPLS) Label Switched Paths
>>> =A0 =A0(LSPs). =A0This document describes extensions to LSP-Ping so tha=
t LSP-
>>> =A0 =A0Ping can be used for On-demand Connectivity Verification of MPLS
>>> =A0 =A0Transport Profile (MPLS-TP) LSPs and Pseudowires. =A0This docume=
nt also
>>> =A0 =A0clarifies procedures to be used for processing the related OAM
>>> =A0 =A0packets. =A0Further, it describes procedures for using LSP-Ping =
to
>>> =A0 =A0perform Connectivity Verification and Route Tracing functions in
>>> =A0 =A0MPLS-TP networks. =A0Finally this document updates RFC 4379 by a=
dding a
>>> =A0 =A0new address type and requesting an IANA registry.
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>

From tglassey@certichron.com  Sat Aug 20 12:17:53 2011
Return-Path: <tglassey@certichron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C09C21F84ED for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 12:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5uDF-MFMjYJ for <ietf@ietfa.amsl.com>; Sat, 20 Aug 2011 12:17:52 -0700 (PDT)
Received: from smtpauth05.prod.mesa1.secureserver.net (smtpauth05.prod.mesa1.secureserver.net [64.202.165.99]) by ietfa.amsl.com (Postfix) with SMTP id 97AAB21F84E1 for <ietf@ietf.org>; Sat, 20 Aug 2011 12:17:52 -0700 (PDT)
Received: (qmail 6290 invoked from network); 20 Aug 2011 19:18:49 -0000
Received: from unknown (67.180.133.66) by smtpauth05.prod.mesa1.secureserver.net (64.202.165.99) with ESMTP; 20 Aug 2011 19:18:49 -0000
Message-ID: <4E5008B2.1030305@certichron.com>
Date: Sat, 20 Aug 2011 12:19:14 -0700
From: Todd Glassey <tglassey@certichron.com>
Organization: certichron.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Question about Policy Announcement and Query...
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 22 Aug 2011 08:01:38 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Aug 2011 19:17:53 -0000

Would a general access policy lookup tool protocol be viable here?  It 
could bolt-on to both DHCP and NEA but seems like the same additions 
would be good in both. The same is true with many other protocols. 
Especially (from my perspective) those being used in automation and 
testimony generation models.

The logic is that today we need to be able to do a complete business 
relationship online and not have to use HTTP as the basis of it. The 
nexus of this is that there really needs to be some way on the web of 
asking for and receiving the use policy for other network services (DNS, 
Email, DHCP, SSH, L2TP, SNMP, etc etc etc) than a web-interface.

This may be as simple as a use model for an existing set of tools - so 
it may be we just need use statements for fulfilling this requirement 
today.

But this brings up a stronger and more subtler argument as to whether 
standards need this type of thing - the ability to communicate the rules 
of engagement inside the context of the specific standard or as an 
alternative through a unified interface standard

Either way, I still want to propose the idea of a Project to come up 
with a proposal for a WG which would handle a uniform Policy Discovery 
Transport thingee and its use models.

I think the PDT should be adapted so it can provide these services to 
existing protocols where applicable as well inside the IETF's stable of 
IP. This allows for some pretty strong packaging options to the Trust as 
well so its probably a double whammy

My suggestion - forget its me suggesting it and just consider the idea 
on the merits of the Idea - you guys can pick someone to run this and 
produce the whole thing, I just want to propose here that this is a 
missing piece of your cake. Its the icing for a number of tools you 
already have locked-down tight so its got value and legs I think.

Todd


-- 
Todd S. Glassey - CISM CIFI
CTO Certichron Inc

This message contains information which may be confidential and/or privileged. Unless you are the intended recipient (or authorized to receive for the intended recipient), you may not read, use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message and any attachment(s) thereto without retaining any copies.

Further we have a formal OPT OUT Policy posted on our website pertaining to the use of any Email Addresses gleaned or taken from any source, web, mailing lists, previous customer lists etc. In all instances we choose to formally OPT OUT and this notice constitutes formal disclosure that you may not collect, buy or sell or provide access to this email address or any pertaining to our DNS MX Record Publication License posted on the web at http://www-wp.certichron.com/?page_id=3947.


From hsantos@santronics.com  Fri Aug 19 17:10:58 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B9921F8AFE for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 17:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zXYAe+VzwUbe for <ietf@ietfa.amsl.com>; Fri, 19 Aug 2011 17:10:57 -0700 (PDT)
Received: from pop3.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 4267F21F8B13 for <ietf@ietf.org>; Fri, 19 Aug 2011 17:10:56 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3161; t=1313799111; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=N1Az8cB vjCLdYlCVOyppYsSW9e0=; b=IqZM63K0NzPO0pUwanSTuV/Z18DOZMcms7Zu+jY IAUnKQ6KHAY9hDWrgpvFdlTGaAWeCsKXEfPx6FoW4UV/WbYDB8r2i+1gyKOGYBV0 G59qNoEmyU98QdGdxepkjv2JzAIsnrNEC2q1H+h8IBFV+w9N/2sldaVnAyEcVkRW AS6U=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 19 Aug 2011 20:11:51 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2254539604.24065.5944; Fri, 19 Aug 2011 20:11:10 -0400
Message-ID: <4E4EFB82.8050400@santronics.com>
Date: Fri, 19 Aug 2011 20:10:42 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: jean-michel bernier de portzamparc <jmabdp@gmail.com>
Subject: Re: IDNA and Multilingual Internet issues and vocabulary after	IDNA2008
References: <CAGzJzZ6yv2jbuP0-Jk586B4RDWr7UhFbp+wqnKoRqk1mBavh5w@mail.gmail.com>	<86E32E259DD17E1166516052@localhost> <CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com>
In-Reply-To: <CAGzJzZ6DG5MfdgHEuggZpwKv_8dt3V1BQnFkNAFFKLxysS2VUw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 22 Aug 2011 08:52:42 -0700
Cc: IETF <ietf@ietf.org>, happiana@ietf.org, precis@ietf.org, IDNA update work <idna-update@alvestrand.no>, internet users contributing group <iucg@ietf.org>, John C Klensin <john-ietf@jck.com>, vip@icann.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Aug 2011 00:10:58 -0000

Not commenting of the legal stuff,  I have to admit I like the idea of 
the Glossary web site with the consolidation of divest material.  I 
thought it had some awkward reading injection of material that 
probably was not necessary, maybe little unprofessional, but overall 
for such a divest environment on the Internet, the basic Glossary idea 
was interesting that I found to be informational. I think it will 
gives people, especially for the new, a better sense of the global 
connected nature of the various groups. If anything, there was an 
initial perception of commercial interest, but that didn't seem to be 
the case. But your email was definitely presented that way or at least 
its how I read it for a person who didn't know much about all these 
groups.  Maybe didn't help if that was not the intent.

Anyway, I hope the "legal" stuff can be settled.  It would be a 
resource link for me.


jean-michel bernier de portzamparc wrote:
> Dear Mr. Klensin,
> 
> "we" are Internet and IETF users. This makes a pretty large community. There
> are three ways one can do it:
> 
> - in surviving with what we (do not) get. Very large part of our community.
> - in hacking the internet from the outside on behalf of our right to protect
> ourselves from digital ecosystem pollution risks. Small part of our
> community.
> - in trying to cooperate with you guys and help your inside work with our
> outside perspective. Microscopic part of our community. Guess why? Please
> read the begining of your mail.
> 
> We do it because Jefsey convinced a few of us and the IETF Chair that it had
> to be tried. However, if the inside Internet is made of individual's and
> ISOC's copyrights and cannot even be discussed and helped, Jefsey will soon
> be alone!
> 
> Please respond: the ball is your field. Tell me: are we wrong trying to work
> in the open, liaise with the IETF and carry a lot of work to be able to
> answer you, the happiana, the PRECIS, the VIP people in a consistant way,
> also with other open works?
> 
> 
> This being said you perfectly know that this
> 
> 2011/8/19 John C Klensin <john-ietf@jck.com>
> 
>> without any specific
>> attribution or acknowledgment.  Those materials include several
>> RFCs and draft-ietf-appsawg-rfc3536bis.
> 
> 
> is wrong. Your name, your RFCs etc. are quoted as such. We do not publish,
> we try to draft a pertinent mail to you!
> 
> 
>> I am an author or major
>> contributor on several of those.  Especially since I had asked
>> earlier that any compendium of this sort list terms covered in
>> other documents, comment on them as you thought appropriate,
> 
> 
> This is correct. But to respond to you, a lot of work must be carried.
> Beginning with an enlarged scope to other intricate real needs you did not
> consider yet.
> 
> Portzamparc
> 
> BTW I am not French, I am Breton!
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

-- 
Sincerely

Hector Santos
http://www.santronics.com




From dworley@avaya.com  Mon Aug 22 09:05:23 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B237821F855A for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 09:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.451
X-Spam-Level: 
X-Spam-Status: No, score=-103.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ViF4+yFLRxLB for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 09:05:23 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 10BCF21F84EB for <ietf@ietf.org>; Mon, 22 Aug 2011 09:05:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEZ9Uk7GmAcF/2dsb2JhbABBqA53gUABAQEBAgESKD8FCwIBCA0BBwMeEDIlAQEEAQ0NDQ2HT5lUAptfhWlfBJg+i2k
X-IronPort-AV: E=Sophos;i="4.68,263,1312171200"; d="scan'208";a="299083704"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 22 Aug 2011 12:06:25 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Aug 2011 12:02:32 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Mon, 22 Aug 2011 12:06:24 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, jefsey <jefsey@jefsey.com>
Date: Mon, 22 Aug 2011 12:05:12 -0400
Subject: RE: [precis] Path towards a multilingalization IUse referent
Thread-Topic: [precis] Path towards a multilingalization IUse referent
Thread-Index: AcxfsfVRZFprf1BqRuSGXEueKrcJ8gBM0/ms
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5844@DC-US1MBEX4.global.avaya.com>
References: <7.0.1.0.2.20110821003129.0da01218@jefsey.com>, <20110821032449.GA39963@shinkuro.com>
In-Reply-To: <20110821032449.GA39963@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 16:05:23 -0000

> From: Andrew Sullivan
>=20
> On Sun, Aug 21, 2011 at 01:08:29AM +0200, jefsey wrote:
> > However, the Internet MUST be supported by a
> > network/human oriented universal semiotic system.
>=20
> I would like a defence of that claim.  Speaking entirely personally, I
> don't believe it.

Hmmm, my opinion is that I would be pleased if I understood the
demand.

But in my social context, when someone argues for a universal
communication system, they usually continue with a demand that
everybody speaks English.  And I don't think that's what we intend.
(<-- this is a joke)

But there is a similar danger with any "universal semiotic system", in
that the more systematic we make it, the less well it aligns with many
of the thousands of human cultures  (<-- this is not a joke)

(In critiques of the Pioneer plaque it was noted that the "arrow" as a
textual convention depends on a cultural history of bow-and-arrow
use.  So much for universal symbols.)

Dale

From mohta@necom830.hpcl.titech.ac.jp  Mon Aug 22 09:34:44 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05DA521F8BA4 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 09:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.016
X-Spam-Level: 
X-Spam-Status: No, score=-0.016 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gpqLiYTWKjib for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 09:34:43 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 34DDC21F8BAA for <ietf@ietf.org>; Mon, 22 Aug 2011 09:34:43 -0700 (PDT)
Received: (qmail 83195 invoked from network); 22 Aug 2011 16:38:10 -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; 22 Aug 2011 16:38:10 -0000
Message-ID: <4E5284F5.5090003@necom830.hpcl.titech.ac.jp>
Date: Tue, 23 Aug 2011 01:33:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [precis] Path towards a multilingalization IUse referent
References: <7.0.1.0.2.20110821003129.0da01218@jefsey.com>, <20110821032449.GA39963@shinkuro.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5844@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5844@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 16:34:44 -0000

Worley, Dale R (Dale) wrote:

> But in my social context, when someone argues for a universal
> communication system, they usually continue with a demand that
> everybody speaks English.  And I don't think that's what we intend.
> (<-- this is a joke)

You are confusing characters and languages.

Plain DNS is already multilingual, because all the languages in the
world can be represented in ASCII characters.

Adding fancy characters means most of the international people can't
recognize the characters, which is against Internationalization.

That is, plain DNS with ASCII is the most internationalized DNS.

							Masataka Ohta

From wesley.george@twcable.com  Mon Aug 22 10:10:46 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD37D21F8541 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 10:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[AWL=0.373,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHZ1akkrjy85 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 10:10:46 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id CB99721F853E for <ietf@ietf.org>; Mon, 22 Aug 2011 10:10:45 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,410,1309752000";  d="scan'208,223";a="250330208"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 22 Aug 2011 13:11:12 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 22 Aug 2011 13:11:33 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>, SM <sm@resistor.net>
Date: Mon, 22 Aug 2011 13:11:32 -0400
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard 
Thread-Topic: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard 
Thread-Index: Acxg7oo7XV0UhjXuRQiQ1JTtqronnA==
Message-ID: <34E4F50CAFA10349A41E0756550084FB0D5571B9@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-intarea-ipv6-required@tools.ietf.org" <draft-ietf-intarea-ipv6-required@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 17:10:46 -0000

From: SM <sm@resistor.net>
To: ietf@ietf.org
Reply-to: sm@resistor.net
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Sup=
port Required for all IP-capable nodes) to Proposed Standard
X-RSN: 1/0/933/10475/58528

>From Section 1:

"However, due to the success of the Internet in finding new and
innovative uses for IP networking, billions of hosts are now
connected via the Internet and requiring unique addressing."

That sounds like the requirement for unique addressing is a
problem. The draft mentions that demand has lead to the exhaustion
of the IANA global pool of unique IPv4 addresses. Should the above
be read as "requiring unique IPv4 addressing"?
_________
WEG] You're reading too much into this. It's a statement of the current sit=
uation, not a discussion about whether unique addresses are good or bad.
There are billions of hosts on the internet, a lot of them require unique a=
ddresses. End of line. No value judgment.
A requirement for unique addresses is not a problem. However, it *is* a pro=
blem if all you have to address those nodes  with is an exhausted IANA IPv4=
 free pool, which leaves us needing IPv6 to meet the demand for those uniqu=
e addresses.


"However, the IPv6 deployment necessary to reduce reliance on IPv4 has
been hampered by a lack of ubiquitous hardware and software support
throughout the industry."

Quoting RFC 5218:

'The lack of a value chain can make it difficult for a new protocol to
progress from implementation to deployment to use. While the term
"chicken-and-egg" problem is sometimes used to describe the lack of a
value chain, the lack of implementation, deployment, or use is not
the cause of failure, it is merely a symptom.'

The assertion that the problem is a lack of ubiquitous hardware and
software support throughout the industry is incorrect. It is the
lack of the value chain that has hampered IPv6 deployment.
_________
WEG] I find it strange that you'd a) quote from a section of 5218 on protoc=
ol failure in a discussion about IPv6, which doesn't meet any of the criter=
ia listed earlier in that section and b) invoke a value chain here as a rea=
son to invalidate the above statement. Whether it's a cause or a symptom, t=
he above quoted issue still exists as a barrier, and ultimately the lack of=
 that support breaks that chain - no killer app making it attractive to mov=
e to IPv6 due to concerns that the target audience wouldn't be able to reac=
h it, due to a lack of last mile support for IPv6, for example. I think thi=
s argument is mostly based on your following assertion, so I'll respond in =
more detail below.


Many vendors in the consumer space such as Internet Service Providers
still view IPv6 support as optional. They are still pushing the
"Internet" as an IPv4 medium only.
<snip>
Even if the average home gets an IPv6-capable device, that would not
get it any further due to last-mile issues.

___________
WEG] As an operator (consumer ISP) who happens to spend a lot of time talki=
ng about IPv6 deployments with other operators, I disagree with this assert=
ion. This is exactly the problem we're trying to solve. From where I sit, I=
 see credible plans from a number of US residential broadband providers to =
have IPv6 enabled on a large portion of their footprint within the next 12-=
18 months. There is no reason why IPv6 support in ancillary devices needs t=
o be a serial process dependent on completion of that last mile deployment.=
 You're saying, "don't bother, there's no IPv6 support on the last mile." W=
e're saying "we're building the last mile, and we'd like to not have to wai=
t for the next technology refresh cycle before the IPv6 support we build ha=
s any devices to use it." Understand that in many cases, even if the provid=
ers turned on IPv6 support in the CMTS or DSLAM/BRAS tomorrow, if the custo=
mer supplies their own modem or wireless gateway, if it doesn't do v6, it's=
 also all for naught.

Anyway, let's get to the meat of the draft.
__________
WEG] Brian's already responded to several of these items, so I'll respond i=
nline in those messages as necessary.


BTW, this draft has nine pages and four authors. The 162-page draft
I read recently has five authors. "If there is a desire to
demonstrate how many companies are interested in this spec, a simple
acknowledgment section can accomplish the same thing".
___________
WEG] I fail to see the relevance of this other than to impugn the authors r=
ather than the ideas in the draft, but since you brought it up, all 4 of th=
e listed authors collaborated on the initial text of this draft at the end =
of IETF 79, and have provided material contributions to the text in each su=
bsequent revision.


I do not support the publication of this document as a RFC. It
attempts to update old RFCs which are well-written in a confusing
manner. The draft comes out as a statement about "IPv6-required"
instead of a Proposed Standard.
__________
WEG] It would be helpful to know whether you do not support this because of=
 the choice to update several RFCs, the choice to make it a proposed standa=
rd (instead of BCP or informational), or you disagree with the entire thing=
. This will make it easier for the authors to address your concerns adequat=
ely.

Thanks

Wes George



This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From wesley.george@twcable.com  Mon Aug 22 10:11:52 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30BEE21F8A96 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 10:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.201
X-Spam-Level: 
X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvvpCI+ttAwq for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 10:11:51 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 8306D21F8A7B for <ietf@ietf.org>; Mon, 22 Aug 2011 10:11:51 -0700 (PDT)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,410,1309752000"; d="scan'208";a="250330770"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 22 Aug 2011 13:12:34 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Mon, 22 Aug 2011 13:12:55 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>, t.petch <daedulus@btconnect.com>
Date: Mon, 22 Aug 2011 13:12:54 -0400
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
Thread-Topic: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
Thread-Index: Acxg7rrwegB7/n4NRHGzAlXZP03yLg==
Message-ID: <34E4F50CAFA10349A41E0756550084FB0D5571BD@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-intarea-ipv6-required@tools.ietf.org" <draft-ietf-intarea-ipv6-required@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 17:11:52 -0000

From: "t.petch" <daedulus@btconnect.com>
To: <ietf@ietf.org>
Reply-to: daedulus@btconnect.com
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Supp=
ort Required for all IP-capable nodes) to Proposed Standard

I find this document utterly bizarre and think it would seriously damage th=
e
Internet to publish it.
____________
WEG] well, I find the vehemence of your statement a bit bizarre, but I woul=
d like to address your concerns if possible. Please explain how a recommend=
ation to support IPv6 is going to "seriously damage the internet."

The idea that ipv6 should be regarded as normal, as of equal standing to ip=
v4 is
fine, the sort of statement that the IAB should make, or have made, as an R=
FC or
in some other form.
____________
WEG] Agree. IETF has remained version-agnostic for some time now. But they =
have not made anything like the statement that this draft makes, which is t=
hat IPv6 will be necessary because IPv4 is going to have difficulties in co=
ntinuing to provide the same level of service post-exhaustion. In the autho=
rs' opinions, it is long overdue as guidance to implementers, so we made th=
e statement in the hopes that we'd reach consensus, which in a way is a str=
onger statement than something coming out of the IAB anyway.

But this I-D claims
" Updates [RFC1122] to clarify that this document, especially in
section 3, primarily discusses IPv4 where it uses the more generic
term "IP" and is no longer a complete definition of "IP" or the
Internet Protocol suite by itself. "

IPv4 is a phenomenal success, and RFC1122 is a key part of that. IPv4 was a
confused jumble, as IPv6 is now, and RFC1122, with another two or so I-Ds, =
cut
through the cruft and rendered it usable. IPv6 desparately needs an equival=
ent
to RFC1122, as a trawl of the v6ops list archives shows, and clearly this I=
-D is
never going to be it, but claiming that this I-D provides an update to RFC1=
122,
coupled
with its title, gives the message that there is not going to be such an I-D=
;
IPv6 will remain a confused jumble (and so is unlikely ever to emulate the
success of IPv4).
___________
WEG] Ignoring for a moment the commentary on the state of the IPv6 RFCs vs =
IPv4, and the need for a "rosetta stone," I'll note that the choice to upda=
te several IP(v4) RFCs was something that has been controversial based on I=
ntarea LC feedback as well, but we believed necessary to provide the linkag=
e between the two. Honestly, I would have rather seen IETF issue formal upd=
ates to the existing "IP" RFCs to include IPv6, rather than building an ent=
irely parallel set of documents, but here we are, so we made a choice. It w=
ould be helpful to understand whether your resistance to this document is s=
olely due to the decision to have this be standards track, to update severa=
l existing RFCs, or both vs the general recommendation that implementers sh=
ould support IPv6. While I believe that removing the update references will=
 reduce the impact of the document, I am not opposed to issuing a new versi=
on of the document that does so and keeps to simply documenting the require=
ments for IPv6 support if consensus supports that action.

Thanks
Wes George


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From mstjohns@comcast.net  Mon Aug 22 12:17:09 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC9321F8C1E for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 12:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.36
X-Spam-Level: 
X-Spam-Status: No, score=-101.36 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROwP3l8W6kZs for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 12:17:08 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by ietfa.amsl.com (Postfix) with ESMTP id 652C721F8C19 for <ietf@ietf.org>; Mon, 22 Aug 2011 12:17:08 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta14.westchester.pa.mail.comcast.net with comcast id PXHo1h0011wpRvQ5EXJBoe; Mon, 22 Aug 2011 19:18:11 +0000
Received: from Mike-PC3.comcast.net ([68.83.217.57]) by omta18.westchester.pa.mail.comcast.net with comcast id PXJ71h00m1EtFYL3eXJ8zl; Mon, 22 Aug 2011 19:18:09 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 22 Aug 2011 15:17:43 -0400
To: ietf-secretariat@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Hyatt Taipei cancellation policy?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110822191708.652C721F8C19@ietfa.amsl.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 19:17:09 -0000

Hi folks - 

I just reserved with the hotel and was quite surprised at the cancellation policy.

Could you please confirm - Cancel before 1 Nov - no charge, 1-7 Nov 1 night, after 7 Nov full amount?

Seriously?  This is extreme. I can understand a 1 day fee up to the date of the reservation and maybe even charging the full amount if I don't cancel, but paying $1500+ because I had to cancel at the last moment seems a bit confiscatory.  

Mike


From wesley.george@twcable.com  Mon Aug 22 12:44:08 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 214BD21F8C79 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 12:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[AWL=0.363, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w3qvG5mSjIH0 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 12:44:07 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6364D21F8C4B for <ietf@ietf.org>; Mon, 22 Aug 2011 12:44:07 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,410,1309752000"; d="scan'208";a="250398704"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 22 Aug 2011 15:44:38 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Mon, 22 Aug 2011 15:44:59 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>, SM <sm@resistor.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 22 Aug 2011 15:44:58 -0400
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
Thread-Topic: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
Thread-Index: AcxhA/ljGa2nUasOTzysHN4mgO3dQQ==
Message-ID: <34E4F50CAFA10349A41E0756550084FB0D557318@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-intarea-ipv6-required@tools.ietf.org" <draft-ietf-intarea-ipv6-required@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 19:44:08 -0000

From: SM <sm@resistor.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Reply-to: sm@resistor.net
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Sup=
port Required for all IP-capable nodes) to Proposed Standard

Section 2 of RFC 4084 lists the primary IP service terms:

(a) Web connectivity

(b) Client connectivity only, without a public address

(c) Client only, public address

(d) Firewalled Internet Connectivity

(e) Full Internet Connectivity

And with the proposed update:

(f) Version support.

Does the service include IPv4 support only, both IPv4 and IPv6
support, or IPv6 support only?

I don't think that it makes sense as it stands. If you want to
wordsmith this, you could go with:

(f) IPv4 Internet Connectivity.

This service provides the user IPv4 Internet connectivity, with
one or more static public IPv4 addresses. Dynamic IPv4 addresses
that are long-lived enough to make operating servers practical
without highly dynamic DNS entries are possible, provided that
they are not characterized as "dynamic" to third parties.

________
WEG] I think that you have a point that this update is a little weak in its=
 current form. I don't have a problem with some clarifying text, but I thin=
k that the problem with the above is that you now get into situations where=
 IPv4 internet connectivity by that definition is no longer possible due to=
 a lack of available addresses. In other words, each of the defined items i=
n the existing section 2 are applicable to IPv4 and IPv6 separately. So per=
haps it needs to discuss the fact that there are now multiple permutations =
of the items in section 2, e.g. where the host has IPv6 internet connectivi=
ty, but really only has client/no public IPv4 connectivity.
Then we're into value-judgment-land regarding whether full IPv6 connectivit=
y coupled with NAT for IPv4 is considered "full internet connectivity" or i=
f only true dual-stack is acceptable for that definition, etc.

Brian was the one who originally suggested this RFC be added as updated by =
this draft, so I'm keen to hear his opinion as well.


(g) IPv6 Internet Connectivity.

This service provides the user/consumer IPv6 Internet connectivity,
with at least a /60 IPv6 prefix. Dynamic IPv6 addressing that are
long-lived enough to make operating servers practical
without highly dynamic DNS entries are possible, provided that
they are not characterized as "dynamic" to third parties.
_________
WEG] I think that this definition is going to be problematic. There are ple=
nty of other documents which already define IPv6 connectivity, and we are u=
nlikely to reach consensus on any definition that includes a prefix size, b=
ut I'd be interested in opinions on the rest of it assuming that the prefix=
 size recommendation is dropped.

Thanks
Wes George


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From lixia@cs.ucla.edu  Mon Aug 22 12:52:00 2011
Return-Path: <lixia@cs.ucla.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8C721F8C73; Mon, 22 Aug 2011 12:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.05
X-Spam-Level: 
X-Spam-Status: No, score=-102.05 tagged_above=-999 required=5 tests=[AWL=0.549, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id liAnnJ2TJxDe; Mon, 22 Aug 2011 12:51:59 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 91B5921F8C70; Mon, 22 Aug 2011 12:51:59 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 5A9E439E80F7; Mon, 22 Aug 2011 12:53:04 -0700 (PDT)
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 ImZMJlGDiGXq; Mon, 22 Aug 2011 12:53:03 -0700 (PDT)
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 9640939E80DC; Mon, 22 Aug 2011 12:53:03 -0700 (PDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <20110822191708.652C721F8C19@ietfa.amsl.com>
Date: Mon, 22 Aug 2011 12:53:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>
References: <20110822191708.652C721F8C19@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Secretariat <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 19:52:00 -0000

On Aug 22, 2011, at 12:17 PM, Michael StJohns wrote:

> Hi folks -=20
>=20
> I just reserved with the hotel and was quite surprised at the =
cancellation policy.
>=20
> Could you please confirm - Cancel before 1 Nov - no charge, 1-7 Nov 1 =
night, after 7 Nov full amount?
>=20
> Seriously?  This is extreme. I can understand a 1 day fee up to the =
date of the reservation and maybe even charging the full amount if I =
don't cancel, but paying $1500+ because I had to cancel at the last =
moment seems a bit confiscatory. =20
>=20
> Mike

Since you brought up the subject of hotel: up to now IETF hotel prices =
have been within the federal per diem allowance, but IETF82 seems an =
exception by a pretty big gap (see =
http://aoprals.state.gov/web920/per_diem_action.asp?MenuHide=3D1&CountryCo=
de=3D1142, lodging allowance $186/day, a single room at Hyatt is =
$263/day with 10% tax)



From sm@resistor.net  Mon Aug 22 13:48:34 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFC3621F8B55 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 13:48:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95L1YnZNR9e7 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 13:48:30 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BCEE621F8C8F for <ietf@ietf.org>; Mon, 22 Aug 2011 13:48:30 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7MKnSen014188; Mon, 22 Aug 2011 13:49:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1314046175; bh=5byO4WhqWSqtldndPj11psRYZFNlA5ELiZNLxrBLiv8=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=GzeE2DnJJ+RCWSLYuHr2dDtPQetpcUz8wOM0jLfNelGWYdh5gfg7kIXl/RQgjtTFa vM0v1NnjIyWrrzNVNTARSzuQh0Y1wPEwdOC7FtWKbmfgtpjS7ThRxOGa4Or/MSQ1YX EQXjGDBVOhy7TFuRGL4ut4FQDYAh/GZCWL/m7dpc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1314046175; bh=5byO4WhqWSqtldndPj11psRYZFNlA5ELiZNLxrBLiv8=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=hL4VsrjFD/d7RUwgwA2z7xukMYUKa78ZRa2C/ErK33f5le5gsHMaDg7Z+Mkz5dSfh P779WEvlIETdgl1DFfjSHYKpb/x/Wh9qKCnv8oxm40m1D/e0yh2BH5beTl1mWWnYks KsVrJDAelCHMetP9accfHLvpIQqF7P7FawdRWiLc=
Message-Id: <6.2.5.6.2.20110822104656.09d4dd80@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 22 Aug 2011 13:47:42 -0700
To: "George, Wesley" <wesley.george@twcable.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard 
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0D5571B9@PRVPEXVS04.corp.t wcable.com>
References: <34E4F50CAFA10349A41E0756550084FB0D5571B9@PRVPEXVS04.corp.twcable.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-ietf-intarea-ipv6-required@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 20:48:34 -0000

Hi George,
At 10:11 22-08-2011, George, Wesley wrote:
>WEG] You're reading too much into this. It's a statement of the 
>current situation, not a discussion about whether unique addresses 
>are good or bad.

Ok.

>WEG] As an operator (consumer ISP) who happens to spend a lot of 
>time talking about IPv6 deployments with other operators, I disagree 
>with this assertion. This is exactly the problem we're trying to 
>solve. From where I sit, I see credible plans from a number of US 
>residential broadband providers to have IPv6 enabled on a large 
>portion of their
>  footprint within the next 12-18 months. There is no reason why 
> IPv6 support in ancillary

 From where I sit I have not seen credible plans from residential 
broadband providers to have IPv6 enabled.  Please note that my 
comment should not be read as a disagreement about what you said 
about US residential providers.

>  devices needs to be a serial process dependent on completion of 
> that last mile deployment. You're saying, "don't bother, there's no 
> IPv6 support on the last mile." We're saying "we're building the 
> last mile, and we'd like to not have to wait for the next 
> technology refresh cycle before the IPv6 support we build has any 
> devices to use it." Understand that in many cases, even if the 
> providers turned on IPv6 support in the CMTS or DSLAM/BRAS 
> tomorrow, if the customer supplies their own modem or wireless 
> gateway, if it doesn't do v6, it's also all for naught.

I don't think that it should be a serial process.  Although my 
earlier quote might not have emphasized it, doing this serially is 
like having a chicken and egg discussion.  I am not saying "don't 
bother".  You are building the "last mile" and you see a problem 
which occurs beyond the DSLAM/BRAS.  You don't want to wait for the 
next technology refresh cycle.  I agree with you on that.  I 
mentioned that the last mile can also be a problem (it may not be one 
from where you stand).

>WEG] I fail to see the relevance of this other than to impugn the 
>authors rather than the ideas in the draft, but since you brought it 
>up, all 4 of the listed authors collaborated on the initial text of 
>this draft at the end of IETF 79, and have provided material 
>contributions to the text in each subsequent revision.

Thanks for the explanation.  For what it is worth, I made a similar 
comment about another draft ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg68520.html 
).  Based on what you said above, there wasn't any desire for 
corporate name-dropping.

>WEG] It would be helpful to know whether you do not support this 
>because of the choice to update several RFCs, the choice to make it 
>a proposed standard (instead of BCP or informational), or you 
>disagree with the entire thing. This will make it easier for the 
>authors to address your concerns adequately.

As I mentioned in a previous message, the draft comes out as a 
statement about "IPv6-required" instead of a Proposed 
Standard.  Irrespective of whether the document is a PS or BCP, it is 
important the ideas are clearly expressed.  Brian mentioned that the 
document can be fixed with some wordsmithing.  I made an attempt at 
"send text" ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg68534.html ).  I 
came to the conclusion that the document needs more work before being 
ready for a Last Call.  The comment about informative v/s normative 
references ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg68535.html ) was 
not made from a process perspective.  You can label it as editorial 
and I am not going to dispute the decision.  In the context of the 
document, I'll just read it as draft-ietf-6man-node-req-bis (or the 
existing RFC) can be overlooked.

I would not support the publication as the draft as Informational in 
its current form as it attempts to update several Standards Track 
RFCs.  You could try to get away with it by dropping the "Updates".

I agree with Tom Petch that the document comes out as utterly bizarre 
( http://www.ietf.org/mail-archive/web/ietf/current/msg68536.html 
).  I would not say that it seriously damages the Internet.  The 
document does not come out as a convincing argument to implement IPv6.

At 12:44 22-08-2011, George, Wesley wrote:
>WEG] I think that you have a point that this update is a little weak 
>in its current form. I don't have a problem with some clarifying 
>text, but I think that the problem with the above is that you now 
>get into situations where IPv4 internet connectivity by that 
>definition is no longer possible due to a lack of available 
>addresses. In other words, each of the defined items in the existing 
>section 2 are applicable to IPv4 and IPv6 separately. So perhaps it 
>needs to discuss the fact that there are now multiple permutations 
>of the items in section 2, e.g. where the host has IPv6 internet

The multiple permutations ends up injecting complexity and can end up 
making the BCP "inaccessible".  As much as it is part of reality, it 
can end up being an hurdle in getting a wider audience to digest that.

>  connectivity, but really only has client/no public IPv4 connectivity.
>Then we're into value-judgment-land regarding whether full IPv6 
>connectivity coupled with NAT for IPv4 is considered "full internet 
>connectivity" or if only true dual-stack is acceptable for that 
>definition, etc.

Yes.

>WEG] I think that this definition is going to be problematic. There 
>are plenty of other

Yes.

>  documents which already define IPv6 connectivity, and we are 
> unlikely to reach consensus on any definition that includes a 
> prefix size, but I'd be interested in opinions on the rest of it 
> assuming that the prefix size recommendation is dropped.

I would avoid a discussion about prefix size.  However, it is going 
to end up being a problem in the long run if the ISP allocates a 
single IPv6 address to the consumer.  There is a little gem in RFC 
1122 which could be used as a workaround for the prefix size discussion.

Regards,
-sm 


From ned+ietf@mauve.mrochek.com  Mon Aug 22 14:01:25 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1484821F854E for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 14:01:25 -0700 (PDT)
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_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XGWVdXWfgT3 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 14:01:24 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 727D921F8591 for <ietf@ietf.org>; Mon, 22 Aug 2011 14:01:24 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O55J3A4BI800IWMH@mauve.mrochek.com> for ietf@ietf.org; Mon, 22 Aug 2011 14:01:18 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O51RV934KW00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 22 Aug 2011 14:01:14 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O55J38IMQU00VHKR@mauve.mrochek.com>
Date: Mon, 22 Aug 2011 13:54:47 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
In-reply-to: "Your message dated Mon, 22 Aug 2011 09:09:47 +0200" <005b01cc609a$7e9ab540$4001a8c0@gateway.2wire.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110820031053.0a551ca8@resistor.net> <005b01cc609a$7e9ab540$4001a8c0@gateway.2wire.net>
To: "t.petch" <daedulus@btconnect.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314046928; i=@mrochek.com; bh=lcDwyBqJf/7ZsECyoMmXyll5IZ6PS8AwwaaBRn1MsRs=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=DCtzbfd7yTn0Q8Y+le1L0ELLEoyV06d20fXEyMizveKlT+qK2NbEdfQX2x17YEh0L 7vx5fpefyqbj3Ebq+UXAYf25ebmkTm3g63ALZxRlziIRelTxB1+F3bW0GZz8PJVn6A jRgOHDt71cS/S7tZhEMT5gIkxkI8gaSda6m8ppuM=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 21:01:25 -0000

> I find this document utterly bizarre and think it would seriously damage the
> Internet to publish it.

This seems a little ... extreme. The document appears to me to be Mostly
Harmless, with all that implies.

> The idea that ipv6 should be regarded as normal, as of equal standing to ipv4 is
> fine, the sort of statement that the IAB should make, or have made, as an RFC or
> in some other form.

> But this I-D claims
> " Updates [RFC1122] to clarify that this document, especially in
>    section 3, primarily discusses IPv4 where it uses the more generic
>    term "IP" and is no longer a complete definition of "IP" or the
>    Internet Protocol suite by itself.  "

> IPv4 is a phenomenal success, and RFC1122 is a key part of that.  IPv4 was a
> confused jumble, as IPv6 is now, and RFC1122, with another two or so I-Ds, cut
> through the cruft and rendered it usable.  IPv6 desparately needs an equivalent
> to RFC1122,

Complete agreement on this point. Such a document, informed by actual IPv6
deployment experience at some sort of scale, is urgently needed. And this most
certainly is NOT that document. But unless publishing this is seen as meeting
the need for an 1122v6 - and I've seen no indication that's the case - I fail
to see the harm.

OTOH, if this really is seen as being a 1122v6, then I join you in opposing
it's publication.

> as a trawl of the v6ops list archives shows, and clearly this I-D is
> never going to be it, but claiming that this I-D provides an update to RFC1122,
> coupled
> with its title, gives the message that there is not going to be such an I-D;
> IPv6 will remain a confused jumble (and so is unlikely ever to emulate the
> success of IPv4).

Maybe I'm being clueless about this, but I don't see how "IPv6 Support Required
for all IP-capable nodes" gives this impression.

				Ned

From chair@ietf.org  Mon Aug 22 14:23:50 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B6821F8BC3; Mon, 22 Aug 2011 14:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z1N+IIVX6IqZ; Mon, 22 Aug 2011 14:23:49 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id C6DDE21F8BBE; Mon, 22 Aug 2011 14:23:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 9F86C1E2124; Mon, 22 Aug 2011 14:24:52 -0700 (PDT)
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 S24jpQOQGyDP; Mon, 22 Aug 2011 14:24:52 -0700 (PDT)
Received: from [192.168.2.101] (pool-96-231-29-247.washdc.fios.verizon.net [96.231.29.247]) by c1a.amsl.com (Postfix) with ESMTPSA id 461321C38158; Mon, 22 Aug 2011 14:24:52 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Experiment for different schedule for Friday
Date: Mon, 22 Aug 2011 17:24:54 -0400
Message-Id: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 21:23:50 -0000

The IESG is considering a different schedule for the Friday of IETF 82.  =
The IESG is seeking your input on these potential changes.

The IESG would like to try a schedule experiment on Friday, using this =
schedule:

 9:00 AM - 11:00 AM - Session I
11:00 AM - 11:20 AM - Room Change and Cookie Break
11:20 AM - 12:20 PM - Session II
12:10 PM - 12:30 PM - Room Change Break
12:30 PM - 13:30 PM - Session III

The IESG has already consulted with the IAOC because of the cost =
associated with the additional food and beverage break.  The IAOC =
believes that the additional cost can be managed without raising the =
meeting fee.

On behalf of the IESG,
   Russ=

From C.Donley@cablelabs.com  Mon Aug 22 14:55:20 2011
Return-Path: <C.Donley@cablelabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB1A21F8B6E for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 14:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.067
X-Spam-Level: 
X-Spam-Status: No, score=0.067 tagged_above=-999 required=5 tests=[AWL=-0.070,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FubOm1tIMkqW for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 14:55:20 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA2221F8B6C for <ietf@ietf.org>; Mon, 22 Aug 2011 14:55:20 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p7MLuOv6024989; Mon, 22 Aug 2011 15:56:24 -0600
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Mon, 22 Aug 2011 15:56:24 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Mon, 22 Aug 2011 15:56:24 -0600
From: Chris Donley <C.Donley@cablelabs.com>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 22 Aug 2011 15:56:23 -0600
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
Thread-Topic: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
Thread-Index: AcxhFlW3myHk8Hj7TwmPWSS9ts/wow==
Message-ID: <CA78256F.1D45A%c.donley@cablelabs.com>
In-Reply-To: <6.2.5.6.2.20110819111507.09a77b18@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.12.0.110505
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 21:55:21 -0000

On 8/19/11 3:42 PM, "SM" <sm@resistor.net> wrote:

>At 09:10 19-08-2011, The IESG wrote:
>>The IESG has received a request from an individual submitter to consider
>>the following document:
>>- 'IANA Reserved IPv4 Prefix for Shared Transition Space'
>>   <draft-weil-shared-transition-space-request-03.txt> as an
>>Informational
>>RFC
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action. Please send substantive comments to the
>>ietf@ietf.org mailing lists by 2011-09-16. Exceptionally, comments may be
>
>
>The draft only mentions an applicability and justification for Shared
>Transition Space and references
>draft-bdgks-arin-shared-transition-space-00.  While the policy fits
>under RIR community processes, it does not fit under allocations made
>for technical specifications.  Publishing this document on the
>grounds that the ARIN wants it is not a good enough reason.  Will
>ARIN be "donating" the /10 IPv4 address space to IANA for it to make
>this allocation?
This proposal reached ARIN consensus (2011-5), and has been recommended
for adoption to the ARIN board. The ARIN BoD has indicated that it is
willing to reserve a /10 if asked to do so by the IETF/IANA.


>
>The draft mentions that:
>
>   "Network equipment manufacturers MUST NOT use the
>    assigned block in default or example device configurations."
>
>As the IPv4 address block is not specified in the document, the above
>requirement cannot be followed.  The expectation that the IPv4
>address block will only be used by Infrastructure Providers is
>optimistic. =20
This will be supplied by IANA in consultation with ARIN.  ARIN has not
pre-announced what block might be used, so we need to wait until IANA gets
back to us later in the process.

>RFC 5735 covers Special Use IPv4 Addresses.  This
>document should update the BCP.
Once we get an assignment from IANA/ARIN, we'll look into updating RFC
5735.
>
>A proposal similar to this one was discussed in a V6OPS meeting in
>Asia.  If my reading is correct, it did not gain consensus.  The
>proposal gets discussed in North America in
>OPSAWG and it gains consensus.
Not quite right. We first brought this proposal to OPSAWG in Maastricht,
and then updated it for Beijing.  From the opsawg (79) minutes:
> Straw poll: more people in the room supported the draft than didn't,
> perhaps 2:1. About half the room expressed an opinion.

Because IANA was down to its final /8, we were asked to also present in
v6ops, which did not reach consensus for or against. Feedback from v6ops
was to approach the RIRs for space, rather than IANA, which we did.

> BTW, this draft contains only 220
>lines, including boilerplate and it has five authors.
How is this relevant? Jason, Victor, and I have been working on this for
over a year.  Chris L and Marla joined the author team with significant
contributions when we substantially updated the draft prior to IETF79.

Chris
>
>Regards,
>-sm=20
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From brian.e.carpenter@gmail.com  Mon Aug 22 15:52:56 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F095721F8B87 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 15:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.295
X-Spam-Level: 
X-Spam-Status: No, score=-103.295 tagged_above=-999 required=5 tests=[AWL=-0.296, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJfw7JSIKvDl for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 15:52:56 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 54EDA21F8B1D for <ietf@ietf.org>; Mon, 22 Aug 2011 15:52:56 -0700 (PDT)
Received: by gwb20 with SMTP id 20so4166563gwb.31 for <ietf@ietf.org>; Mon, 22 Aug 2011 15:54:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Y74sA1ZgiLwVZdv5pBf2o7SMmbla9GX2CQEr9M4gGAw=; b=WT5xE+P2IdvcQwAbTMepmPRcPQhnwWalumXg8Z4vBk3+xFXjX4ybBaVEFUHYz+LEHa qWNKKghGAWghbVz8BoERu5XLR8rYVav1UXrmHviYP02njTQzjDX9NdFoX+DtOguFS0dp ItExuPfNNk97SU56jIIed+9H97nFLWrymeje0=
Received: by 10.236.116.194 with SMTP id g42mr18558423yhh.0.1314053641175; Mon, 22 Aug 2011 15:54:01 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id c63sm154055yhe.4.2011.08.22.15.53.58 (version=SSLv3 cipher=OTHER); Mon, 22 Aug 2011 15:54:00 -0700 (PDT)
Message-ID: <4E52DE03.8020201@gmail.com>
Date: Tue, 23 Aug 2011 10:53:55 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110820031053.0a551ca8@resistor.net>	<005b01cc609a$7e9ab540$4001a8c0@gateway.2wire.net> <01O55J38IMQU00VHKR@mauve.mrochek.com>
In-Reply-To: <01O55J38IMQU00VHKR@mauve.mrochek.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 22:52:57 -0000

+1 to Ned. I can't see why this draft seems to make some people
go defensive - it isn't saying "IPv4 is evil" or anything silly
like that, it's just saying "IPv6 is the future".

RFC1122v6 is another matter entirely. We clearly aren't ready
for it yet, but draft-ietf-6man-node-req-bis is a step on the way.

Regards
   Brian

On 2011-08-23 08:54, ned+ietf@mauve.mrochek.com wrote:
>> I find this document utterly bizarre and think it would seriously damage the
>> Internet to publish it.
> 
> This seems a little ... extreme. The document appears to me to be Mostly
> Harmless, with all that implies.
> 
>> The idea that ipv6 should be regarded as normal, as of equal standing to ipv4 is
>> fine, the sort of statement that the IAB should make, or have made, as an RFC or
>> in some other form.
> 
>> But this I-D claims
>> " Updates [RFC1122] to clarify that this document, especially in
>>    section 3, primarily discusses IPv4 where it uses the more generic
>>    term "IP" and is no longer a complete definition of "IP" or the
>>    Internet Protocol suite by itself.  "
> 
>> IPv4 is a phenomenal success, and RFC1122 is a key part of that.  IPv4 was a
>> confused jumble, as IPv6 is now, and RFC1122, with another two or so I-Ds, cut
>> through the cruft and rendered it usable.  IPv6 desparately needs an equivalent
>> to RFC1122,
> 
> Complete agreement on this point. Such a document, informed by actual IPv6
> deployment experience at some sort of scale, is urgently needed. And this most
> certainly is NOT that document. But unless publishing this is seen as meeting
> the need for an 1122v6 - and I've seen no indication that's the case - I fail
> to see the harm.
> 
> OTOH, if this really is seen as being a 1122v6, then I join you in opposing
> it's publication.
> 
>> as a trawl of the v6ops list archives shows, and clearly this I-D is
>> never going to be it, but claiming that this I-D provides an update to RFC1122,
>> coupled
>> with its title, gives the message that there is not going to be such an I-D;
>> IPv6 will remain a confused jumble (and so is unlikely ever to emulate the
>> success of IPv4).
> 
> Maybe I'm being clueless about this, but I don't see how "IPv6 Support Required
> for all IP-capable nodes" gives this impression.
> 
> 				Ned
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From jmpolk@cisco.com  Mon Aug 22 15:53:56 2011
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B1D321F8C83; Mon, 22 Aug 2011 15:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.6
X-Spam-Level: 
X-Spam-Status: No, score=-103.6 tagged_above=-999 required=5 tests=[AWL=-1.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OX87ei6NPDsY; Mon, 22 Aug 2011 15:53:55 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id A16DB21F8C80; Mon, 22 Aug 2011 15:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=945; q=dns/txt; s=iport; t=1314053702; x=1315263302; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=W4V+3+qB2ZVAtSwun2ZcnRUhboBeuSdUq6cjadirfO4=; b=Csv1A9YLo9cGWXGg4VXLydPrbgwvQkbr1hJ2uArvOzQC1pKqwMgyXt1Z H227elz/QjsvvYPOeo0RoEoXbNJsSjNmMzYn8tHA5mNQCNbnYQza+pNJg cDnELEYYEJ2+24qYZ3g6VfN6KUqW/YA1M7BWtJjxON5rmvHrEvGvnDyZI g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAATdUk6rRDoJ/2dsb2JhbABBqB53gUABAQEBAwEBAQ8BJQI0CxAHBBgeEBkOMAYBEiKHU5ZBAZ8WhkgEh2CcSQ
X-IronPort-AV: E=Sophos;i="4.68,266,1312156800"; d="scan'208";a="15472008"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-2.cisco.com with ESMTP; 22 Aug 2011 22:55:01 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7MMt0QS026344; Mon, 22 Aug 2011 22:55:00 GMT
Message-Id: <201108222255.p7MMt0QS026344@mtv-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 22 Aug 2011 17:54:47 -0500
To: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: Experiment for different schedule for Friday
In-Reply-To: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 22:53:56 -0000

At 04:24 PM 8/22/2011, IETF Chair wrote:
>The IESG is considering a different schedule for the Friday of IETF 
>82.  The IESG is seeking your input on these potential changes.
>
>The IESG would like to try a schedule experiment on Friday, using 
>this schedule:
>
>  9:00 AM - 11:00 AM - Session I
>11:00 AM - 11:20 AM - Room Change and Cookie Break
>11:20 AM - 12:20 PM - Session II
>12:10 PM - 12:30 PM - Room Change Break
>12:30 PM - 13:30 PM - Session III

since there will be cookies, this is ok with me  ;-)


>The IESG has already consulted with the IAOC because of the cost 
>associated with the additional food and beverage break.  The IAOC 
>believes that the additional cost can be managed without raising the 
>meeting fee.

bonus

James


>On behalf of the IESG,
>    Russ
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From brian.e.carpenter@gmail.com  Mon Aug 22 16:02:31 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6A9621F8B3A for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 16:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.592
X-Spam-Level: 
X-Spam-Status: No, score=-103.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVsfKlwfnGHM for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 16:02:31 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4D021F8B36 for <ietf@ietf.org>; Mon, 22 Aug 2011 16:02:31 -0700 (PDT)
Received: by yxj17 with SMTP id 17so3206213yxj.31 for <ietf@ietf.org>; Mon, 22 Aug 2011 16:03:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=f0pPBfaERidmyMsT7NGOskUvi0oPkQ6fNaAnLGLJAvI=; b=hcxzAcfPyKdc/j0cPk2XKwhw6a747EqPkXhG1d3o9lNjWnOuXfbu8ER29+KkuYTAfh 2uZylSE+VUK2svLaUkbRB30H/W70uIHK4wnMWAdIytGgN5om0ZqxRWw/Lyf2QiIjda+5 QFfaPc5gzPyVr6HkV4GeCBw19wZ2eDqmPKKCE=
Received: by 10.236.177.65 with SMTP id c41mr18186707yhm.16.1314054217189; Mon, 22 Aug 2011 16:03:37 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id a29sm52798yhj.17.2011.08.22.16.03.35 (version=SSLv3 cipher=OTHER); Mon, 22 Aug 2011 16:03:36 -0700 (PDT)
Message-ID: <4E52E044.4040100@gmail.com>
Date: Tue, 23 Aug 2011 11:03:32 +1200
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: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt>
References: <CAHhFybrTaLGODUpR38KKKT-g4kkWkYRqXePMvezm0a8BpwPj2w@mail.gmail.com>
In-Reply-To: <CAHhFybrTaLGODUpR38KKKT-g4kkWkYRqXePMvezm0a8BpwPj2w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 23:02:32 -0000

Frank,

On 2011-08-23 00:09, Frank Ellermann wrote:
> Nothing is wrong in BCP 104, it needs no "updated by" moving the definition
> of the term "version support" from one of its sections to another section.

But there *is* something wrong with it - it makes IPv6 sound
like an optional add-on to basic IP service.

I thought this was a bug in BCP 104 at the time, and told the
author so, but lost that argument. That was reasonable in
2004/5, but things have moved on. Then, an ISP could argue that
providing IPv6 service was difficult or impossible; today, that
excuse is weak.

On 2011-08-23 07:44, George, Wesley wrote:

> Brian was the one who originally suggested this RFC be added as updated by this draft, so I'm keen to hear his opinion as well.

Well, I'm not sure there is much point in wordsmithing BCP 104
beyond simply moving version support up into first class, but I
am completely convinced that should be done.

   Brian

From randy@qualcomm.com  Mon Aug 22 16:32:18 2011
Return-Path: <randy@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D6E21F8B30; Mon, 22 Aug 2011 16:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R92WENXvMNKR; Mon, 22 Aug 2011 16:32:17 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 7E81221F8B2C; Mon, 22 Aug 2011 16:32:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1314056003; x=1345592003; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240613ca789572bf5f@loud.pensive.org> |In-Reply-To:=20<0E41725E-77C3-4DEF-BEE7-8220623B4AE9@iet f.org>|References:=20<0E41725E-77C3-4DEF-BEE7-8220623B4AE 9@ietf.org>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date: =20Mon,=2022=20Aug=202011=2016:28:34=20-0700|To:=20IETF =20Chair=20<chair@ietf.org>,=20IETF=20<ietf@ietf.org> |From:=20Randall=20Gellens=20<randy@qualcomm.com> |Subject:=20Re:=20Experiment=20for=20different=20schedule =20for=20Friday|CC:=20IESG=20<iesg@ietf.org> |MIME-Version:=201.0|Content-Type:=20text/plain=3B=20char set=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.39.5]; bh=4ZBa31Fd0r1PitficBtyHsj+KSX6q7KP4b0USZ6d2SU=; b=gUf4hbMN6aIyiTa/DrT9e/yA/P8LazXJIVRK9W+UxGqaeYUifjvS2ico dETIAtF7RJ6WLt36KFvPxWaQ51gZuEVMzpmwJf5hd+ST3ANdLRPJJfXRs PIe1IS1D8l9UdD38X4is3aH/ViDNDi4SIzSZgQtHgEpY6x/yKN9PGm6rZ o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6446"; a="111959419"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine02.qualcomm.com with ESMTP; 22 Aug 2011 16:33:22 -0700
X-IronPort-AV: E=Sophos;i="4.68,263,1312182000"; d="scan'208";a="118513371"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 22 Aug 2011 16:33:22 -0700
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 22 Aug 2011 16:33:21 -0700
Message-ID: <p06240613ca789572bf5f@loud.pensive.org>
In-Reply-To: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
X-Mailer: Eudora for Mac OS X
Date: Mon, 22 Aug 2011 16:28:34 -0700
To: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Experiment for different schedule for Friday
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 23:32:18 -0000

At 5:24 PM -0400 8/22/11, IETF Chair wrote:

>  The IESG is considering a different schedule for the Friday of IETF 
> 82.  The IESG is seeking your input on these potential changes.
>
>  The IESG would like to try a schedule experiment on Friday, using 
> this schedule:
>
>   9:00 AM - 11:00 AM - Session I
>  11:00 AM - 11:20 AM - Room Change and Cookie Break
>  11:20 AM - 12:20 PM - Session II
>  12:10 PM - 12:30 PM - Room Change Break
>  12:30 PM - 13:30 PM - Session III

I'd suggest shortening the first session and eliminating the cookie break, so:

  9:00 AM - 10:30 AM: Session I
10:30 AM - 10:40 AM: room change
10:40 AM - 11:40 AM: Session II
11:40 AM - 11:50 AM: room change
11:50 AM - 12:50 PM: Session III

I don't think 20 minutes is sufficient for a cookie break and room 
change, and think we can go without in order to be done sooner. 
However, if people really want cookies, perhaps they could be in the 
meeting rooms during Session II instead of centrally?

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If you can't annoy somebody there's little point in writing --Kingsley Amis

From warren@kumari.net  Mon Aug 22 16:38:14 2011
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42CBB21F8B8A; Mon, 22 Aug 2011 16:38:14 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1cd4XuP84qap; Mon, 22 Aug 2011 16:38:13 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB4C21F8B95; Mon, 22 Aug 2011 16:38:13 -0700 (PDT)
Received: from [192.168.0.203] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 8EA981B402CF; Mon, 22 Aug 2011 19:39:17 -0400 (EDT)
Subject: Re: [IETF] Re: Experiment for different schedule for Friday
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <p06240613ca789572bf5f@loud.pensive.org>
Date: Mon, 22 Aug 2011 19:39:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <816950BB-AE8D-40E6-8C70-8112C7826813@kumari.net>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <p06240613ca789572bf5f@loud.pensive.org>
To: Randall Gellens <randy@qualcomm.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 23:38:14 -0000

On Aug 22, 2011, at 7:28 PM, Randall Gellens wrote:

> At 5:24 PM -0400 8/22/11, IETF Chair wrote:
>=20
>> The IESG is considering a different schedule for the Friday of IETF =
82.  The IESG is seeking your input on these potential changes.
>>=20
>> The IESG would like to try a schedule experiment on Friday, using =
this schedule:
>>=20
>>  9:00 AM - 11:00 AM - Session I
>> 11:00 AM - 11:20 AM - Room Change and Cookie Break
>> 11:20 AM - 12:20 PM - Session II
>> 12:10 PM - 12:30 PM - Room Change Break
>> 12:30 PM - 13:30 PM - Session III
>=20
> I'd suggest shortening the first session and eliminating the cookie =
break, so:
>=20
> 9:00 AM - 10:30 AM: Session I
> 10:30 AM - 10:40 AM: room change
> 10:40 AM - 11:40 AM: Session II
> 11:40 AM - 11:50 AM: room change
> 11:50 AM - 12:50 PM: Session III
>=20
> I don't think 20 minutes is sufficient for a cookie break and room =
change, and think we can go without in order to be done sooner. However, =
if people really want cookies, perhaps they could be in the meeting =
rooms during Session II instead of centrally?

Or perhaps they could plan ahead a little and grab a cookie or two (and =
some coffee) before the meeting=85.

W


>=20
> --=20
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself =
only
> -------------- Randomly selected tag: ---------------
> If you can't annoy somebody there's little point in writing --Kingsley =
Amis
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From rpelletier@isoc.org  Mon Aug 22 17:14:03 2011
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBA421F8B4C for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:14:03 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q+2iL7m2Kmyz for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:14:03 -0700 (PDT)
Received: from smtp157.iad.emailsrvr.com (smtp157.iad.emailsrvr.com [207.97.245.157]) by ietfa.amsl.com (Postfix) with ESMTP id C3E1621F8B18 for <ietf@ietf.org>; Mon, 22 Aug 2011 17:14:02 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp35.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 490192C8377; Mon, 22 Aug 2011 20:15:07 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp35.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 1EED62C8142;  Mon, 22 Aug 2011 20:15:07 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <20110822191708.652C721F8C19@ietfa.amsl.com>
Date: Mon, 22 Aug 2011 20:15:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1084)
Cc: ietf-secretariat@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 00:14:03 -0000

On Aug 22, 2011, at 3:17 PM, Michael StJohns wrote:

> Hi folks -=20
>=20
> I just reserved with the hotel and was quite surprised at the =
cancellation policy.
>=20
> Could you please confirm - Cancel before 1 Nov - no charge, 1-7 Nov 1 =
night, after 7 Nov full amount?

As stated on the meeting site:  =
<http://www.ietf.org/meeting/82/hotel.html>

Guest Cancellation: Individuals may cancel reservations without penalty =
until 7 days prior to scheduled check-in/arrival. In case of =
cancellation between 3 and 7 days prior to scheduled check-in/arrival, =
the Hotel holds the right to charge the individuals one night=92s stay =
as a cancellation fee. In case of cancellation less than 3 days prior to =
the scheduled check-in/arrival or non-arrival or no-show, the Hotel =
holds the right to charge the individuals for the entire scheduled stay =
as a cancellation fee.

We strive at each meeting to get the best cancellation policies that we =
can, looking for a 1 day cancellation penalty for a cancellation.  =
Often, in Asia and Europe in particular, they will not agree to this. We =
did negotiate this pretty heavily to get the terms we now have.  =
Originally, the hotel wanted to the entire stay to be charged for =
cancellation or no-show at the cut-off date (26 October). =20

While this may only a solution for some, names may be substituted =
without penalty up to the event.

Guest Substitution: Guests may substitute names for reserved rooms =
without penalty up to the event.

Ray

>=20
> Seriously?  This is extreme. I can understand a 1 day fee up to the =
date of the reservation and maybe even charging the full amount if I =
don't cancel, but paying $1500+ because I had to cancel at the last =
moment seems a bit confiscatory. =20
>=20
> Mike
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rpelletier@isoc.org  Mon Aug 22 17:15:32 2011
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD5A21F863A for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.431
X-Spam-Level: 
X-Spam-Status: No, score=-103.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SD7VgTtFibau for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:15:32 -0700 (PDT)
Received: from smtp157.iad.emailsrvr.com (smtp157.iad.emailsrvr.com [207.97.245.157]) by ietfa.amsl.com (Postfix) with ESMTP id 3BEE721F84DA for <ietf@ietf.org>; Mon, 22 Aug 2011 17:15:32 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp35.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 6D1FD2C84DE; Mon, 22 Aug 2011 20:16:38 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp35.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 484D82C82ED;  Mon, 22 Aug 2011 20:16:38 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>
Date: Mon, 22 Aug 2011 20:16:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>
To: Lixia Zhang <lixia@cs.ucla.edu>
X-Mailer: Apple Mail (2.1084)
Cc: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 00:15:32 -0000

On Aug 22, 2011, at 3:53 PM, Lixia Zhang wrote:

>=20
> Since you brought up the subject of hotel: up to now IETF hotel prices =
have been within the federal per diem allowance, but IETF82 seems an =
exception by a pretty big gap (see =
http://aoprals.state.gov/web920/per_diem_action.asp?MenuHide=3D1&CountryCo=
de=3D1142, lodging allowance $186/day, a single room at Hyatt is =
$263/day with 10% tax)

As for the rates, they are high.  Taiwan is expensive, particularly =
given that the hotels know what our options are when we book the TICC.  =
The Hyatt knew that foreign visitors needed to use the Hyatt as =
headquarters and charged accordingly.  Since the time of our site visit, =
2 new hotels have been constructed in the vicinity of the TICC (Le =
Meridien and W), which may provide more competition for Hyatt in these =
circumstances.  At the time we were working on this event, there were no =
acceptable options.

Ray

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


From dhc2@dcrocker.net  Mon Aug 22 17:28:50 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0F0021F86F6 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.915
X-Spam-Level: 
X-Spam-Status: No, score=-5.915 tagged_above=-999 required=5 tests=[AWL=0.684,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 40sbQUp9byAX for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:28:50 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3882A21F86AF for <ietf@ietf.org>; Mon, 22 Aug 2011 17:28:50 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7N0TpVf017068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 22 Aug 2011 17:29:56 -0700
Message-ID: <4E52F47D.1050300@dcrocker.net>
Date: Mon, 22 Aug 2011 17:29:49 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Alternative to the Hyatt
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>
In-Reply-To: <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 22 Aug 2011 17:29:56 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 00:28:50 -0000

On 8/22/2011 5:16 PM, Ray Pelletier wrote:
> The Hyatt knew that foreign visitors needed to use the Hyatt as headquarters


Folks,

For reference, I found the AT Boutique Hotel, near the Convention Center.

Tripadvisor comments are generally positive and the facilities are claimed to be 
newish.  Photos look fine.  Modest, workable place. Breakfast and wifi included.

Prices are entirely reasonable, although of course you get a small room.

They have a book-ahead special that doesn't seem to be available through the 
online system.  I got it by faxing the hotel.  It gives you the windowless rate 
for a room with a window...

The Hyatt is a bit northeast of the Center.  The Boutique is a bit southwest.

d/

ps. They have a page in English, and the fellow responding with a fax produced 
easy English, but it's clear this hotel is not targeted for English speakers. 
My usual experience at such places is that there is enough
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From marshall.eubanks@gmail.com  Mon Aug 22 17:29:30 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9559B21F874E; Mon, 22 Aug 2011 17:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.239
X-Spam-Level: 
X-Spam-Status: No, score=-103.239 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XA3mivA5gX7v; Mon, 22 Aug 2011 17:29:29 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 818F921F89BA; Mon, 22 Aug 2011 17:29:29 -0700 (PDT)
Received: by ywe9 with SMTP id 9so902095ywe.31 for <multiple recipients>; Mon, 22 Aug 2011 17:30:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OLpmcDUSl6LHTpdpK8zdfH/hEdfR1IKHt/ln5ij0EnE=; b=n+Po9VaVxn/5CsN6Sjtwo5w7ZkRM5rwVdqQ5NedUnumhFhQZ/a9RP5pWcZihI6AWKR srr7WR6ezeluDOuSB1bc+/jcVXBA+Zla1ZjokwTgYBMJUf1KSHL13IYrPQFHfZAza49S ezd3UQP3IGV1o/iEyhXZsXAofdyDkF6Rn/vCw=
MIME-Version: 1.0
Received: by 10.150.164.1 with SMTP id m1mr3184216ybe.297.1314059434445; Mon, 22 Aug 2011 17:30:34 -0700 (PDT)
Received: by 10.150.202.16 with HTTP; Mon, 22 Aug 2011 17:30:34 -0700 (PDT)
In-Reply-To: <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>
Date: Mon, 22 Aug 2011 20:30:34 -0400
Message-ID: <CAJNg7VLbXeX668C7Krc8FUafK_X6J1_4jVymYnOOU7e0St2bqg@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Ray Pelletier <rpelletier@isoc.org>
Content-Type: multipart/alternative; boundary=000e0cd58ca0cdcd2b04ab214d8c
Cc: ietf-secretariat@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 00:29:30 -0000

--000e0cd58ca0cdcd2b04ab214d8c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 22, 2011 at 8:15 PM, Ray Pelletier <rpelletier@isoc.org> wrote:

>
> On Aug 22, 2011, at 3:17 PM, Michael StJohns wrote:
>
> > Hi folks -
> >
> > I just reserved with the hotel and was quite surprised at the
> cancellation policy.
> >
> > Could you please confirm - Cancel before 1 Nov - no charge, 1-7 Nov 1
> night, after 7 Nov full amount?
>
> As stated on the meeting site:  <http://www.ietf.org/meeting/82/hotel.htm=
l
> >
>
> Guest Cancellation: Individuals may cancel reservations without penalty
> until 7 days prior to scheduled check-in/arrival. In case of cancellation
> between 3 and 7 days prior to scheduled check-in/arrival, the Hotel holds
> the right to charge the individuals one night=92s stay as a cancellation =
fee.
> In case of cancellation less than 3 days prior to the scheduled
> check-in/arrival or non-arrival or no-show, the Hotel holds the right to
> charge the individuals for the entire scheduled stay as a cancellation fe=
e.
>
> We strive at each meeting to get the best cancellation policies that we
> can, looking for a 1 day cancellation penalty for a cancellation.  Often,=
 in
> Asia and Europe in particular, they will not agree to this. We did negoti=
ate
> this pretty heavily to get the terms we now have.  Originally, the hotel
> wanted to the entire stay to be charged for cancellation or no-show at th=
e
> cut-off date (26 October).
>
> While this may only a solution for some, names may be substituted without
> penalty up to the event.
>
> Guest Substitution: Guests may substitute names for reserved rooms withou=
t
> penalty up to the event.
>
>
This sounds like a good use of the Attendees list. Anyone with reservations
who can't come should publicize it - I am sure that there will be  people
who want to come but can't get reservations.

Regards
Marshall


> Ray
>
> >
> > Seriously?  This is extreme. I can understand a 1 day fee up to the dat=
e
> of the reservation and maybe even charging the full amount if I don't
> cancel, but paying $1500+ because I had to cancel at the last moment seem=
s a
> bit confiscatory.
> >
> > Mike
> >
> > _______________________________________________
> > 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
>

--000e0cd58ca0cdcd2b04ab214d8c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Aug 22, 2011 at 8:15 PM, Ray Pel=
letier <span dir=3D"ltr">&lt;<a href=3D"mailto:rpelletier@isoc.org">rpellet=
ier@isoc.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br>
On Aug 22, 2011, at 3:17 PM, Michael StJohns wrote:<br>
<br>
&gt; Hi folks -<br>
&gt;<br>
&gt; I just reserved with the hotel and was quite surprised at the cancella=
tion policy.<br>
&gt;<br>
&gt; Could you please confirm - Cancel before 1 Nov - no charge, 1-7 Nov 1 =
night, after 7 Nov full amount?<br>
<br>
</div>As stated on the meeting site: =A0&lt;<a href=3D"http://www.ietf.org/=
meeting/82/hotel.html" target=3D"_blank">http://www.ietf.org/meeting/82/hot=
el.html</a>&gt;<br>
<br>
Guest Cancellation: Individuals may cancel reservations without penalty unt=
il 7 days prior to scheduled check-in/arrival. In case of cancellation betw=
een 3 and 7 days prior to scheduled check-in/arrival, the Hotel holds the r=
ight to charge the individuals one night=92s stay as a cancellation fee. In=
 case of cancellation less than 3 days prior to the scheduled check-in/arri=
val or non-arrival or no-show, the Hotel holds the right to charge the indi=
viduals for the entire scheduled stay as a cancellation fee.<br>

<br>
We strive at each meeting to get the best cancellation policies that we can=
, looking for a 1 day cancellation penalty for a cancellation. =A0Often, in=
 Asia and Europe in particular, they will not agree to this. We did negotia=
te this pretty heavily to get the terms we now have. =A0Originally, the hot=
el wanted to the entire stay to be charged for cancellation or no-show at t=
he cut-off date (26 October).<br>

<br>
While this may only a solution for some, names may be substituted without p=
enalty up to the event.<br>
<br>
Guest Substitution: Guests may substitute names for reserved rooms without =
penalty up to the event.<br>
<font color=3D"#888888"><br></font></blockquote><div><br></div><div>This so=
unds like a good use of the Attendees list. Anyone with reservations who ca=
n&#39;t come should publicize it - I am sure that there will be =A0people w=
ho want to come but can&#39;t get reservations.</div>
<div><br></div><div>Regards</div><div>Marshall</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;"><font color=3D"#888888">
Ray<br>
</font><div><div></div><div class=3D"h5"><br>
&gt;<br>
&gt; Seriously? =A0This is extreme. I can understand a 1 day fee up to the =
date of the reservation and maybe even charging the full amount if I don&#3=
9;t cancel, but paying $1500+ because I had to cancel at the last moment se=
ems a bit confiscatory.<br>

&gt;<br>
&gt; Mike<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>
<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>

--000e0cd58ca0cdcd2b04ab214d8c--

From hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com  Mon Aug 22 17:41:16 2011
Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC9B621F8888 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level: 
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wy69QgPmwdzG for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 17:41:16 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id E439021F893C for <ietf@ietf.org>; Mon, 22 Aug 2011 17:41:15 -0700 (PDT)
Received: by fxe6 with SMTP id 6so4001216fxe.31 for <ietf@ietf.org>; Mon, 22 Aug 2011 17:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=28ZMXusRvl1/So+PYog6U++MIWjrcNp8nljqtfV6YPg=; b=El3PPnq+kzCN1G8NT+fEQ0CAoNQ4h7al8/gfsuRTNNeHedkNF/VqBnnLTDVX+GdRTI jc0+OfcjUf3hSWZtG8XWoP2RkZA1gpbzuv7Qy4cAfH0eEEbTKqarQOz71y7SCWju4jGR vZF3F1k2GrdyAU3PcgV6diCE2yli8eu9ly7po=
Received: by 10.223.22.8 with SMTP id l8mr4459084fab.105.1314060141651; Mon, 22 Aug 2011 17:42:21 -0700 (PDT)
Received: from [10.145.41.4] ([89.204.153.132]) by mx.google.com with ESMTPS id 14sm3455373faf.32.2011.08.22.17.42.19 (version=SSLv3 cipher=OTHER); Mon, 22 Aug 2011 17:42:20 -0700 (PDT)
Message-ID: <4E52F768.8020402@gmail.com>
Date: Tue, 23 Aug 2011 02:42:16 +0200
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt>
References: <CAHhFybrTaLGODUpR38KKKT-g4kkWkYRqXePMvezm0a8BpwPj2w@mail.gmail.com> <4E52E044.4040100@gmail.com>
In-Reply-To: <4E52E044.4040100@gmail.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 00:41:16 -0000

Am 2011-08-23 01:03, schrieb Brian E Carpenter:

>> Nothing is wrong in BCP 104, it needs no "updated by" moving the definition
>> of the term "version support" from one of its sections to another section.

> But there *is* something wrong with it - it makes IPv6 sound
> like an optional add-on to basic IP service.

> I thought this was a bug in BCP 104 at the time, and told the
> author so, but lost that argument. That was reasonable in
> 2004/5, but things have moved on. Then, an ISP could argue that
> providing IPv6 service was difficult or impossible; today, that
> excuse is weak.

This is a very important BCP.  It is about non-Internet providers
claiming to be ISPs while favouring packets by IP or manipulating
DNS.  Not offering IPv6 in 2011 also isn't nice, but if the latter
requires new text it should be in a new BCP.  While at it the new
BCP could reference 4409bis instead of RFC 2476.

Getting an "updated by" only as some kind of IPv6 promotion would
IMHO not help with the main purpose of this BCP.

-Frank

From dhc2@dcrocker.net  Mon Aug 22 19:00:03 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D40F21F8AF6 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 19:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.991
X-Spam-Level: 
X-Spam-Status: No, score=-5.991 tagged_above=-999 required=5 tests=[AWL=0.608,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBb80B2+lH1C for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 19:00:02 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3CB3021F8AFA for <ietf@ietf.org>; Mon, 22 Aug 2011 19:00:02 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7N212Cb019060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Aug 2011 19:01:07 -0700
Message-ID: <4E5309DD.6080006@dcrocker.net>
Date: Mon, 22 Aug 2011 19:01:01 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, ietf@ietf.org
Subject: Re: Alternative to the Hyatt
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <4E52F47D.1050300@dcrocker.net>
In-Reply-To: <4E52F47D.1050300@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]); Mon, 22 Aug 2011 19:01:08 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 02:00:03 -0000

Clarification:

The special rate is listed as the Early Bird Package on the website.  That part 
/is/ available.  It's the actual booking that doesn't seem to handle it.

d/

On 8/22/2011 5:29 PM, Dave CROCKER wrote:
> For reference, I found the AT Boutique Hotel, near the Convention Center.
>
> Tripadvisor comments are generally positive and the facilities are claimed to be
> newish. Photos look fine. Modest, workable place. Breakfast and wifi included.
>
> Prices are entirely reasonable, although of course you get a small room.
>
> They have a book-ahead special that doesn't seem to be available through the
> online system. I got it by faxing the hotel. It gives you the windowless rate
> for a room with a window...

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mstjohns@comcast.net  Mon Aug 22 19:20:40 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 775BF21F8634 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 19:20:40 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqPbV0UO5n69 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 19:20:39 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id EC4DE21F87D9 for <ietf@ietf.org>; Mon, 22 Aug 2011 19:20:38 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by QMTA11.westchester.pa.mail.comcast.net with comcast id PeCo1h0021ap0As5BeMl9E; Tue, 23 Aug 2011 02:21:45 +0000
Received: from Mike-PC3.comcast.net ([68.83.217.57]) by omta22.westchester.pa.mail.comcast.net with comcast id PeMj1h00h1EtFYL3ieMk37; Tue, 23 Aug 2011 02:21:45 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 22 Aug 2011 22:21:20 -0400
To: Ray Pelletier <rpelletier@isoc.org>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110823022038.EC4DE21F87D9@ietfa.amsl.com>
Cc: ietf-secretariat@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 02:20:40 -0000

Hi Ray - 

See below

At 08:15 PM 8/22/2011, Ray Pelletier wrote:

>On Aug 22, 2011, at 3:17 PM, Michael StJohns wrote:
>
>> Hi folks - 
>> 
>> I just reserved with the hotel and was quite surprised at the cancellation policy.
>> 
>> Could you please confirm - Cancel before 1 Nov - no charge, 1-7 Nov 1 night, after 7 Nov full amount?
>
>As stated on the meeting site:  <http://www.ietf.org/meeting/82/hotel.html>
>
>Guest Cancellation: Individuals may cancel reservations without penalty until 7 days prior to scheduled check-in/arrival. In case of cancellation between 3 and 7 days prior to scheduled check-in/arrival, the Hotel holds the right to charge the individuals one night’s stay as a cancellation fee. In case of cancellation less than 3 days prior to the scheduled check-in/arrival or non-arrival or no-show, the Hotel holds the right to charge the individuals for the entire scheduled stay as a cancellation fee.


The policy stated on the hotel web site (to which I had to agree to get the reservation)  was Nov 1-7 1 day, after Nov 7 - full amount.  Obviously a disconnect.



>We strive at each meeting to get the best cancellation policies that we can, looking for a 1 day cancellation penalty for a cancellation.  Often, in Asia and Europe in particular, they will not agree to this. We did negotiate this pretty heavily to get the terms we now have.  Originally, the hotel wanted to the entire stay to be charged for cancellation or no-show at the cut-off date (26 October).  

Could you refresh my memory as to which hotels we stayed at had this policy?  I literally cannot remember having any hotel cancellation policy with more than a single night fee ever.  

I will point out there are at least two hotels in walking distance with only slightly more expensive rack rates that have only a 1 night fee if you don't cancel at least 24 hours in advance.  It may be useful to have the hotel re-address the cancellation fee issue in light of that.

Thanks - Mike




>While this may only a solution for some, names may be substituted without penalty up to the event.
>
>Guest Substitution: Guests may substitute names for reserved rooms without penalty up to the event.
>
>Ray
>
>> 
>> Seriously?  This is extreme. I can understand a 1 day fee up to the date of the reservation and maybe even charging the full amount if I don't cancel, but paying $1500+ because I had to cancel at the last moment seems a bit confiscatory.  
>> 
>> Mike
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf



From mstjohns@comcast.net  Mon Aug 22 20:11:58 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D556C21F8B3D for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 20:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.333
X-Spam-Level: 
X-Spam-Status: No, score=-102.333 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lR1J2ZYjIFpp for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 20:11:57 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by ietfa.amsl.com (Postfix) with ESMTP id 1666821F8B3C for <ietf@ietf.org>; Mon, 22 Aug 2011 20:11:56 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta09.westchester.pa.mail.comcast.net with comcast id PfAd1h0030xGWP859fCy0b; Tue, 23 Aug 2011 03:12:58 +0000
Received: from Mike-PC3.comcast.net ([68.83.217.57]) by omta12.westchester.pa.mail.comcast.net with comcast id PfCp1h02M1EtFYL3YfCue8; Tue, 23 Aug 2011 03:12:57 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 22 Aug 2011 23:12:26 -0400
To: Marshall Eubanks <marshall.eubanks@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <CAJNg7VLbXeX668C7Krc8FUafK_X6J1_4jVymYnOOU7e0St2bqg@mail.g mail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <CAJNg7VLbXeX668C7Krc8FUafK_X6J1_4jVymYnOOU7e0St2bqg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_810431917==.ALT"
Message-Id: <20110823031157.1666821F8B3C@ietfa.amsl.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 03:11:58 -0000

--=====================_810431917==.ALT
Content-Type: text/plain; charset="us-ascii"



At 08:30 PM 8/22/2011, Marshall Eubanks wrote:
>Guest Substitution: Guests may substitute names for reserved rooms without penalty up to the event.
>
>
>This sounds like a good use of the Attendees list. Anyone with reservations who can't come should publicize it - I am sure that there will be  people who want to come but can't get reservations.


Sorry Marshall - you're mostly trying to solve a different problem.  For Hiroshima, I literally decided not to come at the last minute. And my scheduled travel was such that I was able to cancel prior to 24 hours so I didn't even incur the 1 day fee.  

Anyone going to Taipei is pretty much going to have everything scheduled prior to 24 hours before arrival (or maybe risk sleeping on the street or 10 miles away).  The chance of being able to find someone to take your reservation with less than 72 hours to go is pretty slim - especially considering the other hotel in the block also requires 72 hour notice to cancel.

Later, Mike



>Regards
>Marshall


--=====================_810431917==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
<br><br>
At 08:30 PM 8/22/2011, Marshall Eubanks wrote:<br>
<blockquote type=cite class=cite cite="">
<dl>
<dd>Guest Substitution: Guests may substitute names for reserved rooms
without penalty up to the event.<br>
<font color="#888888"><br>
</font>
</dl><br>
This sounds like a good use of the Attendees list. Anyone with
reservations who can't come should publicize it - I am sure that there
will be&nbsp; people who want to come but can't get
reservations.</blockquote><br><br>
Sorry Marshall - you're mostly trying to solve a different problem.&nbsp;
For Hiroshima, I literally decided not to come at the last minute. And my
scheduled travel was such that I was able to cancel prior to 24 hours so
I didn't even incur the 1 day fee.&nbsp; <br><br>
Anyone going to Taipei is pretty much going to have everything scheduled
prior to 24 hours before arrival (or maybe risk sleeping on the street or
10 miles away).&nbsp; The chance of being able to find someone to take
your reservation with less than 72 hours to go is pretty slim -
especially considering the other hotel in the block also requires 72 hour
notice to cancel.<br><br>
Later, Mike<br><br>
<br><br>
<blockquote type=cite class=cite cite="">Regards<br>
Marshall</blockquote></body>
<br>
</html>

--=====================_810431917==.ALT--


From sm@resistor.net  Mon Aug 22 21:24:04 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F6B321F8B2A for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 21:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.275
X-Spam-Level: 
X-Spam-Status: No, score=-102.275 tagged_above=-999 required=5 tests=[AWL=-0.276, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E8-ct-7Jma0d for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 21:24:03 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 780C121F8B00 for <ietf@ietf.org>; Mon, 22 Aug 2011 21:24:03 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7N4P49l022644 for <ietf@ietf.org>; Mon, 22 Aug 2011 21:25:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1314073508; bh=mxbF+ClwotF1pcWSuspsLD2pVoJynbRyermuaEIgk74=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=0jJCmz20JBznSOasikD5dGIMApEF6Nh3bVXPxwvw0eOIYopeFdZUixYBW7z+COQhU VMw0nhcKOquIC9Yvlqt4v3A7567QBYCbKIvKJByIgUy7/NTE3Wz4ecPbtmZb1hQ71V /8nJM2wL9toAe3oCxFcTRdyo6J0mqiqmMjzAkuQo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1314073508; bh=mxbF+ClwotF1pcWSuspsLD2pVoJynbRyermuaEIgk74=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=PdZzz7MccD7S5UCjxdq+qAatN+heZ2eQpc5Bn83DGWui26eXYPfelLgIhh44FS9Yd QeA+8pb477Wxonb1Z+fpGa7C4N002NJi9+SxAMdFXL9V/FRt53kuoLzLDINBY5I9Ah NFx9GH+enLeZ0AVte5uLlqHtDuMKxCXQ/W0c80Vo=
Message-Id: <6.2.5.6.2.20110822200837.09adf660@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 22 Aug 2011 21:23:00 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
In-Reply-To: <CA78256F.1D45A%c.donley@cablelabs.com>
References: <6.2.5.6.2.20110819111507.09a77b18@resistor.net> <CA78256F.1D45A%c.donley@cablelabs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 04:24:04 -0000

At 14:56 22-08-2011, Chris Donley wrote:
>This proposal reached ARIN consensus (2011-5), and has been recommended
>for adoption to the ARIN board. The ARIN BoD has indicated that it is
>willing to reserve a /10 if asked to do so by the IETF/IANA.
[snip]
>This will be supplied by IANA in consultation with ARIN.  ARIN has not
>pre-announced what block might be used, so we need to wait until IANA gets
>back to us later in the process.

The information could have been mentioned as a note in the draft.

>Not quite right. We first brought this proposal to OPSAWG in Maastricht,
>and then updated it for Beijing.  From the opsawg (79) minutes:
> > Straw poll: more people in the room supported the draft than didn't,
> > perhaps 2:1. About half the room expressed an opinion.
>
>Because IANA was down to its final /8, we were asked to also present in
>v6ops, which did not reach consensus for or against. Feedback from v6ops
>was to approach the RIRs for space, rather than IANA, which we did.

And a RIR sent this back to the IETF.

>How is this relevant? Jason, Victor, and I have been working on this for
>over a year.  Chris L and Marla joined the author team with significant
>contributions when we substantially updated the draft prior to IETF79.

That was an editorial nit.  Without the above explanation, it comes 
through as a case of corporate name-dropping.

Regards,
-sm 


From john-ietf@jck.com  Mon Aug 22 22:33:36 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C66AB21F8B00; Mon, 22 Aug 2011 22:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEgTp-by9ZVF; Mon, 22 Aug 2011 22:33:36 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 093A621F8AF8; Mon, 22 Aug 2011 22:33:35 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QvjdH-000A49-QT; Tue, 23 Aug 2011 01:34:40 -0400
Date: Tue, 23 Aug 2011 01:34:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ray Pelletier <rpelletier@isoc.org>, Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: Hyatt Taipei cancellation policy?
Message-ID: <66998320DD3FCC5628E32634@PST.JCK.COM>
In-Reply-To: <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 05:33:36 -0000

--On Monday, August 22, 2011 20:16 -0400 Ray Pelletier
<rpelletier@isoc.org> wrote:

>...
> As for the rates, they are high.  Taiwan is expensive,
> particularly given that the hotels know what our options are
> when we book the TICC.  The Hyatt knew that foreign visitors
> needed to use the Hyatt as headquarters and charged
> accordingly.  Since the time of our site visit, 2 new hotels
> have been constructed in the vicinity of the TICC (Le Meridien
> and W), which may provide more competition for Hyatt in these
> circumstances.  At the time we were working on this event,
> there were no acceptable options.

Ray,

I know you want to find sponsors and go where the sponsors want
to go.  I accept the explanation that you negotiated as hard as
you could for both room rates and cancellation policies.  But I
have to wonder, especially in the light of Lixia's observation
about the US Govt rate (which, internationally, is often a
pretty good measure for the higher end of a reasonable rate in a
given city), whether there is a stopping rule.  We were told in
Quebec that you had given up on one Southeast Asian city because
rooms would have cost over USD 300 a night. I don't remember
hearing about a sponsor there.  What looks like USD 275 net is
not all that much less than USD 300, especially if the dollar
continues to sink.

So, if you had a sponsor for a future meeting at that other
location, would an estimated USD 300 be acceptable?  USD 350?

I obviously don't have all of the information available to me
that you and the IAOC do, but it seems to be there is always
another alternative.   If there are no local ones, that
alternative is usually described as "just say no and go
elsewhere".  What I'm trying to understand, mostly for the
future and with the understanding that it is presumably much too
late for Taipei and the several following meetings, is whether
you would ever consider that an option for a meeting for which
you have a sponsor if you hold it in a particular place or if
you and the IAOC really believe there is no alternative under
those circumstances.

   john


   john



From lear@cisco.com  Mon Aug 22 22:39:45 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C826921F8B20; Mon, 22 Aug 2011 22:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.595
X-Spam-Level: 
X-Spam-Status: No, score=-110.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rOIXsCAp+buM; Mon, 22 Aug 2011 22:39:45 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id A5F4521F8B1D; Mon, 22 Aug 2011 22:39:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=759; q=dns/txt; s=iport; t=1314078052; x=1315287652; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=t5TlqFFgT6axKFbOr+kX5rQ/SDnaOU1kDrC+2MBN030=; b=e+tAm//MqY6MdKce9SzjhZ+qq2ghIQa8HDpbszzC0s5Csr948Tw5BLzy XfQODqKhJmYY7a8IbVZJrMbqvMWBCjqW6FB7XMzZ2BLWrmayM8yY+Rey4 z1LFi6HrUGwR3XPp1zjNXd8e4SmmdGC+Uxtd6878RFdoyB/9UOPYfEotH Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAKc8U06Q/khN/2dsb2JhbABBhEujV3eBQAEBAQEDEgEQVQEQCxgCAgUWCwICCQMCAQIBRQYNAQcBAR6eRAGNN5FygSyEDIEQBJMWkHs
X-IronPort-AV: E=Sophos;i="4.68,267,1312156800"; d="scan'208";a="111982409"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 23 Aug 2011 05:40:50 +0000
Received: from ams3-vpn-dhcp5566.cisco.com (ams3-vpn-dhcp5566.cisco.com [10.61.85.189]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7N5eoqG006837; Tue, 23 Aug 2011 05:40:50 GMT
Message-ID: <4E533D39.5070606@cisco.com>
Date: Tue, 23 Aug 2011 07:40:09 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: IETF Chair <chair@ietf.org>
Subject: Re: Experiment for different schedule for Friday
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
In-Reply-To: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 05:39:45 -0000

On 8/22/11 11:24 PM, IETF Chair wrote:
> The IESG is considering a different schedule for the Friday of IETF 82.  The IESG is seeking your input on these potential changes.
>
> The IESG would like to try a schedule experiment on Friday, using this schedule:
>
>  9:00 AM - 11:00 AM - Session I
> 11:00 AM - 11:20 AM - Room Change and Cookie Break
> 11:20 AM - 12:20 PM - Session II
> 12:10 PM - 12:30 PM - Room Change Break
> 12:30 PM - 13:30 PM - Session III
>
> The IESG has already consulted with the IAOC because of the cost associated with the additional food and beverage break.  The IAOC believes that the additional cost can be managed without raising the meeting fee.

I think this is a good experiment to run as proposed.

Eliot

From john-ietf@jck.com  Mon Aug 22 23:03:56 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C01A421F881C; Mon, 22 Aug 2011 23:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id raGpgui70T1p; Mon, 22 Aug 2011 23:03:54 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id B841C21F8ADC; Mon, 22 Aug 2011 23:03:54 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qvk6b-000AUo-1V; Tue, 23 Aug 2011 02:04:57 -0400
Date: Tue, 23 Aug 2011 02:04:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, IETF Chair <chair@ietf.org>
Subject: Re: Experiment for different schedule for Friday
Message-ID: <DC351D99C7573A54509F777F@PST.JCK.COM>
In-Reply-To: <4E533D39.5070606@cisco.com>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <4E533D39.5070606@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
Cc: IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 06:03:56 -0000

+1.  I could also happily live with the alternate, more
compressed, schedule -- I think both are preferable to the
schedule used in Quebec and earlier.

   john


--On Tuesday, August 23, 2011 07:40 +0200 Eliot Lear
<lear@cisco.com> wrote:

> 
> 
> On 8/22/11 11:24 PM, IETF Chair wrote:
>> The IESG is considering a different schedule for the Friday
>> of IETF 82.  The IESG is seeking your input on these
>> potential changes.
>> 
>> The IESG would like to try a schedule experiment on Friday,
>> using this schedule:
>> 
>>  9:00 AM - 11:00 AM - Session I
>> 11:00 AM - 11:20 AM - Room Change and Cookie Break
>> 11:20 AM - 12:20 PM - Session II
>> 12:10 PM - 12:30 PM - Room Change Break
>> 12:30 PM - 13:30 PM - Session III
>> 
>> The IESG has already consulted with the IAOC because of the
>> cost associated with the additional food and beverage break.
>> The IAOC believes that the additional cost can be managed
>> without raising the meeting fee.
> 
> I think this is a good experiment to run as proposed.





From peter@denic.de  Mon Aug 22 23:31:36 2011
Return-Path: <peter@denic.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A45021F8B39 for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 23:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnZS5uHX9SpZ for <ietf@ietfa.amsl.com>; Mon, 22 Aug 2011 23:31:36 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::4]) by ietfa.amsl.com (Postfix) with ESMTP id CA78E21F8B31 for <ietf@ietf.org>; Mon, 22 Aug 2011 23:31:35 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp  id 1QvkXR-0003cx-Q9; Tue, 23 Aug 2011 08:32:41 +0200
Received: from localhost by x27.adm.denic.de with local  id 1QvkXR-00008N-MV; Tue, 23 Aug 2011 08:32:41 +0200
Date: Tue, 23 Aug 2011 08:32:41 +0200
From: Peter Koch <pk@ISOC.DE>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
Message-ID: <20110823063241.GR25053@x27.adm.denic.de>
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 06:31:36 -0000

>              IPv6 Support Required for all IP-capable nodes
>                   draft-ietf-intarea-ipv6-required-01

The document strives to convey the message that "IP" is no longer
equivalent to "IPv4", which is a goal that I'd fully support.
However, while this is a political statement that the IETF really should
make, i have a large amount of scepticism that the document, as
it is written, can successfully convey the message to the desired
target audience.

For one, i share the concerns raised by others that "updating" various
old RFCs is not the right way to go.  First, the documents technically
are not in need of an update (e.g., because RFC 1812 pretty clearly
states that it deals with v4 routers only). Second, changing sentences
or phrases in existing documents, although not without precedent, isn't
best IETF style. This is especially dubious w.r.t. RFC 4084, BCP 104.

Most importantly, though, the updates to existing documents are so
sophisticated and so highly likely to be overread that I'd not see
anybody who managed to remain unaware until today to now follow suit.
It feels a bit like giving purchase departments, or maybe even
legal departments a lever to defeat claims that a product is "IP capable"
when it indeed is IPv4 only.

In that context, these two statements

>       New IP implementations MUST support IPv6.
>
>       Current IP implementations SHOULD support IPv6.

appear especially interesting. What divides implementations into "new"
and "current" and what's the purpose of stating requirements for
"current" implementations, assuming an intuitive meaning of the word?

I'd agree the IETF (and other I* bodies) have a point in making
strong statements about IPv6 adoption, but the IETF has traditionally
abstained from addressing individual false claims of "RFC compliance".
To that extent i do not see how this would be different for the draft
in Last Call.  For the really agnostic, it also isn't too helpful
since RFCs 1812 and 1122 are of lesser concern.  Documents like RIPE-501,
although not ideal, provide much better guidance.

In summary, if the core message is "IP != IPv4" then i believe the
text isn't crisp enough; if it were bullets for legal/purchase, i do not
see the point.

-Peter

From shane@isc.org  Tue Aug 23 03:07:31 2011
Return-Path: <shane@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 844BA21F8751; Tue, 23 Aug 2011 03:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I-DtAbsWzc4V; Tue, 23 Aug 2011 03:07:31 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id ED22F21F8772; Tue, 23 Aug 2011 03:07:30 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 141A55F98BF; Tue, 23 Aug 2011 10:08:28 +0000 (UTC) (envelope-from shane@isc.org)
Received: from [IPv6:2001:610:719:1:beae:c5ff:fe43:aa00] (unknown [IPv6:2001:610:719:1:beae:c5ff:fe43:aa00]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 3B2B8216C22; Tue, 23 Aug 2011 10:08:26 +0000 (UTC) (envelope-from shane@isc.org)
Subject: Agenda known in advance? was Re: Experiment for different schedule for Friday
From: Shane Kerr <shane@isc.org>
To: IETF Chair <chair@ietf.org>
Date: Tue, 23 Aug 2011 12:08:22 +0200
In-Reply-To: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org>
Organization: ISC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.0.2 (3.0.2-3.fc15) 
Content-Transfer-Encoding: 7bit
Message-ID: <1314094107.1965.16.camel@shane-desktop>
Mime-Version: 1.0
Cc: IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 10:07:31 -0000

Russ,

On Mon, 2011-08-22 at 17:24 -0400, IETF Chair wrote:
> The IESG is considering a different schedule for the Friday of IETF 82.
>   The IESG is seeking your input on these potential changes.
> 
> The IESG would like to try a schedule experiment on Friday, using this
> schedule:

In principle this makes sense, but do people think that the IETF meeting
agenda will remain unknown and unknowable until the very last minute? As
we see in the Tao of the IETF:

        ... the agenda is fluid, and there have been many instances of
        participants missing important sessions due to last-minute
        scheduling changes after their travel plans were fixed. Being
        present the whole week is the only way to avoid this annoyance. 

This has happened to me in the past... more than an "annoyance" since
there were three working groups I really wanted to join in the physical
meeting and I missed one. A transcontinental flight, hotel stays, and
time away from the "day job" are a heavy price that is more than
"annoying" when you miss 1/3 of the meetings.

If the idea of not fixing agendas is to remain, then any experiments for
extending the Friday schedule pretty much mean that everyone has to
extend their stay, doesn't it? I think if we want to use Friday time
properly, then this ideology needs to go.

Or maybe it already has and I misunderstand things!

Thanks,

--
Shane


From glenzorn@gmail.com  Tue Aug 23 03:13:04 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D59F21F8AE9; Tue, 23 Aug 2011 03:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rg3ZMpLnrTeU; Tue, 23 Aug 2011 03:13:03 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6AE1C21F8AA8; Tue, 23 Aug 2011 03:13:03 -0700 (PDT)
Received: by gxk19 with SMTP id 19so5138217gxk.31 for <multiple recipients>; Tue, 23 Aug 2011 03:14:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=C0wk9Ci/38Z8O58BjgM685aesfJ3FR5zjP0CPKU/xd0=; b=Q9rJmZoWCTla+/S6mvrhrEzRia7rLze6saQGDYmhhO9uSSmS4aX+1/B/pQOEl142pw G/MDvTlJyNSVDekrPjYTgtuzkqaG1pOY1wbOCm1J6Sxs3F00aC/eF6SZCGbpVB6NOi8o Qf1wwYEotPq2K/s1/qO3k3q1os2v5eZu3uoU0=
Received: by 10.101.133.22 with SMTP id k22mr3388039ann.90.1314094450721; Tue, 23 Aug 2011 03:14:10 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-122-183-227.revip2.asianet.co.th [124.122.183.227]) by mx.google.com with ESMTPS id o8sm8397anm.33.2011.08.23.03.14.07 (version=SSLv3 cipher=OTHER); Tue, 23 Aug 2011 03:14:10 -0700 (PDT)
Message-ID: <4E537D6C.3020002@gmail.com>
Date: Tue, 23 Aug 2011 17:14:04 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Shane Kerr <shane@isc.org>
Subject: Re: Agenda known in advance? was Re: Experiment for different schedule for Friday
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <1314094107.1965.16.camel@shane-desktop>
In-Reply-To: <1314094107.1965.16.camel@shane-desktop>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 10:13:04 -0000

On 8/23/2011 5:08 PM, Shane Kerr wrote:
> Russ,
> 
> On Mon, 2011-08-22 at 17:24 -0400, IETF Chair wrote:
>> The IESG is considering a different schedule for the Friday of IETF 82.
>>   The IESG is seeking your input on these potential changes.
>>
>> The IESG would like to try a schedule experiment on Friday, using this
>> schedule:
> 
> In principle this makes sense, but do people think that the IETF meeting
> agenda will remain unknown and unknowable until the very last minute? As
> we see in the Tao of the IETF:
> 
>         ... the agenda is fluid, and there have been many instances of
>         participants missing important sessions due to last-minute
>         scheduling changes after their travel plans were fixed. Being
>         present the whole week is the only way to avoid this annoyance. 
> 
> This has happened to me in the past... more than an "annoyance" since
> there were three working groups I really wanted to join in the physical
> meeting and I missed one. A transcontinental flight, hotel stays, and
> time away from the "day job" are a heavy price that is more than
> "annoying" when you miss 1/3 of the meetings.
> 
> If the idea of not fixing agendas is to remain, then any experiments for
> extending the Friday schedule pretty much mean that everyone has to
> extend their stay, doesn't it? I think if we want to use Friday time
> properly, then this ideology needs to go.

Either that or the idea that Friday is an "off day" has to go.  Oh,
wait, it has, a couple of years ago.  Slow learner or just in denial?

> 
> Or maybe it already has and I misunderstand things!
> 
> Thanks,
> 
> --
> Shane
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From jaap@bartok.nlnetlabs.nl  Tue Aug 23 03:24:36 2011
Return-Path: <jaap@bartok.nlnetlabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD6BE21F8AFE; Tue, 23 Aug 2011 03:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.969
X-Spam-Level: 
X-Spam-Status: No, score=-2.969 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kp3ekNq-od49; Tue, 23 Aug 2011 03:24:36 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by ietfa.amsl.com (Postfix) with ESMTP id C168721F8AE4; Tue, 23 Aug 2011 03:24:33 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.5/8.14.5) with ESMTP id p7NAPchW047526; Tue, 23 Aug 2011 12:25:38 +0200 (CEST) (envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <201108231025.p7NAPchW047526@bartok.nlnetlabs.nl>
To: Shane Kerr <shane@isc.org>
Subject: Re: Agenda known in advance? was Re: Experiment for different schedule for Friday
In-reply-to: <1314094107.1965.16.camel@shane-desktop>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <1314094107.1965.16.camel@shane-desktop>
Comments: In-reply-to Shane Kerr <shane@isc.org> message dated "Tue, 23 Aug 2011 12:08:22 +0200."
Date: Tue, 23 Aug 2011 12:25:38 +0200
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (bartok.nlnetlabs.nl [127.0.0.1]); Tue, 23 Aug 2011 12:25:38 +0200 (CEST)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 10:24:37 -0000

    
    If the idea of not fixing agendas is to remain, then any experiments for
    extending the Friday schedule pretty much mean that everyone has to
    extend their stay, doesn't it? I think if we want to use Friday time
    properly, then this ideology needs to go.
    
Fully agree. We should consider Friday (morning) as yet another
normal (.5) IETF day or not. 

	jaap


From shane@isc.org  Tue Aug 23 04:32:24 2011
Return-Path: <shane@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6406E21F85B8; Tue, 23 Aug 2011 04:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZe3AZEyqq1u; Tue, 23 Aug 2011 04:32:24 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id D9CE121F85B5; Tue, 23 Aug 2011 04:32:23 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 262C95F984C; Tue, 23 Aug 2011 11:33:25 +0000 (UTC) (envelope-from shane@isc.org)
Received: from [IPv6:2001:610:719:1:beae:c5ff:fe43:aa00] (unknown [IPv6:2001:610:719:1:beae:c5ff:fe43:aa00]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 566FE216C22; Tue, 23 Aug 2011 11:33:22 +0000 (UTC) (envelope-from shane@isc.org)
Subject: Re: Agenda known in advance? was Re: Experiment for different schedule for Friday
From: Shane Kerr <shane@isc.org>
To: Glen Zorn <glenzorn@gmail.com>
Date: Tue, 23 Aug 2011 13:33:19 +0200
In-Reply-To: <4E537D6C.3020002@gmail.com>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <1314094107.1965.16.camel@shane-desktop> <4E537D6C.3020002@gmail.com>
Organization: ISC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.0.2 (3.0.2-3.fc15) 
Content-Transfer-Encoding: 7bit
Message-ID: <1314099203.1965.42.camel@shane-desktop>
Mime-Version: 1.0
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 11:32:24 -0000

Glen,

On Tue, 2011-08-23 at 17:14 +0700, Glen Zorn wrote:
> > 
> > If the idea of not fixing agendas is to remain, then any experiments for
> > extending the Friday schedule pretty much mean that everyone has to
> > extend their stay, doesn't it? I think if we want to use Friday time
> > properly, then this ideology needs to go.
> 
> Either that or the idea that Friday is an "off day" has to go.  Oh,
> wait, it has, a couple of years ago.  

I don't believe I mentioned anywhere that Friday is considered an "off
day". I did not even say that the working group session that I missed
was on a Friday.

What I think is we would get a better use of time by making an agenda
and sticking to it. I think that would make it easier on everyone
attending. I also think that without this, Friday slots will always be
ghetto.

> Slow learner or just in denial?

That's pretty rude. It makes me sad that this kind of mail is "okay" at
the IETF. :(

--
Shane


From tnadeau@lucidvision.com  Tue Aug 23 04:55:29 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4070B21F8AE9; Tue, 23 Aug 2011 04:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.865
X-Spam-Level: 
X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=-0.662, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9fVvzu200of; Tue, 23 Aug 2011 04:55:28 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 9652721F8B1F; Tue, 23 Aug 2011 04:55:28 -0700 (PDT)
Received: from [192.168.1.102] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 2FDB91D9BDC7; Tue, 23 Aug 2011 07:56:35 -0400 (EDT)
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM>
In-Reply-To: <66998320DD3FCC5628E32634@PST.JCK.COM>
Mime-Version: 1.0 (iPad Mail 8L1)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com>
X-Mailer: iPad Mail (8L1)
From: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Hyatt Taipei cancellation policy?
Date: Tue, 23 Aug 2011 07:57:12 -0400
To: John C Klensin <john-ietf@jck.com>
Cc: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 11:55:29 -0000

On Aug 23, 2011, at 1:34 AM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Monday, August 22, 2011 20:16 -0400 Ray Pelletier
> <rpelletier@isoc.org> wrote:
>=20
>> ...
>> As for the rates, they are high.  Taiwan is expensive,
>> particularly given that the hotels know what our options are
>> when we book the TICC.  The Hyatt knew that foreign visitors
>> needed to use the Hyatt as headquarters and charged
>> accordingly.  Since the time of our site visit, 2 new hotels
>> have been constructed in the vicinity of the TICC (Le Meridien
>> and W), which may provide more competition for Hyatt in these
>> circumstances.  At the time we were working on this event,
>> there were no acceptable options.
>=20
> Ray,
>=20
> I know you want to find sponsors and go where the sponsors want
> to go.  I accept the explanation that you negotiated as hard as
> you could for both room rates and cancellation policies.  But I
> have to wonder, especially in the light of Lixia's observation
> about the US Govt rate (which, internationally, is often a
> pretty good measure for the higher end of a reasonable rate in a
> given city), whether there is a stopping rule.  We were told in
> Quebec that you had given up on one Southeast Asian city because
> rooms would have cost over USD 300 a night. I don't remember
> hearing about a sponsor there.  What looks like USD 275 net is
> not all that much less than USD 300, especially if the dollar
> continues to sink.
>=20
> So, if you had a sponsor for a future meeting at that other
> location, would an estimated USD 300 be acceptable?  USD 350?
>=20
> I obviously don't have all of the information available to me
> that you and the IAOC do, but it seems to be there is always
> another alternative.   If there are no local ones, that
> alternative is usually described as "just say no and go
> elsewhere".  What I'm trying to understand, mostly for the
> future and with the understanding that it is presumably much too
> late for Taipei and the several following meetings, is whether
> you would ever consider that an option for a meeting for which
> you have a sponsor if you hold it in a particular place or if
> you and the IAOC really believe there is no alternative under
> those circumstances.

I think we need to adopt a simple rule of thumb whereby we do not book venue=
s where room rates of less than $200 USD are unavailable - sponsor or otherw=
ise.

Tom


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

From tjc@ecs.soton.ac.uk  Tue Aug 23 05:21:04 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC08D21F8507; Tue, 23 Aug 2011 05:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.882
X-Spam-Level: 
X-Spam-Status: No, score=-2.882 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wkq66xCDzShB; Tue, 23 Aug 2011 05:21:03 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 121D321F85F1; Tue, 23 Aug 2011 05:21:02 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7NCM7u7017450;  Tue, 23 Aug 2011 13:22:07 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p7NCM7u7017450
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1314102127; bh=ycIih0xDP0pwmPWP3Wq2Mw8Z/hw=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=Dfraj0GXPRuFk+RRt36+LUHFrkUjo+yHrXmxsg/GqYl4aE94Y22t/c4Rw6R1vkAd+ W5k9+EufW1OADDBVib8SN3BRy7bMlpFa5/K044pZu/gY4WkYsU1jaMwu2y2wLAftHl jlrFJxcjlssZtGJSDQRZ0cKxFDBw/3uryi42s3s8=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n7MDM70366103684Ll ret-id none; Tue, 23 Aug 2011 13:22:07 +0100
Received: from [IPv6:2001:630:d0:f105:84ff:decf:39bf:7fdf] ([IPv6:2001:630:d0:f105:84ff:decf:39bf:7fdf]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7NCM1rP016795 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Aug 2011 13:22:05 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: Hyatt Taipei cancellation policy?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com>
Date: Tue, 23 Aug 2011 13:22:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|7cfc1b2fdbfdeb14e66236f0d6d9d15cn7MDM703tjc|ecs.soton.ac.uk|61121E5C-1B61-4271-B602-84FC30720352@ecs.soton.ac.uk>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <61121E5C-1B61-4271-B602-84FC30720352@ecs.soton.ac.uk>
To: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n7MDM7036610368400; tid=n7MDM70366103684Ll; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p7NCM7u7017450
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 12:21:04 -0000

The room rate I see is 8500 TWD, which is $293 a night.   That is a =
Grand King room, for 2 people.

If you don't put G-23ET in the corporate/group box, it gets much worse!  =
I'm guessing the web link on the IETF site should read =
http://taipei.grand.hyatt.com/hyatt/hotels/index.jsp?extCorporateId=3DG-23=
ET to simplify that?=20

On the plus side, flying out from Europe the time zones mean I don't =
need to stay Saturday night, so that actually puts the total hotel cost =
down, since the stay is 5 nights not the usual 6 (remembering that you =
need to fly in/out including a Saturday night for the cheaper flight).

Tim

On 23 Aug 2011, at 12:57, Thomas Nadeau wrote:

>=20
>=20
>=20
>=20
> On Aug 23, 2011, at 1:34 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
>>=20
>>=20
>> --On Monday, August 22, 2011 20:16 -0400 Ray Pelletier
>> <rpelletier@isoc.org> wrote:
>>=20
>>> ...
>>> As for the rates, they are high.  Taiwan is expensive,
>>> particularly given that the hotels know what our options are
>>> when we book the TICC.  The Hyatt knew that foreign visitors
>>> needed to use the Hyatt as headquarters and charged
>>> accordingly.  Since the time of our site visit, 2 new hotels
>>> have been constructed in the vicinity of the TICC (Le Meridien
>>> and W), which may provide more competition for Hyatt in these
>>> circumstances.  At the time we were working on this event,
>>> there were no acceptable options.
>>=20
>> Ray,
>>=20
>> I know you want to find sponsors and go where the sponsors want
>> to go.  I accept the explanation that you negotiated as hard as
>> you could for both room rates and cancellation policies.  But I
>> have to wonder, especially in the light of Lixia's observation
>> about the US Govt rate (which, internationally, is often a
>> pretty good measure for the higher end of a reasonable rate in a
>> given city), whether there is a stopping rule.  We were told in
>> Quebec that you had given up on one Southeast Asian city because
>> rooms would have cost over USD 300 a night. I don't remember
>> hearing about a sponsor there.  What looks like USD 275 net is
>> not all that much less than USD 300, especially if the dollar
>> continues to sink.
>>=20
>> So, if you had a sponsor for a future meeting at that other
>> location, would an estimated USD 300 be acceptable?  USD 350?
>>=20
>> I obviously don't have all of the information available to me
>> that you and the IAOC do, but it seems to be there is always
>> another alternative.   If there are no local ones, that
>> alternative is usually described as "just say no and go
>> elsewhere".  What I'm trying to understand, mostly for the
>> future and with the understanding that it is presumably much too
>> late for Taipei and the several following meetings, is whether
>> you would ever consider that an option for a meeting for which
>> you have a sponsor if you hold it in a particular place or if
>> you and the IAOC really believe there is no alternative under
>> those circumstances.
>=20
> I think we need to adopt a simple rule of thumb whereby we do not book =
venues where room rates of less than $200 USD are unavailable - sponsor =
or otherwise.
>=20
> Tom
>=20
>=20
>>=20
>>  john
>>=20
>>=20
>>  john
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From tjc@ecs.soton.ac.uk  Tue Aug 23 05:29:42 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8678521F8797; Tue, 23 Aug 2011 05:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.773
X-Spam-Level: 
X-Spam-Status: No, score=-2.773 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pMl+PgOTBGz2; Tue, 23 Aug 2011 05:29:41 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id E1B9A21F86B1; Tue, 23 Aug 2011 05:29:40 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7NCUif4019511; Tue, 23 Aug 2011 13:30:44 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p7NCUif4019511
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1314102644; bh=xf5s9DcMgxXaTuFBdig86ZkMR0M=; h=From:Mime-Version:Subject:Date:In-Reply-To:To:References; b=E/9XKLItBacUkEmx3YSZt7rI+HSSR5VAMgxXoodJXxLkGpjA1WhInyZTg++L3ReXb XFbA9ZBjNX5qBgcmhNFamk8Q7LRKADAv4005es7+qwDrzjVKrN76UpWANjnn/MjOX7 pzKQb5EGx99HI/ig3R4EiUQpGI2LeUeRnKa7CoM4=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n7MDUi0366103757Up ret-id none; Tue, 23 Aug 2011 13:30:44 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7NCUg23019052 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Aug 2011 13:30:42 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1A1D4986-9BCF-4D5C-9378-B096BFF38D08"
Subject: Re: Hyatt Taipei cancellation policy?
Date: Tue, 23 Aug 2011 13:30:41 +0100
In-Reply-To: <EMEW3|7cfc1b2fdbfdeb14e66236f0d6d9d15cn7MDM703tjc|ecs.soton.ac.uk|61121E5C-1B61-4271-B602-84FC30720352@ecs.soton.ac.uk>
To: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <61121E5C-1B61-4271-B602-84FC30720352@ecs.soton.ac.uk> <EMEW3|7cfc1b2fdbfdeb14e66236f0d6d9d15cn7MDM703tjc|ecs.soton.ac.uk|61121E5C-1B61-4271-B602-84FC30720352@ecs.soton.ac.uk> <233F21E3-5569-4B3D-863F-2E6DCDA21D46@ecs.soton.ac.uk>
Message-ID: <EMEW3|b4aeb1d8757db9c020d6c7c2a80cb072n7MDUi03tjc|ecs.soton.ac.uk|233F21E3-5569-4B3D-863F-2E6DCDA21D46@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n7MDUi036610375700; tid=n7MDUi0366103757Up; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p7NCUif4019511
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 12:29:42 -0000

--Apple-Mail=_1A1D4986-9BCF-4D5C-9378-B096BFF38D08
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Oh, and *after* you book, it says

Additional Charges=09
10.000 Percent service charge

So the charge is 10% higher than what's displayed. It would be nice if =
the full charge was more up front.  People checking for budget in =
advance may be unaware of this.

Tim

On 23 Aug 2011, at 13:22, Tim Chown wrote:

> The room rate I see is 8500 TWD, which is $293 a night.   That is a =
Grand King room, for 2 people.
>=20
> If you don't put G-23ET in the corporate/group box, it gets much =
worse!  I'm guessing the web link on the IETF site should read =
http://taipei.grand.hyatt.com/hyatt/hotels/index.jsp?extCorporateId=3DG-23=
ET to simplify that?=20
>=20
> On the plus side, flying out from Europe the time zones mean I don't =
need to stay Saturday night, so that actually puts the total hotel cost =
down, since the stay is 5 nights not the usual 6 (remembering that you =
need to fly in/out including a Saturday night for the cheaper flight).
>=20
> Tim
>=20
> On 23 Aug 2011, at 12:57, Thomas Nadeau wrote:
>=20
>>=20
>>=20
>>=20
>>=20
>> On Aug 23, 2011, at 1:34 AM, John C Klensin <john-ietf@jck.com> =
wrote:
>>=20
>>>=20
>>>=20
>>> --On Monday, August 22, 2011 20:16 -0400 Ray Pelletier
>>> <rpelletier@isoc.org> wrote:
>>>=20
>>>> ...
>>>> As for the rates, they are high.  Taiwan is expensive,
>>>> particularly given that the hotels know what our options are
>>>> when we book the TICC.  The Hyatt knew that foreign visitors
>>>> needed to use the Hyatt as headquarters and charged
>>>> accordingly.  Since the time of our site visit, 2 new hotels
>>>> have been constructed in the vicinity of the TICC (Le Meridien
>>>> and W), which may provide more competition for Hyatt in these
>>>> circumstances.  At the time we were working on this event,
>>>> there were no acceptable options.
>>>=20
>>> Ray,
>>>=20
>>> I know you want to find sponsors and go where the sponsors want
>>> to go.  I accept the explanation that you negotiated as hard as
>>> you could for both room rates and cancellation policies.  But I
>>> have to wonder, especially in the light of Lixia's observation
>>> about the US Govt rate (which, internationally, is often a
>>> pretty good measure for the higher end of a reasonable rate in a
>>> given city), whether there is a stopping rule.  We were told in
>>> Quebec that you had given up on one Southeast Asian city because
>>> rooms would have cost over USD 300 a night. I don't remember
>>> hearing about a sponsor there.  What looks like USD 275 net is
>>> not all that much less than USD 300, especially if the dollar
>>> continues to sink.
>>>=20
>>> So, if you had a sponsor for a future meeting at that other
>>> location, would an estimated USD 300 be acceptable?  USD 350?
>>>=20
>>> I obviously don't have all of the information available to me
>>> that you and the IAOC do, but it seems to be there is always
>>> another alternative.   If there are no local ones, that
>>> alternative is usually described as "just say no and go
>>> elsewhere".  What I'm trying to understand, mostly for the
>>> future and with the understanding that it is presumably much too
>>> late for Taipei and the several following meetings, is whether
>>> you would ever consider that an option for a meeting for which
>>> you have a sponsor if you hold it in a particular place or if
>>> you and the IAOC really believe there is no alternative under
>>> those circumstances.
>>=20
>> I think we need to adopt a simple rule of thumb whereby we do not =
book venues where room rates of less than $200 USD are unavailable - =
sponsor or otherwise.
>>=20
>> Tom
>>=20
>>=20
>>>=20
>>> john
>>>=20
>>>=20
>>> john
>>>=20
>>>=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
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail=_1A1D4986-9BCF-4D5C-9378-B096BFF38D08
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; ">Oh, =
and *after* you book, it says<div><br><span class=3D"Apple-style-span" =
style=3D"color: rgb(51, 51, 51); font-family: arial; font-size: 12px; =
"><table class=3D"gi_AdvancedPurchaseRate_Summ_table " width=3D"360" =
style=3D"font-size: 12px; position: static; z-index: auto; =
"><tbody><tr><td valign=3D"top" style=3D"padding-top: 0px; =
padding-right: 0px; padding-bottom: 0px; padding-left: 0px; =
vertical-align: top; font-size: 12px; font-family: arial; ">Additional =
Charges</td><td style=3D"padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; vertical-align: top; font-size: =
12px; font-family: arial; "><div style=3D"font-family: arial; font-size: =
12px; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">10.000 Percent service =
charge</div></td></tr></tbody></table><br>So the charge is 10% higher =
than what's displayed. It would be nice if the full charge was more up =
front. &nbsp;People checking for budget in advance may be unaware of =
this.</span></div><div><font class=3D"Apple-style-span" color=3D"#333333" =
face=3D"arial"><br></font></div><div><span class=3D"Apple-style-span" =
style=3D"color: rgb(51, 51, 51); font-family: arial; font-size: 12px; =
">Tim</span></div><div><span class=3D"Apple-style-span" style=3D"color: =
rgb(51, 51, 51); font-family: arial; font-size: 12px; =
"><br></span></div><div><div><div>On 23 Aug 2011, at 13:22, Tim Chown =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>The room rate I see is 8500 TWD, which is $293 a =
night. &nbsp;&nbsp;That is a Grand King room, for 2 people.<br><br>If =
you don't put G-23ET in the corporate/group box, it gets much worse! =
&nbsp;I'm guessing the web link on the IETF site should read <a =
href=3D"http://taipei.grand.hyatt.com/hyatt/hotels/index.jsp?extCorporateI=
d=3DG-23ET">http://taipei.grand.hyatt.com/hyatt/hotels/index.jsp?extCorpor=
ateId=3DG-23ET</a> to simplify that? <br><br>On the plus side, flying =
out from Europe the time zones mean I don't need to stay Saturday night, =
so that actually puts the total hotel cost down, since the stay is 5 =
nights not the usual 6 (remembering that you need to fly in/out =
including a Saturday night for the cheaper flight).<br><br>Tim<br><br>On =
23 Aug 2011, at 12:57, Thomas Nadeau wrote:<br><br><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">On Aug 23, =
2011, at 1:34 AM, John C Klensin &lt;<a =
href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt; =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></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">--On Monday, August 22, 2011 =
20:16 -0400 Ray Pelletier<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">&lt;<a =
href=3D"mailto:rpelletier@isoc.org">rpelletier@isoc.org</a>&gt; =
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">...<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">As for =
the rates, they are high. &nbsp;Taiwan is =
expensive,<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">particularly given that the hotels know what our options =
are<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">when =
we book the TICC. &nbsp;The Hyatt knew that foreign =
visitors<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">needed =
to use the Hyatt as headquarters and =
charged<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">accordingly. &nbsp;Since the time of our site visit, 2 new =
hotels<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">have =
been constructed in the vicinity of the TICC (Le =
Meridien<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">and =
W), which may provide more competition for Hyatt in =
these<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">circumstances. &nbsp;At the time we were working on this =
event,<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">there =
were no acceptable =
options.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">Ray,<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I know you want to find sponsors =
and go where the sponsors want<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">to go. &nbsp;I accept the =
explanation that you negotiated as hard =
as<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">you could for both room rates and cancellation policies. =
&nbsp;But I<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">have to wonder, especially in =
the light of Lixia's =
observation<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">about the US Govt rate (which, =
internationally, is often a<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">pretty good measure for the =
higher end of a reasonable rate in =
a<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">given city), whether there is a stopping rule. &nbsp;We =
were told in<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Quebec that you had given up on =
one Southeast Asian city =
because<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">rooms would have cost over USD 300 a night. I don't =
remember<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">hearing about a sponsor there. =
&nbsp;What looks like USD 275 net =
is<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">not all that much less than USD 300, especially if the =
dollar<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">continues to =
sink.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">So, if you had a sponsor for a =
future meeting at that other<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">location, would an estimated USD =
300 be acceptable? &nbsp;USD =
350?<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I obviously don't have all of =
the information available to me<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">that you and the IAOC do, but it =
seems to be there is always<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">another alternative. =
&nbsp;&nbsp;If there are no local ones, =
that<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">alternative is usually described as "just say no and =
go<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">elsewhere". &nbsp;What I'm trying to understand, mostly =
for the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">future and with the understanding that it is presumably =
much too<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">late for Taipei and the several =
following meetings, is whether<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">you would ever consider that an =
option for a meeting for which<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">you have a sponsor if you hold =
it in a particular place or if<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">you and the IAOC really believe =
there is no alternative under<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">those =
circumstances.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I think we need =
to adopt a simple rule of thumb whereby we do not book venues where room =
rates of less than $200 USD are unavailable - sponsor or =
otherwise.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Tom<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"> =
john<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"> =
john<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">_______________________________________________<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></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>_____________________________=
__________________<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></div></body></html>=

--Apple-Mail=_1A1D4986-9BCF-4D5C-9378-B096BFF38D08--

From dworley@avaya.com  Tue Aug 23 06:44:16 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE2721F8ACA; Tue, 23 Aug 2011 06:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.953
X-Spam-Level: 
X-Spam-Status: No, score=-102.953 tagged_above=-999 required=5 tests=[AWL=-0.354, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n5bGYjz9bo4r; Tue, 23 Aug 2011 06:44:16 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id CFEF521F8AC3; Tue, 23 Aug 2011 06:44:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAEKuU06HCzI1/2dsb2JhbABBqBx3gUABAQEBAgESKD8FCwIBCA0IIRAyJQEBBAENDRqHT54OApxKhWlfBJhEi2s
X-IronPort-AV: E=Sophos;i="4.68,269,1312171200"; d="scan'208";a="203621618"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 23 Aug 2011 09:45:23 -0400
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; 23 Aug 2011 09:36:56 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 23 Aug 2011 09:45:22 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Michael StJohns <mstjohns@comcast.net>, Ray Pelletier <rpelletier@isoc.org>
Date: Tue, 23 Aug 2011 09:43:11 -0400
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: AcxhO28KQw7DApa8S2CMsjbXFmokFwAXyme/
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com>
In-Reply-To: <20110823022038.EC4DE21F87D9@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf-secretariat@ietf.org" <ietf-secretariat@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 13:44:16 -0000

> From: Michael StJohns
>=20
> Could you refresh my memory as to which hotels we stayed at had this
> policy?  I literally cannot remember having any hotel cancellation
> policy with more than a single night fee ever.

Maastricht had particularly fierce cancellation rules.  I don't
remember the details, but under some circumstances you could have to
pay for the entire stay.

Dale

From chair@ietf.org  Tue Aug 23 06:47:36 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4BF321F8B32; Tue, 23 Aug 2011 06:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ScBCrned5hf4; Tue, 23 Aug 2011 06:47:36 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 7C41921F8B2F; Tue, 23 Aug 2011 06:47:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id D7CD11C3813F; Tue, 23 Aug 2011 06:48:39 -0700 (PDT)
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 MpLNcV0NLu-l; Tue, 23 Aug 2011 06:48:39 -0700 (PDT)
Received: from 222.22.242.10.in-addr.arpa (m3b2336d0.tmodns.net [208.54.35.59]) by c1a.amsl.com (Postfix) with ESMTPSA id 4481F1C38132; Tue, 23 Aug 2011 06:48:39 -0700 (PDT)
Subject: Re: Agenda known in advance? was Re: Experiment for different schedule for Friday
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <1314094107.1965.16.camel@shane-desktop>
Date: Tue, 23 Aug 2011 09:48:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B58B51A-FDD0-40DC-8F29-AAEAEDC4E202@ietf.org>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <1314094107.1965.16.camel@shane-desktop>
To: Shane Kerr <shane@isc.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 13:47:37 -0000

Shane:

>> The IESG is considering a different schedule for the Friday of IETF =
82.
>>  The IESG is seeking your input on these potential changes.
>>=20
>> The IESG would like to try a schedule experiment on Friday, using =
this
>> schedule:
>=20
> In principle this makes sense, but do people think that the IETF =
meeting
> agenda will remain unknown and unknowable until the very last minute? =
As
> we see in the Tao of the IETF:
>=20
>        ... the agenda is fluid, and there have been many instances of
>        participants missing important sessions due to last-minute
>        scheduling changes after their travel plans were fixed. Being
>        present the whole week is the only way to avoid this annoyance.=20=

>=20
> This has happened to me in the past... more than an "annoyance" since
> there were three working groups I really wanted to join in the =
physical
> meeting and I missed one. A transcontinental flight, hotel stays, and
> time away from the "day job" are a heavy price that is more than
> "annoying" when you miss 1/3 of the meetings.
>=20
> If the idea of not fixing agendas is to remain, then any experiments =
for
> extending the Friday schedule pretty much mean that everyone has to
> extend their stay, doesn't it? I think if we want to use Friday time
> properly, then this ideology needs to go.
>=20
> Or maybe it already has and I misunderstand things!

The important dates page for the meeting =
<http://www.ietf.org/meeting/cutoff-dates-2011.html#IETF82> shows a date =
for the draft agenda and a date for the final agenda.  We try very hard =
to make no changes after the final agenda date.  Sometimes changes are =
unavoidable because the Area Directors learn about WG-specific details =
that cause conflicts.  That said, we do our best to keep to the final =
agenda.

Russ=

From tjc@ecs.soton.ac.uk  Tue Aug 23 07:07:44 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D32C421F8B7E for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 07:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.754
X-Spam-Level: 
X-Spam-Status: No, score=-2.754 tagged_above=-999 required=5 tests=[AWL=-0.155, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsDI7aCXdGsz for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 07:07:44 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 09FE521F8B0A for <ietf@ietf.org>; Tue, 23 Aug 2011 07:07:43 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7NE8lnT010712 for <ietf@ietf.org>; Tue, 23 Aug 2011 15:08:47 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p7NE8lnT010712
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1314108527; bh=hYhgRo3G0HoIMdpmJJUsQdpq+Yc=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=OLGyLtQFP5tSHMIRC3v7M9/qQEUztD8a6VL4i52XRljMmhpxwH4jIPgyuhSlipOap 2BK+1G/kHkntdBhBQ3TVtRkDQSlNF9HR+/O0yAL6iNaavujANQpGLiikv3vbrhjN/X hX9W4ZyctFC8QrBNrEf/MgZxfOCnGZ9ATBatlrsQ=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n7MF8l0366104545lD ret-id none; Tue, 23 Aug 2011 15:08:47 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7NE8idi010281 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 23 Aug 2011 15:08:44 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <4E52DE03.8020201@gmail.com>
Date: Tue, 23 Aug 2011 15:08:43 +0100
Content-Transfer-Encoding: 7bit
Message-ID: <EMEW3|1034e02accae3be67d19b12a50070052n7MF8l03tjc|ecs.soton.ac.uk|E9CC75CD-8C6E-4C61-8765-687079B4C2E8@ecs.soton.ac.uk>
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20110820031053.0a551ca8@resistor.net>	<005b01cc609a$7e9ab540$4001a8c0@gateway.2wire.net> <01O55J38IMQU00VHKR@mauve.mrochek.com> <4E52DE03.8020201@gmail.com> <E9CC75CD-8C6E-4C61-8765-687079B4C2E8@ecs.soton.ac.uk>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n7MF8l036610454500; tid=n7MF8l0366104545lD; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p7NE8lnT010712
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 14:07:44 -0000

On 22 Aug 2011, at 23:53, Brian E Carpenter wrote:

> +1 to Ned. I can't see why this draft seems to make some people
> go defensive - it isn't saying "IPv4 is evil" or anything silly
> like that, it's just saying "IPv6 is the future".
> 
> RFC1122v6 is another matter entirely. We clearly aren't ready
> for it yet, but draft-ietf-6man-node-req-bis is a step on the way.

I agree with Ned and Brian.

Tim


From john-ietf@jck.com  Tue Aug 23 07:23:23 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C30121F8B78; Tue, 23 Aug 2011 07:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.877
X-Spam-Level: 
X-Spam-Status: No, score=-101.877 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, SARE_ADULT2=1.42, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YI-Ipi0t4Abo; Tue, 23 Aug 2011 07:23:22 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 65C1D21F8B72; Tue, 23 Aug 2011 07:23:22 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qvrti-000K4V-Nu; Tue, 23 Aug 2011 10:24:11 -0400
Date: Tue, 23 Aug 2011 10:24:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Hyatt Taipei cancellation policy?
Message-ID: <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM>
In-Reply-To: <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.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: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 14:23:23 -0000

--On Tuesday, August 23, 2011 07:57 -0400 Thomas Nadeau
<tnadeau@lucidvision.com> wrote:

>> I obviously don't have all of the information available to me
>> that you and the IAOC do, but it seems to be there is always
>> another alternative.   If there are no local ones, that
>> alternative is usually described as "just say no and go
>> elsewhere".  What I'm trying to understand, mostly for the
>> future and with the understanding that it is presumably much
>> too late for Taipei and the several following meetings, is
>> whether you would ever consider that an option for a meeting
>> for which you have a sponsor if you hold it in a particular
>> place or if you and the IAOC really believe there is no
>> alternative under those circumstances.
> 
> I think we need to adopt a simple rule of thumb whereby we do
> not book venues where room rates of less than $200 USD are
> unavailable - sponsor or otherwise.

Tom, I'm usually not the one to leap to the defense of the IAOC
on meeting costs, but I think we need to be very careful about
such rules.  For many of us, total cost of meeting -- total
hotel room costs (which may be different from quoted rate), air
fares and other transport, days away from home, meals,
registration fee (for this meeting, I notice what I think is is
a new incentive to register at the last minute prior to the
"early" cutoff), even the cost of beer for those who depend on
it to lubricate conversations -- is far more important than the
hotel bill alone.  In many cities, rooms quoted at USD 200 (or
much less) are easy to find, but one can make up for it in taxi
charges or Internet access surcharges.  Others may have
different constraints -- I've worked with companies for whom
transport to a meeting comes out of different accounts than
being there and therefore counts either more or less.  And hotel
(and other on-site) costs can fluctuate considerably as exchange
rates change.

Of course, the difficulty of calculating total meeting costs is
that each of us has different habits, comes from different
locations, has different travel perferences, etc.  IAOC claims
that they try to approximate that number and consider it.  I
think they often get it wrong but acknowledge that it is
probably impossible to get it right.

So I'm opposed to a USD 200 (or any other number) firm limit on
hotel rates.  At the same time, I continue to wish that the IAOC
would be more open with the community about how these decisions
are made and, in particular, how the tradeoffs between
sponsorship (and hence lower costs to the IETF for meeting
infrastructure and arrangements) and meetings costs to attendees
are made... open enough that the community could give
substantive guidance on the subject, guidance that I assume the
IAOC would follow if it were coherent and plausible.

Being a little cynical, I do wonder if we would see a difference
in meeting selection patterns if all IASA staff and IAOC members
were required to stay in hotel or other rooms costing no more
than, say, your USD 200 per night figure (including transport,
if necessary, to and from the meeting site).  It might help to
calibrate the pain level.  The idea is not realistic for a
number of reasons, but might make an interesting
thought-experiment.

     john


From tnadeau@lucidvision.com  Tue Aug 23 08:07:32 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1F621F8591; Tue, 23 Aug 2011 08:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uli8Pc9rTZgI; Tue, 23 Aug 2011 08:07:31 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE6F21F84EF; Tue, 23 Aug 2011 08:07:31 -0700 (PDT)
Received: from [192.168.1.104] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id C1B761D9CC22; Tue, 23 Aug 2011 11:08:37 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>
Date: Tue, 23 Aug 2011 11:08:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: "ietf-secretariat@ietf.org" <ietf-secretariat@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 15:07:32 -0000

On Aug 23, 2011, at 9:43 AM, Worley, Dale R (Dale) wrote:

>> From: Michael StJohns
>>=20
>> Could you refresh my memory as to which hotels we stayed at had this
>> policy?  I literally cannot remember having any hotel cancellation
>> policy with more than a single night fee ever.
>=20
> Maastricht had particularly fierce cancellation rules.  I don't
> remember the details, but under some circumstances you could have to
> pay for the entire stay.

	One would think that when the IETF negotiates the room =
block/fees, that this could be done as well. After all we are in many =
cases, booking a significant portion of the hotel in question in =
addition to its conference facilities.

	--Tom



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


From erosen@cisco.com  Tue Aug 23 08:07:53 2011
Return-Path: <erosen@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D125D21F8B1B for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 08:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghdQbmvdmAwv for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 08:07:53 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1BFE921F8B06 for <ietf@ietf.org>; Tue, 23 Aug 2011 08:07:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=erosen@cisco.com; l=3281; q=dns/txt; s=iport; t=1314112141; x=1315321741; h=to:cc:subject:in-reply-to:reply-to:date:message-id:from; bh=BM2AKlGQL61nneVoS/nKeDfzDj1XSZgoWcnjSbbu0Os=; b=VHTQSehh8p89sVdaK53xboVfSaXsTN1YAhxHa5wuBo84UZn1/57Hst/o ZLcmvywr2FU/8xTfAUvgkFjiTOIBDUhjFUdM2gRsb8ndLw7PrX5r4aDWa ST9vEZWn7Y4M8NHtcjslDHlf0X8ugdxCkXJ2j0ugFByWSQ+IhAzDL6/Oh M=;
X-IronPort-AV: E=Sophos;i="4.68,270,1312156800"; d="scan'208";a="15694236"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-6.cisco.com with ESMTP; 23 Aug 2011 15:09:00 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7NF8vHP027395; Tue, 23 Aug 2011 15:08: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 p7NF8u1i018575;  Tue, 23 Aug 2011 11:08:56 -0400
To: "George, Wesley" <wesley.george@twcable.com>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
In-reply-to: Your message of Mon, 22 Aug 2011 13:12:54 -0400. <34E4F50CAFA10349A41E0756550084FB0D5571BD@PRVPEXVS04.corp.twcable.com>
Date: Tue, 23 Aug 2011 11:08:56 -0400
Message-ID: <18574.1314112136@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
Cc: "draft-ietf-intarea-ipv6-required@tools.ietf.org" <draft-ietf-intarea-ipv6-required@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: erosen@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 15:07:53 -0000

This document really wants to be a BCP that makes deployment and strategy
recommendations.  But for some reason it has been disguised as a standards
track document (i.e., as a protocol specification), and the result is that
RFC 2119 language is being used in a very peculiar way.  I think this is
what is responsible for the impression that the document is "bizarre".

Some examples:

      a best effort SHOULD be made to update existing hardware and software
      to enable IPv6 support.

RFC 2119 language is used to distinguish optional from mandatory features in
an implementation.  But "a best effort ... to update existing hardware and
software" does not seem to be a feature of an implementation.  I just don't
understand what this statement requires, or how one would tell if a given
implementation is compliant with it or not.

        Current IP implementations SHOULD support IPv6.

Presumably, "current" implementations support whatever they support, I don't
really understand what is being required here.  

        New IP implementations MUST support IPv6.

Is there some objective difference between a "new" implementation and a
"current" implementation?  How many lines of code have to change before a
"current" implementation becomes a "new" one?

But I don't really see why "new" vs. "current" is even relevant.  If there
were a lot of folks writing IP implementations from scratch, using only the
RFCs for guidance, it would be really important to make sure they know about
IPv6.  Does anyone think that that's a real problem?

It may be a problem that new products continue to come out without IPv6
support, but in general, those new products use current implementations.  So
again, there doesn't actually seem to be a useful requirement expressed.

      IPv6 support MUST be equivalent or better in quality and
      functionality when compared to IPv4 support in an IP
      implementation.

So if the v6 support has more bugs than the v4 support (and hence lesser
quality), the implementation would be out of compliance with standards?  I
don't think IETF standards set quality metrics on implementations.

As for functionality, consider the following bit of functionality: the
ability to communicate with an IPv4-only host.  This is a piece of
functionality that v4 support has but v6 support doesn't.  So I guess no
implementation could ever meet the "requirements" of this document.

Finally:

      MUST NOT require IPv4 for proper and complete function.

Suppose the "proper and complete" function of a box requires the downloading
of updates from a server the box cannot necessarily reach using IPv6.  Then
IPv4 would be required for proper and complete function of the box.  Or
perhaps the box is a network monitoring appliance of some sort, and has to
use both IPv4 and IPv6 to do its job.  In this case too, v4 is required for
"proper and complete" function, but that shouldn't lead anyone to say that
the box is non-compliant with IETF standards.

This document just does not say what it means.  The RFC 2119 language is not
being used in the usual manner, it's really being used for its rhetorical
value.  This is not appropriate.  



















      

From ben@nostrum.com  Mon Aug 22 14:47:05 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5206921F8C57; Mon, 22 Aug 2011 14:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dVOTwctMCPMv; Mon, 22 Aug 2011 14:47:04 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id CF29421F8C4B; Mon, 22 Aug 2011 14:47:04 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p7MLksBn037597 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 22 Aug 2011 16:46:55 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-mpls-rsvp-te-no-php-oob-mapping-08
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=windows-1252
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <7CC717E2F49DAA4A827DA3FEA237111B05AEA2CC@XMB-RCD-103.cisco.com>
Date: Mon, 22 Aug 2011 16:46:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2179A14C-0DA4-48D6-B652-572D625E54C4@nostrum.com>
References: <37428C36-C58A-4848-80E1-8B2FA892FA9B@nostrum.com> <7CC717E2F49DAA4A827DA3FEA237111B05AEA2CC@XMB-RCD-103.cisco.com>
To: Zafar Ali (zali) <zali@cisco.com>
X-Mailer: Apple Mail (2.1244.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 23 Aug 2011 08:08:54 -0700
Cc: gen-art@ietf.org, draft-ietf-mpls-rsvp-te-no-php-oob-mapping.all@tools.ietf.org, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 21:47:05 -0000

Thanks for the response. One further comment below. I removed sections =
that I think have been sufficiently addressed:

On Aug 17, 2011, at 2:45 PM, Zafar Ali (zali) wrote:
[=85]

>=20
>> -- section 3: First paragraph: " Addition of "non-PHP behavior" adds =
a
>> variable of attacks on the label assigned by the Egress node. "
>>=20
>> Is "variable" the correct word?
>>=20
>=20
> It seems to describe the sentence well. We are open to any suggestion.=20=

>=20

Maybe "variety"?

[=85]=

From ben@nostrum.com  Mon Aug 22 15:06:12 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3C0621F854F; Mon, 22 Aug 2011 15:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.47
X-Spam-Level: 
X-Spam-Status: No, score=-102.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIODTGfQfZrU; Mon, 22 Aug 2011 15:06:12 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id 2884121F854D; Mon, 22 Aug 2011 15:06:12 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p7MM620S039290 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 22 Aug 2011 17:06:03 -0500 (CDT) (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 Telechat Review of draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09
Date: Mon, 22 Aug 2011 17:06:00 -0500
Message-Id: <1B155AC7-20E8-4D12-81C3-C1D69E4BEF53@nostrum.com>
To: draft-ietf-mpls-rsvp-te-no-php-oob-mapping.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 23 Aug 2011 08:08:54 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 22:06:12 -0000

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

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

Document: draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09
Reviewer: Ben Campbell
Review Date: 2011-08-22
IESG Telechat date: 2011-08-25

Summary: This draft is ready for publication as a proposed standard. =
This version addresses the editorial comments from my previous review, =
except for one that I understand from separate email will be dealt with =
as an RFC editor note.

Major issues:

None

Minor issues:

None

Nits/editorial comments:

None=

From wwwrun@ietfa.amsl.com  Mon Aug 22 15:30:23 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 4F74521F8BA0; Mon, 22 Aug 2011 15:30:23 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Call for Nominations 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110822223023.4F74521F8BA0@ietfa.amsl.com>
Date: Mon, 22 Aug 2011 15:30:23 -0700 (PDT)
X-Mailman-Approved-At: Tue, 23 Aug 2011 08:08:54 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 22:30:23 -0000

Hi All,

The 2011-2012 Nominating committee is seeking nominations from now 
until October 2, 2011. The list of open positions can be found at:

https://www.ietf.org/group/nomcom/2011/

Nominations may be made directly on the NomCom 2011-2012 pages by 
selecting the Nominate link at the top of the page.  The URL for
NomCom 2011-2012 pages is: 

https://www.ietf.org/group/nomcom/2011/

Nominations may also be made by email to nomcom11@ietf.org.
If you do so, please include the word "Nominate" in the Subject and 
indicate in the email who is being nominated, their email address (to
confirm acceptance of the nomination), and the position for which you 
are making the nomination. If you wish to nominate someone via email 
for more than one position, please use separate emails to do so.

Self nomination is welcome. 

NomCom 2011-2012 will follow the policy for "Open Disclosure of Willing 
Nominees" described in RFC 5680.  As stated in RFC 5680: "The list of 
nominees willing to be considered for positions under review in the 
current NomCom cycle is not confidential". Willing Nominees for each 
position will be publicly listed.  The public nominee list will be 
updated at least once a week and possibly more often as nominations are 
received.

With the exception of publicly listing willing nominees, the 
confidentiality requirements of RFC 3777 remain in effect.  All 
feedback and NomCom deliberations will remain confidential and not 
disclosed. 

Because the list of nominees this year is public, we will accept 
feedback on the nominees starting August 23, 2011. Per RFC 5680, we 
will accept feedback from the entire IETF community on all the nominees. 

If you wish to provide anonymous feedback, the chair or any of the 
members will be happy to handle this for you.  The Nominating Committee 
chair can be reached at nomcom-chair@ietf.org and the entire nominating 
committee can be reached at nomcom11@ietf.org. The email addresses of 
individual NomCom members is also on the NomCom 2011-2012 pages.

In addition to nominations, the Nominating Committee is actively
seeking community input on the jobs that need to be filled.  We have
received the job descriptions from the IAB, IESG, and IAOC and they can
be found at:

https://www.ietf.org/group/nomcom/2011/iab-requirements
https://www.ietf.org/group/nomcom/2011/iesg-requirements
https://www.ietf.org/group/nomcom/2011/iaoc-requirements

However, we also need the community's views and input on the jobs 
within each organization. If you have ideas on job responsibilities 
(more, less, different), please let us know.  Please send suggestions 
and feedback to nomcom11@ietf.org. 

Thank you,

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

From wwwrun@ietfa.amsl.com  Mon Aug 22 15:32:18 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 94D9E21F8BF9; Mon, 22 Aug 2011 15:32:18 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Call for Nominations 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110822223218.94D9E21F8BF9@ietfa.amsl.com>
Date: Mon, 22 Aug 2011 15:32:18 -0700 (PDT)
X-Mailman-Approved-At: Tue, 23 Aug 2011 08:08:54 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 22:32:18 -0000

Hi All,

The 2011-2012 Nominating committee is seeking nominations from now 
until October 2, 2011. The list of open positions can be found at:

https://www.ietf.org/group/nomcom/2011/

Nominations may be made directly on the NomCom 2011-2012 pages by 
selecting the Nominate link at the top of the page.  The URL for
NomCom 2011-2012 pages is: 

https://www.ietf.org/group/nomcom/2011/

Nominations may also be made by email to nomcom11@ietf.org.
If you do so, please include the word "Nominate" in the Subject and 
indicate in the email who is being nominated, their email address (to
confirm acceptance of the nomination), and the position for which you 
are making the nomination. If you wish to nominate someone via email 
for more than one position, please use separate emails to do so.

Self nomination is welcome. 

NomCom 2011-2012 will follow the policy for "Open Disclosure of Willing 
Nominees" described in RFC 5680.  As stated in RFC 5680: "The list of 
nominees willing to be considered for positions under review in the 
current NomCom cycle is not confidential". Willing Nominees for each 
position will be publicly listed.  The public nominee list will be 
updated at least once a week and possibly more often as nominations are 
received.

With the exception of publicly listing willing nominees, the 
confidentiality requirements of RFC 3777 remain in effect.  All 
feedback and NomCom deliberations will remain confidential and not 
disclosed. 

Because the list of nominees this year is public, we will accept 
feedback on the nominees starting August 23, 2011. Per RFC 5680, we 
will accept feedback from the entire IETF community on all the nominees. 

If you wish to provide anonymous feedback, the chair or any of the 
members will be happy to handle this for you.  The Nominating Committee 
chair can be reached at nomcom-chair@ietf.org and the entire nominating 
committee can be reached at nomcom11@ietf.org. The email addresses of 
individual NomCom members is also on the NomCom 2011-2012 pages.

In addition to nominations, the Nominating Committee is actively
seeking community input on the jobs that need to be filled.  We have
received the job descriptions from the IAB, IESG, and IAOC and they can
be found at:

https://www.ietf.org/group/nomcom/2011/iab-requirements
https://www.ietf.org/group/nomcom/2011/iesg-requirements
https://www.ietf.org/group/nomcom/2011/iaoc-requirements

However, we also need the community's views and input on the jobs 
within each organization. If you have ideas on job responsibilities 
(more, less, different), please let us know.  Please send suggestions 
and feedback to nomcom11@ietf.org. 

Thank you,

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

From tnadeau@lucidvision.com  Tue Aug 23 08:12:29 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D289A21F8B84; Tue, 23 Aug 2011 08:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.829
X-Spam-Level: 
X-Spam-Status: No, score=-1.829 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_00=-2.599, SARE_ADULT2=1.42]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BW6OgV+ON1dj; Tue, 23 Aug 2011 08:12:29 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id C87AE21F8AE4; Tue, 23 Aug 2011 08:12:28 -0700 (PDT)
Received: from [192.168.1.104] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 5AC571D9CCC8; Tue, 23 Aug 2011 11:13:33 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM>
Date: Tue, 23 Aug 2011 11:13:32 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <581E74FF-79CE-4C94-8076-5ED6345380E8@lucidvision.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 15:12:29 -0000

On Aug 23, 2011, at 10:24 AM, John C Klensin wrote:

> 
> 
> --On Tuesday, August 23, 2011 07:57 -0400 Thomas Nadeau
> <tnadeau@lucidvision.com> wrote:
> 
>>> I obviously don't have all of the information available to me
>>> that you and the IAOC do, but it seems to be there is always
>>> another alternative.   If there are no local ones, that
>>> alternative is usually described as "just say no and go
>>> elsewhere".  What I'm trying to understand, mostly for the
>>> future and with the understanding that it is presumably much
>>> too late for Taipei and the several following meetings, is
>>> whether you would ever consider that an option for a meeting
>>> for which you have a sponsor if you hold it in a particular
>>> place or if you and the IAOC really believe there is no
>>> alternative under those circumstances.
>> 
>> I think we need to adopt a simple rule of thumb whereby we do
>> not book venues where room rates of less than $200 USD are
>> unavailable - sponsor or otherwise.
> 
> Tom, I'm usually not the one to leap to the defense of the IAOC
> on meeting costs, but I think we need to be very careful about
> such rules.  For many of us, total cost of meeting -- total
> hotel room costs (which may be different from quoted rate), air
> fares and other transport, days away from home, meals,
> registration fee (for this meeting, I notice what I think is is
> a new incentive to register at the last minute prior to the
> "early" cutoff), even the cost of beer for those who depend on
> it to lubricate conversations -- is far more important than the
> hotel bill alone.  In many cities, rooms quoted at USD 200 (or
> much less) are easy to find, but one can make up for it in taxi
> charges or Internet access surcharges.  Others may have
> different constraints -- I've worked with companies for whom
> transport to a meeting comes out of different accounts than
> being there and therefore counts either more or less.  And hotel
> (and other on-site) costs can fluctuate considerably as exchange
> rates change.
> 
> Of course, the difficulty of calculating total meeting costs is
> that each of us has different habits, comes from different
> locations, has different travel perferences, etc.  IAOC claims
> that they try to approximate that number and consider it.  I
> think they often get it wrong but acknowledge that it is
> probably impossible to get it right.

	I agree that the overall cost of each meeting is what really counts.
HOWEVER, most of us work at companies which have rules for 
limits on specific charges (i.e.: hotel room rates).  Having room rates
(fees/taxes/etc...) that exceed about $200 usually gets people in 
trouble with their travel departments, not to mention the overall cost
of the meeting.  I think this was discussed at the last Plenary where
typical meeting venues in Asia were having very significantly higher
costs associated with meeting venues/hotels.

> So I'm opposed to a USD 200 (or any other number) firm limit on
> hotel rates.  At the same time, I continue to wish that the IAOC
> would be more open with the community about how these decisions
> are made and, in particular, how the tradeoffs between
> sponsorship (and hence lower costs to the IETF for meeting
> infrastructure and arrangements) and meetings costs to attendees
> are made... open enough that the community could give
> substantive guidance on the subject, guidance that I assume the
> IAOC would follow if it were coherent and plausible.

	I am not advocating for any hard limit. I said "about $200".  I think
most people would agree that $210 or even $230 would be acceptable, 
whereas $300 is getting a bit silly.

> Being a little cynical, I do wonder if we would see a difference
> in meeting selection patterns if all IASA staff and IAOC members
> were required to stay in hotel or other rooms costing no more
> than, say, your USD 200 per night figure (including transport,
> if necessary, to and from the meeting site).  It might help to
> calibrate the pain level.  The idea is not realistic for a
> number of reasons, but might make an interesting
> thought-experiment.

	Indeed. Budget is budget.

	--Tom




> 
>     john
> 
> 


From dworley@avaya.com  Tue Aug 23 10:45:23 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACCA21F893C for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 10:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.448
X-Spam-Level: 
X-Spam-Status: No, score=-103.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Al5CZjepvEr for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 10:45:23 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id E7F1321F8862 for <ietf@ietf.org>; Tue, 23 Aug 2011 10:45:22 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACPmU07GmAcF/2dsb2JhbABCqCJ3gUABAQEBAgESKC4RBQsCAQgNAQchEDIlAQEEDg0ah0+gGAKcc4VpXwSYRItr
X-IronPort-AV: E=Sophos;i="4.68,270,1312171200"; d="scan'208";a="264069966"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 Aug 2011 13:46:29 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Aug 2011 13:42:32 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Tue, 23 Aug 2011 13:46:28 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Date: Tue, 23 Aug 2011 13:46:27 -0400
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: Acxhpo9sso1dJDoISGecsqSA8IuNWgAFMtxc
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com>
In-Reply-To: <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 17:45:23 -0000

> From: Thomas Nadeau
>=20
> One would think that when the IETF negotiates the room block/fees,
> that this could be done as well. After all we are in many cases,
> booking a significant portion of the hotel in question in addition to
> its conference facilities.

Speaking as someone who has never arranged a convention...  There must
be some difficulty given the IETF's use of sponsors.  E.g., for the
Maastricht meeting, we were sponsored by SIDN, a Netherlands company.
This automatically restricted us to a fairly small number of venues,
which is going to make it harder to get good terms when negotiating.

In regard to cancellations, the situation is inherently poor -- if the
bulk of the hotel's business (or the profitable part of it) is due to
conventions, a freed-up room may not be easily resellable, as there is
unlikely to be another convention in the same facility at the same
time.

At root is that we are trying to negotiate a purchase at a discounted
price without committing to buying any particular number of rooms,
versus only a limited number of possible sellers.

Dale

From ole@cisco.com  Tue Aug 23 11:06:16 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27D521F86F6 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:06:16 -0700 (PDT)
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.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0+abm4kEAG3n for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:06:16 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id E7BAD21F86EC for <ietf@ietf.org>; Tue, 23 Aug 2011 11:06:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=910; q=dns/txt; s=iport; t=1314122844; x=1315332444; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=lOO5MBx5Ii7o3yWrLqmgq0ZNfC9tY1aDTdDw7dA43SU=; b=MGfaDmUKge+r8QGh+h99XSIF8rRen1JqB7hm5qOi/whirfsJTdXNme56 DYSj8K7tppozdCm+kt3LQX+VCXBvaL5tw2eFbbfKeRpKCjVeAXr2Fk2Kf vfzIQKj2SRZexPhmcFlmlODbOwAGN3gKuvg0HofA/0z0e5LSRTuTTYVfk 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAGjrU06rRDoH/2dsb2JhbAA/A6gid4E5BwEBAQEDEgECASQ/EAtGVwYTIqUMAYMmDwGcJINBgwcEh2GVMIci
X-IronPort-AV: E=Sophos;i="4.68,270,1312156800"; d="scan'208";a="15776009"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-9.cisco.com with ESMTP; 23 Aug 2011 18:07:24 +0000
Received: from sjc-vpn4-416.cisco.com (sjc-vpn4-416.cisco.com [10.21.81.160]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7NI7NYW003619; Tue, 23 Aug 2011 18:07:23 GMT
Date: Tue, 23 Aug 2011 11:07:23 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: RE: Hyatt Taipei cancellation policy?
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com>
Message-ID: <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 18:06:16 -0000

You said:

"At root is that we are trying to negotiate a purchase at a discounted
 price without committing to buying any particular number of rooms,
 versus only a limited number of possible sellers."

When negotiating a group rate we actually ARE committing to buying a 
certain number of rooms (the "room block"). There are certainly pros
and cons with group rates. On the pro side: guaranteed rate (but not 
necessarily the absolute lowest available at any time), included 
benefits (breakfast, Internet, if applicable), free or subsidized
meeting rooms where applicable. On the cons side is of course the
cancellation policy (not that it has to be as onerous as this one).

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From tnadeau@lucidvision.com  Tue Aug 23 11:22:27 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D5621F8C04 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level: 
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9Y7VfKgU0vK for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:22:25 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 81EFC21F8C0A for <ietf@ietf.org>; Tue, 23 Aug 2011 11:22:25 -0700 (PDT)
Received: from [192.168.1.104] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id B33A21D9DBB2; Tue, 23 Aug 2011 14:23:32 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com>
Date: Tue, 23 Aug 2011 14:23:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 18:22:27 -0000

	But surely based on that block purchasing power we could =
negotiate more reasonable rates than $200+ night?

	--Tom



On Aug 23, 2011, at 2:07 PM, Ole Jacobsen wrote:

>=20
> You said:
>=20
> "At root is that we are trying to negotiate a purchase at a discounted
> price without committing to buying any particular number of rooms,
> versus only a limited number of possible sellers."
>=20
> When negotiating a group rate we actually ARE committing to buying a=20=

> certain number of rooms (the "room block"). There are certainly pros
> and cons with group rates. On the pro side: guaranteed rate (but not=20=

> necessarily the absolute lowest available at any time), included=20
> benefits (breakfast, Internet, if applicable), free or subsidized
> meeting rooms where applicable. On the cons side is of course the
> cancellation policy (not that it has to be as onerous as this one).
>=20
> Ole
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20
>=20


From ole@cisco.com  Tue Aug 23 11:26:40 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5588921F8BE7 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:26:40 -0700 (PDT)
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.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARsCCMceTDiI for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:26:39 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id B95A421F8BCB for <ietf@ietf.org>; Tue, 23 Aug 2011 11:26:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=515; q=dns/txt; s=iport; t=1314124068; x=1315333668; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=zE4fmfn/bBsowOp7NaOmotDwWWYvliJ2OzLbeUpp+EI=; b=ZVpQvwDo/Jx3VEZwCOLuwOkCN5XnlXLGa9ldTzuLlkJ9vWMSR7vSEmg3 5q8u42lNp8XpPzudChm6VDaxB8dAuyPkwsAfLuAwZ0d2CVCKlP7De8kpp Flc0xuDxPtlYar01krYaly+4oQrjhInxYAVMxa9EoXORSg7qLz7DjUUtv g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAFnwU06rRDoG/2dsb2JhbAA/A6dkd4FAAQEBAQIBEgECASQ/EAsOOFcGEyKHT51yAYMmDwGcIoNBgwcEh2GVMIci
X-IronPort-AV: E=Sophos;i="4.68,270,1312156800"; d="scan'208";a="15780045"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-4.cisco.com with ESMTP; 23 Aug 2011 18:27:47 +0000
Received: from sjc-vpn4-416.cisco.com (sjc-vpn4-416.cisco.com [10.21.81.160]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7NIRkOg001180; Tue, 23 Aug 2011 18:27:46 GMT
Date: Tue, 23 Aug 2011 11:27:46 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com>
Message-ID: <alpine.OSX.2.01.1108231126370.70222@sjc-vpn4-416.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 18:26:40 -0000

Probably not for that hotel in that location in the current economic 
climate etc. I wasn't the negotiator :-)


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Tue, 23 Aug 2011, Thomas Nadeau wrote:

> 
> 	But surely based on that block purchasing power we could 
> 	negotiate more reasonable rates than $200+ night?
> 
> 	--Tom
> 
>

From dwm@xpasc.com  Tue Aug 23 11:28:26 2011
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B992621F8BE7 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.353
X-Spam-Level: 
X-Spam-Status: No, score=-2.353 tagged_above=-999 required=5 tests=[AWL=-1.046, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9krwdtofAgtx for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 11:28:26 -0700 (PDT)
Received: from mail.xpasc.com (mail.xpasc.com [68.164.244.189]) by ietfa.amsl.com (Postfix) with ESMTP id 54AC021F8C26 for <ietf@ietf.org>; Tue, 23 Aug 2011 11:28:26 -0700 (PDT)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id E4C20100586 for <ietf@ietf.org>; Tue, 23 Aug 2011 11:29:35 -0700 (PDT)
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 iz6Urb8nitz0; Tue, 23 Aug 2011 11:29:35 -0700
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id ACEAA100585 for <ietf@ietf.org>; Tue, 23 Aug 2011 11:29:35 -0700 (PDT)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id p7NITYLQ013240 for <ietf@ietf.org>; Tue, 23 Aug 2011 11:29:34 -0700
Date: Tue, 23 Aug 2011 11:29:34 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com>
Message-ID: <Pine.LNX.4.64.1108231125430.21813@egate.xpasc.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Propel-ID: iz6Urb8nitz0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietf@ietf.org" <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 18:28:26 -0000

Reasonable has to be measured on the basis of what the venue might expect
for alternative customers at the time of negotiation, not our world view 
of hotels at the time of meetings.

For this to be a meaningful disccusion re. the success or lack there of,
we need to compare what we have vs. similar sized groups in the same 
season, etc. at the same venue.

It is a separate discussion re. whether the overall cost or distribution
of categories of costs is optimum for the group.

Dave Morris

On Tue, 23 Aug 2011, Thomas Nadeau wrote:

> 
> 	But surely based on that block purchasing power we could negotiate more reasonable rates than $200+ night?
> 
> 	--Tom
> 
> 
> 
> On Aug 23, 2011, at 2:07 PM, Ole Jacobsen wrote:
> 
> > 
> > You said:
> > 
> > "At root is that we are trying to negotiate a purchase at a discounted
> > price without committing to buying any particular number of rooms,
> > versus only a limited number of possible sellers."
> > 
> > When negotiating a group rate we actually ARE committing to buying a 
> > certain number of rooms (the "room block"). There are certainly pros
> > and cons with group rates. On the pro side: guaranteed rate (but not 
> > necessarily the absolute lowest available at any time), included 
> > benefits (breakfast, Internet, if applicable), free or subsidized
> > meeting rooms where applicable. On the cons side is of course the
> > cancellation policy (not that it has to be as onerous as this one).
> > 
> > Ole

From sm@resistor.net  Tue Aug 23 12:34:00 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E6FB21F8C75; Tue, 23 Aug 2011 12:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+DMIALy5X2N; Tue, 23 Aug 2011 12:33:59 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D96521F8C73; Tue, 23 Aug 2011 12:33:59 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7NJZ1Wr015217; Tue, 23 Aug 2011 12:35:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1314128106; bh=LY7uOLneZwBtNlaesZetj0gLfraKzq7smroyQq2ScUU=; h=Message-Id:Date:To:From:Subject:Mime-Version:Content-Type:Cc; b=yDBn+MDID7BXpILmfZqOzqiin05ZLswso49zIHl4d4pYrlHo0L37CVXIx6LHCXjYo ELevzAFKnrpfcFL3r2C5nOOZGeqfyrVeaHzsUr41nDvc8KcfjpGiaXhHgc1TAAwsnV HVZm+FLrw4XnW4I6APDrUbvnyLHvS9ppiQ6NVzP0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1314128106; bh=LY7uOLneZwBtNlaesZetj0gLfraKzq7smroyQq2ScUU=; h=Message-Id:Date:To:From:Subject:Mime-Version:Content-Type:Cc; b=3VndPTtGHEgnOyttRB19He3s+tkCvkv+gW1Ll7hQs9mC9+tGPMWMEEHndPxGoC2fv 2NDCQ+RdIqBVKKqEv7pWStlJ1mmSvfk7AmBjwDWGw8nuEDH8uNIwSyF/UG+FtHE1wC U9Qv9mPbnUbnPEOTJ5VznsRSVq4mkQQfapWJThZw=
Message-Id: <6.2.5.6.2.20110823112247.0b645658@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 23 Aug 2011 12:34:53 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Discussing a DISCUSS - down-refs in draft-ietf-yam-rfc4409bis-02
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 19:34:00 -0000

There is currently a DISCUSS for draft-ietf-yam-rfc4409bis-02:

<process weenie="">

The IETF LC
(https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=9680&tid=1314107697)
did not call out the downrefs to RFC 4954 and 5321.  There is no doubt in my
mind that no one will object to these downrefs, but they need to be explicitly
called out in the IETF LC.

</process>

The intent of this message is to discuss the DISCUSS as there seems 
to be a misunderstanding about down-refs.  I do not consider it as 
inappropriate for the AD to have lodged the above DISCUSS.

The argument for this DISCUSS is that the downrefs to RFC 4954 and 
5321 have not been called out during the IETF Last Call.  The quick 
fix is to rerun the Last Call.  That approach would not materially 
affect the outcome.

I have pointed out during the Last Call that there are down-refs [1] 
and provided a justification for them.  Appendix B of 
draft-ietf-yam-rfc4409bis-02 contains a RFC 4897 statement/ disclaimer.

I would be grateful if the IESG or Area Director can clarify the 
DISCUSS criteria used [2] given that BCP 97 allows for annotations in 
handling of normative references in Standards-Track documents.

If there is appropriate community review, is it acceptable to add a 
downward reference even though it was not explicitly called out 
previously?  In other words, why should there be another Last Call?

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg68421.html
2. http://www.ietf.org/iesg/statement/discuss-criteria.html


From ajs@anvilwalrusden.com  Tue Aug 23 13:32:47 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C006D21F8AD3 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 13:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SFI5bem3vEM7 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 13:32:47 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 3895421F8AAC for <ietf@ietf.org>; Tue, 23 Aug 2011 13:32:47 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id AAE401ECB41D for <ietf@ietf.org>; Tue, 23 Aug 2011 20:33:56 +0000 (UTC)
Date: Tue, 23 Aug 2011 16:33:52 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
Message-ID: <20110823203352.GC52234@shinkuro.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com> <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com> <Pine.LNX.4.64.1108231125430.21813@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.64.1108231125430.21813@egate.xpasc.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 20:32:47 -0000

On Tue, Aug 23, 2011 at 11:29:34AM -0700, David Morris wrote:

> For this to be a meaningful disccusion re. the success or lack there of,
> we need to compare what we have vs. similar sized groups in the same 
> season, etc. at the same venue.

_And_ having negotiated at the same time, as Ray pointed out already
in this thread.  Every time one of these discussions comes up, people
seem to forget that the negotiations are happening several years in
advance of the actual event.  Agreements about the future almost
always require the party buying to take some risk that they will be
paying more than the going rate at the time the actual sale date
arrives.  In the case of hotel agreements, the block negotiator takes
some risk that there will be a lower price or otherwise better terms
actually available at the time of the block being used.  The hotel
takes some risk that the block negotiator is unable to deliver the
actual room occupancy negotiated.  Each is making a bet.  

If you don't like the cancellation terms (or other terms of the bet),
don't participate in it: don't make a reservation in the IETF block.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dworley@avaya.com  Tue Aug 23 13:38:45 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B11F21F8C1A for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 13:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.45
X-Spam-Level: 
X-Spam-Status: No, score=-103.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAT9Vfl-2SKs for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 13:38:45 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 046C121F8B20 for <ietf@ietf.org>; Tue, 23 Aug 2011 13:38:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAFsOVE6HCzI1/2dsb2JhbABCp2V3gUABAQEBAgESKD8FCwIBCA0IIRAyJQEBBA4FCBqHT6BiApxehWlfBJhEi2s
X-IronPort-AV: E=Sophos;i="4.68,271,1312171200"; d="scan'208";a="299509542"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 23 Aug 2011 16:39:52 -0400
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; 23 Aug 2011 16:31:25 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 23 Aug 2011 16:39:52 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Ole Jacobsen <ole@cisco.com>
Date: Tue, 23 Aug 2011 16:37:19 -0400
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: Acxhv4P/8TTsm4mBRECt3ZvHDEDO3gAFPBiL
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F584D@DC-US1MBEX4.global.avaya.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com>, <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 20:38:45 -0000

> From: Ole Jacobsen [ole@cisco.com]
>=20
> When negotiating a group rate we actually ARE committing to buying a
> certain number of rooms (the "room block").

Are we really committing?  Yes, the IETF block in the primary hotel
fills in my experience, but if it doesn't, is the IETF committing to
paying the difference?  And of course, there are cancels after the
cutoff, which reduce the number of rooms sold in the block (unless the
IETF is picking up the tab for those, too).

Dale

From fred@cisco.com  Tue Aug 23 14:09:00 2011
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22A4621F8D3C for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.376
X-Spam-Level: 
X-Spam-Status: No, score=-104.376 tagged_above=-999 required=5 tests=[AWL=-1.777, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDn7sr0Ph76o for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:08:59 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 30A5721F8D2D for <ietf@ietf.org>; Tue, 23 Aug 2011 14:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1705; q=dns/txt; s=iport; t=1314133808; x=1315343408; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=dvVJDPZSV+vfTunN7O4nVM/xDWF/g6ye20i1dfPhY/w=; b=SqWQfJMX2mjEcduc5mt1qtuk0BbRqwRGqUXr6FAt64LEg8RAsNWlEQbI 5FFDhdzmrQmB4dKRF8zxoNAqhAEM0Yt9azczmvu6ZexNwRcDCMTXEzNv5 zJ8U7zn235xaOfp+bWKPy2aFgRDg+Ty09r/boMRwnf8xRGysb3HdFc1nS A=;
X-IronPort-AV: E=Sophos;i="4.68,271,1312156800"; d="scan'208";a="15832531"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-6.cisco.com with ESMTP; 23 Aug 2011 21:10:07 +0000
Received: from dhcp-128-107-114-18.cisco.com (dhcp-128-107-114-18.cisco.com [128.107.114.18]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7NLA7qt004710; Tue, 23 Aug 2011 21:10:07 GMT
Received: from [127.0.0.1] by dhcp-128-107-114-18.cisco.com (PGP Universal service); Tue, 23 Aug 2011 14:10:07 -0700
X-PGP-Universal: processed; by dhcp-128-107-114-18.cisco.com on Tue, 23 Aug 2011 14:10:07 -0700
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com>
Date: Tue, 23 Aug 2011 14:09:57 -0700
Message-Id: <5C117D47-99CA-48A4-86D2-DA2E37BA923C@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 21:09:00 -0000

On Aug 23, 2011, at 11:23 AM, Thomas Nadeau wrote:

>=20
> 	But surely based on that block purchasing power we could =
negotiate more reasonable rates than $200+ night?

Well, the Cisco corporate rate at the Hyatt is also $265/night. Given =
that the hotel is around the corner from the Cisco office, we have some =
traffic there.

I wouldn't discount the effect of the value of the dollar on hotel rates =
as measured in US dollars.

> 	--Tom
>=20
>=20
>=20
> On Aug 23, 2011, at 2:07 PM, Ole Jacobsen wrote:
>=20
>>=20
>> You said:
>>=20
>> "At root is that we are trying to negotiate a purchase at a =
discounted
>> price without committing to buying any particular number of rooms,
>> versus only a limited number of possible sellers."
>>=20
>> When negotiating a group rate we actually ARE committing to buying a=20=

>> certain number of rooms (the "room block"). There are certainly pros
>> and cons with group rates. On the pro side: guaranteed rate (but not=20=

>> necessarily the absolute lowest available at any time), included=20
>> benefits (breakfast, Internet, if applicable), free or subsidized
>> meeting rooms where applicable. On the cons side is of course the
>> cancellation policy (not that it has to be as onerous as this one).
>>=20
>> Ole
>>=20
>>=20
>> Ole J. Jacobsen
>> Editor and Publisher,  The Internet Protocol Journal
>> Cisco Systems
>> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>> Skype: organdemo
>>=20
>>=20
>>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From fred@cisco.com  Tue Aug 23 14:16:03 2011
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30E2921F8D63 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.199
X-Spam-Level: 
X-Spam-Status: No, score=-104.199 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fzK5MiBB0Xv5 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:16:02 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id A1A6521F8CE3 for <ietf@ietf.org>; Tue, 23 Aug 2011 14:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=241; q=dns/txt; s=iport; t=1314134231; x=1315343831; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=CPGP4Pn98QLTlWrLDPZ82aTmxACNqGRQ1UUfqeuZVKA=; b=YB8ub70PoVBbDEsYw7avCk5C4obg36OfbMT163hlDPEVJc4SHhcaCfyZ BHbb6RvRojCrtwHHnQQQSADvtKgNc8q3SG9PcSipPNMb0l0aeK3ylCq9f bN8e6Xo6xxUeYKDPINBPPJNVkTV8KS6UsitU7M/eUIzOiaE2QT/Pxty0A 8=;
X-IronPort-AV: E=Sophos;i="4.68,271,1312156800"; d="scan'208";a="15843488"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-7.cisco.com with ESMTP; 23 Aug 2011 21:17:11 +0000
Received: from dhcp-128-107-114-18.cisco.com (dhcp-128-107-114-18.cisco.com [128.107.114.18]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7NLHAX3006112; Tue, 23 Aug 2011 21:17:10 GMT
Received: from [127.0.0.1] by dhcp-128-107-114-18.cisco.com (PGP Universal service); Tue, 23 Aug 2011 14:17:10 -0700
X-PGP-Universal: processed; by dhcp-128-107-114-18.cisco.com on Tue, 23 Aug 2011 14:17:10 -0700
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F584D@DC-US1MBEX4.global.avaya.com>
Date: Tue, 23 Aug 2011 14:12:39 -0700
Message-Id: <F7F9F0A3-B529-4BD2-AF90-2547F8335E08@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com>, <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584D@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 21:16:03 -0000

On Aug 23, 2011, at 1:37 PM, Worley, Dale R (Dale) wrote:

> Are we really committing?  Yes, the IETF block in the primary hotel
> fills in my experience, but if it doesn't, is the IETF committing to
> paying the difference? 

yes.

From d3e3e3@gmail.com  Tue Aug 23 14:24:18 2011
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169F521F8CC1 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:24:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.26
X-Spam-Level: 
X-Spam-Status: No, score=-104.26 tagged_above=-999 required=5 tests=[AWL=-0.661, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1C4yhg9+H3H4 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:24:17 -0700 (PDT)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id 5264E21F8CB9 for <ietf@ietf.org>; Tue, 23 Aug 2011 14:24:16 -0700 (PDT)
Received: by iye1 with SMTP id 1so710120iye.27 for <ietf@ietf.org>; Tue, 23 Aug 2011 14:25:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=dWu3stkHM4SmMZd8arGMcQ/4q5MAM8SI2dpTTtbQXA4=; b=KlHrZm+qWwP9B16SW0axxMXT9cmvl/O6ptgJfvCiNBtA4OlpmqLGE4dVs/YwhmbCr3 TtbcVL7WVqwm/uaa8E/eRLjIpJ0wYNqZ190kMtUqJH7skzyq4l5UJfGap66jlbJNYW9v NU+87Z7pgOSjhr59Vhs07GwTJqPZkeujAo98c=
Received: by 10.231.26.68 with SMTP id d4mr8604445ibc.66.1314134722102; Tue, 23 Aug 2011 14:25:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.182.4 with HTTP; Tue, 23 Aug 2011 14:25:02 -0700 (PDT)
In-Reply-To: <F7F9F0A3-B529-4BD2-AF90-2547F8335E08@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com> <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584D@DC-US1MBEX4.global.avaya.com> <F7F9F0A3-B529-4BD2-AF90-2547F8335E08@cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 23 Aug 2011 17:25:02 -0400
Message-ID: <CAF4+nEGN0kmFSVbgkEG=_Wswe6HGewzk52nsLZMcdQ58d-L1Ng@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
To: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 21:24:18 -0000

Most hotel contracts I've signed have a clause called "Attrition"
which calls for payment if the rooms actually taken fall below some
percentage of the "room block", like below 90% or the like.

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 Tue, Aug 23, 2011 at 5:12 PM, Fred Baker <fred@cisco.com> wrote:
>
> On Aug 23, 2011, at 1:37 PM, Worley, Dale R (Dale) wrote:
>
>> Are we really committing? =A0Yes, the IETF block in the primary hotel
>> fills in my experience, but if it doesn't, is the IETF committing to
>> paying the difference?
>
> yes.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From ole@cisco.com  Tue Aug 23 14:25:44 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DB021F8C4B for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:25:44 -0700 (PDT)
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.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNMMi20TO+Po for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 14:25:44 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 64CEE21F8C12 for <ietf@ietf.org>; Tue, 23 Aug 2011 14:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1485; q=dns/txt; s=iport; t=1314134813; x=1315344413; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=tQdQ/oihPUVCPBZljP/MC+/gBF+dde0TGI+XAF25JqU=; b=hJ6fZyhN8BXfVmSnVDHJ2ZB1AdYV1Wylmr9LaSsLeA5WZN4AP2oWOgdu OCHoYsteLIj2jynoQ2PsPIYLAsOcw9k2IbMf7dDFmNXxlaJOcZ4pwygHI 6AvJpoLHmlN94ZRf3klTuXJw3zrbG6yXQgRr/LO1jGtOIeuZA+oDJLxvI c=;
X-IronPort-AV: E=Sophos;i="4.68,271,1312156800"; d="scan'208";a="15836774"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-3.cisco.com with ESMTP; 23 Aug 2011 21:26:53 +0000
Received: from sjc-vpn6-260.cisco.com (sjc-vpn6-260.cisco.com [10.21.121.4]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7NLQqxQ011447; Tue, 23 Aug 2011 21:26:52 GMT
Date: Tue, 23 Aug 2011 14:26:52 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <CAF4+nEGN0kmFSVbgkEG=_Wswe6HGewzk52nsLZMcdQ58d-L1Ng@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1108231426450.276@sjc-vpn6-260.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com> <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584D@DC-US1MBEX4.global.avaya.com> <F7F9F0A3-B529-4BD2-AF90-2547F8335E08@cisco.com> <CAF4+nEGN0kmFSVbgkEG=_Wswe6HGewzk52nsLZMcdQ58d-L1Ng@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="140733193388032-150182179-1314134812=:276"
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 21:25:45 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--140733193388032-150182179-1314134812=:276
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT

Exactly.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Tue, 23 Aug 2011, Donald Eastlake wrote:

> Most hotel contracts I've signed have a clause called "Attrition"
> which calls for payment if the rooms actually taken fall below some
> percentage of the "room block", like below 90% or the like.
> 
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street
>  Milford, MA 01757 USA
>  d3e3e3@gmail.com
> 
> 
> On Tue, Aug 23, 2011 at 5:12 PM, Fred Baker <fred@cisco.com> wrote:
> >
> > On Aug 23, 2011, at 1:37 PM, Worley, Dale R (Dale) wrote:
> >
> >> Are we really committing?  Yes, the IETF block in the primary hotel
> >> fills in my experience, but if it doesn't, is the IETF committing to
> >> paying the difference?
> >
> > yes.
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
> 
--140733193388032-150182179-1314134812=:276--

From hartmans@mit.edu  Tue Aug 23 15:01:43 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D3521F8D29 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 15:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.756
X-Spam-Level: 
X-Spam-Status: No, score=-103.756 tagged_above=-999 required=5 tests=[AWL=-1.491, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCfFTDm1xsjw for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 15:01:42 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 61C0E21F8D26 for <ietf@ietf.org>; Tue, 23 Aug 2011 15:01:42 -0700 (PDT)
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 B6428203A2; Tue, 23 Aug 2011 18:05:08 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E7F57423D; Tue, 23 Aug 2011 18:02:45 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: SM <sm@resistor.net>
Subject: Re: Discussing a DISCUSS - down-refs in draft-ietf-yam-rfc4409bis-02
References: <6.2.5.6.2.20110823112247.0b645658@elandnews.com>
Date: Tue, 23 Aug 2011 18:02:45 -0400
In-Reply-To: <6.2.5.6.2.20110823112247.0b645658@elandnews.com> (sm@resistor.net's message of "Tue, 23 Aug 2011 12:34:53 -0700")
Message-ID: <tslei0beqgq.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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 22:01:43 -0000

>>>>> "SM" == SM  <sm@resistor.net> writes:

    SM> There is currently a DISCUSS for draft-ietf-yam-rfc4409bis-02:
    SM> <process weenie="">

    SM> The IETF LC
    SM> (https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=9680&tid=1314107697)
    SM> did not call out the downrefs to RFC 4954 and 5321.  There is no
    SM> doubt in my mind that no one will object to these downrefs, but
    SM> they need to be explicitly called out in the IETF LC.

    SM> </process>

    SM> The intent of this message is to discuss the DISCUSS as there
    SM> seems to be a misunderstanding about down-refs.  I do not
    SM> consider it as inappropriate for the AD to have lodged the above
    SM> DISCUSS.

    SM> The argument for this DISCUSS is that the downrefs to RFC 4954
    SM> and 5321 have not been called out during the IETF Last Call.
    SM> The quick fix is to rerun the Last Call.  That approach would
    SM> not materially affect the outcome.

    SM> I have pointed out during the Last Call that there are down-refs
    SM> [1] and provided a justification for them.  Appendix B of
    SM> draft-ietf-yam-rfc4409bis-02 contains a RFC 4897 statement/
    SM> disclaimer.

Hey, I think I read RFC 4897 once.
Someone's actually trying to use that? Who knew!

Seriously, section 3.1 of RFC 4897 makes it clear that an RFC 4897
downward reference does not need an RFC 3967-style comment in the IETF
last call.  As best I can tell, this discuss should be cleared because
The AD is confused about what BCP is being applied here.

Really this is one of those situations where we're all sitting around
the table playing a nice game of "publish that doc" and people have to
get out their copy of the IETF rules, the IETF rules erata and the IETF
player's magazine articles with rules commentary and figure out what is
going on.:-)

From jason_livingood@cable.comcast.com  Tue Aug 23 15:33:21 2011
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2390721F8B40 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 15:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.098
X-Spam-Level: 
X-Spam-Status: No, score=-105.098 tagged_above=-999 required=5 tests=[AWL=3.365, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0oH4OvKitzbc for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 15:33:20 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by ietfa.amsl.com (Postfix) with ESMTP id 6F87821F8B3D for <ietf@ietf.org>; Tue, 23 Aug 2011 15:33:20 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.138033572; Tue, 23 Aug 2011 18:34:23 -0400
Received: from PACDCEXMB06.cable.comcast.com ([fe80::6134:ea50:286a:c0]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%11]) with mapi id 14.01.0289.001; Tue, 23 Aug 2011 18:34:24 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Fred Baker <fred@cisco.com>, Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: AQHMYTtYwfKRwObIc0KKAFBB5ouNU5UqtcmAgAAX34CAACwZgIAABdmAgAAEfwCAAC6EgP//sv4A
Date: Tue, 23 Aug 2011 22:34:23 +0000
Message-ID: <CA798673.37027%jason_livingood@cable.comcast.com>
In-Reply-To: <5C117D47-99CA-48A4-86D2-DA2E37BA923C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.12.0.110505
x-originating-ip: [24.40.55.71]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D46801669824F44ABFC738A388143F75@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 22:33:21 -0000

On 8/23/11 3:09 PM, "Fred Baker" <fred@cisco.com> wrote:

>I wouldn't discount the effect of the value of the dollar on hotel rates
>as measured in US dollars.

I suspect Fred is spot on -- current exchange rate fluctuation is
undoubtedly a huge issue. I would speculate that most hotels would
negotiate for payment in their local currency and that since the time of
that agreement the US dollar has depreciated against most currencies
(blame 'quantitative easing' I suppose).

Jason


From stpeter@stpeter.im  Tue Aug 23 15:49:32 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9B0621F8C66 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 15:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level: 
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQbYuMGGaIxZ for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 15:49:32 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 0F29D21F8C5C for <ietf@ietf.org>; Tue, 23 Aug 2011 15:49:32 -0700 (PDT)
Received: from dhcp-64-101-72-239.cisco.com (unknown [64.101.72.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B905A415A0; Tue, 23 Aug 2011 16:52:56 -0600 (MDT)
Message-ID: <4E542EBF.6080303@stpeter.im>
Date: Tue, 23 Aug 2011 16:50:39 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <CA798673.37027%jason_livingood@cable.comcast.com>
In-Reply-To: <CA798673.37027%jason_livingood@cable.comcast.com>
X-Enigmail-Version: 1.3
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 22:49:32 -0000

On 8/23/11 4:34 PM, Livingood, Jason wrote:
> On 8/23/11 3:09 PM, "Fred Baker" <fred@cisco.com> wrote:
> 
>> I wouldn't discount the effect of the value of the dollar on hotel rates
>> as measured in US dollars.
> 
> I suspect Fred is spot on -- current exchange rate fluctuation is
> undoubtedly a huge issue. I would speculate that most hotels would
> negotiate for payment in their local currency and that since the time of
> that agreement the US dollar has depreciated against most currencies
> (blame 'quantitative easing' I suppose).

Come on, folks, let's be honest: all-in-one conference hotels, and
hotels connected to conference centers, charge exorbitant amounts of
money for the convenience of sleeping in close proximity to the meeting
rooms. Thanks to tips from other cost-conscious IETFers, I was able to
find hotels costing $100 (IETF 81) and $170 (IETF 82) a night cheaper
than the official venue. Sure, I have to walk for five minutes to get
back and forth to the meeting rooms, but that seems like a small price
to pay. If you don't like the recommended hotels, vote with your feet.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From glenzorn@gmail.com  Tue Aug 23 21:33:26 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71E1021F8B47; Tue, 23 Aug 2011 21:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m2js3cwIbq4X; Tue, 23 Aug 2011 21:33:25 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id BB52421F8A6C; Tue, 23 Aug 2011 21:33:25 -0700 (PDT)
Received: by gxk19 with SMTP id 19so745041gxk.31 for <multiple recipients>; Tue, 23 Aug 2011 21:34:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=p1hTQz2q/NmTI9o9Z903aDY4qI0xbhRzIM4JvSDJbyY=; b=o/qGq54BDOSBL1LIClcPxWKX2o41TxKwlpuY8s77s8MlvMZrlCBOKVLPyru/oMEBjJ AILtBZ9duo6m0yBHGV6aFXjLZCDGpwcPxPfYpe0eKuK3h/C7L8Xx9e3Oz9YkWPO/0qa2 j4crGArOXkpN0eUa4/CW2iwCE0if/00KSVTNw=
Received: by 10.146.30.22 with SMTP id d22mr4643107yad.32.1314160475045; Tue, 23 Aug 2011 21:34:35 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-122-122-148.revip2.asianet.co.th [124.122.122.148]) by mx.google.com with ESMTPS id s13sm571755anm.6.2011.08.23.21.34.30 (version=SSLv3 cipher=OTHER); Tue, 23 Aug 2011 21:34:33 -0700 (PDT)
Message-ID: <4E547F53.3080309@gmail.com>
Date: Wed, 24 Aug 2011 11:34:27 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM> <581E74FF-79CE-4C94-8076-5ED6345380E8@lucidvision.com>
In-Reply-To: <581E74FF-79CE-4C94-8076-5ED6345380E8@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 04:33:26 -0000

On 8/23/2011 10:13 PM, Thomas Nadeau wrote:

...

> 	I agree that the overall cost of each meeting is what really counts.
> HOWEVER, most of us work at companies which have rules for 
> limits on specific charges (i.e.: hotel room rates).  Having room rates
> (fees/taxes/etc...) that exceed about $200 usually gets people in 
> trouble with their travel departments, not to mention the overall cost
> of the meeting.  I think this was discussed at the last Plenary where
> typical meeting venues in Asia were having very significantly higher
> costs associated with meeting venues/hotels.

This suggests that perhaps we should look a bit more a _untypical_
venues.  As I attempted (apparently with little success) to point out on
this list, once you expand your scope outside of NE Asia (by which I
mean Japan, South Korea and the easy targets in China (Beijing,
Shanghai, Hong Kong, etc.), a whole new world opens up...

...

From eburger@standardstrack.com  Tue Aug 23 21:39:33 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39CFF21F8B1A for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 21:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.628
X-Spam-Level: 
X-Spam-Status: No, score=-101.628 tagged_above=-999 required=5 tests=[AWL=-0.888, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VNDg8ZvsNcNG for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 21:39:30 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 19A4521F8B09 for <ietf@ietf.org>; Tue, 23 Aug 2011 21:39:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=HkaCpVn6IDVlOZQV1VHKU9BeTczVLRCscMBLAdpgbpHmHBfdLn6b0pFaaIltTQ5/dhdN+XjlJeivWAEaHX1XoF7xTS7X97avhNfbjuw5jeInK/w8o0xVIAkv7tD/fx5C;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Qw5GY-00075b-EO for ietf@ietf.org; Tue, 23 Aug 2011 21:40:38 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-19-846187223; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: Hyatt Taipei cancellation policy?
Date: Wed, 24 Aug 2011 00:40:36 -0400
In-Reply-To: <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM>
To: IETF-Discussion list <ietf@ietf.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM>
Message-Id: <F24ADCCF-9303-4465-A934-79FEB001A7FA@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 04:39:33 -0000

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

IAOC members are like all other IETF members. We pay for our hotel =
rooms. That means when I have a full-time job that wants me at the IETF, =
I stay at the convention hotel. When I don't have a full-time sponsor, =
like now, I stayed at:

o   A charming bed & breakfast 500m from the Maastricht convention =
center. The entire week was the price of one night at the NH. In 2010 US =
Dollars, about USD 215. In 2011 US Dollars, about USD 260. Then again, =
that was per week, not per night.

o   A Hilton in Beijing. That was free for me, as I had tons of HHonors =
points. Taxi ~ USD 6/day.

o   The Hilton in Prague. Score! More HHonors points. Before anyone =
cries foul, I am NOT on the IAOC venue selection committee, so no, I had =
no influence on picking a Hilton.

o   A tourist hotel 2.5km from the Quebec convention center. That hotel =
was CDN 140/night less expensive than the Hilton. CDN 20/day, including =
tip, if you took a taxi by yourself. Much cheaper if you took mass =
transit. Yes, now I am low on Hilton points.

In Beijing and Quebec I moved to the conference hotel mid-week because I =
had a sponsor for half the week. Your mileage may vary.


On Aug 23, 2011, at 10:24 AM, John C Klensin wrote:

> Being a little cynical, I do wonder if we would see a difference
> in meeting selection patterns if all IASA staff and IAOC members
> were required to stay in hotel or other rooms costing no more
> than, say, your USD 200 per night figure (including transport,
> if necessary, to and from the meeting site).  It might help to
> calibrate the pain level.  The idea is not realistic for a
> number of reasons, but might make an interesting
> thought-experiment.


--Apple-Mail-19-846187223
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MjQwNDQwMzZaMCMGCSqGSIb3DQEJ
BDEWBBSH1effHR4KScudtt3j8mSR7cE6ojCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAAAoGJpsq3eBwxWc31ROfDHLUXBte3+5uVism89ltZcT6SUW
PWttD0CefVa/+K+qrFs3R6QEsZZCuVLc0/leqbCe2dO7+PxkmGeJeijx+K2uLfSxdg9m1XQJYHFN
450LRUbrcCeEoiADauWDWnxYG1RVHD2yYPqj1WMIBOqNvfWhGlLjDuzLDt9MsssKu/+gafxUOwZE
jzsAh9N8tF4+isnNuI49cgR/2J4Rl4PrRgYM1Y4z2wA0TeUV8BORoahiFVV3SrFSfu25rnBFxtnW
utCYYEqTW+LyRU/xmgW3sdqZwMZC5BySqFcVVr2ojx+bHYDHUBVonE7ZZ1vj6vJToYoAAAAAAAA=

--Apple-Mail-19-846187223--

From glenzorn@gmail.com  Tue Aug 23 21:40:24 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA1021F8B4B for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 21:40:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJDYFQgxR79D for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 21:40:23 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3F80221F8B1A for <ietf@ietf.org>; Tue, 23 Aug 2011 21:40:23 -0700 (PDT)
Received: by gyf3 with SMTP id 3so749986gyf.31 for <ietf@ietf.org>; Tue, 23 Aug 2011 21:41:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=eAPZ16PlJFRepgBpCl1HcuSlEDVBySP/iOOfc9dY6J4=; b=U+79tZUCmUbsrG3tK3t/68k5ouls3mbfy6e8uWmFuE9Yk3v+iF2MC2o6lmz9SnG7bo Eau500jCDjSznHHDAFLL5NcWyWlWrvIgW+v9w7rx8LsUP069SJ2Xe9rIABe0Tq/XcDQ+ jIknOJYRoBUQKddvKC9Xh04AO612/WGKy98YA=
Received: by 10.146.135.12 with SMTP id i12mr4650730yad.33.1314160892076; Tue, 23 Aug 2011 21:41:32 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-122-122-148.revip2.asianet.co.th [124.122.122.148]) by mx.google.com with ESMTPS id g17sm576229ank.10.2011.08.23.21.41.29 (version=SSLv3 cipher=OTHER); Tue, 23 Aug 2011 21:41:31 -0700 (PDT)
Message-ID: <4E5480F6.4080607@gmail.com>
Date: Wed, 24 Aug 2011 11:41:26 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 04:40:24 -0000

On 8/24/2011 12:46 AM, Worley, Dale R (Dale) wrote:

>> From: Thomas Nadeau
>>
>> One would think that when the IETF negotiates the room block/fees,
>> that this could be done as well. After all we are in many cases,
>> booking a significant portion of the hotel in question in addition to
>> its conference facilities.
> 
> Speaking as someone who has never arranged a convention...  There must
> be some difficulty given the IETF's use of sponsors.  E.g., for the
> Maastricht meeting, we were sponsored by SIDN, a Netherlands company.
> This automatically restricted us to a fairly small number of venues,
> which is going to make it harder to get good terms when negotiating.

Speaking as one who has, there is no difficulty unless the sponsor
decides to create one (e.g., by treating the meeting as a recruiting
tool, perhaps hoping to impress prospective employees with the wonders
of the particular office park wasteland where their headquarters happens
to be located ;-).  Microsoft, for example, hosted a meeting in Orlando
and Cisco has, I believe, hosted or co-hosted meetings all over the world...

...

From glenzorn@gmail.com  Tue Aug 23 22:26:28 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9398B21F8BB5 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FcJseGMGpImL for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:26:28 -0700 (PDT)
Received: from mail-gx0-f194.google.com (mail-gx0-f194.google.com [209.85.161.194]) by ietfa.amsl.com (Postfix) with ESMTP id 018B221F8BB1 for <ietf@ietf.org>; Tue, 23 Aug 2011 22:26:27 -0700 (PDT)
Received: by gxk27 with SMTP id 27so113690gxk.1 for <ietf@ietf.org>; Tue, 23 Aug 2011 22:27:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=2YcEno20pewm7O2ZbLG9AFA4P5C4Bpv0Rpk9ZKYFjp4=; b=ah7ELTFgGiHASpQPrqx029DSQSwSYcxUMK9koPAqkqcaUM67FkVU4Z6PRKnG5Q42J5 3GLD1GlnLnAN5R5b4yg5RSqiqw8jIYeZTIL2zTYgy/iZdvp8bO9OnFGzlEq+43u3/x48 a7WZ6KFzBcCuL07dd4vUy+4XKWn7sp9dBniIM=
Received: by 10.151.99.17 with SMTP id b17mr1658324ybm.252.1314163657369; Tue, 23 Aug 2011 22:27:37 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-122-122-148.revip2.asianet.co.th [124.122.122.148]) by mx.google.com with ESMTPS id p34sm604828ann.17.2011.08.23.22.27.33 (version=SSLv3 cipher=OTHER); Tue, 23 Aug 2011 22:27:35 -0700 (PDT)
Message-ID: <4E548BC2.2080709@gmail.com>
Date: Wed, 24 Aug 2011 12:27:30 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com> <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com> <Pine.LNX.4.64.1108231125430.21813@egate.xpasc.com> <20110823203352.GC52234@shinkuro.com>
In-Reply-To: <20110823203352.GC52234@shinkuro.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 05:26:28 -0000

On 8/24/2011 3:33 AM, Andrew Sullivan wrote:

> On Tue, Aug 23, 2011 at 11:29:34AM -0700, David Morris wrote:
> 
>> For this to be a meaningful disccusion re. the success or lack there of,
>> we need to compare what we have vs. similar sized groups in the same 
>> season, etc. at the same venue.
> 
> _And_ having negotiated at the same time, as Ray pointed out already
> in this thread.  Every time one of these discussions comes up, people
> seem to forget that the negotiations are happening several years in
> advance of the actual event.  Agreements about the future almost
> always require the party buying to take some risk that they will be
> paying more than the going rate at the time the actual sale date
> arrives.  

This can be minimized, though, right?  Maybe the conference room rate
could be set at a percentage of the rack rate, for example.

> In the case of hotel agreements, the block negotiator takes
> some risk that there will be a lower price or otherwise better terms
> actually available at the time of the block being used.  The hotel
> takes some risk that the block negotiator is unable to deliver the
> actual room occupancy negotiated.  Each is making a bet.

Yes, but the total risk on the part of the hotel is that it will be in
the normal state of having empty rooms that need to be filled...

> 
> If you don't like the cancellation terms (or other terms of the bet),
> don't participate in it: don't make a reservation in the IETF block.

And I do, and have for some time now (since I have no corporate expense
account); this has the added benefit (from my POV, YMMV) of actually
_visiting_ Prague, Maastricht, etc. (as opposed to essentially shipping
myself air freight to a facility that could as easily be in Dallas or
(cringe) Minneapolis except that the people might look different or talk
funny, then shipping myself back again).

From john-ietf@jck.com  Tue Aug 23 22:34:47 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6672421F8BEC for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBninPx3Dbty for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:34:46 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 90E7821F8BAD for <ietf@ietf.org>; Tue, 23 Aug 2011 22:34:46 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qw67v-0007Cb-Ng; Wed, 24 Aug 2011 01:35:47 -0400
Date: Wed, 24 Aug 2011 01:35:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, SM <sm@resistor.net>
Subject: Re: Discussing a DISCUSS - down-refs in draft-ietf-yam-rfc4409bis-02
Message-ID: <C3C2137361CCDF9D51E66F83@PST.JCK.COM>
In-Reply-To: <tslei0beqgq.fsf@mit.edu>
References: <6.2.5.6.2.20110823112247.0b645658@elandnews.com> <tslei0beqgq.fsf@mit.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 05:34:47 -0000

--On Tuesday, August 23, 2011 18:02 -0400 Sam Hartman
<hartmans-ietf@mit.edu> wrote:

>>>>>> "SM" == SM  <sm@resistor.net> writes:
> 
>     SM> There is currently a DISCUSS for
> draft-ietf-yam-rfc4409bis-02:     SM> <process weenie="">
> 
>     SM> The IETF LC
>     SM>
> (https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=96
> 80&tid=1314107697)     SM> did not call out the downrefs to
> RFC 4954 and 5321.  There is no     SM> doubt in my mind that
> no one will object to these downrefs, but     SM> they need to
> be explicitly called out in the IETF LC.
>...
  
> Hey, I think I read RFC 4897 once.
> Someone's actually trying to use that? Who knew!
> 
> Seriously, section 3.1 of RFC 4897 makes it clear that an RFC
> 4897 downward reference does not need an RFC 3967-style
> comment in the IETF last call.  As best I can tell, this
> discuss should be cleared because The AD is confused about
> what BCP is being applied here.
> 
> Really this is one of those situations where we're all sitting
> around the table playing a nice game of "publish that doc" and
> people have to get out their copy of the IETF rules, the IETF
> rules erata and the IETF player's magazine articles with rules
> commentary and figure out what is going on.:-)

As someone else who read 4897 once or twice, and independent of
my role as co-editor of the draft in question,

+1.

    john





From glenzorn@gmail.com  Tue Aug 23 22:43:00 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2658E21F8BE7 for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tR4nZD+RrjiU for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:42:59 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9477721F8BDC for <ietf@ietf.org>; Tue, 23 Aug 2011 22:42:59 -0700 (PDT)
Received: by ywe9 with SMTP id 9so765225ywe.31 for <ietf@ietf.org>; Tue, 23 Aug 2011 22:44:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=pHUhQPKMP7VcYoT+8QwSgFlFnUSgqAscSfG8lqFhRuM=; b=nSUiMu3qr0s7Vo+7Oe6VfPACB2sapWvrrsWmy5A9sC8c5YOwHviPUbKP5vSvtZ5D94 VFfUdbej2zPi0B5j46S0rI9R/RLUzG/oefUYhLDnSAptWln69qmonooG8klRhSZbPFay FNiVen6hoolexGkoSrAjKSWATdCv72ZnJkyQU=
Received: by 10.150.47.12 with SMTP id u12mr4737286ybu.133.1314164646929; Tue, 23 Aug 2011 22:44:06 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-122-122-148.revip2.asianet.co.th [124.122.122.148]) by mx.google.com with ESMTPS id l14sm617520anl.8.2011.08.23.22.44.03 (version=SSLv3 cipher=OTHER); Tue, 23 Aug 2011 22:44:06 -0700 (PDT)
Message-ID: <4E548FA0.60506@gmail.com>
Date: Wed, 24 Aug 2011 12:44:00 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Hyatt Taipei cancellation policy?
References: <CA798673.37027%jason_livingood@cable.comcast.com> <4E542EBF.6080303@stpeter.im>
In-Reply-To: <4E542EBF.6080303@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 05:43:00 -0000

On 8/24/2011 5:50 AM, Peter Saint-Andre wrote:

...

> Come on, folks, let's be honest: all-in-one conference hotels, and
> hotels connected to conference centers, charge exorbitant amounts of
> money for the convenience of sleeping in close proximity to the meeting
> rooms. Thanks to tips from other cost-conscious IETFers, I was able to
> find hotels costing $100 (IETF 81) and $170 (IETF 82) a night cheaper
> than the official venue. Sure, I have to walk for five minutes to get
> back and forth to the meeting rooms, but that seems like a small price
> to pay. If you don't like the recommended hotels, vote with your feet.

Unfortunately, since the meeting fees are tied to the block occupancy
(via conference room charges, etc.), this puts us in a double-bind
situation: the smaller the block, the higher the other fees.  This is
the concern that I expressed during the plenary in QC, that because of
exorbitant hotel rates (and consequent lack of occupancy) the meeting
fees would themselves become exorbitant to compensate, the end result
being that major corporate support would be mandatory for attendants:
independents, academics and even employees of small companies need not
apply.  I hope we don't want to go there...

> 
> Peter
> 


From joelja@bogus.com  Tue Aug 23 22:54:14 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C894A21F8C0B for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIFMVWrDls1P for <ietf@ietfa.amsl.com>; Tue, 23 Aug 2011 22:54:14 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 38CA621F8BF6 for <ietf@ietf.org>; Tue, 23 Aug 2011 22:54:14 -0700 (PDT)
Received: from [192.168.1.171] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7O5tH2n033495 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Aug 2011 05:55:18 GMT (envelope-from joelja@bogus.com)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E548BC2.2080709@gmail.com>
Date: Tue, 23 Aug 2011 22:55:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F87C75D3-9964-4588-86B7-9FA88924F1FE@bogus.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com> <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com> <Pine.LNX.4.64.1108231125430.21813@egate.xpasc.com> <20110823203352.GC52234@shinkuro.com> <4E548BC2.2080709@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 24 Aug 2011 05:55:19 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 05:54:14 -0000

On Aug 23, 2011, at 10:27 PM, Glen Zorn wrote:

> On 8/24/2011 3:33 AM, Andrew Sullivan wrote:
>=20
>> On Tue, Aug 23, 2011 at 11:29:34AM -0700, David Morris wrote:
>>=20
>>> For this to be a meaningful disccusion re. the success or lack there =
of,
>>> we need to compare what we have vs. similar sized groups in the same=20=

>>> season, etc. at the same venue.
>>=20
>> _And_ having negotiated at the same time, as Ray pointed out already
>> in this thread.  Every time one of these discussions comes up, people
>> seem to forget that the negotiations are happening several years in
>> advance of the actual event.  Agreements about the future almost
>> always require the party buying to take some risk that they will be
>> paying more than the going rate at the time the actual sale date
>> arrives. =20
>=20
> This can be minimized, though, right?  Maybe the conference room rate
> could be set at a percentage of the rack rate, for example.

There are of course other exposures to be accounted for.

year over year the dollar buys a bit less than 10% less TWD than it did =
this time in 2010. while it is certainly could be done I don't think any =
of the participants bought dollar hedge contracts against the future =
cost of their hotel stay. the person arriving from geneva will pay about =
14% less then they would have a year ago. given taiwan had about 1% =
inflation over the same time scale it seems unlikely that their costs =
went down correspondingly.

>> In the case of hotel agreements, the block negotiator takes
>> some risk that there will be a lower price or otherwise better terms
>> actually available at the time of the block being used.  The hotel
>> takes some risk that the block negotiator is unable to deliver the
>> actual room occupancy negotiated.  Each is making a bet.
>=20
> Yes, but the total risk on the part of the hotel is that it will be in
> the normal state of having empty rooms that need to be filled...
>=20
>>=20
>> If you don't like the cancellation terms (or other terms of the bet),
>> don't participate in it: don't make a reservation in the IETF block.
>=20
> And I do, and have for some time now (since I have no corporate =
expense
> account); this has the added benefit (from my POV, YMMV) of actually
> _visiting_ Prague, Maastricht, etc. (as opposed to essentially =
shipping
> myself air freight to a facility that could as easily be in Dallas or
> (cringe) Minneapolis except that the people might look different or =
talk
> funny, then shipping myself back again).
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From christer.holmberg@ericsson.com  Wed Aug 24 00:51:54 2011
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 798CD21F8B25 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 00:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.553
X-Spam-Level: 
X-Spam-Status: No, score=-6.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eamQmQ5EUYp3 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 00:51:54 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id A9FCE21F8B20 for <ietf@ietf.org>; Wed, 24 Aug 2011 00:51:53 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-6f-4e54adde6d9b
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 4F.B1.20773.EDDA45E4; Wed, 24 Aug 2011 09:53:02 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.250]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Wed, 24 Aug 2011 09:53:02 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 24 Aug 2011 09:52:59 +0200
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: Acxh1AOYSOljlk8BSvqoYmtdbc1RfwAXYEcw
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852233A7F176@ESESSCMS0356.eemea.ericsson.se>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com> <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com> <Pine.LNX.4.64.1108231125430.21813@egate.xpasc.com> <20110823203352.GC52234@shinkuro.com>
In-Reply-To: <20110823203352.GC52234@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 07:51:54 -0000

...and, at least in this case, if you look at similar hotels (e.g. the Star=
wood properties) in the area, you'll find that even the current pre-book-no=
n-refundable-no-breakfast-in-some-cases-no-internet rates will be higher th=
an the rate offered to us. =20

There are also cheaper hotels, so it's all about having the benefits of sta=
ying at/very-close-to the meeting, or having to do some walk.

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
> Behalf Of Andrew Sullivan
> Sent: 23. elokuuta 2011 23:34
> To: ietf@ietf.org
> Subject: Re: Hyatt Taipei cancellation policy?
>=20
> On Tue, Aug 23, 2011 at 11:29:34AM -0700, David Morris wrote:
>=20
> > For this to be a meaningful disccusion re. the success or=20
> lack there=20
> > of, we need to compare what we have vs. similar sized groups in the=20
> > same season, etc. at the same venue.
>=20
> _And_ having negotiated at the same time, as Ray pointed out=20
> already in this thread.  Every time one of these discussions=20
> comes up, people seem to forget that the negotiations are=20
> happening several years in advance of the actual event. =20
> Agreements about the future almost always require the party=20
> buying to take some risk that they will be paying more than=20
> the going rate at the time the actual sale date arrives.  In=20
> the case of hotel agreements, the block negotiator takes some=20
> risk that there will be a lower price or otherwise better=20
> terms actually available at the time of the block being used.=20
>  The hotel takes some risk that the block negotiator is=20
> unable to deliver the actual room occupancy negotiated.  Each=20
> is making a bet. =20
>=20
> If you don't like the cancellation terms (or other terms of=20
> the bet), don't participate in it: don't make a reservation=20
> in the IETF block.
>=20
> A
>=20
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> =

From moore@network-heretics.com  Wed Aug 24 03:52:35 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C17321F8B12 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 03:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1s2Jf+4eCQ2v for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 03:52:34 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB9E21F8AF1 for <ietf@ietf.org>; Wed, 24 Aug 2011 03:52:34 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id EF84820DE7; Wed, 24 Aug 2011 06:53:43 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 24 Aug 2011 06:53:43 -0400
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=5cdR9/5oQgdXaCGRoV156jJPtPM=; b=D8 QoKtd8qkX9PpqUjH++1RyFfe9sioPsKVeYmTS3vg8QQrzjZT2VniU5spkORYS/99 L9MV3cMI86t/QXN0tKnt0jX0ecU3qVK0lYuv7w6+T6pMwbcykbmPYi6cnXkTWNp2 K3Hr2CnnDtEym1qoDkQJz7qPwcS8fwxLMa8vyPChk=
X-Sasl-enc: z/mxMbRXoVPVeqth4l5g9PfuJBYs5BONkdCZ/dV0WvyT 1314183223
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 1ED4F920069; Wed, 24 Aug 2011 06:53:43 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E548FA0.60506@gmail.com>
Date: Wed, 24 Aug 2011 06:53:19 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <28AC8833-0D74-45F4-B92E-A21B93A9CEFC@network-heretics.com>
References: <CA798673.37027%jason_livingood@cable.comcast.com> <4E542EBF.6080303@stpeter.im> <4E548FA0.60506@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 10:52:35 -0000

On Aug 24, 2011, at 1:44 AM, Glen Zorn wrote:

> Unfortunately, since the meeting fees are tied to the block occupancy
> (via conference room charges, etc.), this puts us in a double-bind
> situation: the smaller the block, the higher the other fees.  This is
> the concern that I expressed during the plenary in QC, that because of
> exorbitant hotel rates (and consequent lack of occupancy) the meeting
> fees would themselves become exorbitant to compensate, the end result
> being that major corporate support would be mandatory for attendants:
> independents, academics and even employees of small companies need not
> apply.  I hope we don't want to go there...

we're pretty close to there already.

Keith


From daedulus@btconnect.com  Wed Aug 24 04:18:42 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6482521F8AD6 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 04:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.963
X-Spam-Level: 
X-Spam-Status: No, score=-1.963 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSr+fp2yDpNh for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 04:18:41 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by ietfa.amsl.com (Postfix) with ESMTP id 6A26121F8AD3 for <ietf@ietf.org>; Wed, 24 Aug 2011 04:18:40 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2bthomr14.btconnect.com with SMTP id EBS43307; Wed, 24 Aug 2011 12:14:46 +0100 (BST)
Message-ID: <00ad01cc6246$23e143a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "George, Wesley" <wesley.george@twcable.com>, <ietf@ietf.org>
References: <34E4F50CAFA10349A41E0756550084FB0D5571BD@PRVPEXVS04.corp.twcable.com>
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6Support Required for all IP-capable nodes) to Proposed Standard
Date: Wed, 24 Aug 2011 12:10:59 +0200
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.4E54DD25.004A, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.24.102414:17:7.944, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, __HAS_HTML, HTML_NO_HTTP, BODY_SIZE_4000_4999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr14.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4E54DD27.0194,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: draft-ietf-intarea-ipv6-required@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 11:18:42 -0000

<tp>inline</tp>
----- Original Message -----
From: "George, Wesley" <wesley.george@twcable.com>
To: <ietf@ietf.org>; "t.petch" <daedulus@btconnect.com>
Cc: <draft-ietf-intarea-ipv6-required@tools.ietf.org>
Sent: Monday, August 22, 2011 7:12 PM

From: "t.petch" <daedulus@btconnect.com>
To: <ietf@ietf.org>
Reply-to: daedulus@btconnect.com

I find this document utterly bizarre and think it would seriously damage the
Internet to publish it.
____________
WEG] well, I find the vehemence of your statement a bit bizarre, but I would
like to address your concerns if possible. Please explain how a recommendation
to support IPv6 is going to "seriously damage the internet."

The idea that ipv6 should be regarded as normal, as of equal standing to ipv4 is
fine, the sort of statement that the IAB should make, or have made, as an RFC or
in some other form.
____________
WEG] Agree. IETF has remained version-agnostic for some time now. But they have
not made anything like the statement that this draft makes, which is that IPv6
will be necessary because IPv4 is going to have difficulties in continuing to
provide the same level of service post-exhaustion. In the authors' opinions, it
is long overdue as guidance to implementers, so we made the statement in the
hopes that we'd reach consensus, which in a way is a stronger statement than
something coming out of the IAB anyway.

But this I-D claims
" Updates [RFC1122] to clarify that this document, especially in
section 3, primarily discusses IPv4 where it uses the more generic
term "IP" and is no longer a complete definition of "IP" or the
Internet Protocol suite by itself. "

IPv4 is a phenomenal success, and RFC1122 is a key part of that. IPv4 was a
confused jumble, as IPv6 is now, and RFC1122, with another two or so I-Ds, cut
through the cruft and rendered it usable. IPv6 desparately needs an equivalent
to RFC1122, as a trawl of the v6ops list archives shows, and clearly this I-D is
never going to be it, but claiming that this I-D provides an update to RFC1122,
coupled
with its title, gives the message that there is not going to be such an I-D;
IPv6 will remain a confused jumble (and so is unlikely ever to emulate the
success of IPv4).
___________
WEG] Ignoring for a moment the commentary on the state of the IPv6 RFCs vs IPv4,
and the need for a "rosetta stone," I'll note that the choice to update several
IP(v4) RFCs was something that has been controversial based on Intarea LC
feedback as well, but we believed necessary to provide the linkage between the
two. Honestly, I would have rather seen IETF issue formal updates to the
existing "IP" RFCs to include IPv6, rather than building an entirely parallel
set of documents, but here we are, so we made a choice. It would be helpful to
understand whether your resistance to this document is solely due to the
decision to have this be standards track, to update several existing RFCs, or
both vs the general recommendation that implementers should support IPv6.

<tp>
A general recommendation for implementers (and operators?) to support IPv6
is fine.  The part I am objecting to is having a standards track document
claiming to
update documents such as RFC1122.

Someone attracted by the title, and then seeing what the actual updates are to
RFC1122 etc, will, I fear, regard this as ridiculous, and will think that if
there is no
real update to RFC1122, or a fresh document for IPv6, then the IETF cannot be
serious about IPv6.  I believe that an IPv6 equivalent to RFC1122 etc is needed
now, and agree with Brian that
"draft-ietf-6man-node-req-bis is a step on the way."
but only a step.

Tom Petch
</tp>

While I believe that removing the update references will reduce the impact of
the document, I am not opposed to issuing a new version of the document that
does so and keeps to simply documenting the requirements for IPv6 support if
consensus supports that action.

Thanks
Wes George


From rpelletier@isoc.org  Wed Aug 24 05:17:19 2011
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D957921F8B30 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 05:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.419
X-Spam-Level: 
X-Spam-Status: No, score=-103.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tRjj6KRU5n3q for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 05:17:19 -0700 (PDT)
Received: from smtp207.iad.emailsrvr.com (smtp207.iad.emailsrvr.com [207.97.245.207]) by ietfa.amsl.com (Postfix) with ESMTP id 25F0E21F8B2D for <ietf@ietf.org>; Wed, 24 Aug 2011 05:17:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp30.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id E2D982091C; Wed, 24 Aug 2011 08:18:26 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp30.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id B439F20920;  Wed, 24 Aug 2011 08:18:26 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <66998320DD3FCC5628E32634@PST.JCK.COM>
Date: Wed, 24 Aug 2011 08:18:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 12:17:20 -0000

On Aug 23, 2011, at 1:34 AM, John C Klensin wrote:

>=20
>=20
> --On Monday, August 22, 2011 20:16 -0400 Ray Pelletier
> <rpelletier@isoc.org> wrote:
>=20
>> ...
>> As for the rates, they are high.  Taiwan is expensive,
>> particularly given that the hotels know what our options are
>> when we book the TICC.  The Hyatt knew that foreign visitors
>> needed to use the Hyatt as headquarters and charged
>> accordingly.  Since the time of our site visit, 2 new hotels
>> have been constructed in the vicinity of the TICC (Le Meridien
>> and W), which may provide more competition for Hyatt in these
>> circumstances.  At the time we were working on this event,
>> there were no acceptable options.
>=20
> Ray,
>=20
> I know you want to find sponsors and go where the sponsors want
> to go.  I accept the explanation that you negotiated as hard as
> you could for both room rates and cancellation policies.  But I
> have to wonder, especially in the light of Lixia's observation
> about the US Govt rate (which, internationally, is often a
> pretty good measure for the higher end of a reasonable rate in a
> given city), whether there is a stopping rule.  We were told in
> Quebec that you had given up on one Southeast Asian city because
> rooms would have cost over USD 300 a night. I don't remember
> hearing about a sponsor there.  What looks like USD 275 net is
> not all that much less than USD 300, especially if the dollar
> continues to sink.
>=20
> So, if you had a sponsor for a future meeting at that other
> location, would an estimated USD 300 be acceptable?  USD 350?
>=20
> I obviously don't have all of the information available to me
> that you and the IAOC do, but it seems to be there is always
> another alternative.   If there are no local ones, that
> alternative is usually described as "just say no and go
> elsewhere".  What I'm trying to understand, mostly for the
> future and with the understanding that it is presumably much too
> late for Taipei and the several following meetings, is whether
> you would ever consider that an option for a meeting for which
> you have a sponsor if you hold it in a particular place or if
> you and the IAOC really believe there is no alternative under
> those circumstances.

The IAOC has adopted a program of booking venues 3 years in advance. =20
This will open up more venue choices as we found that even 2 years out =
we were
shut out of places.

The other effect is that these venue decisions will be made for the most =
part without
sponsors and sponsors driving meeting locations.  Typically sponsors =
become=20
engaged 18 or fewer months before a meeting, probably for budgetary =
reasons.

Many places they just don't need our business, and don't budge from =
their $300+USD
guest room rates, or their $350k + cost for meeting space.  We turn =
elsewhere. =20

The meeting in Paris was going to be in another major European city for =
which we were=20
actively engaged in a discussion with a Host.  However, the venue was =
outside the city
center, so the plug was pulled and moved to Paris - where we still do =
not have a Host.
Sponsors welcome! =20

The points are that the IAOC is not going to select a poor venue because =
it may have a=20
sponsor; nor a $300+ USD guest room rate for the headquarters hotel. =20

Ray



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


From moore@network-heretics.com  Wed Aug 24 05:35:53 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9297E21F856B; Wed, 24 Aug 2011 05:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.457
X-Spam-Level: 
X-Spam-Status: No, score=-3.457 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1u+bdcfhW99E; Wed, 24 Aug 2011 05:35:53 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id F0C1721F8569; Wed, 24 Aug 2011 05:35:52 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 735B320882; Wed, 24 Aug 2011 08:37:03 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 24 Aug 2011 08:37:03 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=yVS zsicsZ5/NyQpoD0zinIeD6Zg=; b=qGn0JFDpPY+O01PLaZWmEWwgQUcL2IWBUhq UvpKg+qfSbttfluOX6Ofg1G6yi36AdUOxiTZbEFDhR25y3/ly7GwXM+fyk+pPiK4 uJ0DA1H0j7n3gpZibBTCOr8Nc/DbIh4VlX6ROlnrXVXxZ4sH4ezvUsS2LSk6L7JM HJmWCXEI=
X-Sasl-enc: 512P6UNj2rz6o479kvfsEnebI+kbX8Eeu/ZOwNJu0Orm 1314189422
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2E156920075; Wed, 24 Aug 2011 08:37:02 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-7-874749155
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>
Date: Wed, 24 Aug 2011 08:36:38 -0400
Message-Id: <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>
To: Ray Pelletier <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john-ietf@jck.com>, Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 12:35:53 -0000

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

$300/night is far too high a ceiling for a guest room rate.  A more =
reasonable ceiling would be in the ballpark of $150.

On Aug 24, 2011, at 8:18 AM, Ray Pelletier wrote:

> The points are that the IAOC is not going to select a poor venue =
because it may have a=20
> sponsor; nor a $300+ USD guest room rate for the headquarters hotel. =20=



--Apple-Mail-7-874749155
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; =
">$300/night is far too high a ceiling for a guest room rate. &nbsp;A =
more reasonable ceiling would be in the ballpark of =
$150.<div><br><div><div>On Aug 24, 2011, at 8:18 AM, Ray Pelletier =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">The points =
are that the IAOC is not going to select a poor venue because it may =
have a<span class=3D"Apple-converted-space">&nbsp;</span><br>sponsor; =
nor a $300+ USD guest room rate for the headquarters hotel. =
&nbsp;<br></span></blockquote></div><br></div></body></html>=

--Apple-Mail-7-874749155--

From agmalis@gmail.com  Wed Aug 24 06:27:30 2011
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F9E21F889A; Wed, 24 Aug 2011 06:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id taas7pcNJScS; Wed, 24 Aug 2011 06:27:30 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id E43C221F8AF0; Wed, 24 Aug 2011 06:27:29 -0700 (PDT)
Received: by qyk34 with SMTP id 34so2650862qyk.10 for <multiple recipients>; Wed, 24 Aug 2011 06:28:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=qn9RGxBQIFTYPSrtLCYX7EWC4stpitHLnDNNEKfVvGo=; b=KUZMR6o04Q58luVyPO0b39fAT3sccQYwVX3BS+2iMSIGoennXYWCAsPaNBm4jVupPk TJFkZZt3Ba8HykbjoWNkOVw28J9lJf6Yn6DWZ3eme+/ExsZXCRjoYGOHlQ79lHn30yJh CmDRjx0CIp1hpSAlmzSK3ZSL4onSJQF948KZ8=
Received: by 10.229.63.164 with SMTP id b36mr736503qci.65.1314192519091; Wed, 24 Aug 2011 06:28:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.162.12 with HTTP; Wed, 24 Aug 2011 06:28:19 -0700 (PDT)
In-Reply-To: <DC351D99C7573A54509F777F@PST.JCK.COM>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <4E533D39.5070606@cisco.com> <DC351D99C7573A54509F777F@PST.JCK.COM>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 24 Aug 2011 09:28:19 -0400
Message-ID: <CAA=duU1a-azDAHdv7KBBR__NHJtOcgfU11Kb_fxdV=oT6jnNRA@mail.gmail.com>
Subject: Re: Experiment for different schedule for Friday
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 13:27:30 -0000

+1 for me as well for either proposed new schedule.

On Tue, Aug 23, 2011 at 2:04 AM, John C Klensin <john-ietf@jck.com> wrote:
> +1. =A0I could also happily live with the alternate, more
> compressed, schedule -- I think both are preferable to the
> schedule used in Quebec and earlier.
>
> =A0 john
>
>
> --On Tuesday, August 23, 2011 07:40 +0200 Eliot Lear
> <lear@cisco.com> wrote:
>
>>
>>
>> On 8/22/11 11:24 PM, IETF Chair wrote:
>>> The IESG is considering a different schedule for the Friday
>>> of IETF 82. =A0The IESG is seeking your input on these
>>> potential changes.
>>>
>>> The IESG would like to try a schedule experiment on Friday,
>>> using this schedule:
>>>
>>> =A09:00 AM - 11:00 AM - Session I
>>> 11:00 AM - 11:20 AM - Room Change and Cookie Break
>>> 11:20 AM - 12:20 PM - Session II
>>> 12:10 PM - 12:30 PM - Room Change Break
>>> 12:30 PM - 13:30 PM - Session III
>>>
>>> The IESG has already consulted with the IAOC because of the
>>> cost associated with the additional food and beverage break.
>>> The IAOC believes that the additional cost can be managed
>>> without raising the meeting fee.
>>
>> I think this is a good experiment to run as proposed.
>
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From wesley.george@twcable.com  Wed Aug 24 06:30:00 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F29721F8B57; Wed, 24 Aug 2011 06:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.334
X-Spam-Level: *
X-Spam-Status: No, score=1.334 tagged_above=-999 required=5 tests=[AWL=-1.104,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, MANGLED_YOUR=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id soAS71lKm9+i; Wed, 24 Aug 2011 06:29:57 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 7EAE521F8AF0; Wed, 24 Aug 2011 06:29:57 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,421,1309752000";  d="scan'208,217";a="265651217"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 24 Aug 2011 09:29:16 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Wed, 24 Aug 2011 09:31:07 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Keith Moore <moore@network-heretics.com>, Ray Pelletier <rpelletier@isoc.org>
Date: Wed, 24 Aug 2011 09:31:06 -0400
Subject: IAOC, travel and hotel prices (was RE: Hyatt Taipei cancellation policy?)
Thread-Topic: IAOC, travel and hotel prices (was RE: Hyatt Taipei cancellation policy?)
Thread-Index: AcxiWpFIgjttaZoDTU+NFWI4bGbEOAABigkA
Message-ID: <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>
In-Reply-To: <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.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_34E4F50CAFA10349A41E0756550084FB0D557960PRVPEXVS04corpt_"
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 13:30:00 -0000

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

I've been watching this discussion across several attendee lists, plenaries=
, etc and it appears that we have a routing loop.

Perhaps it's time for those who seem most concerned about this to author a =
BCP draft regarding IETF meeting venue and hotel selection policies that ad=
dresses this, so that IAOC has a bit clearer instructions and a documented =
policy based on community consensus, rather than this discussion continuing=
 to come up every couple of meetings, and the general response from the IAO=
C being "this is hard, we're doing the best we can... [example, explanation=
]"
Not to say that I doubt the intentions or efforts of any of the IAOC folks =
past or present, but the theme I keep seeing in these discussions is a requ=
est for both transparency and price sensitivity, and I'm not sure that the =
feedback is being acknowledged so much as it is being treated as a request =
for explanation of the extenuating circumstances.

It may also be advisable for the IAOC to start asking a few questions (via =
survey, for example):

1)      What (if any) guidelines do(es) you(r company) follow for allowable=
 hotel costs?

2)      Would you prefer to subsidize the cost of the meeting venue with th=
e cost of the hotel room, or via higher registration fees (or evenly split)=
?

3)      Would you prefer the meetings to center on a few locations and nego=
tiate an extremely good deal for repeat attendance (e.g. OFC/NFOEC, etc).

a.       Indefinitely rotate between the same 3 locations?

b.      Rotate on a 2 year basis (6 different locations)

c.       Rotate on a 3 year basis (9 different locations)

d.      Option a, but pick new venues every 2 or 3 years

e.      Status quo (venues completely variable)
Additional questions about air travel and mass transit (the other perennial=
 travel topics) might also be a good idea. Do it every year, or every 2 yea=
rs or after every meeting when the previous meeting (good and bad) is still=
 fresh in everyone's mind.

Thanks
Wes George

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Kei=
th Moore
Sent: Wednesday, August 24, 2011 8:37 AM
To: Ray Pelletier
Cc: John C Klensin; Secretariat IETF; IETF-Discussion list; Lixia Zhang
Subject: Re: Hyatt Taipei cancellation policy?

$300/night is far too high a ceiling for a guest room rate.  A more reasona=
ble ceiling would be in the ballpark of $150.

On Aug 24, 2011, at 8:18 AM, Ray Pelletier wrote:


The points are that the IAOC is not going to select a poor venue because it=
 may have a
sponsor; nor a $300+ USD guest room rate for the headquarters hotel.



________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:645279531;
	mso-list-type:hybrid;
	mso-list-template-ids:-1463932110 67698705 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
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=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: bre=
ak-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I&#8217;ve been watching =
this discussion across several attendee lists, plenaries, etc and it appear=
s that we have a routing loop.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Perhaps it&#8217;s time f=
or those who seem most concerned about this to author a BCP draft regarding=
 IETF meeting venue and hotel selection policies that addresses
 this, so that IAOC has a bit clearer instructions and a documented policy =
based on community consensus, rather than this discussion continuing to com=
e up every couple of meetings, and the general response from the IAOC being=
 &#8220;this is hard, we&#8217;re doing the
 best we can&#8230; [example, explanation]&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Not to say that I doubt t=
he intentions or efforts of any of the IAOC folks past or present, but the =
theme I keep seeing in these discussions is a request for
 both transparency and price sensitivity, and I&#8217;m not sure that the f=
eedback is being acknowledged so much as it is being treated as a request f=
or explanation of the extenuating circumstances.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">It may also be advisable =
for the IAOC to start asking a few questions (via survey, for example):<o:p=
></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">1)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">What (if any) gui=
delines do(es) you(r company) follow for allowable hotel costs?<o:p></o:p><=
/span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">2)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Would you prefer =
to subsidize the cost of the meeting venue with the cost of the hotel room,=
 or via higher registration fees (or evenly split)?<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">3)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Would you prefer =
the meetings to center on a few locations and negotiate an extremely good d=
eal for repeat attendance (e.g. OFC/NFOEC, etc).
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">a.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Indefinitely rota=
te between the same 3 locations?<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">b.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Rotate on a 2 yea=
r basis (6 different locations)<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">c.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Rotate on a 3 yea=
r basis (9 different locations)<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">d.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Option a, but pic=
k new venues every 2 or 3 years<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-list:Ign=
ore">e.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Status quo (venue=
s completely variable)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Additional questions abou=
t air travel and mass transit (the other perennial travel topics) might als=
o be a good idea. Do it every year, or every 2 years or
 after every meeting when the previous meeting (good and bad) is still fres=
h in everyone&#8217;s mind.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Wes George</span><span st=
yle=3D"font-size:9.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;;color:#7F7F7F"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ietf-bou=
nces@ietf.org [mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Keith Moore<br>
<b>Sent:</b> Wednesday, August 24, 2011 8:37 AM<br>
<b>To:</b> Ray Pelletier<br>
<b>Cc:</b> John C Klensin; Secretariat IETF; IETF-Discussion list; Lixia Zh=
ang<br>
<b>Subject:</b> Re: Hyatt Taipei cancellation policy?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">$300/night is far too high a ceiling for a guest roo=
m rate. &nbsp;A more reasonable ceiling would be in the ballpark of $150.<o=
:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On Aug 24, 2011, at 8:18 AM, Ray Pelletier wrote:<o:=
p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:13.5pt;font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">The =
points are that the IAOC is not going to select a poor venue because it may=
 have a</span></span><span class=3D"apple-converted-space"><span style=3D"f=
ont-size:13.5pt;font-family:&quot;Helvetica&quot;,&quot;sans-serif&quot;">&=
nbsp;</span></span><span style=3D"font-size:13.5pt;font-family:&quot;Helvet=
ica&quot;,&quot;sans-serif&quot;"><br>
<span class=3D"apple-style-span">sponsor; nor a $300&#43; USD guest room ra=
te for the headquarters hotel. &nbsp;</span><br>
<br>
</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_34E4F50CAFA10349A41E0756550084FB0D557960PRVPEXVS04corpt_--

From wesley.george@twcable.com  Wed Aug 24 06:33:53 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5774321F8B66 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 06:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level: 
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcOOtw7YyChq for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 06:33:51 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 1B58A21F8B5E for <ietf@ietf.org>; Wed, 24 Aug 2011 06:33:51 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,421,1309752000";  d="scan'208,217";a="265652781"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 24 Aug 2011 09:33:10 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Wed, 24 Aug 2011 09:35:01 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Keith Moore <moore@network-heretics.com>, Ray Pelletier <rpelletier@isoc.org>
Date: Wed, 24 Aug 2011 09:34:58 -0400
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: AcxiWpFIgjttaZoDTU+NFWI4bGbEOAAAgH4g
Message-ID: <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>
In-Reply-To: <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.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_34E4F50CAFA10349A41E0756550084FB0D55796BPRVPEXVS04corpt_"
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 13:33:53 -0000

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


From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Kei=
th Moore
Sent: Wednesday, August 24, 2011 8:37 AM
To: Ray Pelletier
Cc: John C Klensin; Secretariat IETF; IETF-Discussion list; Lixia Zhang
Subject: Re: Hyatt Taipei cancellation policy?

$300/night is far too high a ceiling for a guest room rate.  A more reasona=
ble ceiling would be in the ballpark of $150.

I don't understand why we keep throwing around hard and fast dollar figures=
. Every person, whether paying their own way or using a corporate expense a=
ccount is going to have a different view of what is ok vs what is unaccepta=
bly high, and that may or may not line up with the market rate reality of t=
he actual location chosen. As others have pointed out in the past, the only=
 limit that would make sense is to use something like the US gov't max trav=
el rate guidelines, which are indexed to things like USD value vs. local cu=
rrency, average cost by location, etc. We would likely need a percentage mu=
ltiplier to compensate for the fact that we ask for breakfast, internet ser=
vice, and conference fees to be waived in lieu of a cheaper hotel rate, but=
 I think that's a reasonable rule of thumb. If there are alternative source=
s for the same data from EU or APAC government sources, they could also be =
used, but lots of folks already know about the US gov ones.
US domestic rates are here: http://www.gsa.gov/portal/category/21287
International ones here: http://aoprals.state.gov/content.asp?content_id=3D=
184&menu_id=3D78

If this becomes the stated policy, it makes available the negotiation tacti=
c to note that "we have a lot of members who follow the guidelines set fort=
h here as far as how much they are allowed to spend per night for a hotel, =
if you insist on exceeding this by more than X%, we'll be forced to go else=
where. "

Wes George

________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0D55796BPRVPEXVS04corpt_
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:"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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:645279531;
	mso-list-type:hybrid;
	mso-list-template-ids:-1463932110 67698705 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
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=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: bre=
ak-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><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=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ietf-bou=
nces@ietf.org [mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Keith Moore<br>
<b>Sent:</b> Wednesday, August 24, 2011 8:37 AM<br>
<b>To:</b> Ray Pelletier<br>
<b>Cc:</b> John C Klensin; Secretariat IETF; IETF-Discussion list; Lixia Zh=
ang<br>
<b>Subject:</b> Re: Hyatt Taipei cancellation policy?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">$300/night is far too high a ceiling for a guest roo=
m rate. &nbsp;A more reasonable ceiling would be in the ballpark of $150.<o=
:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I don&#8217;t understa=
nd why we keep throwing around hard and fast dollar figures. Every person, =
whether paying their own way or using a corporate expense account is going =
to have a different view of what is ok vs
 what is unacceptably high, and that may or may not line up with the market=
 rate reality of the actual location chosen. As others have pointed out in =
the past, the only limit that would make sense is to use something like the=
 US gov&#8217;t max travel rate guidelines,
 which are indexed to things like USD value vs. local currency, average cos=
t by location, etc. We would likely need a percentage multiplier to compens=
ate for the fact that we ask for breakfast, internet service, and conferenc=
e fees to be waived in lieu of a
 cheaper hotel rate, but I think that&#8217;s a reasonable rule of thumb. I=
f there are alternative sources for the same data from EU or APAC governmen=
t sources, they could also be used, but lots of folks already know about th=
e US gov ones.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">US domestic rates are her=
e:
</span><a href=3D"http://www.gsa.gov/portal/category/21287">http://www.gsa.=
gov/portal/category/21287</a><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span><=
/p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">International ones here:
</span><a href=3D"http://aoprals.state.gov/content.asp?content_id=3D184&amp=
;menu_id=3D78">http://aoprals.state.gov/content.asp?content_id=3D184&amp;me=
nu_id=3D78</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If this becomes the state=
d policy, it makes available the negotiation tactic to note that &#8220;we =
have a lot of members who follow the guidelines set forth here
 as far as how much they are allowed to spend per night for a hotel, if you=
 insist on exceeding this by more than X%, we&#8217;ll be forced to go else=
where. &#8220;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Wes George<o:p></o:p></sp=
an></p>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_34E4F50CAFA10349A41E0756550084FB0D55796BPRVPEXVS04corpt_--

From fred@cisco.com  Wed Aug 24 07:26:51 2011
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C9C21F8AEC; Wed, 24 Aug 2011 07:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.816
X-Spam-Level: 
X-Spam-Status: No, score=-102.816 tagged_above=-999 required=5 tests=[AWL=-0.217, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HK+S9LBbgbKu; Wed, 24 Aug 2011 07:26:51 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id CF7E421F8AD3; Wed, 24 Aug 2011 07:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2929; q=dns/txt; s=iport; t=1314196082; x=1315405682; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=0Mo0J8thW7zVh+oongnVLIDcLETarzxPs2YPJpxdN9E=; b=fRdZ/rKFv7RVl2PVJsLUcEwE+kQYbEo16V8p1F8yOjAuYiXdpCTEvQ9m nskWos+GvphqHJidIurnj/3qVGdUZbygy03D4hNLuIabEw2s8m4VFzRJ2 jNSNMIhWlIE28VJ+4056gZfuhb7u+IbKSjgXt2P3IzeAfcj4TPN7dUCoj s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANYJVU6rRDoI/2dsb2JhbABCp3d3gUABAQEBAgESASc/BQsLGC5XBhwZh08EnTEBnzmFal8Eh2GLOIUNjA4
X-IronPort-AV: E=Sophos;i="4.68,275,1312156800"; d="scan'208";a="16061295"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-8.cisco.com with ESMTP; 24 Aug 2011 14:28:01 +0000
Received: from Freds-Computer.local (sjc-vpn5-154.cisco.com [10.21.88.154]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7OES0nT017609; Wed, 24 Aug 2011 14:28:00 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 24 Aug 2011 07:28:00 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 24 Aug 2011 07:28:00 -0700
Subject: Re: Agenda known in advance? was Re: Experiment for different schedule for Friday
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <5B58B51A-FDD0-40DC-8F29-AAEAEDC4E202@ietf.org>
Date: Wed, 24 Aug 2011 07:27:45 -0700
Message-Id: <01E03025-6D41-4B04-BEC8-283E40FBE509@cisco.com>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <1314094107.1965.16.camel@shane-desktop> <5B58B51A-FDD0-40DC-8F29-AAEAEDC4E202@ietf.org>
To: IETF Chair <chair@ietf.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 14:26:51 -0000

On Aug 23, 2011, at 6:48 AM, IETF Chair wrote:

> The important dates page for the meeting =
<http://www.ietf.org/meeting/cutoff-dates-2011.html#IETF82> shows a date =
for the draft agenda and a date for the final agenda.  We try very hard =
to make no changes after the final agenda date.  Sometimes changes are =
unavoidable because the Area Directors learn about WG-specific details =
that cause conflicts.  That said, we do our best to keep to the final =
agenda.

To my way of thinking, that's the key bit. That said, I could wish that =
were a week earlier than 10/21. I am planning November travel now, and =
expect it will include visits to Beijing, Hong Kong, and Singapore =
simply because I am in the region and people are making those requests. =
Hence, I expect to leave home 29 October. Company policy wants me to =
have hotels and flights sorted out two weeks earlier. So I will assume I =
have a Friday meeting, and if I don't I'll make the time available to my =
local sales people.

On Aug 22, 2011, at 2:24 PM, IETF Chair wrote:
> 9:00 AM - 11:00 AM - Session I
> 11:00 AM - 11:20 AM - Room Change and Cookie Break
> 11:20 AM - 12:20 PM - Session II
> 12:10 PM - 12:30 PM - Room Change Break
> 12:30 PM - 13:30 PM - Session III

For those flying to Japan, the last flight leaves around 2:30, but most =
flights are late morning
     http://www.hipmunk.com/#!TPE_NRT,Nov18
This does help those going to Beijing:
     http://www.hipmunk.com/#!TPE_PEK,Nov18
Hong Kong is of course every hour: =
http://www.hipmunk.com/#!TPE_HKG,Nov18
The change does help those going to Singapore and Sydney:
     http://www.hipmunk.com/#!TPE_SIN,Nov18
     http://www.hipmunk.com/#!TPE_SYD,Nov18

So there will be some locals and relatively-locals that can make the =
afternoon flight home, and more power to them. My guess is that, like =
me, anyone from Europe or North America who thinks they *might* have a =
meeting on Friday will be planning a flight home Saturday =
(http://www.hipmunk.com/#!TPE_SFO,Nov18). If I'm flying Saturday, =
shifting meetings by a couple of hours on Friday doesn't make much =
difference.=20

We have a discussion of this topic every IETF meeting, and every IETF =
meeting there is a lot of moaning and groaning about flights home. My =
perspective: we all want to go home, and the trade-off I just described =
happens - it just happens to different groups each time. We don't have =
enough time in the week to avoid doing something on Friday. We all wind =
up with Friday meetings - for myself, in the past several years, more =
often than not. So the only meetings I can actually plan to fly home =
from on Friday are meetings on the North American west coast - even the =
east coast usually means I'm out too late to make the flight home.

Get over it. Publish the agenda, and if that means we have to fly home =
Saturday, whatever.=

From ajs@anvilwalrusden.com  Wed Aug 24 07:33:34 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E81F21F8B36 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 07:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UU4BHdd6j4rD for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 07:33:34 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 2AABB21F8ABE for <ietf@ietf.org>; Wed, 24 Aug 2011 07:33:34 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 6062C1ECB41D for <ietf@ietf.org>; Wed, 24 Aug 2011 14:34:45 +0000 (UTC)
Date: Wed, 24 Aug 2011 10:34:42 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
Message-ID: <20110824143441.GF53261@shinkuro.com>
References: <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org> <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com> <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <88EADA27-843D-401F-A99C-7E4562E06FD4@lucidvision.com> <Pine.LNX.4.64.1108231125430.21813@egate.xpasc.com> <20110823203352.GC52234@shinkuro.com> <4E548BC2.2080709@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E548BC2.2080709@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 14:33:34 -0000

On Wed, Aug 24, 2011 at 12:27:30PM +0700, Glen Zorn wrote:

> > advance of the actual event.  Agreements about the future almost
> > always require the party buying to take some risk that they will be
> > paying more than the going rate at the time the actual sale date
> > arrives.  
> 
> This can be minimized, though, right?  Maybe the conference room rate
> could be set at a percentage of the rack rate, for example.

I totally fail to see how that's going to help.

IAOC: "We want a rate at about $150."

Hotel: "We charge $300 a night."

or 

IAOC: "We want a rate at about $150."

Hotel: "We can give you a % of rack rate."

IAOC: "What is the rack rate?"

Hotel: "$1000/night."

IAOC: "We want a rate of 15% of rack rate."

Hotel: "We will not go below 30%."

Worse, the second case requires that the IAOC also negotiate a freeze
in the rack rate.  Every business problem can also be solved by
another layer of indirection.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From manav.bhatia@alcatel-lucent.com  Wed Aug 24 07:38:39 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE0B21F8B52; Wed, 24 Aug 2011 07:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.245
X-Spam-Level: 
X-Spam-Status: No, score=-6.245 tagged_above=-999 required=5 tests=[AWL=0.354,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AS0ulxgtOLwI; Wed, 24 Aug 2011 07:38:38 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 646C421F8B38; Wed, 24 Aug 2011 07:38:38 -0700 (PDT)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p7OEdiS3011695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 24 Aug 2011 09:39:47 -0500 (CDT)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p7OEdgfA008082 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 24 Aug 2011 20:09:43 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Wed, 24 Aug 2011 20:09:42 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 24 Aug 2011 20:09:40 +0530
Subject: RE: [karp] Last Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt> (Supporting Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Topic: [karp] Last Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt> (Supporting Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Index: AcxbcHckAhwFV117ToWRv88q2y5g9gG+iTTg
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFF9A5F02@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <20110719145739.5942.53564.idtracker@ietfa.amsl.com> <tsl7h6ed1sp.fsf@mit.edu>
In-Reply-To: <tsl7h6ed1sp.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
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Mailman-Approved-At: Wed, 24 Aug 2011 08:26:11 -0700
Cc: "ospf@ietf.org" <ospf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 14:38:39 -0000

Hi,

[clipped]

>=20
> Based on this review I have a few recommendations for the=20
> OSPF v3 authentication trailers document.
>=20
> 1) The v3 authentication trailer takes a step back in the=20
> ability to rekey security associations both from OSPF v2,=20
> from IPsec for OSPF v3 and from=20

[ ..]

>=20
> I believe that draft-ietf-ospf-auth-trailer-ospfv3-05 needs=20
> to be revised to require implementation behavior at least as=20
> flexible as draft-ietf-karp-crypto-tables. That is,=20
> associated with each security association is a time for when=20
> sending packets can start with a given SA and for when it=20
> must stop. Infinity and 0 should of course be supported for=20
> the appropriate times.
>=20
> 2) I notice terminology inconsistency between key identifier =20
> and security association identifier. This should probably be=20
> cleaned up, although it's not that big of a deal.

http://tools.ietf.org/id/draft-ietf-ospf-auth-trailer-ospfv3-06.txt address=
es the first two comments.

>=20
>=20
> 3) draft-ietf-ospf-analysis says that we are going to solve=20
> related protocol attacks. That is, we recognize that it's=20
> quite likely that some people will use the same preshared key=20
> both for OSPF authentication and for something else. We need=20
> to mix something into the key or hash or something that is=20
> unlikely to appear in any other use in order to make it=20
> cryptographically unlikely for the resulting OSPF=20
> authentication hash to be a hash useful in some other=20
> protocol or for the hash from some other protocol to be=20
> useful in OSPF.  This draft does not do that.  One possible=20
> way to solve this would be to prepend a constant in front of=20
> the key in the key preparation step or a constant in front of=20
> every packet that gets hashed. The constant should be the=20
> same for OSPFv3 and not used for any other purpose.

We had an offline discussion with Sam and others and we seem to have conver=
ged at this text:

We change the hex that's repeated in the Apad from 0x878FE1F3 to 0x878FE1F4=
. This value will be unique for OSPFv3. Other protocols that use this mecha=
nism must use a different value of Apad - you could think of this as "salti=
ng" the Apad.

OLD TEXT in Sec 4.4:

Apad is a value which is the same length as the hash output or message dige=
st.  The first 16 octets contain the IPv6 source address followed by the he=
xadecimal value 0x878FE1F3 repeated (L-16)/4 times.
This implies that hash output is always a length of at least 16 octets.

NEW TEXT:

Apad is a value which is the same length as the hash output or message dige=
st.  The first 16 octets contain the IPv6 source address followed by the he=
xadecimal value 0x878FE1F4 repeated (L-16)/4 times.
This implies that hash output is always a length of at least 16 octets.

Cheers, Manav=

From acee.lindem@ericsson.com  Wed Aug 24 07:43:01 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB4E21F8B5D; Wed, 24 Aug 2011 07:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.482
X-Spam-Level: 
X-Spam-Status: No, score=-6.482 tagged_above=-999 required=5 tests=[AWL=0.117,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bVDuyFTPLHqF; Wed, 24 Aug 2011 07:43:00 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 89EC221F8B2D; Wed, 24 Aug 2011 07:43:00 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p7OEi77H017867; Wed, 24 Aug 2011 09:44:08 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.60]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 24 Aug 2011 10:44:02 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Date: Wed, 24 Aug 2011 10:44:00 -0400
Subject: Re: [OSPF] [karp] Last Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Topic: [OSPF] [karp] Last Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Index: AcxibEQOgTWOZ5r0QXe4QXW6KcTjhQ==
Message-ID: <8D54DD3C-45C6-4C34-9CD3-DF6B6C758B4E@ericsson.com>
References: <20110719145739.5942.53564.idtracker@ietfa.amsl.com> <tsl7h6ed1sp.fsf@mit.edu> <7C362EEF9C7896468B36C9B79200D8350CFF9A5F02@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFF9A5F02@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-120-882391960"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 24 Aug 2011 08:26:11 -0700
Cc: "ospf@ietf.org" <ospf@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 14:43:01 -0000

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

Hi Manav,=20

On Aug 24, 2011, at 10:39 AM, Bhatia, Manav (Manav) wrote:

> Hi,
>=20
> [clipped]
>=20
>>=20
>> Based on this review I have a few recommendations for the=20
>> OSPF v3 authentication trailers document.
>>=20
>> 1) The v3 authentication trailer takes a step back in the=20
>> ability to rekey security associations both from OSPF v2,=20
>> from IPsec for OSPF v3 and from=20
>=20
> [ ..]
>=20
>>=20
>> I believe that draft-ietf-ospf-auth-trailer-ospfv3-05 needs=20
>> to be revised to require implementation behavior at least as=20
>> flexible as draft-ietf-karp-crypto-tables. That is,=20
>> associated with each security association is a time for when=20
>> sending packets can start with a given SA and for when it=20
>> must stop. Infinity and 0 should of course be supported for=20
>> the appropriate times.
>>=20
>> 2) I notice terminology inconsistency between key identifier =20
>> and security association identifier. This should probably be=20
>> cleaned up, although it's not that big of a deal.
>=20
> http://tools.ietf.org/id/draft-ietf-ospf-auth-trailer-ospfv3-06.txt =
addresses the first two comments.
>=20
>>=20
>>=20
>> 3) draft-ietf-ospf-analysis says that we are going to solve=20
>> related protocol attacks. That is, we recognize that it's=20
>> quite likely that some people will use the same preshared key=20
>> both for OSPF authentication and for something else. We need=20
>> to mix something into the key or hash or something that is=20
>> unlikely to appear in any other use in order to make it=20
>> cryptographically unlikely for the resulting OSPF=20
>> authentication hash to be a hash useful in some other=20
>> protocol or for the hash from some other protocol to be=20
>> useful in OSPF.  This draft does not do that.  One possible=20
>> way to solve this would be to prepend a constant in front of=20
>> the key in the key preparation step or a constant in front of=20
>> every packet that gets hashed. The constant should be the=20
>> same for OSPFv3 and not used for any other purpose.
>=20
> We had an offline discussion with Sam and others and we seem to have =
converged at this text:
>=20
> We change the hex that's repeated in the Apad from 0x878FE1F3 to =
0x878FE1F4. This value will be unique for OSPFv3. Other protocols that =
use this mechanism must use a different value of Apad - you could think =
of this as "salting" the Apad.

Could we simply use the OSPFv3 protocol number, 89, in the Apad, e.g., =
0x898FE1F4,  (or at least the first instance of Apad). Otherwise, we =
probably need a registry for IANA Apads.=20

Thanks,
Acee=20


>=20
> OLD TEXT in Sec 4.4:
>=20
> Apad is a value which is the same length as the hash output or message =
digest.  The first 16 octets contain the IPv6 source address followed by =
the hexadecimal value 0x878FE1F3 repeated (L-16)/4 times.
> This implies that hash output is always a length of at least 16 =
octets.
>=20
> NEW TEXT:
>=20
> Apad is a value which is the same length as the hash output or message =
digest.  The first 16 octets contain the IPv6 source address followed by =
the hexadecimal value 0x878FE1F4 repeated (L-16)/4 times.
> This implies that hash output is always a length of at least 16 =
octets.
>=20
> Cheers, Manav
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDgyNDE0NDQwMVowIwYJKoZI
hvcNAQkEMRYEFOagzsmIf0Tydwb7JRdtBHgoM/e3MFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgFxh8OIrOe6YEjdlhxG7Jh9ultvwLdAR+NpMMBdWyEqHhfZ4ULLPJ0pZGL6HBZrS
GC5p/rmEDAErPwDx6SYbeOjpEhYoGAaFINyw+IyBlWpTsgUsPlXZ9PNKI7wAH2obj21oXMf1+Jp2
2ViEXQqyEd5c3UFJo99uCrO/PqAfsiT9AAAAAAAA

--Apple-Mail-120-882391960--

From acee.lindem@ericsson.com  Wed Aug 24 07:45:27 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B382621F8B6B; Wed, 24 Aug 2011 07:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.106,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n1ctv8hj1CfB; Wed, 24 Aug 2011 07:45:27 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 117F421F8AD9; Wed, 24 Aug 2011 07:45:27 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p7OEkFKK018477; Wed, 24 Aug 2011 09:46:33 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.60]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 24 Aug 2011 10:46:31 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Acee Lindem <acee.lindem@ericsson.com>
Date: Wed, 24 Aug 2011 10:46:31 -0400
Subject: Re: [OSPF] [karp] Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Topic: [OSPF] [karp] Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Index: AcxibJ0W8exhPoa4TDCkVUgqhZqnuA==
Message-ID: <1D4A7913-4FE3-4B9F-9D0D-9FBC5E12F56E@ericsson.com>
References: <20110719145739.5942.53564.idtracker@ietfa.amsl.com> <tsl7h6ed1sp.fsf@mit.edu> <7C362EEF9C7896468B36C9B79200D8350CFF9A5F02@INBANSXCHMBSA1.in.alcatel-lucent.com> <8D54DD3C-45C6-4C34-9CD3-DF6B6C758B4E@ericsson.com>
In-Reply-To: <8D54DD3C-45C6-4C34-9CD3-DF6B6C758B4E@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-121-882542660"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 24 Aug 2011 08:26:11 -0700
Cc: Sam Hartman <hartmans-ietf@mit.edu>, "ospf@ietf.org" <ospf@ietf.org>, "Bhatia, Manav \(Manav\)" <manav.bhatia@alcatel-lucent.com>, "ietf@ietf.org" <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 14:45:27 -0000

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


On Aug 24, 2011, at 10:44 AM, Acee Lindem wrote:

>=20
>=20
> Hi Manav,=20
>=20
> On Aug 24, 2011, at 10:39 AM, Bhatia, Manav (Manav) wrote:
>=20
>> Hi,
>>=20
>> [clipped]
>>=20
>>>=20
>>> Based on this review I have a few recommendations for the=20
>>> OSPF v3 authentication trailers document.
>>>=20
>>> 1) The v3 authentication trailer takes a step back in the=20
>>> ability to rekey security associations both from OSPF v2,=20
>>> from IPsec for OSPF v3 and from=20
>>=20
>> [ ..]
>>=20
>>>=20
>>> I believe that draft-ietf-ospf-auth-trailer-ospfv3-05 needs=20
>>> to be revised to require implementation behavior at least as=20
>>> flexible as draft-ietf-karp-crypto-tables. That is,=20
>>> associated with each security association is a time for when=20
>>> sending packets can start with a given SA and for when it=20
>>> must stop. Infinity and 0 should of course be supported for=20
>>> the appropriate times.
>>>=20
>>> 2) I notice terminology inconsistency between key identifier =20
>>> and security association identifier. This should probably be=20
>>> cleaned up, although it's not that big of a deal.
>>=20
>> http://tools.ietf.org/id/draft-ietf-ospf-auth-trailer-ospfv3-06.txt =
addresses the first two comments.
>>=20
>>>=20
>>>=20
>>> 3) draft-ietf-ospf-analysis says that we are going to solve=20
>>> related protocol attacks. That is, we recognize that it's=20
>>> quite likely that some people will use the same preshared key=20
>>> both for OSPF authentication and for something else. We need=20
>>> to mix something into the key or hash or something that is=20
>>> unlikely to appear in any other use in order to make it=20
>>> cryptographically unlikely for the resulting OSPF=20
>>> authentication hash to be a hash useful in some other=20
>>> protocol or for the hash from some other protocol to be=20
>>> useful in OSPF.  This draft does not do that.  One possible=20
>>> way to solve this would be to prepend a constant in front of=20
>>> the key in the key preparation step or a constant in front of=20
>>> every packet that gets hashed. The constant should be the=20
>>> same for OSPFv3 and not used for any other purpose.
>>=20
>> We had an offline discussion with Sam and others and we seem to have =
converged at this text:
>>=20
>> We change the hex that's repeated in the Apad from 0x878FE1F3 to =
0x878FE1F4. This value will be unique for OSPFv3. Other protocols that =
use this mechanism must use a different value of Apad - you could think =
of this as "salting" the Apad.
>=20
> Could we simply use the OSPFv3 protocol number, 89, in the Apad, e.g., =
0x898FE1F4,  (or at least the first instance of Apad). Otherwise, we =
probably need a registry for IANA Apads.=20

I meant 0x898FE1F3 as to not change the last 3 octets of the existing =
HMAC-SHAx Apad.=20

Thanks,
Acee=20

>=20
> Thanks,
> Acee=20
>=20
>=20
>>=20
>> OLD TEXT in Sec 4.4:
>>=20
>> Apad is a value which is the same length as the hash output or =
message digest.  The first 16 octets contain the IPv6 source address =
followed by the hexadecimal value 0x878FE1F3 repeated (L-16)/4 times.
>> This implies that hash output is always a length of at least 16 =
octets.
>>=20
>> NEW TEXT:
>>=20
>> Apad is a value which is the same length as the hash output or =
message digest.  The first 16 octets contain the IPv6 source address =
followed by the hexadecimal value 0x878FE1F4 repeated (L-16)/4 times.
>> This implies that hash output is always a length of at least 16 =
octets.
>>=20
>> Cheers, Manav
>> _______________________________________________
>> OSPF mailing list
>> OSPF@ietf.org
>> https://www.ietf.org/mailman/listinfo/ospf
>=20


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDgyNDE0NDYzMlowIwYJKoZI
hvcNAQkEMRYEFH9BW6Cw3iAeOyDw3Yb4yFoxDamTMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgBiclg0zq7RirLCErjLzunMZp7eZ2Six6yyGXQgG5MOEWnMJduiAcs9bMD3giIne
0kaKra4wDlgkujmgawVzHpHgoZx8BojxSFyE9+K5jjYmvqtq6xUSKM2uf1cS2+0F1vFTkCfFtax4
4+q2CJ2ALxEsACgoBJtMwnmcTEKdOGchAAAAAAAA

--Apple-Mail-121-882542660--

From manav.bhatia@alcatel-lucent.com  Wed Aug 24 07:50:07 2011
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296D221F8BAB; Wed, 24 Aug 2011 07:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.266
X-Spam-Level: 
X-Spam-Status: No, score=-6.266 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M52X7HeBlzNF; Wed, 24 Aug 2011 07:50:06 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 4BEA821F8B8A; Wed, 24 Aug 2011 07:50:06 -0700 (PDT)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id p7OEpAri021455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 24 Aug 2011 09:51:13 -0500 (CDT)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p7OEp9dF030370 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 24 Aug 2011 20:21:09 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Wed, 24 Aug 2011 20:21:09 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Acee Lindem <acee.lindem@ericsson.com>
Date: Wed, 24 Aug 2011 20:21:08 +0530
Subject: RE: [OSPF] [karp] Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Topic: [OSPF] [karp] Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Index: AcxibJ0W8exhPoa4TDCkVUgqhZqnuAAAC72A
Message-ID: <7C362EEF9C7896468B36C9B79200D8350CFF9A5F06@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <20110719145739.5942.53564.idtracker@ietfa.amsl.com> <tsl7h6ed1sp.fsf@mit.edu> <7C362EEF9C7896468B36C9B79200D8350CFF9A5F02@INBANSXCHMBSA1.in.alcatel-lucent.com> <8D54DD3C-45C6-4C34-9CD3-DF6B6C758B4E@ericsson.com> <1D4A7913-4FE3-4B9F-9D0D-9FBC5E12F56E@ericsson.com>
In-Reply-To: <1D4A7913-4FE3-4B9F-9D0D-9FBC5E12F56E@ericsson.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-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Mailman-Approved-At: Wed, 24 Aug 2011 08:26:11 -0700
Cc: "ospf@ietf.org" <ospf@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 14:50:07 -0000

Hi Acee,

> >>=20
> >> We change the hex that's repeated in the Apad from=20
> 0x878FE1F3 to 0x878FE1F4. This value will be unique for=20
> OSPFv3. Other protocols that use this mechanism must use a=20
> different value of Apad - you could think of this as=20
> "salting" the Apad.
> >=20
> > Could we simply use the OSPFv3 protocol number, 89, in the=20
> Apad, e.g., 0x898FE1F4,  (or at least the first instance of=20
> Apad). Otherwise, we probably need a registry for IANA Apads.=20
>=20
> I meant 0x898FE1F3 as to not change the last 3 octets of the=20
> existing HMAC-SHAx Apad.=20

We would still need an IANA registry of Apads unless youre thinking of usin=
g the IP protocol type as the first octet of the Apad. If it's the latter, =
then OSPFv3 and OSPFv2 would share the same Apad, which would defeat the pu=
rpose of the whole exercise.

This would also not work for multiple protocols that ride over UDP and TCP.=
 BFD and RIP would end up using the same Apad as their IP protocol is the s=
ame.=20

We thus need a unique Apad that each standard can define if we want to prot=
ect ourselves from the attack that Sam describes.

Cheers, Manav=20

From moore@network-heretics.com  Wed Aug 24 08:46:57 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8829321F8C36 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 08:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.458
X-Spam-Level: 
X-Spam-Status: No, score=-3.458 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrkEEdP0pIAM for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 08:46:56 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 7728C21F8C35 for <ietf@ietf.org>; Wed, 24 Aug 2011 08:46:56 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 4EF0F20832; Wed, 24 Aug 2011 11:48:07 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 24 Aug 2011 11:48:07 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=dJc JFm/A+mtex+mFlMTVEADLD0M=; b=AEQXiyPeeO1Zf9eS79ThrYgZyBBCa6BJM3+ vc0L0D0I5mgMXlxOomABlYLaA9NSuWsonze7ZEgl1bxD0gOirR5vCsq+mJAO3G3w +NG2PJ1alaOwLpnbdHA82KtLR+o/T0nWJTksODq/WEdpSwQlip6wlbGd+0VRju9D uVk3Zmu8=
X-Sasl-enc: Zrpmrwu08jyFbTc8VZ0kThYZgNBm+iMQ+fkfoI0TpszO 1314200886
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 77FFE920178; Wed, 24 Aug 2011 11:48:05 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-10-886213362
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>
Date: Wed, 24 Aug 2011 11:47:42 -0400
Message-Id: <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>
To: "George, Wesley" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion list <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 15:46:57 -0000

--Apple-Mail-10-886213362
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Aug 24, 2011, at 9:34 AM, George, Wesley wrote:
=20
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Keith Moore
> Sent: Wednesday, August 24, 2011 8:37 AM
> To: Ray Pelletier
> Cc: John C Klensin; Secretariat IETF; IETF-Discussion list; Lixia =
Zhang
> Subject: Re: Hyatt Taipei cancellation policy?
> =20
> $300/night is far too high a ceiling for a guest room rate.  A more =
reasonable ceiling would be in the ballpark of $150.
> =20
> I don=92t understand why we keep throwing around hard and fast dollar =
figures. Every person, whether paying their own way or using a corporate =
expense account is going to have a different view of what is ok vs what =
is unacceptably high, and that may or may not line up with the market =
rate reality of the actual location chosen. As others have pointed out =
in the past, the only limit that would make sense is to use something =
like the US gov=92t max travel rate guidelines, which are indexed to =
things like USD value vs. local currency, average cost by location, etc. =
[...]

I think you're missing my point.  I'm concerned about the total cost of =
attending an IETF meeting, or IETF meetings in general.  The per night =
room rate obviously isn't the only factor.  But when the room rate goes =
much above $150/night, it starts to become a very significant factor, =
often the most significant factor, in total travel cost.

More broadly, when IETF negotiators start thinking it's okay for rooms =
to cost much more than $150 per night, there's a serious disconnect =
going on.  Maybe they don't realize it, but at that point they're =
actively working to exclude participation from those not supported by =
large companies or governments. =20

I'm not arguing for a hard, fixed ceiling for room rates or anything =
else.  I'm saying that the average total cost of attending an IETF =
meeting needs to be kept down.

(Having said that, I personally don't mind if the conference hotel is =
expensive as long as there are reasonably priced alternatives nearby.  =
In Quebec City I stayed at a very nice hotel in the old town, about 5 =
minutes' walk away.  But I also realize that for some participants, even =
that distance might be a significant burden.)

Whether the room cost is reasonable for a particular location matters if =
you're getting reimbursed by someone who will only pay the USG per diem =
rate.  And for those in that situation, it's a valid concern.  It's just =
not what I happen to be concerned about.

Keith

p.s. I keep thinking that we should try, at least once, holding a =
meeting on a college campus between semesters.   Colleges tend to have =
lots of meeting space, campus networks with wi-fi, lots of food =
available nearby (though perhaps not "fine lunches and dinners"), and =
the ones that have popular sports teams tend to have plenty of nearby =
hotel rooms available at reasonable prices in the off season.   Some =
colleges will want to charge conference center rates, but I bet that =
there are lots of colleges struggling to make ends meet that might be =
willing to cut a deal.=20


--Apple-Mail-10-886213362
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Aug 24, 2011, at 9:34 AM, George, Wesley =
wrote:</div><div><span class=3D"Apple-style-span" style=3D"color: =
rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 15px; =
">&nbsp;</span></div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><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"font-family: Helvetica; font-size: medium; "><div =
style=3D"border-right-style: none; border-bottom-style: none; =
border-left-style: none; border-width: initial; border-color: initial; =
border-top-style: solid; border-top-color: rgb(181, 196, 223); =
border-top-width: 1pt; padding-top: 3pt; padding-right: 0in; =
padding-bottom: 0in; padding-left: 0in; position: static; z-index: auto; =
"><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">ietf-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:ietf-bounces@ietf.org=
]<span class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Keith =
Moore<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Wednesday, August 24, 2011 =
8:37 AM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Ray =
Pelletier<br><b>Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>John C Klensin; Secretariat =
IETF; IETF-Discussion list; Lixia Zhang<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: Hyatt Taipei =
cancellation policy?<o:p></o:p></span></div></div></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">$300/night is far too =
high a ceiling for a guest room rate. &nbsp;A more reasonable ceiling =
would be in the ballpark of $150.<o:p></o:p></div><div =
style=3D"font-family: Helvetica; font-size: medium; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"color: rgb(31, 73, 125); ">I don=92t understand why we keep =
throwing around hard and fast dollar figures. Every person, whether =
paying their own way or using a corporate expense account is going to =
have a different view of what is ok vs what is unacceptably high, and =
that may or may not line up with the market rate reality of the actual =
location chosen. As others have pointed out in the past, the only limit =
that would make sense is to use something like the US gov=92t max travel =
rate guidelines, which are indexed to things like USD value vs. local =
currency, average cost by location, etc. =
[...]</span></div></div></div></div></div></span></blockquote><div><br></d=
iv>I think you're missing my point. &nbsp;I'm concerned about the total =
cost of attending an IETF meeting, or IETF meetings in general. =
&nbsp;The per night room rate obviously isn't the only factor. &nbsp;But =
when the room rate goes much above $150/night, it starts to become a =
very significant factor, often the most significant factor, in total =
travel cost.</div><div><br></div><div>More broadly, when IETF =
negotiators start thinking it's&nbsp;okay for rooms to cost much more =
than $150 per night, there's a serious disconnect going on. &nbsp;Maybe =
they don't realize it, but at that point they're actively working to =
exclude participation from those not supported by large companies or =
governments. &nbsp;</div><div><br></div><div>I'm not arguing for a hard, =
fixed ceiling for room rates or anything else. &nbsp;I'm saying that the =
average total cost of attending an IETF meeting needs to be kept =
down.</div><div><br></div><div>(Having said that, I personally don't =
mind if the conference hotel is expensive as long as there are =
reasonably priced alternatives nearby. &nbsp;In Quebec City I stayed at =
a very nice hotel in the old town, about 5 minutes' walk away. &nbsp;But =
I also realize that for some participants, even that distance might be a =
significant burden.)</div><div><br></div><div>Whether the room cost is =
reasonable for a particular location matters if you're getting =
reimbursed by someone who will only pay the USG per diem rate. &nbsp;And =
for those in that situation, it's a valid concern. &nbsp;It's just not =
what I happen to be concerned =
about.</div><div><br></div><div>Keith</div><div><br></div><div>p.s. I =
keep thinking that we should try, at least once, holding a meeting on a =
college campus between semesters. &nbsp; Colleges tend to have lots of =
meeting space, campus networks with wi-fi, lots of food available nearby =
(though perhaps not "fine lunches and dinners"), and the ones that have =
popular sports teams tend to have plenty of nearby hotel rooms available =
at reasonable prices in the off season. &nbsp; Some colleges will want =
to charge conference center rates, but I bet that there are lots of =
colleges struggling to make ends meet that might be willing to cut a =
deal.&nbsp;</div><div><br></div></body></html>=

--Apple-Mail-10-886213362--

From hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com  Wed Aug 24 10:36:39 2011
Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B749621F8B16 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 10:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.831
X-Spam-Level: 
X-Spam-Status: No, score=-102.831 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pM-bxOpvX4fB for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 10:36:38 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id AE15C21F8B31 for <ietf@ietf.org>; Wed, 24 Aug 2011 10:36:38 -0700 (PDT)
Received: by ywe9 with SMTP id 9so1245820ywe.31 for <ietf@ietf.org>; Wed, 24 Aug 2011 10:37:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=hdVNQJdwwOwqCEpokU4gHfeBmKHOq2TSP1t3PEKffBU=; b=ECr3jNFyurT+T1qKuauWKs1VCbE6gG5ckrHbMeVDgh3K6jq4x7V2V/yF0+ule98a72 MIMuxlkgdW4tzp3yehmEWRNl8VzjDXbdPllr6LRqXhGvoseEDI+ckT5cN63OEZcNlew2 CbrtgvXD+WFlGZTU7GHj0ySZn57mH5tQarrfw=
Received: by 10.143.69.12 with SMTP id w12mr2724672wfk.298.1314207469143; Wed, 24 Aug 2011 10:37:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.98.5 with HTTP; Wed, 24 Aug 2011 10:37:08 -0700 (PDT)
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Wed, 24 Aug 2011 19:37:08 +0200
Message-ID: <CAHhFybrcU5-jmSkQY5ZJ3RzStPE5brJj3a+XP_TWYM80yByFDg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-websec-origin-04.txt> (The Web Origin Concept) to Proposed Standard
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 17:36:39 -0000

Hi, a clear definition of "same origin" on standards track is a good thing.
Maybe some details could be improved:

1 - <OWS>, maybe I miss the point, but that is apparently the same as LWSP
    with an additional SHOULD to produce only a single SP.  If that is the
    case just saying LWSP would be clearer.  Caveat, the similar <OWS> in
    I-D.ietf-httpbis-p1-messaging-15 does not yet/more say that TAB is bad.
    If you insist on it please replace WSP by SP, and add HT to <obs-fold>.

2 - GUID, if this is supposed to be an UUID as described in RFC 4122 please
    say so.  Otherwise say *what* it is.  Reading section 4 I was sure that
    it talks about a "name-based UUID" (RFC 4122 section 4.3 for the URL
    namespace in appendix C of RFC 4122), a.k.a. UUID version 3 or 5.

    But later section 5 bullet 3 apparently expects UUID version 1 based
    on timestamps, and not some kind of "URI equality" as in version 3/5.

3 - i18n, the Unicode serialization is defined, but apparently not used.
    Is the draft actually designed for IRIs instead of URIs?  There is a
    "MUST support IDNA2003, if IDNA2008 is unsupported" in the i18n part:
    I don't get why if only URIs are affected.

    I think you want IRIs, and that's why you reference IDNA, please add
    a reference to RFC 3987 and use the correct term if that is the case.
    If you really only want URIs you could get rid of the unused Unicode
    serialization and the IDNA mustard.

4 - null
    For the Origin: HTTP header field the important serialization is in
    both cases ASCII, please swap sections 6.1 and 6.2, and limit the
    Unicode section to step 4.  Steps 1..3 and 5..6 are identical, and
    just saying "null" in the same style as "://" would be clearer than
    talking about U+006E, U+0075, U+006C, U+006C in the ASCII section.

    If what you really want is a case-sensitive lower-case string "null"
    the ABNF notation for both serializations should be %x6E.75.6C.6C or
    similar.

5 - www, obviously you decided that there will be no exception for www.
    Maybe note why in the FAQ (section 3.2).  I can't say that I like
    the concept "different port or different scheme is never the same
    origin", but at least it is clear, and automatically covers https:.

-Frank

From sm@resistor.net  Wed Aug 24 10:48:33 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B1821F8BB2 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 10:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vlq8M3K5CRpM for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 10:48:32 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3347A21F8B8A for <ietf@ietf.org>; Wed, 24 Aug 2011 10:48:32 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7OHnakJ015060; Wed, 24 Aug 2011 10:49:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1314208182; bh=ZGmmXo1oyAxryGoXQJGc6ttImxJilH/3fthCJMyW3PA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Content-Transfer-Encoding; b=sQJ88yaU1mFirhNKzaAOWpBM2tJDt7sJdxw8FbMGQ4Rpgf2fciDOwnGkuUz9AsiFr 1irmRIa3FfSioOij4c6ocPdzN/6EOfVf9r1rAjxWXq6GNOc0O/si++1HGS+NzcOSXE 9ReqAQMN6UIW5c4m2uAGKPMO2307kAMyKubh9v/M=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1314208182; bh=ZGmmXo1oyAxryGoXQJGc6ttImxJilH/3fthCJMyW3PA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Content-Transfer-Encoding; b=KjE0AtUMgkKCQXZnyJWtbg5X0quutfdHIYxD7laHDISDrOyA+4h2zEIjDMVBlZgOv ju0+kV+7vJbVhxLZafDQki1s+bL0oKRsOQtVI8s3BRJsefSpZUmLOZCzKfWVVDmvJI HQwLPTFJ6FiP3TyFjAmaj246odeq5S5LamCPvaYU=
Message-Id: <6.2.5.6.2.20110824075034.06819068@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 24 Aug 2011 10:49:23 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: IAOC, travel and hotel prices (was RE: Hyatt Taipei cancellation policy?)
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.t wcable.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 17:48:33 -0000

At 06:31 24-08-2011, George, Wesley wrote:
>Perhaps it=92s time for those who seem most=20
>concerned about this to author a BCP draft=20
>regarding IETF meeting venue and hotel selection=20
>policies that addresses this, so that

See draft-palet-ietf-meeting-venue-selection-criteria-04 (expired).

>  IAOC has a bit clearer instructions and a=20
> documented policy based on community consensus,=20
> rather than this discussion continuing to come=20
> up every couple of meetings, and the general=20
> response from the IAOC being =93this is hard,=20
> we=92re doing the best we can=85 [example, explanation]=94

It's safer to stick to a tried strategy.

>Not to say that I doubt the intentions or=20
>efforts of any of the IAOC folks past or=20
>present, but the theme I keep seeing in these=20
>discussions is a request for both transparency=20
>and price sensitivity, and I=92m not sure that the=20
>feedback is being acknowledged so much as it is=20
>being treated as a request for explanation of the extenuating=
 circumstances.

My guess is that the contact covers:

  (a) Guest substitution

  (b) Client attrition

  (c) Guaranteed reservations and the terms for a refund

  (d) Reservation cut-off

  (e) Hotel rate after cut-off

Some of the information could probably be made=20
available at the time of the announcement of the=20
venue selection.  Although it still won't be=20
possible to select a different venue, it gives=20
the community ample time to complain.

Glen Zorn mentioned that "the end result being=20
that major corporate support would be mandatory=20
for attendants: independents, academics and even=20
employees of small companies need not=20
apply".  Lixia Zhang mentioned that "up to now=20
IETF hotel prices have been within the federal=20
per diem allowance". Peter Saint-Andre mentioned=20
that "thanks to tips from other cost-conscious=20
IETFers, [he] was able to find hotels costing=20
$100".  Ray mentioned that "Many places they just don't need our business".

A rough number for hotel and travel costs might be as follows:

   U.S. to Taiwan:     $3,619
   U.K. to Taiwan:     $3,765
   China to Taiwan:    $3,094

   U.S. to Paris:      $3,841
   U.K. to Paris:      $2,325
   China to Paris:     $3,780

   U.S. to Vancouver:  $3,226
   U.K. to Vancouver:  $5,535
   China to Vancouver: $4,212

The question of cross-subsidization has not been=20
brought into the discussion yet.  There is also=20
the question of rotation across continents.  Over=20
the years U.S. IETF participation (used loosely)=20
has dropped to 50%.  IETF participation from the=20
European Union has increased to 25%.  IETF=20
participation from Asia has increased to=20
15%.  The choice of IETF meeting venue has an=20
impact on U.S. participation.  Based on the above=20
numbers, I would have concluded that it=20
shouldn't.  I doubt that U.S. participants=20
encounter visa issues.  Maybe it is because those=20
without major corporate support find the attendance too expensive.

Is there any hypothesis about why this type of=20
discussion does not occur when a venue in the U.S. is selected?

Regards,
-sm=20


From melinda.shore@gmail.com  Wed Aug 24 12:08:33 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E858921F8C0F for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FHsOrATNC0wB for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:08:33 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5B59E21F8C0D for <ietf@ietf.org>; Wed, 24 Aug 2011 12:08:33 -0700 (PDT)
Received: by gyf3 with SMTP id 3so1328021gyf.31 for <ietf@ietf.org>; Wed, 24 Aug 2011 12:09:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=wKt3tAors6TRcklVdOQFXz5EQllyx/VNo6urmbw7HzA=; b=ugnD2mUMz7C5mt3a+ssevGAHZ4Ct22/HZXJDlefLeHWzOFJ0f6KQRJj8Qg/MDtwiaH 5TNm2w4KzvZa94ZgwjzwSDlc2wgJkVO0iIgAFvjlxZZeeq/5NBUjri+yqEy55ApkfJbM s8xoy1nTeVv2MkGB86gcXxA8GlA2gNm8xqUPI=
Received: by 10.142.226.2 with SMTP id y2mr2909343wfg.449.1314212984174; Wed, 24 Aug 2011 12:09:44 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu [137.229.12.236]) by mx.google.com with ESMTPS id a11sm612898wff.12.2011.08.24.12.09.42 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 12:09:43 -0700 (PDT)
Message-ID: <4E554C78.9000504@gmail.com>
Date: Wed, 24 Aug 2011 11:09:44 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>
In-Reply-To: <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 19:08:34 -0000

On 08/24/2011 07:47 AM, Keith Moore wrote:
>Maybe they don't realize it, but at that point they're
> actively working to exclude participation from those not supported by
> large companies or governments.

It seems to me that this is a very, very important point.

Melinda

From hartmans@mit.edu  Wed Aug 24 12:27:54 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9605421F8C4D for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.684
X-Spam-Level: 
X-Spam-Status: No, score=-103.684 tagged_above=-999 required=5 tests=[AWL=-1.419, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V6CR5+z1KgWT for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:27:54 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5E921F8C75 for <ietf@ietf.org>; Wed, 24 Aug 2011 12:27:54 -0700 (PDT)
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 A87B120148; Wed, 24 Aug 2011 15:31:20 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 219DA423D; Wed, 24 Aug 2011 15:28:55 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com>
Date: Wed, 24 Aug 2011 15:28:55 -0400
In-Reply-To: <4E554C78.9000504@gmail.com> (Melinda Shore's message of "Wed, 24 Aug 2011 11:09:44 -0800")
Message-ID: <tslr54a8v7s.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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 19:27:54 -0000

>>>>> "Melinda" == Melinda Shore <melinda.shore@gmail.com> writes:

    Melinda> On 08/24/2011 07:47 AM, Keith Moore wrote:
    >> Maybe they don't realize it, but at that point they're actively
    >> working to exclude participation from those not supported by
    >> large companies or governments.

    Melinda> It seems to me that this is a very, very important point.

I'd like to underscore this poin.
I'd like to make two others.

1) We don't have to go to any particular location.  There has been an
assumption made by people in this discussion that sometimes when we pick
locations with particularly expensive hotels, we'll get particularly
expensive meetings.  That's great except that we were the ones who chose
to go to those locations.
If we can't meet our cost targets at a location, go somewhere else.

2) If I had to say yes or no in a parliamentary vote of confidence in
the IAOC, today my answer would probably be no.  I feel that a lot of
concerns have been raised, and I don't find the responses very
convincing.  When I've looked into issues with the IAOC, I haven't found
the visibility necessary to really evaluate things.
That to me is not a good combination.

From scott.brim@gmail.com  Wed Aug 24 12:35:44 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBA6E21F8C60 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.557
X-Spam-Level: 
X-Spam-Status: No, score=-103.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5B0r0OmrkYtt for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:35:44 -0700 (PDT)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id 429CE21F8BA0 for <ietf@ietf.org>; Wed, 24 Aug 2011 12:35:44 -0700 (PDT)
Received: by iye1 with SMTP id 1so2332121iye.27 for <ietf@ietf.org>; Wed, 24 Aug 2011 12:36:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qXt/4K4O/wW93TOwnDxghg3eIIFawfPh9931kTZ0nJg=; b=Lwc6+ncucEx8geAL/l+kprpHbtS3YGPKNQ4TKx8HAEZAaOKg5jnjQgmRB4dagpBfqM I3QOxp5K6XozRmFaf++cYq5nB3dG2sTJjqw5/5i6cWM6bjy3rGqaJU24EV4hLoANWjfc D2VOlrshJSjGPwyBVhk2PxqCPnaaK4ZjT6uYk=
Received: by 10.42.163.9 with SMTP id a9mr5210643icy.345.1314214615351; Wed, 24 Aug 2011 12:36:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.35.129 with HTTP; Wed, 24 Aug 2011 12:36:35 -0700 (PDT)
In-Reply-To: <4E554C78.9000504@gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 24 Aug 2011 15:36:35 -0400
Message-ID: <CAPv4CP9qoFA7GygDGOB-hgRMh2mVmxy530whQ2RagaCRs3MXGw@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 19:35:44 -0000

On Wed, Aug 24, 2011 at 15:09, Melinda Shore <melinda.shore@gmail.com> wrote:
> On 08/24/2011 07:47 AM, Keith Moore wrote:
>>
>> Maybe they don't realize it, but at that point they're
>> actively working to exclude participation from those not supported by
>> large companies or governments.
>
> It seems to me that this is a very, very important point.

I haven't stayed in the main hotel for a number of IETFs, in order to
save money, but I haven't had trouble finding a good place to stay, in
various cities around the world.  IMHO the IETF can continue to book
rooms at a hotel that has good support for foreigners and is adjacent
to the meeting facility, but also make sure there is good
transportation so that people -- most people perhaps -- can stay
elsewhere.

From ole@cisco.com  Wed Aug 24 12:36:49 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D41F21F8C9E for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:36:49 -0700 (PDT)
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.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gmlr8rsF8iPk for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 12:36:48 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id D240A21F8C5F for <ietf@ietf.org>; Wed, 24 Aug 2011 12:36:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=2452; q=dns/txt; s=iport; t=1314214679; x=1315424279; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=M1RuCreOWiU0GG65SwFbdyueRJ16LZEJiT4WwV1ZsgI=; b=jkEwerQXL8YmvbwpfiYg74CYd2J60YVIv/77J4yewpot22/yZlH3dkrD oaLh0xeeZ1fVoehqVGLBOKXWetMfnWE1KH7MyGfpyvIdh2BvrgKAeg02P QJzqDbz8NZsPzRkP1NujfiVkPElt9n+gL7d3ipeP/ugkwlrQBlNMaKt/N w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAH5SVU6rRDoG/2dsb2JhbAA/Aw6ncneBQAEBAQEDAQEBDwECASQwBAsQCxguIQYwBhMUBweHU5tAAYMmDwGbaINBgwgEh2GVLwGGS1g
X-IronPort-AV: E=Sophos;i="4.68,277,1312156800"; d="scan'208";a="16181065"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-8.cisco.com with ESMTP; 24 Aug 2011 19:37:58 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7OJbwFg017396; Wed, 24 Aug 2011 19:37:58 GMT
Date: Wed, 24 Aug 2011 12:37:57 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <tslr54a8v7s.fsf@mit.edu>
Message-ID: <alpine.OSX.2.01.1108241231320.7436@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 19:36:49 -0000

Let me just point out that the IETF community has expressed a strong 
preference for:

* "One roof" venues, meeting space in HQ hotel or HQ hotel next to 
  convention center.

* Cities, not resorts, because the former yields many more 
  accomodation options for those who wish to stay in HQ hotel 
  alternatives.

* Sticking to our fixed dates, published up to 5 years in advance.

I think you will find that the one-roof solution does indeed lead to 
fairly expensive HQ properties, this is more or less true all over the
world and is currently made much worse by the weak dollar. The fixed
date restriction (which is good in my view) also contributes to 
challenges with venue availability. We been told more than once that
"if you do it a week later or earlier..."

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 24 Aug 2011, Sam Hartman wrote:

> >>>>> "Melinda" == Melinda Shore <melinda.shore@gmail.com> writes:
> 
>     Melinda> On 08/24/2011 07:47 AM, Keith Moore wrote:
>     >> Maybe they don't realize it, but at that point they're actively
>     >> working to exclude participation from those not supported by
>     >> large companies or governments.
> 
>     Melinda> It seems to me that this is a very, very important point.
> 
> I'd like to underscore this poin.
> I'd like to make two others.
> 
> 1) We don't have to go to any particular location.  There has been an
> assumption made by people in this discussion that sometimes when we pick
> locations with particularly expensive hotels, we'll get particularly
> expensive meetings.  That's great except that we were the ones who chose
> to go to those locations.
> If we can't meet our cost targets at a location, go somewhere else.
> 
> 2) If I had to say yes or no in a parliamentary vote of confidence in
> the IAOC, today my answer would probably be no.  I feel that a lot of
> concerns have been raised, and I don't find the responses very
> convincing.  When I've looked into issues with the IAOC, I haven't found
> the visibility necessary to really evaluate things.
> That to me is not a good combination.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From steve@shinkuro.com  Wed Aug 24 13:00:45 2011
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE2521F8586 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.664
X-Spam-Level: 
X-Spam-Status: No, score=-1.664 tagged_above=-999 required=5 tests=[AWL=-0.194, BAYES_00=-2.599, HELO_EQ_DSL=1.129]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8EFCkNdxuSOr for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:00:45 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 15ECC21F857D for <ietf@ietf.org>; Wed, 24 Aug 2011 13:00:44 -0700 (PDT)
Received: from [70.88.139.89] (HELO dynamic156.shinkuro.com) by execdsl.com (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 19827560; Wed, 24 Aug 2011 20:03:04 +0000
Subject: Is the IAOC responsive?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <tslr54a8v7s.fsf@mit.edu>
Date: Wed, 24 Aug 2011 16:01:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AAB0832F-D048-4A22-90DA-0F2AD0F0595D@shinkuro.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1084)
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:00:45 -0000

In response to Sam's comment re whether the IAOC is responsive and/or =
transparent, if this is indeed a problem it needs to be fixed.  As a =
founding member of the IAOC, I can attest that these two qualities, =
responsiveness and transparency, were the driving concerns that led to =
the creation of the IASA.

Having served on the IAOC and having watched successive administrations, =
I know first hand the old verity, "You can please all of the people some =
of the time and some of the people all of the time, but you can't please =
all of the people all of the time."  Moreover, it's almost always the =
people that are unhappy that make the most noise.

All of this is normal and to be expected.  That said, the IETF is in =
full control of the IAOC, so if they're not responsive and/or not =
transparent, it's relatively easy to get their attention and/or replace =
them.  But the more likely situation is that different subgroups within =
the IETF want different things, and it's simply impossible to satisfy =
everybody.  There are surely a large fraction of attendees who like =
having everything in one place and who are relatively insensitive to the =
price.  Whether that should be the prevailing answer is up to the =
overall community.  The IAOC will surely do whatever the overall =
community wants, as long as it's actually feasible.  If the community =
insists on contradictory or impossible results and then insists on =
blaming the IAOC, we'll simply have dysfunctional chaos.

Let's get the facts laid out for all to see, figure out what choices =
we're going to make, and then live with the results.

Thanks,

Steve

Full disclosures:

1. My brother, Dave Crocker, is currently on the IAOC.

2. I did not discuss this with him.  In general, we have different value =
sets with respect to meetings (and many other things).

3. Whenever he and I are aligned, we're almost always right.



On Aug 24, 2011, at 3:28 PM, Sam Hartman wrote:
>=20
>=20
> 2) If I had to say yes or no in a parliamentary vote of confidence in
> the IAOC, today my answer would probably be no.  I feel that a lot of
> concerns have been raised, and I don't find the responses very
> convincing.  When I've looked into issues with the IAOC, I haven't =
found
> the visibility necessary to really evaluate things.
> That to me is not a good combination.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From dhc@dcrocker.net  Wed Aug 24 13:10:57 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9322C21F8742 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ye-mTvWl8gY for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:10:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 11ACD21F84F8 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:10:57 -0700 (PDT)
Received: from [192.168.1.3] (10.sub-166-250-34.myvzw.com [166.250.34.10]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7OKBtj1004646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 13:12:03 -0700
Message-ID: <4E555B06.6000108@dcrocker.net>
Date: Wed, 24 Aug 2011 13:11:50 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>
In-Reply-To: <tslr54a8v7s.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 24 Aug 2011 13:12:05 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:10:57 -0000

On 8/24/2011 12:28 PM, Sam Hartman wrote:
>  I feel that a lot of
> concerns have been raised, and I don't find the responses very
> convincing.

As the new guy on the IAOC block, I'm still learning the complexities of IETF 
venue planning.

Perhaps you can list the concerns that have been raised and -- as an efficiency 
filter -- are shared among a significant base of the community?

It would also help to see what responses have been offered and what is 
unsatisfactory about them.


> When I've looked into issues with the IAOC, I haven't found
> the visibility necessary to really evaluate things.

The issue of transparency/visibility has been raised a couple of times in this 
thread.  While I understand it as a general concept, I'm not clear how to apply 
it pragmatically here.

I don't understand what folks should be done differently /in specific/ that 
would continue to permit a practical process of event planning.  To use an 
extreme example:  A completely fishbowl model of administrative process, in 
which every discussion and decision is explored under full view of the entire 
community, is not practical.

d/

ps.  As a personal aside, I'll note that I've lobbied rather vigorously for 
venues that entail less travel effort, by eliminating the additional hop needed 
to get from a major hub.  Note that that has gotten essentially zero support 
from the community.  The community has vigrously expressed a preference for 
"interesting" venues rather than ones that are chosen solely for logistics 
convenience.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc@dcrocker.net  Wed Aug 24 13:13:37 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD62021F8B91 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2PBgDY0JAacw for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:13:37 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CD95521F8B8B for <ietf@ietf.org>; Wed, 24 Aug 2011 13:13:36 -0700 (PDT)
Received: from [192.168.1.3] (10.sub-166-250-34.myvzw.com [166.250.34.10]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7OKEaeT004692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 13:14:47 -0700
Message-ID: <4E555BA7.2040204@dcrocker.net>
Date: Wed, 24 Aug 2011 13:14:31 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Steve Crocker <steve@shinkuro.com>
Subject: Re: Is the IAOC responsive?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <AAB0832F-D048-4A22-90DA-0F2AD0F0595D@shinkuro.com>
In-Reply-To: <AAB0832F-D048-4A22-90DA-0F2AD0F0595D@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]); Wed, 24 Aug 2011 13:14:48 -0700 (PDT)
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:13:37 -0000

On 8/24/2011 1:01 PM, Steve Crocker wrote:
> 2. I did not discuss this with him.  In general, we have different value sets with respect to meetings (and many other things).


oh?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From stpeter@stpeter.im  Wed Aug 24 13:17:50 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C243221F8ACE for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.468
X-Spam-Level: 
X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UunY6Fcaumjc for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:17:49 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB1621F8ACA for <ietf@ietf.org>; Wed, 24 Aug 2011 13:17:49 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 19FF64167D; Wed, 24 Aug 2011 14:21:19 -0600 (MDT)
Message-ID: <4E555CB2.7070405@stpeter.im>
Date: Wed, 24 Aug 2011 14:18:58 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net>
In-Reply-To: <4E555B06.6000108@dcrocker.net>
X-Enigmail-Version: 1.3
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:17:50 -0000

On 8/24/11 2:11 PM, Dave CROCKER wrote:

> ps.  As a personal aside, I'll note that I've lobbied rather vigorously
> for venues that entail less travel effort, by eliminating the additional
> hop needed to get from a major hub.  Note that that has gotten
> essentially zero support from the community.  The community has
> vigrously expressed a preference for "interesting" venues rather than
> ones that are chosen solely for logistics convenience.

As long as a relatively large percentage of IETF folks see meetings as
an opportunity to sight-see, I don't think we'll see much support for
rotating among a small set of major hub locations.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From geoff.ietf@mulligan.com  Wed Aug 24 13:20:40 2011
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A41B21F8C3E for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xtv3WCCwibU6 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:20:39 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id CB7A421F8B80 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:20:38 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id E6DC4184E0; Wed, 24 Aug 2011 14:21:52 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id 594AD15F504; Wed, 24 Aug 2011 14:21:45 -0600 (MDT)
Subject: Re: Hyatt Taipei cancellation policy?
From: Geoff Mulligan <geoff.ietf@mulligan.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <tslr54a8v7s.fsf@mit.edu>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com>  <tslr54a8v7s.fsf@mit.edu>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 14:21:49 -0600
Message-ID: <1314217309.1973.195.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:20:40 -0000

On Wed, 2011-08-24 at 15:28 -0400, Sam Hartman wrote:
> 1) We don't have to go to any particular location.  There has been an
> assumption made by people in this discussion that sometimes when we pick
> locations with particularly expensive hotels, we'll get particularly
> expensive meetings.  That's great except that we were the ones who chose
> to go to those locations.
> If we can't meet our cost targets at a location, go somewhere else.
> 

Sam makes a really good point here.  We didn't have to go to Taipei.
For some reason we chose to go to Taipei.  When the IAOC was looking at
places years ago was the dollar so strong that the hotel was cheap - I
doubt it.  It was probably just as expensive back then.  It should have
just been dropped from the list and the city as wel.  The hotel (and
host if there was on) could/should have been told - sorry too expensive.
There was never a requirement to go to Taipei.  

There was never a requirement to go to Maastricht with the 3 train
changes and hotels spread out and not under a single roof, awful
cancellation policy (unless you booked it separately from the IETF).
Nice place, but no one ordered us to go to Maastricht.

I liked Hiroshima, but even it was not easy to get to (multiple trains).

We seem to be limiting attendance to people from large companies just so
that we can meet everywhere in the world.  If it isn't relatively
inexpensive then we say, sorry we can't go there.  So what.  We don't
have to visit every country. 

I know that this is blasphemous but why can't we meet in just a couple
of the same places over and over again -- yeah it's boring for those
that want to be a tourist, but I go to work and would prefer a venue
that has good/easy access (major airport nearby) with a "cheapish" hotel
and a decent cancellation policy.

	geoff

PS - Lets just go to Minneapolis 3 times a year - bet we can get a great
rate and the US dollar is on-sale!





From dcrocker@bbiw.net  Wed Aug 24 13:22:48 2011
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA1021F8C18 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bf+sv5CVMVvf for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:22:47 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C905921F8C78 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:22:47 -0700 (PDT)
Received: from [192.168.1.3] (10.sub-166-250-34.myvzw.com [166.250.34.10]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7OKNkXe004869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 13:23:55 -0700
Message-ID: <4E555DCD.2000001@bbiw.net>
Date: Wed, 24 Aug 2011 13:23:41 -0700
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im>
In-Reply-To: <4E555CB2.7070405@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 24 Aug 2011 13:23:58 -0700 (PDT)
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:22:48 -0000

On 8/24/2011 1:18 PM, Peter Saint-Andre wrote:
> As long as a relatively large percentage of IETF folks see meetings as
> an opportunity to sight-see, I don't think we'll see much support for
> rotating among a small set of major hub locations.

+1

But it's worse than "relatively large percent".  There's absolutely no minority 
constituency that is vocal about wanting this to change.  That's why I declared 
myself giving up on this topic.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From stpeter@stpeter.im  Wed Aug 24 13:26:16 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD1321F8C8F for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:26:16 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E11STMFLrpPk for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:26:15 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B1A2C21F8C8D for <ietf@ietf.org>; Wed, 24 Aug 2011 13:26:15 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 58A8041683; Wed, 24 Aug 2011 14:29:45 -0600 (MDT)
Message-ID: <4E555EAD.1040505@stpeter.im>
Date: Wed, 24 Aug 2011 14:27:25 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Dave CROCKER <dcrocker@bbiw.net>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net>
In-Reply-To: <4E555DCD.2000001@bbiw.net>
X-Enigmail-Version: 1.3
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:26:16 -0000

On 8/24/11 2:23 PM, Dave CROCKER wrote:
> 
> 
> On 8/24/2011 1:18 PM, Peter Saint-Andre wrote:
>> As long as a relatively large percentage of IETF folks see meetings as
>> an opportunity to sight-see, I don't think we'll see much support for
>> rotating among a small set of major hub locations.
> 
> +1
> 
> But it's worse than "relatively large percent".  There's absolutely no
> minority constituency that is vocal about wanting this to change. 

I'd be perfectly happy to rotate among the same 5 or 6 places all the
time, but my motto is "dare to be dull". Plus I'm not sure how such a
policy would work with sponsorships, because a number of recent sponsors
presumably preferred the meeting to happen in their country for reasons
of national pride or convenience.

> That's why I declared myself giving up on this topic.

Sure, one can tilt at a particular windmill for only so long...

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From hartmans@mit.edu  Wed Aug 24 13:26:23 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F9B321F8C9D for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.667
X-Spam-Level: 
X-Spam-Status: No, score=-103.667 tagged_above=-999 required=5 tests=[AWL=-1.402, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zPCPjmMh8S5s for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:26:23 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id C8BD521F8C9C for <ietf@ietf.org>; Wed, 24 Aug 2011 13:26:22 -0700 (PDT)
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 426CD2043E; Wed, 24 Aug 2011 16:29:49 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 592F2423D; Wed, 24 Aug 2011 16:27:25 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: dcrocker@bbiw.net
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net>
Date: Wed, 24 Aug 2011 16:27:25 -0400
In-Reply-To: <4E555B06.6000108@dcrocker.net> (Dave CROCKER's message of "Wed,  24 Aug 2011 13:11:50 -0700")
Message-ID: <tslmxey8sia.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: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:26:23 -0000

>>>>> "Dave" == Dave CROCKER <dhc@dcrocker.net> writes:

    Dave> ps.  As a personal aside, I'll note that I've lobbied rather
    Dave> vigorously for venues that entail less travel effort, by
    Dave> eliminating the additional hop needed to get from a major hub.
    Dave> Note that that has gotten essentially zero support from the
    Dave> community.  The community has vigrously expressed a preference
    Dave> for "interesting" venues rather than ones that are chosen
    Dave> solely for logistics convenience.

Can you start by backing up the assertion  that the community has
vigrously expressed a preference for interesting venues?
I may just need a new IETF community:-)

From geoff.ietf@mulligan.com  Wed Aug 24 13:27:20 2011
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00E0A21F8CB8 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0S02KkXg2lih for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:27:19 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF9321F8CB7 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:27:19 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id 37A53184E0; Wed, 24 Aug 2011 14:28:32 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id 81D0315F504; Wed, 24 Aug 2011 14:28:24 -0600 (MDT)
Subject: Re: Hyatt Taipei cancellation policy?
From: Geoff Mulligan <geoff.ietf@mulligan.com>
To: Dave CROCKER <dcrocker@bbiw.net>
In-Reply-To: <4E555DCD.2000001@bbiw.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 14:28:28 -0600
Message-ID: <1314217708.1973.199.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:27:20 -0000

Maybe the majority doesn't care one way or the other - they will just go
wherever the meetings are held in which case:
  let's make them easy to get to
  cheap
  decent food
  one roof (with other hotels near-by)
  cheap
  and easy to get to

You could pick Rosemont, IL (next to O'hare) for every meeting (oops,
sorry - misses on decent food).

	geoff

On Wed, 2011-08-24 at 13:23 -0700, Dave CROCKER wrote:
> 
> On 8/24/2011 1:18 PM, Peter Saint-Andre wrote:
> > As long as a relatively large percentage of IETF folks see meetings as
> > an opportunity to sight-see, I don't think we'll see much support for
> > rotating among a small set of major hub locations.
> 
> +1
> 
> But it's worse than "relatively large percent".  There's absolutely no minority 
> constituency that is vocal about wanting this to change.  That's why I declared 
> myself giving up on this topic.
> 



From dcrocker@bbiw.net  Wed Aug 24 13:29:40 2011
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD8D121F8CA7 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TrojiZuSEc0W for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:29:40 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5C04B21F8CA2 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:29:40 -0700 (PDT)
Received: from [192.168.1.3] (10.sub-166-250-34.myvzw.com [166.250.34.10]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7OKUhxS005027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 13:30:50 -0700
Message-ID: <4E555F6E.3060105@bbiw.net>
Date: Wed, 24 Aug 2011 13:30:38 -0700
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>
In-Reply-To: <tslmxey8sia.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 24 Aug 2011 13:30:51 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:29:40 -0000

On 8/24/2011 1:27 PM, Sam Hartman wrote:
> Can you start by backing up the assertion  that the community has
> vigrously expressed a preference for interesting venues?
> I may just need a new IETF community:-)


gosh, I hadn't thought that that was less than obvious, given the vote for 
quebec and many, many comments about venue choice over the years.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From akatlas@gmail.com  Wed Aug 24 13:32:28 2011
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3B021F8CDF for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.533
X-Spam-Level: 
X-Spam-Status: No, score=-3.533 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lj6+9+bVQuGM for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:32:27 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7131C21F8CE2 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:32:27 -0700 (PDT)
Received: by pzk33 with SMTP id 33so3073917pzk.18 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yf7U1reugeJLt444K2ZgJgGRxwmbGTHOhWAa71HrLks=; b=XJPNKkbIQkxjBYvzYPDK5rJf17PQSiauFbfB57uKXiYsNozFh/pfU2TLXKfCM2VtEQ pRV1mcNtb3XjmiqxEO0aFnFL3x+ihNrQxjxcDwtGxtSKglhSb/sZkiKtrm+TfcHgOgW0 yKKuVKeQ8q9ZlfytKN++tn1xWSLOjum/mfCkY=
MIME-Version: 1.0
Received: by 10.142.238.13 with SMTP id l13mr3128835wfh.31.1314218018821; Wed, 24 Aug 2011 13:33:38 -0700 (PDT)
Received: by 10.68.41.201 with HTTP; Wed, 24 Aug 2011 13:33:38 -0700 (PDT)
In-Reply-To: <4E555F6E.3060105@bbiw.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net>
Date: Wed, 24 Aug 2011 16:33:38 -0400
Message-ID: <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
From: Alia Atlas <akatlas@gmail.com>
To: Dave CROCKER <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=000e0cd2440c2b560104ab463a30
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:32:28 -0000

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

On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER <dcrocker@bbiw.net> wrote:

>
>
> On 8/24/2011 1:27 PM, Sam Hartman wrote:
>
>> Can you start by backing up the assertion  that the community has
>> vigrously expressed a preference for interesting venues?
>> I may just need a new IETF community:-)
>>
>
>
> gosh, I hadn't thought that that was less than obvious, given the vote for
> quebec and many, many comments about venue choice over the years.


I'm one who really liked Minneapolis - we had excellent meeting space,
places to run into each other, reasonable food access, and a clueful hotel.

Is it interesting to go to new places?  Sure and if I'm lucky I might get a
morning or afternoon to look around.  Would I be perfectly happy going to
the same 2-3 places every year?  Absolutely.

Alia

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

<div class=3D"gmail_quote">On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:dcrocker@bbiw.net">dcrocker@bbiw.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;">
<div class=3D"im"><br>
<br>
On 8/24/2011 1:27 PM, Sam Hartman wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Can you start by backing up the assertion =A0that the community has<br>
vigrously expressed a preference for interesting venues?<br>
I may just need a new IETF community:-)<br>
</blockquote>
<br>
<br></div>
gosh, I hadn&#39;t thought that that was less than obvious, given the vote =
for quebec and many, many comments about venue choice over the years.<font =
color=3D"#888888"></font></blockquote><div><br>I&#39;m one who really liked=
 Minneapolis - we had excellent meeting space, places to run into each othe=
r, reasonable food access, and a clueful hotel.<br>
<br>Is it interesting to go to new places?=A0 Sure and if I&#39;m lucky I m=
ight get a morning or afternoon to look around.=A0 Would I be perfectly hap=
py going to the same 2-3 places every year?=A0 Absolutely.<br><br>Alia <br>=
</div>
</div>

--000e0cd2440c2b560104ab463a30--

From randy@qualcomm.com  Wed Aug 24 13:33:52 2011
Return-Path: <randy@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B4D21F8CFE for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level: 
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PNAcFP1-xoKa for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:33:51 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 9B78B21F8CFD for <ietf@ietf.org>; Wed, 24 Aug 2011 13:33:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1314218103; x=1345754103; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240611ca7b0f76e68f@[172.16.1.69]> |In-Reply-To:=20<6.2.5.6.2.20110824075034.06819068@resist or.net>|References:=20<20110822191708.652C721F8C19@ietfa. amsl.com>=0D=0A=20<801FB726-F672-4F7F-8D9C-7ED37DB08672@c s.ucla.edu>=0D=0A=20<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04 @isoc.org>=0D=0A=20<66998320DD3FCC5628E32634@PST.JCK.COM> =0D=0A=20<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> =0D=0A=20<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-he retics.com>=0D=0A=20<34E4F50CAFA10349A41E0756550084FB0D55 7960@PRVPEXVS04.corp.twcable.com>=0D=0A=20<6.2.5.6.2.2011 0824075034.06819068@resistor.net>|X-Mailer:=20Eudora=20fo r=20Mac=20OS=20X|Date:=20Wed,=2024=20Aug=202011=2013:29:4 8=20-0700|To:=20SM=20<sm@resistor.net>,=20<ietf@ietf.org> |From:=20Randall=20Gellens=20<randy@qualcomm.com> |Subject:=20Re:=20IAOC,=20travel=20and=20hotel=20prices =20(was=20RE:=20Hyatt=20Taipei=20=0D=0A=20cancellation=20 policy?)|MIME-Version:=201.0|Content-Type:=20text/plain =3B=20charset=3D"us-ascii"=3B=20format=3Dflowed |X-Random-Sig-Tag:=201.0b28|X-Originating-IP:=20[172.30.4 8.1]; bh=OEIAHZfhNLcWElazzDEz6pg7rJTj3+SHEieh8n/Gxlo=; b=gLPjQjxkjFDZNY1XHefK6sJAwLbHAoE9MJLF6R9wEBxKTGJ1PUI1Q9R3 yvFc89Sc3/5KmzhBUBB3hnATyv+LsS+yZlnvybOTN/3WzaB1/XrEm9X6H WHMxBmMlBmCiRHcxysgREacmgnENwi8oiSElY1mUCgcSseni7Be3TQZMN 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,6448"; a="112495138"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 24 Aug 2011 13:35:03 -0700
X-IronPort-AV: E=Sophos;i="4.68,275,1312182000"; d="scan'208";a="102826066"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 24 Aug 2011 13:35:03 -0700
Received: from [172.16.1.69] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Aug 2011 13:35:02 -0700
Message-ID: <p06240611ca7b0f76e68f@[172.16.1.69]>
In-Reply-To: <6.2.5.6.2.20110824075034.06819068@resistor.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com> <6.2.5.6.2.20110824075034.06819068@resistor.net>
X-Mailer: Eudora for Mac OS X
Date: Wed, 24 Aug 2011 13:29:48 -0700
To: SM <sm@resistor.net>, <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: IAOC, travel and hotel prices (was RE: Hyatt Taipei  cancellation policy?)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:33:52 -0000

At 10:49 AM -0700 8/24/11, SM wrote:

>  Is there any hypothesis about why this type of discussion does not 
> occur when a venue in the U.S. is selected?

Maybe because when the venue is in the U.S., hotel prices tend to be 
lower, and immigration hassles (fingerprints and rude treatment) and 
visa problems dominate the complaints?

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
...neither the whole of truth nor the whole of good is revealed
to any single observer, although each observer gains a partial
superiority of insight from the peculiar position in which he
stands.'                                      --William James, 1899

From tnadeau@lucidvision.com  Wed Aug 24 13:38:22 2011
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B7721F8D2B for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6XEcW8IYmdt for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:38:21 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 76C1421F8D2A for <ietf@ietf.org>; Wed, 24 Aug 2011 13:38:20 -0700 (PDT)
Received: from [192.168.1.104] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 677121DA44CE; Wed, 24 Aug 2011 16:39:31 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: multipart/alternative; boundary="Apple-Mail=_7A9FC309-32EC-43A6-9049-55AFF2E1EEE3"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com>
Date: Wed, 24 Aug 2011 16:39:27 -0400
Message-Id: <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Sam Hartman <hartmans-ietf@mit.edu>, Dave CROCKER <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:38:22 -0000

--Apple-Mail=_7A9FC309-32EC-43A6-9049-55AFF2E1EEE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Aug 24, 2011, at 4:33 PM, Alia Atlas wrote:

> On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER <dcrocker@bbiw.net> =
wrote:
>=20
>=20
> On 8/24/2011 1:27 PM, Sam Hartman wrote:
> Can you start by backing up the assertion  that the community has
> vigrously expressed a preference for interesting venues?
> I may just need a new IETF community:-)
>=20
>=20
> gosh, I hadn't thought that that was less than obvious, given the vote =
for quebec and many, many comments about venue choice over the years.
>=20
> I'm one who really liked Minneapolis - we had excellent meeting space, =
places to run into each other, reasonable food access, and a clueful =
hotel.
>=20
> Is it interesting to go to new places?  Sure and if I'm lucky I might =
get a morning or afternoon to look around.  Would I be perfectly happy =
going to the same 2-3 places every year?  Absolutely.

	I am with you on that. I do not attend IETFs as a vacation and =
sight-seeing opportunity.

	--Tom


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


--Apple-Mail=_7A9FC309-32EC-43A6-9049-55AFF2E1EEE3
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 24, 2011, at 4:33 PM, Alia Atlas wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER <span dir="ltr">&lt;<a href="mailto:dcrocker@bbiw.net">dcrocker@bbiw.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
On 8/24/2011 1:27 PM, Sam Hartman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can you start by backing up the assertion &nbsp;that the community has<br>
vigrously expressed a preference for interesting venues?<br>
I may just need a new IETF community:-)<br>
</blockquote>
<br>
<br></div>
gosh, I hadn't thought that that was less than obvious, given the vote for quebec and many, many comments about venue choice over the years.<font color="#888888"></font></blockquote><div><br>I'm one who really liked Minneapolis - we had excellent meeting space, places to run into each other, reasonable food access, and a clueful hotel.<br>
<br>Is it interesting to go to new places?&nbsp; Sure and if I'm lucky I might get a morning or afternoon to look around.&nbsp; Would I be perfectly happy going to the same 2-3 places every year?&nbsp; Absolutely.<br></div></div></blockquote><div><br></div><span class="Apple-tab-span" style="white-space:pre">	</span>I am with you on that. I do not attend IETFs as a vacation and sight-seeing opportunity.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre">	</span>--Tom</div><div><br></div><div><br><blockquote type="cite"><div class="gmail_quote"><div><br>Alia <br></div>
</div>
_______________________________________________<br>Ietf mailing list<br><a href="mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>https://www.ietf.org/mailman/listinfo/ietf<br></blockquote></div><br></body></html>
--Apple-Mail=_7A9FC309-32EC-43A6-9049-55AFF2E1EEE3--

From dcrocker@bbiw.net  Wed Aug 24 13:55:00 2011
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1CC21F8C20 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KAbql1ibh7vV for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:54:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA6D21F8C06 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:54:59 -0700 (PDT)
Received: from [192.168.1.3] (10.sub-166-250-34.myvzw.com [166.250.34.10]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7OKu1AT005795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 13:56:10 -0700
Message-ID: <4E55655C.6030502@bbiw.net>
Date: Wed, 24 Aug 2011 13:55:56 -0700
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: geoff <geoff@proto6.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430>
In-Reply-To: <1314218041.1973.204.camel@d430>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 24 Aug 2011 13:56:11 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:55:00 -0000

On 8/24/2011 1:34 PM, geoff wrote:
> I agree.  I think that there is a vocal minority that wants this.  I
> don't think that community as a whole really cares.


Sorry, but the vote on Quebec City, and the recent, follow-on commentary are far 
more substantial and proportionally dominant than a "vocal minority".

If there is, indeed, a significant constituency that would prefer a strict focus 
on -- for example -- cost, to the exclusion of such things as -- for example -- 
going to new venues, it needs to speak up and make its requirements far more 
clear and consensus-based than has happened so far.

Stray postings of personal preference might help to start the process, but they 
won't achieve much on their own.

d/

ps. Underlying any sort of change to the model is a change in the nature of 
host/sponsor recruitment.  The current approach uses new venues to aid in 
finding new sponsors.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From melinda.shore@gmail.com  Wed Aug 24 13:56:00 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80A8721F8C6D for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wbu+uqdy3DKB for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:56:00 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 817D921F8C6C for <ietf@ietf.org>; Wed, 24 Aug 2011 13:55:59 -0700 (PDT)
Received: by pzk33 with SMTP id 33so3132907pzk.18 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:57:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mxrD3XrAQnjMRj2stbKD2ybE2U7BUyMCbZaJMoXcnpI=; b=u3o6u4cXtHrzNRkJxW16u6deqmITuD8a+6R8eOjC8DLVsnxPqcCanOYDKRMI6v1CG2 XM015fipvCSNa1hYit0lcRzZjIWxAf/MTUx9Q28fKCOPEnRePgrjbFSYHHgbJcK4beud 2E/Vfyi3KTiCrKr4TbgC9VDeN1T8ZoqN0epOo=
Received: by 10.143.97.19 with SMTP id z19mr2955481wfl.317.1314219430921; Wed, 24 Aug 2011 13:57:10 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu [137.229.12.236]) by mx.google.com with ESMTPS id g14sm660152wfh.10.2011.08.24.13.57.08 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 13:57:09 -0700 (PDT)
Message-ID: <4E5565A6.1020508@gmail.com>
Date: Wed, 24 Aug 2011 12:57:10 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: Dave CROCKER <dcrocker@bbiw.net>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net>
In-Reply-To: <4E555DCD.2000001@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:56:00 -0000

On 08/24/2011 12:23 PM, Dave CROCKER wrote:
> But it's worse than "relatively large percent". There's absolutely no
> minority constituency that is vocal about wanting this to change. That's
> why I declared myself giving up on this topic.

I wonder how many of us have done exactly this.

One of the most productive meetings I've ever participated in was
a conference program committee meeting at the Logan Hilton.  No
distractions and everybody was there to work.

Melinda



From d3e3e3@gmail.com  Wed Aug 24 13:57:56 2011
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE7E921F8DA2 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.235
X-Spam-Level: 
X-Spam-Status: No, score=-104.235 tagged_above=-999 required=5 tests=[AWL=-0.636, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFQC2B57Kbqn for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:57:56 -0700 (PDT)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id B1CF721F8DA1 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:57:55 -0700 (PDT)
Received: by iye1 with SMTP id 1so2433468iye.27 for <ietf@ietf.org>; Wed, 24 Aug 2011 13:59:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=ghGSm3ode8qrG2BlJTWNDMDX9W5FtZbKRvscTod978E=; b=WcO1anbd+uKyW7PCkTjvndWadNKpciMGvgGZHgs7vM5mCzzlZFCwr+je6soGS6fMhu q1wSHk+q7vrgLvHPvnOOqzFodpegx9eK4I1F1+936xxwsTTnegOc1Evm7uziRWiP0I34 6q/Yz0Jq+84t4CvblKmb70mtbAz3RGxH3tunE=
Received: by 10.231.41.69 with SMTP id n5mr10955905ibe.92.1314219546064; Wed, 24 Aug 2011 13:59:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.182.4 with HTTP; Wed, 24 Aug 2011 13:58:46 -0700 (PDT)
In-Reply-To: <1314217708.1973.199.camel@d430>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net> <1314217708.1973.199.camel@d430>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 24 Aug 2011 16:58:46 -0400
Message-ID: <CAF4+nEESUOzqu_WiP6BFEGvRqGYEO+69rN2EMk-_HRn96ueqkg@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
To: Geoff Mulligan <geoff.ietf@mulligan.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:57:56 -0000

On Wed, Aug 24, 2011 at 4:28 PM, Geoff Mulligan <geoff.ietf@mulligan.com> w=
rote:
>
> ...
>
> You could pick Rosemont, IL (next to O'hare) for every meeting (oops,
> sorry - misses on decent food).

Minneapolis or Chicago, one place doesn't make it. The policy of the
IETF has been to meet where the attendees come from, although with
some projection into the future. So I thought we were currently trying
to equalize meetings in North America, Europe, and Asia. So it is an
absolute minimum of three places.

Donald

> =A0 =A0 =A0 =A0geoff
>
> On Wed, 2011-08-24 at 13:23 -0700, Dave CROCKER wrote:
> >
> > On 8/24/2011 1:18 PM, Peter Saint-Andre wrote:
> > > As long as a relatively large percentage of IETF folks see meetings a=
s
> > > an opportunity to sight-see, I don't think we'll see much support for
> > > rotating among a small set of major hub locations.
> >
> > +1
> >
> > But it's worse than "relatively large percent". =A0There's absolutely n=
o minority
> > constituency that is vocal about wanting this to change. =A0That's why =
I declared
> > myself giving up on this topic.
> >
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From ole@cisco.com  Wed Aug 24 14:10:08 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D19C821F8B2D for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:10:08 -0700 (PDT)
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.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EzKDbTs20QhE for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:10:07 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 6947121F86AA for <ietf@ietf.org>; Wed, 24 Aug 2011 14:10:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=548; q=dns/txt; s=iport; t=1314220279; x=1315429879; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=VJYERV2KbfEPBGRrcD58OonUCLGhoooSMEm1OU//Jw4=; b=PV2hI1EdfqJAtfJx5z4saXZ2NaQ2zz06eKjO5gnpYdRNDO0AFUqSSbwT hrsxvlVTmiya65XqichLWDctaGqA6V1yKv1ltUh9j+svze8+Ta9Pf9GjF RqFVApLpEjfRpB9qtSGbaRHYffSB0Bs7IImdhk98tyVL8X/U5QF++GzUu U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKdnVU6rRDoI/2dsb2JhbABCqAB3gUABAQEBAgESAQIBJD8FCwtGVwY1h0+bFQGDJg8Bm2KGSQSHYZxT
X-IronPort-AV: E=Sophos;i="4.68,277,1312156800"; d="scan'208";a="16208147"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-5.cisco.com with ESMTP; 24 Aug 2011 21:10:54 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7OLAsMR016936; Wed, 24 Aug 2011 21:10:54 GMT
Date: Wed, 24 Aug 2011 14:10:53 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Dave CROCKER <dcrocker@bbiw.net>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <4E55655C.6030502@bbiw.net>
Message-ID: <alpine.OSX.2.01.1108241408280.7436@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: geoff <geoff@proto6.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 21:10:09 -0000

On Wed, 24 Aug 2011, Dave CROCKER wrote:

> ps. Underlying any sort of change to the model is a change in the nature of
> host/sponsor recruitment.  The current approach uses new venues to aid in
> finding new sponsors.

Not quite. But you are correct that sponsors/hosts often strongly 
influence the choice of venue and let's not forget that there are 
places (China for example) where we could NOT do a meeting without
a host [regardless of any financial considerations]. There may not
be many such places, but the do exist.

Ole

From moore@network-heretics.com  Wed Aug 24 14:11:53 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30A0C21F8CE5 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.458
X-Spam-Level: 
X-Spam-Status: No, score=-3.458 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id swDO6lJ4te9V for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:11:52 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 6060E21F8CDE for <ietf@ietf.org>; Wed, 24 Aug 2011 14:11:52 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id C4F3B212E5 for <ietf@ietf.org>; Wed, 24 Aug 2011 17:13:03 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 24 Aug 2011 17:13:03 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:message-id:references:to; s=smtpout; bh=h3Z989 0AS5Sgot4AFWCxwLXWK+E=; b=nbuVNi42sTccOwrZde+1feqY/CV7BI4BiLc9Ln 5+Eieh4crkuNqzHLswcBEVfCAzR4gxVS2f8WTBpbShgFfuq7Qcv7KLACXKWAi17V Q3f+BsiVs8uRvlCLB8vd4PeVZqKRUAQNc3Yn/SxeuP2HYFw8oBFN0ztief1vvioo 8cWVQ=
X-Sasl-enc: 6gcL7dj0J5Lcm43LEuJFZFPZ0xG/dO15tHbh8fByiUVq 1314220383
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id CAB0B900B9C; Wed, 24 Aug 2011 17:13:02 -0400 (EDT)
Subject: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-13-905710725
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E55655C.6030502@bbiw.net>
Date: Wed, 24 Aug 2011 17:12:39 -0400
Message-Id: <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 21:11:53 -0000

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

Maybe there needs to be some sort of voting system for future venues.

You'd be eligible to vote if you'd attended an IETF anytime within the =
past, say, 2 years - or if you were willing to commit to attending the =
one you vote on if it wins.  (say by putting down a deposit toward =
meeting fees).

Instead of picking one venue, the committee would solicit bids from N =
(say 3-4) different venues within a geographic region.    The bids would =
include:
room cost per night in the conference hotel
room cost per night in each of some small number of alternate hotels
locations of said hotels and nature of transportation between there and =
the conference venue
meeting fee for the entire week if that venue is chosen
other pertinent information (like what kind of food is nearby, what kind =
of facilities there are in or near the venue for impromptu gathering, =
what kinds of sightseeing opportunities there are, etc.)
The committee would survey attendees from time to time and tell the =
prospective venues what kinds of criteria the attendees found important, =
so they'd know how best to make their pitch.

Every eligible voter would get one vote.  There would be a strict =
deadline for submitting bids, and a strict deadline for voting.

That way, everyone could figure his own travel costs, factor in his own =
willingness to stay further away for less cost, etc.

Keith


--Apple-Mail-13-905710725
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; ">Maybe =
there needs to be some sort of voting system for future =
venues.<div><br></div><div>You'd be eligible to vote if you'd attended =
an IETF anytime within the past, say, 2 years - or if you were willing =
to commit to attending the one you vote on if it wins. &nbsp;(say by =
putting down a deposit toward meeting =
fees).</div><div><br></div><div>Instead of picking one venue, the =
committee would solicit bids from N (say 3-4) different venues within a =
geographic region. &nbsp; &nbsp;The bids would =
include:</div><div><ul><li>room cost per night in the conference =
hotel</li><li>room cost per night in each of some small number of =
alternate hotels</li><li>locations of said hotels and nature of =
transportation between there and the conference venue</li><li>meeting =
fee for the entire week if that venue is chosen</li><li>other pertinent =
information (like what kind of food is nearby, what kind of facilities =
there are in or near the venue for impromptu gathering, what kinds of =
sightseeing opportunities there are, etc.)</li></ul><div>The committee =
would survey attendees from time to time and tell the prospective venues =
what kinds of criteria the attendees found important, so they'd know how =
best to make their pitch.</div><div><br></div><div>Every eligible voter =
would get one vote. &nbsp;There would be a strict deadline for =
submitting bids, and a strict deadline for =
voting.</div></div><div><br></div><div>That way, everyone could figure =
his own travel costs, factor in his own willingness to stay further away =
for less cost, =
etc.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-13-905710725--

From narten@us.ibm.com  Wed Aug 24 14:29:10 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5959B21F8D6E for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.453
X-Spam-Level: 
X-Spam-Status: No, score=-106.453 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPv+fFni+4Ou for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:29:09 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id B967421F8D70 for <ietf@ietf.org>; Wed, 24 Aug 2011 14:29:09 -0700 (PDT)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7ODrGEw013855 for <ietf@ietf.org>; Wed, 24 Aug 2011 07:53:16 -0600
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7OLSvhf170008 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:28:57 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7OLStb6000647 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:28:56 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-218-237.mts.ibm.com [9.65.218.237]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7OLSscF032707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 15:28:55 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7OLSq4i011660; Wed, 24 Aug 2011 17:28:53 -0400
Message-Id: <201108242128.p7OLSq4i011660@cichlid.raleigh.ibm.com>
To: Geoff Mulligan <geoff.ietf@mulligan.com>
Subject: Re: Hyatt Taipei cancellation policy?
In-reply-to: <1314217708.1973.199.camel@d430>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net> <1314217708.1973.199.camel@d430>
Comments: In-reply-to Geoff Mulligan <geoff.ietf@mulligan.com> message dated "Wed, 24 Aug 2011 14:28:28 -0600."
Date: Wed, 24 Aug 2011 17:28:52 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: Sam Hartman <hartmans-ietf@mit.edu>, Dave CROCKER <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 21:29:10 -0000

Geoff Mulligan <geoff.ietf@mulligan.com> writes:

> Maybe the majority doesn't care one way or the other - they will just go
> wherever the meetings are held in which case:
>   let's make them easy to get to
>   cheap
>   decent food
>   one roof (with other hotels near-by)
>   cheap
>   and easy to get to

Having watched this debate play out in multiple venues (ICANN goes all
around the world 3x a year as well) over multiple years, I've come to
the following main conclusion:

1) you can't please all the people all the time, and there will be
griping no matter what we do. We've got 1200 attendees. That's a lot
of folk who have differing ideas of what is important. 

2) There is no perfect solution. There are too many variables, not all
of which are known in advance. And, everyone weighs various factors
differently. Convenience of travel, for instance, is very different
for US-based folk vs. Chinese and Australians.

3) The absolutely most important thing to get right is a meeting venue
that works for getting work done. In my mind, the really key things
here are:

  a) everyone can (easily) walk to the meeting site (this facilitates
     mingling, including at the bar)
     
  b) there is ample local food within walking distance (again for
     mingling/meetings)

  c) proper facilities (adequate meeting room, wireless, range of room
     rate options, and yes, I suppose cookies, etc.)

If you get the above right, the other inconveniences don't matter
(except maybe visa hassles). Or more precisely, folk can (and just
should) deal with it.

Seriously, taking one extra plane hop (or gasp! riding a train!) is
just noise, when talking about a meeting that lasts 5+ solid days.
I'd much rather take an extra hop to get to a meeting venue that works
well, then save a few hours travel time to reach a venue that doesn't
have places to eat.

Etc.

Hub cities are no panacea. I too like Minneapolis. As a venue, it
meets the key IETF needs as better than most places we've visited. It
has good airline connectivity (not perfect, but good). It meets the
key criteria above. You can also walk everywhere underground in the
winter, so the argument that it's "too cold" seems specious. Etc.

But does everyone like Minneapolis? Apparently not. I'm told that the
IAOC has stopped going there because they were getting too many
complaints. People do get tired of going to the same places, even if a
location works.

I've concluded that going to new places is better than hubs. Even
though I rarely take vacation in conjunction with meetings, getting
1/2 a day to sight see or even being able to walk into town for dinner
in a new location is a positive thing over being at the same places
too often.

Thomas

From tjc@ecs.soton.ac.uk  Wed Aug 24 14:29:51 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 799D921F8D88 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=0.602,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Arp3-LyA6euc for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:29:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 7B98721F8D6E for <ietf@ietf.org>; Wed, 24 Aug 2011 14:29:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7OLUvVn002243 for <ietf@ietf.org>; Wed, 24 Aug 2011 22:30:57 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p7OLUvVn002243
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1314221457; bh=3ecrBF9eek5pqavTfev1c2kHk94=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=Vr+Rlkyx4Rd7nT2imivV2kCE0ABMniyHw0l6MF8nfNjaXAwirvBIvla01svbtiUCV 8XVdYXljfmF3kCShuy/X5Wa+JwJGypvumssMKEiNkBeVN/ryDFKKUTBHBuibpDQCTO sCMKnKz6udnmCgmSXLZeuGmV1V6pNKKru95adiP0=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n7NMUv0366114070hO ret-id none; Wed, 24 Aug 2011 22:30:57 +0100
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7OLUnQF018902 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Wed, 24 Aug 2011 22:30:50 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: Hyatt Taipei cancellation policy?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAF4+nEESUOzqu_WiP6BFEGvRqGYEO+69rN2EMk-_HRn96ueqkg@mail.gmail.com>
Date: Wed, 24 Aug 2011 22:30:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|5b8fcd876016714cebb89d0ce7c43212n7NMUv03tjc|ecs.soton.ac.uk|AD133A17-91EE-436A-9AA2-C62149928FCD@ecs.soton.ac.uk>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net> <1314217708.1973.199.camel@d430> <CAF4+nEESUOzqu_WiP6BFEGvRqGYEO+69rN2EMk-_HRn96ueqkg@mail.gmail.com> <AD133A17-91EE-436A-9AA2-C62149928FCD@ecs.soton.ac.uk>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n7NMUv036611407000; tid=n7NMUv0366114070hO; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p7OLUvVn002243
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 21:29:51 -0000

On 24 Aug 2011, at 21:58, Donald Eastlake wrote:

> On Wed, Aug 24, 2011 at 4:28 PM, Geoff Mulligan =
<geoff.ietf@mulligan.com> wrote:
>>=20
>> ...
>>=20
>> You could pick Rosemont, IL (next to O'hare) for every meeting (oops,
>> sorry - misses on decent food).
>=20
> Minneapolis or Chicago, one place doesn't make it. The policy of the
> IETF has been to meet where the attendees come from, although with
> some projection into the future. So I thought we were currently trying
> to equalize meetings in North America, Europe, and Asia. So it is an
> absolute minimum of three places.

That's a fair point, and the three region split is in principle the =
right thing to do.  But I think Taipei's prices are the highest I've =
seen for the venue hotel, and the organising committee should take note =
of the comments about that, and the cancellation policy, for future =
venue selections.

I am also a fan of Minneapolis.  I just looked at Hilton IETF venue =
prices there for the IETF82 week.  There are king rooms under $200 a =
night direct from the hotel with a good cancellation policy, and that's =
without any negotiated price.  That's a $500-$600 difference in cost =
over the 5-6 nights people would typically stay.

I'm interested in how much sponsors contribute, and how that compares to =
$500 less in hotel fees over a week times 1,200 attendees.

The Hilton Prague also has rooms at $200 the same week.

The idea of exploring a university campus is an interesting one.

Tim=

From brian.e.carpenter@gmail.com  Wed Aug 24 14:31:38 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28DA421F8C3F for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJBNPYKolmSE for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:31:37 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF9821F8C2A for <ietf@ietf.org>; Wed, 24 Aug 2011 14:31:37 -0700 (PDT)
Received: by qwc23 with SMTP id 23so1291011qwc.31 for <ietf@ietf.org>; Wed, 24 Aug 2011 14:32:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RayTMhKL6M0jRqH0YH4F6r7bAFLLLYvsKhiQrnKc5wQ=; b=hDAnpBgmauPO9bQw3KuqbOE/XhpGIuzlJ//8m46C8zg4b+LmLNFn8OhDeqldJ0y9gI b8dgzwyOzMLm/84fMzp9xmAp32PQIcUPyurvEhIK6+WzmRDkZWFX6HvZjN7DoaBBiSoi JM0YxHeJu0iMB+20BDhVdcknJ73006vuxchVc=
Received: by 10.224.213.196 with SMTP id gx4mr3369023qab.98.1314221568843; Wed, 24 Aug 2011 14:32:48 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id gr10sm2454602qab.12.2011.08.24.14.32.46 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 14:32:48 -0700 (PDT)
Message-ID: <4E556DFC.5060705@gmail.com>
Date: Thu, 25 Aug 2011 09:32:44 +1200
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: Keith Moore <moore@network-heretics.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>
In-Reply-To: <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 21:31:38 -0000

Keith,

I would be amazed if any major hotel or convention centre would allow its
bid to be made public in this way. I too am disturbed by the Taipei hotel
rate, but I know from my own time on the IAOC that matching bids, dates,
hosts and all the other constraints is essentially an insoluble problem.

It would be interesting if someone with historical data could plot IETF
hotel and meeting fee costs over the years since 1986, normalized to take
account of inflation and trade-weighted currency variations. I really
can't guess what the outcome would be.

Regards
   Brian Carpenter

On 2011-08-25 09:12, Keith Moore wrote:
> Maybe there needs to be some sort of voting system for future venues.
> 
> You'd be eligible to vote if you'd attended an IETF anytime within the past, say, 2 years - or if you were willing to commit to attending the one you vote on if it wins.  (say by putting down a deposit toward meeting fees).
> 
> Instead of picking one venue, the committee would solicit bids from N (say 3-4) different venues within a geographic region.    The bids would include:
> room cost per night in the conference hotel
> room cost per night in each of some small number of alternate hotels
> locations of said hotels and nature of transportation between there and the conference venue
> meeting fee for the entire week if that venue is chosen
> other pertinent information (like what kind of food is nearby, what kind of facilities there are in or near the venue for impromptu gathering, what kinds of sightseeing opportunities there are, etc.)
> The committee would survey attendees from time to time and tell the prospective venues what kinds of criteria the attendees found important, so they'd know how best to make their pitch.
> 
> Every eligible voter would get one vote.  There would be a strict deadline for submitting bids, and a strict deadline for voting.
> 
> That way, everyone could figure his own travel costs, factor in his own willingness to stay further away for less cost, etc.
> 
> Keith
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From eburger-l@standardstrack.com  Wed Aug 24 14:47:42 2011
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4CD21F8D72 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74St1y7J8VFJ for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 14:47:41 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4AB21F8D2A for <ietf@ietf.org>; Wed, 24 Aug 2011 14:47:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=1WykQ5TJKAFBMC6PuxgU9AoMFoCS+ItW42O+jXJgqCeWYBIQBfPJ12UwUXu3JKVaKQG6DY4ECMy66/ddUb4z95Ufva2b1r2m8M+NnPEeTpmzHR8W0lNozudhN2PqVkqq;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QwLJa-0006Xa-Vz for ietf@ietf.org; Wed, 24 Aug 2011 14:48:51 -0700
From: Eric Burger <eburger-l@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-103-907880094
Subject: Re: voting system for future venues?
Date: Wed, 24 Aug 2011 17:48:49 -0400
In-Reply-To: <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>
To: IETF-Discussion list <ietf@ietf.org>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>
Message-Id: <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 21:47:42 -0000

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

Just a reminder, the community VOTED for Quebec City.

Backing up Dave here, the community repeatedly VOTES or, in post-meeting =
surveys, INDICATES (VOTES) for the sort of venues we have been booking.

Let me say it one more time: I have stayed at hotels for between =
one-half and one-seventh the price of the IETF hotel. Instead of griping =
about the IETF hotel, WHICH SEEMS TO ALWAYS SELL OUT, I save my money =
(it's my money!) and stay at the nearby hotel. Who cares if the IETF =
hotel is expensive, so long as I am not barred from visiting the bar?

Speaking for myself (I am NOT on the venue selection committee - I'll =
let them speak for themselves), I would offer that one has to ask =
oneself what one is really asking the IAOC to *do*?  We find venues that =
are all under one roof (check), have food near by (OK, Maastricht was a =
bomb, but we analyzed the root cause of that and it should not happen =
again), is relatively easy to get to for a not stupidly expensive amount =
of money (check), is relatively close to some critical mass of active =
IETF participants (check), and have options for people on a budget =
(check).

Let's ask again: what is it you WANT?

This is getting beyond Steve's "you cannot satisfy all of the people all =
of the time."

On Aug 24, 2011, at 5:12 PM, Keith Moore wrote:

> Maybe there needs to be some sort of voting system for future venues.
>=20
> You'd be eligible to vote if you'd attended an IETF anytime within the =
past, say, 2 years - or if you were willing to commit to attending the =
one you vote on if it wins.  (say by putting down a deposit toward =
meeting fees).
>=20
> Instead of picking one venue, the committee would solicit bids from N =
(say 3-4) different venues within a geographic region.    The bids would =
include:
> room cost per night in the conference hotel
> room cost per night in each of some small number of alternate hotels
> locations of said hotels and nature of transportation between there =
and the conference venue
> meeting fee for the entire week if that venue is chosen
> other pertinent information (like what kind of food is nearby, what =
kind of facilities there are in or near the venue for impromptu =
gathering, what kinds of sightseeing opportunities there are, etc.)
> The committee would survey attendees from time to time and tell the =
prospective venues what kinds of criteria the attendees found important, =
so they'd know how best to make their pitch.
>=20
> Every eligible voter would get one vote.  There would be a strict =
deadline for submitting bids, and a strict deadline for voting.
>=20
> That way, everyone could figure his own travel costs, factor in his =
own willingness to stay further away for less cost, etc.
>=20
> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-103-907880094
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; ">Just =
a reminder, the community VOTED for Quebec =
City.<div><br></div><div>Backing up Dave here, the community repeatedly =
VOTES or, in post-meeting surveys, INDICATES (VOTES) for the sort of =
venues we have been booking.</div><div><br></div><div>Let me say it one =
more time: I have stayed at hotels for between one-half and one-seventh =
the price of the IETF hotel. Instead of griping about the IETF hotel, =
WHICH SEEMS TO ALWAYS SELL OUT, I save my money (it's my money!) and =
stay at the nearby hotel. Who cares if the IETF hotel is expensive, so =
long as I am not barred from visiting the =
bar?</div><div><br></div><div>Speaking for myself (I am NOT on the venue =
selection committee - I'll let them speak for themselves), I would offer =
that one has to ask oneself what one is really asking the IAOC to *do*? =
&nbsp;We find venues that are all under one roof (check), have food near =
by (OK, Maastricht was a bomb, but we analyzed the root cause of that =
and it should not happen again), is relatively easy to get to for a not =
stupidly expensive amount of money (check), is relatively close to some =
critical mass of active IETF participants (check), and have options for =
people on a budget (check).</div><div><br></div><div>Let's ask again: =
what is it you WANT?</div><div><br></div><div>This is getting beyond =
Steve's "you cannot satisfy all of the people all of the =
time."<br><div><br><div><div>On Aug 24, 2011, at 5:12 PM, Keith Moore =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">Maybe there needs to be =
some sort of voting system for future venues.<div><br></div><div>You'd =
be eligible to vote if you'd attended an IETF anytime within the past, =
say, 2 years - or if you were willing to commit to attending the one you =
vote on if it wins. &nbsp;(say by putting down a deposit toward meeting =
fees).</div><div><br></div><div>Instead of picking one venue, the =
committee would solicit bids from N (say 3-4) different venues within a =
geographic region. &nbsp; &nbsp;The bids would =
include:</div><div><ul><li>room cost per night in the conference =
hotel</li><li>room cost per night in each of some small number of =
alternate hotels</li><li>locations of said hotels and nature of =
transportation between there and the conference venue</li><li>meeting =
fee for the entire week if that venue is chosen</li><li>other pertinent =
information (like what kind of food is nearby, what kind of facilities =
there are in or near the venue for impromptu gathering, what kinds of =
sightseeing opportunities there are, etc.)</li></ul><div>The committee =
would survey attendees from time to time and tell the prospective venues =
what kinds of criteria the attendees found important, so they'd know how =
best to make their pitch.</div><div><br></div><div>Every eligible voter =
would get one vote. &nbsp;There would be a strict deadline for =
submitting bids, and a strict deadline for =
voting.</div></div><div><br></div><div>That way, everyone could figure =
his own travel costs, factor in his own willingness to stay further away =
for less cost, =
etc.</div><div><br></div><div>Keith</div><div><br></div></div>____________=
___________________________________<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/m=
ailman/listinfo/ietf</a><br></blockquote></div><br></div></div></body></ht=
ml>=

--Apple-Mail-103-907880094--

From stephen.farrell@cs.tcd.ie  Wed Aug 24 15:00:24 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8195A21F8D49 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXFhHvKk1fiz for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:00:23 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 03B9021F8D46 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:00:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 55DF3153572; Wed, 24 Aug 2011 23:01:26 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-type:in-reply-to:references:subject:mime-version :user-agent:from:date:message-id:received:received: x-virus-scanned; s=cs; t=1314223285; bh=yB5nwFK00PghKxw57JLPCjpC IKujj4oIQLqKaJ7eOc8=; b=zIwbba34YjfrCpYtK0OMImP8OcCicGd9WLDKHlyL wZHPuxqptFy+DKG97zBgP3xCAdJxe9aPPgr4jdKb0YetvcrSYxKc044I3+I5PStz 0amgRpY3ApVacCybInSX+cn0tluG8WQUp9ybnPPmw0w3A4YHSpZoUEBftcBIQH9O 5LQN2O+l/tG95HSZTy3gaTmD2jOI7/B1dk0PMiDqB7u6NobDBZoYiG6jbWmJdvOR fO//fVsUeM7yKbJ+BAv4yIw7HANVxjdK3W6mtnbD26YvPg1b+A5suIqGfmBZRuxy dwSmMt2m1RQ2wWGI687Y+cTvsbekSifEkGDnq/UOa+y3yQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id wzKv3d4v2dbY; Wed, 24 Aug 2011 23:01:25 +0100 (IST)
Received: from [10.87.48.7] (unknown [86.46.30.197]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 748A8171C1B; Wed, 24 Aug 2011 23:01:24 +0100 (IST)
Message-ID: <4E5574AA.3030705@cs.tcd.ie>
Date: Wed, 24 Aug 2011 23:01:14 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com>
In-Reply-To: <4E556DFC.5060705@gmail.com>
Content-Type: multipart/mixed; boundary="------------080209030508030408090607"
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:00:24 -0000

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


On 08/24/2011 10:32 PM, Brian E Carpenter wrote:
> It would be interesting if someone with historical data could plot IETF
> hotel and meeting fee costs over the years since 1986, normalized to take
> account of inflation and trade-weighted currency variations. I really
> can't guess what the outcome would be.

Well, since you ask:-)

I was complaining to the iaoc about this last year and just this
evening sent them the attached updated whinge.

Not all you asked for but some of it.

IMO, it doesn't look that good in terms of iaoc performance over
time.

S.

--------------080209030508030408090607
Content-Type: message/rfc822;
 name="Attached Message"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Attached Message"

Message-ID: <4E55629D.6010109@cs.tcd.ie>
Date: Wed, 24 Aug 2011 21:44:13 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: IAOC <iaoc@ietf.org>
Subject: Re: increasing IETF hotel costs
References: <4CE2CDAA.5020101@cs.tcd.ie>
In-Reply-To: <4CE2CDAA.5020101@cs.tcd.ie>
Content-Type: multipart/mixed;
 boundary="------------060206020904090400070005"

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


Hi again,

We had some exchanges on this last year and its broken
out again on the IETF list so I thought I'd update those
figures.

Looks to me like this is getting worse not better. The
original text below explains the method followed.

I would be *really* pleased if you guys would state
publicly that you've set yourselves a goal to
address this.

Stephen.

On 11/16/2010 06:30 PM, Stephen Farrell wrote:
>
> Hi,
>
> So the expensive hotel thing has been bugging me. I had the
> impression that it just keeps getting more expensive and from
> the attached, that appears to be true. I realise that there
> are a bunch of constraints, but my feeling is that this is
> not being specifically addressed and is getting worse.
>
>> From the graphic attached we seem to have started to get
> more expensive around 2007 and there's no sign of us
> getting cheaper. We now seem to be an inflation-adjusted
> 15% more expensive from the already-expensive 2003-2007
> hotel rates.
>
> Any comments, or, much better, plans to address this?
>
> What I did:
>
> - Go to each of the meeting pages from IETF 56-79
> - Take the lowest meeting-hotel cost quoted, without including taxes
> - Put those in a spreadsheet (attached as xls and O-O)
> - Convert currencies using the historic figures for the relevant
>    month (URL is in the spreadsheet)
> - Calculate the 6-meeting running average cost to smooth
>    geographic differences and incidentals
> - Divide by figures for the US consumer price index, (URL is in
>    the spreadsheet)
> - Normalise so the first 6-meeting average is 1.00
> - Plot that giving the graphic (jpg) attached.
>
> Thanks,
> Stephen.

--------------060206020904090400070005
Content-Type: image/jpeg;
 name="hotel-costs.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="hotel-costs.jpg"

/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof
Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwh
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wgAR
CAG1BM0DASIAAhEBAxEB/8QAGwABAQADAQEBAAAAAAAAAAAAAAMEBQYCAQf/xAAYAQEAAwEA
AAAAAAAAAAAAAAAAAQIDBP/aAAwDAQACEAMQAAAB78AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAADBzuYht5+vMveZqNueWmxDp6ckOm8YXwzMzSwOhnosM61rtiAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJVGJk+h59B5nYR+XHn57
EvlhHxkjz6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1v
uGe1PuWzajwbpp6mza/wjZueqneNR7RtGLip2jS5BsmnqbNpcg2TW+zPan6jatZ8TtGHI2LS
5JsWrmbhraGc1mzDSWNq1WMb5rsI3zDxDbsXXG7a+RtWq9GzazOKgAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAxfuSMDzsRgfNgNdg79DXtgmNdjbonV+tkRj4O2J1U9
yNPkbAa22YMLH2o133YEa/XdCTh4m3GDTKGpwOlGLPOGBlVGtyMoY/zJEcPZDGxdmMbG2Q1/
3PGqbUYGd9AAAAAAAAAAAAAAAAAAAAAAAAAAAAAB58FWPkAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACVRqobwaTa2mFBNQTUE1BNQT
UE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE
1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1B
OnF9RemYKXAAAAAAATpMoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAABiZXBXz0P6Nm5N6hjsAAAAABKmL8PdddmmQmKJiiYomKJiiYomKJiiYomK
JiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJi
iYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiifNWrgdTrd7eikL5
agAAAAAAAJ0mUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAR5W
1N5xOx89GHdsDP5ukIkAAAAY6MPR4fd7ZfRjtOk6AAAAAAA8Htj+DLnhZpQAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAABo+U1y/R3HDsfnH/ToeE6jAvS2/1Pitui98j4iexcdppj
9KflHYHTtdsctQiQAADjsTXLtuVx+qmOV6rOUuFL81vMnl9M+oY2TncEgADDRl8JfodsszIM
dQTOk6AAAAAADx7Gv+bEa7JyJhQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE
1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUij01W2mPiiLTUE1BNSY0eqzdsdTsusRM1GWs1B
NQTUE1BPEzyNXXPTHP67sV68VPuceY/ON1jdlpnyrtmenGeuxH59uOpE1GWs1BNQTUHJ9Hkc
rpn05TPSagm+8pavQcBt+u1y/O/0ijO81FNJqCF50AAAADzjmUAABOkygAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAABFFuSwd5tl+d9L33y1dBvNVo6X7Vw2yh07n9Yne8vsestXEzDHUEgAA
AAAAAAAAAAAAAAPn0cp1Xj852x/Sud53pzQdXsVbBnoAABOk6AAAAGNq9vrDcgAxbefJG08g
KCagmoJqCagmoJqCagmoJqCagmoJqCagmoJqCagmoJqCagmoJqCagmoJqCagmoJqYKMrVajj
OjD9Ztwu2pfpGDsc9PCiJm98bam55nbdVpTByqMdZqEzUE9Zt0x+Yb3smuU1GO01BNQTUE1B
NQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQT5PsFq6jZ0RM1ETNQTUE1BNQQvOgAAABHUb
rCNgAABOkygAAAAAAAAAAAAAAAAAAAAAAAADjuc2x/TOcj0UTyuZ1oxMsy0Y2SNBruwaU47X
/oOgvTl+2wd/EhjsAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABOk6AAAAE9NstOdGAeD2wsA3
k9VsTITFExRMUTFExRMUTFExRMUTFExRMUTFExRMUTFExRMUTFExRMUTFExRrOXvn0/L5nVX
rzWXvFLUTU0omKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJi
iYomKJiiYomKJiiYomKJiiYomKJiiYomFIXAAAAMfX7LUm8A8exi/ckY1aTKAAAAAAAAAAAA
AAAAAAAAAMHlb0zcHX9bvjq+t9ufYK3AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AnSdAAAADBxNyAAAE/uKjNRsAkAAAAAAAAAAAAAAAARRZpdDpTquVyOqtXleqszuFbgAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATpOgAAAAAAABp+M/S8LTPjO61fN3p3TSb/
AB1moi01BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTU1MxsOMl1m2X5d+sZaszUZazUE1BNQTU
E1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1BNQTUE1
BNQTUE1BNQTUE1BNQTUE1BNQTUELzoAAAAAAAAJ0mUBz+j7z5pnqdvy+stXu3I7Wl9y5+R0r
lIzHYvy3Z3p37jlbdj45H2ZON4xdM+7ccz07FyW0rbcoxrbMfPsSAMCYz56PQ6Z5eRvc4+fT
LUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACdJ0AAAAAAEq4p7j5xDPvrM
8yExRMU0e4TX8/6var1wq5ClvNponR7LKWiiatqJiiYomGq2qa8hx/67ib48xfq/VL8k60cl
z/6amPz39Gmpeial6JiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYom
KJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJiiYomKJhSFwAAAAAAABOk
ygAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJ0nQ
AAAAAAAMcZE8TLKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAnSdAAAAAAADF85g1WdfXGalkk1BNTCK0w888KCakydMOxZQTUE5w9GSoJqCc/u
CbF8qTUE55GvMxiZ5NQTUxT1TA2R4UE1Bj01+QZCgmoJzh5M1QTUE521hsXi5NQTUwS1IZZN
QTUkeKYWWelBNQY9MKpkKCagnP5jGcoJqCc7as2SeQTUE1MIrTB2RNQTU8EqYdyqgmoMemJ8
MxQTUE5+9YbR69E1BOeRqjYoZZNQTUwC9MfMJqCakj5bW5RkAAAAAAAAajbjBzgAYWaNNuPo
ARshq7ZyQAGtltwABjYuzGLlAA1O2Q1e0JAMTLGs2YAPn0aXJ2IAA1sNyAAGs2YxskAGNkjX
7AAGPkDX5vsAAYc9gAAMbG2Q+fQAYGeMPMABjZI1W1AB59IYGd9SAAxcPbAADHw9oPPoQCfm
j3ows0AGq2o1mzABGw0e1uAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI/dPjw6Wegn
Lp2iyIbVzWTLc++aHStLugAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAACagAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/8QA
MBAAAQQDAAECBQQCAgMBAQAAAgABAxIEERMFFCAVMDIzQBBQYHAhIyKAJTE1JDT/2gAIAQEA
AQUC/wCvJZYCHqSXrf8AZ6v/AGRm5jDKM8cMozxkYh+gyscss4wqPJGQ/wBAMZB/oub/APmA
CZ3/APqM0r+QjvXCikLGgZiCQAvVzbF36oyaLyWbkDylCOOeEAimhhAoMMheL+iuYO3pcdVG
1RYkIiLco6co+bwxO7CzOQibDGAMMUcaCGKN3x4XQiwt/wBq8mU2kiyA5BlyGnzBaD14cwzC
lmjyicPVuSObeK2USA5XmPPdl6lwcsso2jlcpHzKzy5Bm0M+5GzXIjyCjn+ICoTMsosoheXJ
5o8wo0eQ+myiXqyU83FR5bSJ/INoMnrKGYzzPnOIwZbTSHkNGRZRCannkBRu8jwdSkxpugzz
bheWVY53AMqTUU12x8g5DhKT1BySDmSZtYyy/wDnNmNFJGbSx/ySWJzKKFo4wxqL0uongMh4
SOcWLyUkRQJoHLD9N/r9KvQk8fpHJPiuaGPU/oy0+IShhN29EXE8W5PjyGEUJBK+Ozs+IZqX
F6lJjdD9N/reM+ksJHK+FvHKAujQ6lHDIUMBTPGEgvNjdpJ4CmQC4qTFugGdiji5lBC0MUgW
D08loYua9KTKKLmgxXB44ZRnOA3m9HVPiGULwExt/hv+twkxN1juE8Uhf0tJRo8KWP0t4ZJ8
Y6mREy2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a
2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2aZ3t+Ef0/0N8c/5
Ys/qcb8E/p/oXJnHGgCGWRvGgQeP/BP6f6Ed2FieTy+cEYxP8+SQIgZ2dgyI5CP6f6E8jlvm
S4mJHiRP935+S+seGRuUJdZjZ9VdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVd
VdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVd
VdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVd
VdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVd
eUzXgHxuD6eKrrWpfwj+n+ZeQmLHwviub8/OzGw4PGYZHL+j/d/CP6f5hLLHCGR5lycPGZWY
8/hZI4sTLjy4vmTTDjwwRH5XOZmFv0f7v4R/T/F3dhYs7FAfiuasHyocfV4yExMfwZZY4QyP
MuTxeMycs8fEhxW/TOxyxzgnjyYvlO7C08p+VzoYRx4f1f7vzidxGCTtC0zvPjZL5CP6f4l5
TIlxsYPLZbH8TzpFbzJL4f5JN4Jtj4XFEvgKg8PjgHwTGReCG3wjJhXo/KRLP9asWf02TH5u
B0GfiyN8nK8vJFk/Gck2i8Zk5Z4+JDit7Z4JPHywTx5MXyJ8qHGWf5D1L4OG2HB7H+784rVx
wmihpN6oIZOpi2qMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqM
qMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqM
qMqMqMqMqMqMqMqMqMqMqMqMqMqMqMqMs7OixFHh5fkii8Lzmoyoyoyoyoyoyoyoyoyoyoym
w4MhR+PxYjPCx5HPw2KT/Bp4k4+VxnPyk8YfEctfGAGL4jlSr/y0qbC8pI3wMiWR4icZ/F4M
kD0ZUZUZUZUZUZUZUZTx/DcmPnLHRlRlRlRlRlRlNJBjjnZnqz8W2/I0ZUZUZUZUZa1L+Ef0
/wAFllCGP4rhICYw98kgxR5Hk5cmTB8SMX4k4PJj/BMlY0A48PznZiYhk8TLHIMsf6kYgOT5
jZQeLmyjhhjx4/c/3fwj+n+C+VzouSh8nlYscXmMU2CQJG9mX5CHEZgzPLHj4sWKH7M7MTCU
niZWdiZZflooWHGzPKSYuFDifJf7vySJhFsgHk95/T/A5ZY4QmzsnyB4Xi48b9HZiaXxeJKp
PDTRF6zyWI0Pm4TUnmcYDyPMlIsPxP8AlmYW/aJIxljfLyMOQT8h5EcXxUOO/wAp/u/JyLcI
fvezIc2gjfcUBSPMZjroC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6A
ugLoC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6AugLoC6Aug
LoC6AugL4rhKPIhlDoC6AugLoC6AugLoCy/JQ4zRQzeTkgCDGi6AugLoC6AugLoCmxMKdZWI
8WT4Ueb9AXQF0BdAXQF0BdAXQF0BdAXQF0BdAXQF0BdAXQF0BdAXQF0BdAXQF0BdAXQF0BdA
XQF0BdAXQF0BdAXQF0BdAXQF0BdAXQF0BdAUviQlmwYAw4egLoC6AugLoC6AugLoC6AugLoC
sxS/Jlrxib/Z7JY+oBFRo4Och/T+7zZmPApvON+mLn5ONjRebhJB5DEkTOxN+juwtleVOZ8P
xAh/BH+78mXfGFm7e8/p/dJZ4oGm83Gyv5TNUHhBZQ40OP8ArLjwzI/D4hp/CnG9fL46n8nn
iYFleUlxMOLEj/gj/d+SZUAMgnL3n9P7l5fL0YZGWZx+EIigwsfGb5Od431k2D430c38Ff7v
yT+jFGs3vP6f3DKz4cVnnzvJvF4OOkfh8eOX+JP935ORbjBJbJ/UmsOI7visRVx7RGbvqzqz
qzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqzqz
qzqzqzqzqzqzqzqzrIzosVizs3PLG8Owpnq1nVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnV
nVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnV
nVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnVnW9y/Jm+3GJPP+
pCxiGPHG3p4+gY8cZH9P7ZL5rlMfk8rMfH8M5OICA/xZ/u/Jl+1BEQS+8/p/asjLhxWl8nk5
Zv4zOJ/F48uNjfxh/u/JyRd1ix0P3n9P7RkZcOK0vk8nLPH8M5PFFHCH8af7v4LEJPNkQggl
jl/ZZZQhjfy2GzS+Tycs8fwzk8UUcIfxx/u/g40kPqfKf/S8TlBjmxETbNbNbNbNbNbNbNbN
bNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNORC3kPKDPEoo+IbNbNbN
bNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbN
bNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbN
bNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNbNf56/hTY8JrI8XjTtrN8SWN5bHm/YcvyEOI
2s3yxYmDFiD/ACB/u/hH9P6ZXiYZmafO8Y+J5GHL+aRiA5/k+CwvKT5OX82SQYo8rypzPieI
/wCTMwt/IX+7+Ef0/q7MTZfhwkcc7NwCDzrOfxXCR+ZxRf43jI/Oxsvjykzcg5cXOzxi/wDN
L0flJV8IyZkPghtP4RD4Oe3w7PgXqvKwoPOg7xeUxJUMsZB6vGTOxN7J83Hxjm8xjBGEGX5U
8fEhxW/kb/d+dJI0QRytImyRcoZuzH9Pt8pjy5ONF4rJ7fCsJBgYsbekxkEUcX6SeHx5JcXF
DEi+QcYSNL4vElWT4YI4lFg+QKH4f5JfD/JL4f5JfD/JLOhnhm8TDHPl/wAlf7vzsgCOONj6
enN5YYXGY2fVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXVXTx2b0MCaOrVdV
dVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdV
dVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdV
dVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVdVda1L+E
f0/0M/3fwj+n+hn+7+Ef0/0M/wB358sjgo5bhFkOZH9P9DP93580ZE8UZgocVxmMB1zBcwXM
FzBcwXME0Y75guYLmC5guYJ4x3zBcwXMFzBcwXMEEY05guYLmC5guYLmN+YLmC5guYLmCOMa
cwXMFzBcwXMFzBNGO+YLmC5guYLmCKMdcwXMFzBcwXMFzBDGOuYLmC5guYLmC5jfmC5guYLm
C5guYIIxpzBcwXMFzBcwXMb8wXMFzBcwXMEUY65guYLmC5guYLmCaMd8wXMFzBcwXME8Y75g
uYLmC5guYLmCCMacwXMFzBcwXMFzG/MFzBcwXMFzBHGNOYLmC5guYLmC5gmjHfMFzBcwXMFz
BFGOuYLmC5guYLmC5ghjHXMFzBcwXMFzBVZpPwmyrSwSvKPsnyOLnPIIM+2/UzaOMMgzGGV5
H9k2TzkfI/8A0+yWRoo3zHaOMnMPYOVeWDJ7F7J5uIlkStE29ewcywxTOZ+ybJ5yFkuz+x96
9VL1ik6D7JZZYyGZ3yPYbmzBPKccUnWL2HPMBxzEUnslMwE8p48f2PvRZUgKGR5A9k8skTR5
XST2FaoTTG0Ejyx+x5pRliyXkL2G5sw5hkLPYfY2b/xjlJ5PZLkPGXd+/skPnH6iRyhl6h+D
6aRljhKHtliJ5fTzCzf+v1lj6wtDNbHheL2zQGUgYbxl7J4u0TRTMUEbxh7PSluHHMC9k8Tm
gxzZ/Y/+W9JLSCB45PZNAZSHhuT+1seQRhjeMfY8bvkUm9X7JxI4Z45CYN09nM+sMJBL7J43
lDIxXlTf4b2DEYwQxkJ+ySNzkbGNi9hbrxJsJm03saMu8GMUcnsnEjhnxnkQjUf1f/02EVY4
5OvsnxilkKOfr7JRc4vTTComcY/7oGUCOOQJQTGLv7CJgD+kZI5GmeEhaSKTfF2GSKpYutcX
AKdJXhJoDifrFD/s/pMwGQQjGNv+wH//xAArEQACAQIEBQQCAwEAAAAAAAABAgADERITITEQ
ICJBUDJRYGFAcUJwgJD/2gAIAQMBAT8B+YduB/pPv/hJXVtvhjtbaU6WHX4WzYRcxF/kfgbO
F3j421EBvzjrOLt5VqoU2MzR2mNvaOKhgzAJif2hq2G0WsDvAQeXOWdbfUVAvA9OvLe0PWbD
byAIO3KXLaJBSXvzWvMIhprMBGxiCpMB7mZS94KSg35fR+uLOF3hDVPoREwC3jyxfRYKJGxl
3G+sFVe8NRRMLP6pa34hOX+pjZ/TFpga+KvaPWt6YKq94CDtwZwu8wl/VyEA7wUgGv8AjMob
eAW08S1YA2nW31BSHfXiaaxka3SZTS2rb/BGqASzNvpMtfb4SzhYMxjYxUC7fCTUUTrb6ioF
28vUTELQE0xY7QMDt+ASBvLs+20p08HmzT7jSYyvrgqKe8zF95mp7wVxMz6mJ/aHMxTM9xBU
U95ccSbQ1Oy6wJfVvPEXFotJRMI4BQNeUqDvGo32mUJlCGiDETCLf8Uv/8QALBEAAgEDAgQG
AQUBAAAAAAAAAQIAAxExEhMgIUFQECIyQGBhUSMwUnGQQv/aAAgBAgEBPwH/AAXamy5+GIt8
4lSrr5fC1UsbCO3/ACuPgaoWxE215GEW428g0jPdVpFhcTaPWaF6tENIRtsmaU/lBSucxqLD
EIIzwii08ifcaoW8B5hY54QLwDbFznuBUjPCEC83hrN04gbTUYKrTcByI5p/ibg6CbzdIazE
W4fX/fiqFsQFaf2ZUfWb9vChObRqwbIlqZxyhpN0gpMZqVPTmE39oF3P7mhU9UaoTy/aHYAL
xKF/VGot0hBGfBULYmpU5LwAkYjViVt7ZWK4hN+Z7StEkXn6a/cNU9OUz4Cq46xai38wlR78
lx2ge8WmW5zUiennN1/z8JWmWh21FxGctn4SKTGeRPuM5bPd6b6DeELUNxmFSufYAE4llp5z
KlXX3sVOh5zQG9ENNx0m2/4my/4hoG02/uaU/lBtaZt3wYabDpLHxAJxBT6tyhqW5J35TY3j
VWM1HwLsRY8IYjESvbM3TN0xaxEqPrN/8Uv/xABFEAABAwIDBAYHBAkEAgIDAAACAAEyEZED
EqEhIjFCBBNBUWGSICMwUnGBsRBAYNEUMzRQYnCiweFDcoKjJIAFc1Px8v/aAAgBAQAGPwL/
ANecYqFTCejr9lx9PzXV/o+NmpWmz804NgYrkzM70ps1VXAg8CWca08UxjWnimzPSr0+zEw2
rUKVTM9XIuAi2111biYHxobfbmF6t/Iz/wCQ/wB/5Jn/AEsn8N1B/wDU/wBVj9UQNujXM1V6
xxcv4Woqj0gxbM+xmbvXRcPE/Vvn49r1TjRnwhxxZu5u9Y7uOHmYnZjLEo4d3YukZuO5WyE8
TYJYeUXfvRABb3a49jVQjgk2GJYZZ3H6oMMsLDqYvvYby+LLBy9VmqVcM+banYRy5SdqVrb+
RZM4DQuOziv2fC8jLNRs3CqcqNV+L/ZQWZm8Fk6scvdTYsnVjk92mxM74QVbg+VO7M1X4uqE
LO3c6oACLdzMnyYYjXjRlUMMBfwZPXBw9u191UFmZu5v/awMIM1Sq+6zV1QZ8Vsz+9sd1h+p
b1jVHfQYjszOb0oRUa6ruVzZZ7t0IgwU25qFWyZgwq+rY9416vDzNkzvtQYtH3suxn71Xqtz
rOrrm8Uzk77cfLsPwdEzCGajuzdZXh3reDfyDsYtm10efC3xpsYuNUeGY5SGnB6psN2HaWWe
9ZC4jQOtYc2bxTBlfa57XKvB1lHDGvc50rt7EeYW6scPM+3aqUByeLAdVjMeyjDsrVlj+r3c
Jtr5uOxPu19W58VvYPFmdqF4oxMKELjE+91XqtzrOrrm8Uz9VuOeRnzeKbYO3tM8rINlBMXe
te5NugzuOah4lNiEQCouDHV3TYZMLVrwOrt8UBnhUA2d2fN2UWTcrSu6eZYrE0BzfFMHVjmy
1o50t9nSaFTJlps4J2bpOPw7cKn9liZscnYDpSjbdnwQOfTd9+TdRdQeY2dq5NrttWUSx8+b
eZxGrN9E+8buz0fOzM7WW0BcnxHAWYkeYcpA9HZYZGRM2JwZxaixgxCZ6UdqNwRsA5/Vs9HK
nehNmHKQ5t88qEQBnqLFvFSvwWTcrSr5zyoTHgTV/EomB5THwqsvF+NVgb36pqcOKAWPeAsz
FRDXF9YJZmLLsQG+LUhry9jqdfVsHBZQc9uFkemHWv5LDwnejjl0WXN/qZ+HjVT/ANRz4IA6
7YDOLbnYt7E3srNVh7nROeJUyy7WHudHiVkzNRUbF2Medt36qnW+rY87Nl8U2Iz5CzHIex3X
Vdazi/vBVPvbr4eR2WU8etKZaCjxCPM507KLHZy2YumyifPis9cN8PYKB89MrU4eLP8A2Rln
pmy9nc6y5v8AUz8PGqbCHPlbFzUcPGvFDiAeVxZ22tVNhdbwd6FTsWfCPI7jlfdqnNyrUGFY
XrWdsPYzZexYWEXWZAZ22hSjUp81v4uZqUow0QFmpl4+LJ2zjkduDhWylUexY2/TrKdnCi38
UHbuYKf3WI9a5yzIQ407aJ2Esj97J8TrvW9+XZT4IncsxE9XdbMTax5x3eCKr5iN6u6CuJUM
OA0RYj4ovm4tk/yixAxctRyxqqBiUHIwPs2psJ8UXHLl24azYWJlfLlerVTNWvj/AOt9Rdnb
vZZM45/drtWUMUCfuYv5Lv1mXJ25uCw2zj3cVlE8MWAneldpEsLCw8brBy7WpFRa6iN1EbqI
3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URu
ojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdR
G6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN
1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1Ebq
I3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3UR
uojdRG6iN1Ebqjs1/ufzb6/yHZ/0f+v/AAhxsuXN2V+5fNvr/IYsQuzg3e6qGGZfAarCExcS
27H+P3L5t9f5Cu7vRmTUF2wR0b80AA1BYXo33DMb0ZVbgsolt+HFfNvr/IUei9GqTV205nWQ
Nr8xd6b4P9wPY7u7OzUGqBsp8O0XTGQmLs1BHI7UUn4t9VMtFMtFMtFMtFMtFMtFMtFMtFMt
FMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMt
FMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMt
FMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMt
FMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMt
FMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMtFMt
FMtFMtF1WFiv1r8fBl1hO7Yht3cFMtE2877H+5/Nvr+MzMCynsov139Le3zUqb7BZfpnSG47
Rr39/wBrfB/ufzb6/jHPiGwj4rq+ihV32Zn/ALMut6TiZa+9tdOeHidY7cuWizhsfmHu9qWK
cRT42KPqW47dEzM1Gb7W+D/c/m31/DDu70ZlmfHw/k9V+u/pZP8ApeNv5tm72fJftGF52WYC
Yh72+5Z8Q2EfFdX0UKu+zM/9mXW9LNx+PH/C9WG33u37X6d0bYbTH3k2JhvVvp7N3d6MybBw
i9S3DZqhwgiPoN8H9vVmzP3IcSlK9iLDcKUGta8VWmHSlaNiVdtF82+v4TE8IspZ6cEzliZh
rtajbVmweibj8N13WZmoz7abq/a/+wk1ekbP9iq74heDuv2n+j/Kpi+tKvHayni3b8luY7sP
iNV/4/SqV48RWcekZ3bsz1+qw/0zxy8P7IcbLmy9lU2cDF+3tZlVscP+T09kQYPVGDcH4rKO
GGd9jUZdb0s3H48f8L1Ybfe7fSfpXRWrh/6mEmxMN6t9PYj1x5c3DYh6P0Uqsex34V8FlrU3
2k/ot8H9vuszv4vRCBMGzuL/AAnxMuHlpll/hYZG2G2Rnh2rt4t2+K5vM65vM65vM65vM65v
M65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65v
M65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65v
M65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65v
M65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65vM65v
M65vM65vM65vM65vM6cGzFi04Zn2fFdZim4B2Zv7MgP9IrlJnj/lc3mdc3mdc3mdc3mdc3md
c3mdc3mdc3mdc3mdc3mdc3mdN1ouVOG86Yww6E3bmdO54TE79rqrZw8BdZsDpVC8q7cUR8a1
/unDFwCDEdtj5nanydfryQN1eIZ03nc6bVmwOik4/wDIlnESBn7K0+qzF0nK/d1j/wBlmPpO
8/HdqibAw3LD7HcmWK+OGV3pl3lzeZ1zeZ1zeZ1zeZ1zeZ1zeZ1zeZ1zeZ11+GD/AKMWwxZ+
CYwJ3F+D5nXN5nXN5nXN5nXN5nXN5nXN5nWbFxMv/J0OUXER4Veqwvn9FzeZ1zeZ1zeZ1zeZ
1zeZ03Hg/b9z+bfX8DPiYj0Fu1frv6XTGMSarewczegtxddR0Nnar0zdr/kmxOkUMqQ7G+6Y
mG3EhdlPCu/5IRYRYsrMTi3H27s7VZ11mHU+iE+8PupjB6i/B/QzGTCPe66vog5nfmp9GT43
SyIc3Z2v+SyYQ5R9Nvg/3P5t9fwMfRR3j2Vfsb7MNsXCzYdN2rU2LfzYb+LVVcMxJv4Xr6NH
fMfussxPkwv6fksuENK8X7/3O7O1WddXiVPohPul7qZ2erP9mXBpinoybExnyYfY7t9GXq23
n4k/H2LfB/ZOT8GWTbX4ew+bfX8CZ8Q2EfFdR0YHYXba3es+JTExPhH7HZ2qzp/V5HftDYs/
Rsba1adjp2xcPMzU2kPD5sqYoFh6sqb5eIsmDooExP2vxsuu6XtOtcta3TMzUZv3S4G1Rfiy
xMDBxXYBN2arM66urkFdr0oyYy9ZiN2v2ezb4P7I8rC+zmeiwx9W1N79Y5O+z4eibgWV2ata
IXfi7LGEyrldqbFJuLdvipjdTG6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdTG6mN1MbqY3Uxu
pjdTG6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdT
G6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdTG6mN1+u/pdMYYjZXUxupjdTG6mN1MbqY3UxuqN
6zE91l1uPisOHXv+ibDw3Fm+PFTG6mN1MbqY3Uxupjdbwgxe8L0RBgiZg3B+KxnxByvspm2K
Y3UxupjdTG6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdTG6mN1MbqY3Ux
upjdTG6mN1MbqY3UxupjdTG6mN1MbqY3UxupjdTG6mN1MbqY3R4n6WLZid6U/wAp8PrhOpVr
wUxupjdTG6mN1MbqY3UxupjdTG6mN1MbpqOz7H9keeNNqDOOKzuValTeenh6LhnIa8aIW6w3
p30Tn1plm41p+S+bfX98UxMUWfu4uvU4XzP7B/8AHzYA81H+q9ZhkG3s2p6Y47Pe2fVM7PVn
+13d6My6noYlt5qbfkmPpG8Xudjfn+BG+D+yOg5npw71hZSxDpLPXZ7D5t9f3rXFxBH4uqYO
G5eJbFu5sMNnDdZVxzzP3DwXqsMR8e37fWYQlspV2TUYg/2l+ac8DpNC5dlNVRn6wR29j1/u
t71OyOT80OCeLVm2/BUFqn2n2v8AgVvg/siJ+DNVZSBm3suwq9lfYfNvr+88MMDHdiaubISY
Bx8XMT0bfdZukY3bty9vzTdXhtmbmfj7JsTrclBpTLVPidbnqNKZafgZvg/siq9NnFbmCLj/
APkYcvsPm31/eL5irie4yccNsuF4bG+br1uITl/ChxGPEqL14t+E2+D+yJw4t/FRAzO/j6wy
7PFvQdqu3iyw3d3d+90GNnLMWLlpXZSqwxxWLMTcetctFF+LfVQLRQLRQLRQLRQLRQLRQLRQ
LRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQ
LRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLRQLResrX3WpVZOjA4D/D+ar0hiN/dHgm
ZsN2ZvgoFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooF
ooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooF
ooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooFooF
ooFooFooFooFooFooFooFooFooFooFooFooFooFooFom3XbY/snbIR12UFC7jjM38WXjSnoU
evyeiZhzUZ6ydZ8u34qoj8NvBfNvr+7Tw/0euUnauddV0bDy193a66zpR1d9uVv7usoCwj3N
+F2+D+yLey7JdyHdw8Mc1Wylx2ew+bfX91+sPb7vauq6IDj8OP8AhO74VXf+NkQYo5Sz14/h
lvg/ssOmH1jMVXH5Lb0Yher7zu2xr+w+bfX90+sPb7vauq6IDj8OP+F1nSjq77crf3dZMMGE
fD8Nt8H+5OzEzu3FZSxcNiq2xyT9XiCdPdev7lfExHoLdqd+tr4ZXXVdEBx+HH/C6zpR1d9u
Vv7usmGDCPh+HW+D/csYcMw20ozP4LF+X0WIJuzZ6Ud0zswuz/xKI3URuojdRG6iN1EbqI3U
RuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuoj
dRG6d3YWZv4kWBhjUXpU/syYeEAj4OojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN
1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1Ebq
I3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3UR
uojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojdRG6iN1EbqI3URuojd
RG6iN1Ebpqs3B+37nmLCw3KrbXFbB6su8EWXewa8abH/ACVD9UX8XC/7ho75j91kObdwa8ab
G/NbrVOm0+/8Qt8H+5/Nvr9rvhN1eJ4cEw4jZsLx2t8nWVt3E91/a5jJhHvdYf6OWFiVrXbW
iDCMcPKVeDeHtnM3oLcXXU9DEtvNTb8l1vS3zHWuX80zM1Gb8RN8H+5/Nvr6Ds7VZ1m6O7YZ
e72LJ0kHMf4vzTMWBlGu183DRfrv6XVGzn4iyhi2b803V4JF/uei/Zv6/wDCImxsQWd60zvs
T9XhljNWRM5L/wDhZy6Rkd+zPT6L/wAjpVacOJLfx3cfAaIf0c/j1j/4W/iYbD4bV6jpNRHa
LZnbRZTwM78a5K/ReswCZv4Xqm9Zkd+w9icxxBcW4uzr9owvOyZ2erP6OTFxMpUrwdVw36wu
7gmxMUsuHto9Poy9WG33u38SN8H9vmfRPscSHizqmUqO+Vi7HdM7YRiLtVnen5r5t9fSEMIc
xZ68UHWYO5mbNvNwX6n+p1RsAP8Ak1V+z4XkZP1eGIV91qfYWI54lSevFk+HhuTs713vY0xA
Em/iaqf1eR37Q2I8TDxSoIu9Cav2AQdKoLizs3WEv2v/ALCX7X/2Ev2v/sJftf8A2EmHHxM5
Za1rVO2IOZmGuv4mb4P7dsu1xJiojxHw3bO7NSvBkzZSYGPNtJqfmgccDqWFt7bJSfi31Uy0
Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Uy0Ts5
O7P8F+rDyD+SZmJ2Zvgploploploploploploploploploploploploploploploploplopl
oploploploploploploploploploploploploploploploploploploploploploploplopl
oploploploploploploploploploploploploploploploploploploploploploploplopl
oploploploploploploploploploploploploploploploploploploploploploploplopl
oploploploploploploploploploploploploploploploploplom3nfY/3P5t9f5Dt8H+5/
Nvr/ACHb4P8Ac/m31/kO3wf7gLCOYiejNVO7tRxejsgzBlbEao7V82+v8h2+D/cAMKZgeu3t
W3LvO5EhMmFstaZXd/8A9KLVq3YoDZQGygNlAbKA2UBsi3G49ygNlAbKA2UBsoDZDuNx7lAb
KA2UBsoDZQGygNkNQatO5QGygNlAbKA2UBsm3GpTuUBsoDZQGygNlAbIqA1adygNlAbKA2UB
soDZQGyLcbj3KA2UBsoDZQGygNlsBuLdigNlAbKA2UBsoDZQGy2g3F+xQGygNlAbKA2UBsm3
GpTuUBsoDZQGygNlAbKA2Q1Bq07lAbKA2UBsoDZQGyfcalO5QGygNlAbKA2UBstgNxbsUBso
DZQGygNlAbKA2Rbjce5QGygNlAbKA2UBsh3G49ygNlAbKA2UBsoDZQGyGoNWncoDZQGygNlA
bKA2TbjUp3KA2UBsoDZQGygNkVAatO5QGygNlAbKA2UBsoDZFuNx7lAbKA2UBsoDZQGy2A3F
uxQGygNlAbKA2UBsoDZbQbi/YoDZQGygNlAbKA2TUGmx/ueURZ228+9ZO7jldidqV9EW3av7
xUZZ2wtjDmKpJn9AjfgzVRO2GLu3YJ1RsQ0IHo9Hr6ORmF3pXeLKhwWHjxfu9FzdCVMPaWWv
Wbt0xPl/4lVvRysw0q7T22Wxhy0rPb829FuFXejVei6xsPDdv/s4/DYmq1H9EjytlYc2wttk
4ELM9M2x6+jkZhd6V3iyovV7gPQnr6O7tfxXV9UObhsPZ9E+yjs9Hb0Wphg7O9G39v0RYThS
jVrXj6O4Iv8A7iomIcFttefZSyHEZqZm9Fh6kSr7p7foiwzBhJmrsevo5hEHZuOYqf2QmWHv
lyV9Hd2v4o82GG7Rth7Kv8lm3P8AgWb0XJgAh8To/wBFlyj3T229HcZnfxeiKmFh7r0/WbPo
s7iw91Hr6Ig+GG93HtpZBUKMbVHbX0dwRf8A3FRE/Ututmff7PDYmduD+ixEFBcXJqPVZMQM
pUzbHr6JMwM+Ucz1eiAMj0Jq5vRI35WqsnUs50Z9hbFWlHZ3Z/uTMOTKx52eu34I+sYKOTlu
lX+3ohigwuQs7UJYYUA8MW4OVNtlt9A8P3monP1bFlYadjo6sIs77AHg3omQZHzhlfN2LCy4
xOwPV60/L0cuytWdqosSmFmd65ey6fNSpE5bODeiwbvVseevasKuTLhNRnbt9ECGmYCq1UFc
tM7mTN6NEIZhHILiJDxdOWUMNqUyh9fRMgyPnDK+bsWXdy7KlV67PD0gJsr4gm5eD1RZqZiL
M9PRE9mURe66zKGWmWX+PRMAeju1EAYbD1fMzlSqarMz9zejiGztVxoHgiNxAGdoh2v3+iwt
SmZq/BG44hMRNSmyn0XGvou24+I5Znrw4rEM8rOfYPo4T7MovV0w7mRsTPXt9F6cexdSLtmy
0qmZuDeiZu/EWYfBA9AGjbzjxP4+iYA9HdqKgiFMuWtXan5phbsano5XyDuuzkPE/iusxctc
uVmH0XLKB1GjZuX4LCdmAmBqVctr6eiQiWV3bivVDhYbPscRKldEwuAhTsF6/wA6TBn3g4ss
4PUfs2ei5Fwb+SWKQC++WT5UbahbL6tnPY+G5dvcmYqvuMwl1bk9b7FiC2E9cuJwHjtRsOG/
V7juzNx27V0jKLs2fY3yZdHccN4s50bxZVfDLK+NXa3ZlW7hlV8M2fZZVw8NxwdmZnw3er7e
ztWDmZ3YRLiNKbf5KZSarKg/+wP/xAAtEAABAwMEAAUDBQEBAAAAAAABABHxITHRQVFh8CBx
gZGhEDCxQGBwweFQgP/aAAgBAQABPyH/AM8k7aSBW1vdA+BVAVdllqGk2iFxHFZ2oP8ABKCR
ARI3ULIJQESN1CyGkwAPmbfQcF2G1Q6PDa9CDFimNCRuNPrdCSH8i38GdDhCCFDVir4XZbFu
WK92xCAfOggfkoKMVWwKtwjEuZwsHQ/yiR30tXBQOE07biQaBYFfALXBZ1NQNCIOdk/OWA1l
M7nROakBQBqF66po0AUoNXsUNr4oBaq2oRnL1pgeW38Fk4CoJD3boDLhxFDTBYq2yAAFaBU/
TgdQMETvl4/wRO75J+CL0UiA4QKq2CpRSc7gcI/NNwgEOAFoYdEBauRh0CAgFUCp3QOK7AYD
/wBWMOgEJjA1rNdU7KtAoMBZm3QVon3Nm9KfKbcIsAh3fZRfi3VM78WRXqmTKjXAVuqW7xEv
R2qaK4ZBfawNgNzRBLCqULOGvqii8A5qHodmshRzjCEMKDWZCaJ6Agx6AKfKeCYuKsiQAWp5
oRVG/ACahZDwglZEH0GyEE4YUnzcPVEhtwKizC42QRPsQD+/RDVwmqMIaKmiHdTrzOOEHqbA
gXkkBjtdCr060vZNEJdEZqbJ3ovStEzXhtxwQFaUNUPYcyVDAqw9kUXgHCuPQ7NZGku1tPQ7
NZHAxwgD1Ro6RdwqhAO0MitZqVKK4ZDVgX03oioagBtNgt8plriOLHVDXWra21RsdimQLY1t
r/YQruQOuPpRU+yFtkOd3MAar+aMWHZN9xQ0v1IbGGrckEWuVeOtmZ1RuGAzWKe6ag+A2FTZ
hQSqza9IG2hEmNsxD3pSy3MAnFnoUCBRLy6sDd/O6PEURGA50zMCggV+SBe+QXcAalFcUNDs
DpRUrS1pn0DcqzVAf9y1bkAJYINwQgN9YkYuSXJTW675gIExZ1lq9CPVGx/QIozNt6pp8h2k
sUFaW5TRvQKz1+UCBFgjVtmY1V1omR0cWerD/S/N/sFeNnrQIb5ROAUgZUGL1vz8IiEvsTBi
Yg3TVhFgADzM/wDauzsCzPlGioa+931V+EAALNXT1M72R3wjAGLuLOGsFVVecBIOSXFaGvKA
Ub9g5I0L+q18hQsQXBNa/CALGAs0Ge1eURBqsEHiUCUQH1utMB1HZB5YDorL83+wROybIAqG
tiOLoJzZFFuaGiK7q65c7g15NUMQYgBYYWaorVPkkRpWj1+U1C4QGuQYvW/PwqkSe1Cti8k/
BiY9wN6oV7VDawLe4CHszI0zknofdEiDSAC1R66o9J50X/JVAB1OSXu5ekULUA/pOHBjsOim
K6BLfk1Fk9Kud0UbU+atqD0TwkYJPqF3BrUV4TY7Y5htb0QjdxNCRpU6s6D2wAEYs7MfMhpj
GYO4a35T7lPT2DY6XQpVAg5bUVofdV5YLvAsbitUJKEQF2v/AJuJADksAgc12I4KBDFts/Ba
kXZE/wALmYMNwjOmOkOrWiA6kSN47D19U4E+BgBba1vIqpuhwB6/JSnClOFKcKU4UpwpThSn
ClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOF
KcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU
4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4Upw
pThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThS
nClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClO
EzjnBNHf1z+jtdqP4HL9LBHw/ot+hqMxI/r9Fa7UfwMXMUVC20Eym2cyCQSoLEVforXaj+BR
lgHJJYAKwlprq32d2zoG8cB5j9AVDj1QWaoOCnuiQcOQAcE39Fa7UfwLY5rRxDe3s6uMakuf
dF024/QCAbEGN24RDINJZMw5CGQiFjDySGdVzjqbOFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2
CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsF
HYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKO
wUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdg
o7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR
2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2C4FZA97Q92R2yYkMp2qH
8/8AFHYIE53E24/R2u1H7zGFcAy13G/Drpx/faEDXJ13PCPgCTIwqSL/AOffb69NuP0drtR+
8SoLal108WQwLkm34L+yPSzCnqLaCpp8K8yxqCOK18lYY0Jc+6/dehYcsHKJEBGBzAaD/frZ
0MsAwADAD69NuP0drtR+2BlgHJJYAIwJAbZewqunGtxtd0DZ5rsn9oSIliuD+iKgtqXXTxZD
AuSbfgv7IGBjpU27Na4+WybogxiVS9fTy+pQb0QoGpb8+90+XbjUtj9sZYBySWACJEBHJzAa
n/XpZ09CwwcufB024++cEgsGqdJ8Xqdkc6LU9xrJgYl8iwsVrtR+03iYBFhox38kxpALMzZ2
Wtl5+eGXBNMFuK19114kM9F1QGEj3QgAjTsfYA/QioNwLUbMD9LBxHRwee7hfkZ8mzvqvJNP
u9AZdB6P+C36Gg7gj+0HE+LMb1F/hGocO1z7H7Q5Gq66g1BT68rpifZ6myBgY6VNuzWuPlsm
6IMYlUvX08vE+XfKbcdp5J8u3GpbH7O/guF28vNHoMw3IiWusnhA1iNdhx4em3H3zAtohp7s
VUG7EkLhNUXWuzu7fgiQZEFV/DUHFVXHr1uxc/Ryufo5XP0crn6OVz9HK5+jlc/Ryufo5XP0
crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+jlc/Ryufo5
XP0crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+jlc/Ryu
fo5XP0crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+jlc/
Ryufo5XP0crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+jlc/Ryufo5XP0crn6OVz9HK5+j
lc/Ryufo5XP0crVmwoPc+PwqwxesaEa2lv8AVsyDS7HdOfo5XP0crn6OVz9HK5+jlc/Ryufo
5XP0crn6OVz9HK5+jlapXVQf1RW9oFP5V7NTj+6F2Zmsfl1qU0NDR5gnhOgnbr7/AH0Igsnp
Maj1XcCFIggwNGjPzsrVGhrU8wRwvKRNM9CdOCGuYG/Bak1t9rV6oEDtXppXbVNdQBAHar2P
kufo5XP0crn6OVz9HK5+jlc/Ryufo5XP0cor3hBWH795FHCYv9wI5+jlc/Ryufo5XP0crn6O
Vz9HKfDE2d4+QuUOsTqyL68WCYRfylta5+jlc/Ryufo5XP0crn6OUBanlEdR+jtdqP2NqOew
njRdONF0cAm4P2Abx3Ih13AB8Pur+EyA24H83f8ASFVADXs5DfSxTM0Q8C/P3xlgGIIcEI5B
vIJ9wdCgbx3B4DICXKwCPYgAMqk/4YRQYT2Wv8U/CZlcdhv4+m3H6O12o/YxzqQgLRLt50+m
sEQ5llGNttCqpAAOGD8N/iNxEWcAP4eALPUU120VOIbQjZRqb5RtYDhc+b/jjLAMQQ4IQyTe
QT7kahDLAOCC4I+juOKdK76+nwiAmDaAL8mlflBi+QMS5D7PTbj7REWA5KBxrak2dnbzb7Fr
tR+xCoLal10dFcYIcdydP91W0lYmjyeuv4+gywDEEOCE6eaKPIW+FUXcAS3sAR/id4DCuH5H
uiTge4tfn4RMIGwLRi4fdAC4gAYLthVwjXt6sHktUMsAwADAD/kg3jsRAS2mochcCaHrkCt3
ZG4JDikC4GX+3024+1QypOjBbuETvC6oV/rwibFHHaIhs4JPsgB7QYA4VKrh4eQowowowowo
wowowowowowowowowowowowowowowowowowowowowowowowowowowowowowowowowowowowo
wowowowowowowowowowowowowowowowowunGisNgmn5UYUYUYUYUYUYUYRcYUK/5OiYvNpZT
YfQV/KFXNyxy3KjCjCjCjCjCjCeSaPQE51pf1TQiqNVBqFV2gJg5quz+ijCjCjCjCjCjCjCj
CjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjCjC0
rCUs5dKnoWtAG/CjCjCjCjCjCjCjCjCjCjCjCFE5aL6j7QkAiH3DZk0+IEekaqU8NBDQTXI2
qCjNFFhqewRXfWRafZLXaj/sE2aLEaHoKpkxyWvWPkM/Qa3KydyfJcpkBoseiBvofhU1+TEh
lgHBBcEfUZYBySWACLyDCGE/yeXr5IezbBGp56F7/sTptx9pwAHLHwsq18SABtN62Onr9i12
o/6rBCxIuFthqn0rqLTgtc/CBoIEEgaIHV7ka6oeC3Ht+65+EGqjMwWed/q6vZ1A3ncK2P8A
U+SNSGbiIDyccLzR5921akEAHcB+bir3ByQAA3YX/wBQUExWHQcfsXptx9oL6dEyGy0/4A+x
a7Uf9M1KJyBrM7eRRVMAF4n1Rg/JIhWeTueFxASe1r4+1o9HnBO/K1ejzgHfj9jdNuPtGAZm
59iAJ1XNb6G/p9i12o/6I+AIUJV+dr6o1cxY6T5KG3wgQ37SAOKiqIqhi7Dgvt+0+m3H2hoh
okOY23CPc6dk4AG3gOENPmBNM1Ujk1VSAwjO4DNbRC8p2aCRdyoPRUznqbOVPZKeyU9kp7JT
2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2Sns
lPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JPERKxCL0dHmsj6jz02O3qmPfgA
9zudNk0vDABgA91PZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU
9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7
JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2S
nslPZKeyU9kp7JT2SnslPZKeyU9kp7JT2SnskCc7ibcfaOtGFzDsfMhDCwuWMNwWL28BwYAd
8vcIZQMAJm9ygHcSbmc6tZ0LHAgM4yzYPb0VrtR/zfKYkdi2yHSzCvoL6Cor8p4shxXJN/yW
90JASwWA/a/Tbj7Tbd5BxZDgSF06bClbP9i12o/5b9EGOAqXp6eSJgY61Ns72uHlujliHJJS
T7p4mEAYaMNvL9s9NuPtAzMxoiztzuyI8etGw8SANHp9i12o/wCS/RBjgKl6enkiYGOtTbO9
rh5bp4shxXJN/wAlvdBQW0Dr/tvptx+iOKFgBt5ok3TwAIqFzwjLPb/i6jnsJ40QqEQDscPw
iYGOtTbO9rh5bp4shxXJN/yW90FBbQOv+3em3H6Kl5JlV1Mn1emK7iQsKPxyhVocEOBHspTh
SnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnCl
OFKcKU4UpwpThSnClOFKcIVaHJLAB7IAK5BrrQMOPoEQW0/wqpThSnClOFKcKU4UpwpThSnC
lOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFK
cKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4
UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4UpwpThSnClOFKcKU4Upwp
ThSnClOFKcKU4UpwpThSnClOFKcIE2ZtO1H6Mk/TwBJqFSOMUEw9Rb+0b4jrmk51uH+plPwl
09W/4PAFnqKa7aIWxHWNJxrYf8VzSw18P3D024/R2u1H1F0apYZ5GPlGriLDSfBQW+EWBiYe
fux1/NPumQEuVgFhOqax80E6qCZ6Ed+PvA3juRF5BhDCf5PL18kxVK7cZ16UMsAwADAD9xdN
uP0drtR4BlgGIIcELdUhO+vx2yHNJH1PlruN/ROaABVs3ZOnGhdmZ7H5b6WPOhMN9n+hFHTA
WAJshhqKYFhR36/0PNNPs9AZfkZ827NohgOrg893K99/iM3mRgDVReXswVpuojVtF1qzYDSj
WgrhJ/hMm9UKPM2+VZwepA9V2T+0MsA4ILgjwgDoYD1PQcJxJ9gIPyITaR2Icannxeibogxi
VS9fTy/cnTbj75I+Q4AFxJsE0XwzNx7INYmkgMNLvoUWwtjn2crXajxNEwCDBRjv5r+78Sti
unOjUuHe59yuyf0ueEZd7fQCqWbMOS+yv4AwJdgP6+yLiIuwAdOnmijyFvhBimbCJAe9PpSc
cQwagsuvEuvEuvEuvEnHeAO0OaV9UGuxwbOA/c3Tbj77AWQczsXZC2sBOAXNUQ+X2ka7cidU
CYRDQI2Wv6qucdTZwo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR
2CjsFHYKOwUdgml4YgggR7fR40vDAAAAPZR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2Cj
sFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHY
KOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwU
dgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7
BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdgo7BR2CjsFHYKOwUdggTncTbj9Ha7UfwP024/R2u1
H8D9NuP0drtR/A/Tbj9BdcZMFnqVW9h07EIKuietxzSnyrXaj+B+m3H6CwJoGwcGIdPdYtkm
hNgN0DDiABC/Bs4CKcDE96qqMKMKMKMKMKMKv2bPQFGFGFGFGFGFT7N3oKjCjCjCjCjCjC0c
R3SMKMKMKMKMI7+j+xRhRhRhRhRhauIzJGFGFGFGFGFGFX7NnoCjCjCjCjCjCb6nQ5KMKMKM
KMKMKMJ/qdTkowowowowowjv6P7FGFGFGFGFGFGFo4jukYUYUYUYUYQ29G9yjCjCjCjCjCb6
nQ5KMKMKMKMKMKMKv2bPQFGFGFGFGFGFT7N3oKjCjCjCjCjCjC0cR3SMKMKMKMKMI7+j+xRh
RhRhRhRhauIzJGFGFGFGFGFGFX7NnoCjCjCjCjCjCb6nQ5KMKMKMKMKMKMJ/qdTkowowowow
owgaCCsw8v0b0BCFAc2vB+U47pqW8IAIZk2oDc+qbZL0CG4F3KayxD18F4FEmSCMHUdDsghL
QCz0NPDRkQJm6wG5oggoLDXvZ28I2HsANyaBGRb3Cd6ONlfIzTDwiK3XDLbngqG6MMBDbY8I
CWKyBvU6BeSaXudrCd0ZGoFQ7t4CWDlDcs6jLedDoFNiFOx9B4aMiBM3WA3NEV7KbWCWsNbj
XwtmwaIJgmHTuAPlzOxPD+k/C/3zsR4R4FdcC9MkRiLM9xreEVJnVz+pRdM3NFq+7yQjwDjH
w3nKwIWDVstUJkG3sfQV8JsARJlb8lTWjssGtW8LZsGiCYLXfvFqGYmzdERUvQsvdh4QcwNQ
h2AcjBEYclS1rng/hMSOz2nuxRN1Dc7eqh7sJsBG9h4TOQI1IQDVskIAGzB5huGpfwipM6uf
1KHlqk3VMdSx2Q7CHHgJYOmLndphuGpdFQlKoiPYV8Nc8/ZVtStlYccBHh7eEQ8SCEAg2yAN
Vhe5altk5m2U7hwWof0TkJ/MIES50c320RkAggku0s8L1LCMGLasdkNRGqJd5qDROYwA6gHw
CMFgV2ysThRcgB1pT+k9AaJL/CL+XhCH8l1RSt7Ivkpci48J4ChoRwXqqJbuk0ANov6K/pAa
zQeEWRJZOt6M3N3QcaJfXfvSnz4SbyyrTRv7RQPYqBIoB4QcKxQpJvgqBq7J/Gi7cE7qDwhD
+S6opW9kDs25FRewml/EQgk3JuKO2x+EaDIrQB9PCb5YAGrmr7IOif612d3b8PCFgzCdEWDA
VTiFAaJgDeuuB8DwlvsAxrqd/VNXpEhI3FBXwkmqD9QLkIGHTtHyQEIJEBc6+Gr0FyV34TuR
Cs4DDejnwvYdxHWlENTDhrvcszc3fwuUNN26LYmvUfU/lCGmAwHhZMZhXudFy+gUXd6PXXwh
YMwnRHmQ6wwPIUDgoVuCDwA5AFjui2Fe4kh1o9dUQbUHATq5NR4RCCqch+9B/qycUk5h0Cre
E/8AGA2J8SBgVeY9h0sraCBqb2H80uN2KVnQ07iQC230YRPeoFKFjXwn2Ybk/wAJOVrgtq+I
QiDpAME2lhGmqLMVsCNRDVLXTLVkXQ4g3nRHcA5LPVRnQMnGcDehomwbPi7gteboG+hjD1ou
eHQ3YSE5rRhEgAKOGKrToRnzsAtCY1C7cfwoUvjlk08gEuXJJJ5J/wDQP//aAAwDAQACAAMA
AAAQ88888888888888888888888888888888888888888888888888888888888888888888
8888888888888888888888888888888888888888888v4MN1eQ8888888888888888888888
8888888888888888888888888888888888888888888888888Mccsc8cc888888888888888
888888888888888888888888888888888888888888882ww07930480w1w88w0440488ww08
8888888888888888888888888888888888888888888888888c88+/sNssss8d8csc8s8M8c
c8ss88888888888888888888888888884488888888888888888888888888888888888888
8888888888888888888888888888888888888sc6MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMY88888888o888888888888888888888888888
8888888888888888888888888888888888888883V8888888EAwwwwwwwwwwwwwwwwwwwwww
wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww1hc88888888o88888888888888888
888888888888888888888888888888888888888/n188888/y8U88888884o888888888888
888888888888888888888888888885xlKLxx988888y9+8K38887O/8AFPPPPPPPPCDDDDDD
DDDDDDDDDDDDDDDDDDDDDDDDDDDDDzzDDCCfTDDDDH/zTmjbXTDDDAhDCtbzDNPPPPMPPPKP
PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP/mTt8On/PPPPPPPPPPPPPPPPPLAcnfPPPFPPPPK
PPIADDDDDDDDDDDDDDDDDDDDDDDDDDDD26gDA/7zDDHTDDDDDDDDDDDDDDDDDDDDDDDDDDDN
PPPPJPPPKPPPPPPPPPPPPPPPPPPPPPPPPPNonf7/AE13zzzzzzzzzzzzzzzzzzzzzzzzzzzz
zzzzzxTzzzzjzzSrDDDDDDDDDDDDDDDDDDDDDDD+EPDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
DDDDDDDDDDBzzzzzzzzwjzzzzzzzzzzzzzzzzzzzzz4z/wA8888888888888888888888888
88888888888888888U88888888r/APPPPPPPPPPPPPPPPPP9ff8Azzzzzzzzzzzzzzzzzzzz
zzzzzzzzzzzzzzzzzzzzzzzzxTzzzzzzzzoY8wwwwwwwwwwwwwwwwh0wwwwwwwwwwwwwwwww
wwwwwwwwwwwwwwwwwwwwwwwwwwwwwzTzzzzzzzyjwpXbLLHHEfH7jTzmU5zzzzzzzzzzzzzz
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzxTzzzzzygCLDDNKPNLDDDBMWIFLLDDDDDDDDDD
DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBzzzzzzzzyjzzzzzzzzzzzzzzzzzzzzzz
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzxTzzzzzzzCDzzzzzzzzzzzzzzzzz
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzxTzzzzzzwwgQwwgwwQwwAww
gQwgQwwgwgQwwQwwwQwgwwwAwwwwwgwwwQwwwwggwwgwwwwwQQwwQwxjzzzzzzzzxzzzzy57
zxzzwxzy5zzxzzwzzxzzyxzyzzzyzzwzzwxzyzzyxzz67zwzzy13zzzz37zxzzzzzzzzzzzz
zzzzzzzzzzzzzzzzzzzzzzzzzzzyfz7jDzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzyzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
zzzzzzz/xAArEQACAQIDBgYDAQAAAAAAAAABEQAhMRBB8CBAUFFx0TBgYYGRoXDB4bH/2gAI
AQMBAT8Q83gMjr3gq2rw0K1aUPr3hGvntHRzNa1/ILP8GiuuneOjis1dfqAsOZOGmuvaemGt
fMcNNa5YrKCsexk9apxj0wFNdO0Aoo6uIJYGutc9hQ1B1z77Cy8C0XmvLyKUReTDirjaAOqv
gHLXLyGCAYnPP15DuSEZRA6wAMbRIAZgl6y3fwsnwutCMsJ9o233iNU6GKAQDFX+8M4n+vmC
8hlgL2SEkR2aPuVYVPPACaWN+/eAghjYIAzD5Uv2gAAQ8LJcEJADMuh7BKqYQ+yBVqPPaIAj
AEICkLqlCNX/ANhxLJHWsfd9qRmY+8W+yWTH8fyAuowBVQEj+yXg+HEgVMY2szKzV6TJgHpC
CqD6zNoKigcu8AAhulka5PT+TIUOZhFqnn4Rticvf9b6QBkwZAVQ4BkZdDwEQCnSOXeAABDE
AgcWp3YMggAS3hm2/EaOO1R8mMM29YAAEIQDQwvKDVHzDBwgG2OT3kmrnkJn6chAO3DxtvVG
NTyhtBA6QFRxE12CQLwEG25EgBmWwvpFdo+5YnFyKHOKi+YQSye4BWUIKp5oFi2+NiJa0tg9
xLFBDBFBJSMY2P4jrfeFWVPqMLw+5Yo9TEAMlQbuIUms/XGstgZizgGz6wBsIABaFkFdmwHB
k6YE3PzPVPzBCBP+wX5WnrvRpt5raNNzUBeyoC8AHH4OS2gVWLE18L1xyWJrrXLbzeAKixNf
CzeApsGuLgCpsuJYAqLhBn8nL8g//8QALBEAAgECAgkEAwEBAAAAAAAAAREAITEQQSBQUWFx
kaHR8DBAYMGBseFw8f/aAAgBAgEBPxD5eTfh9iZgcf1BZwVgs/LDvCKgeWmThh/wl0cNMDTz
j2MVV5l3jo/LOKqmagr5wP3Hng/Ov1FBXzh3GHnnKOjhpiKrDzzng4pfWaooa4EO/l+5hLL/
AD5yioo6uChcFPPNmK86T/sFCPNnYTdLy95m5bDdoKeec/lZhqYS/ggBivhgzJsXhQop6GR+
BiEBAZTr8DtyAB4J4fcISN9IAkoQhni/b0jSLVVPEVcBxMT2I5deIjQgkfikdbog1AfvlDuY
SwFolgGK9V0lKNBswICtLdu0IIKOgQkA5tmWGzfCSSz6Wb1IASUJYi0AHQQL0s4RSgbNIhMF
QlLJLgNG+MBVP9QcBAeFImz+axGQcBHPohAj/X9hCocDaCEmPolkLVwBJQiW/kIEVHjM6Jb4
EHUN0yKGhq2u0ITPtL0UC+/+y4NnYPuCUoNg9K7EZ+9ISAcMBNMAJRiWQsDKgiXTt7Qkks4l
GSjFHtizNQh5npi/vgt1Fcq5CJoU3QkkzASCxPAGGUXKDLtNUXYGGhUI9wKyDaZkDbTCS+rw
v7qtCg2wUwE8Ybq1iKaABNoQRQ+yAJKEvQQ30jtVdJfmtxtDJRyVsGGEC9gdQMwGOvYGUMAC
S12cBKb4a8vwby6fb9QGzQF/4gbMRRcecVfogUHXbnFsz0l2h2WJBA4dWEACkNueujDiUQZQ
u2uEJbkwkmpjAU0bmUKCrhfYcpuxyhRkD9QuQ/whxfDd3pCvsBXS3TJ6QriK+qK4uGmksDT0
s3pEOkeIppKN6JDoY6vEU0t8yWkKekKBYEMKEsvEUxUJddFQl4EOPVDpM+fSOh3fzvPOoGGX
+ff/xAAtEAEBAAIBBAECBQQDAQEAAAABEQAhMUFRwfBhIHEQYIGRoTBAUHCAsdHh8f/aAAgB
AQABPxD/AI8tGwdCi6t8OZgAkHrjUob9nSgvTymF0Y1S0Gjeni8Y7AlGV86E/XDB9wBSLheo
4Zf0EKRcL1MKvoStaDXz+BUSAhWpN9u8xrWJppyh0DqqGBSck4NQVB8P4lxsACVRc/I/6M/g
smlUkMPZQv7N/DfS+OQmpml175HWTwR00p/OQs89kGq/POW0XdGEDh1Qd8KZ+k6i2ipTjFc5
19CZQIkS4kuyxq5E+LjIXtQtq4FJ95gbkq04MOoX9nE6j6piYeRa5O94wgh9JVHNOq7PONAj
wokHsECjBwL7qL7U+40anb/RbVZrQ9bE20c9sGAhomj+MWQ6ROU1rmU4wwdgKCcC8srPwFDq
oWi1Yd1XNiVW0pauk5VygjvdReiYJ7RBE4BmpkfqSSJCvWHfOJphp9xzn6SK+4EziBaB++G8
1PBTfuQ3kUCxZ3mtvzg9hgH2Af8AKx9dXRanBry7Jy4l1kqSKrwdM68YwsdIiBe2jpNuoYzW
pBMKDQrcrrW89d4dE+SW6lzr38SF2IIU4rRk2stIqWgpN7h56zqgHNUGdQR0LVD5wGo7Vw+B
sORNmuuDqmN+4RqUzqJeGXBALyNz2AEH5dvBg2RcDojcIKRFJTKvASA5BArFjrNwoDBngT1R
sbpDjndxtNHm3EVLsJMBPkio8Mmk/dvZinNG3GiEaJy3qbwWoVQhPSnDwOyZWGBD1TuOaigU
3g5hrHXwNFsS/N6Y6gSOgrgXT0SWLMfCokId1Ic6ujjKRqpCggV3jvWubCA+1a69vW8/xhMB
YaQygBLNj3xElJECSU0jYjJY4O5TC3CNSmdRLwy4RjvolsrioZtWdLkPFoyKcKFV6APzMfNw
4Qg1kZyN2dMh5lbCMp2As0FN5zzg0cTRvYs52TZstUCtQW6Dw4QUEYCOIiAhU3zqYde7noEG
IchrZzvWTHkJdIgTTo68mSLPm1Q3gpuxs74lCik4emQFUWQM1Eab1vxl6hIlcNiJfj+MsZwp
cgA2rhODCIj7gunzXHN3kSyUnoOoDOo6ZGVFmpx4IBV1OmTCMgjDQDgiJbecYWGgG6W6gWwV
7GIGjnmYDAoiPB9sKr4Q0QNkA70hmDwKbzMOrwbX9uMXnXxypNO0Djc2mRkgUQl1l/ZPnEAN
F2sBQE2KBTeP4Iy0CsqPA60cb3lhu5aJd/mU3R9bq2Bdg6TjG7rKqtB02usmPtm1C864+coi
3qp3TsjOTvrLnngCqW+sLzW+cSDZsG4EVERXq5z/AN4yrqeej45xF2lyClOpthh+MCCrLkEO
TnS566drf0v6zIXXEpD1jdTa/HGSXyZFfeZew13YcTQ+zHVeQT4e+h04nQ0hJ22qufiZ9mjz
urd34dMCK/y27i49oSuOZkBIFs7L5KWapTmTOrvMaOaLYX9TGpLFoFFB8higgcY4HhdSwvTe
objQCoGTglKoWIi6w+5d8RlMe5eu96UU4EETo3fFzgSICRxXXW9x+M7I594nJOj9fjOohXJs
d+7Z8fOeuna39L+swgwII2AW2GCUl4zgE8GqlCOBvf2cdQJt0V1xQonRmspFgVI0NArufGJR
dgCpbmq9AHGElnCTAdVj2H6s0FsHbKluyR1g0yXSBJ+5U/ZD4xpIQO+Y962uvXvmkYGm98By
degyPqUzEja5c9Msiexg2PEbT4wSTtIa1FL9s6onGnTOd9V1zlWJGpbLZuc98SK0AKI3Z1Hh
Oo4WcqdOCHRSp6rOJnQR89gBRgAOX75QzNV9yqrijviD7grmACmAA5fvj2oQEIjfoEGj5uLj
lMw8hndpyXCw4BI030dDqPQRSWTa+7lNXThVUhREO3JtilA4yZq+5VhwCttN8YLNAgCu7Ift
/wAbkZgVVgGB+GkA+E04hAFRAfquLggULBywb/pc5alEciVdczHi66ZDUIOFBwfhwV4Nmyr5
XGuTAHB8DaBS62v7YHsLVC0Br7v9DlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKl
SpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSp
UqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSumBVbgh1H+mlT4Ab11Xp3z/AO3bSQvV
x1/0xUG/ELCDHTtTswrwOPh9UIpKUOlP3O+bMg1sco7NI/6XqJQ4eAKqvAGA8lRnmK5HRA6B
sWOKPoIfyq7V2qr/AGHMdNC34A2vwZZ4LiUSjgRCJuGKQCU2n/Q1RYqiog2T7S01zwMGg0Qp
4AbnR8qr/YEVPWkoYaKn3dYp9ZqoqMJ8d+mOnxW+VFTA6w4LyzdJhEl+41/oQgQIECBAgQIE
CBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECB
AgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECFXX
yzj0ArSdQrqrBgwETynEP6CgTk4Q25MJE+yH+hqhg+GJVYAIuzjgXp/YYn4LIBioWo1Z1Q1a
R26X4QkA54dYkT/oYjUoQDiViwOVBgVZi2rnUFEOVaH7HFKGJa1ASh3gIkjOFST3hyV/Lc3B
NJopXyB3Or4RD+o9hBshUADuqHbe0MJb4BANnqrGJythgUOHgCABwB+biNRKHDwBVV4AyXu6
bUzVVz0Pwx/8YQTo8/d+DS3wYsjGJp2J/ZUIBxKxYHKgwKsxbVzqCiHKtD9jiJU2l0kOBwHV
ka/9istXRQwlcB+PLypVqUH78CGwK8AgprqA6J/4lEf6aUOHgCqrwBjLfIIBo9VaVORssOwo
2Qqqr3VXtvQH9mRA/G2CvuoGJtGA6xJYXjtkKlNKK4ODXK34waTKVRITfy/KlTmMEpTpAnIz
hPEXHcLKapxn7y6M07g7HgJx0z9HgxdkapxNu+/wqWh4SqGwVxnWP2cveqhaJv7xpOPwCnwV
GkJoXYt+fj8MjeRIoa3QDu9DznnjE+XqcpP1z+bQpp0nBu+2tzPUHq5fp1z/AO3bSRnVx0yj
NwRLLsIm2VzB6jUVDYQeipvmT9v6XH8L7DOiMVNdsJqMPiiQa2MdNIjdRKm0ukhwOA6sjX/s
Vlq6KGErgPq5BDDQ5IHAbdd/KQ4BBTXUB0T/AMSiP9H/AKUzy8GcOe+aZ0BBDWRxXrZQtfwW
QDEElRuXqrqw/syLX1+qfcIfs4cWjS7VQRGprjnZlmBs7kPot31frjEHNVANoGqw7Tesm7lH
HvoWHj8pVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqV
KlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSgVwbbJWxpsbQ6Ec2DUgIoKN6bqXmocNNBg3gZGlnP
T+pUqVKlSpUqVKlT+CZOXj4H7Ze0+4UI89q4HkY5PU6rxC3UweBUpTXeqv6zXGfJS/l3aOzS
T9sXd4yPtCKP8MJ8E1gk6ABeYyZ/+N/4wNHosAVpQvZGtdu/Rfz7pDTpL++X9Ogpp2jUu++t
TBnIdCNcB2l09d7ufOTqp72F2u0FzQGALQa33Dg4xqLixUjdRevsdv6NSpUqVKlSoJdouroA
kO1UrgFqMoZP30jpHYiP11KlSpUqA+BRG0GCwpYMu81Ul3TG1ZpoLG7dQmwHqF9039VSpUqV
K5LT+ZVn5Zqa8y4hUGgvKfhjp9w6QUY7NPX+h0I+hDyroDaoGdMISeShNOW1AGwmcMxDqbeo
cnwNl0n9m3ClaBIsuq/hkGbxJoimDtWu9/10ocPIERHkTDEm30tCL+gLzrZh0I+hTwjpHYiP
0S+DFsYVdG0M5K68QJEBUWF6iURwh6GNN0XkBoIukkGGA5WKq5VVV4NvAHAfmAjUP10MoKrq
ECGiu6J+FugApZAZQbWjedku3YTRGxFoPVKprmVYslEDKLuJ+/0vqGgymw9tu3O6DHDe2gok
VOz59+EaM5y4vMJV+7CArAv+HShw8gREeRMcSbXS2iH6qHO9mAUOHkCiJyJ+DpAovfQhrdNL
o1RhSekV0BQQ3ZyHJAxf5YUCzoBxwFhal/syNPfu6AVcMQmEAKbenJPyZUoQDiViwOVBgVZh
GWdovLgZCDKhaDNgIraRHV5Y7WBDa4lDh5AiI8iZ0tDd0TumhH5LzvEuwACToJUUVn9HV0vD
zSG4E0FU35uFUJFoRRUClpBdN8wI6AiQaUtLEQRE6ZcgiUHjQrpVeUljityoERW7VruDNbtQ
Chw8AQAOAP8AE9CPoU8I7E2IJi2jHADOUllhCqzeNy2LGInCaRyPDGYPjRsRYiu4nLYEn9qR
CJsL1EbUO32+5zgjSATdgiiJK6rXX6YQ5wYCdDq6OafGX0BJKoXOEVllqh1f1XJ/SQKSn7TP
SvOelec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvO
elec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOele
c9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOelec9K
8/hjY4tlsUdQmx6Z6V5z0rznpXnPSvOelec9K856V5zejIhAesU0ONuzUblCmTTdS6BoV99h
M2iRRuoTqv8A4EAM9K856V5z0rznpXnPSvOelec3nD7liVFd6O/u5zvS/YzoBiprtnLxi5TC
jVKnY+M9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvO
elec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOelec9K856V5z0rznpXnPSvOele
c9K856V5z0rznpXnPSvOelec9K858yzKCLFl5z4AgRYJX6vnPSvOelec9K856V5z0rznpXnP
SvOelec9K856V5z0rznLAiUfZ/pJ4R8wtU/TOGUPlYGjBYIcd/peYJBsCOkm+hfnL3qCUQAY
2TX3bc1201CEOBIdk+b/AJmo7ARBQlLYE6pNncw7dAggpss0nWNvGt5/9/Zkp4uOk53kYeUG
k2fuUFo68Z0pa0u3iK46WfrgUOHkCiJyJ+KUOHgCqrwBiFxtKbyWwhanLhFw73dwC7DtAJ8H
Q/k4iUUD4CqL78ZoCwHv68acGsX+dqWsQBAivUWzQLs75N0yTacAoPMan30HYy4CAfGqB5Gu
MK/RXoFoogk4Eb26cOgpbxJqLqLOXodj8aRKSU7aPmMiRbnWlLR3nPYnSc4pCSGQyLradm3Y
ufISaByqOsTnodMpeQkYV4H4NM1983jBrOhkL2AfuBXFn5AdGUvSggZo5av5OInWhDkgXWM/
eNQZK6dFGcJ1v+bqc/BHigNSjpdnxdxdIcogVg29c38OBYWh00rt9966goBMtG9lOkG3Rf6X
6owqUWP0fGfojCrRa/R8/lAiFA0UGZzHTPnFI7RVM4LwwLJ8f5mol3DecCCLMDeiweMXlg0j
URduNHIUzWmxrpiijtd6pNGHopXIAsOqfl0j0uOpbCvYt6bDZLjqNkStH5Cqq8kN36CjpNH6
FEx+QdPYcrtw5OEOExcQDQuneJlnKdhoUeRr7mTdIhUs+43/AI8gQIECBAgQIECBAgQIECBA
gQIECBAgQIECBAgQIECBAgQIECBAgQIEB0ZQCbvlmnbrU51hORI6RS0NpTapj4ZBXybh1GtE
6mIIsnwIAGgH5VIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIE
CBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQ05MLV+yv9IFw50gEXQ/nAcS12qptugJZ
9ED1V5NdIJ+jgcrD9F4prbrhxMXUKhCIuELUK1x4hpW3IpDo1HH+Oqfv2yBUuWcZChi2tVNg
doCJYwbVzqCKnKsJ9xi3wYtjWBo2r+YSKjZ0iJIN++JHr1yDCIWq70a6/wCTqLX/ALFbIOio
rK5TKlTIXS04HI9WVo8fAaqu6ucxglKMak5X5jInlmSrCOoYlzi1YqSgISIhBL+/+RqLX/sV
sg6KisrlMqVMhdLTgcj1ZG1c6gipyrCfcYgQDiVgVeVAq1Z+bSMakHq+YDh++IEqn1bYtNb+
2dPc60WWmWP7f4XXmXEKg0F5TE54A6hwUFflD5ypUyF0tOByPVkbVzqCKnKsJ9xiBAOJWBV5
UCrVn5uIvG+MsHTX67AO425aYG8W615rqmoKhFFLvWADUwSHH6BRE3E/wZUqVKlSpUqVKlSp
UqVKlSpUqVKlSpUqVKlSpUqVKqQ4/AKquoGM9pJACQiGzZ7OuH8IkA3SsCruoFWrPy+VKlSp
UqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSpUq
VKlSpUqVKlSpUqVKlSpUqVKlSpUqVKlSvQgS1fdD+zQBVPqW1K619sVsYE8TI7Fa8KBTHIWE
uGAA00clQKDNqH0K+XWhwHDZhf8AAvqGgymw9tu3O6DHFISAOGUC00csVKHCequ+lYWC9DsW
pfzuRqVuwz0xATRCWOVThg8sGlagDt1i4GuUt0XmgHoht7QmB/Vl8GLYwq6NoZ/0wkdjlvLt
msBgIgRWcjp/W6EfQh5V0BtUDELjaU3kthC1OXCLkuGALlK0m9bBmtoZgUOHgCABwB+eSNRK
HDyBER5Ex84VLS1RKyLoE0AbOM5FjpFZU2tdIGNl4i2O4Uw3Dn8MV4VSENdbq/pN8/hk5p1+
IJOXr2/X8Avp9eQgiaBnBxiDSl6HBaARnl+F/FoU0bRoXXfe7njjF+XocLf0wvIsVNaiA3Oj
5z1C6/7JfjHcy1E1qIHc6njP1rZPlW71pY3fLnxdFpHWzOhY732mCWxhKo1E1l3f0z5tBdF7
poU+Qc6yv+taZWhhDben4NAocPIFETkT6Y2C3SlBqHKx5LAXnVdADsLZrlNHPHHP1A7Qp4hT
GDX/ALFZauihhK4D85kSJIFVQAO6oYjOg+tKOyIjyLnP0SRFH2CoDNOD8AnA8aTb5PrqcRgl
INag5GeOkt3PF43+GK1FR2EDqoa4s/f8GnT3OlFlgsr+/wCB6KUwQpXquIpYmgdAGoP6MWLJ
RCWI7i/vnS0N3RO6aEfkvO8ZSYSK4GBAOGfPH4c+9BGGBBCENfTVVVVwJsPsCiPIpxvHV+fd
JFB2RdNG7PzqRiypHB1ToUGXrkPLaVVxI5XQrJlGaknlqG2waG5dY4EmvAAKUDukTjrk3SYR
JfuNf3JAgQIECBAgQIECBAgQIECBAgQIECCKLH8CIjuJ+CRBFh+BAA1A/NhAgQIECBAgQIEC
BAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIECBA
gQIECBAgQIECBAgQIECBAgQIECBAgQIECBAgQIENuTCRPsh/zeqEahGoRdA5eEJMGAD0cOFd
/cEYUkRhpwY5h3AGGKiOkc7/ANMVCKcpSQSIApptjxxhu7c4ENHQAFZxxiJhmxOzTK8xvnWH
kwICpO2u1ueleM9K8Z6V4z0rxnpXjPSvGdKZ3MnS1xb/ADnpXjPSvGeleM9K8Z6V4zrTOpk6
2uLP4z0rxnpXjPSvGeleM9K8Z6V4z4tkbYW65z0rxnpXjPSvGeleM9K8Zq3abLZuuef5z0rx
npXjPSvGeleM9K8Z8WyNsZNc56V4z0rxnpXjPSvGeleM9K8Z0pncydLXFv8AOeleM9K8Z6V4
z0rxnpXjO9Eo2TenEueleM9K8Z6V4z0rxnpXjPSvGdqJRsudOJM9K8Z6V4z0rxnpXjPSvGat
2my2brnn+c9K8Z6V4z0rxnpXjPSvGeleM+LZG2Fuuc9K8Z6V4z0rxnpXjPSvGbt2my25rnj+
M9K8Z6V4z0rxnpXjPSvGd6JRsm9OJc9K8Z6V4z0rxnpXjPSvGeleM6UzuZOlri3+c9K8Z6V4
z0rxnpXjPSvGdaZ1MnW1xZ/GeleM9K8Z6V4z0rxnpXjPSvGfFsjbC3XOeleM9K8Z6V4z0rxn
pXjNW7TZbN1zz/OeleM9K8Z6V4z0rxnpXjPi2RtjJrnPSvGeleM9K8Z6V4z0rxnpXjOlM7mT
pa4t/nPSvGeleM9K8Z6V4z0rxneiUbJvTiXPSvGeleM9K8Z6V4z0rxnpXjO1Eo2XOnEmeleM
9K8Z6V4z0rxnpXjH9QEYWzZ+v8/2es/6HZEMLBLt1kxVqCDdS0J/3936WqSKMwKo9QBN3NJp
qgiqgJF6HG94JpBAESl39F89YlYF1klbdxkrCzl0k4XA29K+oGitOxCfSASwONIlGta0a5xJ
LqEAh81Cu9U7/S6GUdCgCujab6ZZDSCwNxaTSI3gMVaNA6Juft9KELBBymndxLb1kxZHQk2u
ANjSL8z6V7BgzYpUYAtj9s0e3VFoBCpJsd7DAZIEYKbL1+gESAVcgwVBQKaxY2bfmYtWMqsh
XQ64k7P0gEsDjSJRrWtGucNoZfSNooDcx1g/S0xhvWeygw+Y4pv7NBTQUhrB57sTjbFFbjCi
RGGn6dojg2884Qq9hhZKiFFcHBrlb8H02RfQAO9LftiGBQkUQ5XcHRtTBgAPMX/v7/SzKDdJ
VoQ6HyBclVdbQQF0acT7L9M0VVib1K9e2MMCb11U8ACdOUOv0tMYb1nsoMPmOCQqDUEIOgiY
6TvjovQmp/K+PpMuLkmwASqgb5cXwCaJQECkJbXmT6boiRqd9E/jLki00psbNOuOR3rJUjBQ
2BVI8muJ9MqZQ4Ktk7E6kM4X9/wupWnC719NkX0ADvS37YkLSJKigUjAgk3vG3oW7iU+igrA
usA+Td2OpKY4Uurk9vDWWO9AZSTZF+ksYXOVENVtzDje8sEnDNgg2eu1m+/0jR6naBYZxFQO
8yd+wrSY0DBZlLQU1zD+yH1L8IoBAWGnBdOgQVaHg739PpRIEc1VAgj2bF4w+mC2bNQrqi/c
dRNIE2APWML+x9HGXpXYlwcjwtUNoaNADs842yY6IjF2LbAfTATRJIGILqVTg3h86UNIMSm8
NbOH6XViAKxAHZkfvhvRckE0bR23pJ84arcGoupKfMKqz6R60dlUnico6hqZU80YwBCDQqDT
vX0gvaWm8hQU1QxiGsCvDg0Bq7BarN7n0jwAR/XEFV/cCIh0Vi13rNz9Ujt2bJrhe79MBNEk
gYgupVODeKBkGGRXV2g2g8M+oiNCbSOwmiMeGs3kCUpABYoAF1Z0+lGyx2EqJOE56uECS6vJ
9Fu+r9fpXhdNCtLQelxWjhVABXulNXRxaCSoWzcAtCfB9LgrcOikNaUcPBh0EU5K2h0cPyv0
gCIdpABDrAy4nAohs2gWrHbhjADK/JgH7B9Jw1lFbospwBmoaZhHI6gcLRR1YdO30gChM1DJ
1uLf0MgYfWiqdHMdQJPpBbCYuBGr8XKOoJooS0u6uOuDgABwBo+lByppQKTqbU/Yx4w+5E0I
3bsqvP0rwumhWloPS4AuB2Kc6UOoA9d5TrcHYIfQjwwgOnzhpDBQWiRw9Sr1yVTSbNghtQ1N
Tl+krFaYa2Wxo6rTfYbc43AKDBo9W/H0q8BfrTnWI4z/AICqTu6qmXdk5aQUP3LX9P1/3SFH
lIaqbSOu2CyAFFUjyHUfwNPetKGAxBHpbz2+m8fZlgcsN4IgnD/pHR1UvQp8xm/lzTT24ibI
WpxPi44tT4a0AXpVHvrG+W4FNKEqJF4nTBfbWITghtECqd8OiFnQaitjsdOIYrJ3KemAqDU5
0zD6yYxoATkJvrrnDoXStSmrwaPTjGSlJhogwLaWsdzHsk8pOaaCwtA6T/Smpw1KQjREiIg0
xKkDKjlQq/K/8gf/2Q==
--------------060206020904090400070005
Content-Type: application/vnd.ms-excel;
 name="hotel-costs.xls"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="hotel-costs.xls"

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAOwADAP7/CQAGAAAAAAAAAAAAAAABAAAAHAAAAAAA
AAAAEAAAGQAAAAEAAAD+////AAAAAAAAAAD/////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
///////////////////////////////////9/////////wMAAAAEAAAABQAAAAYAAAAHAAAA
CAAAAAkAAAAKAAAACwAAAAwAAAANAAAADgAAAA8AAAAQAAAAEQAAABIAAAATAAAAFAAAABUA
AAAWAAAAFwAAABgAAAD+/////v///xsAAAD+////HQAAAP7/////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////1IA
bwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAWAAUA////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAA/v///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///////////////8AAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP//
/////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP7///8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA////////////////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAA/v///wAAAAAAAAAACQgIAAAFBQBsCckH4QAAAMEAAgAAAL8AAADAAAAA
4gAAAFwAIAAEQ2FsYyAgICAgICAgICAgICAgICAgICAgICAgICAgIEIAAgDkBJwAAgAOAD0A
EgAAAAAAAEAAIDgAAAAAAAEAfwBAAAIAAACNAAIAAAAiAAIAAAAOAAIAAQDaAAIAAAAxABQA
yAAAAP9/kAEAAAACAAAFQXJpYWwxABQAyAAAAP9/vAIAAAAAAAAFQXJpYWwxABQAyAACAP9/
kAEAAAAAAAAFQXJpYWwxABQAyAACAP9/vAIAAAAAAAAFQXJpYWwxABQAyAAAAP9/kAEAAAAA
AAAFQXJpYWwxABQAyAAAAP9/kAEBAAACAAAFQXJpYWwxAB4AyAAAAP9/kAEAAAABAAAPVGlt
ZXMgTmV3IFJvbWFuHgQKAKQAB0dFTkVSQUweBAsApQAIWVlZWVwtTU0eBAcApgAEMC4wMOAA
EAAAAKQA9f8gAMAgAAAAAAAA4AAQAAEAAAD1/yD0wCAAAAAAAADgABAAAQAAAPX/IPTAIAAA
AAAAAOAAEAACAAAA9f8g9MAgAAAAAAAA4AAQAAIAAAD1/yD0wCAAAAAAAADgABAAAAAAAPX/
IPTAIAAAAAAAAOAAEAAAAAAA9f8g9MAgAAAAAAAA4AAQAAAAAAD1/yD0wCAAAAAAAADgABAA
AAAAAPX/IPTAIAAAAAAAAOAAEAAAAAAA9f8g9MAgAAAAAAAA4AAQAAAAAAD1/yD0wCAAAAAA
AADgABAAAAAAAPX/IPTAIAAAAAAAAOAAEAAAAAAA9f8g9MAgAAAAAAAA4AAQAAAAAAD1/yD0
wCAAAAAAAADgABAAAAAAAPX/IPTAIAAAAAAAAOAAEAAAAKQAAQAgAMAgAAAAAAAA4AAQAAEA
KwD1/yDwwCAAAAAAAADgABAAAQApAPX/IPDAIAAAAAAAAOAAEAABACwA9f8g8MAgAAAAAAAA
4AAQAAEAKgD1/yDwwCAAAAAAAADgABAAAQAJAPX/IPDAIAAAAAAAAOAAEAAAAKUAAQAgBMAg
AAAAAAAA4AAQAAAApgABACAEwCAAAAAAAADgABAABwCmAAEAKBzAIAAAAAAAAOAAEAAAAKQA
AQAgBMAgAAAAAAAA4AAQAAAApQABACEUwCAAAAAAAADgABAABwCkAAEAKBjAIAAAAAAAAJMC
BAAAgAD/kwIEABCAA/+TAgQAEYAG/5MCBAASgAT/kwIEABOAB/+TAgQAFIAF/4UADQDjAwAA
AAAGU2hlZXQxhQANAD4pAAAAAAZTaGVldDKFAA0ApCoAAAAABlNoZWV0MwoAAAAJCAgAAAUQ
AGwJyQcNAAIAAQAMAAIAZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIAAQCAAAgAAAAA
AAAAAAAlAgQAAAAaAYwABAABAAEAgQACAMEEKgACAAAAKwACAAAAggACAAEAFAAiACEmQyYi
VGltZXMgTmV3IFJvbWFuLFJlZ3VsYXIiJjEyJkEVACcAJiZDJiJUaW1lcyBOZXcgUm9tYW4s
UmVndWxhciImMTJQYWdlICZQgwACAAAAhAACAAAAJgAIADMzMzMzM+k/JwAIADMzMzMzM+k/
KAAIAIMt2IIt2PA/KQAIAIMt2IIt2PA/oQAiAAkAZAABAAEAAQCCACwBLAEzMzMzMzPpPzMz
MzMzM+k/AQBVAAIACwB9AAwAAAAAAJQLDwAAAAAAfQAMAAEAAQCUCxUAAAAAAH0ADAACAAQA
lAsPAAAAAAB9AAwABQAFAJQLFgAAAAAAfQAMAAYAAAGUCw8AAAAAAAACCgAAADEAAAANAAAA
CAIQAAAAAAAMABsBAAAAAAABDwAIAhAAAQAAAAkAGwEAAAAAAAEPAAgCEAACAAAACQAbAQAA
AAAAAQ8ACAIQAAMAAAAJABsBAAAAAAABDwAIAhAABAAAAAkAGwEAAAAAAAEPAAgCEAAFAAAA
CQAbAQAAAAAAAQ8ACAIQAAYAAAAMABsBAAAAAAABDwAIAhAABwAAAAwAGwEAAAAAAAEPAAgC
EAAIAAAADAAbAQAAAAAAAQ8ACAIQAAkAAAAMABsBAAAAAAABDwAIAhAACgAAAAwAGwEAAAAA
AAEPAAgCEAALAAAADAAbAQAAAAAAAQ8ACAIQAAwAAAAMABsBAAAAAAABDwAIAhAADQAAAAwA
GwEAAAAAAAEPAAgCEAAOAAAADAAbAQAAAAAAAQ8ACAIQAA8AAAAMABsBAAAAAAABDwAIAhAA
EAAAAAwAGwEAAAAAAAEPAAgCEAARAAAADAAbAQAAAAAAAQ8ACAIQABIAAAAMABsBAAAAAAAB
DwAIAhAAEwAAAAwAGwEAAAAAAAEPAAgCEAAUAAAADAAbAQAAAAAAAQ8ACAIQABUAAAAMABsB
AAAAAAABDwAIAhAAFgAAAAwAGgEAAAAAAAEPAAgCEAAXAAAADAAaAQAAAAAAAQ8ACAIQABgA
AAAMABoBAAAAAAABDwAIAhAAGQAAAAwAGwEAAAAAAAEPAAgCEAAaAAAADAAaAQAAAAAAAQ8A
CAIQABsAAAAMABoBAAAAAAABDwAIAhAAHgAAAAUAGgEAAAAAAAEPAAQCDAAAAAAADwAEAE1l
ZXQEAgwAAAABABUABABEYXRlBAIMAAAAAgAPAAQAQ3VycgQCEAAAAAMADwAIAE1pbi1tZWV0
BAIPAAAABAAPAAcARlggcmF0ZQQCCwAAAAUAFgADAFVTRAQCDgAAAAYADwAGAFVTIENQSQQC
FAAAAAcADwAMAENwaS1hZGp1c3RlZNYAGQAAAAgADwAOAGJhc2VkIGZyb20gMXN0AQwGBAIU
AAAACQAPAAwANm1lZXRpbmcgYXZlBAIUAAAACgAPAAwAQ3BpLWFkanVzdGVk1gAZAAAACwAP
AA4AYmFzZWQgZnJvbSAxc3QBDAZ+AgoAAQAAAA8A4gAAAAQCDwABAAEAFQAHADIwMDMtMDME
AgsAAQACAA8AAwBVU0S9ABIAAQADAA8ALgIAAA8ABgAAAAQABgAfAAEABQAWAAAAAAAAYGFA
AgAAAAAACQBEAcADRAHABAZ+AgoAAQAGABcAcx8BAAYAHwABAAcAGADegncL3i3oPwIAAAAA
AAkARAHABUQBwAYGBgAfAAEACAAYAAAAAAAAAPA/AgAAAAAACQBEAcAHRAEABwZ+AgoAAgAA
AA8A5gAAAAQCDwACAAEAFQAHADIwMDMtMDcEAgsAAgACAA8AAwBFVVK9ABIAAgADAA8AAgIA
AA8AXwEAAAQABgAfAAIABQAWALxAJsULZGJAAgAAAAAACQBEAsADRALABAZ+AgoAAgAGABcA
cx8BAAYAHwACAAcAGABYbQrHv5fpPwIAAAAAAAkARALABUQCwAYGBgAfAAIACAAYAMU5I4B3
7/A/AgAAAAAACQBEAsAHRAEABwZ+AgoAAwAAAA8A6gAAAAQCDwADAAEAFQAHADIwMDMtMTEE
AgsAAwACAA8AAwBVU0S9ABIAAwADAA8ABgIAAA8ABgAAAAQABgAfAAMABQAWAAAAAAAAIGBA
AgAAAAAACQBEA8ADRAPABAZ+AgoAAwAGABcAcx8BAAYAHwADAAcAGAAJZyOcjXDmPwIAAAAA
AAkARAPABUQDwAYGBgAfAAMACAAYAIycYcGlsu0/AgAAAAAACQBEA8AHRAEABwZ+AgoABAAA
AA8A7gAAAAQCDwAEAAEAFQAHADIwMDQtMDIEAgsABAACAA8AAwBVU0S9ABIABAADAA8AWgIA
AA8ABgAAAAQABgAfAAQABQAWAAAAAAAAwGJAAgAAAAAACQBEBMADRATABAZ+AgoABAAGABcA
KycBAAYAHwAEAAcAGADbUSR0B2npPwIAAAAAAAkARATABUQEwAYGBgAfAAQACAAYAA9rMAmN
0PA/AgAAAAAACQBEBMAHRAEABwZ+AgoABQAAAA8A8gAAAAQCDwAFAAEAFQAHADIwMDQtMDgE
AgsABQACAA8AAwBVU0S9ABIABQADAA8AfgIAAA8ABgAAAAQABgAfAAUABQAWAAAAAAAA4GNA
AgAAAAAACQBEBcADRAXABAZ+AgoABQAGABcAKycBAAYAHwAFAAcAGADOLW6zVO/qPwIAAAAA
AAkARAXABUQFwAYGBgAfAAUACAAYAJr2I/DS0vE/AgAAAAAACQBEBcAHRAEABwZ+AgoABgAA
AA8A9gAAAAQCDwAGAAEAFQAHADIwMDQtMTEEAgsABgACAA8AAwBVU0S9ABIABgADAA8AMgIA
AA8ABgAAAAQABgAfAAYABQAWAAAAAAAAgGFAAgAAAAAACQBEBsADRAbABAZ+AgoABgAGABcA
KycBAAYAHwAGAAcAGAAhCERKXLfnPwIAAAAAAAkARAbABUQGwAYGBgAfAAYACAAYAJODfGYp
Y+8/AgAAAAAACQBEBsAHRAEABwYGACUABgAJABgAdbXboKwAYkACAAAAAAAPACUBwAbABQUZ
EAAAHgYABgYAHwAGAAoAGABe/WnnvWXoPwIAAAAAAAkARAbACUQGwAYGBgAfAAYACwAYAAAA
AAAAAPA/AgAAAAAACQBEBsAKRAYACgZ+AgoABwAAAA8A+gAAAAQCDwAHAAEAFQAHADIwMDUt
MDMEAgsABwACAA8AAwBVU0S9ABIABwADAA8AHgIAAA8ABgAAAAQABgAfAAcABQAWAAAAAAAA
4GBAAgAAAAAACQBEB8ADRAfABAZ+AgoABwAGABcAKzEBAAYAHwAHAAcAGACxelg9rB7mPwIA
AAAAAAkARAfABUQHwAYGBgAfAAcACAAYABMxrlxIRu0/AgAAAAAACQBEB8AHRAEABwYGACUA
BwAJABgAH2CGS1frYUACAAAAAAAPACUCwAfABQUZEAAAHgYABgYAHwAHAAoAGACD7967Gn3n
PwIAAAAAAAkARAfACUQHwAYGBgAfAAcACwAYAEbwxqDezu4/AgAAAAAACQBEB8AKRAYACgZ+
AgoACAAAAA8A/gAAAAQCDwAIAAEAFQAHADIwMDUtMDcEAgsACAACAA8AAwBFVVK9ABIACAAD
AA8A9gEAAA8ATwEAAAQABgAfAAgABQAWAFcMlPBG02JAAgAAAAAACQBECMADRAjABAZ+AgoA
CAAGABcAKzEBAAYAHwAIAAcAGADsnl+PIK3oPwIAAAAAAAkARAjABUQIwAYGBgAfAAgACAAY
AHxkHBI2VPA/AgAAAAAACQBECMAHRAEABwYGACUACAAJABgAuawYKOH9YUACAAAAAAAPACUD
wAjABQUZEAAAHgYABgYAHwAIAAoAGABaJ7OgZ5XnPwIAAAAAAAkARAjACUQIwAYGBgAfAAgA
CwAYAOYpgQm+7u4/AgAAAAAACQBECMAKRAYACgZ+AgoACQAAAA8AAgEAAAQCDwAJAAEAFQAH
ADIwMDUtMTEEAgsACQACAA8AAwBDQUS9ABIACQADAA8AggIAAA8A2wEAAAQABgAfAAkABQAW
ACNoOKn78mBAAgAAAAAACQBECcADRAnABAZ+AgoACQAGABcAKzEBAAYAHwAJAAcAGAABNV1N
jjfmPwIAAAAAAAkARAnABUQJwAYGBgAfAAkACAAYAM8ei9c2Z+0/AgAAAAAACQBECcAHRAEA
BwYGACUACQAJABgAahOiGQshYkACAAAAAAAPACUEwAnABQUZEAAAHgYABgYAHwAJAAoAGAAx
7glpf8PnPwIAAAAAAAkARAnACUQJwAYGBgAfAAkACwAYAFiT6MoyK+8/AgAAAAAACQBECcAK
RAYACgZ+AgoACgAAAA8ABgEAAAQCDwAKAAEAFQAHADIwMDYtMDMEAgsACgACAA8AAwBVU0S9
ABIACgADAA8AkgIAAA8ABgAAAAQABgAfAAoABQAWAAAAAAAAgGRAAgAAAAAACQBECsADRArA
BAZ+AgoACgAGABcAAzsBAAYAHwAKAAcAGACCIAiCIAjqPwIAAAAAAAkARArABUQKwAYGBgAf
AAoACAAYAApDBonUOfE/AgAAAAAACQBECsAHRAEABwYGACUACgAJABgAFb5MxLVrYkACAAAA
AAAPACUFwArABQUZEAAAHgYABgYAHwAKAAoAGACtxHUFNGTnPwIAAAAAAAkARArACUQKwAYG
BgAfAAoACwAYACmP4Hc1ru4/AgAAAAAACQBECsAKRAYACgZ+AgoACwAAAA8ACgEAAAQCDwAL
AAEAFQAHADIwMDYtMDcEAgsACwACAA8AAwBDQUR+AgoACwADAA8AzgIAAAMCDgALAAQADwDs
UbgehevxPwYAHwALAAUAFgAkSZIkSfpjQAIAAAAAAAkARAvAA0QLwAQGfgIKAAsABgAXAAM7
AQAGAB8ACwAHABgAd8K5wFRe6T8CAAAAAAAJAEQLwAVEC8AGBgYAHwALAAgAGAB7zb/DeMnw
PwIAAAAAAAkARAvAB0QBAAcGBgAlAAsACQAYAJsfZUoXcGJAAgAAAAAADwAlBsALwAUFGRAA
AB4GAAYGAB8ACwAKABgAdDy1LcRp5z8CAAAAAAAJAEQLwAlEC8AGBgYAHwALAAsAGAAGb4pp
gbXuPwIAAAAAAAkARAvACkQGAAoGfgIKAAwAAAAPAA4BAAAEAg8ADAABABUABwAyMDA2LTEx
BAILAAwAAgAPAAMAVVNEvQASAAwAAwAPAM4CAAAPAAYAAAAEAAYAHwAMAAUAFgAAAAAAAGBm
QAIAAAAAAAkARAzAA0QMwAQGfgIKAAwABgAXAAM7AQAGAB8ADAAHABgAm6ZpmqZp7D8CAAAA
AAAJAEQMwAVEDMAGBgYAHwAMAAgAGADn260YK83yPwIAAAAAAAkARAzAB0QBAAcGBgAlAAwA
CQAYAJsfZUoXQGNAAgAAAAAADwAlB8AMwAUFGRAAAB4GAAYGAB8ADAAKABgA9ly9r+Rx6D8C
AAAAAAAJAEQMwAlEDMAGBgYAHwAMAAsAGACG44US+AfwPwIAAAAAAAkARAzACkQGAAoGfgIK
AA0AAAAPABIBAAAEAg8ADQABABUABwAyMDA3LTAzBAILAA0AAgAPAAMARVVSvQASAA0AAwAP
AEYCAAAPAC8BAAAEAAYAHwANAAUAFgCrqqqqqipoQAIAAAAAAAkARA3AA0QNwAQGAwIOAA0A
BgAXAG3n+6nx6mlABgAfAA0ABwAYAHY5EO2F1u0/AgAAAAAACQBEDcAFRA3ABgYGAB8ADQAI
ABgAcktUNZ2+8z8CAAAAAAAJAEQNwAdEAQAHBgYAJQANAAkAGAANPCy8M3dkQAIAAAAAAA8A
JQjADcAFBRkQAAAeBgAGBgAfAA0ACgAYAAyr7FW2ROk/AgAAAAAACQBEDcAJRA3ABgYGAB8A
DQALABgAj+1VvDmS8D8CAAAAAAAJAEQNwApEBgAKBn4CCgAOAAAADwAWAQAABAIPAA4AAQAV
AAcAMjAwNy0wNwQCCwAOAAIADwADAFVTRL0AEgAOAAMADwDiAgAADwAGAAAABAAGAB8ADgAF
ABYAAAAAAAAAZ0ACAAAAAAAJAEQOwANEDsAEBgMCDgAOAAYAFwBt5/up8eppQAYAHwAOAAcA
GADNtdhQxGXsPwIAAAAAAAkARA7ABUQOwAYGBgAfAA4ACAAYAFlpZSaZyvI/AgAAAAAACQBE
DsAHRAEABwYGACUADgAJABgAU48TlFIpZUACAAAAAAAPACUJwA7ABQUZEAAAHgYABgYAHwAO
AAoAGABAt1QXoiDqPwIAAAAAAAkARA7ACUQOwAYGBgAfAA4ACwAYAPonpX9zIvE/AgAAAAAA
CQBEDsAKRAYACgZ+AgoADwAAAA8AGgEAAAQCDwAPAAEAFQAHADIwMDctMTIEAgsADwACAA8A
AwBDQUS9ABIADwADAA8AggIAAA8AlwEAAAQABgAfAA8ABQAWAN+IApNOzWNAAgAAAAAACQBE
D8ADRA/ABAYDAg4ADwAGABcAbef7qfHqaUAGAB8ADwAHABgAl9f4afJy6D8CAAAAAAAJAEQP
wAVED8AGBgYAHwAPAAgAGAA5UcI3ti3wPwIAAAAAAAkARA/AB0QBAAcGBgAlAA8ACQAYAB3q
XxALo2VAAgAAAAAADwAlCsAPwAUFGRAAAB4GAAYGAB8ADwAKABgAcBqCKuu26j8CAAAAAAAJ
AEQPwAlED8AGBgYAHwAPAAsAGACtqi5nAoXxPwIAAAAAAAkARA/ACkQGAAoGfgIKABAAAAAP
AB4BAAAEAg8AEAABABUABwAyMDA4LTAzBAILABAAAgAPAAMAVVNEvQASABAAAwAPAPYCAAAP
AAYAAAAEAAYAHwAQAAUAFgAAAAAAAKBnQAIAAAAAAAkARBDAA0QQwAQGAwIOABAABgAXAARW
Di2y6WpABgAfABAABwAYANIUzXc0F+w/AgAAAAAACQBEEMAFRBDABgYGAB8AEAAIABgAWyvc
mpyW8j8CAAAAAAAJAEQQwAdEAQAHBgYAJQAQAAkAGABzP7VlYChmQAIAAAAAAA8AJQvAEMAF
BRkQAAAeBgAGBgAfABAACgAYAAvjI5aUWOo/AgAAAAAACQBEEMAJRBDABgYGAB8AEAALABgA
NY/fSSRH8T8CAAAAAAAJAEQQwApEBgAKBn4CCgARAAAADwAiAQAABAIPABEAAQAVAAcAMjAw
OC0wNwQCCwARAAIADwADAEVVUr0AEgARAAMADwAKAgAADwD/AAAABAAGAB8AEQAFABYAsyzL
sizLaUACAAAAAAAJAEQRwANEEcAEBgMCDgARAAYAFwAEVg4tsulqQAYAHwARAAcAGAB6XNTb
UavuPwIAAAAAAAkARBHABUQRwAYGBgAfABEACAAYAIOeD2JtS/Q/AgAAAAAACQBEEcAHRAEA
BwYGACUAEQAJABgAtbq+UoYgZ0ACAAAAAAAPACUMwBHABQUZEAAAHgYABgYAHwARAAoAGABT
DRRPon/rPwIAAAAAAAkARBHACUQRwAYGBgAfABEACwAYAHajZNGjCPI/AgAAAAAACQBEEcAK
RAYACgZ+AgoAEgAAAA8AJgEAAAQCDwASAAEAFQAHADIwMDgtMTEEAgsAEgACAA8AAwBVU0S9
ABIAEgADAA8AfgIAAA8ABgAAAAQABgAfABIABQAWAAAAAAAA4GNAAgAAAAAACQBEEsADRBLA
BAYDAg4AEgAGABcABFYOLbLpakAGAB8AEgAHABgAKnvpbL6h5z8CAAAAAAAJAEQSwAVEEsAG
BgYAHwASAAgAGADuB9iWjUbvPwIAAAAAAAkARBLAB0QBAAcGBgAlABIACQAYAAsQFKjbtWZA
AgAAAAAADwAlDcASwAUFGRAAAB4GAAYGAB8AEgAKABgAXsP6FM4A6z8CAAAAAAAJAEQSwAlE
EsAGBgYAHwASAAsAGAC1OQXvdrXxPwIAAAAAAAkARBLACkQGAAoGfgIKABMAAAAPACoBAAAE
Ag8AEwABABUABwAyMDA5LTAzBAILABMAAgAPAAMAVVNEvQASABMAAwAPAK4DAAAPAAYAAAAE
AAYAHwATAAUAFgAAAAAAAGBtQAIAAAAAAAkARBPAA0QTwAQGAwIOABMABgAXAHe+nxov0WpA
BgAfABMABwAYABIziW6vhvE/AgAAAAAACQBEE8AFRBPABgYGAB8AEwAIABgAF5GBDOsx9z8C
AAAAAAAJAEQTwAdEAQAHBgYAJQATAAkAGADtSKKLFJRnQAIAAAAAAA8AJQ7AE8AFBRkQAAAe
BgAGBgAfABMACgAYAO3iAFaoIuw/AgAAAAAACQBEE8AJRBPABgYGAB8AEwALABgAB0fpRo1z
8j8CAAAAAAAJAEQTwApEBgAKBn4CCgAUAAAADwAuAQAABAIPABQAAQAVAAcAMjAwOS0wNwQC
CwAUAAIADwADAFNFS70AEgAUAAMADwBeFwAADwAXDAAABAAGAB8AFAAFABYABf004N8saEAC
AAAAAAAJAEQUwANEFMAEBgMCDgAUAAYAFwB3vp8aL9FqQAYAHwAUAAcAGAAnmw1i+9jsPwIA
AAAAAAkARBTABUQUwAYGBgAfABQACAAYAPNUMtLWFvM/AgAAAAAACQBEFMAHRAEABwYGACUA
FAAJABgAxB2r2znGZ0ACAAAAAAAPACUPwBTABQUZEAAAHgYABgYAHwAUAAoAGAC+KaCufl7s
PwIAAAAAAAkARBTACUQUwAYGBgAfABQACwAYADK3FyfLmvI/AgAAAAAACQBEFMAKRAYACgZ+
AgoAFQAAAA8AMgEAAAQCDwAVAAEAFQAHADIwMDktMTEEAgsAFQACAA8AAwBKUFm9ABIAFQAD
AA8A8tIAAA8Ad4sAAAQABgAfABUABQAWAA1W6AxW6GJAAgAAAAAACQBEFcADRBXABAYDAg4A
FQAGABcAd76fGi/RakAGAB8AFQAHABgAslRSrNCP5j8CAAAAAAAJAEQVwAVEFcAGBgYAHwAV
AAgAGABIA3FvBdztPwIAAAAAAAkARBXAB0QBAAcGBgAlABUACQAYAEsV/G8QoGdAAgAAAAAA
DwAlEMAVwAUFGRAAAB4GAAYGAB8AFQAKABgAFh6+JvUw7D8CAAAAAAAJAEQVwAlEFcAGBgYA
HwAVAAsAGACh54wQ7nzyPwIAAAAAAAkARBXACkQGAAoGfgIKABYAAAAPADYBAAAEAg8AFgAB
ABUABwAyMDEwLTAzBAILABYAAgAPAAMAVVNEvQASABYAAwAPAAoDAAAPAAYAAAAEAAYAHwAW
AAUAFgAAAAAAAEBoQAIAAAAAAAkARBbAA0QWwAQGfgIKABYABgAPALtUAQAGAB8AFgAHABgA
Lop1Xh947D8CAAAAAAAJAEQWwAVEFsAGBgYAHwAWAAgAGABrNnijvtbyPwIAAAAAAAkARBbA
B0QBAAcGBgAlABYACQAYAPW/phq7umdAAgAAAAAADwAlEcAWwAUFGRAAAB4GAAYGAB8AFgAK
ABgAwCzUg6rb6z8CAAAAAAAJAEQWwAlEFsAGBgYAHwAWAAsAGABYbO/C/kTyPwIAAAAAAAkA
RBbACkQGAAoGfgIKABcAAAAPADoBAAAEAg8AFwABABUABwAyMDEwLTA3BAILABcAAgAPAAMA
RVVSvQASABcAAwAPAKICAAAPADsBAAAEAAYAHwAXAAUAFgDFTuzETuxqQAIAAAAAAAkARBfA
A0QXwAQGfgIKABcABgAPALtUAQAGAB8AFwAHABgAM4vW+n2b7z8CAAAAAAAJAEQXwAVEF8AG
BgYAHwAXAAgAGABEaAgQW+r0PwIAAAAAAAkARBfAB0QBAAcGBgAlABcACQAYAPiaAXPr6mdA
AgAAAAAADwAlEsAXwAUFGRAAAB4GAAYGAB8AFwAKABgAB+wAPz0U7D8CAAAAAAAJAEQXwAlE
F8AGBgYAHwAXAAsAGADpLZmiGGryPwIAAAAAAAkARBfACkQGAAoGfgIKABgAAAAPAD4BAAAE
Ag8AGAABABUABwAyMDEwLTExBAILABgAAgAPAAMAVVNEvQASABgAAwAPAAIDAAAPAAYAAAAE
AAYAHwAYAAUAFgAAAAAAAABoQAIAAAAAAAkARBjAA0QYwAQGfgIKABgABgAPALtUAQAGAB8A
GAAHABgAfOJ+vPws7D8CAAAAAAAJAEQYwAVEGMAGBgYAHwAYAAgAGAC2A/ORBqXyPwIAAAAA
AAkARBjAB0QBAAcGBgAlABgACQAYAPiaAXPrmmhAAgAAAAAADwAlE8AYwAUFGRAAAB4GAAYG
AB8AGAAKABgALzlnfNzi7D8CAAAAAAAJAEQYwAlEGMAGBgYAHwAYAAsAGABFlIuxmfHyPwIA
AAAAAAkARBjACkQGAAoGvQASABkAAAAPAEIBAAAZAOp6AgABAAQCCwAZAAIADwADAFVTRL0A
EgAZAAMADwAWAwAADwAGAAAABAAGAB8AGQAFABYAAAAAAACgaEACAAAAAAAJAEQZwANEGcAE
Bn4CCgAZAAYAFwBrXwEABgAfABkABwAYACYiNIa9B+w/AgAAAAAACQBEGcAFRBnABgYGAB8A
GQAIABgAj8zQ3WCM8j8CAAAAAAAJAEQZwAdEAQAHBgYAJQAZAAkAGABP8FbIQNBnQAIAAAAA
AA8AJRTAGcAFBRkQAAAeBgAGBgAfABkACgAYAFA7iu9DG+s/AgAAAAAACQBEGcAJRBnABgYG
AB8AGQALABgAmnnoRdHG8T8CAAAAAAAJAEQZwApEBgAKBr0AEgAaAAAADwBGAQAAGQBWfAIA
AQAEAgsAGgACAA8AAwBVU0S9ABIAGgADAA8AtgMAAA8ABgAAAAQABgAfABoABQAWAAAAAAAA
oG1AAgAAAAAACQBEGsADRBrABAZ+AgoAGgAGAA8AA2EBAAYAHwAaAAcAGABEgytE4sjwPwIA
AAAAAAkARBrABUQawAYGBgAfABoACAAYAFqFe4+5NvY/AgAAAAAACQBEGsAHRAEABwYGACUA
GgAJABgAI8b4Isa4aEACAAAAAAAPACUVwBrABQUZEAAAHgYABgYAHwAaAAoAGACdH8pOagPs
PwIAAAAAAAkARBrACUQawAYGBgAfABoACwAYAORxnB0QX/I/AgAAAAAACQBEGsAKRAYACga9
ABIAGwAAAA8ASgEAABkAQn4CAAEABAILABsAAgAPAAMAVVNEvQASABsAAwAPAL4DAAAPAAYA
AAAEAAYAHwAbAAUAFgAAAAAAAOBtQAIAAAAAAAkARBvAA0QbwAQGfgIKABsABgAPAANhAQAG
AB8AGwAHABgAYbpf/CTt8D8CAAAAAAAJAEQbwAVEG8AGBgYAHwAbAAgAGAB3UEPOtmb2PwIA
AAAAAAkARBvAB0QBAAcGBgAlABsACQAYAMu3fMu3jGpAAgAAAAAADwAlFsAbwAUFGRAAAB4G
AAYGAB8AGwAKABgAPzdz1KkV7j8CAAAAAAAJAEQbwAlEG8AGBgYAHwAbAAsAGAA/aT6kzbrz
PwIAAAAAAAkARBvACkQGAAoGBAI2AB4AAAAPAC4AaHR0cDovL3d3dy5vYW5kYS5jb20vY3Vy
cmVuY3kvaGlzdG9yaWNhbC1yYXRlcwQCHAAeAAQADwAUAHVzZWQgdG8gZ2V0IEZYIHJhdGVz
CAIQACAAAAAIABsBAAAAAAABDwAIAhAAKgAAAAYAGwEAAAAAAAEPAAgCEAArAAAADQAbAQAA
AAAAAQ8ACAIQACwAAAANABsBAAAAAAABDwAIAhAALQAAAA0AGwEAAAAAAAEPAAgCEAAuAAAA
DQAbAQAAAAAAAQ8ACAIQAC8AAAANABsBAAAAAAABDwAIAhAAMAAAAA0AGwEAAAAAAAEPAAQC
VgAgAAAADwBOAGh0dHA6Ly93d3cuaW5mbGF0aW9uZGF0YS5jb20vaW5mbGF0aW9uL0NvbnN1
bWVyX1ByaWNlX0luZGV4L0hpc3RvcmljYWxDUEkuYXNweAQCHwAgAAcADwAXAHVzZWQgZm9y
IFVTIENQSSBmaWd1cmVzfgIKACoAAAAPAGYfAAADAg4AKgABABcAd76fGi/RakABAgYAKgAF
AA8AfgIKACsAAAAaAGIfAAADAg4AKwABABcABFYOLbLpakC+ABwAKwACABoAGgAaABoAGgAa
ABoAGgAaABoAGgAMAH4CCgAsAAAAGgBeHwAAAwIOACwAAQAXAG3n+6nx6mlAvgAaACwAAwAa
ABoAGgAaABoAGgAaABoAGgAaAAwAvQASAC0AAAAaAFofAAAXAAM7AQABAL4AHAAtAAIAFwAa
ABoAGgAaABoAGgAaABoAGgAaAAwAvQASAC4AAAAaAFYfAAAXACsxAQABAL4AGgAuAAMAGgAa
ABoAGgAaABoAGgAaABoAGgAMAL0AEgAvAAAAGgBSHwAAFwArJwEAAQC+ABoALwADABoAGgAa
ABoAGgAaABoAGgAaABoADAC9ABIAMAAAABoATh8AABcAcx8BAAEAvgAaADAAAwAaABoAGgAa
ABoAGgAaABoAGgAaAAwAPgIKALYGAgAAAP///wAdAA8AAwQACwAAAAEABAAEAAsLCgAAAAkI
CAAABRAAbAnJBw0AAgABAAwAAgBkAA8AAgABABEAAgAAABAACAD8qfHSTWJQP18AAgABAIAA
CAAAAAAAAAAAACUCBAAAABoBjAAEAAEAAQCBAAIAwQQqAAIAAAArAAIAAACCAAIAAQAUACIA
ISZDJiJUaW1lcyBOZXcgUm9tYW4sUmVndWxhciImMTImQRUAJwAmJkMmIlRpbWVzIE5ldyBS
b21hbixSZWd1bGFyIiYxMlBhZ2UgJlCDAAIAAACEAAIAAAAmAAgAMzMzMzMz6T8nAAgAMzMz
MzMz6T8oAAgAgy3Ygi3Y8D8pAAgAgy3Ygi3Y8D+hACIACQBkAAAAAQABAAIALAEsATMzMzMz
M+k/MzMzMzMz6T8BAFUAAgALAH0ADAAAAAABlAsPAAAAAAAAAgoAAAAAAAAAAAAAAD4CCgC2
AAAAAAD///8AHQAPAAMAAAAAAAABAAAAAAAAAAoAAAAJCAgAAAUQAGwJyQcNAAIAAQAMAAIA
ZAAPAAIAAQARAAIAAAAQAAgA/Knx0k1iUD9fAAIAAQCAAAgAAAAAAAAAAAAlAgQAAAAaAYwA
BAABAAEAgQACAMEEKgACAAAAKwACAAAAggACAAEAFAAiACEmQyYiVGltZXMgTmV3IFJvbWFu
LFJlZ3VsYXIiJjEyJkEVACcAJiZDJiJUaW1lcyBOZXcgUm9tYW4sUmVndWxhciImMTJQYWdl
ICZQgwACAAAAhAACAAAAJgAIADMzMzMzM+k/JwAIADMzMzMzM+k/KAAIAIMt2IIt2PA/KQAI
AIMt2IIt2PA/oQAiAAkAZAAAAAEAAQACACwBLAEzMzMzMzPpPzMzMzMzM+k/AQBVAAIACwB9
AAwAAAAAAZQLDwAAAAAAAAIKAAAAAAAAAAAAAAA+AgoAtgAAAAAA////AB0ADwADAAAAAAAA
AQAAAAAAAAAKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP7///8CAAAAAwAAAAQAAAD+////BgAAAP7/
//8IAAAA/v//////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////
AQAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAP7/AAABAAIAAAAAAAAAAAAAAAAAAAAAAAEAAADghZ/y+U9oEKuRCAArJ7PZ
MAAAAJgAAAAHAAAAAQAAAEAAAAAIAAAASAAAAAkAAABcAAAACgAAAGgAAAALAAAAdAAAAAwA
AACAAAAADQAAAIwAAAACAAAA6f0AAB4AAAAJAAAAc3RlcGhlbiAAAAAAHgAAAAIAAAAyAAAA
QAAAAIDmbt0BAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAQAAAAADgCOCcYswBAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAP7/
AwoAAP////8QCAIAAAAAAMAAAAAAAABGHAAAAE1pY3Jvc29mdCBFeGNlbCA1LjAtVGFiZWxs
ZQAGAAAAQmlmZjUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAP7/AAABAAIAAAAAAAAAAAAAAAAAAAAAAAEAAAAC1c3VnC4bEJOX
CAArLPmuMAAAABgAAAABAAAAAQAAABAAAAACAAAA6f0AAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFIA
bwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAWAAUA//////////8BAAAAEAgCAAAAAADAAAAAAAAARgAAAAAAAAAAAAAAAAAA
AAAAAAAAGgAAAEACAAAAAAAAQgBvAG8AawAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAgACAAAAAwAAAP////8AAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAACiwAAAAAAAABAE8AbABlAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgACAP//
/////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUAAAA
AAAAAAUAUwB1AG0AbQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAoAAIABAAAAAUAAAD/////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAQAAAMgAAAAAAAAAAQBDAG8AbQBwAE8AYgBqAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABIAAgD///////////////8AAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFAAAASgAAAAAAAAAFAEQAbwBjAHUA
bQBlAG4AdABTAHUAbQBtAGEAcgB5AEkAbgBmAG8AcgBtAGEAdABpAG8AbgAAAAAAAAAAAAAA
OAACAP///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAcA
AABIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA////////////////AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAA/v///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD/////////////
//8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD+////AAAAAAAAAAA=
--------------060206020904090400070005--

--------------080209030508030408090607--

From narten@us.ibm.com  Wed Aug 24 15:01:04 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 781F221F8AF2 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.46
X-Spam-Level: 
X-Spam-Status: No, score=-106.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjItCVpfEKdV for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:01:03 -0700 (PDT)
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.144]) by ietfa.amsl.com (Postfix) with ESMTP id CF6E421F8AB9 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:01:02 -0700 (PDT)
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by e4.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7OLcqCq009280 for <ietf@ietf.org>; Wed, 24 Aug 2011 17:38:52 -0400
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7OM215n2633890 for <ietf@ietf.org>; Wed, 24 Aug 2011 18:02:03 -0400
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7OM7aXh019290 for <ietf@ietf.org>; Wed, 24 Aug 2011 16:07:36 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-218-237.mts.ibm.com [9.65.218.237]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7OM7Z8l019215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 16:07:35 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7OM1mjM011921; Wed, 24 Aug 2011 18:01:49 -0400
Message-Id: <201108242201.p7OM1mjM011921@cichlid.raleigh.ibm.com>
To: Eric Burger <eburger-l@standardstrack.com>
Subject: Re: voting system for future venues?
In-reply-to: <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com>
Comments: In-reply-to Eric Burger <eburger-l@standardstrack.com> message dated "Wed, 24 Aug 2011 17:48:49 -0400."
Date: Wed, 24 Aug 2011 18:01:48 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:01:04 -0000

> Let's ask again: what is it you WANT?

Eric, haven't I been clear enough? I want a pony!

(http://www.urbandictionary.com/define.php?term=I%20want%20a%20pony)

:-)

Thomas

From moore@network-heretics.com  Wed Aug 24 15:02:18 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A16F321F8D0A for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.459
X-Spam-Level: 
X-Spam-Status: No, score=-3.459 tagged_above=-999 required=5 tests=[AWL=0.139,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UaEWLsKUYkfu for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:02:18 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id EC90421F8D07 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:02:17 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 4EA4720842; Wed, 24 Aug 2011 18:03:29 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 24 Aug 2011 18:03:29 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=QQd jtgWcAPNPO6WQ2wxeI8PchBw=; b=Rdj4ruYYKFF4n+oQHA5sktcOPhi8cNKpmis Qskhln3BwqlkJEGS1m9l9sF5FMJAnoSjo6tTh0/r7dU2irfFhL1G6+H2iMFnPfDj WRuivGjIzf2MmLLOdab6MoRRzm+BWf5O3Ky5a27T/gSUelS9mj3HPTW1hfa0jfBG d0f49wM8=
X-Sasl-enc: GQLowyiz3T1vkZVnjQcPGfEzuIsp3lDwmnPIIjiicj0l 1314223408
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6011B901DE8; Wed, 24 Aug 2011 18:03:28 -0400 (EDT)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-14-908735907
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com>
Date: Wed, 24 Aug 2011 18:03:04 -0400
Message-Id: <F1B0F373-B4FB-42D0-B549-CC7F2635E9A3@network-heretics.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com>
To: Eric Burger <eburger-l@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:02:18 -0000

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

On Aug 24, 2011, at 5:48 PM, Eric Burger wrote:

> Let's ask again: what is it you WANT?

Personally, I want to be able to afford to travel to the meetings, and =
to be able to do so without having to commit to spending the money =
months in advance.

More broadly, I want IETF meetings to be accessible by a wide range of =
interests: academics, operators, small vendors, large vendors, even =
users.

Keith


--Apple-Mail-14-908735907
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><div>On Aug 24, 2011, at 5:48 PM, Eric Burger wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Let's ask =
again: what is it you =
WANT?</span></blockquote></div><br><div>Personally, I want to be able to =
afford to travel to the meetings, and to be able to do so without having =
to commit to spending the money months in =
advance.</div><div><br></div><div>More broadly, I want IETF meetings to =
be accessible by a wide range of interests: academics, operators, small =
vendors, large vendors, even =
users.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-14-908735907--

From ole@cisco.com  Wed Aug 24 15:06:50 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043F621F8B3D for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:06:50 -0700 (PDT)
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.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y2qcE17kdJsX for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:06:49 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 40DA821F8B38 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=548; q=dns/txt; s=iport; t=1314223681; x=1315433281; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=oKiyAfMVOKg3DcdI2XBTKMN9ZgjNhdsazhHzTxHyZ9o=; b=d7WITf6TWlOeedf+a5cizWXMK0kI9eQkFiqxacLSO7zMtDTF9Eiwsuw6 jMerPo/6Cg7lMM7Sry6lADR7UnQQFfXL7vilMNJWNjC6ia/Czot2BgFZx a9e+Drkn+BFhRdKyA0OdH3EWU+RqgSW5wCExyWIiNgub2cOS0GCJFLFoz 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAK11VU6rRDoH/2dsb2JhbAA/A6gBd4FAAQEBAQMSAQIBJD8QC0ZXBhMioxsBgyYPAZthg0GDCASHYZUwhyM
X-IronPort-AV: E=Sophos;i="4.68,277,1312156800"; d="scan'208";a="16222241"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-5.cisco.com with ESMTP; 24 Aug 2011 22:08:00 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7OM7xQR003812; Wed, 24 Aug 2011 22:07:59 GMT
Date: Wed, 24 Aug 2011 15:07:59 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: voting system for future venues?
In-Reply-To: <4E5574AA.3030705@cs.tcd.ie>
Message-ID: <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:06:50 -0000

"....doesn't look that good in terms of iaoc performance over time."

Are you seriously suggesting that we are looking for more and more 
expensive venues over time? Do you not think there might be some
factors such as inflation, currency fluctuations, general cost 
increases (oil prices perhaps) that dictate most of this?

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From chris.newman@oracle.com  Wed Aug 24 15:19:42 2011
Return-Path: <chris.newman@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C58B121F8B53; Wed, 24 Aug 2011 15:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.895
X-Spam-Level: 
X-Spam-Status: No, score=-105.895 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lCzQvZJ8xeT5; Wed, 24 Aug 2011 15:19:42 -0700 (PDT)
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by ietfa.amsl.com (Postfix) with ESMTP id 4600021F8742; Wed, 24 Aug 2011 15:19:42 -0700 (PDT)
Received: from brmsunmail2-sfbay.uk.sun.com ([10.79.11.101]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id p7OMKqST006277; Wed, 24 Aug 2011 22:20:52 GMT
Received: from gotmail.us.oracle.com (gotmail.us.oracle.com [10.133.152.174]) by brmsunmail2-sfbay.uk.sun.com (8.14.4+Sun/8.14.4/ENSMAIL,v2.4) with ESMTP id p7OMKqOq024913; Wed, 24 Aug 2011 22:20:52 GMT
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [10.145.239.205] (nifty-silver.us.oracle.com [10.145.239.205]) by gotmail.us.oracle.com (Oracle Communications Messaging Exchange Server 7u5-4.01 64bit (built May 4 2011)) with ESMTPA id <0LQG0003LE2PTS00@gotmail.us.oracle.com>; Wed, 24 Aug 2011 15:20:51 -0700 (PDT)
Date: Wed, 24 Aug 2011 15:20:49 -0700
From: Chris Newman <chris.newman@oracle.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-yam-rfc4409bis-02.txt> (Message Submission for Mail) to Full Standard
Message-id: <966F4E24F51C2C7597C6872C@96B2F16665FF96BAE59E9B90>
In-reply-to: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
References: <20110811133752.23199.23779.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Cc: yam@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:19:42 -0000

--On August 11, 2011 6:37:52 -0700 The IESG <iesg-secretary@ietf.org> wrote:
> The IESG has received a request from the Yet Another Mail WG (yam) to
> consider the following document:
> - 'Message Submission for Mail'
>   <draft-ietf-yam-rfc4409bis-02.txt> as a Full Standard

I have read this draft and support advancing it to Full Standard as written 
or with modifications suggested by others.

My comment on issues raised:

Russ Housley's discuss:

The document is more helpful to implementers if it has an informational 
downward reference to deployed signing technologies such as DKIM and 
multipart/signed (RFC 2480, RFC 1847) so that implementers know to consider 
the impact of message modification on those technologies. Normative 
language on that topic is best avoided so the document would be improved by 
removing the "SHOULD" related to those technologies.

I believe the alternative text that was proposed is fine, but I would also 
be fine with the current text and also with dropping the offending 
paragraph if necessary to advance the specification.

Informative reference to RFC 6186:

As much as I like 6186 and hope it deploys, there is not sufficient 
deployment today to justify a reference from a full standard.

Informative reference to RFC 5068 / BCP 134:

I think an informative reference would be helpful to readers, but if adding 
that reference would cause an approval delay then expedience is more 
important.

SMTP AUTH / STARTTLS:

I have seen SMTP AUTH and STARTTLS work well operationally between multiple 
independent implementations of submission. Problems with those technologies 
related to MTA relay are unrelated to this submission draft and thus need 
no additional text in this draft.

		- Chris


From stephen.farrell@cs.tcd.ie  Wed Aug 24 15:23:57 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4415E21F8C22 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.932
X-Spam-Level: 
X-Spam-Status: No, score=-105.932 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PgFlj7XmdO6S for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:23:56 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7D0CE21F8C1E for <ietf@ietf.org>; Wed, 24 Aug 2011 15:23:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 9A6E2171C5B; Wed, 24 Aug 2011 23:25:02 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1314224702; bh=YpZWrUtiKUk/50 mOhRW4tJvCOhJ35ORZzMMt5T6V90Q=; b=0yBbKjL7bwA0fY5QXaQ5rNossf07po XBnsqk9JCvO5KdRi6CwoO8qQsOaTFQUcQ0ojxfr2c+1nsFpdluLbC7kuYIDiZL1P p2fUkV3Pss1KJ0hxirrxyLUgl3peJ/4arxPVFZhwAAu+HkhHIHpoXNIbOFLGOppn tLV2U9eYz06MGPNr+rn4AZ40J9+Kabd5RrfGoSTdzwznXaL34db7rMYSWrPUMgiL j38z/LyTuP71KtcPnySKAPlB3PTNInCR2rJE5PyoKQdl6dohqqNK7jFU0FYg4tpX Vqrzw3OWuFpND5RpqPtHD18iPovd1GrFEd1tia6Qy8ijMacTD/CVtHsA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id Det87B5vWv-0; Wed, 24 Aug 2011 23:25:02 +0100 (IST)
Received: from [10.87.48.7] (unknown [86.46.30.197]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 17572171C1B; Wed, 24 Aug 2011 23:25:01 +0100 (IST)
Message-ID: <4E557A33.7050607@cs.tcd.ie>
Date: Wed, 24 Aug 2011 23:24:51 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:23:57 -0000

On 08/24/2011 11:07 PM, Ole Jacobsen wrote:
>
> "....doesn't look that good in terms of iaoc performance over time."
>
> Are you seriously suggesting that we are looking for more and more
> expensive venues over time?

No. And obviously not. I don't see how it helps to suggest
that either.

 > Do you not think there might be some
> factors such as inflation, currency fluctuations, general cost
> increases (oil prices perhaps) that dictate most of this?

Inflation is accounted for in the figures given. We're
still >20% above inflation in terms of hotel prices based
on these figures.

You might claim hotel price inflation is higher than the
overall, I don't know. I would hope the iaoc would know
that. What I'm claiming is that the numbers seem to me
to show that the outcome is not so good. And hence it seems
to me that the iaoc is not performing that well in this respect.

You might bring out the meeting fee argument etc. but I
think you (the iaoc as a group) should start by acknowledging
that there is a real issue here and then try to address
that and *not* argue I'm accusing you of bad faith or
something.

S.


>
> Ole
>
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>
>
>

From warren@kumari.net  Wed Aug 24 15:43:05 2011
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5047221F8CCA for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wx7k624tayb6 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:43:04 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 6823221F8CC6 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:43:04 -0700 (PDT)
Received: from dot.her.corp.google.com (unknown [74.202.225.33]) by vimes.kumari.net (Postfix) with ESMTPSA id 74B341B4153B for <ietf@ietf.org>; Wed, 24 Aug 2011 18:44:15 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [IETF] Re: Hyatt Taipei cancellation policy?
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <201108242128.p7OLSq4i011660@cichlid.raleigh.ibm.com>
Date: Wed, 24 Aug 2011 18:44:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <73B65805-9EFA-4D45-A6F3-A71FEE5E4880@kumari.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net> <1314217708.1973.199.camel@d430> <201108242128.p7OLSq4i011660@cichlid.raleigh.ibm.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:43:05 -0000

On Aug 24, 2011, at 5:28 PM, Thomas Narten wrote:

> Geoff Mulligan <geoff.ietf@mulligan.com> writes:
>=20
>> Maybe the majority doesn't care one way or the other - they will just =
go
>> wherever the meetings are held in which case:
>>  let's make them easy to get to
>>  cheap
>>  decent food
>>  one roof (with other hotels near-by)
>>  cheap
>>  and easy to get to
>=20
> Having watched this debate play out in multiple venues (ICANN goes all
> around the world 3x a year as well) over multiple years, I've come to
> the following main conclusion:
>=20
> 1) you can't please all the people all the time, and there will be
> griping no matter what we do. We've got 1200 attendees. That's a lot
> of folk who have differing ideas of what is important.=20

+lots

And the folk who are happy with the status quo / apathetic / just glad =
that they don't have to choose locations are likely to be silent, so the =
tone of the conversation is very negative.

I probably fall into the apathetic / glad it's not me category -- I care =
about:
1: Being able to meet and get work done.
2: Having a hotel really close / attached to the venue (so I can drop my =
bag off between sessions and dinner).
3: Having sort of food somewhere nearby.

I view the meeting as work time, not vacation time -- if we meet in a =
resort in the Alps or a hotel in New Jersey, it's all the same to me =
(and, I suspect, to many) and so I haven't been very vocal on this =
thread...



>=20
> 2) There is no perfect solution. There are too many variables, not all
> of which are known in advance. And, everyone weighs various factors
> differently. Convenience of travel, for instance, is very different
> for US-based folk vs. Chinese and Australians.
>=20
> 3) The absolutely most important thing to get right is a meeting venue
> that works for getting work done. In my mind, the really key things
> here are:
>=20
>  a) everyone can (easily) walk to the meeting site (this facilitates
>     mingling, including at the bar)
>=20
>  b) there is ample local food within walking distance (again for
>     mingling/meetings)
>=20
>  c) proper facilities (adequate meeting room, wireless, range of room
>     rate options, and yes, I suppose cookies, etc.)
>=20
> If you get the above right, the other inconveniences don't matter
> (except maybe visa hassles). Or more precisely, folk can (and just
> should) deal with it.

100% agree.

>=20
> Seriously, taking one extra plane hop (or gasp! riding a train!) is
> just noise, when talking about a meeting that lasts 5+ solid days.
> I'd much rather take an extra hop to get to a meeting venue that works
> well, then save a few hours travel time to reach a venue that doesn't
> have places to eat.
>=20
> Etc.
>=20
> Hub cities are no panacea. I too like Minneapolis. As a venue, it
> meets the key IETF needs as better than most places we've visited. It
> has good airline connectivity (not perfect, but good). It meets the
> key criteria above. You can also walk everywhere underground in the
> winter, so the argument that it's "too cold" seems specious. Etc.
>=20
> But does everyone like Minneapolis? Apparently not. I'm told that the
> IAOC has stopped going there because they were getting too many
> complaints. People do get tired of going to the same places, even if a
> location works.
>=20
> I've concluded that going to new places is better than hubs. Even
> though I rarely take vacation in conjunction with meetings, getting
> 1/2 a day to sight see or even being able to walk into town for dinner
> in a new location is a positive thing over being at the same places
> too often.

And I've concluded that the IAOC have a crappy job to do and that folk =
like to kvetch.

If they found a private Caribbean island with free flights and a 5 star =
resort for $10USD per night, *someone* would complain that the sand was =
too hot and the falling coconuts were a hazard...

W

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


From joelja@bogus.com  Wed Aug 24 15:44:00 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D16821F8CDC for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.22
X-Spam-Level: 
X-Spam-Status: No, score=-102.22 tagged_above=-999 required=5 tests=[AWL=0.379, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Kzj8leNh004 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 15:44:00 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACBA21F8CC6 for <ietf@ietf.org>; Wed, 24 Aug 2011 15:44:00 -0700 (PDT)
Received: from [10.101.144.54] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7OMherm093570 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Aug 2011 22:43:40 GMT (envelope-from joelja@bogus.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E557A33.7050607@cs.tcd.ie>
Date: Wed, 24 Aug 2011 15:43:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 24 Aug 2011 22:43:41 +0000 (UTC)
Cc: Ole Jacobsen <ole@cisco.com>, IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 22:44:00 -0000

On Aug 24, 2011, at 3:24 PM, Stephen Farrell wrote:
> Inflation is accounted for in the figures given. We're
> still >20% above inflation in terms of hotel prices based
> on these figures.
>=20
> You might claim hotel price inflation is higher than the
> overall, I don't know. I would hope the iaoc would know
> that. What I'm claiming is that the numbers seem to me
> to show that the outcome is not so good. And hence it seems
> to me that the iaoc is not performing that well in this respect.
>=20
> You might bring out the meeting fee argument etc. but I
> think you (the iaoc as a group) should start by acknowledging
> that there is a real issue here and then try to address
> that and *not* argue I'm accusing you of bad faith or
> something.

Does not control for currency fluctuation unless I missed something in =
the table.

not that externalities such as the ECB members flushing the euro down =
the toilet don't impact costs but the notion that we can anticipate or =
ameliorate such risks on a 2-5 year time scale is unlikely.=

From geoff.ietf@mulligan.com  Wed Aug 24 16:08:56 2011
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E384A21F8CA2 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmk58G5I4FUX for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:08:56 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id 4796621F8CA4 for <ietf@ietf.org>; Wed, 24 Aug 2011 16:08:56 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id F29D5184E2; Wed, 24 Aug 2011 17:04:06 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id 77A0B15F504; Wed, 24 Aug 2011 17:03:56 -0600 (MDT)
Subject: Re: Hyatt Taipei cancellation policy?
From: Geoff Mulligan <geoff.ietf@mulligan.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <tslmxey8sia.fsf@mit.edu>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net>  <tslmxey8sia.fsf@mit.edu>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 17:04:01 -0600
Message-ID: <1314227041.1973.213.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
Cc: dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 23:08:57 -0000

On Wed, 2011-08-24 at 16:27 -0400, Sam Hartman wrote:
> >>>>> "Dave" == Dave CROCKER <dhc@dcrocker.net> writes:
> 
>     Dave> ps.  As a personal aside, I'll note that I've lobbied rather
>     Dave> vigorously for venues that entail less travel effort, by
>     Dave> eliminating the additional hop needed to get from a major hub.
>     Dave> Note that that has gotten essentially zero support from the
>     Dave> community.  The community has vigrously expressed a preference
>     Dave> for "interesting" venues rather than ones that are chosen
>     Dave> solely for logistics convenience.
> 
> Can you start by backing up the assertion  that the community has
> vigrously expressed a preference for interesting venues?
> I may just need a new IETF community:-)

I agree.  I think that there is a vocal minority that wants this.  I
don't think that community as a whole really cares.

We had this huge debate about the number of times (down to fractions of
times) to visit each area of the world so as to increase participation
and we then have locations that make it difficult to get to or expensive
or both and expensive to get to which limits participation.

I like Santa Clara, CA

	geoff

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




From geoff.ietf@mulligan.com  Wed Aug 24 16:14:19 2011
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A699521F8C12 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mph+LTRSe5LD for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:14:19 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id 2D74A21F8C07 for <ietf@ietf.org>; Wed, 24 Aug 2011 16:14:19 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id 999D3184E0; Wed, 24 Aug 2011 17:15:35 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id F0E3615F504; Wed, 24 Aug 2011 17:15:24 -0600 (MDT)
Subject: Re: [IETF] Re: Hyatt Taipei cancellation policy?
From: Geoff Mulligan <geoff.ietf@mulligan.com>
To: Warren Kumari <warren@kumari.net>
In-Reply-To: <73B65805-9EFA-4D45-A6F3-A71FEE5E4880@kumari.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net> <1314217708.1973.199.camel@d430> <201108242128.p7OLSq4i011660@cichlid.raleigh.ibm.com> <73B65805-9EFA-4D45-A6F3-A71FEE5E4880@kumari.net>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 17:15:30 -0600
Message-ID: <1314227730.1973.216.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 23:14:19 -0000

On Wed, 2011-08-24 at 18:44 -0400, Warren Kumari wrote:

> And I've concluded that the IAOC have a crappy job to do and that folk like to kvetch.
> 
> If they found a private Caribbean island with free flights and a 5 star resort for $10USD per night, *someone* would complain that the sand was too hot and the falling coconuts were a hazard...
> 

While that may be true, those complaints are much different than, "I
can't afford to travel to the meeting site" or "I can't afford the
hotel".

	geoff



From ole@cisco.com  Wed Aug 24 16:31:00 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB6021F8CA0 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:31:00 -0700 (PDT)
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.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9HxwCgBMoYF8 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:30:58 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 9F71921F8C75 for <ietf@ietf.org>; Wed, 24 Aug 2011 16:30:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=3282; q=dns/txt; s=iport; t=1314228730; x=1315438330; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=mrHj/1yqRKH8lg3pGFwmFHgaTClV5rZYeJDU7fEQaM0=; b=KoOjoMPu0J4rXb/sf2mMcf/WQlBfoOTp2I0wI7fGH5GqVnaMlcSzlrss d7avb85NSTQTVetTl7Qk4tPqVfP7SpcI9mTjusDJwMaNVlzZ3lRbfxee6 8XL8iUqZW/R75Sws/EiYCp1WzRmfe0RSxquzQ4pEyn2EC8vLpytFpFtZz U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAKiJVU6rRDoI/2dsb2JhbAA/A6gBd4FAAQEBAQIBEgECASQuAg8QCxguVwYTIodPmwMBgyYPAZtXg0GDCASHYZUwhyM
X-IronPort-AV: E=Sophos;i="4.68,278,1312156800"; d="scan'208";a="16240999"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-5.cisco.com with ESMTP; 24 Aug 2011 23:32:08 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7ONW7WG007284; Wed, 24 Aug 2011 23:32:07 GMT
Date: Wed, 24 Aug 2011 16:32:07 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: voting system for future venues?
In-Reply-To: <4E557A33.7050607@cs.tcd.ie>
Message-ID: <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 23:31:00 -0000

Sorry, I wasn't trying to suggest a bad faith situation, just reacting 
to your WORDING :-)

I agree that hotel prices have risen and that isn't limited to the 
venues under consideration by the IETF. NANOG and APRICOT hotel rates 
have gone up as have other meeting hotel rates, and certainly the 
hotels I stay in as an individual have gone up a LOT in, say, the last 
ten years, and that's not even accounting for the currency changes. I 
have a couple of "favorite" hotels that have have gone from "under 
100" (for values of Euros, Pounds, Dollars, other kinds of dollars) to 
"well above 200" in that timeframe.

I think the only way to get HQ hotel rates down is to go to the sort
of places that the IETF seems to not want to go. One of the cheapest
places to fly to in the world is Las Vegas. You can also get really
good hotel rates there, group or individual. Since I went to Las Vegas
every year for 10+ years and basically did nothing but attend a 
conference and tradeshow *I* have no problem going back and would 
certainly consider it an option, but I certainly don't love it and
wouldn't care if I ever set foot there again, and I know for a fact
that many on this list feel the same way.

The University Campus, or maybe "University Conference Center" idea
is worth exploring, such places do exist (in Atlanta for example),
but, as others have pointed out, we need to clearly define what the
goal is here and recognize that there are some incompatible 
requirements.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 24 Aug 2011, Stephen Farrell wrote:

> 
> 
> On 08/24/2011 11:07 PM, Ole Jacobsen wrote:
> >
> > "....doesn't look that good in terms of iaoc performance over time."
> >
> > Are you seriously suggesting that we are looking for more and more
> > expensive venues over time?
> 
> No. And obviously not. I don't see how it helps to suggest
> that either.
> 
> > Do you not think there might be some
> > factors such as inflation, currency fluctuations, general cost
> > increases (oil prices perhaps) that dictate most of this?
> 
> Inflation is accounted for in the figures given. We're
> still >20% above inflation in terms of hotel prices based
> on these figures.
> 
> You might claim hotel price inflation is higher than the
> overall, I don't know. I would hope the iaoc would know
> that. What I'm claiming is that the numbers seem to me
> to show that the outcome is not so good. And hence it seems
> to me that the iaoc is not performing that well in this respect.
> 
> You might bring out the meeting fee argument etc. but I
> think you (the iaoc as a group) should start by acknowledging
> that there is a real issue here and then try to address
> that and *not* argue I'm accusing you of bad faith or
> something.
> 
> S.
> 
> 
> >
> > Ole
> >
> > Ole J. Jacobsen
> > Editor and Publisher,  The Internet Protocol Journal
> > Cisco Systems
> > Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> > E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> > Skype: organdemo
> >
> >
> >
> 

From hgs@cs.columbia.edu  Wed Aug 24 17:00:32 2011
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D65F721F8C59 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SH5geWUSEnq7 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:00:31 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id C6FBE21F8C58 for <ietf@ietf.org>; Wed, 24 Aug 2011 17:00:31 -0700 (PDT)
Received: from new-host.home (pool-173-54-225-113.nwrknj.fios.verizon.net [173.54.225.113]) (user=hgs10 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p7P01bjV000641 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Aug 2011 20:01:38 -0400 (EDT)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=windows-1252
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com>
Date: Wed, 24 Aug 2011 20:01:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A11059FD-C516-40BB-BD9E-9BBE4ED03705@cs.columbia.edu>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1244.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 00:00:32 -0000

Having organized (or tried to=85) conferences at a US university, some =
caveats:

- You can get cheap housing, but only in the summer and some places. (I =
recently stayed at the U. of Toronto for $38/night, albeit having =
showers down the hall may not be everybody's cup of tea. Rates in =
Columbia summer housing are no better than NY hotel rates and you'd have =
to book years in advance to get a large enough room block, given all the =
summer events at major universities.)

- Most university class room are designed for smaller classes than the =
typical IETF room size (with 5 or 6 parallel sessions, you'd want 200 or =
so seats in each, I'm guessing), so you might have all the larger venues =
(100+ seats) spread around campus, maybe one per building. Makes it =
difficult to have a single cookie area.

- Some universities will charge pretty hefty sums to use their student =
center facilities, which is probably the only facility large enough for =
a plenary. Generally, they'll charge market rates for rooms unless you =
can get local faculty to sponsor the event.

- With a few exceptions (GaTech is probably one and maybe Toronto, if =
you define city center generously), large universities are not in the =
city center and not close to large number of business-level hotel rooms, =
for the obvious reasons that students aren't their typical customers and =
you can't survive on parents weekend and graduation alone. You will =
typically find more motels and such, but geared towards driving to =
campus, not walking.

Universities outside North America may be more suitable, but again only =
during semester breaks in most cases. Even Internet2, which presumably =
could easily get campus event sponsorships through their CIO members and =
has mostly university attendees, typically doesn't have its member =
meeting at universities.

Henning

On Aug 24, 2011, at 7:32 PM, Ole Jacobsen wrote:

>=20
> Sorry, I wasn't trying to suggest a bad faith situation, just reacting=20=

> to your WORDING :-)
>=20
> I agree that hotel prices have risen and that isn't limited to the=20
> venues under consideration by the IETF. NANOG and APRICOT hotel rates=20=

> have gone up as have other meeting hotel rates, and certainly the=20
> hotels I stay in as an individual have gone up a LOT in, say, the last=20=

> ten years, and that's not even accounting for the currency changes. I=20=

> have a couple of "favorite" hotels that have have gone from "under=20
> 100" (for values of Euros, Pounds, Dollars, other kinds of dollars) to=20=

> "well above 200" in that timeframe.
>=20
> I think the only way to get HQ hotel rates down is to go to the sort
> of places that the IETF seems to not want to go. One of the cheapest
> places to fly to in the world is Las Vegas. You can also get really
> good hotel rates there, group or individual. Since I went to Las Vegas
> every year for 10+ years and basically did nothing but attend a=20
> conference and tradeshow *I* have no problem going back and would=20
> certainly consider it an option, but I certainly don't love it and
> wouldn't care if I ever set foot there again, and I know for a fact
> that many on this list feel the same way.
>=20
> The University Campus, or maybe "University Conference Center" idea
> is worth exploring, such places do exist (in Atlanta for example),
> but, as others have pointed out, we need to clearly define what the
> goal is here and recognize that there are some incompatible=20
> requirements.
>=20
> Ole
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20
> On Wed, 24 Aug 2011, Stephen Farrell wrote:
>=20
>>=20
>>=20
>> On 08/24/2011 11:07 PM, Ole Jacobsen wrote:
>>>=20
>>> "....doesn't look that good in terms of iaoc performance over time."
>>>=20
>>> Are you seriously suggesting that we are looking for more and more
>>> expensive venues over time?
>>=20
>> No. And obviously not. I don't see how it helps to suggest
>> that either.
>>=20
>>> Do you not think there might be some
>>> factors such as inflation, currency fluctuations, general cost
>>> increases (oil prices perhaps) that dictate most of this?
>>=20
>> Inflation is accounted for in the figures given. We're
>> still >20% above inflation in terms of hotel prices based
>> on these figures.
>>=20
>> You might claim hotel price inflation is higher than the
>> overall, I don't know. I would hope the iaoc would know
>> that. What I'm claiming is that the numbers seem to me
>> to show that the outcome is not so good. And hence it seems
>> to me that the iaoc is not performing that well in this respect.
>>=20
>> You might bring out the meeting fee argument etc. but I
>> think you (the iaoc as a group) should start by acknowledging
>> that there is a real issue here and then try to address
>> that and *not* argue I'm accusing you of bad faith or
>> something.
>>=20
>> S.
>>=20
>>=20
>>>=20
>>> Ole
>>>=20
>>> Ole J. Jacobsen
>>> Editor and Publisher,  The Internet Protocol Journal
>>> Cisco Systems
>>> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>>> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>>> Skype: organdemo
>>>=20
>>>=20
>>>=20
>>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From stephen.farrell@cs.tcd.ie  Wed Aug 24 17:34:58 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA4121F8B5C for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_AFFORDABLE=1, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikjTzIfk09Hw for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:34:57 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5699821F8B54 for <ietf@ietf.org>; Wed, 24 Aug 2011 17:34:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 15E89171C5B; Thu, 25 Aug 2011 01:36:02 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1314232561; bh=FbfK9wkBgoyEvM /CWkQRxb7qN5W0wMY9eLLU3wR5QHI=; b=kmAkToEA/h/SHWP3sjPU0/X0tklaRc YHuAgVcbRm7uV4vTOMq9z5ICKc3j1mvII2ufec5xgaUSAS+K6udbNzM+CE1o1+xX 1svEuLrF58N6EE3x391RkZYy7pwSvS74VLZYu2aIQkfCm/jDIUSPjzfg/vfPyIzm fNcw+sczrLqSOCR7t+a2tTNzSDJdqlO5HYDqhSHOUD0RbvHDcUy0s6YSY/+iHeDl wMtdYr/Ayevi+Dphdh2D+wfvDWonX20nCMWSZR9T2nKECNLlSJGBX6oquYfI1mYQ v8OdE1SkyW5tZZyaH7RLg1SPQ4sta2Ob18NLJhPzdGpT4Ri1+RLR26Lg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id RPpmmd-+fbUS; Thu, 25 Aug 2011 01:36:01 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.44.74.255]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 2FE87171C1B; Thu, 25 Aug 2011 01:36:00 +0100 (IST)
Message-ID: <4E5598D0.6030703@cs.tcd.ie>
Date: Thu, 25 Aug 2011 01:35:28 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 00:34:58 -0000

On 08/25/2011 12:32 AM, Ole Jacobsen wrote:
>
> Sorry, I wasn't trying to suggest a bad faith situation, just reacting
> to your WORDING :-)

Hmmm. You accused me of suggesting bad faith so the above is correct I
guess.

> I agree that hotel prices have risen

I didn't say that. I said that IETF meeting hotel prices have
risen more than 20% above inflation. I have no idea if average
hotel prices for setups like ours have done that, or if the
IETF attendees are really getting a bad deal. I think the
latter though to be honest. Have you evidence that I'm right
or wrong?

 > and that isn't limited to the
> venues under consideration by the IETF. NANOG and APRICOT hotel rates
> have gone up as have other meeting hotel rates,

Do you/the iaoc have solid information on that or just anecdotes?
Do the iaoc communicate with other conference organisers to get such
information?
Have those other rates gone up more or less than IETF HQ rates?

 > and certainly the
> hotels I stay in as an individual have gone up a LOT in, say, the last
> ten years, and that's not even accounting for the currency changes. I
> have a couple of "favorite" hotels that have have gone from "under
> 100" (for values of Euros, Pounds, Dollars, other kinds of dollars) to
> "well above 200" in that timeframe.

Fine. But not very relevant. Hotel prices in, for example,
Ireland, have fallen thanks to our local financial incompetence.
I don't know the trends in hotel prices where we meet, but would
hope that the iaoc does. Do you?

> I think the only way to get HQ hotel rates down

Have the iaoc actually tried to achieve this specific goal?
Personally, I don't believe you've been doing that, but I
could be wrong.

 > is to go to the sort
> of places that the IETF seems to not want to go. One of the cheapest
> places to fly to in the world is Las Vegas. You can also get really
> good hotel rates there, group or individual. Since I went to Las Vegas
> every year for 10+ years and basically did nothing but attend a
> conference and tradeshow *I* have no problem going back and would
> certainly consider it an option, but I certainly don't love it and
> wouldn't care if I ever set foot there again, and I know for a fact
> that many on this list feel the same way.

Go for it and we'll see. Maybe it'll be crap (but to be honest
how much can it differ from Disney;-) but its worth trying so
long as the meeting facilities work for the meeting.

> The University Campus, or maybe "University Conference Center" idea
> is worth exploring, such places do exist (in Atlanta for example),
> but, as others have pointed out, we need to clearly define what the
> goal is here and recognize that there are some incompatible
> requirements.

I think this is *very* much worth doing. (Full disclosure: I tried
to get IETF-72 in Trinity College Dublin but that fell over thanks
in part to our local fascist sysadmins who hopefully don't read this
list;-)

Bottom line - the HQ hotel is a big cost for those who stay there
and getting to the unaffordable state for various folks for various
reasons. *Please* make it a specific goal to reduce that. Or
produce some model of overall costs that you aim to reduce if you
prefer. Anything so long as its measurable and starts going down.

S.

PS: Just in case. Yes we can stay at alternative hotels. But
nonetheless, aiming to reduce the HQ hotel rate is still a
good thing.


>
> Ole
>
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>
>
> On Wed, 24 Aug 2011, Stephen Farrell wrote:
>
>>
>>
>> On 08/24/2011 11:07 PM, Ole Jacobsen wrote:
>>>
>>> "....doesn't look that good in terms of iaoc performance over time."
>>>
>>> Are you seriously suggesting that we are looking for more and more
>>> expensive venues over time?
>>
>> No. And obviously not. I don't see how it helps to suggest
>> that either.
>>
>>> Do you not think there might be some
>>> factors such as inflation, currency fluctuations, general cost
>>> increases (oil prices perhaps) that dictate most of this?
>>
>> Inflation is accounted for in the figures given. We're
>> still>20% above inflation in terms of hotel prices based
>> on these figures.
>>
>> You might claim hotel price inflation is higher than the
>> overall, I don't know. I would hope the iaoc would know
>> that. What I'm claiming is that the numbers seem to me
>> to show that the outcome is not so good. And hence it seems
>> to me that the iaoc is not performing that well in this respect.
>>
>> You might bring out the meeting fee argument etc. but I
>> think you (the iaoc as a group) should start by acknowledging
>> that there is a real issue here and then try to address
>> that and *not* argue I'm accusing you of bad faith or
>> something.
>>
>> S.
>>
>>
>>>
>>> Ole
>>>
>>> Ole J. Jacobsen
>>> Editor and Publisher,  The Internet Protocol Journal
>>> Cisco Systems
>>> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>>> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>>> Skype: organdemo
>>>
>>>
>>>
>>
>

From stephen.farrell@cs.tcd.ie  Wed Aug 24 17:40:09 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85E7B21F8BB8 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.099
X-Spam-Level: 
X-Spam-Status: No, score=-106.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kbvd-XfXf4L for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:40:08 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9312A21F8B9F for <ietf@ietf.org>; Wed, 24 Aug 2011 17:40:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 028E0171C5B; Thu, 25 Aug 2011 01:41:08 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1314232867; bh=diO2BFRBaAB29V di6yV9SZy/N5RvUd971OK/rewjcx4=; b=s30HeWWS/oK38DH18a/hRoNNVEzCk1 M7RQ2XtbTeuDd8/IZPkRbp3Ws0PnyJfo1NA1pzYeiB/VTwPBo1GnZ04DpTe6WARs l8SwOWysLExMVYEFiNyY7tLQr/0ba+swBlmE8JJsniwmaOzkvP/OMy61hNusd62J 3PGE+dKE8etd86tJYmUYX/qJzsSodEvMWIom+6LSKicb5nI9h6KdIsTcjPeMofg9 2m4GlO7tuERlUAFHFzZP1axnbLaYk3wlxEs2cu7uTKSX5Q7sx4htFmnWUeacXMz1 INUMwDlDBE4V6TmZ0/QrxK22z7tUSLQ+6FbWjvgHedlaaT2G66bZkJuA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id bW+iFUlpuQPa; Thu, 25 Aug 2011 01:41:07 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.44.74.255]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 4EEDC171C1B; Thu, 25 Aug 2011 01:41:07 +0100 (IST)
Message-ID: <4E559A18.3090005@cs.tcd.ie>
Date: Thu, 25 Aug 2011 01:40:56 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com>
In-Reply-To: <62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.com>, IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 00:40:09 -0000

On 08/24/2011 11:43 PM, Joel Jaeggli wrote:
>
> On Aug 24, 2011, at 3:24 PM, Stephen Farrell wrote:
>> Inflation is accounted for in the figures given. We're
>> still>20% above inflation in terms of hotel prices based
>> on these figures.
>>
>> You might claim hotel price inflation is higher than the
>> overall, I don't know. I would hope the iaoc would know
>> that. What I'm claiming is that the numbers seem to me
>> to show that the outcome is not so good. And hence it seems
>> to me that the iaoc is not performing that well in this respect.
>>
>> You might bring out the meeting fee argument etc. but I
>> think you (the iaoc as a group) should start by acknowledging
>> that there is a real issue here and then try to address
>> that and *not* argue I'm accusing you of bad faith or
>> something.
>
> Does not control for currency fluctuation unless I missed something in the table.
>
> not that externalities such as the ECB members flushing the euro down the toilet don't impact costs but the notion that we can anticipate or ameliorate such risks on a 2-5 year time scale is unlikely.

Not that sure what your point is. If there's a fair way to
arrange the actual data that shows costs not increasing
faster than inflation I'd be interested in seeing that.
I don't believe there is.

While I'm sure there are details of the table I made
up that can be debated, I'd rather the iaoc do that work
and then

My point is that for what I've been able to easily measure
it looks to me like the iaoc haven't got great results.

Also, I don't see that they're actually concentrating on
reducing costs in a way that can be measured. And I think
they should.

S.


From joelja@bogus.com  Wed Aug 24 17:52:32 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34CDA21F8BF4 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:52:32 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fM7-ZfTZJCzA for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:52:31 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C671E21F8BE5 for <ietf@ietf.org>; Wed, 24 Aug 2011 17:52:31 -0700 (PDT)
Received: from [10.101.144.54] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7P0qORB000799 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 25 Aug 2011 00:52:24 GMT (envelope-from joelja@bogus.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E5598D0.6030703@cs.tcd.ie>
Date: Wed, 24 Aug 2011 17:52:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5732DA2E-A007-4166-96BB-97330FFE7905@bogus.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com> <4E5598D0.6030703@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 25 Aug 2011 00:52:25 +0000 (UTC)
Cc: Ole Jacobsen <ole@cisco.com>, IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 00:52:32 -0000

On Aug 24, 2011, at 5:35 PM, Stephen Farrell wrote:
>=20
>> The University Campus, or maybe "University Conference Center" idea
>> is worth exploring, such places do exist (in Atlanta for example),
>> but, as others have pointed out, we need to clearly define what the
>> goal is here and recognize that there are some incompatible
>> requirements.
>=20
> I think this is *very* much worth doing. (Full disclosure: I tried
> to get IETF-72 in Trinity College Dublin but that fell over thanks
> in part to our local fascist sysadmins who hopefully don't read this
> list;-)

It's worth noting that trinity didn't actually have meeting room big =
enough for the plenary at least as the plan for the venue I was =
consulted on went.  each venue has unique challenges, some are harder =
than others.

Having worked at a large  US state school for more than a decade, only =
the summer meeting is likely to align with an academic calender in a way =
that wouldn't cause people to laugh hysterically and show you the door.

From joelja@bogus.com  Wed Aug 24 17:55:47 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03EC821F8B55 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.305
X-Spam-Level: 
X-Spam-Status: No, score=-102.305 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ChrjQNx40glE for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 17:55:46 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0E22221F8B47 for <ietf@ietf.org>; Wed, 24 Aug 2011 17:55:46 -0700 (PDT)
Received: from [10.101.144.54] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7P0tdYh001086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 25 Aug 2011 00:55:39 GMT (envelope-from joelja@bogus.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E559A18.3090005@cs.tcd.ie>
Date: Wed, 24 Aug 2011 17:55:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com> <4E559A18.3090005@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 25 Aug 2011 00:55:39 +0000 (UTC)
Cc: Ole Jacobsen <ole@cisco.com>, IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 00:55:47 -0000

On Aug 24, 2011, at 5:40 PM, Stephen Farrell wrote:

>=20
>=20
> On 08/24/2011 11:43 PM, Joel Jaeggli wrote:
>>=20
>> On Aug 24, 2011, at 3:24 PM, Stephen Farrell wrote:
>>> Inflation is accounted for in the figures given. We're
>>> still>20% above inflation in terms of hotel prices based
>>> on these figures.
>>>=20
>>> You might claim hotel price inflation is higher than the
>>> overall, I don't know. I would hope the iaoc would know
>>> that. What I'm claiming is that the numbers seem to me
>>> to show that the outcome is not so good. And hence it seems
>>> to me that the iaoc is not performing that well in this respect.
>>>=20
>>> You might bring out the meeting fee argument etc. but I
>>> think you (the iaoc as a group) should start by acknowledging
>>> that there is a real issue here and then try to address
>>> that and *not* argue I'm accusing you of bad faith or
>>> something.
>>=20
>> Does not control for currency fluctuation unless I missed something =
in the table.
>>=20
>> not that externalities such as the ECB members flushing the euro down =
the toilet don't impact costs but the notion that we can anticipate or =
ameliorate such risks on a 2-5 year time scale is unlikely.
>=20
> Not that sure what your point is. If there's a fair way to
> arrange the actual data that shows costs not increasing
> faster than inflation I'd be interested in seeing that.
> I don't believe there is.
>=20
> While I'm sure there are details of the table I made
> up that can be debated, I'd rather the iaoc do that work
> and then
>=20
> My point is that for what I've been able to easily measure
> it looks to me like the iaoc haven't got great results.

and what I'm saying is the current venue is 10% more expensive now then =
when negotiated.

so is your deviation 10% 20% etc.

is the ioac on the hook for the value of the us dollar?


> Also, I don't see that they're actually concentrating on
> reducing costs in a way that can be measured. And I think
> they should.
>=20
> S.
>=20


From stephen.farrell@cs.tcd.ie  Wed Aug 24 18:10:45 2011
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 953A321F883A for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.349
X-Spam-Level: 
X-Spam-Status: No, score=-106.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IqIqi6uDocs4 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:10:44 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id DAB3D21F86DD for <ietf@ietf.org>; Wed, 24 Aug 2011 18:10:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 0E23F171C5B; Thu, 25 Aug 2011 02:11:27 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1314234686; bh=6+I4rg+8nd0gCd TgrFWdKsq7YypiuBB31OV/ZCp4Eso=; b=s/F74aeDt465pbl/Y/+bpkaUYSbasC tLnHKjjTagSC8NVJ5W8sfVUQaNavYmxCU8fSoTLsbhtRlwz11ECjENlLLlFyxuBe GATqn0JKPgcV9ecKunVmptQWzolaWnSMtm1tvwmkOOBuTqVYXEsHFQo/xPPMcc8Q mktrZLkyvLXyL3YmU5vcC3qChbOc7Ht4HYLeHlkpDXlWxQAltuCgi/XUlYFe+bBq 4g5+NFkWVztEQFhcHuZ7zkxpL50XVetAEPB4D5wiaGSq//nOLJJ7kn67xYTaAkr8 LyFXnfnE5Z1446wdWy1nmSDI8e1OucjOOnXtM7EVdBN1C4HXAiPtQPiQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 8YhD9vudeUQk; Thu, 25 Aug 2011 02:11:26 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.44.74.255]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 459D7171C1B; Thu, 25 Aug 2011 02:11:15 +0100 (IST)
Message-ID: <4E55A126.90102@cs.tcd.ie>
Date: Thu, 25 Aug 2011 02:11:02 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com> <4E559A18.3090005@cs.tcd.ie> <6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com>
In-Reply-To: <6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.com>, IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 01:10:45 -0000

On 08/25/2011 01:55 AM, Joel Jaeggli wrote:

> and what I'm saying is the current venue is 10% more expensive now then when negotiated.

Ok. I don't know that that information ("when negotiated")
is public.

> so is your deviation 10% 20% etc.

Not that simple. The model I used is based on 6-meeting
inflation adjusted moving averages. So the percentages
don't just add up like that. But feel free to suggest
a model that accounts for currencies like that if you
want. I think if iaoc had some cost model and a specific
goal to reduce costs according to that model, then that'd
be good almost regardless of the model's details.

> is the ioac on the hook for the value of the us dollar?

Nope. iasa and iaoc are on the hook for organising
and that includes costs. There are many things they
don't control and they've a hard job. But then that's
true of most of us;-)

S.

From ole@cisco.com  Wed Aug 24 18:36:04 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04ABA21F8B47 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.098
X-Spam-Level: 
X-Spam-Status: No, score=-102.098 tagged_above=-999 required=5 tests=[AWL=-0.499, BAYES_00=-2.599, GB_AFFORDABLE=1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9VzieDwpy7W for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:36:03 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 44C7C21F8A69 for <ietf@ietf.org>; Wed, 24 Aug 2011 18:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=3408; q=dns/txt; s=iport; t=1314236235; x=1315445835; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=G5kb4EPiycH/ISiFLy77GdI+b+2dbcapNARKDSUjE0k=; b=ZveTvBabbVoBBr+l4cDlKUW/nc9OqCIz+7meXc6yqoM7BWa+EbTwGtNi 7XFye7GFvo2NR8JB2I+/qfci4mBuvmyDJXbcY9AjTGUyNGCVhlodsldhE j11An7HFzcoHoD9wgHPNWWa+ENef2IJFzjs7+I+T1CrwfFd4LrE2OYnpt M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EALimVU6rRDoH/2dsb2JhbABCqAF3gUABAQEBAgESAQIBJC4REAsYLlcGJw6HT5sKAYMmDwGbUoZLBIdhnFM
X-IronPort-AV: E=Sophos;i="4.68,278,1312156800"; d="scan'208";a="16263762"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-8.cisco.com with ESMTP; 25 Aug 2011 01:37:15 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7P1bENH010614; Thu, 25 Aug 2011 01:37:14 GMT
Date: Wed, 24 Aug 2011 18:37:14 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: voting system for future venues?
In-Reply-To: <4E5598D0.6030703@cs.tcd.ie>
Message-ID: <alpine.OSX.2.01.1108241824520.16097@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com> <4E5598D0.6030703@cs.tcd.ie>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 01:36:04 -0000

On Thu, 25 Aug 2011, Stephen Farrell wrote:
> 
> I didn't say that. I said that IETF meeting hotel prices have
> risen more than 20% above inflation. I have no idea if average
> hotel prices for setups like ours have done that, or if the
> IETF attendees are really getting a bad deal. I think the
> latter though to be honest. Have you evidence that I'm right
> or wrong?

I'll let the people who crunch the numbers answer that one.

> 
> > and that isn't limited to the venues under consideration by the 
> > IETF. NANOG and APRICOT hotel rates have gone up as have other 
> > meeting hotel rates,
> 
> Do you/the iaoc have solid information on that or just anecdotes? Do 
> the iaoc communicate with other conference organisers to get such 
> information? Have those other rates gone up more or less than IETF 
> HQ rates?

Well, *I* attend all of those events and *I* have experienced 
significant increases in hotel rates over the last decade. You can 
call that an anecdote I suppose. Based on my experience, the increases 
are across the board.

> 
> Fine. But not very relevant. Hotel prices in, for example,
> Ireland, have fallen thanks to our local financial incompetence.
> I don't know the trends in hotel prices where we meet, but would
> hope that the iaoc does. Do you?

Again, I don't have comprehensive data, but will note (again) that we 
are severely limited by venue availability for an event our size, 
based on the "one-roof" desire, and (often) inclusion of meeting 
rooms.

> 
> > I think the only way to get HQ hotel rates down
> 
> Have the iaoc actually tried to achieve this specific goal?
> Personally, I don't believe you've been doing that, but I
> could be wrong.

It's been said already that there is a tradeoff between "big city" 
venues (that have meeting space) and remote resorts like CityWest: in 
both cases the HQ hotel is often expensive, but the community clearly
wants us to go places where they have alternatives. Hotel rates are
certainly high on our list of factors when choosing a venue, but it
isn't the only factor.

> 
> Go for it and we'll see. Maybe it'll be crap (but to be honest
> how much can it differ from Disney;-) but its worth trying so
> long as the meeting facilities work for the meeting.

We can certainly look into it.

> 
> > The University Campus, or maybe "University Conference Center" idea
> > is worth exploring, such places do exist (in Atlanta for example),
> > but, as others have pointed out, we need to clearly define what the
> > goal is here and recognize that there are some incompatible
> > requirements.
> 
> I think this is *very* much worth doing. (Full disclosure: I tried
> to get IETF-72 in Trinity College Dublin but that fell over thanks
> in part to our local fascist sysadmins who hopefully don't read this
> list;-)
> 
> Bottom line - the HQ hotel is a big cost for those who stay there
> and getting to the unaffordable state for various folks for various
> reasons. *Please* make it a specific goal to reduce that. Or
> produce some model of overall costs that you aim to reduce if you
> prefer. Anything so long as its measurable and starts going down.
> 
> S.
> 
> PS: Just in case. Yes we can stay at alternative hotels. But
> nonetheless, aiming to reduce the HQ hotel rate is still a
> good thing.
> 
> 
> >
> > Ole
> >

From ole@cisco.com  Wed Aug 24 18:41:38 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F5D21F8BB5 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Il5u7gSD5kw2 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:41:37 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id A723B21F8B4E for <ietf@ietf.org>; Wed, 24 Aug 2011 18:41:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=494; q=dns/txt; s=iport; t=1314236570; x=1315446170; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=xMEE0SqtyGMzBS0xj4DvvAbhde+s8ci9W6q5O6UI3hA=; b=dqj0FRU3x+/soTyuocKAinvd5AaEhkN6AQzLJWq5M199ZBhciwEDwj6i H50x2sFHynBcRTYXuSMpW3yy+XMlFje0XTFZcQnsGsGYnqU0kbQr0VSQp QuMdnvjeupnKTRXSJiiFrCKYd7W0hIQktTM7/P37B/hlfoUAh+nOOf/+B k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHynVU6rRDoG/2dsb2JhbABCqAF3gUABAQEBAxIBAgEkPxALRlcGNaJVAYMmDwGbT4ZLBIdhnFM
X-IronPort-AV: E=Sophos;i="4.68,278,1312156800"; d="scan'208";a="16267776"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-7.cisco.com with ESMTP; 25 Aug 2011 01:42:49 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7P1gmS6027318; Thu, 25 Aug 2011 01:42:48 GMT
Date: Wed, 24 Aug 2011 18:42:48 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: voting system for future venues?
In-Reply-To: <4E55A126.90102@cs.tcd.ie>
Message-ID: <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com> <4E559A18.3090005@cs.tcd.ie> <6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com> <4E55A126.90102@cs.tcd.ie>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 01:41:38 -0000

I have been asked to post the following for someone who does not wish 
to be identified:

"I work for a large company that can afford to pay fairly
high room rates at the official HQ hotel. I'm willing to
do so as a way to help the IETF get free meeting rooms
and thereby keep the meeting fee low, reducing the burden
on those with limited budgets. I agree that IAOC should
ensure that there are inexpensive hotels nearby so that
those with a tight budget can save money."


Ole



From prvs=0218402cdc=medel@globetel.com.ph  Wed Aug 24 18:53:06 2011
Return-Path: <prvs=0218402cdc=medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C56B621F8BF8 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level: 
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F2j1p+Lew5xE for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 18:53:06 -0700 (PDT)
Received: from smtp02.globetel.com.ph (smtp02.globetel.com.ph [203.177.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 19FF021F8B8C for <ietf@ietf.org>; Wed, 24 Aug 2011 18:53:05 -0700 (PDT)
Received: from exgtbh02.globetel.com ([10.225.208.154]) by smtp02.globetel.com.ph (8.14.4/8.14.4) with ESMTP id p7P1b9qD011975;  Thu, 25 Aug 2011 09:37:10 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.145]) by exgtbh02.globetel.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 25 Aug 2011 09:54:10 +0800
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: voting system for future venues?
Date: Thu, 25 Aug 2011 09:54:09 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com>
In-Reply-To: <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: voting system for future venues?
Thread-Index: AcxiyF+n6BrAJ55aQW2wkAM01tsIcAAAFjiQ
X-Priority: 1
Priority: Urgent
Importance: high
References: <20110822191708.652C721F8C19@ietfa.amsl.com><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu><4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu><1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net><15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com><4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie><alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com><4E557A33.7050607@cs.tcd.ie><62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com><4E559A18.3090005@cs.tcd.ie><6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com><4E55A126.90102@cs.tcd.ie> <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: "Ole Jacobsen" <ole@cisco.com>, "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
X-OriginalArrivalTime: 25 Aug 2011 01:54:10.0410 (UTC) FILETIME=[E1DB5CA0:01CC62C9]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-08-24_05:2011-08-25, 2011-08-24, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1108240285
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 01:53:06 -0000

Hi,
Likewise.... but
I'm Medel Ramirez, working in a Telco here in the Philippines (Makati
City).
Have been following a lot of technical discussions; likewise in this
matter, would like to extend a hand in this issue.
For you know I have already hosted a lot of Technical Events and one of
the biggest was,
1) First Philippine IPv6 Forum last May 2008 at Sofitel Hotel, Manila,
Philippines; which was attended by participants worldwide...

Regards,
Medel Ramirez
Globe Telecom, Inc
Manila, Philippines

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Ole Jacobsen
Sent: Thursday, August 25, 2011 9:43 AM
To: Stephen Farrell
Cc: IETF-Discussion list; Keith Moore
Subject: Re: voting system for future venues?


I have been asked to post the following for someone who does not wish=20
to be identified:

"I work for a large company that can afford to pay fairly
high room rates at the official HQ hotel. I'm willing to
do so as a way to help the IETF get free meeting rooms
and thereby keep the meeting fee low, reducing the burden
on those with limited budgets. I agree that IAOC should
ensure that there are inexpensive hotels nearby so that
those with a tight budget can save money."


Ole


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

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From hartmans@mit.edu  Wed Aug 24 19:03:12 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F9C21F8B9F; Wed, 24 Aug 2011 19:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.619
X-Spam-Level: 
X-Spam-Status: No, score=-103.619 tagged_above=-999 required=5 tests=[AWL=-1.354, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xU8-rPFw9j3Z; Wed, 24 Aug 2011 19:03:11 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id D512D21F8B30; Wed, 24 Aug 2011 19:03:11 -0700 (PDT)
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 74E8620148; Wed, 24 Aug 2011 22:06:36 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 549E0423D; Wed, 24 Aug 2011 22:04:12 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com>
Date: Wed, 24 Aug 2011 22:04:12 -0400
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> (david black's message of "Wed, 24 Aug 2011 20:45:58 -0400")
Message-ID: <tslliui6ycj.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@ietf.org, gareth.richards@rsa.com, gen-art@ietf.org, ietf-krb-wg@lists.anl.gov, hartmans-ietf@mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 02:03:12 -0000

>>>>>   <david.black@emc.com> writes:


    > [1] In section 6.1 at the top of p.28, I don't believe that the
    > use of lower case "recommended" is a strong enough warning about
    > the danger in using anonymous PKINIT because it exposes the OTP
    > value:

    >    It is therefore recommended that anonymous PKINIT not be used
    > with OTP algorithms that require the OTP value to be sent to the
    > KDC and that careful consideration be made of the security
    > implications before it is used with other algorithms such as those
    > with short OTP values.

    > At a minimum, that warning should be in upper-case:

    >    It is therefore RECOMMENDED that anonymous PKINIT not be used
    > with OTP algorithms that require the OTP value to be sent to the
    > KDC. In addition, the security implications should be carefully
    > considered before anonymous PKINIT is used with other algorithms
    > such as those with short OTP values.

    > Beyond that, the security issue in the first sentence may be
    > severe enough to justify a prohibition, so the following would
    > also be acceptable:

    >    Therefore anonymous PKINIT SHALL NOT be used with OTP
    > algorithms that require the OTP value to be sent to the KDC. In
    > addition, the security implications should be carefully considered
    > before anonymous PKINIT is used with other algorithms such as
    > those with short OTP values.

I definitely agree that we should use RFC 2119 language.
Note that WG participants have questioned this text in last call for
other reasons.
Many implementations use anonymous pkinit in a mode where the KDC's
certificate is verified--that is the client is anonymous but the KDC is
identified through a PKI.
WG participants believe (and I agree) that the security concern does not
apply at all in this case.
So, the text needs reworking.

    > [2] In section 5, the first paragraph in the IANA considerations
    > is unclear, and following its reference to section 4.1, I don't
    > see any clarifying text there either.  I think Sections 4.1 and
    > 4.2 need to say that the value of otp-algID is a URI obtained from
    > the PSKC Algorithm URI Registry, and the first paragraph in
    > section 5 should say that URIs for otp-algID are to be registered
    > in that registry, see RFC 6030.

Why should we require that alg-ids be registered URIs?  I.E. what is
wrong with me using
http://algorithms.painless-security.com/otp/best-thing-since-unsliced-bread
(or a tag URI if you like) for my OTP algorithm?
I have no problem with the IETF registering its algorithms there, or us
encouraging people to register them them, but it's a URI. What purpose
is served by forcing registration?

From presnick@qualcomm.com  Wed Aug 24 19:56:54 2011
Return-Path: <presnick@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45DB121F8B5D for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 19:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.518
X-Spam-Level: 
X-Spam-Status: No, score=-106.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdZv2789Kt4S for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 19:56:53 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1F921F8B5B for <ietf@ietf.org>; Wed, 24 Aug 2011 19:56:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1314241085; x=1345777085; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4E55B9E2.4010406@qualcomm.com>|Date:=20We d,=2024=20Aug=202011=2021:56:34=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Eric=20Burger=20<eburger-l@sta ndardstrack.com>|CC:=20IETF-Discussion=20list=20<ietf@iet f.org>,=20Dave=20CROCKER=20<dcrocker@bbiw.net>|Subject: =20Re:=20voting=20system=20for=20future=20venues? |References:=20<20110822191708.652C721F8C19@ietfa.amsl.co m>=09<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> =09<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>=09<669 98320DD3FCC5628E32634@PST.JCK.COM>=09<F74DDD2D-163A-4CBF- 99A5-E452CBB7C17F@isoc.org>=09<CE8FC485-DA54-491B-B57E-96 DA2FE835FC@network-heretics.com>=09<34E4F50CAFA10349A41E0 756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>=09<E9A8F 486-2327-4F48-B21A-6155CF334F21@network-heretics.com>=09< 4E554C78.9000504@gmail.com>=20<tslr54a8v7s.fsf@mit.edu> =09<4E555B06.6000108@dcrocker.net>=20<tslmxey8sia.fsf@mit .edu>=09<1314218041.1973.204.camel@d430>=20<4E55655C.6030 502@bbiw.net>=09<15F4BD95-8858-4E47-896A-703A472412B1@net work-heretics.com>=20<7AE9A1D4-439A-4857-85BF-C1BED2FC430 9@standardstrack.com>|In-Reply-To:=20<7AE9A1D4-439A-4857- 85BF-C1BED2FC4309@standardstrack.com>|Content-Type:=20tex t/plain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=+pXui57w4pUVdTkWkDf8GzKILbyDCGdvIPAEv4rPNAk=; b=JgMzIeYv3drOvar6uc/imbKbesHSGshbAhOxw5sPpAyEvbME87OJopvi E1Iy5LuTG9a1NDENMHrdHKDl0MidinxnSDK8lAgq4kUpDqd57kj2r8O1d DWtS5VpLYEezeN6NBnWCo+aznjT8Gd83Sxs7nOtsdpOVWPpgI4qtjN2bg U=;
X-IronPort-AV: E=McAfee;i="5400,1158,6448"; a="112759495"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine01.qualcomm.com with ESMTP; 24 Aug 2011 19:58:05 -0700
X-IronPort-AV: E=Sophos;i="4.68,279,1312182000"; d="scan'208";a="155504437"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 24 Aug 2011 19:58:05 -0700
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Aug 2011 19:56:37 -0700
Message-ID: <4E55B9E2.4010406@qualcomm.com>
Date: Wed, 24 Aug 2011 21:56:34 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Eric Burger <eburger-l@standardstrack.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net>	<15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com>
In-Reply-To: <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF-Discussion list <ietf@ietf.org>, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 02:56:54 -0000

On 8/24/11 3:55 PM, Dave CROCKER wrote:

> Sorry, but the vote on Quebec City, and the recent, follow-on 
> commentary are far more substantial and proportionally dominant than a 
> "vocal minority".

On 8/24/11 4:48 PM, Eric Burger wrote:

> Just a reminder, the community VOTED for Quebec City.
>
> Backing up Dave here, the community repeatedly VOTES or, in 
> post-meeting surveys, INDICATES (VOTES) for the sort of venues we have 
> been booking.

OK, what follows is based on precisely one data point (i.e., me), but I 
hope you will see that it is therefore as worthy as these two claims 
about the community having "voted for Quebec City".

I pondered long and hard when I answered that stupid survey question. 
Because what it asked me was, "Which would you prefer, Vancouver, 
Quebec, or <I think one other North American place I can't remember>?" 
And I, stupidly apparently, answered Quebec. And it was stupid because I 
didn't think you were actually going to count as you apparently did. You 
see, I answered Quebec because (a) I like Quebec as cities go; (b) it 
happens to be a shorter physical trip for me than Vancouver; and (c) I 
happen to work for one of those companies who pays my bills, so I really 
don't care what the relative prices of hotels are.

But you never asked the question that I would have answered quite 
differently: "Which place is the most logical for the IETF to meet?" 
Because had you asked that, I surely would have chosen Vancouver over 
Quebec. It's a crapload easier for most folks to get to, they have 
facilities that have worked well for us in the past, and *I don't object 
to going to Vancouver over Quebec*. You see, if you start asking for 
objections as opposed to desires, I think you'll get much different 
answers. You'd certainly hear about objections to certain travel 
itineraries. You certainly hear objections to total cost profiles. 
Because the community is now weighted in favor of folks with corporate 
travel budgets, I suspect the "desire" answers are going to be much 
different than the "objections" answers.

Now, like I said, one data point. Maybe the vast majority of people not 
only wanted to go to Quebec, but thought it was the right place to go 
and would have objected to a choice of Vancouver over Quebec. But I 
don't think you are justified in claiming that without some additional 
data. And either way, I don't think "Where do you want to meet?" is the 
right question to ask.

There are a host of reasons that voting is a stupid decision making 
process. I thought we knew that.

pr

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


From brian.e.carpenter@gmail.com  Wed Aug 24 20:11:19 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D55DE21F8560 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVqDd796MF8B for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:11:16 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id E1F8921F855D for <ietf@ietf.org>; Wed, 24 Aug 2011 20:11:14 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1641761gwb.31 for <ietf@ietf.org>; Wed, 24 Aug 2011 20:12:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=fX7FPh86acyKFPRPgmB1ZmYaMzHBLxVO10CMeItRQW0=; b=ugtMEEeFuXiRojbK2BLuh7PLW9CallwJyr6/rq9KpYEOIymlIMG6A4bYGFUD3kjuVx KlNwUio+xPwnKB6kxkuW0kbVa/5Hf7ItiSuCGLhQ11QpZegDCRefMbSUSj8rcqpp0dwu 0nVtjwqgEoubw1hfEjUQKX0H261joCM6zYFmI=
Received: by 10.236.138.228 with SMTP id a64mr35203267yhj.4.1314241946911; Wed, 24 Aug 2011 20:12:26 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id x42sm254317yhm.37.2011.08.24.20.12.24 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 20:12:26 -0700 (PDT)
Message-ID: <4E55BD82.9020309@gmail.com>
Date: Thu, 25 Aug 2011 15:12:02 +1200
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: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie>
In-Reply-To: <4E5574AA.3030705@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 03:11:19 -0000

Stephen,

Thanks. Now, we should maybe calibrate that in something other
than USD (maybe in milligrams of gold, or the Economist's Bic Mac
index) and also find an independent source on hotel price inflation.

I'm not assuming that it's the IAOC's fault, but the numbers are bad.

Regards
   Brian

On 2011-08-25 10:01, Stephen Farrell wrote:
> 
> On 08/24/2011 10:32 PM, Brian E Carpenter wrote:
>> It would be interesting if someone with historical data could plot IETF
>> hotel and meeting fee costs over the years since 1986, normalized to take
>> account of inflation and trade-weighted currency variations. I really
>> can't guess what the outcome would be.
> 
> Well, since you ask:-)
> 
> I was complaining to the iaoc about this last year and just this
> evening sent them the attached updated whinge.
> 
> Not all you asked for but some of it.
> 
> IMO, it doesn't look that good in terms of iaoc performance over
> time.
> 
> S.
> 
> ------------------------------------------------------------------------
> 
> Subject:
> Re: increasing IETF hotel costs
> From:
> Stephen Farrell <stephen.farrell@cs.tcd.ie>
> Date:
> Wed, 24 Aug 2011 21:44:13 +0100
> To:
> IAOC <iaoc@ietf.org>
> 
> To:
> IAOC <iaoc@ietf.org>
> 
> 
> 
> Hi again,
> 
> We had some exchanges on this last year and its broken
> out again on the IETF list so I thought I'd update those
> figures.
> 
> Looks to me like this is getting worse not better. The
> original text below explains the method followed.
> 
> I would be *really* pleased if you guys would state
> publicly that you've set yourselves a goal to
> address this.
> 
> Stephen.
> 
> On 11/16/2010 06:30 PM, Stephen Farrell wrote:
>>
>> Hi,
>>
>> So the expensive hotel thing has been bugging me. I had the
>> impression that it just keeps getting more expensive and from
>> the attached, that appears to be true. I realise that there
>> are a bunch of constraints, but my feeling is that this is
>> not being specifically addressed and is getting worse.
>>
>>> From the graphic attached we seem to have started to get
>> more expensive around 2007 and there's no sign of us
>> getting cheaper. We now seem to be an inflation-adjusted
>> 15% more expensive from the already-expensive 2003-2007
>> hotel rates.
>>
>> Any comments, or, much better, plans to address this?
>>
>> What I did:
>>
>> - Go to each of the meeting pages from IETF 56-79
>> - Take the lowest meeting-hotel cost quoted, without including taxes
>> - Put those in a spreadsheet (attached as xls and O-O)
>> - Convert currencies using the historic figures for the relevant
>>    month (URL is in the spreadsheet)
>> - Calculate the 6-meeting running average cost to smooth
>>    geographic differences and incidentals
>> - Divide by figures for the US consumer price index, (URL is in
>>    the spreadsheet)
>> - Normalise so the first 6-meeting average is 1.00
>> - Plot that giving the graphic (jpg) attached.
>>
>> Thanks,
>> Stephen.
> 
> ------------------------------------------------------------------------
> 

From ole@cisco.com  Wed Aug 24 20:16:22 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E72721F874E for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dsnuRjp16VGx for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:16:22 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id E9AD121F873A for <ietf@ietf.org>; Wed, 24 Aug 2011 20:16:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1165; q=dns/txt; s=iport; t=1314242254; x=1315451854; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=OSkGU4HWrnspssUSK5Kqk5CO/OV99FQbV3rVvwazJPU=; b=gfR26MT4lhOGAHI1AjrLiVKGnDFcv7YJzbbyoaBat9iS6I0zCy3coDys /Hh39uAV2opvI04nSuc/KwC9e+LZtqKdpDYmAjQpTLrSW6aZ66rUopLXo Qb7soP/PXwonf68KuzhPIMUJA2j9wxJr053TFaeZ8szUmwB9WhrJZRW9O M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAFK+VU6rRDoG/2dsb2JhbAA/A6gAd4FAAQEBAQIBEgECASQ/BQsLRlcGEyKHT5pgAYMmDwGbUYNCgwkEh2GVMIcj
X-IronPort-AV: E=Sophos;i="4.68,279,1312156800"; d="scan'208";a="16272639"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-6.cisco.com with ESMTP; 25 Aug 2011 03:17:33 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7P3HXld032750; Thu, 25 Aug 2011 03:17:33 GMT
Date: Wed, 24 Aug 2011 20:17:33 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
Subject: RE: voting system for future venues?
In-Reply-To: <A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com>
Message-ID: <alpine.OSX.2.01.1108242012340.16097@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com> <tslmxey8sia.fsf@mit.edu><1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net><15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com><4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie><alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com><4E557A33.7050607@cs.tcd.ie><62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com><4E559A18.3090005@cs.tcd.ie><6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com><4E55A126.90102@cs.tcd.ie> <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com> <A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 03:16:22 -0000

Medel,

The Sofitel Manila is where APRICOT 2009 was held. A great venue, 
possibly even large enough to hold an IETF (I am not sure), *and*
the rate (at the time) at 7,525 Pesos was pretty good. Today it
is $177 which is still pretty good. The question is: would the IETF
go to the Philippines for a meeting. It's worth finding out.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Thu, 25 Aug 2011, GT RAMIREZ, Medel G. wrote:

> Hi,
> Likewise.... but
> I'm Medel Ramirez, working in a Telco here in the Philippines (Makati
> City).
> Have been following a lot of technical discussions; likewise in this
> matter, would like to extend a hand in this issue.
> For you know I have already hosted a lot of Technical Events and one of
> the biggest was,
> 1) First Philippine IPv6 Forum last May 2008 at Sofitel Hotel, Manila,
> Philippines; which was attended by participants worldwide...
> 
> Regards,
> Medel Ramirez
> Globe Telecom, Inc
> Manila, Philippines
> 

From brian.e.carpenter@gmail.com  Wed Aug 24 20:20:43 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B406F21F874E for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-8TE5acQZw8 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:20:43 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3F90E21F86DF for <ietf@ietf.org>; Wed, 24 Aug 2011 20:20:43 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1643310gxk.31 for <ietf@ietf.org>; Wed, 24 Aug 2011 20:21:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JykJf0rU+WfC0KBBzO3eY8J8+Xk8pUcNrOR2z/vY4Os=; b=QfI9YRgT5C1Dv/JEtT0kLmNwI6UMtkZT5wvwlTOaCY9gjdSZtZOwA0kWODM1kRXe+s TlIjJCWwmO1b8jbGMRgkKy16Dh/WMzDfSnujXQd/X8xWk6W0PPJh6AcRTb9hkqIWByZI c4e/r3STmXchYWb1IfMuW51RUFWM+wzpmlqJ4=
Received: by 10.236.181.170 with SMTP id l30mr35485841yhm.126.1314242515272; Wed, 24 Aug 2011 20:21:55 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id j45sm253886yhe.78.2011.08.24.20.21.52 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 20:21:54 -0700 (PDT)
Message-ID: <4E55BFB9.2070200@gmail.com>
Date: Thu, 25 Aug 2011 15:21:29 +1200
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: Ole Jacobsen <ole@cisco.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net>	<15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>	<4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie>	<alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com>	<4E557A33.7050607@cs.tcd.ie>	<62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com>	<4E559A18.3090005@cs.tcd.ie>	<6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com>	<4E55A126.90102@cs.tcd.ie> <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 03:20:43 -0000

On 2011-08-25 13:42, somebody other than Ole Jacobsen wrote:

> "I agree that IAOC should
> ensure that there are inexpensive hotels nearby so that
> those with a tight budget can save money."

This is the key point. The anchor hotel, especially when there
is a convention centre involved, is quite likely to be overpriced.
The IAOC should, IMNSHO, ensure that an adequate set of moderately
priced hotels within a short walk of the venue is available.
That seems to be the problem in Taipei; the backup hotel is
useless and not particularly cheap.

   Brian

From ajs@anvilwalrusden.com  Wed Aug 24 20:24:57 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C28421F8B5B for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level: 
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mamssRHh2rzR for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:24:56 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3DC21F86BE for <ietf@ietf.org>; Wed, 24 Aug 2011 20:24:56 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4D6B31ECB41D for <ietf@ietf.org>; Thu, 25 Aug 2011 03:26:09 +0000 (UTC)
Date: Wed, 24 Aug 2011 23:26:06 -0400
From: ajs@anvilwalrusden.com
To: ietf@ietf.org
Subject: Re: voting system for future venues?
Message-ID: <20110825032605.GI53261@shinkuro.com>
References: <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 03:24:57 -0000

On Wed, Aug 24, 2011 at 03:07:59PM -0700, Ole Jacobsen wrote:
> 
> "....doesn't look that good in terms of iaoc performance over time."
> 
> Are you seriously suggesting that we are looking for more and more 
> expensive venues over time? Do you not think there might be some
> factors such as inflation, currency fluctuations, general cost 
> increases (oil prices perhaps) that dictate most of this?

With respect, I don't think that's what he was suggesting at all.  I
think he was suggesting that he had a model of expected increases in
costs, and plotted against that the actual increases in costs, and
noted that there was a difference.  I might have phrased the question
myself as, "Can you think of gaps in my model that explain the
difference?"  But I think the point is a fair one: if there is a
difference between the rate of increase for IETF meetings and the rate
of other increases, one either needs an explanation, or one might
conclude that the negotiations are not as tough as they might be.

None of this is, on my part, an effort to disparage the IAOC.
Frankly, having observed things closely, I think you're all nuts to be
willing to do that.  It's a thankless task.  But that is not a
response to Stephen's model, and given the work that went into it, I
think it is important evidence.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From john-ietf@jck.com  Wed Aug 24 20:35:45 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C5621F8B26 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gkmr78AHi-ki for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:35:44 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2E71821F8B13 for <ietf@ietf.org>; Wed, 24 Aug 2011 20:35:44 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QwQkR-0000Eq-Fp; Wed, 24 Aug 2011 23:36:55 -0400
Date: Wed, 24 Aug 2011 23:36:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: voting system for future venues?
Message-ID: <EB3E6E8F9FA601100DD26607@PST.JCK.COM>
In-Reply-To: <4E55B9E2.4010406@qualcomm.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com>	<tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net>	<tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430>	<4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com> <4E55B9E2.4010406@qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 03:35:45 -0000

--On Wednesday, August 24, 2011 21:56 -0500 Pete Resnick
<presnick@qualcomm.com> wrote:

>...
>> Just a reminder, the community VOTED for Quebec City.
>> 
>> Backing up Dave here, the community repeatedly VOTES or, in 
>> post-meeting surveys, INDICATES (VOTES) for the sort of
>> venues we have  been booking.
> 
> OK, what follows is based on precisely one data point (i.e.,
> me), but I hope you will see that it is therefore as worthy as
> these two claims about the community having "voted for Quebec
> City".
> 
> I pondered long and hard when I answered that stupid survey
> question. Because what it asked me was, "Which would you
> prefer, Vancouver, Quebec, or <I think one other North
> American place I can't remember>?" And I, stupidly apparently,
> answered Quebec. And it was stupid because I didn't think you
> were actually going to count as you apparently did. You see, I
> answered Quebec because (a) I like Quebec as cities go; (b) it
> happens to be a shorter physical trip for me than Vancouver;
> and (c) I happen to work for one of those companies who pays
> my bills, so I really don't care what the relative prices of
> hotels are.
> 
> But you never asked the question that I would have answered
> quite differently: "Which place is the most logical for the
> IETF to meet?" Because had you asked that, I surely would have
> chosen Vancouver over Quebec. It's a crapload easier for most
> folks to get to, they have facilities that have worked well
> for us in the past, and *I don't object to going to Vancouver
> over Quebec*. You see, if you start asking for objections as
> opposed to desires, I think you'll get much different answers.
> You'd certainly hear about objections to certain travel
> itineraries. You certainly hear objections to total cost
> profiles. Because the community is now weighted in favor of
> folks with corporate travel budgets, I suspect the "desire"
> answers are going to be much different than the "objections"
> answers.
>...

FWIW, and a second data point: I tried to point out this
particular difficulty in the "vote" process several times, both
when the poll was being conducted and more recently.  While our
reasons are different, my response to the question asked and my
likely responses had the obvious other question(s) been asked,
would have been identical to yours.

> But I don't think you are justified in
> claiming that without some additional data. And either way, I
> don't think "Where do you want to meet?" is the right question
> to ask.

Exactly.

> There are a host of reasons that voting is a stupid decision
> making process. I thought we knew that.

We used to, once upon a time.

best,
   john



From randy@qualcomm.com  Wed Aug 24 20:42:03 2011
Return-Path: <randy@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60A2721F8C08 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.557
X-Spam-Level: 
X-Spam-Status: No, score=-106.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uA+1IA-ybKgz for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 20:42:02 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id CF31421F8B1D for <ietf@ietf.org>; Wed, 24 Aug 2011 20:42:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1314243795; x=1345779795; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240617ca7b7430775a@[172.16.1.69]> |In-Reply-To:=20<alpine.OSX.2.01.1108241614510.16097@sjc- vpn5-137.cisco.com>|References:=20<20110822191708.652C721 F8C19@ietfa.amsl.com>=0D=0A=20<801FB726-F672-4F7F-8D9C-7E D37DB08672@cs.ucla.edu>=0D=0A=20<FE5EB7C9-C395-4B98-A0D4- 8B2320F78C04@isoc.org>=0D=0A=20<66998320DD3FCC5628E32634@ PST.JCK.COM>=0D=0A=20<F74DDD2D-163A-4CBF-99A5-E452CBB7C17 F@isoc.org>=0D=0A=20<CE8FC485-DA54-491B-B57E-96DA2FE835FC @network-heretics.com>=0D=0A=20<34E4F50CAFA10349A41E07565 50084FB0D55796B@PRVPEXVS04.corp.twcable.com>=0D=0A=20<E9A 8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> =0D=0A=20<4E554C78.9000504@gmail.com>=20<tslr54a8v7s.fsf@ mit.edu>=0D=0A=20<4E555B06.6000108@dcrocker.net>=20<tslmx ey8sia.fsf@mit.edu>=0D=0A=20<1314218041.1973.204.camel@d4 30>=20<4E55655C.6030502@bbiw.net>=0D=0A=20<15F4BD95-8858- 4E47-896A-703A472412B1@network-heretics.com>=0D=0A=20<4E5 56DFC.5060705@gmail.com>=20<4E5574AA.3030705@cs.tcd.ie> =0D=0A=20<alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137 .cisco.com>=0D=0A=20<4E557A33.7050607@cs.tcd.ie>=0D=0A=20 <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.c om>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Wed, =2024=20Aug=202011=2020:40:08=20-0700|To:=20Ole=20Jacobse n=20<ole@cisco.com>,=20Stephen=20Farrell=20<stephen.farre ll@cs.tcd.ie>|From:=20Randall=20Gellens=20<randy@qualcomm .com>|Subject:=20Re:=20voting=20system=20for=20future=20v enues?|CC:=20IETF-Discussion=20list=20<ietf@ietf.org>,=20 Keith=20Moore=0D=0A=09<moore@network-heretics.com> |MIME-Version:=201.0|Content-Type:=20text/plain=3B=20char set=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.39.5]; bh=xGuZT02zhnOIPIPXIUzIEjMHucI6pkXnAlIyrixoNLo=; b=TroP1BCjBF+HGvthM9C/qZ08AkqctlRLMxbgbkFp84XWOLPc9Cs61IPs yYY+J1qvwQD0bd9DsC0F+jS7msR2Y6uXFnC9U78RJmBdcVuVc4QBDJ8jN IBhp+ayUKqgKnWQ0PrH/0DE0s5AghP4zvpd+z2YpKlbwJEkaD+FWnMilV E=;
X-IronPort-AV: E=McAfee;i="5400,1158,6448"; a="112765107"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine01.qualcomm.com with ESMTP; 24 Aug 2011 20:43:14 -0700
X-IronPort-AV: E=Sophos;i="4.68,279,1312182000"; d="scan'208";a="155504707"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 24 Aug 2011 20:43:14 -0700
Received: from [172.16.1.69] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Aug 2011 20:43:13 -0700
Message-ID: <p06240617ca7b7430775a@[172.16.1.69]>
In-Reply-To: <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <4E557A33.7050607@cs.tcd.ie> <alpine.OSX.2.01.1108241614510.16097@sjc-vpn5-137.cisco.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 24 Aug 2011 20:40:08 -0700
To: Ole Jacobsen <ole@cisco.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: voting system for future venues?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 03:42:03 -0000

At 4:32 PM -0700 8/24/11, Ole Jacobsen wrote:

>  I think the only way to get HQ hotel rates down is to go to the sort
>  of places that the IETF seems to not want to go. One of the cheapest
>  places to fly to in the world is Las Vegas. You can also get really
>  good hotel rates there, group or individual. Since I went to Las Vegas
>  every year for 10+ years and basically did nothing but attend a
>  conference and tradeshow *I* have no problem going back and would
>  certainly consider it an option, but I certainly don't love it and
>  wouldn't care if I ever set foot there again, and I know for a fact
>  that many on this list feel the same way.

I suspect (but don't have any actual knowledge) that Minneapolis or 
Vancouver would be a compromise that would has worked fairly well in 
the past.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
As soon as we started programming, we found to our surprise that it
wasn't as easy to get programs right as we had thought.  Debugging had
to be discovered.  I can remember the exact instant when I realized
that a large part of my life from then on was going to be spent in
finding mistakes in my own programs.
 --Maurice Wilkes discovers debugging, 1949 (courtesy of Paul Robinson)

From ole@cisco.com  Wed Aug 24 21:04:15 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B1A021F8C74 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 21:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nfVZ2iJRy1aZ for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 21:04:15 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5248521F8C59 for <ietf@ietf.org>; Wed, 24 Aug 2011 21:04:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1922; q=dns/txt; s=iport; t=1314245124; x=1315454724; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=PeVyo8Rtn8FeTL5tDFUnNkIaqyJ6EkNiwqk/VZlYLxI=; b=KhQ9TEiJ6T7Iqnqs9jvBUaory+x2lIgQfd1si/TiZONMdWxOyg9JNGeH l58tg85DubCeMYOGSDsoU6pG/dK82bTIg6jdFCOmxzQnhIPrVL+QVPZYr Cr/6yf0tzPJKQQ+RNsAW2J3ma/dgYYw78Qx5vh8SX0KSwihZ94LiUgd/X w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuMFAPnIVU6rRDoJ/2dsb2JhbAA/A5hsjxR3gUABAQEBAgEBAQEPAQIBJDQLBQsLGC4nMBkih08Emn0BgyYPAZtSg0KDCQSHYZUwhyM
X-IronPort-AV: E=Sophos;i="4.68,279,1312156800"; d="scan'208";a="16279726"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-3.cisco.com with ESMTP; 25 Aug 2011 04:05:23 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7P45MwS032739; Thu, 25 Aug 2011 04:05:23 GMT
Date: Wed, 24 Aug 2011 21:05:22 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: ajs@anvilwalrusden.com
Subject: Re: voting system for future venues?
In-Reply-To: <20110825032605.GI53261@shinkuro.com>
Message-ID: <alpine.OSX.2.01.1108242104570.18070@sjc-vpn5-137.cisco.com>
References: <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <20110825032605.GI53261@shinkuro.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 04:04:15 -0000

Right, and I apologize for the wording.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 24 Aug 2011, ajs@anvilwalrusden.com wrote:

> On Wed, Aug 24, 2011 at 03:07:59PM -0700, Ole Jacobsen wrote:
> > 
> > "....doesn't look that good in terms of iaoc performance over time."
> > 
> > Are you seriously suggesting that we are looking for more and more 
> > expensive venues over time? Do you not think there might be some
> > factors such as inflation, currency fluctuations, general cost 
> > increases (oil prices perhaps) that dictate most of this?
> 
> With respect, I don't think that's what he was suggesting at all.  I
> think he was suggesting that he had a model of expected increases in
> costs, and plotted against that the actual increases in costs, and
> noted that there was a difference.  I might have phrased the question
> myself as, "Can you think of gaps in my model that explain the
> difference?"  But I think the point is a fair one: if there is a
> difference between the rate of increase for IETF meetings and the rate
> of other increases, one either needs an explanation, or one might
> conclude that the negotiations are not as tough as they might be.
> 
> None of this is, on my part, an effort to disparage the IAOC.
> Frankly, having observed things closely, I think you're all nuts to be
> willing to do that.  It's a thankless task.  But that is not a
> response to Stephen's model, and given the work that went into it, I
> think it is important evidence.
> 
> Best regards,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From prvs=0218402cdc=medel@globetel.com.ph  Wed Aug 24 21:34:54 2011
Return-Path: <prvs=0218402cdc=medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4B021F8B1E for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 21:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.472
X-Spam-Level: 
X-Spam-Status: No, score=-1.472 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DKhc+nMGU1Am for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 21:34:53 -0700 (PDT)
Received: from smtp02.globetel.com.ph (smtp02.globetel.com.ph [203.177.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 01FD421F8B13 for <ietf@ietf.org>; Wed, 24 Aug 2011 21:34:52 -0700 (PDT)
Received: from exgtbh01.globetel.com ([10.225.208.17]) by smtp02.globetel.com.ph (8.14.4/8.14.4) with ESMTP id p7P4IrdI013974;  Thu, 25 Aug 2011 12:18:53 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.145]) by exgtbh01.globetel.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 25 Aug 2011 12:35:53 +0800
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: voting system for future venues?
Date: Thu, 25 Aug 2011 12:35:52 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE1279DD3C@EXVSGT02.globetel.com>
In-Reply-To: <alpine.OSX.2.01.1108242012340.16097@sjc-vpn5-137.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: voting system for future venues?
Thread-Index: Acxi1YnAXt6frFwiQCm4BAw2Pid4KgACeL2A
X-Priority: 1
Priority: Urgent
Importance: high
References: <20110822191708.652C721F8C19@ietfa.amsl.com><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com> <tslmxey8sia.fsf@mit.edu><1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net><15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com><4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie><alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com><4E557A33.7050607@cs.tcd.ie><62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com><4E559A18.3090005@cs.tcd.ie><6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com><4E55A126.90102@cs.tcd.ie> <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com> <A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com> <alpine.OSX.2.01.110 82420123 40.16097@sjc-vpn5-137.cisco.com>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: "Ole Jacobsen" <ole@cisco.com>
X-OriginalArrivalTime: 25 Aug 2011 04:35:53.0927 (UTC) FILETIME=[799A8D70:01CC62E0]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-08-25_01:2011-08-25, 2011-08-24, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1108240323
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 04:34:54 -0000

Hi Ole,
If Sofitel Manila, will not be enough space for a 5 to 6 sessions
@ 200 seats at same time there is a larger spaces around that area,
Either SMX / Mall of Asia or our World Trade Center, Manila.

We welcome you to our beautiful country, Philippines.

Regards,
Medel
++++++++++++++++++++++++++++++++++++++++=20

-----Original Message-----
From: Ole Jacobsen [mailto:ole@cisco.com]=20
Sent: Thursday, August 25, 2011 11:18 AM
To: GT RAMIREZ, Medel G.
Cc: Stephen Farrell; IETF-Discussion list; Keith Moore
Subject: RE: voting system for future venues?

Medel,

The Sofitel Manila is where APRICOT 2009 was held. A great venue,=20
possibly even large enough to hold an IETF (I am not sure), *and*
the rate (at the time) at 7,525 Pesos was pretty good. Today it
is $177 which is still pretty good. The question is: would the IETF
go to the Philippines for a meeting. It's worth finding out.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Thu, 25 Aug 2011, GT RAMIREZ, Medel G. wrote:

> Hi,
> Likewise.... but
> I'm Medel Ramirez, working in a Telco here in the Philippines (Makati
> City).
> Have been following a lot of technical discussions; likewise in this
> matter, would like to extend a hand in this issue.
> For you know I have already hosted a lot of Technical Events and one
of
> the biggest was,
> 1) First Philippine IPv6 Forum last May 2008 at Sofitel Hotel, Manila,
> Philippines; which was attended by participants worldwide...
>=20
> Regards,
> Medel Ramirez
> Globe Telecom, Inc
> Manila, Philippines
>=20

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From glenzorn@gmail.com  Wed Aug 24 22:04:28 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 363F021F8AB0; Wed, 24 Aug 2011 22:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkNY+Ga0sOzL; Wed, 24 Aug 2011 22:04:27 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8643E21F8AA9; Wed, 24 Aug 2011 22:04:27 -0700 (PDT)
Received: by gyf3 with SMTP id 3so1709494gyf.31 for <multiple recipients>; Wed, 24 Aug 2011 22:05:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qXoz5zfFCAaNLYbXGQT4t3ixyApz5GqEbKW6C+FQZbI=; b=fQg/Usu6/9Bd2G6S2Z8kGkS/SokuJlq5HgTRfJrruhL4Ku3FS/A3OP/aglvVvPqsQt 4e5to334pjVgGeZxPcMR4QP4CrheGv8p2I5hk0kbmRDUs8wB8/UPQgUX2EprZo3S+Hy4 BNtiyO1DV22AmiPp2BWRBxfidMg0a6lIcNrhE=
Received: by 10.101.144.19 with SMTP id w19mr5634276ann.119.1314248739611; Wed, 24 Aug 2011 22:05:39 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-120-20-200.revip2.asianet.co.th [124.120.20.200]) by mx.google.com with ESMTPS id 9sm232898and.25.2011.08.24.22.05.35 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 22:05:39 -0700 (PDT)
Message-ID: <4E55D81B.9000505@gmail.com>
Date: Thu, 25 Aug 2011 12:05:31 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "George, Wesley" <wesley.george@twcable.com>
Subject: Re: IAOC, travel and hotel prices (was RE: Hyatt Taipei cancellation policy?)
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: Keith Moore <moore@network-heretics.com>, Lixia Zhang <lixia@cs.ucla.edu>, Secretariat IETF <ietf-secretariat@ietf.org>, John C Klensin <john-ietf@jck.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 05:04:28 -0000

On 8/24/2011 8:31 PM, George, Wesley wrote:
> I’ve been watching this discussion across several attendee lists,
> plenaries, etc and it appears that we have a routing loop.
> 
>  
> 
> Perhaps it’s time for those who seem most concerned about this to author
> a BCP draft regarding IETF meeting venue and hotel selection policies
> that addresses this, so that IAOC has a bit clearer instructions and a
> documented policy based on community consensus, rather than this
> discussion continuing to come up every couple of meetings, and the
> general response from the IAOC being “this is hard, we’re doing the best
> we can… [example, explanation]”

I think that a large part of the problem is that the IAOC is attempting
to satisfy policies based upon consensus.  Unfortunately, the consensus
seems to be largely centered around convenience (if not outright
luxury), a goal that is mostly incompatible with cost containment.  Most
people seem to want to be able to commute to sessions by (at most)
walking across the street, more preferably via elevator.  A large
conveniently located bar is very popular, as well.  Convenience costs money.

...

From melinda.shore@gmail.com  Wed Aug 24 22:10:16 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9DA721F8B65 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 22:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J7CVbEWUUP51 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 22:10:15 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 44CC721F8AED for <ietf@ietf.org>; Wed, 24 Aug 2011 22:10:15 -0700 (PDT)
Received: by pzk33 with SMTP id 33so4448683pzk.18 for <ietf@ietf.org>; Wed, 24 Aug 2011 22:10:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+BxvJEfYynKEyz6SmTuUo3E7uo8k6VzUWuIxIsBWmaI=; b=VHfkG1SnM2ierjXfYUGvkZKZuodF+F5ix97XTOOx77Yao1sN9Kb2EvN9xc91adiFSc S6u3cY/jmu+4lk7Gw3FJZ9ZkwJRoOoj/os5/oKM2B5U0TfUIaSxSizUu8aVhiQotXHdX /HME4BF6Wh/IkAaC3GoslWbZQip12nkz1HJy0=
Received: by 10.143.58.20 with SMTP id l20mr737834wfk.351.1314249043408; Wed, 24 Aug 2011 22:10:43 -0700 (PDT)
Received: from polypro.local (66-230-82-131-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.131]) by mx.google.com with ESMTPS id u2sm1048397pbq.9.2011.08.24.22.10.41 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 24 Aug 2011 22:10:42 -0700 (PDT)
Message-ID: <4E55D94F.9020307@gmail.com>
Date: Wed, 24 Aug 2011 21:10:39 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAOC, travel and hotel prices (was RE: Hyatt Taipei cancellation policy?)
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com> <4E55D81B.9000505@gmail.com>
In-Reply-To: <4E55D81B.9000505@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 05:10:16 -0000

On 8/24/11 9:05 PM, Glen Zorn wrote:
> I think that a large part of the problem is that the IAOC is attempting
> to satisfy policies based upon consensus.

Really?  Consensus of whom?  I haven't seen anything remotely
like consensus on much to do with meeting logistics.  Closest
we seem to have come is a couple of surveys, which apparently
were treated something like votes by the people who worry
about such things.

Melinda

From randy@qualcomm.com  Wed Aug 24 22:39:03 2011
Return-Path: <randy@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD5C21F85FE; Wed, 24 Aug 2011 22:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.558
X-Spam-Level: 
X-Spam-Status: No, score=-106.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVOctYtQRKvp; Wed, 24 Aug 2011 22:39:02 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4010D21F85F7; Wed, 24 Aug 2011 22:39:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1314250815; x=1345786815; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240619ca7b8f45d047@[172.16.1.69]> |In-Reply-To:=20<4E55D81B.9000505@gmail.com>|References: =20<20110822191708.652C721F8C19@ietfa.amsl.com>=0D=0A=20< 801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>=0D=0A =20<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>=0D=0A =20<66998320DD3FCC5628E32634@PST.JCK.COM>=0D=0A=20<F74DDD 2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>=0D=0A=20<CE8FC48 5-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>=0D=0A =20<34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.c orp.twcable.com>=0D=0A=20<4E55D81B.9000505@gmail.com> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Wed,=202 4=20Aug=202011=2022:39:02=20-0700|To:=20Glen=20Zorn=20<gl enzorn@gmail.com>,=20"George,=20Wesley"=0D=0A=09<wesley.g eorge@twcable.com>|From:=20Randall=20Gellens=20<randy@qua lcomm.com>|Subject:=20Re:=20IAOC,=20travel=20and=20hotel =20prices=20(was=20RE:=20Hyatt=20Taipei=0D=0A=20cancellat ion=20=09policy?)|CC:=20Keith=20Moore=20<moore@network-he retics.com>,=20Lixia=20Zhang=20<lixia@cs.ucla.edu>,=0D=0A =09Secretariat=20IETF=20<ietf-secretariat@ietf.org>,=20Jo hn=20C=20Klensin=0D=0A=09<john-ietf@jck.com>,=20IETF-Disc ussion=20list=20<ietf@ietf.org>|MIME-Version:=201.0 |Content-Type:=20text/plain=3B=20charset=3D"us-ascii"=3B =20format=3Dflowed|X-Random-Sig-Tag:=201.0b28 |X-Originating-IP:=20[172.30.39.5]; bh=dehtkshM3NePIE4KBZDEwgMUHWnGzAzAfa1iuxcN4AU=; b=PcF2w2GvfQwWqHf/6Jw6yTCtFg4vrkb3NPYsi53K4m3GM5CbJzVV3Ktk wWcTAWD0UDTDyODTkYIliR642QaVNt9DtUQXKydhxFBjUopY101YrFB16 yz4acSec0qJGO9qhTkpZoGIFUMp5OlUAWxwlXxB5x1tTXIS/qwQYeFven E=;
X-IronPort-AV: E=McAfee;i="5400,1158,6448"; a="112777899"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 24 Aug 2011 22:40:14 -0700
X-IronPort-AV: E=Sophos;i="4.68,279,1312182000"; d="scan'208";a="64671846"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 24 Aug 2011 22:40:15 -0700
Received: from [172.16.1.69] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 24 Aug 2011 22:40:13 -0700
Message-ID: <p06240619ca7b8f45d047@[172.16.1.69]>
In-Reply-To: <4E55D81B.9000505@gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com> <4E55D81B.9000505@gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 24 Aug 2011 22:39:02 -0700
To: Glen Zorn <glenzorn@gmail.com>, "George, Wesley" <wesley.george@twcable.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: IAOC, travel and hotel prices (was RE: Hyatt Taipei cancellation 	policy?)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: John C Klensin <john-ietf@jck.com>, Secretariat IETF <ietf-secretariat@ietf.org>, IETF-Discussion list <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>, Lixia Zhang <lixia@cs.ucla.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 05:39:03 -0000

At 12:05 PM +0700 8/25/11, Glen Zorn wrote:

>   Most
>  people seem to want to be able to commute to sessions by (at most)
>  walking across the street, more preferably via elevator.  A large
>  conveniently located bar is very popular, as well.

These are factors which help contribute to a successful meeting by 
making it easier to bump into people.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Peace:  In international affairs, a period of cheating between two
periods of fighting.

From glenzorn@gmail.com  Wed Aug 24 22:41:59 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 899B521F86AF for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 22:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEyf4f7bMM4s for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 22:41:58 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id CC69D21F8634 for <ietf@ietf.org>; Wed, 24 Aug 2011 22:41:58 -0700 (PDT)
Received: by yxj17 with SMTP id 17so1716479yxj.31 for <ietf@ietf.org>; Wed, 24 Aug 2011 22:43:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=iBffiZASzaVbWoM8B9IKzDlxMO6j5FS0yUHsx1ySfgg=; b=cbM1Kumz5VjYE4wHZvWzdI1vBSZDuhlT2+PDKyWQeLNySUgQPxtPix7Ps992fPzull HBX/izHGrUw2C59oWPFNprDyptdcnpGWdlz9AOks7MjzemdFCgpV0i31Vlwru2rTwvVP 0GmBy5Zo4mnr5aCcNddcQJ5jzQwX/1oA2Q8U0=
Received: by 10.91.6.11 with SMTP id j11mr5819502agi.49.1314250989301; Wed, 24 Aug 2011 22:43:09 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-120-20-200.revip2.asianet.co.th [124.120.20.200]) by mx.google.com with ESMTPS id d7sm252364anb.40.2011.08.24.22.43.07 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 22:43:08 -0700 (PDT)
Message-ID: <4E55E0E8.3000601@gmail.com>
Date: Thu, 25 Aug 2011 12:43:04 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IAOC, travel and hotel prices (was RE: Hyatt Taipei cancellation policy?)
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com> <4E55D81B.9000505@gmail.com> <4E55D94F.9020307@gmail.com>
In-Reply-To: <4E55D94F.9020307@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 05:41:59 -0000

On 8/25/2011 12:10 PM, Melinda Shore wrote:

> On 8/24/11 9:05 PM, Glen Zorn wrote:
>> I think that a large part of the problem is that the IAOC is attempting
>> to satisfy policies based upon consensus.
> 
> Really?  Consensus of whom?  I haven't seen anything remotely
> like consensus on much to do with meeting logistics.  Closest
> we seem to have come is a couple of surveys, which apparently
> were treated something like votes by the people who worry
> about such things.

Hmm.  What is this thread (& the many on essentially the same topic that
have preceded it)?  If I had to call consensus on it, I would
characterize it as "one roof, easy to get to, convenient for
socializing" (that, interestingly, often from those who claim to "only
go to work").  All of those things add up to big hotel in big city,
which is always expensive.

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


From henk.uijterwaal@gmail.com  Wed Aug 24 23:12:52 2011
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2728821F8AF4 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 23:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.486
X-Spam-Level: 
X-Spam-Status: No, score=-3.486 tagged_above=-999 required=5 tests=[AWL=0.113,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-r1NZsh0HT9 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 23:12:51 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id CC95B21F8AED for <ietf@ietf.org>; Wed, 24 Aug 2011 23:12:50 -0700 (PDT)
Received: by ewy19 with SMTP id 19so835472ewy.31 for <ietf@ietf.org>; Wed, 24 Aug 2011 23:14:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=19JW8uh/XNFdZTuJiTlaKNs1Q1Yr94S5qrajmdiX+64=; b=ksA9p6RXaXlq/2FkDelKNInq2wmOfO58NrC1uUPJIytx9kTlD3ZCNXjfKjnyvrGfzH WDXe0eMjSHB2+ArKxGTDFgfjBrO0E2BP4yEEG+dezm69UdCPRJD7FsY5ylKOEdAiMFpG zIvZgbORLlt9/fTqgu4J/YW2aUmIiNF4OYZww=
Received: by 10.213.16.69 with SMTP id n5mr219262eba.55.1314252842117; Wed, 24 Aug 2011 23:14:02 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) by mx.google.com with ESMTPS id x56sm155576eea.34.2011.08.24.23.14.00 (version=SSLv3 cipher=OTHER); Wed, 24 Aug 2011 23:14:01 -0700 (PDT)
Message-ID: <4E55E827.4060802@gmail.com>
Date: Thu, 25 Aug 2011 08:13:59 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>
In-Reply-To: <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 06:12:52 -0000

On 24/08/2011 23:12, Keith Moore wrote:
> Maybe there needs to be some sort of voting system for future venues.

First of all, remember that the community asked for venue selections
2 to 3 years in advance.  I don't think that many people can predict
if they will attend a meeting 2 years from now.

This proposal would require that the secretariat works out 3-4 proposals
for meeting locations in great detail.   That is a lot more work than
the current approach: start with a few locations, discard options as
one goes along.  More work means more costs and thus higher meeting fees.

Do we really want to increase fees just to have more options?


> You'd be eligible to vote if you'd attended an IETF anytime within the past,
> say, 2 years - or if you were willing to commit to attending the one you vote on
> if it wins.  (say by putting down a deposit toward meeting fees).
> 
> Instead of picking one venue, the committee would solicit bids from N (say 3-4)
> different venues within a geographic region.    The bids would include:
> 
>   * room cost per night in the conference hotel
>   * room cost per night in each of some small number of alternate hotels
>   * locations of said hotels and nature of transportation between there and the
>     conference venue
>   * meeting fee for the entire week if that venue is chosen
>   * other pertinent information (like what kind of food is nearby, what kind of
>     facilities there are in or near the venue for impromptu gathering, what
>     kinds of sightseeing opportunities there are, etc.)

Looking at past discussions on the mailing lists, this list will be a lot longer.


> That way, everyone could figure his own travel costs, factor in his own
> willingness to stay further away for less cost, etc.

Not true: it is not possible (nor sensible) to buy plane tickets 2 years
in advance and a lot of things can change in between.


Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From dougb@dougbarton.us  Thu Aug 25 01:51:27 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEC7421F89CC for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 01:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=-0.930,  BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wk4EOWnapLQ for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 01:51:27 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7CC21F87FC for <ietf@ietf.org>; Thu, 25 Aug 2011 01:51:26 -0700 (PDT)
Received: (qmail 25403 invoked by uid 399); 25 Aug 2011 08:52:36 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Aug 2011 08:52:36 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4E560D53.9040804@dougbarton.us>
Date: Thu, 25 Aug 2011 01:52:35 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie>
In-Reply-To: <4E5574AA.3030705@cs.tcd.ie>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 08:51:28 -0000

Including only the hotel costs may (I haven't crunched the numbers) be
providing a very distorted view of the situation. In order to get the
whole picture you have to include the meeting fees and air fare, at
minimum.


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 sm@resistor.net  Thu Aug 25 02:10:13 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D5D021F8B08; Thu, 25 Aug 2011 02:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t0cKGxTrrvdh; Thu, 25 Aug 2011 02:10:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC8321F8B00; Thu, 25 Aug 2011 02:10:10 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7P9BH9M013006; Thu, 25 Aug 2011 02:11:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1314263482; bh=3d+Nnsvx6nCF6LwnhxQ/tu0WEbOddiITTfRgdbZs1uk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=MumcH9zWRzWgxJftDj22aalwliljey9WcfNLTx98+m83gRtMYUmq5U2tQXhHLBZGq IssmvzPZrg9sYo9pB6DgYnyZ1tEmDHqoG3y11ZKfQaGzgya2na/CjIIHVbU95f/yn1 jFBl5Wc8M7aZVsy3w7LRBEFFNhBEfulq4qNy67dw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1314263482; bh=3d+Nnsvx6nCF6LwnhxQ/tu0WEbOddiITTfRgdbZs1uk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=wOuJhdd1gFz0W4fKLW/8m4r6zi4Cc66LNdmkj4hoiNHTowiYR/p4k53uZHEY9Un1Z qUDyJFjJ2ea/qOKFl1+nQ2UfGtEra8SJcubvDU7siinoJcbCJLDM0wuuHowaZ2nYpa kpCEMscP8xuW8lQqq0cE0Ix60oQsPjRUd59tafXw=
Message-Id: <6.2.5.6.2.20110824233526.0bc439a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 25 Aug 2011 02:08:06 -0700
To: iaoc@ietf.org
From: SM <sm@resistor.net>
Subject: Re: IAOC, travel and hotel prices
In-Reply-To: <p06240611ca7b0f76e68f@[172.16.1.69]>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D557960@PRVPEXVS04.corp.twcable.com> <6.2.5.6.2.20110824075034.06819068@resistor.net> <p06240611ca7b0f76e68f@[172.16.1.69]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 09:10:13 -0000

Dear IETF Administrative Oversight Committee,

I hope that the questions below are in full compliance with BCP 
101.  If not, please feel free to ignore them.

A few years back, the IAOC posted the following information:

Venue I advantages include:

*  Rooms and meeting space under one roof
*  Many direct North American and International flights
*  Well known location for an IETF meeting

Venue II advantages include:

*  Broader range of hotel guest room rates and less expensive
*  A new location, adjacent to a European-like historic district with 
numerous restaurants
*  Convention center a short walk from main hotels (several within a 
5 minute walk)

(a) Can the IAOC provide a list of advantages and disadvantages for 
venue selection?

(b) Has the IAOC published (redacted) hotel contracts in the past?

(c) Can the IAOC publish (redacted) hotel contracts for past venues?

(d) Can the IAOC publish the list of members on the venue selection committee?

(e) Has the IAOC ever held asked IETF participants to vote on the 
selection of a venue?

(f) If the answer to (e) is yes, can the IAOC specify the voting 
system criteria?

(g) Where can I find the policy or guideline for setting meeting 
dates five years in advanced?

(h) Where can I find the policy or guideline for venue selection 
three years in advance?

(i) Can the IAOC provide a list of confidential and non-confidential 
agreements it has entered into since the year 2010?

(j) Has the IAOC taken any procedural variant decision?

(k) What guidelines have been developed for regular operational 
decision making?

Regards,
-sm

P.S. My opinion about the topic of travel and hotel prices is as 
follows: "the church is near, but the way is icy, the tavern is far, 
but I will walk carefully".


From glenzorn@gmail.com  Thu Aug 25 02:35:29 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE63621F8829 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 02:35:29 -0700 (PDT)
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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5brV33YDp1Xh for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 02:35:29 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5964721F8834 for <ietf@ietf.org>; Thu, 25 Aug 2011 02:35:29 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1879994gwb.31 for <ietf@ietf.org>; Thu, 25 Aug 2011 02:36:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=NTqJ33mF4vhP4swTZVoef8Q/90Q3r7O5fgajQQOQrYM=; b=spfWMrs7UBafF+toC5zBQpke5N1Z5ysLx/no2AzhoddX3F6jHYN1+3u+ZMXWrlyU9s xde8Fgh/DTCNaDCvnoJqu7W38fVP1AgOrtv170EeC9iCdvxvEeGNUENRMXZdvI9VkCsf 6ccSngCTDldowPlZ2HoBNZjQw/M1qIx4H8FkE=
Received: by 10.101.177.17 with SMTP id e17mr6060621anp.164.1314265000462; Thu, 25 Aug 2011 02:36:40 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-122-65-112.revip2.asianet.co.th [124.122.65.112]) by mx.google.com with ESMTPS id p34sm387938ann.17.2011.08.25.02.36.37 (version=SSLv3 cipher=OTHER); Thu, 25 Aug 2011 02:36:39 -0700 (PDT)
Message-ID: <4E5617A1.407@gmail.com>
Date: Thu, 25 Aug 2011 16:36:33 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <4E560D53.9040804@dougbarton.us>
In-Reply-To: <4E560D53.9040804@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 09:35:30 -0000

On 8/25/2011 3:52 PM, Doug Barton wrote:

> Including only the hotel costs may (I haven't crunched the numbers) be
> providing a very distorted view of the situation. In order to get the
> whole picture you have to include the meeting fees and air fare, at
> minimum.

As I believe has been mentioned, hotel costs and meeting fees are
intimately related.  Air fares, of course, vary with locations, both
that of the meeting and of the individual participant.  For example, if
I booked a round-trip to Taipei today, I could pay ~$300 but I had to
search rather desperately to find a flight to QC for less than $2000
(both coach fares).  That is one salutary effect of the current
scheduling scheme, IMHO: it seems to spread the pain of airfare around a
little bit...

From dougb@dougbarton.us  Thu Aug 25 02:46:51 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CEF521F8560 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 02:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Level: 
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqt4X2ajzgJZ for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 02:46:50 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 63EB621F855D for <ietf@ietf.org>; Thu, 25 Aug 2011 02:46:50 -0700 (PDT)
Received: (qmail 29269 invoked by uid 399); 25 Aug 2011 09:47:58 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Aug 2011 09:47:58 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4E561A4E.40007@dougbarton.us>
Date: Thu, 25 Aug 2011 02:47:58 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0
MIME-Version: 1.0
To: Glen Zorn <glenzorn@gmail.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <4E560D53.9040804@dougbarton.us> <4E5617A1.407@gmail.com>
In-Reply-To: <4E5617A1.407@gmail.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 09:46:51 -0000

On 08/25/2011 02:36, Glen Zorn wrote:
> On 8/25/2011 3:52 PM, Doug Barton wrote:
> 
>> Including only the hotel costs may (I haven't crunched the numbers) be
>> providing a very distorted view of the situation. In order to get the
>> whole picture you have to include the meeting fees and air fare, at
>> minimum.
> 
> As I believe has been mentioned, hotel costs and meeting fees are
> intimately related. 

Right, that was sort of my point. :)

> Air fares, of course, vary with locations

Also true, however if we're going to use "charts and graphs" to provide
a metric of the effectiveness of the IAOC in this area it's important to
take the whole picture into account.

And while the regional rotation does spread the pain in a general way,
there is a discussion point in regards to "boutique" venues vs. more
pedestrian ones, and air fare is relevant to this issue as well.

Note, I left out "cost of food" from my minimal data set since there are
2 independent variables inherent in that which (I believe probably)
cancel this factor out over a reasonably long survey period. Individual
taste (which can vary pretty widely) and the fact that local costs
really are going to average out over time. But if someone wanted to make
an argument that this should be included with the other 3 factors I
would be quite easily persuaded.

Meanwhile, count me in the "more or less willing to believe that the
IAOC is making the best of a difficult task + glad it's not me"
category. I've both been responsible for and assisted with conference
planning and execution for groups both larger and smaller than the IETF,
and it's an unbelievably difficult job. And to top it off, like so many
other things in both life and business the better job you do this time
the higher the expectations are next time.


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 bortzmeyer@nic.fr  Thu Aug 25 03:22:50 2011
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65BCB21F855A for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 03:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.949
X-Spam-Level: 
X-Spam-Status: No, score=-108.949 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NsaU9A7Rlba7 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 03:22:49 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by ietfa.amsl.com (Postfix) with ESMTP id 4C19821F8559 for <ietf@ietf.org>; Thu, 25 Aug 2011 03:22:49 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 80FAF1C0895 for <ietf@ietf.org>; Thu, 25 Aug 2011 12:24:01 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 7C2D31C088A for <ietf@ietf.org>; Thu, 25 Aug 2011 12:24:01 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.6.69]) by relay2.nic.fr (Postfix) with ESMTP id 7A44C7B0090 for <ietf@ietf.org>; Thu, 25 Aug 2011 12:24:01 +0200 (CEST)
Date: Thu, 25 Aug 2011 12:24:01 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Questionnaire to survey opinion concerning a possible redefinition of UTC
Message-ID: <20110825102401.GA10559@nic.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs"
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 6.0.2
X-Kernel: Linux 2.6.32-5-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 10:22:50 -0000

--82I3+IH0IqGh5yIs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Since several RFCs rely on UTC and leap seconds (3339, 4765, 5905,
etc), this questionnaire may be of interest for some persons [the Web
page mentions two articles, if you are in a hurry, the first one is
the PRO and the second one the CON]. One more week to comment.

http://hpiers.obspm.fr/eop-pc/index.php?index=questionnaire


QUESTIONNAIRE TO SURVEY OPINION CONCERNING A POSSIBLE REDEFINITION OF UTC

Universal Time, the conventional measure of Earth rotation is the traditional basis for civil timekeeping. Clocks worldwide are synchronized via Coordinated Universal Time (UTC), an atomic time scale recommended by the Radiocommunications Sector of the International Telecommunications Union (ITU-R) and calculated by the Bureau International des Poids et Mesures (BIPM) on the basis of atomic clock data from around the world.

UTC is computed from TAI by the introduction of leap seconds such that UTC is maintained within 1 second of UT1. Since 1972, these leap seconds have been added on December 31 or June 30, at the rate of about one every 18 months. Since 1 January 2009, 0:00 UTC, UTC-TAI= -34s.

After years of discussions within the scientific community, a proposal to fundamentally redefine UTC will come to a conclusive vote in January 2012 at the ITU-R in Geneva. If this proposal is approved, it would be effective five years later. It would halt the intercalary adjustments known as leap seconds that maintain UTC as a form of Universal Time.
Then, UTC would not keep pace with Earth rotation and the value of DUT1 would become unconstrained.Therefore UTC would no longer be directly useful for various technical applications which rely on it being less than 1 second from UT1. Such applications would require a separate access to UT1, such as through the publication of DUT1 by other means.

The objective of the survey is to find out the strength of opinion for maintaining or changing the present system.

Your response is appreciated before 31 August 2011

--82I3+IH0IqGh5yIs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFOViLBQTZHl5fW0kYRAprXAJ9cM9KQTndnCddSuilTAGqb6dMJjACcCVkX
FA+ods6B1GBVtZNJ1AYKl0o=
=YhAA
-----END PGP SIGNATURE-----

--82I3+IH0IqGh5yIs--

From moore@network-heretics.com  Thu Aug 25 04:05:23 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7EE21F85AB for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 04:05:23 -0700 (PDT)
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.139,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqeGKS33azPd for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 04:05:22 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 8285721F85AA for <ietf@ietf.org>; Thu, 25 Aug 2011 04:05:22 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3E9F920544; Thu, 25 Aug 2011 07:06:35 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Thu, 25 Aug 2011 07:06:35 -0400
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=5+Dapoln2fhfTDoLx3SLth3cJck=; b=B8 7UVTpbJ5tP/Ysv4wbQDCPqwJzYcaaY7p+lUrq7kGB620gIp9wzZjwj8P/izRRo9c z4iV6RsCCqKhbWgboyjaKFZR8M2QwKozxSbrXdyTiN03X8FjyRoQcvkVM7LJXO5M CinVZjXj4Tsyas17J2Bh086/zV9l6JUzpfDrM0JS4=
X-Sasl-enc: 3QERQhqL0/qQbPR8L3erR85vgvbGZ3esLE9opofvmJ8U 1314270394
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2A1E69202EA; Thu, 25 Aug 2011 07:06:34 -0400 (EDT)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E55E827.4060802@gmail.com>
Date: Thu, 25 Aug 2011 07:06:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCEDB75B-8237-481A-AB4F-428D861F0D8A@network-heretics.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com>
To: henk@uijterwaal.nl
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 11:05:23 -0000

On Aug 25, 2011, at 2:13 AM, Henk Uijterwaal wrote:

> On 24/08/2011 23:12, Keith Moore wrote:
>> Maybe there needs to be some sort of voting system for future venues.
>=20
> First of all, remember that the community asked for venue selections
> 2 to 3 years in advance.  I don't think that many people can predict
> if they will attend a meeting 2 years from now.
>=20
> This proposal would require that the secretariat works out 3-4 =
proposals
> for meeting locations in great detail.   That is a lot more work than
> the current approach: start with a few locations, discard options as
> one goes along.  More work means more costs and thus higher meeting =
fees.

I don't think it should be (much) more work to let attendees make the =
final choice.  (Though I admit that it's possible that presenting all of =
that information in the best possible light for each venue might end up =
being time consuming.)

But on what basis are the options discarded by IAOC, if the different =
options aren't examined to at least the level of detail that I =
suggested?

> Do we really want to increase fees just to have more options?

Not more options, but more transparency into the selection and more =
assurance that the selection is made on the basis of what people really =
want or don't want.=20

>> You'd be eligible to vote if you'd attended an IETF anytime within =
the past,
>> say, 2 years - or if you were willing to commit to attending the one =
you vote on
>> if it wins.  (say by putting down a deposit toward meeting fees).
>>=20
>> Instead of picking one venue, the committee would solicit bids from N =
(say 3-4)
>> different venues within a geographic region.    The bids would =
include:
>>=20
>>  * room cost per night in the conference hotel
>>  * room cost per night in each of some small number of alternate =
hotels
>>  * locations of said hotels and nature of transportation between =
there and the
>>    conference venue
>>  * meeting fee for the entire week if that venue is chosen
>>  * other pertinent information (like what kind of food is nearby, =
what kind of
>>    facilities there are in or near the venue for impromptu gathering, =
what
>>    kinds of sightseeing opportunities there are, etc.)
>=20
> Looking at past discussions on the mailing lists, this list will be a =
lot longer.

No doubt.

>> That way, everyone could figure his own travel costs, factor in his =
own
>> willingness to stay further away for less cost, etc.
>=20
> Not true: it is not possible (nor sensible) to buy plane tickets 2 =
years
> in advance and a lot of things can change in between.

True.  Though broadly speaking, if it's expensive to fly somewhere =
today, it's unlikely to be cheap to fly there in two years.

(Admittedly, the real gotcha in Quebec seems to have been that there =
were so few seats available that the few low-priced fares were quickly =
exhausted. Everyone could get quotes two years in advance and all see =
the same cheap fares, even if those fares were only available for say 10 =
seats per day.)

Keith


From mcr@sandelman.ca  Thu Aug 25 06:38:53 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A281E21F86B1 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 06:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.462
X-Spam-Level: 
X-Spam-Status: No, score=-1.462 tagged_above=-999 required=5 tests=[AWL=0.492,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0e1yQ1SD1Stp for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 06:38:53 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB3721F862F for <ietf@ietf.org>; Thu, 25 Aug 2011 06:38:52 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id CE9F6342CB; Thu, 25 Aug 2011 09:39:24 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 6E23D98411; Thu, 25 Aug 2011 09:40:26 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <alpine.OSX.2.01.1108241231320.7436@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <alpine.OSX.2.01.1108241231320.7436@sjc-vpn5-137.cisco.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 25 Aug 2011 09:40:26 -0400
Message-ID: <4527.1314279626@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 13:38:53 -0000

>>>>> "Ole" == Ole Jacobsen <ole@cisco.com> writes:
    Ole> * Sticking to our fixed dates, published up to 5 years in
    Ole> advance.

    Ole> I think you will find that the one-roof solution does indeed
    Ole> lead to fairly expensive HQ properties, this is more or less
    Ole> true all over the world and is currently made much worse by the
    Ole> weak dollar. The fixed date restriction (which is good in my
    Ole> view) also contributes to challenges with venue
    Ole> availability. We been told more than once that "if you do it a
    Ole> week later or earlier..."

Given that we are now booking three years in advance (vs 1 year that
occured 5 years ago), perhaps it is time to change our policy to publish
the dates only three years in advance.

We still have the list of conflicts/avoidances to deal with.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From nsb@guppylake.com  Thu Aug 25 06:57:34 2011
Return-Path: <nsb@guppylake.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5FED21F85AB for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 06:57:34 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ep5xrCZQFjob for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 06:57:34 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 42A3421F85A4 for <ietf@ietf.org>; Thu, 25 Aug 2011 06:57:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer; b=VAiQ/rpmPPFTOHhc9ZO2ul/jzAC4t4k8/eEzN+3329o+0I2k/4IGYYTaHy48BDhEuzEO88MXpahr8e7zKCB/OPVc4zQ0AaTTgq9z6ClGcnQDnBvXQ1WLO2WaRzD11v/e;
Received: from 173-98-4-51.pools.spcsdns.net ([173.98.4.51] helo=[192.168.0.194]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1QwaS3-0002e0-6s; Thu, 25 Aug 2011 09:58:45 -0400
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/mixed; boundary=Apple-Mail-135-966062994
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <alpine.OSX.2.01.1108242104570.18070@sjc-vpn5-137.cisco.com>
Date: Thu, 25 Aug 2011 09:58:31 -0400
Message-Id: <EEA7A37D-2ACE-41E4-B308-67E12C1A07DF@guppylake.com>
References: <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <20110825032605.GI53261@shinkuro.com> <alpine.OSX.2.01.1108242104570.18070@sjc-vpn5-137.cisco.com>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 13:57:35 -0000

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

Here's the appreciation of the Yen (there are similar results for other =
strong currencies) since IETF 61, from xe.com:

--Apple-Mail-135-966062994
Content-Disposition: inline;
	filename=PastedGraphic-7.tiff
Content-Type: image/tiff;
	x-unix-mode=0666;
	name="PastedGraphic-7.tiff"
Content-Transfer-Encoding: base64

TU0AKgADMYj7+/v/+vr6//z8/P/7+/v/+/v7//r6+v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//7+/v/7+/v///////n5+f/s7Oz//P36//r69//6
+vf/+vr3//r89P/6/PT/+frz//n68//5+vP/+frz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fL/+vny//r58v/6+fL/+vny//r58v/6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz/+3s5//5+PL/+/r0//n48v/7+vT/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vny//r58v/6+fL/+vny//r58v/6+fL/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//n48v/5+PL/+vnz//r58//6+fP/
+vnz//r59v/6+fb/+/r3//v69//7+vf/+/r3//z7+P/8+/j//Pv4//z7+P/7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+fn5/+/v7//8/Pz//Pz8//v7+//+/v7/+/v7//r6+v/6+vr/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v4//v7+P/8/fr/+/v7//v7/v/7+v///Pv///Xz/P+urbP/+/r///v7/v/8/Pz/+vr6//7+
/v/5+fn//Pz8//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v//Pr7//77/f/7+fr/+/n6//v5+v/Lycr/+vn2//z7+P/6+fb/+vn2//r58//6+fP/+vnz
//r58//6+fP/+vnz//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6
+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//8+/j/+vn2/9fW0//v7uv/+/r3//v69//6+fb/+/r3//r59v/6+fb/+vn2//r59v/6+fb/
+vn2//r59v/6+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fb/+vn2//r59v/6
+fb/+vn2//r59v/6+fb/+vn2//r58//6+fP/+vnz//r58//6+fP/+vnz//r59v/6+fb/+vn2//r5
9v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+vr/+vr6//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6+vr//Pz8//z8/P/6+vr/+/v7//z8/P/6+vr/
9PT0/9TU1P/8/Pz///////v7+//+/v7/+fn5//z8/P/6+vr/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v4//v7+P/9/vf/+/v7
//v7+//7+v///Pv///Xz/P+urbP/+/r///v7/v/8/Pz/+fn5//v7+//5+fn/+/v7//7+/v/7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7/v/7+/7/+/v+//v7/v/7+/7/+/v+//v7/v/7+/7/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//r6+v/6+vr/+vr6//r6+v/6+vf//Pv2//b17//39vH/
9/bx///++P/y8ez////5//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vT/+/r0
//v69P/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vT/+/r0//r58//6+fP/
+vnz//r58//6+fP/+vnz//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+/r3//v69//7
+vf/+/r3//v69//7+vf/+/r3//v69//6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r5
9v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fb///77//Tz8P/6
+fb/+fj1//r59v/19PH//v36//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//5+vP/+frz//n59v/5+fb/+vr3//r69//6+vr/+/v7//v7+//7+/v/+/v+//v7/v/7
+/7/+/v+//v7/v/7+/7/+/v+//v7/v/7+/7/+/v+//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//r6+v//////9/f3//n5
+f/6+vr/+vr6///////5+fn/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+P/8/fr/+/v+//v7/v/7+v///Pv///Xz/P+u
rbP/+/r///v7/v/5+fn/+/v7//n5+f/5+fn///////v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/j/+/v4//v7+P/7+/j/+/v4//v7+P/7+/j/+/v4//n59v/5
+fb/+fn2//n59v/5+fb/+fn2//n68//5+vP/+/r0//n48v/29e//+vnz//r58//8+/b///74//f2
8f/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//5+PX/+fj1//r59v/6+fb/
+vn2//r59v/6+fb/+vn2//v69//6+fb/+vn2//v69//7+vf//Pv4//v69//7+vf/+/r3//v69//7
+vf/+/r3//v69//7+vf/+/r3//v69//7+vf//Pv4//z7+P/8+/j//Pv4//z7+P/8+/j//Pv4//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//8+vv//Pr7//z6+//8+vv//Pr7//z6+//8+vv//Pr7//z6+//8+vv//Pr7//z6+//8+vv/
/Pr7//z6+//8+/j/+/r3//v69//7+vf/+/r3//v69//7+vf/+/r3//v69//6+fb/+vn2//r59v/6
+fb/+vn2//r59v/6+fb/+vn2//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vT/+vnz////+f/8+/b/9/bx//b17//5+PL/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//5+vP/+frz//n6
8//5+vP/+frz//n68//5+vP/+frz//r69//6+vf/+vr3//r69//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8/Pz/+/v7
//r6+v/6+vr/+/v7//v7+//7+/v/+/v7///////6+vr/+vr6//r6+v/7+/v//v7+//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+P/8/fr/+/v+//v7/v/7+v///Pv///Xz/P+urbP/+/r///v7/v/8/Pz/+fn5
//v7+//5+fn/+/v7//7+/v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+P/8+/j//Pv4//z7+P/7+vf/+/r0//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP//Pv2//f28f/6+fP/9vXv//799//KycT/+vnz//n48v/6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r59v/6
+fb/+vn2//r59v/6+fb/+vn2//r59v/6+vr/+vr6//r6+v/6+vr/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//8/Pz//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//8/Pz/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//r69//6+vf/+vr3//r69//6+vf/+vr3//r69//6+vf/+fn2//n59v/5+fb/+fn2//n59v/5+fb/
+fn2//n59v/6+fP//Pv2/9bV0P/w7+n/+vnz//b17//5+PL/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fL/+vny//r58v/6+fL/+vnz//r58//7+vT/
+/r0//r58//6+fP/+vnz//r58//6+fb/+vn2//r59v/6+fb/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6+vr/+vr6//v7+//7+/v//Pz8//r6+v/5
+fn/9vb2/8/Pz//8/Pz/+/v7//b29v//////+/v7//7+/v/5+fn/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+P/8/fr/
+/v+//v7/v/7+v///Pv///Xz/P+urbP/+/r///v7/v/5+fn/+vr6//7+/v/6+vr//Pz8//r6+v/7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v4//v7+P/7+/j/+/v4//r69//6+vf/+vz0//r89P/6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vny//r58v/6+fL/+vny//r58v/6+fL/9/bx//n49f/+
/fr/+/r3//f28//Z19X/9/bz//z7+P/7+vf/+vn2//r59v/6+fb/+vn2//r59v/5+PX/+fj1//n5
+f/5+fn/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v/
/Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+P/7+/j/+vr3/+Dg
3f/v7+z/9vbz//v7+P/5+fb/+vr3//n59v/5+fb/+fn2//n59v/5+fb/+fn2//n59v/5+fb/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vf/+/r3//v69//7+vf/+/r3//z7+P/8+vv//Pr7
//z6+//8+vv//Pr7//z6+//8+vv//Pr7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+vr6//r6+v/7+/v//Pz8//v7+//6+vr/+fn5/9/f3//5+fn/+vr6
//z8/P//////+vr6//z8/P/6+vr/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+P/8/fr/+/v+//v7/v/7+v///Pv///Xz
/P+urbP/+/r///v7/v/7+/v//Pz8//z8/P/7+/v/+/v7//r6+v/7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7/v/7+/7/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr3//r69//6
+vf/+vr3//n68//5+vP/+frz//n68//6+fb/+vn2//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58v/6+fP/+/r3//n49f/8+/j/+/r3//n49f/6+fb/+/r3
//r59v/6+fb/+vn2//r59v/7+vf/+/r3//z7+P/8+/j//Pv4//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//z8/P/8/Pz/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8/fr/+/v4//n59v/7+/j//P36//7++//8/fr/
+fn2//r69//6+vf/+vr3//n59v/5+fb/+fn2//n59v/5+fb/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fb/+vn2
//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r59v/6+fb/+vn2//r59v/7+fr/+/n6//v5+v/8+vv//Pr7//z6+//8
+v7//Pr+//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+P/8/fr/+/v+//v7/v/7+v///Pv///Xz/P+urbP/+/r///v7/v/7+/v/
+vr6///////39/f/+/v7//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vv+//r7/v/7
+/7/+/v+//v7/v/7+/7/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//z6
+//8+vv//Pr7//v5+v/7+vf/+/r3//v69//6+fb/+vn2//r59v/6+fP/+vnz//r58//6+fP/+vnz
//r58//7+vf/+/r3//v69//6+fb/+vn2//r59v/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+fn2//f39//6+vr/9/f3//f39//Ozs7/+fn5//7+/v/7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//8/Pz//Pz8/9XV1f/s7Oz/+/v7//v7+//5+fn//v7+//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v//Pv4//v69//7+vf/+/r3//v69//6+fb/+vn2//r59v/6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r59v/6+fP/+/r3//v69//8+/j//v36//v7+//7+/7/+vr9
//r6/f/6+v3/+/v+//v7+//8/Pz/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+v37//r9+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v//Pz8//z8/P/6+vr/+/v7//z8
/P/6+vr/9PT0/9PT0//8/Pz/+fn5//z8/P/+/v7/+vr6//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+v37//j9+//+
//////b///30//////z/+/v7//Xx+/+wrLj/+/v+//r9+P/8/Pz/+/v7//7+/v/7+/v//Pz8//n5
+f/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v+//v7/v/7+/7/+/v+//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v69//6+fb/+vn2//r59v/6+fb/
+vn2//r59v/6+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r59v/6+fb/+vn2//v69//7+vf/+/r3//v69//8+/j/+vr6//z8
/P/8/Pz/+vr6//n5+f/Jycn/+fn5//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7
+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8/Pz/9vb2
/9nZ2f/q6ur/+/v7///////8/Pz/+vr6//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
/Pr7//z6+//8+/j//Pv4//z7+P/8+/j//Pv4//v69//7+vf/+/r3//v69//6+fb/+vn2//r59v/5
+PX/+fj1//r59v/6+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vny//r58v/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r69//6+vr/+/v7//v7+//8/Pz/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v//Pz8//v7+//7+/v/+/v7//z8/P/6+vr/9/f3/8/Pz//29vb/
///////////39/f/+vr6//v7+//8/Pz/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v4//n89P/5+vP///j+///4///x9///8fv/
/+/1//+trsL//Pr+//z79v/7+/v/+vr6//r6+v/7+/v/+vr6//7+/v/7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/j/+/v4//z7+P/8
+/j/+/r3//v69//7+vf/+/r3//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fL/+vny//r58v/6+fL/+vny//r58v/5+vP/+frz//n68//5+vP/+frz//n68//6+vf/+vr3
//v7+P/7+/j/+/v7//v7+//7+/v/+/v7//v7+//7+/v//Pz8//f39//7+/v//Pz8//7+/v/+/v7/
/v7+//r6+v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6+vr//v7+//7+/v///////Pz8//n5+f/7
+/v//Pz8//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v+//v7/v/7+/7/+/v+//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr3//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fL/+vny//r58v/6+fL/+vny//r58v/6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+/r0//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vf/+/r3//v7+P/7+/j/+/v7//v7+//7+/v/+/v7
//v7/v/7+/7/+/v+//v7/v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7///////+/v7/+fn5//v7+//5+fn///////r6
+v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//7//P/w9fb/8/f//+j1//9ieZz/RVyF/2V5qv+frtX/+/r////59v/5
+fn/9/f3//7+/v/+/v7/+/v7//r6+v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+P/7+/j/+/v4//v7+P/7+vf/+/r3//v69//7+vf/+vn2//r59v/6+fb/+vnz
//r58v/6+fL/+vny//r58v/6+fL/+vny//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//n48v/5+vP/+vz0//r89P/6/PT/+/v4//v7+P/7+/j/+/v4//v7+//7+/v/+/v7//v7+//7
+/7/+/v+//v7/v/7+/7//v7+//n5+f/8/Pz/+/v7//v7+//09PT//Pz8//7+/v/7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//6+vr///////X19f/7+/v//v7+//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v+//v7/v/7+/7/+/v+//v7/v/7+/7/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//z7+P/8+/j//Pv4//z7+P/7+vT/+/r0//v69P/6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r59v/6+fb/+vr3//r69//6+vr/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v//Pz8//z8/P/6+vr/+vr6
//v7+//7+/v/+vr6//T09P/8/Pz/+fn5//v7+//6+vr//v7+//r6+v/8/Pz/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vv///r+
///Q2fT/EyA+/zdPf/8HG0n/GjJk/xAhUP9xgKv/9vv///z7+P/6+vr/9vb2//z8/P/6+vr/////
//r6+v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v4//v7+P/7+/j/+/v4//z7+P/7+vf/
+/r3//r59v/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+fj1//n49f/6+fb/+vn2//v69//7+vf//Pv4//z7+P/7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/////
//z8/P/39/f/+fn5///////Nzc3///////z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7
+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//5+fn/
/////9zc3P/09PT///////r6+v/5+fn//Pz8//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v4//v7
+P/7+/j/+/v4//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//r6+v/6+vf/+vr3
//n59v/5+fb/+fn2//n59v/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vn2//r59v/6+fb/+/r3//r69//6+vf/+/v4//v7+P/7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v//Pz8//z8/P/6+vr/9fX1/9bW1v//
////+fn5//n5+f/7+/v//v7+//7+/v/39/f/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vv///j7///R3///DiNW/wAYTf85VIH/
4f7//+Tu//+kqMP/+Pv///r9+//+/v7/+vr6//n5+f/8/Pz/+vr6//7+/v/7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v4//v7+P/7+vf/+vn2//n49f/5+PX/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r59v/6+fb//Pv4
//z7+P/8+/j//Pv4//z6+//8+vv//Pr7//z6+//6+v3/+vr9//v7/v/7+/7/+/v+//v7/v/7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v///////f39//6+vr/+vr6///////0
9PT///////v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6+vr/+vr6//v7+//+/v7//v7+//n5
+f/6+vr//Pz8//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+P/7+/j/+/v4//v7+P/7+/j/+/v7//v7+//7+/7/
+/v+//v7/v/7+/v/+/v7//r6+v/6+vr/+/v7//v7+//7+/v/+/v7//r6+v/6+vr/+vr6//r6+v/6
+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r59v/6+fb/+vn2//r59v/6+fb/+vn2//r58//6+fP/+/r0//r58//6+fP/
+vnz//n68//5+vP/+vz0//r89P/7+/j/+/v4//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//6+vr//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+vr6//v7+//8/Pz/+vr6//r6+v/39/f/////
//n5+f/5+fn/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/7/+/v+//v7+//7+/v/+/v4//v7+P/7+/v//Pr7//z6/v/8+v7/+v37//r9+//7+/v/
/Pr7//v7+//7+/v/+/v7//v7+//7+/v/+/v4//v7+P/7+/j/+/v7//r9+//7+/v/+/v4//v7+P/7
+/j/+/v4//v7+//7+/v/+vv+/+Hn7/9icY3/Bx1Q/wohVv89Um3/6fX///Ds+/+1rLf/+/r///r9
+//5+fn/+/v7///////6+vr/+fn5//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/7/+/v+//v7
/v/7+/7/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v4//v7+P/7+/j/+/v4//r69//6+vf//Pjz
//z48//8+PP//Pjz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//n59v/6+vf/+vr3//r69//6+vf/+vr3//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v//Pz8//n5+f/6+vr//Pz8//r6+v///////Pz8//r6+v/7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//6+vr//v7+//v7+///////+/v7//n5+f/8/Pz/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/j/+/v4//v7+P/6+vf/+/r3
//r59v/6+fb/+vn2//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+/r0//v69P/7+vT//Pv4//z7+P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+vr6///////+/v7/+fn5//v7+//+/v7/+vr6//r6+v/+/v7/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7/v/8+v//+/r///v7/v/6
/fj/+P71//r99v/7+/j///j+///0///78P//9f////T////+/P////z///79+v/5+fb//Pr///z6
///8+/j/+/32//v99P/6/fb/+vv+//r7///5+v//+/z///z9+v/+//j//v/4//f49f/29fL/9fj/
/9Th//9DV37/gqLc/w8gRv9zg5//7vX///Tz//+nprD/+/v+//r9+//8/Pz/+fn5//v7+//6+vr/
/v7+//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/7/+/v+//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+P/7+/j/+/v4//r69//7+vf/+/r3//r59v/6+fb//Pjz//z48//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//v69P/7+vT/+/r0//v7+P/7+/j/+/v4//v7
+P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+vr6//7+/v/6+vr//Pz8//v7+//FxcX/+vr6//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6
//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8
/Pz/+fn5/9nZ2f/s7Oz/+vr6//7+/v/7+/v/+fn5//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//8/fr//P36//v7+P/7+/j/+/v4//v7+P/8+/j/+/r3//v69//7
+vf/+/r0//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+/r3//v69//7+fr//Pr7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//z8/P/6+vr/9fX1/8/P
z//5+fn//v7+//n5+f/8/Pz/+/v7//z8/P/39/f/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7/v/8+v///Pr///v7/v/6/fv/+v34//r9+P/7+/v//Pr+
//zz/////P//c4GR/z5MWv/z9///+vv///r7/v/8/v//+vv+//r7/v/7+/j/+/v4//v7+P/7+/7/
/Pr///z4///79///+/f///f2/f///////v/4//T27//3+P7/5+7//21zn/9qeqr/xef//xcqQP/l
9///8Pf//+7t//+qqLb/+/v7//r99v/5+fn/+vr6///////6+vr//v7+//f39//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//8/Pz//Pz8//v7+//6+vr/+vr6//v7+//7+/j/+/v4//r59v/6+fb/+vn2//r5
9v/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vn2//r59v/6+fb/+vn2
//n59v/6+vf/+vr3//v7+P/7+/j/+/v4//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7/v/7+/7/+/v+//v7/v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+fn5//z8/P///////Pz8//f3
9//T09P/9/f3//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7/9ra2v/t7e3/+/v7
///////7+/v/+vr6//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+P/7+/j//Pv4//v69//7+vf/+vn2
//r59v/6+fb/+/r0//v69P/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fb/+vn2//v6
9//7+vf//Pv4//z7+P/7+/v/+/v7//v7+//6+vr/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+vr6//r6+v/7+/v//Pz8//z8/P/6+vr/9vb2/9TU1P/6+vr//Pz8//7+/v/+/v7/
9fX1//7+/v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/7/+/v+//v7+//7+/v/+/v4//v7+P/6+/7/+/v+//r4///4/P//bn6h/zJCX/+9
x97/+Pz///v////z9/n/+f/5//X89v/5+/f//v////76///79////vn6//759P///vj/+fjx//r8
8P/1+ez/+v/z//L9+//b4f//ODxe/zI3Uf+8y/H/mK7m/xckSP/l8v//8ff//+vp8f+zsLT/+/v7
//r9+//6+vr//v7+//z8/P/8/Pz/+fn5//n5+f/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6+vr/+/v7
//v7+//7+/v/+/v7//r6+v/7+vf/+vn2//r59v/6+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//v69P/7+vT/+/r3//v69//7+/j/+/v4//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/7/+/v+//v7
/v/7+/7/+/v+//v7/v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+vr6//n5+f////////////X19f/7+/v/9vb2//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//8/Pz/9vb2//r6+v/5+fn/+/v7///////8/Pz/+fn5//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8+vv//Pr7//z7+P/8+/j/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//8+PP//Pjz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+/r3//v69//7+fr/
/Pr7//z6+//8+vv/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v//Pz8//n5+f/29vb////////////7+/v/+fn5//r6+v/+/v7/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/7/+/v+//v7
+//7+/v/+/v7//v7+//7+/7/+v37//r9+//w+v//bH+t/yw9Z//Czuf/9vz///X6/v/6/fv/+Pr5
//z8/P/8/Pz/+/v+//78///7+v//+frz//r+9P/+////8PX5//j+///4////8v/1/+r7///O2P//
JitQ/+Xs/f/m7///na3e/xkjRv/2////8PH0/+vo6v+xr7D/+/r///r7///8/Pz/+/v7//z8/P/6
+vr//v7+//n5+f/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//r6+v/6+vr/+vn2//r59v/6
+fb/+vn2//r59v/6+fb/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vT/+/r0//v6
9P/8+/b/+/v4//v7+P/7+/j/+/v4//v7+//7+/v/+/v7//v7+//7+/7/+/v+//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v+//v7/v/7+/7/+/v+//v7/v/7+/7/+/v+//v7/v/7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//z8/P/+/v7/+/v7//z8/P/U1NT/+/v7//r6+v/7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/9vb2/+Dg4P/y8vL//Pz8///////6+vr/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//6+/7/+vv+//v7/v/7+/7/+/v+//v7/v/7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/j//Pv4//v69P/7+vT/+/r0//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//8+PP//Pjz//z48//8
+PP//Pjz//z48//6+fL/+vny//r58//6+fP/+vn2//r59v/69/n/+/n6//v5+v/7+fr/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//r6+v/7+/v//Pz8//v7+//6+vr/+fn5
/9ra2v/39/f//v7+//7+/v/8/Pz/+fn5//7+/v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6/fv/+v37//v7+//8+vv//Pr7//z6+//7+/v/
+v37//n79//y/v//aHux/yEvXv+Worz/9Pf+//7+///7+fr//ff9//n2+v////z//P36//Hx9P/3
+P7/+/////D2///a4P//T1J+/6Op4v9ASGn/0eLp/+3////E1Pj/LTRQ/+/x///2+v//5ff//9Pn
8f/r8ff///7///Lq/v+uprb/+vv///r7///6/fv/+v37//3//v/5+/r//f/+//j6+f/6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
/v/7+/7/+/v+//r6+v/7+vf/+/r3//r58//6+fP/+vnz//r58//6+fL/+vny//r58//6+fP/+vnz
//r58//5+fb/+fn2//n5+f/6+vr/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+fv6//v+/P/9//7/+v37
//r9+//Jy8r/+Pr5//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+fv6//r9+//6/fv/+/78//v+
/P/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//9//7/+Pr5/9bZ1//q7Ov/
+fv6//7////5+/r/+/78//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+vv+//r7/v/6/fv/+v37//n7+v/5+/r/+vr6//r6+v/5+fb/+fn2//r58//5
+PL/+fjy//n48v/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+frz//r89P/6+vf/+/v4//v7+//7+/v/
+/v7//v7+//7+/7//Pz///r7/v/5+v3/+v37//v+/P/5+/r/9fj2/9HU0v/2+ff/+v37//r9+//9
//7/+Pr5//3//v/4+vn/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+/v7
//v7+//7+/j/+/v4//v7+//7+/v/+vv+//r7/v/4/P//+Pz///j8///4/P7/+/v7//v7+P/8+/j/
//r2///+9//v9fv/ssjq/xgqSP+Ck63/4Oz9//v+///7+v//+fz0//X37v///vz//Pf5//z8///2
9/r/+vv+//b3+v/+/fr/+fn2//v++v/4/fv/9vz///n+///6/PT///77///8///v9v//Zn+2/xwx
Wv+Lm7D/+f////r3/P/8+/j/+//4//P8///U1/r/WV+K/y49Y/+30fj/5vb//+X3//9nf5z/V3Sd
/ypFd/8TKlv/MUp+/2F4q/+Vqtn/Qk9p/+z1/f/w9fT/8PX5//H2+v/x8vj/8vP5/+3t+/+trLf/
+vv+//r9+//4+vn/+fv6//v+/P/7/vz/+/78//n7+v/6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6+vr/+vr6//n5+f/6+fb/
+vn2//r58//6+fP/+vnz//r58//6+fP/+/r0//r58//6+fP/+fn2//r69//7+/j/+/v4//v7+//7
+/v/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+/78//j6+f/9//7/+/78//n7+v/6/fv/+/78//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+fv6//r9+//6/fv/+/78//v+/P/6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//7/vz/+/78//r9+//7/vz/+v37//r9+//6/fv/+/78//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//v7+//7+/v/+/v7//v7+//7+/j/+/v4//v69//7+vf/+vn2//r59v/6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+frz//n68//5+fb/+fn2//r69//6+vf/+/v7//v7+//7+/v/+vr6//r6
+v/7+/v/+/78//r9+//6/fv/+v37//v+/P/6/fv/+fv6//r9+//6/fv/+v37//r9+//5+/r/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+/v7//v7+//7+/v/9Pz//9Pl//88Tnv/DBlC/05j
m/8mNmj/XG2V/9Td7P/39/f//v36//v7+P/4/P//8fr///P6//92gZf/PlBo/4qhs//y////7PTx
//T+///1////+v////v////19fX//P36//X48//t+f//bIKp/xUoUP8uPWr/iZi+//P////s9O7/
9vXy/+Lm8P9tfZ7/QFZ8/8To//+Ep9X/DiFZ/w0aVf8kLFn/ytH6/+zz///r9v//5PT8/8LS4f9i
cIn/ucfe/+/1+//z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//6+vr/+vr6////
///5+fn/+/v7//r6+v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8
/Pz/+/v7//v7+//6+vf/+fn2//r59v/6+fb/+vn2//v69//6+fb/+vnz//r59v/6+fb/+vn2//r5
9v/5+fb/+fn2//v7+P/7+/j/+/v4//v7+P/7+/j/+/v4//v7+P/7+/j/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v//Pz8//v7+//+/v7/+/v7//z8/P/R0dH/+vr6//7+/v/7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//6+vr//Pz8/9/f3//v7+//+/v7///////39/f///////v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//r6+v/5+fn/+fn2//r58//6+fP/+vnz//n48v/5
+PL/+fjy//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//n59v/5+fb/+fn2//n59v/6+vf/+/v4//v7+//7+/v/+/v7//v7+//6+vr/
9/f3/9fX1//6+vr/+fn5//7+/v/6+vr/+vr6///////6+vr/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v4//v7+P/6/fv/+v37//j8/v/4/P7/+v37//r9+/////z/9vXv
//z7+P//////9fb8//v////6////6/r//zBAZP+iu+3/qbza/8XY8f97kbD/dIai/83X5P/+////
//v////4/v/+////8Pr9//T///9CT2z/DRtF/2d+q//z////9fr+//b+//93faD/cXuU/+/////W
5/b/a3uN/2l8m/+RqdT/WW+d/2yCt/+gtO//PUlr//H8///4/v//7/b//5Gbu/8iMFL/hZ3F/9nu
//+Po7b/MEVq/x4vVP/m9v//7PX///D19v/z9fT/8vT2//Lz+f/y8/v/8vP5//P19P/z9fT/8vP5
//T1+v/x8vj/8vP5/+3t+/+trLf/+/v+//v7+//+/v7/+/v7//z8/P/6+vr//Pz8//r6+v/7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr3//r69//6+fb/+vn2
//r59v/6+fb/+vnz//r58//6+fP/+vnz//r59v/6+fb/+fn2//r69//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+P/7+/j/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+fn5//z8/P//////
/Pz8//v7+//Jycn/+fn5//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8
//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+fn5/9fX1//v
7+///v7+//n5+f/+/v7//Pz8//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v4//v69//7+vT/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vn2//r59v/6+fP/+vnz//r58//6
+fP/+frz//n68//5+fb/+vr3//v7+P/7+/j/+/v7//v7+//5+fv/9vb5/9DQ0P/5+fn/+/v7//v7
+//8/Pz//v7+//n5+f/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
/Pv4//z7+P/7+/v/+vv+//j8///4/P7/+vv+//v7+P/6+fb//vn0//r3+f/6+v3/8PP9//j////t
+///Mz1O/6u6zP/k8///7/X9//H3//+zvsv/WmVz/7/N2v/1////9vr////+///6+///7O///8rW
/f9JWoX/FCZT/26Guv+tv+P/ZHGQ/zE9ZP8uPGf/anyl/7vS+/+50fP/Zn+h/yU7Zv8dMF//ZnOj
/7G/7/+uwOr/Tlx2/8/X5f/2/v//tMbw/zdFb/+Wo9D/3OX//+zy+//w9fn/3uf5/9Ld7v/r+Pr/
7fj2//Dz/f/y8v//9e////Xv///18vf/9fTx//T08f/z9fT/8vP5//T1+v/x8vj/8vP5/+7s+/+u
rLf/+/v+//v7+//8/Pz/+vr6//r6+v/7+/v/+vr6//7+/v/7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7/v/7+/7/
+/v7//v7+//7+/v/+vr6//r6+v/5+fn/+vn2//r59v/6+fP/+vnz//r58//6+fP/+vnz//r58//5
+vP/+frz//r69//7+/j/+/v7//v7+//7+/v/+vr6//v7+//7+/v/+/v7//v7+//7+/v/+/v7//r9
+P/6/fj/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v///////n5+f/7+/v/+/v7//z8/P/+/v7///////v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vr6//v7+//7+/v//Pz8//z8/P/7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//+/v7//v7+//z8/P/7+/v//Pz8//z8/P/8/Pz/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8/Pz/+/v7//v7+//7+/v/+/v+//v7/v/7+/7/
+/v7//z7+P/8+/b/+/r0//v69P/6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vn2//r59v/6+fP/+vnz//r58//6+fP/+vnz//r58//4+fL/+frz
//n59v/5+fb/+vr6//z8/P/7+/7/+vr9//z8/P/8/Pz/+/v7//z8/P/29vb//Pz8//r6+v/8/Pz/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//8+/j///r5///6+f/8+vv/+vv+//r7
///4/P7/+vv+//v7+P/8+/j///z7///+/////v//9fr//+/5///a7P//LzhR/9bZ7v/w7/v/9fX4
//X18v/u8O//4ez5/zxMcf+itez/4/H//0RKW/+vr77/9fz//7TN6v9LZYv/Ijdp/zBIhf8/WZr/
GjJk/wofQv9jgaj/a4Kw/21/qP+Il73/a3ue/6O55P9fb5D/eX2Z/+3v//+yw+P/V2iC/7jH2f/f
8v//gJq2/1drgv/0+v//8vPw//H48v/1+vn/7efv//Xu9//w9fn/7/b2//T09v/38fn/9/H5//T0
9v/v9vH/7fnu//D28f/z9fT/8vP5//T1+v/y8fj/9PL5/+7s+/+urLf/+/v+//v7+//7+/v//Pz8
//r6+v/6+vr///////7+/v/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz/
/Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8
/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//vv9//79+v/8+/b//Pv2//v6
8//7+vP/+vny//r58v/6+fP/+vnz//r59v/6+fb/+/n6//v5+v/7+/v/+/v7//z8/P/8/Pz//Pz8
//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz/
/Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8
/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8
/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8
//z8/P/8/Pz///////r6+v/6+vr/+/v7///////5+fn///////z8/P/8/Pz//Pz8//z8/P/8/Pz/
/Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8
/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8
/P/8/Pz/+/v7//z8/P/+/v7//v7+//7+/v/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8
//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz/
/Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8
/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8
/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8
//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz/
/Pz8//z8/P/8/Pz///////7+/v/+/v7/+vr6//n5+f/5+fn///////z8/P/8/Pz//Pz8//z8/P/8
/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8
/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8
//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz/
/Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8
/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//77/f/++/3//vv9//77
/f/8+vv//Pr7//z7+P/7+vf/+/r3//v69//7+vT/+/r0//v69P/7+vT//vrz//768//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vT//Pv2//z79v/7+vT/+/r0//z79v/+
/ff//Pv4//v7+///////+vr9//7+///39/f/+/v7///////+/v7//Pz8//z8/P/8/Pz//Pz8//z8
/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/8/Pz//Pz8
//z8/P/8/Pz//Pz8//z8/P/8/Pz//v77//f28///9v////f9//79+v/+//j/9fj2//b3+v/39/f/
/v///+rx//86Rlv/ma/W/z5Sfv9MXpb/X2qa/97Y+f/78v3/8vT2/+z2+f/q+///pLjT/zlIaf8z
Q2b/tsny/z1Lav+tvuL/6f7//zxMcf+ctOP/YXqj/yQ3Vv9MW3n/tMHX//X4///s8f//bXqe/0JV
fP9Zdp//fZi1/+Hs9v/09PT/9PHz/+zw9//J1+j/eIqg/4WUsv+8ye3/W2aC/6Ouyf/n8v//6fH8
/+/0+P/z9fH/9PTx//X18v/09PT/9PT2//Lz+//y8/v/8vP5//L09v/z9fT/8/Xx//b59f/09vX/
8PH3//Hy+P/x8Pf/7ezz/+vo9/+zsbz/+/v+//v7+///////9/f3//v7+//5+fn/9/f3//z8/P/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//v5+v/7+fr/+/r3//r59v/6+fP/+vnz//n48v/5+PL/+fjy//n48v/5+PL/
+fjy//n49f/6+fb/+vf5//r3+f/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr//Pz8//f39//7
+/v/9/f3///////Ly8v/+vr6//v7+//6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v7+//6+vr/+vr6//r6+v/7+/v/
+/v7//v7+//6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr//v7+/9bW
1v/v7+//+/v7//f39//5+fn//Pz8//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v7+//7+/v/+/v7//v7+P/7+/j/
+vn2//r59v/5+PL/+fjy//n48v/5+PL/+vnz//r58//5+PL/+fjy//n48v/5+PL/+fjy//n48v/5
+PL/+fjy//n48v/5+PL/+fjy//n48v/5+PL/+fjy//n48v/5+PL/+fjy//n48v/5+PL/+fjy//n4
8v/5+PL/+fjy//n48v/5+PL/+vnz//r58//5+PL/+vnz//r58//39vH/9PPt/9HR0f/8/Pz/////
//f39//29vb/+/v7//f39//7+/v/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+/v+//z8///6/fv/+P37//v//P/7////+vr///X0///7////zdfs/2l+tv8VKmL/Vnux/xYv
Uv9OX4b/1eD//+/z///v8PP/7+/v//L09v/1+v7/3+n2/+P1//9PY4n/LEJ3/xAkXP8GGE3/JTps
/z5Qc/+/zuD/5O/r//P57//u8vf/8vb9//r6+v/09fr/8vb//620zv+YpLn/1N/u/+zy9//x8fH/
9vP4//Ty+f/q8v7/qbfM/zA9Xf+HmsT/Tlx2/+b1///r9f//8/f//+/0+P/5+/r/8vPw//f49f/x
9PL/8fL1//Hy+P/x8vj/8fL4//Hy9f/x8vX/8fTy//T28v/4+vn/9vf9//X2/P/09fr/8vP5/+zp
+f+tq7b/+/v+//v7+//+/v7/+fn5//r6+v/5+fn/+/v7//z8/P/7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v69//7
+vf/+vn2//r59v/5+PL/+fjy//n48v/5+PL/+frz//n68//5+fb/+fn2//n5+f/6+vr/+/v7//v7
+//8/Pz//Pz8//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v//Pz8//v7+//5+fn//Pz8//7+/v/q6ur/////
//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//z8/P/7+/v/+/v7//v7+//8/Pz//Pz8//z8/P/7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//+/v7//Pz8//Ly8v/39/f/+/v7//b29v/+/v7/
/Pz8//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+P/7+/j//P36//z9+v/8+/j/+/r3//r5
9v/6+fb/+vn2//v69//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//7+vT/
+vnz//n48v/5+PL/+vnz//v69P/6+fP/9/bx/+vr6P/+/v7/+vr6//v7+//6+vr/+/v7//n5+f/7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6/fv/9vv6//j6+f/5+fv//Pr7
//r88P/+//j/7/X7/7O60P94gqj/MT9u/xswa/8LIlr/UHOr/xYrTf+OoLr/5/L8/+348//v9vP/
7+78//Dt////+///8vH5//D2+v/U4+z/jKCz/7vU9P+lv+b/YnWT/7zL4f/z+///9PH4//n08v/2
9fL/8fPs//H48v/1+vn/7Ovy//Tx+P/28/j/8PPx/+rw9P/0+v//9fb9//Dv+//09///s7/X/zJF
b/9NYo//e4ql//T+///s9f//6/H5//X6/v/x8vX/9PT0//T08f/z9fT/8/X0//D19v/w9fn/8vT2
//L09v/09PT/9PT0//P18f/x9PL/8PH3//T1+v/19vz/8fL4/+vq+f+wsLv/+/v+//v7+//5+/r/
+fv6//n7+v/6/fv/+/78//n7+v/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//n7+v/5+/r/+vr6//r59v/6+fP/+vnz//r58//6+fb/+vn2
//n59v/5+fb/+vr3//r69//6+vr/+/v7//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+/78//j6+f/6/fv/+/78//3//v/5+/r//f/+//j6+f/6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+fv6//r9+//6/fv/+/78//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//7/vz/+/78//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+/78//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//5+v3/+fr9//n6
/f/5+v3/+fr9//n6/f/5+v3/+fr9//r7/v/6+/7/+vv+//r7/v/6+/7/+vv+//r7/v/6+/7/+fv6
//n7+v/5+/r/+fv6//r9+//6/fv/+v37//r9+//7/vz/+/78//r9+//6/fv/+v37//r9+//5+/r/
+fv6//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//5+/r//f/+//n7+v/+////+/78//j6+f/7/vz/+fv6//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+/v7//v7+//7+/v/+/v7//r6+v/6+vr/+fn5//n59v/6+fP/
+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6
+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//39vH//Pv2//z79v/5+PL/9vXv//r5
8//6+fP/9/bx//r58//8+/b/+vn2//n49f/8+/j//v36//v7+P/7+/j/+/v7//v7+//7+/v/+/v7
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+P74//3/+///+v////v///X18v/y/fv/6/3//1JlhP8S
HFH/WWux/83s//9FXn3/Kz1q/2+Arf/U4vP/8v37/+/28f/w9vH/8vP5//Lz+//09Pb/9fL0//X0
7v/19PH/9vP7//Pv/P/z7///9vT///b3/f/w9fT/7vXy/+/28f/w9vH/8PX0/+/28//v9vb/9PL5
//Xy+f/18vT/8/X0/+z2+v/q9fz/7PL7//H1///v9f3/wtDj/0ldhf8rPWL/lKO0/+ry+//v9fv/
8PP7//T1+v/19fj/9PT2//Ly9f/z9fT/8/X0//D19P/w9fT/8vT2//L09v/09Pb/9PT0//P19P/z
9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//5+/r/+fv6//r9+//2+ff//f/+//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+fv6//n7+v/4+vn/+Pr2//r59v/6+fP/+vnz//r58//6+fb/+/r3//r69//6+vf/+/v7//v7+//6
/fv/+v37//r9+//6/fv/+vv+//r7/v/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//7/vz/+fv6//b59//U1tX/+Pr5//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+fv6//r9+//6
/fv/+/78//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//v+/P/7/vz/+/78//v+/P/7/vz/+v37//n7+v/4+vn/9vn3//X49v/1+Pb/9Pb1
//T29f/09vX/9Pb1//T29f/z9fT/8/X0//P19P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8/X0//P19P/0
9vX/9Pb1//T29f/1+Pb/9fj2//b59//2+ff/+Pr5//j6+f/5+/r/+fv6//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//5+/r/+fv6
/9ve3P/u8O//+fv6//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//7+/v/+/v7//v7+//6+vr/+vr6//r69//6+fb/+vnz//r58//6+fP/+vnz//r5
8//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz//r58//6+fP/+vnz
//r58//6+fP/+vnz//r58//7+vT//Pv2//799//7+vT/+fjy//Lx7P///vj/8O/p/9TTzf/39vH/
+vnz//f28f/7+vf/+fj1//z9+v/8/fr/+/v7//v7+//6/fv/+v37//r9+//6/fv/+vv+//r7/v/6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+vr3//7+/v/6////9f///8/j/P9EVnr/a4Cz/yU1Yv8SHkH/hZvA/9Dw//9IYHr/ER5M
/5Ce1f/e5vT/9vbz//Ty+f/09Pb/8/Xx//P17v/z9fH/8vT2//Dz/f/y8v3/8PH3//X19f/29vb/
9PT0//Ly9f/19fj/9PT2//Dx9P/w9fn/8PX2//P18f/09PT/9fL5//Ty+f/y9Pb/8PX0/+348//q
9fT/9vf6/+/w8//z9fT/4Obs/5Sfuv+SoLj/6vX8/+/29v/v9Pj/8fb6//Xz+//y8fj/8vL1//X1
+P/z9fT/8/X0//D19P/w9fT/8vT2//L09v/08vn/8vT2//P19P/w9fT/8PX5//H2+v/x8vj/8vP5
/+3t+/+trLf/+vv+//r9+//5+/r/+fv6//3//v/5+/r//v////b59//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//4
/fv/+P37//j9+//4/fv/+P37//j9+//6/fv/+v37//v7+P/6+vf/+vn2//r58//6+fP/+vnz//r5
9v/6+fb/+vn2//r59v/6+fb/+/r3//v7+//8/Pz/+/v7//v7+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+fv6//v+/P/7/vz/+v37//r9+//Lzsz/
+fv6//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//v+/P/6/fv/+fv6//n7+v/6/fv/+/78//v+/P/7/vz/+/78
//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//4+vn/+Pr5//b59//1+Pb/9Pb1//T29f/z9fT/
8/X0//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//P19P/z9fT/8/X0//P19P/z9fT/8/X0//T29f/09vX/
+fv6//n7+v/6/fv/+v37//r9+//6/fv/+v37//n7+v/6/fv/+fv6/9fa2f/u8O//+v37//7////5
+/r/+fv6//r9+//6/fv/+v37//r9+//6/fv/+v37//v+/P/7/vz/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//7+/7/
+/v7//r99v/6/fb/+P37//j8/v/6/fj/+v34//z9+v/6+vr/+fr///r7///6/fv/+fz0//n68v/7
/fT/+v37//r7/v/6+/7/+vv+//r7/v/6+/7/+vv+//r7/v/6+/7/+vv+//r7/v/6+/7/+vv+//r7
/v/6+/7/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6+vr/+vr3//n59v/5+fb/+fn2//n59v/6+fb/+vn2//r58//6+fP/
+vnz//r58//8+PP//Pjz//z58v/8+fL//vjy//748v/6+fP/+Prz//j68//5+vL//vjv//r59v/h
7PP/naq6/2hug//w9///9vz///j+9f/39Or/+/fq/9LOyv/5+PX/+/r3//v69//8+/j/9vXy//79
+v/6+fb/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+vv+//r7/v/6+/7/+vv+//v7+//7+/v/+/v+
//v7+//6/fv/+v34//j+9f/4/vX/+P74//j8/v/6+///+vv///v7/v/8+vv//Pr+//v7/v/5+v3/
8P///zFDcP8ZK1//EhxI/7zJ+f/n6v//9fj//+n5//+Mmqv/ZG2N/9vh///s7/z/9fb5//Lz+f/y
8/n/8vT2//P19P/y9Pb/8vP5//D1+f/w9fn/8PX2//D19P/w9vH/8PX0//L09v/y8/n/9PL5//Ty
+f/y8/n/8vT2//P19P/z9fT/9PT2//L09v/y9Pb/8vT2//L09v/z9fT/8vT2//P19P/z9fT/8vT2
//Dz+//w8/v/8PX2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//6
/fv/+/78//r9+//7/vz/+fv6//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//4/fv/+P37//j9+//4/fv/+v37
//r9+//6/fv/+fv6//r69//6+vf/+vnz//r58//8+PP//Pjz//r59v/6+fb/+/r3//z7+P/7+/j/
+/v4//v7+//6+vr/+v37//r9+//6/fv/+v37//r9+//6/fv/+P37//j9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//b59//+////+/78//b59//9//7/+Pr5//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//n7+v/5+/r/+fv6//r9+//7/vz//f/+//v+/P/6/fv/+Pr5//j6+f/2+ff/9fj2//T29f/z
9fT/8fTy//H08v/z9fT/8/X0//P19P/z9fT/8/X0//P19P/09vX/9Pb1//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/9Pb1//P19P/z9fT/8/X0//P1
9P/09vX/9Pb1//X49v/4+vn/9fj2//v+/P/6/fv/+v37//3//v/7/vz/+fv6//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//7+v//+/v+//r99v/6/fb/+vv+//j8
/v/6/fj/+v32//v++v/5+/r/9/j///n6///9//v//v/5//r/+//5/vz/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//7
+/v/+/v7//v7+P/6+vf/+fn2//n59v/6+fb/+fj1//r58//6+fP/+vnz//r58//8+PP//Pjz//z4
8//8+PP//vjz//748//6+fP/+frz//j69v/4+vb//Pjz//r3+f/b5vL/dIOb/yEtT/+7yvL/9Pz/
//X27//7+vP/+vny//v69P/29e//+/r0//v69P/5+PX/+vn2//n49f/8+/j/+vr3//v7+P/7+/v/
+/v7//v7+//7+/v/+v37//r9+//6/fv/+v37//r9+//6/fv/+/v+//v7/v/6/fv/+v37//j9+//4
/fv/+P37//j9+//6/fv/+v37//r7/v/6+/7/9vv///X////p+v//jaG0/z5Ra//F3v7/x9nu/+r1
///v9PX/9PTx//X48//r8O//7/b2//H29f/09vL/8/Xx//P19P/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P1
9P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//6/fv/+fv6//r9+//4+vn//f/+
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+/v7//v7+//6+vf/+vr3//r59v/6
+fb/+vnz//r58//6+fP/+vnz//r69//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//4/fv/+P37//j9+//4/fv/+P37//j9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv//f/+
//r9+//5+/r/+v37//3//v/g4uH//f/+//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//v+/P/5+/r/+Pr5//b5
9//1+Pb/9fj2//T29f/z9fT/8fL1//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/8fL1
//L09v/y9Pb/8vT2//Hy9f/x8vX/8fL1//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//T1+P/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//L09v/y9Pb/8vT2//T1+P/09fj/8vT2//L09v/z9fT/
9Pb1/+Di4f/u8O//8/X0//T29f/09vX/+fv6//j6+f/4+vn/+fv6//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6+/7/+v37//v7+P/7+/j/+v37//r9+//4/vj/+P74//n7+v/5+v3/
+/r///v7/v/9//v/+v////L+///t+f//9vz///r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//7+/v/+/v7//v7+//7+/v/+/v4
//r69//6+vf/+fn2//r59v/6+fb/+vnz//r58//6+fP/+vnz//z48//8+PP//Pf5//r59v/6+fL/
+frv//j68//4+vb/+fn5//n5+//1+P//qbbQ/wsbQ/8hMVz/9Pf////68v/6+fb/9/f3/+bl3//7
+vP/+fjx//n48f/7+vT/+fjy//z79v/39vH/+fn2//r69//6+vf/+/v4//v7+P/7+/j/+v34//n7
9//4/vX/+P71//j9+//4/fv/+v37//r9+//7+/7/+/v+//v6///7+/7/+/v4//r99v/6/fb/+P37
//b8///z+///0d///xsnSv8vRXf/Dh9C/9Hl+f/o9fj/7/n8//P5/f/s8vv/+Pv///Pt9//68/n/
9fbv//P17v/3+fv/6/D0//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/
8vP5/+3t+/+trLf/+vv+//r9+//6/fv/+fv6//7////4+vn/+/78//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//v7+//7+/v/+vr3//r69//5+fb/+fn2//r59v/6+fb/+vn2//r59v/7+vf/+vr3
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//j8/v/4/P7/
+Pz+//j8/v/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+/78//7////6/fv/+v37//v+/P/L
zsz/+/78//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+/78//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+fv6//j6+f/2+ff/9vn3//T29f/09vX/8/X0//P19P/09vX/9Pb1//P19P/z9fT/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/09vX/8/X0/9HU0v/n6uj/8/X0//T2
9f/z9fT/8/X0//P19P/09vX/9Pb1//X49v/2+ff/+fv6//r9+//6/fv/+/78//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//4
/fv/+v37//v7+P/8+vv/+/v+//r9+//2/vj/9P/4//v////6+P///Pf5///8+//6/fb/6vf9/2t+
nv8UITn/8/v///r9+//7/vz//f/+//X49v/9//7/9vn3//v+/P/6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//v7+//7+/v/+/v7//v7+//6+vf/+vr3//n59v/5
+fb/+vn2//r59v/6+fP/+vnz//r58//6+fP//v77//b48f/7/O3//v/u//3/8P/19+v//Pv2//b2
9v/P19//b4CZ/0Rglv8oP2z/9P////v68//6+vr/7+/v/9HQy//7+vP//v32//n48f/8+/b/+fjy
//v69P/39vH/9fXy/////P/29vP////8//n59v/y8/D/+v34//v++v/6/fj/+v34//j8/v/4/P7/
+P74//j++P/7+/v/+/v+//v3///++///+fn2//r+9P/z/PD/9f///6++1f+1x/H/kqjg/zZJf/8t
Qnr/ER9E/9Td7P/7/vr/8fHx//Lz+f/v9f3/7/P///fv/v/47/n/9/Lx//T08f/y8/v/8PP9//Lz
+f/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9
+//7+/v/+vr6//z8/P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v+//v7/v/7+/v/+/v7//v5+v/7+fr/
+/r3//r59v/7+vT/+vnz//r58//6+fP/+fn2//r69//7+/j/+/v4//r9+//6/fv/+v37//r9+//6
/fv/+v37//v7+//7+/v/+/v+//v7/v/7+/7/+/v+//v7/v/7+/7/+/v+//v7/v/7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//z8/P/8/Pz//v7+//r6+v/y8vL//v7+//z8/P/7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+vr6//v7+//7+/v/+/v7//z8/P/8/Pz/+/v7//v7+//5+fv/9/f6//b2+f/19fj/9PT2//T09v/0
9Pb/9PT2//T09v/09Pb/8vL1//T09v/19fj/9vb5//X1+P/19fj/8/X0//P19P/z9fT/8/X0//P1
9P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/
9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T0
9P/09PT/9PT0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0
//P19P/z9fT/8/X0//P19P/09Pb/9vb5/+rq7P/09Pb/9fX4//T09v/29vn/9fX4//T09v/09Pb/
9PT2//T09v/09Pb/9PT2//T09v/19fj/9vb2//f39//5+fn/+/v7//v7+//7+/v/+/v7//r6+v/7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//r9+//4/fv/+v37//z6/v//+P7//Pr+
//r9+//0//j/8//4//j+///7+v////n5//r08P/6//j/7v///1BpmP8OHUT/7/r///v8///+////
9/n7//r7/v/6+/7/+fr9//f5+//6+/7/+vv+//r7/v/6+/7/+vv+//r7/v/6+/7/+vv+//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//6/fv/+v37//r9+//6/fv/+v37//r9+//7+/v/+/v7//r69//6+vf/+vn2//r59v/6+fb/+vn2
//r58//6+fb/+vr9//L09v/2+fX//v/4//j58P/39u///vjz//f4/v+4yt7/RFh8/0Ndkf8wRHH/
f4+j/+z2+v/+/v//9vXy//Tz7f/+/ff/+/r0//r58//8+/j/+fj1//n49f/6+fb/9vbz//v7+P/1
9fX//Pz8//v7+//09PT/+/78//n7+v/7+/v/+/v7//r7///6+/7/+P71//j+9P/7/fb//Pr7///3
///79P//+/r3//X88v/z//r/7////xonR/8+Uof/LkVz/1t0nP/a7P//7PX///T1/P/19fj/8vLy
//H08P/z9fH/8/Xu//P37f/z9e7/9fTx//T09P/09PT/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0
//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//7+/v/+/v7//v7+//7+/v/
+fn5//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/7/+/v7//v5+v/6+fb/+vn2//r59v/5+PL/+vnz//r5
8//7+vf/+/v4//v7+P/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v+
//v7/v/7+/7/+/v+//v7/v/7+/7/+/v+//v7/v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7
+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
/Pz8//v7+//5+fn//Pz8//7+/v/29vb///////n5+f/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7
+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v//Pz8//z8/P/8/Pz/+/v7//r6
+v/39/f/9fX1//T09P/09Pb/9PT2//T09v/09Pb/9fX4//X1+P/09Pb/9PT2//X1+P/09Pb/9PT2
//T09v/19fj/9fX4//X1+P/09Pb/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/
8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T0
9P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//P19P/z9fT/
8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/y
8vX/8vL1//T09v/09Pb/8vL1//Ly9f/29vn/8vL1//X1+P/19fj/9PT2//T09v/09Pb/9PT2//T0
9v/09Pb/9PT0//T09P/09PT/9PT0//X19f/39/f/+vr6//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/
+/v7//v7+//7+/v/+/v7//v7+//6/fj/+v34//z6+//8+vv//Pr///r7/v/2/vj/9P/4//j8///6
+P////X2///9+P/4/vX/7////zJLf/8MHUv/7/n///7////3+P//+Pz//+Xu/v8gKDH/2+Pu//r+
///7+v///Pr+//v6///6+///+vr///r7///4/P7/+v37//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//6+v3/+vr9//n7+v/4/vj/
+v37//v7+//7+/j/+/v7//v7+//6/fv/+vr6//r59v/8+PP/+vnz//r59v/5+v//usDT/1Zba//G
y9H/+P37//f28//++PP///Xy//b2//+lvOH/OVB9/2d8tP8yQXD/Ii9Q/9Ph/P/6+///+/b1//z3
+f/69/n/+/n6//f49f/5+PL/+vz0//f39//29/3/8PP7/73Dy/8iJiz/8vb9//n5+//7+/v/+ff+
//z6///8+v7//Pr///r7///4/P//+v32//v98f/8+/T//Pv4//rz/f///P//+fn2//X99//w////
5f3//yQxXf+Oo+X/MEVu/2x9m//r7vb/9/L0//Dq/v/28v//8O/+//Hy+f/09Pb/8/X0//D28f/v
9vP/8vL9//Ty/f/y8/v/8vP5//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//P19P/z9fT/8vP5//T1/P/x
8vj/8vP5/+3t+/+trLf/+vv+//r9+//5+fn/+fn5//f39//7+/v/+fn5//v7+//6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr3
//r69//6+fb/+vn2//n48v/5+PL/+fjy//n48v/6+fb/+vn2//n5+f/6+vr/+vr6//r6+v/5+v3/
+fr9//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v7+//6+vr/+fn5//v7
+//Ly8v/+fn5//n5+f/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v7+//6+vr/+fn5
//n5+f/6+vr/+vr6//r6+v/6+vr/9/f3//b29v/19fX/9PT0//Ly8v/y8vL/8vLy//Ly8v/y8vL/
8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8fHx//Ly8v/y8vL/9PT0//Ly8v/y
8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly
8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy
//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/
8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y
8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly
8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy/9HR0f/m5ub/9PT0
//Hx8f/09PT/9PT0//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/
8vLy//Ly8v/y8vL/9PT0//T09P/09PT/9fX1//f39//6+vr/+/v7//v7+//6+vr/+fn5//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/++fr/+/r3//n89P/2/ff/+fr///n6///6/PT/+vz0//v7/v/8+v////j+///+///5//X/7P//
/zNLff8KGkb/8Pr///Ty+f/6/v//IStM/wseSP8hPm3/fZfF/8rb+f/59/////f3//77///6+///
+ff///f4///5+/f/+v70//r69//6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//v4/f/99///+/j9//b99//1/vT/+fv3//v69//++fT/+/r3//n6
///4+///+/r///v5+v///PL/+vnz/8zR4f+Rn8H/TmOU/yo8Zf+tv9X/7/v+//T69P/u8/H/4ez2
/4mXq/80RV//orrl/5Oo2f8sPW3/Eydf/2N4r//w8////PX4/9LOzP////z/9/L0//X2+f/g7+//
aXh+/1lmdf/o9///2uz//xEcM/8XJkT/6f3//+349v/x8+f///31//v29f/8+v7/9vf6//j9+//4
+vb/+/by//z39v/8+///7PD6/+/29v/2/vv//v////X+//+KmcL/Z3ek/0NRbv/d5v//8fb///Hy
+P/v8PX/7e70//Hy+P/09fr/9PX6//T1+v/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL1//L09v/x8vX/8fL5//Lz+//x8Pj/8vH5/+7r/v+uq7r/+vr9
//r6+v/5+fn/+vr6//r6+v/8/Pz/+fn5//v7+//6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+fn2//n59v/6+fb/+fj1//n49f/5
+PX/+fj1//r59v/7+vf/+/r3//r6+v/7+/v/+/v7//r6+v/5+v3/+fr9//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v7+//7+/v/+fn5//r6+v/X19f/+fn5//n5+f/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v7+//6+vr/+fn5//X19f/y
8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly
8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/09PT/9PT0//T09P/y8vL/8vLy//Ly8v/y8vL/8vLy
//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/
8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y
8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly
8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy
//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/
8vLy//Ly8v/y8vL/8vLy//Ly8v/x8fH/8fHx/9ra2v/o6Oj/9PT0//X19f/x8fH/9PT0//Ly8v/y
8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly8v/y8vL/8vLy//Ly
8v/y8vL/8vLy//Ly8v/09PT/9fX1//f39//6+vr/+/v7//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v5+v/99/3//ff9//n7+v/5+/r/
+vj///r6/f/6/PT/+vzz//n79//19fX/+/X6//77///1+vv/4vX//xAjTv8OIEn/5fb///b////k
8///GCRW/xEoYv8aNnb/BxpT/zJHev/g8///9P////T/+//x+PL/+vr3//79+v/++fr///r7//v5
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//b7+v/2+/3/+fr///v4///++fr//vn3//z7+P/3+PX/+fv6//j8/v/0/v//
8/7//4mXvf8pNmP/CRlG/w0dTP8xPWz/tcP3/6S04/8jM1z/S2Gc/zJEcf/k7///7/r//7vS+P8R
J0n/RWmU/y1GYv/w8fj///Tq/9XRwv/5+PL/8O39/5Kat/8RI0f/TW2g/xYpUf9idqT/lqTT/zhE
bP8UI0z/xuH//+T5///y/fb/9vvr//j76P/4+fD/+/32//b17////vv/9/j1//n6///0+v//OEBd
/3GAmv/o9v//+/v4//D5//8KG0f/CBtM/7XH6f/k7Pr/7fH4/+/w9f/t7vT/7/D1//Dx9//y8/n/
8vP5//Lz+f/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL1//Hy9f/x8vX/8PH4//Lz+//w8fj/8fL5/+3q/f+uq7r/+vr9//r6+v/39/f//v7+//r6+v/+
/v7/9vb2//n5+f/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vn2//n48v/4+fL/+Pny//f49f/5+fb/+fn2//r69//6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+fn5//b29v/+/v7/+vr6//T09P/+/v7/9/f3//n5+f/5+fn/+vr6//v7+//7+/v/+vr6//n5
+f/6+vr/+vr6//v7/v/6+v3/9vb5//T09v/x8fT/8fH0//Hx9P/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//Hx9P/y8vX/9PT2//T09v/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y
8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y
8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8PDz//X1+P/w8PP/8vL1//f3+v/x8fT/7+/x//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//Ly9f/y8vX/8vL1//n5+f/6+vr/+vr6//r6+v/5+fn/+fn5//r6+v/7+/v/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/7+P3/+/j9//r6+v/5+/r/+vj///r6/f/6/PT/+f3z//r/
+P/z+fP/+/v+//r4///1+P//8v///wsaPf80THz/PFN4/3WNuf87VIT/HDNk/wsdS/9jgLv/aYO8
/xooT/8zQWH/5fP///H5+f/4+vP//Pz///b1/P/+////9/n7//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//n79//2/fT/9v30//n6/f/6
+P//+vj///r4///7+P3//vn3///99f/5+vP/9fr5//D+//+Dkq3/gZS+/2yCt/8yRW//2fT//8LZ
6f9jfJf/f5nE/526+P8KGEb/EyJQ/0pYgv/Ny+T/8fH//73R6v8eMkf/o7/d/0lYbf+7vM7/9vD4
///28//y8fn/w9T//xcoWv9ngb//GStZ/5Ww3/9ie6T/Nkx9/zlMgP+OoNj/KTJZ/ztFYf8xN0z/
Q0pe//D6///z+fD/9vjs///4+///+///8/v//+37///r/f//N0Nr/x4sVv+VpM7/9vr///T///8J
HUj/KUR5/+Py///t7vb/8fL4//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy
9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1
//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/
8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x
8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//H08v/x8vX/8fL5//Lz
+//w8fj/8fL5/+zs/f+sq7j/+fr9//n7+v/6/fv/+v37//b59//7/vz/+v37//n7+v/6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+/78//v+/P/6/fv/+v37//r9+//6/fj/
+vn2//r58//5+vP/+frz//n59v/6+vf/+v37//r9+//6/fv/+v37//r9+//6/fv/+/v7//v7+//7
+/v/+/v7//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+Pr5//n7+v/7/vz/+fv6
//n7+v/T1dT/+Pr5//r9+//7/vz/+v37//r9+//6/fv/+/78//r9+//5+/r/9vn3//Hy9f/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/09fj/8vT2//L09v/y9Pb/9fb5//T1
+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8PH0/9XW2f/o6uz/
9fb5//Dx9P/19vn/8fL1//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//P1
9P/z9fT/9Pb1//j6+f/7/vz/+/78//v+/P/5+/r/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//7+/j/+v34//j9+//4/fv/+vv///v7/v/7+/v/+v34//X99//v9vH//v////78///29P//
vcTf/zhJZP/X9v//1vT//xUnVP8LHkj/jqvd/0BRbf/Y6v//3/P//xomRv8SHEX/2ej///D1////
//z/9vf9//v////z/vz/8v34//j9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//4/vj/+P74//v7/v/8+v//+/v+//r7/v/6+/7/+v37
////+f/29vP/9vz//8/e9v9QYoz/IDFf/zBEcf9ecZf/6/X//9zm9f+Ro8X/IjNZ/yY6aP84THL/
2Oj4//H5+f/w8PD/9vbz/+rz6f/q9e7/7PH1/4+Vpv9TXoT/ydj//8jO3/+jsMD/DSA8/yY8Yf/e
6v//oKSz/8vX2v+csL3/ESVA/2J8oP/l9v//6vD1//H2///c5Pv/GCM7/+z+///4////9PTx////
+P/29/r/s8DW/xIcOP/j+v//DRlB/6bA7/8QHzX/6f3//+Dy//8SHUP/hZfG/9zm9f/5+v3/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//T29f/y9Pb/8vP7//X2/f/y8/v/8vP7/+3t/v+urbv/
+vv+//r9+//4+vn/+Pr5//n7+v/5+/r/+v37//n7+v/6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+fv6//n7+v/4+vb/+vnz//r58v/5+vP/+vz0//r6
9//7+/j/+v37//v+/P/6/fv/+v37//r9+//6/fv/+/v7//v7+//7+/v/+/v7//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//j6+f/5+/r/+Pr5//v+/P/O0M//+fv6//r9+//5
+/r/+v37//r9+//5+/r/9vn3//T29f/z9fT/8fTy//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//Hy9f/y9Pb/9PX4//T1+P/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/9PX4/9TV2P/m5+r/8vT2//T1+P/v8PP/9PX4//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//P19P/z9fT/8/X0//H08v/z9fT/
9Pb1//j6+f/5+/r/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+P/4/vT/+P70//b++P/4
/fv/+vv///v6///6+///+Pz+//L9+P/2//v/+vv+///+///u6///foGW/2p6iv/l/f//4/P//x8q
Sv81R3D/mrDX/97s/f/p9///3PL//xgoVP8LHEn/RFmD/97s///7/////v36//r58/////z/9Pby
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+/v+///3////9///+/v4//j+9f/2/vv/9v7+///////6+///8fn//6u32v9f
bqf/Kz1y/z5Se/+dsNH/7vf///D1///Lz/L/XmmQ/xwuUv90j7H/5e////T1/P/w7vb/8e/w//fw
8P/59PD/6evq/8zZ6v8XKlH/GDBg/0plkv8/VXf/rcHi/+72///x5vn/9un2//Hw+P/Ey+H/GSND
/6i44P/p8vf//v/1/+rr4//h5+v/ICw//+D2///u9v//6uzr//L09v/z+///4/f//xAfPv+81v//
ESA+/9v2//9IYH//DyA8/1BjgP+Bhpr/8O/+//Hz///t8f7/8vP5//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//D19P/w9fb/8PP7//H1/P/x8vn/8vP7/+3t/v+trLr/+vv+//r9+//6/fv/+v37//r9
+//7/vz/+/78//n7+v/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+Pr5//n7+v/5+/r/+fv6//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//n7+v/9//7/+v37//j6+f/4+vn/+/78//j6+f/7/vz/+fv6//b3+v/09fj/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8fL1//L09v/y9Pb/9PX4//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/19vn/8PH0//Hy9f/x8vX/8fL1//X2+f/19vn/8fL1//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//P19P/z9fT/+Pr5//n7
+v/6/fv/+v37//r9+//6/fv/+v37//z9+v//+vb//Pjz//v8///1+v7/+fr///7////6//v/+v32
///+///89fj/8u3s//r////Y8P//N0ho/5+syf/n8v//6fX//5Kfs/8eJ0v/0+L//+n2///v+f//
7/L//ykuQ/+zx/H/GSc+/+Lr9v/5/vz/9v///+v4+f/x9vj//v7////6+//8+/j/+P71//b++P/0
/v//9P/+//r99v/8+/T///n5///6+f/6/vT/9//1//T+///2/P//+/v+//z6///++P//6Ob6//D9
/v/q/fb/9f////X7///6+v3///7///Xx/v/1+P//kaLA/x8xTf9MXof/x9f//+vz///x8vn/9vb5
/+/w8//0+f3/5O3y/7rEy//h7PP/6fL3//D19v/19fX/8O/s//Xy9P/y8vX/7O/8/+fu///K1vD/
M0Rl/wYcTP8ZMWD/5fv//+vz7f/s8Ob/+Pny//T09v/v7fb/8vP5//Dx9//n6O7/7+32/+3p+f91
d4z/a3ya/+L9///p+f//bnqL/xwqOP/o////6P3//w8cPP+KpNv/FyhL/+n3//90fJP/YWiN//D3
///r7uz/9fXq//X2+f/t8fj/8vP5//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5
//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//5+/r/+v37//v+/P/4+vn/+/78//v+/P/6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+/78//j6+f/7/vz/
+fv6//r9+//w8/H/+/78//n7+v/19vn/9PX4//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//L09v/y9Pb/9PX4
//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/9fb5/+fo6//y
9Pb/9PX4//Hy9f/w8fT/9PX4//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fTy//P19P/2+ff/+fv6//r9+//7/vz/
+v37//v7+//69/n//v7+//j+9f/x+fb/+f////P7///u9v//9fv///Ly9f/++/3/+vv+/+75//8b
J0L/O0lq/9nn+//r8/z/9Pr+/+fu//8dIkX/1OD//+Xw/P/p9PD/+P///+Xx///g9f//HilK/9fd
/f/0+v//8/zy//r/9f/1+PP///////z6/v/7+/v/+P37//b+/v/2/P//+Pz///v7+//8+vv//Pj/
//v6///6/fj/+P74//j8/v/6+/7/+/v+//j7///Czur/LztW/1Bgfv+tu9X/+P7///j6+f/z/P//
9fv///z39v/v7vr/aHyg/wobPv9leZr/5PP///T3///19fj/9fX1//Dx9P/v9Pj/9vz///H3/f/v
9fn/8fn5/+vu6f/z9O3/9fTt//Lu6f/x8O3/8PH3/+zy+//X4fD/ZnSQ/xIjS/8iMl3/3+n///Hy
+P/w8PP/8e7z//r3/v/w8PP/8PPu/+/y6v/0+vD/8/nw/+3v8f/i6vn/Z3iW/3CDrf/T4v//OkZz
/wsZRP+lxP//2/3//w8fPP8WJTr/5fn//+Ts9P/z9/z/7Pf+/+jy+f/v9fv/8vP5//Tx8//39fb/
9PT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+t
rLf/+vv+//r9+//9//7/+Pr5//n7+v/4+vn//v////n7+v/6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+fv6//n7+v/6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv//f/+//v+/P/5+/r/+fv6//7////FyMb/9/n7//Dx
9P/y9Pb/8vT2//L09v/y9Pb/9PX4//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//L09v/y9Pb/9PX4//T1+P/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/8vT2/9TV2P/n6Ov/8fL1//L09v/v8PP/9PX4
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/9PX4//L09v/x9PL/8/X0//X49v/5+/r/+/78//v8///3+P7//v////X9
7//y/vP/6vb//5iju/8WHTH/8/v///j+///2/P//8P3//6270v89SWv/4/P//+z1///x9PL/7e3w
//b2///x9P//5+7///H59v/0/fL/6vHu/+v5///j9f//HylF/zlCYP/n7///+v////v/9f/7/vr/
9vn3//v7+//7+/v/+P74//j++P/6/fv/+/v7//v7+P/6+///9vv///T7///0/v//+P74//v99v/8
+/b//Pr7//T8//+0yuv/LEFp/x4xZ/9CVIj/sLnS//n8///5+fn/+/78//L+//+XqLv/SluC/5uw
3P/q+///7Pb6/+3v8f/29PX/9/f3/+zs7P/09fj/7e/x//P3+f/w9fT/8/Xx/+/v7P/y8ez/9fTt
//b17v/r6uT/8fHu//T29f/r8PT/4Ov3/32Jpf8wOk7/7/L8//Xy9//t7fD/7e3w//v5+v/t7Of/
7/Dl/+zx4f/t9OP/9P7v/+/18P/h7Pn/pLPd/yk3Yf8iLFP/4Pb//2eDtv8IHEL/hqbk/xAfQf/k
9f//7PT0//b09f/39fb/6u/w/+/1+f/w9v//+fr///Dr7P/68vL/9PT0//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//5+/r/+Pr5
//n7+v/7/vz/+/78//j6+f/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+vv+//v8///3+fv/+fr9//X2+f/r7O//9PX4//T1+P/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y8/n/8vP5//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8fL1//L09v/y9Pb/9PX4//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8fL1//L09v/y9Pb/8vT2//L09v/y9Pb/9PX4//T1+P/z9fT/8/X0//P19P/z
9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/8fL1//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2/+/w8//09fj/8vT2//Hy9f/w8fT/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//Lz+f/y8/n/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1
//L09v/y9Pb/8vT2//Hy9f/y9Pb/9fb5//f5+//2+///+/////b58v/2/vv/5vf//11sh/8nMFH/
7vv//+37//+tvcz/Dhow/6G33v88SGj/8P7//+3x+P/09PT/9fH7//Ty+//z9fT/8Pbx//P17v/z
9fH/8PP9/+/z///r9v3/6vn//xolPv/e6v//+f7///v////z/v//9P////j8/v/7/vr/+v/5/+70
7P////n////8//n5+//u9v//qbrc/y89Vv+ou8X/7/v6////+f/8/fr/+v///+37//+Ln8D/ZX6q
/05jm/8oOmn/bYOu/+r9///19P//0dbi/1Fng/8cME3/eIek/+nx///u9Pn/8PX2//X49v/1+Pb/
8vT2//L09v/y9Pb/8vT2//T09P/y8vL/8vPw//Hx7v/x8e7/8fHu//Hx7v/x8+z/8fPs//Hz7P/w
8er/7/Ht/+zx8//w9fT/9PPt//Hw6f/v8e3/7vTu//P07f/y8er/8u7p//X07v/09u//6/Ls/+vu
6f/s8Pr/2eT//xgfOf94gJf/2+z5/+P9///i/v//MENo/0lWfP/r8///7Ozs//Xy9//18fv/9fD/
//Ly///v9vb/8PX0//Xy9P/38vT/9PT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/
8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//5+/r/+fv6//v+/P/7/vz/+/78//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv//P7///f5+//x
8vX/9PX4//Hy9f/3+fv/8vT2//Hy9f/y9Pb/8vT2//L09v/y9Pb/8vP5//Lz+f/y8/n/8vP5//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//L09v/y9Pb/
9PX4//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//Hy
9f/x8vX/8vT2//T1+P/09fj/9fb5//X2+f/4+vn/+Pr5//j6+f/4+vn/+Pr5//j6+f/4+vn/+Pr5
//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/9/n7//f5+//29/r/9fb5//T1+P/09fj/
8vT2//L09v/x8vX/8fL1//Hy9f/x8vX/8fL1//L09v/y9Pb/9PX4//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/9fb5//L0
9v/29/r/9PX4//T1+P/x8vX/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//Lz+f/y8/n/8vP5//Lz+f/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/x9vX/+Pr5//z8/P/7////2u3//z1Oaf87SG7/6fr//7C/4/9qfZ//ECBG/2d/
sf9oeJj/6/r///X0///09Pb/8vT2//L09v/w9fT/8/X0//T09v/18vn/9PL9//Lz+//4+vn/6vX8
/x0pQv/V6f//8/v///P4//8mMkf/zN7+//X+///2+/r/9P/7//P69P///v////z///X0///z////
jaTb/xwxWv98krH/4vL///L2/f/2+v//8////+X5//+Fmr3/c4ep/8XY8f+Hmrb/HTBW/w4fSv9e
c6f/Z3iq/yQxWP+TocX/5e35/+/0+P/x/P//7PX///Hx8f/09PH/8vT2//D1+f/y9Pb/8vT2//T0
9P/09PT/9PT0//T09P/x9PL/8fTy//Dz8f/w8/H/8fHx//Hx7v/y8ez/8vHs//f28//19PH/9O/r
/+/w6f/s9O7/6/jt//D06v/18Oz/9/D1//Hr8//v7fT/9fXy//Pz5f/09er/5+3z/+Xr8//09Pb/
6urn/////P/x9vr/xtHf/9Pe7P/y8/v/8fH0/+7y9P/x9PL/9/D1//jx9P/z9fT/8PX0//D1+f/y
8/n/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t
+/+trLf/+vv+//r9+//69/n/+fn5///8/v/39/f//vv9//7+/v/8+vv/+/v7//z6+//7+/v//Pr7
//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/
+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7
+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7
+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7
//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v/
/Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8
+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6
+//8/Pz//vv///r6/f/7+P3//Pz///z6/v/5+fv/9vP4//X1+P/18vf/9PT2//Lw9P/Ly87/8e7z
//Ly9f/18vf/9PT2//Xy9//09Pb/9fL3//T09v/18vf/9PT2//Xy9//09Pb/9fL3//T09v/18vf/
9PT2//Xy9//09Pb/9fL3//T09v/18vf/9PT2//Xy9//09Pb/9fL3//T09v/18vf/9PT2//Xy9//0
9Pb/9fL3//T09v/18vf/9PT2//Xy9//09Pb/9fL3//T09v/28/j/9fX4//bz+P/09Pb/9fL3//T0
9v/18vf/9PT2//Xy9//09Pb/9fL3//T09v/28/j/9fX4//Xy9//09Pb/9PHz//T09P/18vT/9PT0
//Tx8//y8vL/9fL0//T09P/39fb/+fn5//v5+v/7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v/
/Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//v7+//8
+vv/+/v7//z6+//7+/v//Pr7//v7+//8+vv/+/v7//z6+//7+/v//Pr7//z8/P/7+fr/+/v7//77
/f/8/Pz//Pr7//n5+f/29PX/9PT0//Xy9//09Pb/9fL3//T09v/18vf/9PT2//Xy9//09Pb/9fL3
//T09v/18vf/9PT2//Xy9//09Pb/9fL3//T09v/18vn/9fP7/9DQ0//o6Ov/8/X0//P19P/y8vL/
8vLy//b2+f/y8PT/8vD3//Xy+f/09Pb/9fX4//T29f/v8fD/8/X0//Dz8f/w8PP/9vb5//Ty+f/y
8fj/+ff+//Du9v/y9Pb/8vT2//D19P/z9fT/8/X0//T09P/09Pb/9PT2//Xy9//09Pb/9fL3//T0
9v/18vf/9PT2//Xy9//09Pb/9fL3//T09v/18vf/9PT2//Xy9//09Pb/9fL3//T09v/1+Pb/7/Dz
//f2/v/2+v//5fH//zlFav8tPF//5P///2yAp/9pgLD/BxtO/xwyY/+zw+P/8fb///Hy+f/29/r/
9PT0//P19P/w9fb/8PX2//T08f/09e7/9fL0//Ty+//w7///8Pn//xglOf/V7P//8v7//8PQ2P8g
Mk//jqPM/+rx///5+v//+v////P49v/8+/j/+/z//+z///8fMkz/DyFE/0xqoP8cNm7/Ijlo/73O
6//s/v//Mk13/wkgSv8LHUL/pbni//P6///o7Pn/1d/3/42ewP83Un//NUx6/4yVuv/t6///8u//
//X0///t8f7/7/X7//H29f/w8+7/8vT2//Ty+f/08vn/9PL5//Lz+f/y9Pb/8vP5//Lz+f/08vn/
9PL5//Hx9P/w8PP/8vDx//Lw8f/y7e//8Ovq/83Lyf/y8e7/8fDt//Dv7P/09PH/7e7r//X07v/1
9PH/9fDx//Lw8f/y8PH/8vHu//Lx6v/y8er/8vHu//Lx7v/y8e7/9fDu//Xw7v/y8e7/8fHu//Hx
7v/y8PH/8vDx//Hx8f/x8fH/9PHz//Tx8//y9Pb/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5
//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/
8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y
8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz
+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5
//Lz+f/y8/n/8vT2//P19P/y9Pb/8fL5//T1/P/x8vj/8vP7/+3t/v+urbv/+vv+//r9+//7+/v/
+vr6//v7+//5+fn/+fn5//v7+//6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/5+fn/+fn7//r6/f/7+/7/
+fn7//X1+P/x8fT/8vL1//Hx9P/x8fT/9PT2//Ly9f/q6uz/9fX4//T09v/y8vX/8vL1//Ly9f/y
8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8fH0//Ly9f/09Pb/9PT2//T09v/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//Ly9f/y8vX/8vL1//Ly8v/y8vL/9PT0//b29v/39/f/+fn5//v7+//6+vr/+vr6//n5+f/5
+fn/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+/v7//v7+//7+/v/+/v7//r6+v/5+fn/9/f3//b29v/09PT/8vLy//Hx8f/x8fH/
8fHx//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y
8vX/8vL1//Ly9f/08fX/9fL3/+fn6v/x8fT/8/X0//H08v/09PT/8vLy//Hu8//28/j/9vP7//Lw
9//y8fn/9PX8/+3x+P/m7PD/7vL3/+/w9f/29fz/8vH4/+3r7//18vf/+fb6//Hx9P/y8vX/8vL1
//Hy9f/x8vX/8vL1//Ly9f/08fj/9PH4//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//H08v/w8/H/7/Hw//v0///y7v//4ur//xIePP8Q
Ijv/0/r//zBMgP8JHE3/DhxM/2x7pf/u9v//7/Hw//Tz///w8///7vP8/+7z/P/x8fz/8fL5/+71
9f/v9PL/8vH4//Pv+v/u6vf/7vX//xkkQf/S6P//7PP///b///8kM2D/XW6i/+Ho/v/+/v//9fX1
//T3//+Jka7/SlR5/9rs//9OXIP/hJO7/6K05f8mOm//CBpJ/6K69P82SHP/Pk+A/1Jjkv9nd5f/
w9Hn//Tz///39v//7/L//6y42f81S3L/OU90/7TA2//v8f//8fH8//Hy+P/09fr/8fL1//D19v/u
8vf/8fL4//Lx+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/y8fj/8vH4//Hx9P/w8PP/8e/w//Hv
8P/07/D/8ezu/+rp5v/08/D/8fDt//Hw7f/08/D/8O/s//Dv7P/x8O3/8fDt//Hw7f/x8O3/8fDt
//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hv8P/x7/D/
8fH0//Hx9P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL1//Hy9f/x
8vX/8PH4//Lz+//w8fj/8fL5/+zs/f+trLr/+fr9//n7+v//////+vr6//n5+f/8/Pz/+vr6//n5
+f/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr9//r6/f/39/r/8vL1//Hx9P/09Pb/8fH0//Dw
8//v7/H/9PT2//X1+P/s7O//9/f6//T09v/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8fH0//Ly9f/y
8vX/9PT2//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/09PT/9fX1//f3
9//6+vr/+/v7//v7+//6+vr/+fn5//n5+f/6+vr/+vr6//v7+//7+/v/+/v7//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr9//r6/f/5+fv/+fn7//b2+f/0
9Pb/8vL1//Hx9P/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8PH0//Dx9P/29vb/8fHx//Xy9P/x7/D/9PH1//Du9v/x8vn/+Pv//8jM2/94f4v/
lJik/+js9v/19v3/8O72//f1+f/w7fL/9vT1//Dt7//y8vX/8vL1//Lx+P/y8fj/8vH4//Lx+P/0
8fj/9PH4//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/w8ff/9PT2//Xt7f/6+P//4O7//wsYOf8PIkf/eJ3X/wokV/8mQXT/4fH/
//H0///t7vT/9PTx/+3u9P/w8/3/7fL//+/x///27vz/8+/6/+/09f/r9vL/7/T1//Ly8v/2+PH/
6PL5/z5VdP8MHz3/u9Hm/73S8P8ZMV3/ECRQ/83g+v/r8/z/9fr+/+/6//8+U4L/ECFR/8HU//8p
ME3/rbTM/+Px///f+f//M0tl/4uw2f89V3f/rb3O/+z1/f/u9Pj/7PH1//Hw9//18///7O7//8rR
9v9OYIf/TmCC/8jS5//r8fn/7/X5/+/09f/1+Pb/8PDz//Hy+f/y8/v/8fL5//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8vP5//Ly9f/w8PP/8e/w//Hv8P/x7/D/8e/w//Hw7f/x8O3/
9PPw//Hw7f/x8O3/9PPw//Dv7P/v7uv/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x
8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hv8P/x7/D/8PDw//Hx8f/w8fT/8fL1//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL1//Hy9f/x8vX/8PH4//Lz+//w8fj/8fL5
/+zs/f+trLr/+fr9//n7+v/5+fn/+vr6//n5+f/7+/v/+/v7//n5+f/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+fn7//b2+f/y8vX/8fH0//Hx9P/y8vX/8fH0//Ly9f/09Pb/8fH0//T09v/Fxcj/
8fH0//Hx9P/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y
8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8fH0//Ly9f/y8vX/9PT2//Ly9f/y8vX/9PT2
//Ly9f/x8fT/8fH0//T09P/29vb/+fn5//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/7+/v/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//n5+f/6+vr/+vr6//r6
+v/6+vr/9/f3//b29v/19fX/8fH0//Hx9P/x8fT/8fH0//Hx9P/x8fT/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/09PT/8PDw/9DR1P/k5er/8fL4//Hy9f/x
8fT/8vLy//Tz8P/29fL/8vLy//Dx9//q7ff/6vH//6mxxv9ZX3T/jpSp/+71///09v//8vP7//b2
+f/09PT/7Ovo//Hv8P/y8vX/8vL1//Hy+f/x8vn/8vH4//Lx+P/08fX/9PHz//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/9PT2//T09v/y8vX/8fH0//Hw9//w7vr/
8fD3//r/9//2////3vH//w4bQf8JGkz/ME6H/wgdRf/L6P//5Or///v3///79///8fD3/+/x8P/w
8/H/7/Ty//Hy9f/28PX/9vD4//Lx+P/v9Pj/6/X5/+vz/P/w8v//4On//1Fjmf8PIln/FChg/yA2
ev8JHmv/BRpY/zJFZ//R4/j/8////5asxf8XM2D/CyVZ/8DY//8nMFT/q7LL/+Xt///k9v//WG2U
/xMlV/8mNmv/uL/m//Hx///09Pb/9vbz//Hy+P/t7vb/8O/+/8XM3f90gZj/iZet/+3y///x8vj/
7/T4/+/0+P/y8vX/8vL1//Hy+P/x8vn/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hx9P/y8vX/8vLy//Hx8f/v7O7/7Orr/8rJxv/x8O3/9PPw//Tz8P/v7uv/7+7r//Hw
7f/y8e7/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw6v/x8Or/8fDq
//Hw6v/x8Or/8fDq//Hw7f/x8O3/8PDw//Dw8P/w8fT/8fL1//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL1//Hy9f/x8vX/8PH4//Lz+//w8fj/8fL5/+zs/f+trLr/+fr9//n7+v/5
+fn/+/v7//v7+//8/Pz/+/v7//n5+f/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6
+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/
+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//v7+//5+fn/9fX4//Ly9f/y
8vX/9PT2//T09v/y8vX/8fH0//Ly9f/19fj/8vL1//Dw8//OztD/8PDz//T09v/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/
8vL1//T09v/y8vX/8vL1//Ly9f/09Pb/9PT2//T09v/y8vX/8fHx//T09P/29vb/+fn5//v7+//7
+/v/+vr6//n5+f/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6
+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6
//r6+v/7+/v/+/v7//r6+v/6+vr/+vr6//f39//29vb/9PT0//Ly8v/x8fH/8vLy//Ly8v/09PT/
8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y
8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/x9PL/8fTy/9TV2P/l5uv/8vP7//Lz+f/y8fj/8vLy//f28//08+3/9PT0
//Dx9//r7/z/5+///+ny//9zfZn/a3KO//H7///r9f//5en2/+/0+P/v8fD/9fXy/+/v7P/x8vX/
8fL1/+/y+f/v8vn/8fL4//Hy9f/y8vL/8vPw//Ly8v/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y
8vX/8vL1//Ly9f/y8vX/8vL1//T09v/29vn/+fn7//z6/v//+///8fD4//D////j+///1u7//xIh
Qf8uRX3/ChxJ/w8cOv/u+///7/H///Lx+P/29/r/7/Dz/+/w8//29/r/7/Ty/+/09f/v8vn/8vH5
//fu+P/28PX/6/fv/+r48v/y8v//8u///+v1//89Sm//ECFR/yE3cv8RI1P/RVqN/xkkT/+UotP/
6v7//2F1lv9xlcT/DSVO/0hcjf8+SG7/wsje/+bq+v/p8///c36c/ykyW/9faJP/1Nrr//L09v/x
8fT/9PT2/+/1+//u9Pn/9vv6/+/x8P/s8vj/8fX8//Tx9f/08fX/8fH8/+/y/P/y8vX/8vLy//Hy
9f/v9PX/8fL4//Hy+P/x8vj/8fL4/+/0+P/v9Pj/7/T4/+/0+P/y8/n/8fL4//Ly9f/y8vX/9PT0
//Ly8v/x7/D/7+zu/9DPzP/x8O3/8vHu//X08f/x8O3/8O/s//Hw7f/x8O3/8fDt//Hw7f/x8O3/
8fDt//Hw7f/x8O3/8fDt//Hw7f/x8Or/8fDq//Hw6v/x8Or/8fDq//Hw6v/x8Or/8fDq//Lx7v/y
8e7/8PDw//Dw8P/w8fT/8fL1//L09v/x8vX/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL1//L0
9v/x8vX/8fL5//Lz+//w8fj/8fL5/+3t/v+trLr/+fr9//n7+v/7/vz//f/+//3//v/6/fv/+Pr5
//3//v/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//v7/v/7+/7/+vv+//r7/v/6/fv/+v37//r9+P/6/fj/+v34//r9
+P/6/fv/+v37//r7/v/6+///+vv///v6///8+v///Pr+//r9+P/4/vX/9//1//f/9f/4/fv/+vv+
//r7///6+/7/+v37//r9+P/6/fj/+/v4//v7+//7+/v/+/v7//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+/78//v+
/P/6/fv/+v37//r9+//6/fv/+v37//n7+v/1+Pb/8vT2//Hy9f/y9Pb/9PX4//T1+P/y9Pb/9PX4
//Hy9f/5+v3/9fb5/+3v8f/3+fv/8PH0//L09v/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/
9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/0
9fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//L09v/y9Pb/8/X0//P1
9P/x9PL/8/X0//T29f/2+ff/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//n79//5+/f/+v37//v+/P/7/vz/+/78//v+/P/6/fv/
+/78//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//7/P//+vv+//f5+//19vn/8vT2//L09v/y
9Pb/8vT2//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1
+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4
//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T29f/19fX/
9PT0//Tx9f/18vn/9vb5//T1+P/z9/n/8PX2//Hy+P/09Pb/9fX1//Hx9P/u8/z/6fP//46ewP8g
Mln/ByBJ/xEoUP90har/8vT///bw///38fv/8vH5/+7y9//w9vH/8Pbx//D19v/w8/v/8PP9//Lz
+//38vT/+fTy//b29v/09vX/8/X0//H08v/z9fT/8/X0//T29f/1+Pb/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//v7/v/39fz/+P///4mhzv8KH0j/LUh1/zhRff/d9f//FBs2/+zz///y8v3/
9PL9//T09v/09e7/8/Xx//Dz///w8v//8fX8//H2+P/x9vr/9PX6//Xz+//19fj/8fb1//H29f/y
9Pb/9PT2//L09v/v9fn/7PX//+v2///s9f3/6Pb//yMwWf/D3P//epDA/yY2U/+xx+n/pLnQ/2Nw
gP/U3uj/8PX2//P18f/z9fT/8PX5//Lz+//w8/v/8vT2//P19P/09fj/9PX4//H2+v/x9vj/9Pb1
//T29f/09fj/9PX4//X1+P/19fj/9PX6//T1+v/19fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/
9PX4//T1+P/09fj/9PX4//T1+P/09fj/8vT2//L09v/09fj/9PX4//L09v/x8vX/8vLy//Lz8P/x
8e7/8PDt//X18v/w8O3/8vPw/+3u6//y8/D/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx
7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Lz8P/x8e7/8fHu//Hx7v/y8vL/8vLy
//T09P/19fX/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/
9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/0
9fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1
+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4
//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//P19P/1+Pb/8fL4//Dx+P/x8vj/
9PX6/+3t+/+urrj/+vv+//r9+//Q09H/zc/O/8/R0P/Q09H/z9HQ/83Pzv/O0M//ztDP/87Qz//O
0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Q
z//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP
/87P0v/Oz9L/ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//
zs/S/87Qz//Oz9L/ztDP/87Qz//L0M//y9DP/8vQ0f/L0NH/y9DR/87Qz//O0M//ztDP/87Qz//O
0M//zs/S/87P1P/Oz9T/zs/S/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Q
z//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP
/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//P0dD/z9HQ/87Qz//P0dD/z9HQ/8/R0P/P0dD/
z9HQ/8nLyv/Jy8r/yMnM/8nKzf/Jys3/ysvO/8nKzf/Iycz/yMnM/8jJzP/Jys3/yMnM/8rLzv+n
qKv/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nK
zf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN
/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/yMrJ/8nLyv/Kzcv/y87M/8/R0P/Q09H/
ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//O
0M//ztDP/9DT0f/P0dD/z9HQ/8/R0P/P0dD/z9HQ/8/R0P/Q09H/z9HQ/8/R0P/O0M//ztDP/83P
zv/Lzsz/ycvK/8nLyv/Iycz/yMnM/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN
/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/
ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/J
ys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Iysn/xcbJ/7a1u//Cv8b/ysrN/8nL
yv/Gysn/w8rK/8vM0v/LzNL/z8zQ/8zMz//DydH/x9Hl/1xrj/8+U4L/NVOO/woeSf9daYz/xsjd
/8/L1f/FxcX/vcTC/8nUzf/GzsX/x83H/8rKyv/Jx87/yMnQ/8XJ0P/Jys3/ycvK/8rNy//Lzsz/
zc/O/87Qz//P0dD/z9HQ/8/R0P/P0dD/ztDP/87Qz//O0M//ztDP/87Qz//O0M//ztDP/87Qz//Q
0dT/w83i/1Fomf8AFkf/CiBR/zROe/+7ze3/wcrZ/8nK0f/Kys3/ysrN/8rKyv/KzMX/yczF/8nK
z//HytH/ycrP/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN
/8nKzf/Jys3/w8vZ/15rjv8dK0z/Ex03/3WFov+8y+H/yNPg/77Gz//JztL/ycrN/8nLyv/Kys3/
ysrN/8nKz//Jys//ycrP/8nKz//Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/J
ys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nK
zf/Iycz/ycrN/8jJzP/Iycz/yMnM/8nKzf/HyMr/w8XE/6+vr//FxsP/x8fE/8jIxf/FxsP/y8vJ
/8jIxf/FxsP/yMjF/8jIxf/IyMX/yMjF/8jIxf/IyMX/yMjF/8jIxf/IyMj/yMjI/8jIxf/IyMX/
yMjF/8jIxf/IyMX/yMjF/8jIxf/IyMX/x8fE/8fHxP/IyMj/ycnJ/8nJyf/Kysr/ycrN/8nKzf/J
ys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nK
zf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN
/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/
ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/Jys3/ycrN/8nKzf/J
ys3/ycrN/8nKzf/Jys3/ycvK/8jKyf/Jy8r/yMnO/8vM0v/Ky9H/zc7T/9TT4f+mprD/+vv+//r9
+//6/fv/+Pr5//v+/P/1+Pb/+v37//v+/P/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6
//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/
+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n79//5+/f/+fv6//n7+v/6
+v3/+vr9//r6/f/6+v3/+vr9//r6/f/6+vr/+vr6//r69//6+vf/+vz0//n89P/1/vT/9f70//r6
+v/7+P3/+/j///v4/f/6+vr/+vr3//n98//5/fP/+vr3//v5+v/7+P3/+vr9//n6/f/2+/3/+fv6
//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/
+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5
+/r/+fv6//n7+v/7/vz/+v37//r9+//6/fv/+/78//v+/P/5+/r/9vn3//T29f/09vX/9PX4//T1
+P/09fj/9PX4//T1+P/09fj/9PX4//Dx9P/x8vX/8PH0//X2+f/Iycz/8fL1//L09v/09fj/9PX4
//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/
9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/0
9fj/9PX4//T1+P/09fj/9fj2//j6+f/6/fv//f/+//3//v/7/vz/+fv6//n7+v/5+/r/+fv6//n7
+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//v+/P/9//7//f/+
//3//v/9//7/+/78//r9+//5+/r/8/X0//P19P/x8vX/8fL1//Hy9f/x8vX/8fL1//L09v/09fj/
9PX4//T1+P/09fj/9PX4//T1+P/09fj/9fb5//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/0
9fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1
+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4
//T1+P/09fj/9PX4//T1+P/w9fT/8fb4/9DR1//n5u3/9PT2//H08v/s8+3/8Pj1//X2+f/19fj/
8vDx//Hx8f/v9fv/7fn//2p6nf9oe6T/yuD//1trjP9wfZ7/0N79/8HO7P/m9f//4/D4//D6/f/0
9fj/9/X5//r19v/59vr/+ff+//n7+v/4/vT/+P/x//v++v/7/vz/+/78//v+/P/7/vz/+/78//v+
/P/7/vz/+fv6//n7+v/5+/r/+fv6//n7+v/5+/r/+fv6//n7+v/6////4/H//y5EcP8KHVb/BxpT
/ztSg//u////6PPu//T1+P/19fj/9Pb1//T29f/19fj/9fX4//T28v/09vL/9Pb1//T1+P/09fj/
9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/8Pb8/+z2///Y
5vf/0Nnp/+fy///r8/z/7/X7//X6/v/q6/D/9fP7//Xz+//09fz/9PX8//T1+v/x9vr/8fb4//H2
9f/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4
//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/y9Pb/9PX4//L09v/x8vX/
8vT2//T1+P/x8vX/6+7s/8vLy//y8/D/8PDt//Hx7v/x8e7/8PDt//Hx7v/y8/D/8vPw//Lz8P/y
8/D/8vPw//Lz8P/y8/D/8vPw//Lz8P/y8vL/8vLy//Lz8P/y8/D/8vPw//Lz8P/y8/D/8vPw//Lz
8P/y8/D/8vPw//Lz8P/y8vL/9PT0//X19f/19fX/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4
//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/
9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/0
9fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1
+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9Pb1
//j6+f/2+ff/8PH3//Hy+P/09fr/9PX6/+vq+f+rqrX/+vv+//r9+//7/vz/+/78//n7+v/7/vz/
+v37//n7+v/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+P/6/fj/+v37//r9+//7+/v/+/v7//v7/v/7+/7/////
//v7/v/6+vr/+fv6//n7+v/6/fj/+/78//T7+f/t+/v/9v////n6/f/7+fr///z///v2+P/0+f3/
+P////b////z/P//9vf6//v5+v///Pv//v33////+f/4+vP/+v34//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//5+/r/+v37//r9+//2+ff/8fTy//P19P/z9fT/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//Hy9f/19vn/8vT2//Dx9P/w8fT/9PX4//Hy9f/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//Hy9f/19vn/+fv6
//r9+//6/fv/+/78//v+/P/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+fv6//j6+f/4+vn/9vn3//T29f/z9fT/8/X0//P19P/z
9fT/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x
9vX/7vL0/+/w9f/y8fj/9PT2//P19P/z+fP/7/Ty//T1+P/t7/H/9fL0//n6/f/p8fr/r77T/z1N
bv9gcZj/5Or//3yGqP8ZKFH/ESVU/xcsYv9dcqT/5fX///b58v///vf///3z//v99P/4+vb/9/f/
//r6/////P////r5//v7+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//z9/z/5vX//zNFc/8NIFb/DR5U/22Ctv/m8v//8Pbx//T09v/0
8vn/8vP5//Dz+//y8/v/9PL7//L09v/z9fT/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//D19v/w9fb/8PX2//D19P/z9fT/8/X0
//T09v/09Pb/9PL7//Ty+//y8/v/8vP7//D1+f/w9fb/8PX0//D19P/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0/+3t
7f/v7+z/8fHu//Hx7v/x8e7/8vPw//Dw7f/w8O3/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu
//Hx7v/x8fH/8fHx//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8fH/
8fHx//Ly8v/y8vL/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x
8vj/8vP5/+3t+/+trLf/+vv+//r9+//4+vn/+fv6//3//v/5+/r/+/78//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r7/v/6+/7/+vv+//r9+//7+/v/+/v4//v7+P/7+/j/+Pr2//r9+//+////+f7///n////w
+v7/8fr//9vp+v+Ak7n/Rld5/3yFmv/n7/7/+P7///X///+/0/H/0/H//0tgiv8VIkP/tMDk//H5
///7/P//9fX1//T69P/6//v/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//b59//0
9vX/8fTy//P19P/z9fT/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/9PX4//Dx9P/y9Pb/8fL1//L0
9v/o6uz/9PX4//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/09fj/9PX4//X2+f/5+v3/+v37//r9+//6/fv/+/78//v+/P/6
/fv/+fv6//r9+//6/fv/+/78//v+/P/7/vz/+v37//r9+//7/vz/+v37//n7+v/4+vn/9vn3//X4
9v/09vX/8/X0//P19P/z9fT/8/X0//P19P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/v9PL/9PX4/+3s8//y8Pf/8vD0
//f39//u8Oz/8fb1//T1+v/t7vT/8vL1/+zx9f/v+v//p7jR/0NWff9yhbL/6/L//7vB3/9DVXj/
IjRe/0FWi/84SG//8P////X////x/P//9v///+76+//4////9/f///v4///29f3//v////r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//w8/H/6fL//zlIbf80SXb/FSNH/9vu///x9v//9fL0//X08f/09PT/8PP7//Dz+//y9Pb/8vT2
//Lz+//y8/v/8vP5//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//T09v/09Pb/8/X0//P19P/z9fT/8/X0//P19P/y9Pb/8vP5//Lz+f/y
8/n/8vP5//T09v/09Pb/9PT0//T09P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8fL1//Hy9f/y9Pb/8vT2//T1+P/y9Pb/8fTy/+rq6v/x8e7/8PDt//Lz8P/w8O3/
7+/s//X18v/w8O3/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8fH/8fHx//Hx7v/x
8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8fH/8fHx//Ly8v/y8vL/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+
//r9+//7/vz/9vn3//r6/f/2+ff//v////r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6+/7/
+vv+//r7/v/4/P7/+Pz+//j9+//6/fv/+v37//v7+//7+/v/+v37//r9+//6/fv/+v37//r9+//6
/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+vv+//r7///6+///+/v7//v7
+//7+/7/+v37//r9+//6/fj/+Pr2//7//P/6/fv/+Pz+//T+///x/P//v8zf/xwoQv87T4H/fZXR
/0RRdP/U4f//6Pr//2F1lv8fNmT/BhxQ/x86dv8rRYH/FCdX/0BQev/Dz+7/9Pv///r////1/Pb/
+v34//r9+//6/fv/+v37//v7+P/7+/j/+v34//j++P/4/fv/+v37//v7+//7+/v/+v34//r9+//6
+/7/+vv+//r9+//6/fv/+v37//r9+//6/fv/+v34//r9+//6/fj/+/v7//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+fv6//r9+//7/vz/+fv6//X49v/z9fT/8/X0//P19P/z9fT/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/9fb5//L09v/v8PP/8PH0//n6/f/Cw8b/9vf6//Hy9f/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//Hy9f/x8vX/8vT2//L0
9v/09fj/9fb5//n6/f/6+/7/+/78//r9+//5+/r/+v37//v+/P/6/fv/+v37//r9+//6/fv/+v37
//n7+v/4+vn/9vn3//X49v/z9fT/8/X0//P19P/z9fT/8/X0//P19P/z9fT/8/X0//H08v/x9PL/
8/X0//P19P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//P19P/z9fT/9fX1/8/N1P/s6PL/9PT2//Dw8P/z9fT/9vn3//L09v/v
8PP/+/v+//P4//+uvNP/QU9u/zNDav+crtP/6fX//+73+v/s9/7/5/P//7XC5f8xPFr/RFJs/9Hp
//93jMn/KDhq/4SVvP9KU2f/q6y8//v8///u/e//8f/w//b++P/6+/7/+v37//v7+//6/fj/+v34
//r9+//6/fv/+v37//v7+//6/fv/+v37//j9+//4/fv/+/v7//v7+P/+//n/2uTo/yEtRf/V7P//
5ff//+r2///29f3/9vHw//X07v/z9e7/8PX2/+/29v/z9fH/9PTx//Lz+f/y8/v/8vP5//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//Lz
+f/y8/n/8vT2//L09v/z9fT/8/X0//P19P/z9fT/8vT2//L09v/08vn/9PL5//T09v/09Pb/9PT0
//T09P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/09fj/8vT2//Hy9f/y
9Pb/9PX4//L09v/w8fT/7e/x/8jIyP/19fL/9PTx/+3u6//y8/D/7e7r//Hx7v/y8/D/8fHu//Hx
7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8fH/8fHx//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu
//Hx7v/x8e7/8fHu//Hx7v/x8fH/8fHx//Ly8v/y8vL/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+////vf////4//z79v//
//z//Pz8//r9+//6+/7/9PX4//b59//7/vz/+vr3//r7///s8///Ymh9/3eAkv/0////+P////v/
///5+/r/+vr6//v5+v/8+vv/+vr9//r9+//7/vz/+/78//r6+v/39/f/9vb2//b29v/29vb/9vb2
//b29v/29vb/9fj2//X49v/19vn/9fj2//b59//2+ff/+vf5//r3/P/6+P//9vv///b++//2/vj/
/f/+//n49f///fj///r2//r89P/1/v//d4Wn/219nv/U6PT/1+v5/ykzVv+su/b/VWWS/xgnUf8K
H1T/ABlK/0Jah/+30///LkV5/xcqW/8OGkT/iJjD/+Ly///y////5fv//7/W9P9wgqv/jp7A/+Pt
+v/1+vv/+/////v8///7/vr/8/Xx////////////7/T4//n+/////vv///r5//v7+//7+/v/+/v+
//v7+//7+/v/+/v4//z6+//8+/j/+/v7//v7+//7+/v/+/v7//v7+//6/fv/+v37//r9+//8/Pz/
+vr6//v7+//8/Pz/+fn5//X19f/y8vL/9fX1//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/k5OT/9vb2//Ly8v/09PT/9PT0//T09P/09PT/9PT0//T0
9P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//X19f/39/f/+/v7//v7+//7+/v/
+/v7//v7+//8/Pz//Pz8//v7+//6+vr/+fn5//f39//29vb/9PT0//Ly8v/09PT/9PT0//X19f/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T0
9P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/
9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9fX1//X19f/09PT/9PT0//T09P/09PT/9PT0//T0
9P/29fL/9fTx/+fn5f/x9O3/9Pbv//j69v/7+P///Pj///78///8/P//+/v4//j///9ugKb/Q1R6
/77I4P/x9f//8/X0//Dw8P/29fz/8fT//9/t/v+RosD/Kjhj/0pfmf9ui87/Fy1l/zBOif8TKFb/
PU1y/+7+///x/P//9fv///r////39/f///v9///+///+////9Pn3//j++P/6/fj//vv9///8/v/5
+v3/9fr+//P+/P/z/P//+P7///b////o+f3/scTR/xgiPf/q9///6uv///n2///69fb/8fDq/+/2
8f/t+PP/7fjz//D19v/18fv/9fH7//T09P/z9fH/8/X0//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/8fL1
/+fn5//w8PD/8vLy//Hx8f/x8O3/8vHu//Tz8P/y8e7/9fDu//Xw7v/y8e7/8vHu//Lx7v/y8e7/
8vDx//Lw8f/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vHu//Tz8P/y8e7/8vHu//Lx7v/y
8e7/8vHu//Lx7v/y8/D/9PT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1
+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//2+/3/9Pv7//j//P/0+/n/+P74//j9+//7////9PX8
//T1+P/8/fr//Pf2//f4///k9v//Kjpd/xwsTv/O4f//9fr///r6+v/3+fv/+/z///r6+v/++/3/
/Pz///r6/f/39/r/9fX4//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/0
9Pb/8/X0//D37v/w9fT/8vL///Pw///09PH/9PXq//T16v/08+z/+PL4//v1+v/17e3/+fj1/+/0
+P/z/P//XGmM/32Mrf/e6PL/0eP4/yg/dv8TKGD/hJS2/9Ti+P/W7v//PlBo/1JecP/Q1+3/8e3/
/9nZ//9QYpj/Q2Cg/xkycP8GHlf/ABpL/wsjVP8LHlP/ECFQ/2d7of/g7f//+/f////4///9/e//
8/r0/4OSrf8qOFf/OUZh/8TS5f/2////8PPx//v7/v/8+v7//Pr///z6///7+v//+/r///v6///7
+v//+vv+//r7/v/7+/v/+/v7//v7+P/7+/j/+/v4//v7+P/6+vr/+/v7//z8/P/6+vr/9vb2//T0
9P/09PT/9fX1//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9fX1//T09P/19fX/9fX1
//Ly8v/y8vL/9/f3//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/
9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/y8vL/9PT0//f39//6+vr/+/v7//v7+//6+vr/+fn5//f39//39/f/9vb2//X1
9f/09PT/8vLy//T09P/09PT/9fX1//X19f/19fX/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/
9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T0
9P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/19fX/9vb2//b2+f/59///+ff///7++//7//X/
+v/3//v+9//7+P3//vr///78///+/P///vv//9TY5/9vfp//ipu7/+fw+P/5+vP/7+7r//7+/v/1
+P//7/L5/+nt8v/p8fr/0uT5/4Waw/8LF0//ESBc/0FZhP+Ys+P/CxtM/yU0Zv+ftc//6fr+//n5
9v///vr//Pb+/93h7f9WY3L/7f7///T59//8+/b//Pf2//n2+v/7////+/////Lz8P/v9///mK/P
/xUoTP/R7v//ESBE/xMgQf/f8v//5e7+//T1+P/8+/j/8vHu//L09v/w9fn/8PX2//L09v/09Pb/
9PT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//Hy9f/x8vX/8vT2//L09v/y9Pb/8vT2//T09P/19fX/8vLy//Ly8v/0
8/D/8fDt//Lx7v/y8e7/9fDu//Xw7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y8e7/8vHu//Lx
7v/y8e7/8vHu//Lx7v/y8e7/8vHu//Tz8P/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8/D/9PT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1/P/x8vj/8vP5/+3t+/+trLf/
+vv+//r9+//v9///5u///4ORuv8mNF7/ITNl/yU1Yv9GUG3/+P////j8///5+fn///z///X6///Z
8f//Dh9C/zFGe/8gMFj/xM3f///////8+///+vr9//7////6+vr////8//Lx7v/19PH/+vn2//b2
9v/w8PD/9vb2//T09P/09PT/9PT0//T09P/09PT/9fL0//X08f/19PH/9fTx//T08f/09PH/9PT2
//T09P/09e3/9PXq//X08f/18vf/8vL1//j8///n8Pj/6Pb//46fxv8zQmv/EiJC/7LI6f/h6vL/
6e73/7zQ7/9ebo3/v8bZ/+rp9f/s7Pr/5un2/+Dq7f/n7fL/7uv0/+ro/P+Ll7b/JDRS/x0vUf9I
XoH/kJ7A/9fg+//u+v//ytjs/254nf+SmL7///z///n2+P/5/v//1OT3/1Jtlv8qRHT/jKTX/0lW
d//u+v//+f////r9+//7/fb/+/v4//z9+v/29vP/+v34//7////5+/r/+v37//r9+//7+/v/+/v7
//z6+//8+vv//Pr7//z6+//6+vr//Pz8//v7+//5+fn/9fX1//T09P/09PT/8vLy//T09P/09PT/
9PT0//T09P/09PT/9PT0//T09P/09PT/8vLy//X19f/19fX/9fX1//Hx8f/Ly8v/8fHx//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T0
9P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/19fX/9fX1//X19f/19fX/9fX1
//X19f/19fX/9fX1//T09P/19fX/9fX1//T09P/y8vL/9PT0//X19f/19fX/9fX1//T09P/09PT/
8vLy//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T0
9P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/
9PT0//T09P/y8vL/8vLy//Ly8v/09PT/9PT0//T09P/09PT/9PT0//Ly8v/y8vL/9vb2//f39//3
9/f/+fn5//r6+v/7+/v/+/v7//v7+//59/7///7//9LT2v/n6vf/+P///7i/0v/c4e3/7/T4//n/
/v/6//7/9vf9/8TL3v9xf6P/mafL/+rs/f/39fb/9fX1//H2+P/s9vn/7vT4//Xy9//18vT/6vHu
/9/r7v+7yN7/6vn//+j1+//V5fD/eoux/yYyWP9MWHr/8Pr///P6///2/v//8/r//8zd//8ZLEr/
mLLS//H8/////vv///z8//v29f/6+v3/+/v+///69v/v8///ZoGy/wceUv8OIF3/DRxO/0JUd//k
9///6fX4//H29f/z9fT/8vL1//Xy+f/08vv/8vP5//L09v/w9fT/8/X0//Lz+f/08vn/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/09fj/9PX4//L0
9v/y9Pb/8vT2//T1+P/x8vX/7e/x/8rKyv/19fX/8PDw//Hx8f/x8O3/8fDt//Tz8P/19PH/9fDu
//Xw7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/
8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/x8fH/9PT2//Lz+f/y8/n/8vP5//Lz+f/y
8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz
+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5
//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/
8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y
8/n/8vT2//P19P/x8vX/8fL5//Lz+//x8vj/8fL5/+3t/v+trLr/+vv+//r9+/8OIFH/CxtL/x0u
Xf+owPb/vM/5/7zL8f9HU3T/sLza/+/1/f/7////9P7//87d9f8gLDz/x97//6O16f8hKk//f4yh
/+72///8+/////r///r6+v/7/vz//Pr7//b18v/w8O3/9vb2//T09P/t7/H/9vf6/+3v8f/y8/n/
8vT2//T09v/09PT/9PT0//T08f/19PH/9fL0//jv+f/38vT/9fTt//T16v/09PH/9PT2//Xx+//0
8vv/9PX4/+Ts9P/V6P//Hy1I/2R4q/8yRHH/ESE5/8DT7P/k6Pn/7ez0/+zq6//s6uv/7Ovz//Hw
+P/y7PT/5+fn/+Pr4v/r+O3/6u/w/+vu9v/p7/T/3+jt/+bq8f/o6u//8vDx/+/s7v/w9vr/8///
/5Gfs/9rd4z/vcve//D+///i7f//cX6i/3aKnf/k+///tsPn/1peff/KyNv//v////X7///4////
+P////n////x+fb/9Pn3//7//P/2+fL//f73//3+9//8/fr//P36//z8/P/8/P///Pz///z8///6
+v3//Pz///v7/v/39/r/9PT2//T09v/09Pb/8vL1//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T0
9v/09Pb/8vLy//X19f/y8vL/9fX1//T09P/Ozs7/8vLy//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/
9PT0//T09P/09PT/9PT0//T09P/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//Ly9f/0
9Pb/9PT2//X1+P/19fj/9PT2/+3t8P/n5+r/7+/v//Hx8f/19fX/9fX1//Ly8v/y8vL/8vLy//T0
9P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0
//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/
9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/0
9PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T09P/09PT/9PT0//T0
9P/19fX/9fX1//b29v/39/f/+vr6//v7+//8/Pz//Pz8//z8/P/8/Pz//Pz8//z8/P/7+/v/+/v7
//v7+/////z//f73/9Xb0v/m8/X/tMHi/y85Yf9CTHz/Mz5o/y46XP+Jmrr/8P7//9Lg9/9jeJL/
eYyh/+3x/v/x7/D/8/ft//D46v/w9+7/8fL1//Lv///y7///9fL5//T09v/29f3/7Ovy//T17f/1
/PP/6fH6/6y3x/9ETF7/7////8/m//8KGDT/HStQ/2d8sP8OIEf/UGaP/9bl/f/1+/////v////6
/f/7+P3/9/j//93i8f+fr87/V3Gr/wkdUv8UJFb/ssX3/+n3///v9///7PH1//Hy+P/5+v//8fH0
//Xy9//18vf/9PL7//Dz+//v9vb/7/bz//T09v/18vf/9PT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/9PX4//T1+P/09fj/9PX4//T1+P/09fj/9PX4//T1+P/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/9PX4//L09v/y9Pb/8vT2//T1+P/y9Pb/
8PH0/9HR0f/w8PD/8vLy/+/v7//x8O3/8vHu//Tz8P/x8O3/9fDu//Xw7v/y8e7/8vHu//Lx7v/y
8e7/8vDx//Lw8f/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vHu//Hw7f/x8O3/8fDt//Hw
7f/x8O3/8fDt//Hw7f/w8PD/8vL1//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL1//L09v/x8vX/8fL5
//Lz+//w8fj/8fL5/+3t/v+trLr/+vv+//r9+/8aK0b/W26L/7LE2f/t+f//6+/8/9nf9v9MV37/
rrnl//r////0/P//w9j2/yMzSP/r+///6vX//+Lp//91faH/c4Sb/+/////79/////X5//n2+v/2
9vn/8e7z//Xy+f/y8fj/8O73//Dx+P/O0dv/aGpz/9zg6f/w8///8PP9//Dz/f/y8/v/9PL7//Ty
+f/18vn/9fL5//fx+//18vn/8/Xx//D19P/w8/v/8vP7//Xy9P/18vT/+vj//+fs+/9ETWb/pK/U
/9jl///BzuT/2+Lz/+zw+v/l6O//6Ors/+zq6//w7fL/5ejy//D1///v7vr/5OXs/+fs8P/r7O//
9+zw//Hs7v/i7+n/4vDt/+vp8v/t5/H/7OPu/+3p8//l7fn/6fn//8rY6f9fa3//NUZj/4GSwf96
iL//b3ek/7jA1v/l8vv/wtni/1hugf8pOFv/nbDj/8LS/v9XZIL/Tlhx//P8///z+v//+Pv///X2
/P/6+vr/+vn2//z48//6+fP/+vn2//n5+f/5+fn/9/n7//f5+//6+v3/+/v+//r6/f/29vn/8vL1
//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/9PL5//Hw9//x8Pf/
9PL5//Hw9//18/v/9PL5//Hw9//08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/0
8vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty
+f/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//Ly9f/y8vX/8vL1//Hx9P/x8fT/9PT2
//X1+P/19fj/8fD3//Lx+P/y8fj/8vH4//Lx+P/y8fj/8vH4//Lx+P/08vn/9PL5//Ty+f/08vn/
9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/0
8vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty
+f/08vn/9PL5//Ty+f/08vn/9PL5//Ty+f/08vn/8vH4//Lx+P/y8fj/8vH4//Lx+P/y8fj/8vH4
//Lx+P/y8fj/8fD3//Lx+P/y8fj/9PL5//Xz+//29fz/9/f6//n5+f/6+vr/+vr6//v7+//7+/v/
+/v7//r6+v/6+vr/+vr6//r6+v/6+vr/+vr6//r6+v/6+vr/+/v7//z6/v/68/3/+/f///b7///z
////YXSV/yg6Y/9kfan/kK/d/2qIs/8nPWL/YXKm/4WXz/8zR3P/b4So//b7///q5+n/8vH5//Lu
/v/17P//9+/+//P19P/x9PD/9PHz//fy9P/19PH/8/Xx/+759//k8ff/7/b//7zE5P9XZYD/nrXZ
/3aUwP8dMlz/kKjk/x8uWv+zyv//N0Zq/4WVs//0////+ff////8///y8/v/7/v//4ylx/8MIEf/
CRtT/w8iVv9hcpr/6/b//+/w8//8+/j/7uv0//Hu/v/08///8vP5//X08f/19PH/8PP7/+z1/f/r
+Pn/7fj2//T09P/18vT/9PT2//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz
+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5
//Lz+f/y8/n/8vP5//Lz+f/y8/n/8vP5//Lz+f/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8vP5//Lz+f/x8vj/8fL4//Lz+f/y8/n/8fL1//Hx9P/v7+//8fHx/+zs
7P/08/D/8O/s//Lx7v/y8e7/9O/t//Tv7f/x8O3/8fDt//Hw7f/x8O3/8e/w//Hv8P/x8O3/8fDt
//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/w8PD/
8vL1//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL1//Hy9f/x8vX/8PH4//Lz+//w8fj/8fL5/+zs/f+t
rLr/+fr///n6/f/o6PP/9fb8//Dz7v/z9fH/9Pn6/9Hh8P9IZ4j/GzRW/9Tf///09v//1N///yIs
Rv/l8vv/8P74/+jz8f+frLz/FyRG/36Rwf/z/P//+vv///bz+P/59vr/9fb9/+zw9//09vL/7/bz
/+n2//97kKj/DCBG/0ponv+Dm8j/na7P/7CzzP/p6P7/8vT///D2///u8uj/9vfo//Xv6//27vT/
9/b+//Hy+P/z9Ov/9Pbv/+z1/f/m8f7/7PX9/6qzv/9OVW3/ztPv/+rn9v/u6/T/7er6/+3t+//q
6/L/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr
8P/n6/L/5Oj4/+ru+//09PH/8vPw//P5/f/h6///YnCZ/xcjSv9IV4P/sL3g/+zv/P/t7On/8fHu
/9vj7P+Lnbr/MEVm/zxUf/8iNF7/RFWA/87d///v9v//+P7///D////w/Pf/+fjy///59P//+v//
//r////x9P//+/3/8fL4//r7/v/28+n///74//r3/v/39v//7/L5/+/1+f/w9vr/7vX1/+/08v/y
8vL/9PHz//Tx9f/z7/z/8+/6//Tx9f/08/D/8fH0//Dw8//29vn/8vL1//Dw8//d3eD/8PDz//Ly
9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vH4//Pv/P/y8fn/8fL1/+/08v/x8vX/8vL1
//bw9f/28fP/8O/p//Lz8P/z+vr/7Pb6/+z1///z+P//8vLy//Dv7P/y8vL/8vLy//Ly9f/y8vX/
8vL1//Ly9f/y8fj/8vH4//T09v/y8vX/8vL1//Ly9f/09PT/9PT0//T08f/09PT/8vL1//Ly9f/y
8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly
9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1//Ly9f/y8vX/8vL1
//Ly9f/y8fj/8vH4//Lx+P/y8fj/8vH4//Lx+P/y8vX/8vL1//T09v/09Pb/8vL1//Ly9f/y8vX/
8vL1//Ly9f/y8vX/8vLy//Ly8v/y8vL/8vLy//Ly8v/09PT/9PT0//X19f/29vb/9/f3//n5+f/6
+vr/+vr6//v7+//6+vr/+vr6//v69//6+vr/9vv///X7///1/ff/9v33//v4/f/7+P3///74//f5
+//z+v//eYGY/5mitv/b4/H/+vr///z6///8+v//9vL8/+Tl7P/u9///N0le/5+3yv/o9PL/8Pjy
/+z3//+Kmrj/Q1Z9/2Nzov+rp9n/5+L//+Ty7P/p++j/7vXw/+/09f/x8vj/8fL5//Hy+f/x8vn/
8fL4//H08v/r7un/9vn1//P49v/r8ff/7vb//9be9/+Bh6j/MjhY/36Ltv+6xur/9vr//+zt9P/o
6///tsHj/25/rP87SG3/hYuf//j7///i6f3/1+r//0ttpP8AGkj/P1J5/9Hf/v/s8f//8PH3//Hy
+P/x8vj/8vP5//Lz+f/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8vP5
//Lz+f/x8vj/8fL4//Lz+f/x8vj/7/Dz/+Dg4//x8fH/9PT0//T09P/v7+z/8fHu/+/v7P/y8/D/
8PDt//Dw7f/w8O3/8PDt//Dw7f/w8O3/8e/w//Hv8P/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x
8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/x8O3/8fDt//Hw7f/w8O3/8fL1//Hy9f/x8vX/8fL1//Hy
9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy+P/x8vj/8fL4
//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/
8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x
8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy+P/x8vj/8fL4//Hy
+P/x8vj/8fL1//H08v/x9PL/8fL4//Lz+f/x8vj/8fL4/+zs+v+trLf/+fr9//n7+v/u8On/8/Xx
//T1/P/08///7fH4/+vy//+2xe3/Mj5i/zRBWf/V5v//m6rR/0pWc//v+///7PL4//P3+f/r8v//
0eH//xMdUP84SH3/P093/5epwP/t+f//8vL///Xy///s8f//5fP//5Gq3f8MHUr/ZX63/xIkUf87
TYn/ChdE/xAfPv/i9f//8PP///Ht/f/x6///8fP//97q//+escv/vM/r/9jm///m7f//9vT////z
9f/08fj/1ej//0Raev+GmbP/1OT0/+Dr8v/m8fD/5fPt/+b07v/p7e//6+zy/+vs8v/r7PL/6+zy
/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/s7O//7+7r//Tv7f/08fX/
9vf9//T3///v9///5/H//+/5///v8///9Pf///Ly9f/v7O7/8vL1//X2/P/q8vv/6/b//+rw+P/T
2/b/TFeP/w0YTf8ZKVr/cIWs//L////7//X/+frz//v7+//6/v//8fz//+z++v/o+/D/8v/v/+/6
8//q9v//1OL1//H8///x+fn/7e70//r3/P/08/D/9vXv//T08f/w9fT/7/X7/+/1+//v9vP/8PX0
//Dz+//y8/v/9fP7//X1+P/y8vX/8vL1//f3+v/CwsT/9vb5//X1+P/09Pb/9PT2//T09v/09Pb/
9PT2//T09v/09Pb/9PT2//Xy9//09PT/8/Xu//D37v/w9fn/8vL///Xv///17///7+30//X88//r
+Oj/6vfq/+z08f/v9Pj/+vb///Ls9v/09Pb/8/X0//P19P/z9fT/8vT2//L09v/y9Pb/8vT2//T1
+P/y9Pb/8vT2//L09v/09fj/9PX4//T1+P/y9Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2
//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/
9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/08vn/9PL5//T09v/0
9Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT2//T09v/09Pb/9PT0//X1
9f/29vb/+fn5//r6+v/7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7//v7+//7+/v/+/v7
//r7/v/6+/7/+vv///j8/v/4/vj/+P74//v7/v/7+/7/+fr9//b///+rweP/Gy9N/yhAXv+1z+j/
+P////r89P/5//T/7/7+/3F+n/8tOGL/Lzxq/7XC8f/p7///8PX2//H5+f/r9vL/6vjv/+718v/y
8fz/7ur6//Hv+//09fr/8PX0//D28f/z9fT/8vT2//Lz+f/y8/n/9PT2//T09P/x8e7/8fTt//P1
7v/x+PL/8fb4/+/1+//t8v//7fL///P6+v/x+PL/8fTw//X18v/w8er/7/Hw/+r2+f/D2Oz/GS5O
/4+z8P9MbKz/Cx5M/zhIbf/l8v//6+/8//L09v/09fj/9PX4//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/8vT2//T1+P/y9Pb/8vT2//L09v/x
8vX/7e/x/8rKyv/19fX/8fHx//Hx8f/x8e7/8fHu//Lz8P/w8O3/8fHu//Hx7v/x8e7/8fHu//Hx
7v/x8e7/8vDx//Lw8f/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu
//Hx7v/x8e7/8fHu//Hx7v/x8e7/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//P19P/z9fT/
8fL4//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//v8PP/9PX4//L09v/1+Pb/7/Xw//D19v/v
8///ydXx/x8yTv/A5P//fJO//2V1lf/q9v//7/X5//Lz8P/08vn/2N39/4KOuv8eMlz/DSFH/xcq
R//d9///2vP//3GJrf8JG1H/CRpa/wsbT/96jLz/3+T//+3t+//p7fr/3Or+/0tfe/87UW3/4v7/
/6C6y//C3fb/JThZ/xIkVP8mPnr/DSBR/x0xYv8NG0f/TGCM/9nu//+rvdn/LTpX/4SStP/h6///
5Oj4/+zp/P/t6fn/8uz2/+3n7//s6/L/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r
7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/s7O//9u/v//Hs6//19vn/7PL3/+76/f/x+/7/7vDv//f2
8//59PD/9fTu//X48//u8/H/8fTy//b3+v/08fX/8PDw/+rz6f/t+vX/8fn//+rz//+vweT/Tl1y
/83b2//y//P/8//3//P++v/7+/7/9vT//6qz3f8WIEr/HS5d/0Vgmf8uR3z/ESZM/yY5Uf/D0+X/
7vP8//r6/f/28PX/9/H3//Ty+f/w8/v/7/X5/+/29v/v9vP/8PX0//Ty+f/08vv/9fb8/+3v8f/y
9Pb/8vT2//T1+P/x8vX/9PX4//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//Xy
9P/09PT/8/Xx//D19P/v9fn/8PP7//Ly/f/y8/v/8/f5/+z09P/p9fj/sb3F/7K6yf/s8f//8fD4
//f1+f/09PT/8/X0//P19P/z9fT/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//L09v/09fj/
9PX4//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//T1+P/y9Pb/8vT2//L09v/09vX/9fj2//j6+f/5+/r/+/78//v+/P/6/fv/+v37//r9+//6/fv/
+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+P37//j8/v/4/P7/+v34//v7+P/6
/fj/+v37//r7/v/6+///8fn//2Nyjv8rRG//Une0/xg2av8WLVT/usbh//r6///4/v//8P///ztM
df9ccKL/prPT/97m9P/09fj/9fXy//Lz+f/19fj/8vHs//f28f/x8vj/9PX8//Ly9f/29vb/8/Xx
//D28f/y9Pb/8vP5//Lz+//y8/v/9PL7//Ty+f/19fj/9fX1//Ly8v/x8e7/8/Xx//b59//1+Pb/
8PH0//Lx+f/18/z/8e/w//f28f/w8ub/8/ft//b3/f/L1PT/IC5m/wocXf8GHFr/GS1d/+Xt///x
8Pf/9/b+//Lx+f/09fr/9PX4//L09v/y9Pb/8vT2//L09v/09fj/9PX4//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/8fL1//T1+P/y9Pb/8fL1//b29v/09PT/8fHx
//Ly8v/v7+z/9vbz//Dw7f/y8/D/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8vDx//Lw8f/x8e7/
8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x
8e7/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/x9PL/8fL4//T1+v/x8vj/8vP5/+3t
+/+trLf/+vv+//r9+//09fr/8fL1//T28v/09vX/8vL9//Hx/P/v9PX/3+/3/5Ct1P80TXj/TGCM
/3mHqf/p8///8fTy//Lz8P/5+PL//Pv4//P5/f/d9P7/0Or//xcmRP/h+f//0e3//wwfOf8YNWr/
Bx5S/w8cQ//f6v//9vf+/+Xi5P/q6ff/6/P//9bm//8mNl3/TGWe/xAkU/8dK1f/W2iN/9nj+P/p
8/3/3+v5/97x///P6P//T2qY/wskT/8LH0P/ZG6I/9bY6v/n7Pv/5e35/+Xt+//n6vf/7e3w/+/s
7v/s7O//6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/q6/D/6uvw/+vs8v/r7PL/6uvw
/+rr8P/t7PP/8u74//Lx+P/v9vb/7vn1/+348//v9vP/9PL5//Xy+f/18vn/9PT2//D19P/t+PH/
7fjx//D19P/18vn/9fH7/+3x+//u9Pn/7PHz//H3///Fy+r/dHqe/5GVuv/v+f//zt3z/01ZZv+u
tcv/6vP//3N+rf9oeav/gp7F/2iJsP8aMl3/w+f//01ij/9DUnH/5vX///P4///19P//8O39//Pw
///08vv/8/Xx//P18f/09Pb/9fL5//fy9P/38vH/9PT0//Hy9f/19vn/9fb5/+3v8f/19vn/8fL1
//Hy9f/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//T09v/y9Pb/8PX5/+/1+f/w9fb/
8PX0//P37f/z9+3/7/Ty/+75//+0v+b/Q054/xwlS/+2xer/4PD7//D7+v/w9fn/8PH3//f4/v/2
9/3/9PX6/+/w9f/29/r/9vf6//L09v/y9Pb/8fL1//L09v/y9Pb/9PX4//T1+P/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//Hy9f/09fj/8vT2//Hy9f/x8vX/8fL1//L09v/09fj/9fb5//j6+f/5+/r/+fv6//r9+//6
/fv/+v37//r9+//5+/r/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9
+//6/fv/+v37//r9+//6/fv/+v37//r9+//4/fv/+v32//r99v/7+/j/+/v7//r7/v/0/P//5fP/
/yUzWv8NIEj/b47M/x8zZv8NGUH/hJC8/+Dl///+/v//9Pj//z1Ja/+ktt//7Pf///P19P/x8fH/
9PT0//L09v/y9Pb/9fTx//T09P/v9fv/7PX9//Dz+//w9fn/8vP5//Lz+f/y8/n/8vP5//Lz+//y
8/v/8vP7//Lz+//y8/v/8vP5//Lz+f/y9Pb/8vT2//P19P/z9fT/8/X0//L09v/x8vX/8vH4//L0
9v/w+Pj/8Pj4//D28f/v9PX/5Oj5/5KWr/9WXXX/7Pf//+ry+//s9PH/7/33/+v58//w9fb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
9PX4//T1+P/y9Pb/8fL1//L09v/y9Pb/8fL1//Hx8f/19fX/9fX1/+/v7//09PH/8fHu//Hx7v/w
8O3/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8vDx//Lw8f/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx
7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//09vX/
8/X0//X2+f/w8ff/9PX6//T1/P/v7vr/9fr//9Hj+P9IV2n/h5Kp//D3///q7ff/8vT2/+/09f/r
8O//9fX1//T09v/x9vr/2uby/xsmPP/a8f//nq/c/ztJav/j9///3vH//+Du///m7///4eXs/+vr
7v/n5en/8O/7/+Du//9xgKH/NUJn/6i24f/b4Pv/8PH4/+rp4v/y7+L/9e/p/+3r7//n7Pv/2+X9
/7TA3v/h6v//4uby/+/w8//m5+3/5+zw/+ny9//j7O//6Ors/+/v8f/r7PL/6+zy/+vs8v/r7PL/
6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+zt8//r7PL/6uvw/+vs8v/v8PX/8vH4//Ty+f/y
9Pb/8/X0//P19P/y8vL/9fL5//Xx+//08vv/8vP7//D1+f/w9fb/8PX2//P19P/09Pb/9fL0//bx
8P/19O7/8/nw/+n38f/Z5PH/kqLA/y0+bP8tQXn/HjFn/w0gUf8uSYP/IThp/xooTf+ks9b/7vf/
/+Ts+v/J0ef/4+///93m//+dpb7/Qkpc//P8///s9f3/7/b2//D19P/z9fT/9PT2//T09v/09Pb/
8vT2//P19P/z9fT/8vT2//T1+P/w8fT/8vT2//X2+f+/wcP/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/w9fb/8PX2/+/1+f/y8/n/9PT2//X08f/09PH/7/T1/+ny
//+Glrj/ZXao/0Zajf8XJk//orzi/3WJnv+6wND/7e34//X0///19v3/9PX8//T1+v/19vn/9PX4
//P19P/z9fT/8fTy//P19P/z9fT/9Pb1//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/9PX4//T1+P/09fj/9fb5//b3
+v/5+v3/+vv+//r7/v/6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37
//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/+v37//r9+//6/fv/
+/v7//z6+//7+/v/+P37//j9+//8+vv//Pr7//v7+P/z/v//orfc/0BUeP+Qo8L/3ez///P4//+h
qcL/WWiF/7XI5P/x+f//2Nvw/zpGX/+nutX/5vb//+/5/P/s7Pr/9vT///P19P/w9vH/8/X0//L0
9v/y8/v/8vP7//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8/X0//L09v/y9Pb/8vP5
//Lz+f/y8/n/8vT2//L09v/y9Pb/8/X0//X18v/z9fH/7Pb5/+v4+f/v9PX/8vLy//H08v/x9PL/
8/j2//T28v/w7+z//vv9/+3u9v/w8/v/6vHx/+718v/w9fb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/x8vX/8vT2//T1
+P/x8vX/7/Dz/8nJyf/w8PD/8vLy//Ly8v/w8O3/8PDt//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu
//Hx7v/x8e7/8vDx//Lw8f/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/
8fHu//Hx7v/x8e7/8fHu//Hx7v/x8e7/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z
9fT/8vP5//T1+v/x8vj/8vP5/+3t+/+trLf/+vv+//r9+//x8vX/8PH0//X2+f/x8vX/8fTy//T1
+P/08v3/9PL9//Dz+//v9fn/7/bz//D19P/z9fT/9PT2//Lx+f/y8fj/8fTy//T7+f/j8PP/uMzf
/xopUP+xyv//ER9G/4KRvP/j7///5fD8/+Xq7v/v8fD/5+Xm//Hv8P/t7On/6+7s/+Xv8v/k7/b/
5e/z/+ns8//s6/L/7Ovy/+vs8//r7PP/6+zz/+vs8//r7PP/6+zz/+zr8//s6/L/6+zy/+vs7//s
7O//7Ozv/+vs8v/r7PL/7Ovy/+zr8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6+zy/+vs8v/q6+7/6+zv/+/w8//x8vX/8vT2//L09v/y9Pb/8vT2//T09v/09Pb/9PT2
//L09v/y9Pb/8vP5//Lz+f/y8/n/8vT2//L09v/y9Pb/9PT2//Xz+//18/v/8PX5/+/1+f/v+f3/
6vP//9no///I1/z/wdD4/x8oRP+Uosn/q7fY/+bv///w9v//8PH0//f39//48vj/8PDz/+357v/f
8PT/XWiP/214pP/t+f//6vX0//H08P/5+vP/8PPu//P19P/1+vv/7/Dz//f3+v/w8O3/6+/l//j5
8P//+v//8ur5//H1/P/P1dn/7fH4//Lz+f/5+fv/7+/v//P57//z+e//7ezp//z6+//w7vb/9fP8
//Ty+//08vv/9fL3//T09v/z9fT/8/X0//X08f/08vn/6e///+////8oN1H/nLTU/9fq//9YZ4L/
ITJV/zdKcP94iKX/1d/3//Hz///w7/v/8fb4//H08P/19O7/9vXu//X07v/1+PH/6/Pt//P69P/y
8vL/9fX1//j69v/z9fT/9fL3//Xy9//08vn/8vP5//D1+f/v9vb/8PX0//D37v/0+O7/9PXt//P0
7f/y8/D/8/X0//L09v/w8/v/7/L8//Ly/f/08v3/9PX4//P19P/z9fH/8/Xx//T09v/18/v/8vH5
//Lz+//09fr/8/f5//T59//5+/f/+v37//v7+P/8+/j//Pv4//z7+P/7+/v/+/v7//v7+//7+/v/
+/v7//v7+P/7+/j//Pv4//v7+P/7+/v/+v37//r7/v/4/fv/+P71//r99v/8+v///Pj///z4///7
+v//9v77//j+9f/79e////34///99f/2+PH//v////X2+f/3+fv/+/r////0////+///9fj2//r/
///59/////z///fz/f/8+///gYWu/3V7nv/b5u3/9P3z/+vw8f/r9v//h560/2iDnf/A3fz/jqXB
/15wgv+/0uD/6/j5/+zx8P/w8PD/9vbz//P19P/w9fb/7/L5//Dz/f/w8/3/8vL9//Hw+P/v7fT/
7Ovy/+vs8v/r7O//6+zv/+vs7//r7O//6+zv/+vs7//t7/H/7e70/+/w9f/v8PX/8PH3//Dx9//x
8vj/8fL4//Hx9P/x8vX/7/T1/+/09f/x8vX/9PT2//Lz+f/y8/n/8fb6//H2+v/09fj/9PT0//Lz
+f/y8/n/8fL4//Hy+P/x8vj/8fL4//Hy9f/x8vX/8fL1//L09v/y9Pb/9PX4//L09v/y9Pb/8vT2
//L09v/09fj/9PX4//P19P/x9PL/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//Hy9f/y9Pb/8vT2//L09v/x8vX/8PH0/9fX1//x8fH/
8PDw//X19f/19PH/7+7r//b18v/t7On/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y
8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y8PH/8vDx//Tx
8//y8vL/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5
/+7s+/+urLf/+/v+//v7+//v8PP/9PX4//T1+P/x8vX/9fb5//Dx9P/08vn/8vP5//L09v/w9fT/
8Pbx//D28f/09Pb/9PL5///4///r6O//+vr3//X99//g7+//0+j5/w4aOv8NGkH/ICxK/9vt///f
7f//6/L//+rr8v/v7PD/6uXm//Dt7//s7O//6e3y/+ns8//n7fb/6ezz/+vs8//s6/L/7Ovy/+vs
8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy
/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/q6+7/
7O3w/+/w8//y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//Hy9f/09fj/9PX4//L09v/v9PX/7/b2/+70+f/q8vv/6vL+/77G
1P/1+v//7/L///Lz+//w8fT/8PPx//b28//y8vL/5+fq//v8///w+f//2un2/1RieP9dao//vMnt
/+Tt8v/u9O7/7/D3/+/y/P/t8fv/7vL3//n49f/5+fb/8vb9/+3x+P/t7e3/9fTu//X18v/09fj/
7O30//L2/f/3+fv/7Ozs//Xy+f/49P//9e////Hv+//s9PH/8Pjy//L09v/08vn/9fL0//T09P/y
9Pb/8/X0//X07v/09Pb/4ur//0lTcP9sfZX/z+L0/+Tp8v/h5vL/3On//36Nqv9peo3/xtbl/+z1
/f/z9/z/9fr+/+zx9f/w8/v/7PD3//P4///r8fn/7PD6//Du9//99/3/+vL4/+/s8//29fz/8vT2
//P19P/z9fT/8vT2//Ly/f/y8v3/9PT2//T08f/09PH/9PT2//Xz///08vv/8vLy//P07f/08+3/
9PPw//T09P/09PT/9fXy//T17v/19u//9Pbv//f49f/5+fn/+/r///v6///7+v//+/r///v7/v/8
/Pz//Pz8//z8/P/7+/v/+v37//r7/v/6+/7/+Pz///j8///6+/7/+vv+//r7/v/7+/v/+/v7//z7
+P/7+/v/+/v7//v7+//7+/j/+/v4//v7+//8+v//+/r///r7/v/6/fv/+/v7//z6+////vz/8vP5
/+j2///i8v//+/////r///8+SWn/bXuk/+zz///5+v3/+//w//j96f/7//j/6fTy/+v9///s////
gpGu/2x6kv/Y5ej/6/by//D2+v/r7///4+n//4SMtP83RW//Dxs+/3yLs//c5f//8vb///Tz///0
8fj/8vLy//T09P/w9fT/8PX2/+z08f/r8O//6+7p/+zu5//s7On/6+zv/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6+zy/+vs8v/s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+vs7//r7O//6+zv
/+vs7//r7O//6+zv/+vs7//r7O//6+zv/+vs7//s7fD/7O3w/+zt8P/t7/H/7e/x/+3v8f/v8PX/
7/D1/+/w9f/w8ff/8fL1//Hy9f/y9Pb/9PX4//L09v/y9Pb/8vT2//Hy9f/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/0
9fj/8vT2//Hy9f/x8vX/8vT2//T1+P/09fj/8vT2//Ly8v/t7e3/9fX1//b29v/y8e7/8fDt//Hw
7f/y8e7/9fDu//Xw7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y8e7/8vHu//Lx7v/y8e7/8vHu
//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y8PH/8vDx//Tx8//y8vL/9PT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8vP5//T1+v/x8vj/8vP5/+7s+/+urLf/+/v+//v7+//0
9fj/9PX4//X2+f/y9Pb/8vT2//Hy9f/z9fT/8/X0//P19P/z9fT/8/X0//L09v/08vv/9PL9//33
///v7PP/9PPw//H08P/r8/D/3Ofx/9Tg/P9mcYv/3uj9/+Dr9//l6/P/6u30/+3s8//w7fL/7Obr
/+/s8//s6/P/6+r2/+js9v/o7Pb/6ezz/+nt8v/s7O//7Ozs/+vs8v/r7PL/6+zy/+vs8v/r7PL/
6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r
7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7O//7O3w//Dx9P/09fj/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//X1+P/09Pb/8vLy//H08v/x9PL/7/Ty/+/08v/v9PL/7PHw//P3+f/19vn/7O3z//Ty+f/x8Pf/
8fH0//r6/f/x8vX/9vf9//Xz///w7/v/6fDt/9nm6f+ru9r/OUVr/xglRP/e8f//6vX///L2///x
7v//9fP8//X57//09+f/9vDq//Hr5f/x9en/9Pry//Dz+/+9xN//JzJY/xMiR/+En8D/mq/D/+/y
+f/17vT/9+/+//Ps+v/39vP/9vXu//fy8f/19PH/9PTx//P18f/y8/n/9PT2//T17f/w9fn/e3+j
/3J6oP/Q3u//3ebp/+/v7//r6Or/8vP7/+Tt//+Bj7X/bHyh/7rH5f+vvuL/PU98/wsZQP97jLL/
0+T//8bT8f9ZZID/Q1Bx/73M5v/3+fv/9PDm//Tz8P/19fX/9PTx//T17v/09+f/9PXt//Ty+f/0
8vv/9PT2//Xy9P/18vT/9PH1//bu/P/18fv/9fX1//X49v/w8/3/7fH7//T1+P/3+PX/+/n6//z6
+//8+vv/+/v4//r99v/4/vX/+P74//r9+//8+v////j////4////+P7//Pr7//v7+P/7+/j/+/v4
//v7+//7+/v/+/v7//r9+//6/fv/+vv+//j8/v/4/P7/+Pz+//r9+//7+/v/+/v7//z7+P/8+/j/
/Pr+//z6/v/7+/7/+/v7//j++P/6/fj//Pr7///4/////v//8v7//xIjQ/8fNVv/h5y//9nw//8R
JV3/ABdT/zFHfP9jd53/y9Xt/+zz///2////iZW0/yAtVv8vP27/Kzhj/6Sy2f/d5fz/6/H5//H2
9f/09PH/9O/t//78//+0u9P/rLfT/8LJ4v/i5/j/8fH8//r4///59vj/8vLy//T09P/x8vX/6/D0
/+rv8//r7PP/6+zz/+zr8v/s6/L/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/
6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r
7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6+zy/+/w8//w8fT/8vT2//T1+P/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/9PX4
//L09v/x8vX/7/Dz/8/Pz//y8vL/9vb2//Hx8f/08/D/7+7r//Lx7v/08/D/9fDu//Xw7v/y8e7/
8vHu//Lx7v/y8e7/8vDx//Lw8f/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y
8e7/8vDx//Lw8f/y8PH/8vDx//Tx8//y8vL/9PT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P1
9P/z9fT/8vP5//T1+v/x8vj/8vP5/+7s+/+urLf/+/v+//v7+//y9Pb/8fL1//X2+f/x8vX/9fb5
//Dx9P/z9fT/8/X0//P18f/z9fT/8vT2//Lz+//08v3/9PL9//Xy+f/19fX/9fX1//Dz8f/s7fP/
6ezz/+ft9v/n7fb/6e3y/+vs7//r7O//7Ozv/+zr8v/t6/L/7enz/+3p8//s6vb/7Ovz/+vs8//r
7PP/6+zy/+vs8v/r7O//6+zv/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy
/+vs8v/s7fP/6+zy/+rr8P/r7O//7/Dz//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//Ty+f/08vn/9PL5//Ty+f/y
8/n/8vT2//L09v/z9fT/8/X0//P19P/y9Pb/8vT2//Ty+//08vv/9PL9//Ty+//08fj/8vL1/+/1
+//v9fv/8vH4//Ty+f/q7fT/1OL4/yw+av8SIk//Ii5K/+ry////+P//8Ojo//D19P/1+vn/9/D1
//Xx/v/Y5P7/2e7//+L4+P+yyND/Dxw5/3aNzP8NHFP/DRlD/9ff+P/6+///8Oz2//Lx/P/w8/3/
7PL7//Ty/f/5+P//3ubu/+nx+v/w8/3/7/D1//r9+P/u8/z/Jy1M/8PM+v/g7Pr/4+7s/+fs7v/p
7e//6u30/+ru/v/i6///zuH//y9Hcf8rR3n/GTBl/yQ6c/88U4f/s8///zpNdv+Vrtv/cIe4/1dt
lv96lrX/wdnx//D7///w7vr/9+/+//rz/P/z9O3/8Pjq/+r36//p9PD/6vHx//P19P/x8O3/8u/o
////9f/r7eX/8v37/9jo+v9bbJT/JjJX/5Cbsv/w9f//+vf////6/////P///vv///r9+//2/ff/
+P74//7/+f/++fT///f3///6+//19fj/9P7///T8///7////9vb5//fy9P///vr//fTv///99P//
/vj///31//v7+P/6/fv/+Pz+//j8///6+/7/+vv+//v7+//7+/v//Pr7//z6+//7+/v/+/v7//z6
///7+v//+v37//r9+P/++///9Pv//xYmRf9HY5z/Ch1V/yxEhP8qPnL/UWmj/w4iXv8QIl3/Ex5L
/8TT///l9v//O0dj/62+4v/d7v//5/H///j7///x8vX/8fTy//T5+v/r8PH/7/Dz//b2+f/z+Pb/
7PHw/83Tzf/l5+P/8/Xx//j58v/x8e7/9PTx//H08v/v8PP/6+zy/+rr8v/r6vb/6+r2/+vq+f/r
6vb/6+zz/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy
/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/s7fP/
7/Dz//L09v/y9Pb/8fL1//L09v/09fj/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//Hy9f/x8vX/8vT2//L09v/w8fT/7/Dz/8vLy//x
8fH/8fHx//Dw8P/29fL/8fDt//Tz8P/x8O3/9fDu//Xw7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw
8f/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y8PH/8vDx
//Tx8//09PT/9PT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8fL4//T1+v/y8/n/
8vP5/+7s+/+vrrj/+/v+//v7+//x8vX/8fL1//L09v/w8fT/8vT2//L09v/y8/n/8vT2//T08f/0
9PH/9PT2//Ty+f/y8v3/8vP5//P18f/w9+7/7vTu/+rv8P/q6/L/6+zz/+zr8v/r6+7/6+vu/+vr
7v/q6/D/6uvw/+rr8v/q6/L/6uvy/+rr8v/q6/D/6uvw/+vp8f/r6+7/6uvw/+rr8P/q6/D/6uvw
/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/
6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/s
7fD/8PH0//L09v/x8vX/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//P19P/z9fT/8vP5//Lz+f/y8/v/8vP7//Lz+//y8/n/8vT2
//P19P/z9fT/8vT2//Lz+f/y8/v/8vL9//Lz+//x9vj/8PX2//T1+v/08vv/9vD4//fx+f/18vn/
6Oz5/+Px///Q4v//bn6h/218mf/u/v//6fL1//X2/f/y8fj/9Pr0/+Xz//8NG0n/DR9b/wscSf86
TXb/maLG/+jt///g6P//SFJr/6Gxu//g8fP/6vX8/+/6//9se6X/P05+/xsoTf+Ak8H/FylO/4Oa
w//h7v//4Of4//D5///g6v//LTZS/77J7v/k7Pr/6e3y/+fs7v/q7/D/6Ojz/+zs9//q6uz/5Oz3
/3uQq/88Tmn/laW+/8rb+f9RZ4z/DyBG/w0eQ/+bsN//2+b//254mv9Wa53/T2aX/258ov9ZY4L/
W2qJ/7XG6v+QnL7/j5av/9nh6f/4/P7/9fj///L2///t8v//6fH8/+/9///v////tcXl/0FObv/P
4P//nrDT/0dXcv/m9v//9fr///77////+fn///r5//v8///1+P//9vz///b7+v/+/fb//Pv2//T1
/P/h6f//RVR0/0RYgP86S27/2e3//+Hx///w9///9vb////7/f///Pz/+/Xx//z7+P/7+/v/+vv+
//j8/v/6+/7/+vv+//v7+//8+vv///r7//z6+//6/fj/+v34//r7/v/7+v///Pr7//z7+P//+/r/
+fz//xclQf+gvvP/Kzxo/8nb///p8///7vb//+v2///t/v//aH+T/2yGo/+Xsdr/QlNv/8/b6f/2
+v//+vj///bz+//08/D/9PTx//H2+v/v9Pj/7vPx//X48//x8fH/+fn7//L09v/19vz/7/T4/+/0
+P/s8fX/6/Dx/+nt7//n7O7/6uzr/+rs6//r6+v/6+vr/+rs6//q6+7/6uvw/+rr8P/q6/D/6uvw
/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/
6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q
6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/7O3z//Dx9//y8/n/8vP5//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8fL1//f39//09PT/8PDw//Hx8f/v7uv/8O/s
//b18v/x8O3/9fDu//Xw7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/y8e7/8vHu//Lx7v/y8e7/
8vHu//Lx7v/y8e7/8vHu//Lx7v/y8e7/8vDx//Lw8f/x7/D/8vDx//Tx8//09PT/9PT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L0
9v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2
//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/
8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y9Pb/8vT2//L09v/y
9Pb/8vT2//L09v/y9Pb/8/X0//P19P/z9fT/8fL4//T1+v/x8vj/8vP5/+7s+/+urLf/+/v+//v7
+//09fj/8vT2/+/w8//x8vX/8vT2//Hy9f/x8vj/8fL4//Ly8v/y8vL/8vL1//Lx+P/x8vn/8fL1
//D28f/v9e3/6/Dv/+fs8P/o6Pb/6un1/+zs7//r6+v/6+vu/+vr7v/q6/D/6uvw/+fr8v/n6/L/
5+zw/+fs8P/q6+7/6uvu/+vr7v/r6+7/6uvw/+rr8P/n6/L/5+vy/+rr8P/q6/D/6uvw/+rr8P/q
6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr
8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6Orv/+rr8P/t7/H/8fL1//L09v/x8vX/8fL1
//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/
8fTy/+/18P/v9fD/7/Ty/+/09f/x8vj/8fL4//Hy+P/x8vX/8fL1//H08v/x9PD/8fTw/+/08v/v
9PX/7/T1/+/0+P/r9fj/7vL3//fx9//77/f/9vD4//Ty+f/y8/n/7PHz/+3v8f/m6/f/z+D7/w8b
Mv8YKUP/3PH///Dy///28PX/9vXy/+rz//8NGkH/lLP//yhCiP8KGUX/4O3//+ft9v/m8v//p7jR
/x8vUP+Wr93/jZ2//5imyP8cKEP/q8X5/x81bf8rR4b/Y4XI/ytEcf80RWL/aHaQ/8rb/P9qeJT/
fYml/9fi+v/h5O7/7+/v/+nr6v/s7fD/6+nx/+vp8v/n5/L/8Oz2//Ll8f/u4u3/7Ovz/+Hp9/+3
xuD/q7ze/8/g///d7P//5vH+/+Tp8v/o6vv/tLrQ/6m71v+yz/L/WXeZ/yhAZf8sPHD/SVWJ/56l
yv/l6///+v///+z1//+wvdv/KDdT/y5AZf9rgbX/fY3J/z1Hbf/p8fr/0t7f/3WJm/91h6D/7v7/
//b7/f/6+fL//vrz//r4///39///9Pr///r////29fL/+vf5/+3x/v+irtH/Kj9z/w8kWv8uSX3/
EihQ/zxRf/9cbZX/5fL///b7///3+P7/+vr6//n7+v/5+/r/+fv6//n7+v/6+vr/+vr6//v5+v/7
+fr//ff///v4/f/2/fT/9f7z//P/9P/2+/r///b////0///29P//5/L//z1Rdf+ctd//5+/+//T0
9P/v7+//9/X2//vt8//17fv/6/n//3yRtv8nOF//coao/97r8//v9PL/9PL7/+vp8v/09vX/8vT2
//Dv+//28///8vH8//Hw9//19fj/7+/v//Hy9f/x8vj/6/D0/+ft8//p7PP/6ezz/+fr8v/q6/L/
6uvy/+vp8v/r6fL/6+n1/+rp9f/q6fX/6uvy/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q
6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr
8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/L/6uvy/+rr8P/q6/D/6uvw
/+rr8P/q6/D/6uvw/+rr8P/o6u//6+zy/+/w9f/x8vj/8fL4//Hy+P/x8vj/8fL1//Hy9f/x8vX/
8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x
8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy
9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1
//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/
8fL1//Hy9f/x8vX/8vT2/+/v7//x8fH/8fHx/+3t7f/w7+z/8vHu/+/u6//x8O3/8u3s//Lt7P/w
7+z/8O/s//Dv7P/w7+z/8O3v//Dt7//w7+z/8O/s//Dv7P/w7+z/8O/s//Dv7P/w7+z/8O/s//Dv
7P/x8O3/8e/w//Dt7//w7e//7+/v//Lw8f/y8vL/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1
//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/
8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x
8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy
9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1//Hy9f/x8vX/8fL1
//H08v/w8/H/8PH3//Lz+//w8ff/8PH3/+3q+v+tq7b/+/v+//v7+//x8vX/8PH0//L09v/w8fT/
8fL1/+3v8f/w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//t7vT/6uvw/+jq7//o
6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq
7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv
/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//
6Orv/+jq7//o6u//6Orv/+vs8v/t7vT/8PH3//Dx9//v8PX/8PH0//Dx9P/w8fT/8PH0//Dx9P/w
8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx
9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9//x8Pf/8fD3
//Hx9P/x8fH/8fH0//Hw9//w8fj/8O/7/+zw+v/r8fn/5O77/9zo+f+mssr/MDlQ/0NPbP+SosD/
5vP//6Sxxv84RF3/4/P//9vo//+4wNb/5Ofx/+Hi5f/n6O7/4en3/3N/mv8iLkj/ydz//6e43P+c
p7//3On//3SDrf8XIjz/z9vn/+bw8//k7Pr/3Ob//7XE6P+Yp8b/1+Hw/+fs8P/n5+X/6+rn/+vs
8//m5fT/6ujx/+vp8v/o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//n6O7/5+ju
/+fo7v/o6u//6Orv/+rr8P/n7PD/5PDz/+b09//x9///7/P//4GGpP9ncpz/YXKn/woWQv8lNmH/
kKbM/+Py///m7vf/6/D0/+70+P/s8///5/H//+71///ByOH/SlZz/zZDZv8rOWH/JjBO/+b0/P/2
+/r/+vX2//Ls9P/29v//7vX//9jo+v90h5j/a36T/+Dy///s9///4er6/+n1//+Ypbr/QVFz/2+E
tv8mNmj/Ljtp/7O53//09v//8vH5//f1/P/7+v//+ff+//r58//69u//+vf5//z7+P/6+fL/9ffu
//T5/f/v+///wdTw/xwsTP8OG0j/Dx1H/5uuzv/e7P3/7fH+//Hu9v/07+v/9vHt//X1+P/v8PX/
7O3z/+/w9f/w8ff/7/D1//Dx9//y8/n/8PH3//Dx9//v8PX/7/D1/+/w9f/v8PX/7/D1//Dx9//y
8/n/6+zy/8vM0v/Z2t//5uft/+rr8P/o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq
7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv
/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//
6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//s
7fP/8PH3//Lz+f/x8vj/7/D1/+/w9f/w8ff/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx
9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0
//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/
8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH3//Dx9//w
8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8fL4//Dx9//w8ff/8PH3//Dx9//v8PX/6+zv/8rI
yf/s6+j/7+7r//Dv7P/v7uv/8vHu//Dv7P/s6+j/8O/s//Dv7P/w7+z/8O/s//Dv7P/w7+z/8O/s
//Dv7P/w7+z/8O/s//Dv7P/w7+z/8O/p//Dv6f/w7+n/8O/p//Dv7P/w7+z/7+/v/+/v7//v8fD/
7/Hw//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w
8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx
9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0
//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/
8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dx9P/w8fT/8PH0//Dz8f/w8fT/7/D3//Hy+f/w
8fj/8PH4/+3q/f+uq7r/+/v+//v7+//w8ff/7/D1/+/w9f/v8PX/7/D1//Hy+P/w8ff/8PH3//Dx
9//w8ff/8PH3//Dx9//w8ff/8PH3/+/w9f/s7fP/6Orv/+fo7v/n6O7/6Orv/+jq7//n6O7/6Orv
/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//
6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o
6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//n6O7/6Orv/+zt
8//w8ff/8PH3/+/w9f/v8PX/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3
//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/
8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9P/w8/H/8PPx//Dx9P/w8ff/8fD3//Hw+P/w
7/7/8O7///Hv///s8Pr/5u3k/93n1//l8ub/3ujv/+ft//9wdqT/bXuh/36PsP88RF//5+///+Pm
/P/m6fP/7PH1/+Xq6P/n7uj/5efm/+bm6f/x7vb/49/p//Dt9P/o5+7/6Orv/+Lo8f/p7/T/7O/t
/+vt5f/l5eL/6+7s/+Lm7f/k5/H/6un1/+fm7f/r6Or/7Ovo/+jo6P/q6O//6uf2/+jl9f/o6fH/
6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6uvw/+rr8P/q
6/D/7O30/+fm8f/t7PT/7e34//Dz///P0+L/vsfW/9Pe7P/m7///7vn//+bq8f/y9Pb/8fH0//Xy
+f/w7Pb/8e/7/+vo+v/39///6fH8/+Pz///E2/b/U2eA/5qswf/z////8fb///D6///J4///VXOe
/wkfUv8WJ1v/r7Lh//Pu///w7e//8/fq/+v06f/o9fD/5vj8/9bn9v+6zOH/1ej//0BNc/9ATHj/
iZS9/+bu///4/fv/+v3t//n48v/3+PX/9f39//j8/v//+vr/9O7p//n68//s9///dIGt/2h4qv/Z
6v//7fv//+zy+//v8PX/7e/x//f5+//q5vD/8e36//Ty+//y8/n/8fL4//Dx9//v8PX/8PH3//Hy
+P/09fr/7/D1//Dx9//w8ff/8fL4//Dx9//v8PX/7e70/+3u9P/n6O7/6+zy/+rr8P/r7PL/6uvw
/+Xm6//n6O7/6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//
6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o
6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+jq
7//o6u//6Orv/+jq7//o6u//6Orv/+jq7//o6u//6Orv/+zt8//v8PX/8PH3/+/w9f/v8PX/8PH3
//Dx9//v8PX/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/
8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w
8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx
9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3
//Dx9//v8PX/8PH3//Hy+P/w8ff/7/D1//Dx9//w8ff/7/Dz//Hv8P/y8e7/7+7r//Dv7P/s6+j/
8fDt/+/u6//y8e7/7+7r/+/u6//v7uv/7+7r/+/u6//v7uv/7+7r/+/u6//v7uv/7+7r/+/u6//v
7uv/7+7r/+/u6//v7uv/7+7r//Dv7P/v7uv/7+/v/+/v7//t7/H/7/Dz/+/w8//w8fT/8PH3//Dx
9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3
//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/
8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w
8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx9//w8ff/8PH3//Dx
9//w8ff/8PH3//Dx9//w8ff/8PH0//Dx9P/w8fT/7/D3//Hy+f/v8Pf/8PH4/+zp/P+tqrn/+/v+
//v7+//x8vj/8PH3/+/w9f/q6/D/7/D1//Hy+P/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/
7/D1/+3u9P/q6/D/5+ju/+fo7v/o6u//5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n
6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo
7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju
/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+bn7f/o6u//6+zy/+3u9P/v8PX/7/D1/+/w9f/t7vT/
7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v
8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w
9f/v8PX/7/D1/+/w9f/v8PP/7/Dz/+/u+v/v7vr/7/D1/+/w8//v8fD/7/Dz//Dx+P/v7vr/7e72
/+jq7//h5uf/5+zw/+jq+//c4/n/q7vV/4ybtP/d5Pv/7e3+/+3p8//g3uX/5+zu/93n5v/h7Ov/
5Ovr/+jo6P/q5+n/7Obr/+jo6//l6O//5Orv/+jn7//o5+7/5eru/+Xq7v/l6uj/5+ro/+jo6//o
5+7/5+jv/+Xo7//l6uv/5ero/+fq6P/n6uj/5+jv/+fn8v/n6O//5+ju/+fo7v/n6O7/5+ju/+fo
7v/n6O7/5+ju/+jq7//n6O7/5+ju/+fo7v/o6u//6Orv/+jq7//o5/L/7OL5/+nk+f/k6u//4+7p
/+Tx5f/o8Ob/7e3t//Dt9P/x7fr/8O39/+vv/P/p8fr/6fL3/+zx9f/z7fP/9O/t//H16f/v9+n/
6+7n/+7w7P/x8vX/5+n8/4GFrv8lLFr/DBhE/wsfUf8IIVr/FjNt/ypGdf8lNlf/rbfL//Ly/f/w
7f3/8O73/+/x8P/v8fD/8O73//Du9//v8PP/7PHw/+/5/P/h7fv/usXk/yEoQv+zv+D/4vP//6vA
0//P4+//9Pz//+/v8f//+/v///r6//Hx/P/p7///YGeK/4mTtv/k7PT/6u/t//Du9v/x8fT/7PPq
/+vy7P/u7Pv/8O3//+/u+v/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/
7e70/+zt8//q6/D/5+ju/+bn7f/o6u//7O3z/+Hi6P/l5uv/5+ju/+Xm6//n6O7/6uvw/+fo7v/n
6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo
7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju
/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5+ju/+fo7v/n6O7/5uft/+fo7v/n6O7/
5+ju/+bn7f/o6u//6+zy/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v
8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w
9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1
/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/
7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7e70//Dx9//w
8ff/7e70/+/w9f/w8ff/7O3w/+jm5//x8O3/7Ovo/+/u6//t7On/8fDt/+3s6f/v7uv/7+7r/+/u
6//v7uv/7+7r/+/u6//v7uv/7+7r/+/u6//v7uv/7+7r/+/u6//v7uv/7+7r/+/u6//v7uv/7+7r
//Dv7P/v7uv/7e3t/+3t7f/t7/H/7/Dz/+/w8//v8PP/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/
7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v
8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w
9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1
/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/7/D1/+/w9f/v8PX/
7/Dz/+3v8f/w8fT/7/D3/+/w9//v8Pf/7/D3/+vo+v+vrLv/+/v+//v7+//w8ff/5+ju/+3u9P/v
8PX/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+rr8P/n6O7/5uft/+bn
7f/m5+3/5ebr/+Xm6//m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft
/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/
5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m
5+3/5uft/+Xm6//n6O7/6+zy/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u
9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70
/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/
7e70/+3u9P/t7vT/7e/x/+3v8f/u8O//7vDv/+/x8P/v8PX/7Oz6/+rp+v/q6fr/6Onx/+Xn5v/j
6eP/3+vs/+Xv8//m5+7/5uXs/+7o7v+/vcH/6evq/9/k5f/k6O3/5Ofu/+bm8f/m5vH/5ubx/+bn
7v/i6O3/5Ojt/+jk7v/n5u7/3+vu/97r7v/g6u7/5ufu/+vk7v/r5O3/5uft/+Lo7f/i6O3/4ujt
/+bn7f/n5u3/5+bt/+bn6v/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/
5uft/+bn7f/n6O7/5+ju/+fo7v/k6Or/5O3j/+Tt4//m5+r/5ubx/+fk9v/n5Pb/5uX0/+bm8f/n
5/L/6Onx/+zq9v/t7Pf/7+32/+/w9f/r8O//6/Dv/+fs8P/o7Pb/8fP//+zq///18P//8e33/+Tl
6v/m8fj/zuT5/1hxj/8gMlf/vNP//9/v///l8fT/8PP7/+zt9P/v7/H/7+30//Dq/v/u6v//6+3/
/+fu///q7vv/7e72//Do7v/47fT/+PL8/+rs/f/r+f//o7XY/3qNtP9WYoT/lJe4//Dy///b7v//
2vP//0VXe/8WIT3/gY6j/9vk9P/q7f//6u7//+rw9P/q8e7/6u/t/+3t7f/z7O//8+zy/+3s8//s
7fP/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/6uvw/+jq7//n6O7/5uft/+bn7f/m5+3/5uft/+bn
7f/k5er/6uvw/8jJzv/f4OX/5+ju/+Lj6f/i4+n/6Orv/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft
/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/
5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m
5+3/5uft/+bn7f/m5+3/5uft/+bn7f/l5uv/5uft/+fo7v/m5+3/5uft/+jq7//s7fP/8PH3/+3u
9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70
/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/
7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t
7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u
9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/v8PX/7O3z/+zt8//v8PX/7e70/+/w9f/s7fP/5ebp
/8rIyf/y8e7/6unm/+rp5v/s6+j/7+7r//Dv7P/r6uf/7ezp/+3s6f/t7On/7ezp/+3s6f/t7On/
7ezp/+3s6f/t6+z/7evs/+3r7P/t6+z/7ezp/+3s6f/t7On/7ezp/+/s7v/t6+z/7Ozs/+3t7f/t
7/H/7e/x/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u
9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70
/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/
7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t
7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e/x/+zt8P/v8PP/7O30/+3u
9v/t7vb/7e72/+nm+f+tqrn/+/v+//v7+//r7PL/7O3z/+3u9P/s7fP/8PH3/+3u9P/t7vT/7e70
/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+fo7v/m5+3/5uft/+fo7v/m5+3/5ebr/+Xm6//m5+3/
5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m
5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn
7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/o6u//7O3z
/+3u9P/t7vT/7O3z/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/
7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t
7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vb/7e70/+7w7//u8O//7e70/+3u
9v/t7fj/7e72/+/w8//v8fD/6uvu/+rr8v/w7/v/6+r2/+Xm6f/n7Ov/5Ovo/+Hp5v/m6+z/4uPp
/+vp8f/k4+b/6Obn/+bm5v/n5+r/5+bt/+fm8f/n5vH/5+bu/+fm7f/n5+f/6Obn/+vl6v/n5+r/
3+3n/97t5//g6u3/5ufu/+vk7v/r5O3/5+fq/+Tp5//i6O3/5Ofu/+fm8f/n5vH/6Obt/+fn6v/m
5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/n6O7/5+ju/+fo
7v/m5+3/4ufr/+Ln6//m5+7/5ufu/+fm7f/n5+r/5+fn/+fn5//q5+n/5+fn/+fl6f/m5ez/6Ofv
/+rr8v/s7Pf/7/D3//Du9v/v7/H/7/Ty/+Hp5v/p9PL/7PL3/+zt8//t7PT/7Or2//Lx+f/s7+v/
7vDv/+zp+f/x6///8er0//Ls8v/u8O//6/Dv/+rx8f/q8fH/7vDp/+/w6f/w7fL/7+32/+rv8//u
9fL/6/bm/+bt4//t7fD/7ez0/+vu+/+pscn/Mjtd/4OZz/8PJVH/GDFd/w8jPf/M4vr/6Oz5//Hr
8//x6/P/7+zw/+rv7f/q8fH/6+72/+vu9v/t7vT/7O3z/+3u9P/t7vT/7e70/+zt8//r7PL/6Orv
/+bn7f/l5uv/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/n6O7/5uft/+Xm6//n6O7/
5+ju/+Lj6f/l5uv/6Orv/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m
5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn
7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft/+bn7f/m5+3/5uft
/+bn7f/m5+3/5uft/+bn7f/m5+3/6uvw/+3u9P/v8PX/7O3z/+3u9P/t7vT/7e70/+3u9P/t7vT/
7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t
7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u
9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70
/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/
7e70/+3u9P/v8PX/7e70/+/w9f/v8PX/7O3z/+/w9f/v8PX/6urs/+rq6v/s6+j/7Ovo/+3s6f/r
6uf/9PPw/+3s6f/t7On/7ezp/+3s6f/t7On/7ezp/+3s6f/t7On/7ezp/+3s6f/t6+z/7evs/+3r
7P/t6+z/7ezp/+3s6f/t7On/7ezp/+/s7v/s7Oz/7e3t/+/v7//v8PP/7/Dz/+3u9P/t7vT/7e70
/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/
7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t
7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u
9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70
/+3u9P/t7vT/7e70/+3u9P/t7vT/7e70/+zt8P/v8PP/7e72/+3u9v/t7vb/7e34/+rn9v+uq7r/
+/v+//v7+//r7PL/6+zy/+zt8//t7vT/7e70/+vs8v/s7fP/7O3z/+vs8v/r7PL/7O3z/+zt8//r
7PL/6Orv/+Xm6//l5uv/5ebr/+Xm6//l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebr/+Xm6//l5uv/5ebr/+Tl6v/o6u//6+zy/+zt8//r7PL/7O3z/+zt8//r
7PL/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt
8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z
/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//r7PL/
6+zy/+zt8//t7vT/7e70/+zt8//r7PL/5uft/+Lj6f/n6O7/5ebr/+Dh5v/s7fP/5OXq/+Tl6v/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5OXs/+Xm7f/l5u3/5ufu/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl6v/k
5er/5uft/+fo7v/o6u//6+zy/+zt8//t7vT/7O3z/+zt8//s7fP/7O3z/+zt8//r7PL/6+zy/+vs
8v/r7PL/6+zy/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+3u9P/s7fP/6+zy/+vs8v/s7fP/7O3z
/+3u9P/q7ff/7PP//+Hp///l6///8Pf//+Dk8f/n6/X/8vP7/+3u9P/s7O//7Ozs/+3t8P/t7fD/
6+zy/+rr8P/n6O7/5ufu/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/k5ez/5ufu/+Lj6v/n6O//5ebt/+Lj6v/m5+7/5OXs/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/k5er/5ebr/+fo7v/q
6/D/7O3z/+zt8//r7PL/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt
8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z
/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/
7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s
7fP/7O3z/+zt8//s7fP/7O3w/+zt8P/s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//r7PL/6+zy/+zs
7//s7O//7e3w/+zs7//r6+v/6urq/+zs7P/t7e3/6+vr/+jo6P/r6+v/6+vr/+rq6v/o6Oj/6urq
/+rq6v/q6ur/6urq/+rq6v/q6ur/6urq/+rq6v/q6uf/6urn/+rq5//q6uf/6urq/+rq6v/q6ur/
6urq/+rq7P/r6+7/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/7O3z/+zt8//s7fP/7O3z/+zt8//s
7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt
8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z
/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/
7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s7fP/7O3z/+zt8//s
7fP/7O3z//Hy9f/q6+7/5+jv/+jp8f/t7fv/8O/+/+vp9f+1s7v/+/r///v7/v/l5uv/5uft/+jq
7//l5uv/6+zy/+rr8P/o6u//6+zy/+vs8v/q6/D/6uvw/+vs8v/o6u//5OXq/+Tl7P/k5ez/5OXs
/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k
5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl
7P/k5er/5OXq/+Xm6//o6u//6+zy/+vs8v/q6/D/6uvw/+vs8v/q6/D/6+zy/+vs8v/r7PL/6+zy
/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/
6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r
7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6uvw/+fo7v/i4+n/4eLo/+bn7f+2t7z/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs
/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k
5ez/4uPq/+Tl7P/k5ez/5ebt/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl
7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl6v/k5er/4uPp/+Lj6f/i4+n/4uPp
/+Tl6v/k5er/5OXq/+Tl6v/l5uv/5ebr/+bn7f/m5+3/5+ju/+fo7v/q6/D/6uvw/+rr8P/q6/D/
6uvw/+vs8v/r7PL/6+zy/+vs8v/r7PL/7O3z/+zt8//r7PL/6+zy/+rr8P/q6/D/4OXm//H2+P/i
5+n/6u/z/+Tl6v/k5er/6+nx/+jn7v/m5O3/5ePs/+Pi7f/j4u3/4uLw/+Pj8f/i5vL/4ubw/+Tl
7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs
/+Tl7P/k5ez/4uPq/8XGzf/X2N//4uPq/+Tl7P/k5ez/4uPq/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k
5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl
7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/l5uv/5+ju/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy
/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/
6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r
7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zv
/+vs7//r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/q6/D/6uvw/+vp8f/s6/L/6+vu/+rq7P/n5+f/
5ubm/8TExP/n5+f/6urq/+fn5//q6ur/5ubm/+rq6v/q6ur/6Ojo/+jo6P/o6Oj/6Ojo/+jo6P/o
6Oj/6Ojo/+jo6P/p6eb/6enm/+jo6P/o6Oj/6Ojo/+jo6P/o6Ov/6Ojr/+rq7P/r6+7/6+zy/+vs
8v/q6/D/6uvw/+rr8P/q6/D/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy
/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/
6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r
7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs
8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+vs8v/r7PL/6+zy/+jq7P/n6Ov/7O30
/+3u9v/q6ff/6Oj2/+Pi7f+wr7f/+/r///v7/v/h4un/4uPq/+fo7//h4un/4OHo/+Tl7P/i4+r/
5OXs/+Xm7f/o6fH/6+zz/+rr8v/m5+7/5OXs/+Lj6v/i4+r/4uLt/+Li7f/i4u3/4uLt/+Li7f/i
4u3/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Lj6v/k5ez/4eLp/+Hi6f/i4+r/4uPq/+Lj6v/i4+r/5OXs/+rr8v/q6/L/
6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q
6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr
8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw
/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/5+jv/+rr8v/t7vb/
5OXs/+Lj6v+7vML/4OHo/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uLt/+Li7f/i4u3/4uLt/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/k5ez/5OXs
/+Tl7P/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+n/5OPm/+Tj5v/k4+b/4+Lp/+Pi6f/j4ur/4+Lt
/+Pi7f/j4u3/4+Lt/+Pi7f/j4ur/4uPq/+Lj6f/i4+n/4uPp/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/h4un/5OXs/8TFzP/X
2N//4uPq/+bn7v/h4un/4eLp/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/5OXs/+Lj6v/h4un/4eLp/+Lj6v/i4+r/
5OXs/+Tl7P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q
6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr
8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw
/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/
6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8v/q
6/L/6uvy/+rr8v/q6/L/6uvy/+vp8f/r6fH/6+vu/+jo6//n5+r/5ubp/8TExP/o6Oj/6+vr/+vr
6//r6+v/4uLi/+vr6//q6ur/6Ojo/+jo6P/o6Oj/6Ojo/+jo6P/o6Oj/6Ojo/+jo6P/o6Oj/6Ojo
/+jo6P/o6Oj/6Ojo/+jo6P/o6Ov/6Ojr/+vp8f/r6fH/6uvw/+rr8P/q6/L/6uvy/+rr8v/q6/L/
6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q
6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr
8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw
/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/
6uvw/+rr8P/q6/D/6uvw/+rr8P/q6/D/6uvw/+rr7v/r7O//6Onx/+rr8v/q6ff/6un3/+fm8f+u
rbT/+/r///v7/v/g4ej/5ufu/+bn7v/i4+r/5ebt/9/g5//k5ez/4uPq/+Hi6f/h4un/4uPq/+Lj
6v/i4+r/4uPq/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/k
5ez/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/k5ez/5ebt/+rr8v/q6/L/6uvy/+rr8v/q6/D/6uvw/+rr
8P/q6/D/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy
/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/
6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q
6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6Onx/+bn7v/19v3/6Onx/+Xm7f/k5ez/4eLp/+Dh
6P/i4+r/4uPq/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Tl7P/i4+r/4uPq/+Lj6v/k5ez/5OXs/+Tl7P/i4+r/4uPq/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Li
7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt
/+Li7f/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4+Lt/+Pi7f/j4u3/4+Lt/+Pi7f/j4u3/4+Lt/+Pi7f/j4ur/4+Lq/+Lj6v/i
4+r/4uPq/+Lj6f/i4+n/4uPp/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/k5ez/3d7l/+Dh6P/f4Of/4eLp/+bn7v/l5u3/4eLp
/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/5OXs/+Tl7P/m5+7/6uvy/+zt9P/q6/L/6uvy/+rr
8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy
/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/
6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q
6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr
8v/q6/L/6uvy/+rr8v/q6/L/6uvw/+rr8P/q6/D/6uvw/+rr8v/q6/L/6uvy/+rr8v/o6fH/6uvy
/+vp8f/q6O//6Ojr/+fn6v/o6Ov/6urs/+Xl5f/k5OT/7Ozs/+3t7f/o6Oj/5ubm/+bm5v/q6ur/
6Ojo/+jo6P/o6Oj/6Ojo/+jo6P/o6Oj/6Ojo/+jo6P/o6Oj/6Ojo/+jo6P/o6Oj/6Ojr/+jo6//o
6Ov/6Ojr/+vp8f/r6fH/6uvw/+rr8P/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr
8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy
/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/
6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q
6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr8v/q6/L/6uvy/+rr
8v/q6/L/6uvw/+rr8P/r7O//6Onx/+rr8v/q6ff/6un3/+fm8f+urbT/+/r///v7/v/h4ez/4eHs
/+Li7f/g3+v/4eHs/+Df6//g3+v/4N/r/+Hh7P/h4ez/4N/r/+Df6//h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7//h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eLp
/+Dh6P/i4+r/5ufu/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/
6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o
6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp
8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx
/+jp8f/o6fH/5+jv/+bn7v/s7fT/4eLp/+3u9v+/wMf/6+zz/+Lj6v/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/i4u3/4uLt/+Li7f/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4un/4eLp/9/i6f/f4+j/4eLo/+Hi6P/h4un/4eLp/+Hh7P/h4ez/4eHv/+Hg8f/i3/P/4t/y
/+Hh7//h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/g3+v/3d3o/8jH0v/Y2OP/4eHs/+Pj7v/f3un/4N/r/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/i4u3/5eTw/+fn8v/q6fX/6un1/+jo8//o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/
6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o
6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp
8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx
/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/
6Orv/+jq7//o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/q6/L/6Onx/+jn7v/o5+7/6ujv/+jn7v/m
5un/5eXo/8nJzP/m5un/6+vu/+vr7v/q6uz/5ubp/+vr7v/o6Ov/6Ojr/+jo6//o6Ov/6Ojr/+jo
6//o6Ov/6Ojr/+jo6//o6Oj/6Ojo/+jo6P/o6Oj/6Ojr/+jo6//o6Ov/6Ojr/+ro7//q6O//6Onx
/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/
6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o
6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp
8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx
/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Onx/+jp8f/o6fH/6Orv/+jq7//q6+7/
5+jv/+jp8f/o6Pb/6Oj2/+bk8P+tq7P/+/r///v7/v/h4ez/4N/r/+Pj7v/g3+v/4+Pu/9/e6f/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4uLt/+Li7f/h4ez/4N/r/+Hh7P/k5ez/5ufu/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5ufu/+jp8f/q
6/L/5ufu/+fo7/+6u8H/5ufu/+fo7//n6O//5ebt/+Lj6v/h4un/4eLp/+Hi6f/h4un/4OHo/+Lh
7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs
/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/
4uHs/+Pi7f/j4u3/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/i4u3/397p/7+/
yv/S0t3/4N/r/+Xk8P/g3+v/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4uHs
/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/4uHs/+Lh7P/i4ez/
4uHs/+Hh7P/h4ez/4eLp/+Hi6f/h4un/4eLp/+Hi6f/g4ej/4uPq/+Xm7f/n6O//5+jv/+fo7//m
5+7/5+ju/+jq7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+fy/+fn8v/o6fH/5ufu/+bl7P/m5ez/5+fq/+fn6v/l5eX/4uLi/76+wf/l5ej/6urs
/+jo6//o6Ov/4uLl/+jo6//m5un/5+fq/+fn6v/n5+r/5+fq/+fn6v/n5+r/5+fq/+fn6v/n5+f/
5+fn/+bm5v/m5ub/5+fq/+fn6v/o5+7/6ujv/+jn7//o5+//6Ofy/+jn8v/n5/L/5+fy/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7v/o6u//5ubx/+jo8//q5/b/6OX1/+bk
8P+urbT/+/r///v7/v/f3un/4N/r/+Hh7P/f3un/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/g3+v/4eHs/+Hh7P/h4ez/4N/r/+Hh7P/l5u3/5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//6+zz/+Xm7f/n6O//5ufu/+jp8f/r7PP/6+zz
/+fo7//n6O//5+jv/+fo7//m5+7/5OXs/+Hi6f/h4un/4OHo/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Df6//g3+v/4N/r/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/g3+v/5eTw/+Hh7P/m5vH/4eHs/9/e6f/f3un/
4uLt/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eLp/+Dh
6P/f4Of/4OHo/+Tl7P/m5+7/5+jv/+fo7//n6O//5+jv/+bn7v/m5+7/5+ju/+jq7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O7/
5uft/+fm7f/n5u3/5+fq/+jo6//n5+r/5+fq/+rq7P/r6+7/5eXo/+bm6f/o6Ov/5+fq/+jo6//n
5+r/5+fq/+fn6v/n5+r/5+fq/+fn6v/n5+r/5+fq/+fn6v/n5+f/5+fn/+fn6v/n5+r/5+bt/+jn
7v/o5+//6Ofv/+jn7//o5+//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7v/n6O7/5ubx/+jo8//n5/X/5uX0/+Xj7v+urbT/+/r///v7/v/i4u3/
4N/r/9zc5//f3un/4N/r/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/4N/r/+Df6//f3un/
397p/+Hh7P/l5u3/5+jv/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m
5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn
7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu
/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5+jv/+Xm7f/m5+7/5ufu/+fo7//l5u3/6+zz/+Xm7f/m5+7/5ebt/+Xm7f/m
5+7/5+jv/+bn7v/i4+r/4OHo/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/3Nzn/+Hh7P/g3+v/397p/+Df6//f3un/3Nzn/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/93d6P/d3ej/3+Dn/+Hi6f/k5ez/5ufu/+bn7v/l5u3/
5ebt/+Xm7f/m5+7/5ufu/+bn7v/m5+7/5uft/+Xm6//m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m
5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn
7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu
/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m
5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5uft/+bn7f/m5+3/5uft/+bm6f/m5un/5ubp/+bm
6f/m5un/5+fq/+jo6//l5ej/5+fq/+bm6f/k4+b/6Ojr/+fn6v/l5ej/5ubp/+bm6f/m5un/5ubp
/+bm6f/m5un/5ubp/+bm6f/m5un/5ubp/+bm6f/m5un/5+bt/+fm7f/n5u7/5+bu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m
5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn
7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu
/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7f/m
5+3/5eTw/+fn8v/m5fT/5eTy/+Li7f+srbP/+/r///v7/v/d4ev/297o/9/i7P/c4On/3+Ls/9ve
6P/d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr
/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/
3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d
4ev/3eHr/93h6//d4ev/3eHr/93h6//g3+v/4eHs/+Df6//f3un/4N/r/+Pj7v/m5+7/5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//6Onx/+fo
7//n6O//5ebt/+rr8v+7vML/5+jv/+bn7v/n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+bm8f/j4+7/4eHs/9/e6f/d3ej/397p/9/e6f/g3+v/4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/
4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/397p/+Df6//g
3+v/4eHs/+Df6//g3+v/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h
6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr
/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/
3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d
4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h
6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//f4uz/3eHr
/73Ayv/Q093/3+Ls/+Dj7f/c4On/3ODp/93h6//d4ev/3eHr/93h6//d4ev/3eHr/93h6//d4ev/
4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/4N/r/+Df6//f3un/397p/+Df6//g3+v/4N/r/9/e6f/f
3un/4N/r/+Li7f/j4+7/5ebt/+bn7v/n6O//5+jv/+bn7v/m5+7/5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+ju/+fo7v/n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7v/m5+3/5ufq/+bn6v/l5un/5ebp/+bm6f/m5un/5ubp/+fn6v/l5ej/4eHk/8HBw//m5un/
5+fq/+fn6v/l5ej/5ubp/+fn6v/m5un/5ubp/+bm6f/m5un/5ubp/+bm6f/m5un/5ubp/+bm6f/m
5ez/5+bt/+fm7f/o5+7/5+jv/+fo7//n6O//5+jv/+fn8v/n5/L/5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv
/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//
5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n
6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo
7//n6O//5+jv/+fo7//n6O//5+jv/+fo7//n6O//5+jv/+fo7v/m5+3/5+fy/+fn8v/m5fT/5+f1
/+Li7f+ur7b/+/z///v8///f4uz/2t3n/9ve6P/b3uj/3ODp/93h6//c4On/3ODp/9zg6f/c4On/
3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c
4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg
6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp
/9zg6f/f3un/4N/r/9/e6f/f3un/4eHs/+Xk8P/n6O//5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m
5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn
7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu
/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/6uvy/+Tl7P/k5ez/5ebt/+rr8v/Z2uH/
6uvy/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bm8f/m5vH/5ubx/+bm8f/l
5PD/4uLt/+Df6//d3ej/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/+Df6//f3un/397p/9/e6f/g3+v/4N/r/+Df6//g3+v/3ODp
/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/
3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c
4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg
6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp
/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/
3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/f4uz/3+Ls/9XY4v/Z3Ob/3ODp/9ve6P/c
4On/3eHr/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/g3+v/4N/r/+Df6//f3un/4N/r/+Hh7P/l5PD/5ubx/+fn8v/m5vH/5ufu
/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5uft/+bn7f/m5+7/
5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m
5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn
7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu
/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7f/l5uv/5ebp/+Tl6P/k
5uX/5efm/+bm6f/l5ej/5eXo/+Xl6P/l5ej/4uLl/9vb3v/n5+r/5ubp/+Xl6P/g4OP/5ubp/+Xl
6P/n5+r/5eXo/+Xl6P/l5ej/5eXo/+Xl6P/l5ej/5eXo/+Xl6P/l5uv/5ebr/+bn7v/m5+7/5ufu
/+bn7v/m5vH/5ubx/+bm8f/m5vH/5ufu/+bn7v/k5+7/5Ofu/+Tn7v/k5+7/5ufu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m
5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn
7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu
/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/5ufu/+bn7v/m5+7/
5ufu/+bn7v/m5+7/5ufu/+Xq7v/i5+v/5ejy/+Xo8v/m5fT/5+f1/+Li7f+ur7b/+/z///v8///Z
3Ob/297o/9zg6f/b3uj/3eHr/9nc5v/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/c3Of/3Nzn/9zc5//d
3ej/397p/+Hh7P/j4+7/4+Pu/+bm8f/m5vH/5eTw/+Xk8P/l5PD/5eTw/+Xk8P/l5PD/5ufu/+bn
7v/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5OXs/+bn7v/o6fH/5+jv/+Hi6f/n6O//5+jv/+Tl7P/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/4uPq
/+Dh6P/d3uX/3N3k/93e5f/f4Of/3+Dn/93e5f/b3uj/297o/9ve6P/a3ef/2t3n/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/c4On/3ODp/9zg6f/c4On/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/a3ef/2dzm/93h6//a3ef/297o/9/i7P/a3ef/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/3d7l/93e5f/d3uX/3d7l/93e5f/d3uX/3N3k/9zd5P/d3uX/
4OHo/+Lj6v/k5ez/5ebt/+bn7v/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5+bt/+fm7f/n5u3/5uXs/+Pi6f/k4+b/5OPm/+Xl6P/k4+b/5eXo/+Tj5v/i4uX/5OPm
/+Xl6P/l5ej/5OPm/+Xj6v/j4un/39/h/+jo6//h4eT/5eXo/+fn5//g4OD/5OTk/+Tk5P/i4+b/
4uPm/+Lj5v/i4+b/4uPp/+Tl6v/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Tn
7v/h5ez/5Ofx/+Lm8P/j4/H/5uX0/+Li7f+vsLf/+/z///v8///d4ev/2t3n/9/i7P/a3ef/19vk
/9rd5//b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/d3ej/3d3o/93d6P/c3Of/3Nzn/9zc5//c3Of/3d3o
/9zc5//d3ej/397p/+Hh7P/i4u3/4+Pu/+Xk8P/l5PD/5OXs/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5OXs/+Tl7P/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/r7PP/5OXs/+Xm7f+2t77/4eLp/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5OXs/+Dh6P/f
4Of/3d7l/9zd5P/a3ef/297o/9ve6P/b3uj/297o/9ve6P/b3uj/2t3n/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/a3ef/
297o/7W4wv/N0Nn/3eHr/9/i7P/a3ef/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/3d7l/93e5f/d3uX/3d7l/9/g5//g4ej/4eLp/+Lj6v/l5u3/5ebt/+Xm7f/k5ez/5OXs/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5uXs/+bl7P/l4+r/
5ePq/+Tj5v/k4+b/5OPm/+Tj5v/i4uX/5OPm/+Tj5v/k4+b/5OPm/+Tj5v/h4eT/39/h/76+wf/g
4OP/5OPm/+Xl6P/l5ej/5eXo/+Dg4P/i4uL/5OTk/+Tk5P/i4+b/4uPm/+Lj6f/i4+n/5OXq/+Tl
6v/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/
5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l
5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm
7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt
/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Xm7f/l5u3/5ebt/+Lm7f/h5ez/4ubw/+Lm8P/j4/H/
5eTy/+Hh7P+ur7b/+/z///v8///c3Of/3d3o/9/e6f/d3ej/397p/9vb5v/a3ef/2t3n/9rd5//a
3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd
5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n
/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/
2t3n/9rd5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//d3ej/3d3o/93d6P/d3ej/3Nzn/9zc5//c
3Of/3Nzn/9zc5//d3ej/3d7l/9/g5//g4ej/4eLp/+Lj6v/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl
7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs
/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/4eLp/+Xm7f/n6O//5OXs/+Dh6P/B
wsj/4eLp/+Lj6v/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl
7P/k5ez/5OXs/+Tl7P/k5ez/4uPq/+Lj6v/k5ez/5OXs/+Xm7f/k5ez/5OXs/+Lj6v/h4ez/4N/r
/9/e6f/c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/93d6P/d3ej/
2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a
3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd
5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n
/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/
2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a
3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//d3ej/2Njj/8PDzf/R0dz/397p/93d
6P/g3+v/2tnl/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3+Dn/+Dh6P/h4un/4uPq
/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k
5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl
7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs
/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k
5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5ePq/+Pi6f/i4ej/4uHo/+Li5f/k4+b/4uLl/+Li
5f/i4uX/5OPm/+Tj5v/i4uX/4uLl/+Tj5v/h4eT/39/h/8LCxP/g4OP/4eHk/+Li5f/k4+b/5ubp
/+Hh5P/i4uX/4uLl/+Li5f/h4uj/4eLo/+Lj6f/i4+n/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k
5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl
7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs
/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/
5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k5ez/5OXs/+Tl7P/k
5ez/5OXs/+Tl7P/k5ez/5OXs/+Xm7f/i4+r/4+Pu/+Pj7v/i4vD/5eTy/+Hh7P+trrT/+/z///v8
///c3Of/3Nzn/9vb5v/b2+b/29vm/9vb5v/a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n
/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/
2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a
3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3N3k
/9zd5P/c3eT/3N3k/9zd5P/d3uX/3d7l/93e5f/g4ej/4eLp/+Hi6f/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4eLp/+Dh6P/i4+r/4uPq/+Dh6P/l5u3/4uPq/+Dh6P/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4u3/4uLt/+Li7f/i4u3/4eHs/9/e6f/d
3ej/3Nzn/9zc5//c3Of/29vm/9vb5v/c3Of/3Nzn/9zc5//b2+b/2t3n/9rd5//a3ef/2t3n/9rd
5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n
/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/
2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a
3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd
5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n/9rd5//a3ef/2t3n
/9rd5//a3ef/2t3n/9rd5//c3Of/29vm/93d6P/d3ej/3Nzn/93d6P/d3ej/3Nzn/9zc5//c3Of/
3Nzn/93d6P/f3un/4N/r/+Hh7P/i4u3/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uHo/+Lh6P/i4ej/4uHo/+Li5f/i4uX/4uLl/+Li5f/i4uX/4uLl/+Li5f/i4uX/
4uLl/+Li5f/i4uX/4uLl/+Li5f/h4eT/4eHk/+Dg4//h4eT/4uLl/+Li5f/k4+b/4uLl/+Li5f/h
4uj/4uPp/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/
4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i
4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj
6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uLt/+Hh7P/i4vD/4uLw/93d6P+vsLf//Pv///z8///b2+b/29vm/9vb5v/Y2OP/
3Nzn/9rZ5f/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b
2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb
5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm
/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/
29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b
2+b/29vm/9vb5v/a2eX/2tnl/9vb5v/b2+b/3Nzn/93d6P/f3un/397p/+Hh7P/h4ez/4uLt/+Li
7f/i4u3/4uLt/+Li7f/h4ez/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt
/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/
4uLt/9/e6f/j4+7/4eHs/+Li7f/FxdD/4eHs/+Pj7v/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i
4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li
7f/i4u3/4uLt/+Li7f/h4ez/4eHs/+Hh7P/i4u3/4uLt/+Li7f/i4u3/4uLt/+Hh7P/g3+v/397p
/93d6P/c3Of/3Nzn/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/
29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b
2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb
5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm
/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/
29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/b
2+b/2tnl/8nI0//V1OD/29vm/93d6P/c3Of/397p/+Hh7P/h4ez/4uLt/+Li7f/i4u3/4uLt/+Li
7f/i4u3/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq/+Lj6v/i4+r/4uPq
/+Lj6v/i4+r/4uPq/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/
4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i
4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li
7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt
/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/
4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Hh7P/h4un/4uHp/+Lh6P/i
4ej/4uHo/+Li5f/i4uX/4uLl/+Li5f/i4uX/4eHk/+Hh5P/h4eT/4uLl/+Li5f/h4eT/4ODj/8fG
yf/h4eT/4uLl/9/f4f/h4eT/4eHk/+Tj5v/h4eT/4uHo/+Lh6P/h4un/4eLp/+Li7f/i4u3/4eHs
/+Hh7P/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/
4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i
4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li
7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt
/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/
4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Li7f/i4u3/4uLt/+Lj6v/i4+r/4uLt/+Li7f/j
4PD/4+Dw/9/d6P+wr7f//Pv///z8///Y2OP/19fi/9zc5//X1+L/3d3o/9jY4//a2eX/2tnl/9rZ
5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl
/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/
2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a
2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ
5f/a2eX/2tnl/9rZ5f/a2eX/29vm/9vb5v/b2+b/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl
/9rZ5f/Y2OP/2Njj/9jY4//a2eX/2tnl/9jY4//a2eX/29vm/93d6P/f3un/4N/r/+Df6//g3+v/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/397p/+Pj7v/h4ez/4uLt/+Df
6/+7usX/4N/r/+Df6//h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Df6//g3+v/4eHs/+Li7f/i4u3/4uLt/+Hh7P/f
3un/3Nzn/9zc5//c3Of/29vm/9vb5v/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ
5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl
/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/
2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a
2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ
5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/f3un/397p/7+/yv/W1uH/4eHs
/+Pj7v/f3un/4eHs/+Df6//g3+v/4eHs/+Hh7P/i4u3/4eHs/+Hh7P/h4ez/4eLp/+Hi6f/h4un/
4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Lj6v/h4un/4OHo/+Dh6P/g3uf/4N7l/+De5f/g3uX/4N7l/+Dg4//g4OP/4ODj
/+Dg4//h4eT/4ODj/9/f4f/g4OP/4eHk/+Hh5P/f3+H/3Nzf/7y8v//f3+H/3d3g/9/f4f/l5ej/
3d3g/+Hh5P/i4ej/4eDn/+Hg5//h4un/4eLp/+Hh7P/h4ez/4eHv/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/
4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h
4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eLp/+Hi6f/h4un/4eHs/+Hh7P/i3+//4t/v/97c6/+vrrj//Pv/
//z8///a2eX/2tnl/9rZ5f/X1+L/3Nzn/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/
2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a
2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ
5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl
/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/
2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a
2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/b2+b/29vm/9vb5v/c3Of/3d3o/9/e
6f/g3+v/4eHs/+Hh7P/g3+v/4N/r/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs
/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4uPq/+Dh6P/g4ej/4eLp/+Lj6v/c3eT/5ebt/+Dh6P/h4un/
4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h
4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi
6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4uLt/+Li7f/i4u3/4eHs
/+Hh7P/h4ez/4N/r/+Df6//d3ej/3d3o/9zc5//b2+b/29vm/9rZ5f/Y2OP/2Njj/9rZ5f/a2eX/
2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a
2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ
5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9rZ5f/a2eX/2tnl/9jY4//a2eX/2tnl/9rZ5f/a2eX/2tnl
/9rZ5f/a2eX/2tnl/9jY4//Y2OP/2tnl/9rZ5f/a2eX/29vm/9vb5v/b2+b/3Nzn/93d6P/d3ej/
397p/+Df6//g3+v/4eHs/+Hh7P/h4un/4uPq/+Dh6P/k5ez/4eLp/+Dh6P/g4ej/4uPq/+Hi6f/h
4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi
6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp
/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/
4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h
4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi
6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp
/+Hi6f/i4en/4uHp/+Hh7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hi6f/h4un/4OHm/+Dh5v/g4OP/
4ODj/+Hf4P/h3+D/4ODj/+Dg4//g4OP/4ODj/+Dg4//g4OP/4ODj/+Dg4//g4OP/4ODj/9/f4f/g
4OP/4ODj/+Dg4//g4OP/39/h/93d3f/g4OD/39/h/9/f4f/g3uX/4eDn/+Lh6f/h4Oj/4eHs/+Hh
7P/h4ez/4eHs/+Hh7P/h4ez/4eHs/+Hh7P/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp
/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/
4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h
4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi
6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp
/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/4eLp/+Hi6f/h4un/
4eLp/9/j6P/f4un/3+Lv/93h7f/h4ez/4eHs/93d7v+vr7z//Pz///z8/P/Y2OP/2Njj/9jY4//W
1uH/29vm/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY
4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj
/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/
2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y
2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY
4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj
/9jY4//Y2OP/2Njj/9jY4//X1+L/2tnl/9jY4//Y2OP/2Njj/9jY4//Y2OP/2tnl/9rZ5f/b2+b/
3Nzn/93d6P/f3un/397p/+Df6//h4ez/4eHs/+Df6//g3+v/4N/r/+Df6//g3+v/4N/r/+Df6//g
3+v/4uPq/9/g5//f4Of/4OHo/+Lj6v/b3OP/5ebt/9/g5//g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh
6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo
/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/
4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/4N/r/+Df6//g
3+v/4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/4N/r/9/e6f/f3un/3d3o/93d6P/c3Of/29vm/9vb
5v/b2+b/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/19fi/9fX4v/Y2OP/2Njj/9jY4//Y2OP/2Njj
/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/19fi/9fX4v/X1+L/
2Njj/9jY4//Y2OP/2Njj/9jY4//X1+L/19fi/9jY4//a2eX/29vm/9vb5v/c3Of/3Nzn/9/e6f/f
3un/397p/+Df6//g3+v/4N/r/+Hh7P/h4ez/397p/+Df6//g3+v/4N/r/+Df6//g3+v/4N/r/+Df
6//g4ej/4eLp/9/g5//i4+r/4OHo/9/g5//f4Of/4eLp/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo
/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/
4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g
4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh
6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo
/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/
4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g3+v/4N/r/+Df6//g
3+v/4N/r/+Df6//g4ej/4OHo/+Dh6P/f4Of/3+Dl/93e5P/f3+H/39/h/9/f4f/f3+H/39/h/9/f
4f/f3+H/39/h/9/f4f/f3+H/39/h/9/f4f/g4OP/39/h/9/f4f/f3+H/39/h/9/f4f/f3+H/3d3g
/9zc3//g4OP/39/h/93d4P/f3eT/4eDn/+Hi6f/g4ej/4N/r/+Df6//g3+v/4N/r/+Df6//g3+v/
4N/r/+Df6//g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g
4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh
6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo
/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/
4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g
4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/+Dh6P/g4ej/4OHo/97i5v/d4ej/3eHt/93h
7f/g3+v/4N/r/9zc7P+urbv//Pz///z8/P/Y2OP/1tbh/9rZ5f/W1uH/29vm/9bW4f/Y2Ob/2Njm
/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/
2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y
2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY
5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm
/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/
2Njm/9jY5v/Y2Ob/2Njm/9jY5v/Y2Ob/2Njm/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y
2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY4//Y2OP/2Njj/9jY
4//Y2OP/2Njj/9zc5//c3Of/3d3o/9/e6f/g3+v/4N/r/9/e6f/d3ej/3Nzn/+Df6//d3ej/397p
/9zc5/+4uMP/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/4eHs/7+/yv/W1uH/
397p/9/e6f/d3ej/4N/r/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/3+Dn/9/g5//f4Of/3d7l
/9/d5P/f3eT/393k/9/d5P/f3+H/39/h/9/f4f/f3+H/393k/9/d5P/f3eT/393k/9/d5P/f3eT/
393k/9/d5P/g3uX/393k/9/d5P/f3eT/4N7l/+De5f/d3OP/29ng/7q7wP/f4OX/3N3k/9zd5P/h
4un/3N3k/+Df6//d3ej/397p/9/e6f/f3un/397p/9zg6f/c4On/3ODp/9zg6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/3+Dn/93h6P/c4Of/3N/s/9zf7P/g3+v/397p/9zc7P+vr7z/
/Pz///z8/P/b2+b/2tnl/9jY4//V1OD/2Njj/9bW4f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X
1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX
5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl
/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/
19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X
1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX5f/X1+X/19fl/9fX
5f/X1+X/19fl/9fX4v/X1+L/19fi/9fX4v/X1+L/19fi/9fX4v/X1+L/19fi/9fX4v/X1+L/19fi
/9fX4v/X1+L/19fi/9fX4v/X1+L/19fi/9fX4v/X1+L/19fi/9fX4v/X1+L/19fi/9fX4v/X1+L/
19fi/9fX4v/Y2OP/2tnl/9vb5v/c3Of/3ODp/9nc5v/d4ev/297o/93h6/+/w8z/297o/93h6//c
4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg
6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp
/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e
6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p
/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/
397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f3un/397p/9/e6f/f
3un/397p/9/e6f/f3un/397p/9/e6f/c4On/3ODp/8fK0//V2OL/297o/9zg6f/d4ev/3ODp/9zg
6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp
/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/
3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c
4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg
6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp
/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/
3ODp/9zg6f/c3+z/3N/s/9/e6f/f3un/3+Dn/9/g5//f3eT/393k/93c4//d3OP/3dzj/93c4//d
3OP/3dzj/9zd4//c3eP/3dzj/93c4//d3OP/3dzj/93c4//d3OP/3dzj/93c4//f3eT/3dzj/93c
4//d3OP/393k/9/d5P/d3OP/29ng/8TFzP/b3OP/3d7l/93e5f/g3+v/3Nzn/9/e7P/g3+3/397s
/9/e7P/c3+z/3N/s/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/
3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c
4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg
6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp
/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/
3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c4On/3ODp/9zg6f/c
4On/3ODn/93h6P/c4Of/3N/s/9zf7P/f3un/397p/9va6/+urbv//Pz///z8/P/f3un/4N/r/93d
6P/c3Of/19fi/9bW4f/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk
/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/
1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W
1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW
5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk
/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/
1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W
1uT/1tbk/9bW5P/W1uT/1tbk/9bW5P/W1uT/1tbk/9XU4v/V1OL/1tbk/9bW5P/W1uT/1tbk/9bW
5P/W1uT/1tnj/8/S3P/W2eP/1Nfh/9XY4v/W2eP/19vk/9rd5//b3uj/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d
6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o
/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/
3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d
3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d
6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o/93d6P/d3ej/3d3o
/93d6P/c4On/297o/9zg6f/c4On/297o/9ve6P/f4uz/2t3n/9ve6P/b3uj/297o/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/
297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/3d3o/93d
6P/c3eT/3N3k/9vc4//c2+L/29ng/9zc3//c3N//3Nzf/9zc3//b3OL/29zi/9vc4v/b3OL/3Nvi
/9zb4v/c2+L/3Nvi/9zb4v/c2+L/3Nvi/9zb4v/c2+L/3Nvi/9zb4v/c2+L/3Nvi/93c4//d3OP/
3dzk/93d6P/c3Of/397p/9/e6f/d3ev/3d3r/9zc6v/g3+3/297r/9ve6//b3uv/297r/9ve6P/b
3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o
/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uj/297o/9ve6//b3uj/
297o/9ve6P/b3uj/297o/9ve6//b3uj/297o/9ve6P/b3uj/297o/9ve6P/b3uX/297o/9ve6P/b
3uj/297o/9ve6P/b3uj/297r/9ve6P/d3ej/297o/93d6P/b3uj/297o/9ve6P/b3uj/297o/9ve
6P/b3uX/297o/9ve5f/b3uj/297l/9ve6P/b3uX/297o/9ve5f/b3uj/297l/9zg5//b3uX/297r
/9ve6//d3ej/3d3o/9rZ6v+urbv//Pz///z8/P/f3un/2tnl/9zc5//V1OD/0tLd/9fX4v/V1OL/
1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V
1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU
4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi
/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/
1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V
1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU
4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi
/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/S0uD/
1dTi/9TT4f+wsL3/1NPh/9XU4v/U0+H/1dTi/9XU4v/X1+X/2Njm/9rZ5//c3Or/3Nzq/9vb5v/b
2+b/3Nzn/93d6P/d3ej/3d3o/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c
3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3d3o/76+yf/S
0t3/3d3o/9rZ5f/c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c
3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zd5P/d3OT/3Nvi/9vZ4P/b2eD/29ng/9vZ4P/b2eD/
29ng/9vZ4P/b2eD/29ng/9vZ4P/b2eD/29ng/9vZ4P/b2eD/29ni/9vZ4v/b2eD/29ng/9vZ4P/b
2eD/29ve/9vb3v/b297/29ve/9vZ4P/a2N//29zj/9zd5P/b3OP/2drh/7q5xP/c3Of/3d3o/9vb
5v/c3Of/397p/9vb5v/f3un/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c
3Of/3Nzn/9zd5P/c3eT/3Nzq/9zc6v/c3Of/3N3k/9zd5P/c3eT/3Nzn/9zc6v/c3Of/3N3k/9zd
4//c3eT/3Nzn/9zc6v/c3Of/3N3k/9zd5P/c3eT/3N3k/9zd5P/c3Of/3Nzn/9zc6v/c3Or/3Nzq
/9zc6v/d2ur/3dzn/93c5P/d3Of/3Nzq/9zc6v/c3Or/3Nzq/9zc6v/c3Or/3Nzq/9zc6v/c3Or/
3Nzq/9zc6v/c3Or/3Nzq/9zc6v/c3Or/3Nzn/9rd5//a3ef/2tzs/9rc7P/c3Or/3Nzq/9rY6/+u
rb3//Pz///z8/P/d3ej/29vm/9rZ5f/U097/1dTg/9XU4P/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU
4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi
/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/
1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V
1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU
4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi
/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/
1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V
1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1NPh/9XU4v/V1OL/1tbk/9LS4P+8u8n/1NPh/9bW
5P/V1OL/1dTi/9XU4v/V1OL/1dTi/9XU4v/V1OL/1tbk/9XU4P/W1uH/19fi/9jY4//b2+b/3Nzn
/93d6P/f3un/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c
3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c
3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3d3o/8bG0f/U097/3d3o/9/e6f/a2eX/3d3o
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c
3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn
/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3eT/3d7l/9zd5P/c
3eT/29zj/9vc4//b2eD/29ng/9vZ4P/b2eD/29ng/9vZ4P/b2eD/29ng/9vZ4P/b2eD/29ng/9vZ
4P/b2eD/29ng/9vZ4P/b2eD/29ng/9vZ4P/b2eD/29ng/9vZ4P/b2eD/29ng/9vZ4P/b2eD/29ng
/9rb4P/b3OL/3N3k/93e5f/c3eT/2drh/8TEz//a2eX/29vm/9/e6f/b2+b/3d3o/9zc5//d3ej/
3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c
3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc
5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3N3k/9zd5P/c3eT/3Nzn
/9zc6v/c3Or/3Nzn/9zc5//c3eT/3Nzn/9zc5//c3eT/3N3k/9zd4//c3eT/3Nzq/9zc7P/a3Oz/
2tzs/9rc7P/a3Oz/3Nzs/9zc7P/c3Oz/3Nzq/9zc6v/c3Or/3Nzn/9zc5//c3Of/3Nzn/9zd5P/c
3eT/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Of/3Nzn/9zc5//c3Or/3Nzq/9zc6v/c3Or/3Nzq/9zc
6v/c3Or/3Nzn/9rd5//a3ef/2tzs/9rc7P/c3Or/3Nzq/9rY6/+urb3//Pz///z8/P/W1uT/3d3r
/9bW5P/S0uD/0tLg/9XU4v/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/
1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U
0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT
4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh
/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/
1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U
0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT
4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh
/9TT4f/U0+H/1NPh/9LS4P/W1uT/19fl/8zM2v/a2ef/0NDd/9XU4v/U0+H/1NPh/9TT4f/U0+H/
1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/19fl/9jY5v/a
2ef/29ro/9va6P/b2uj/29ro/9va6P/a2ef/29ro/9va6P/b2uj/2tnn/9rZ5//b2uj/3Nzq/9va
6P/b2uj/29ro/9va6P/b2uj/29ro/9zc6v/c3Or/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro
/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/
29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b
2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va
6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro
/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/
29ro/9va6P/a2ef/2Njm/9rZ5//c3Or/3Nzq/9rZ5//c3Or/2Njm/9va6P/b2uj/29ro/9va6P/b
2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va
6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro
/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/
29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b
2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9nc6P/Z3Oj/2dzo/9nc
6P/b2+b/29vm/9vb5v/b2+b/29vm/9vb5v/a2+L/2tvi/9vZ4v/a2OH/2tjh/9rY4f/a2N//2tjf
/9rY3//a2N//2tjf/9rY3//a2N//2tjf/9rY3//a2N//2tjf/9rY3//a2N//2tjf/9rY3//a2N//
29ng/9rY3//a2N//2tjf/9rY4f/a2OH/2drh/9na4f/a2eX/29vm/9vb5v/b2+b/2tnl/9vb5v/b
2+b/29vm/9zc6v/Y2Ob/19fl/9/e7P/c3Or/3d3r/9bW5P/a2ef/29ro/9va6P/b2uj/29ro/9va
6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro
/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9va6P/b2uj/
29ro/9va6P/b2uj/29ro/9va6P/b2uj/29ro/9ze8P/U1ej/2tzs/8zO4P+/wNv/y8rr/8C/4P/H
yOP/1dfn/9fb5P/d4ev/1dfn/87O5//JyeX/19jx/9fY8f/X2PH/xcbe/9PU8P/Ly+f/u7vX/8LC
3/+9vdj/vsDU/8vN3//Q0+D/3eHr/9XY4v/Z3Oj/19vn/9zc7P/a2ef/297l/9XY3//b3uX/3ODn
/9PW4P/a3ef/2t3n/9bZ4//Z3Ob/1tnj/93h6//W2eP/19vk/9rd5P/d4ev/1trh/9nc4//Z3Ob/
2tzs/9na6//b2uj/2tnn/9jX6v+urb3//Pz///z8/P/Y2Ob/19fl/9HR3//U0+H/1NPh/9TT4f/U
0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT
4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh
/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/
1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U
0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT
4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh
/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/
1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/0dHf/9XU4v/U
0+H/1dTi/9HR3/+zsr//0tLg/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9TT4f/U0+H/1NPh/9HU
4f/R1OH/0dTh/9HU4f/R1OH/0dTh/9HU4f/R1OH/0NPg/9DT4P/Q0+D/0NPg/9DT4P/R1OH/09bi
/9PW4v/V2OX/1tnm/9fb5//X2+f/2dzo/9fb5//X2+f/1tnm/9fb5//X2+f/19vn/9fb5//X2+f/
19vn/9fb5//Z3Oj/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X
2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb
5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn
/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/
19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X
2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/09bi/8LF
0f/O0d3/1djl/9bZ5v/Z3Oj/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn
/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/
19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X
2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb
5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn
/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9rZ5f/a2eX/
2tvi/9rb4v/a2OH/2tjh/9rY3//a2N//2Nfe/9jX3v/a2N//2tjf/9rY3//a2N//2tjf/9rY3//a
2N//2tjf/9rY3//a2N//2tjf/9rY3//a2N//2tjf/9rY3//a2N//2trc/9ra3P/a2N//2Nfe/9na
4f/Z2uH/2Njj/9jY4//a2eX/29vm/9rZ5//a2ef/2tnn/9rZ5//Y2Ob/1tbk/7y/y//U1+P/19vn
/9nc6P/U1+P/19vn/9bZ5v/W2eb/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/
19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X
2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb5//X2+f/19vn/9fb
5//X2+f/19vn/9vd7/+horn/iYir/3p3n/+Ukbv/x8Xw/3Rzkv+3ttb/X156/6ioxP/R0ev/293y
/9TV6v+0tND/Uk9z/zIwUf96epz/v8Dj/9XU/P9jY4f/Y2OI/7y75f+6ud//v77f/8zN6P/V1+z/
1NXo/9fZ6//GyN3/bm6G/0ZGXf9TUm3/W1p4/7i32v95eJr/RENh/1pZev9NTGv/o6HK/8C+6P8y
MU7/QD9d/1FQb/9ZWHb/PTxV/1ZVcP9ra4f/2Nny/9fb5//X2+T/19nq/9fZ6v/a2ef/2Njm/9fV
6f+trLz//Pz///z8/P/Y2Ob/1dTi/9TT4f/U0+H/z87c/9TT4f/S0uD/0tLg/9LS4P/S0uD/0tLg
/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/
0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S
0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS
4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg
/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/
0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S
0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS
4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9TT4f/Q0N3/0dHf/9TT4f+vr7z/1NPh
/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/
0NPg/9DT4P/Q0+D/z9Lf/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/T
1uL/1djl/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/19vn/9fb5//X2+f/19vn/9fb5//X2+f/1tnm/9bZ
5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm
/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/
1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W
2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ
5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm
/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/X2+f/19vn/7e6xv/N0Nz/1tnm/9XY5f/U1+P/
1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W
2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ
5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm
/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/
1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W
2eb/1tnm/9bY6f/W2On/1tnm/9bZ5v/W2eb/1tnm/9jY4//Y2OP/19jf/9fY3//Y19//2Nff/9jX
3v/Y197/2Nfe/9jX3v/Y197/2Nfe/9jX3v/Y197/2Nfe/9jX3v/Y197/2Nfe/9jX3v/Y197/2Nfe
/9jX3v/Y197/2Nfe/9jX3v/Y197/19nb/9fZ2//X2N7/19je/9fY3//Z2uH/2Njj/9rZ5//Y2Ob/
2Njm/9jY6f/Y2On/19vn/9fb5//V2OX/0dTh/7a5xf/Z3Oj/1Nfj/9bZ5v/W2eb/1djl/9bZ5v/W
2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ
5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm
/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tnm/9bZ5v/W2eb/1tjp/9fa7//a3Pf/
XF54/6amy/+IhrH/ammU/5ORvf+AgKb/kJKq/8nM4P/Y2/D/2972/6Wmwv9KSmn/sLDY/8bG8f9s
bJD/WVl9/7+97/9sa5n/XVyI/7277/++vOv/vr7n/8XG6f/X2fb/ycni/76+2v+hoMD/U1Jv/8PA
7P+npM//dHOZ/29vlf9TUnb/sLDa/7a04v+GhK//VFJ5/7q55/80Mlb/1tX//76+5/83NlP/2tv+
/7i62f8yM0r/2tz1/9bZ5v/W2eP/19nq/9bY6f/Y2Ob/2Njm/9fV6f+trLz//Pz///z8/P/V1+f/
0dPk/9HR4f/V1OX/09Ll/9LP4f/Xz+D/1dHg/8/T4v/N1eD/0NPg/9LS4P/U0eD/0tLg/83V4P/N
1eD/z9Pg/9LS4P/U0t3/0tLd/83V4P/K1+D/zNbd/8/T4P/Tz+f/08/p/9DS5//N1OL/zNfZ/83W
2v/S0On/08/s/9PR4//Q0+D/y9Tk/83T5P/S09r/09TZ/9LS3f/Q0+D/0NPg/9DT4P/Q0+D/0NPg
/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/8/S3//R1OH/0NPg/9DT4P/Q0+D/
0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q
0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT
4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg
/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/0NPg/9DT4P/Q0+D/
0NPg/9DT4P/Q0+D/0dPk/8/S3//R1d7/0NPd/9DS5P/Q0uP/0dXc/83Q1//Q0uT/0NLk/9DT2v/Q
1dn/0NPg/9DT4P/Q093/0NPd/8/T4v/Q0uP/18/j/9XR4P/N1OL/zdTi/9XP5P/Vz+P/0NLj/8/T
4P/S0uP/0tLj/9LR5P/Q0uP/0tLj/9DS4//Q0uP/z9Pi/8/T4v/P0+L/0NTk/9PX5v/V2en/1trq
/9bY6f/W2On/1tnm/9bZ5v/Y2Ob/2Njm/9jY5v/Y2Ob/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/
1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V
2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY
5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl
/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/
1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V
2OX/1djl/9XY5f/W2eb/1djl/9XY5f/X2+f/19fl/9bW5P/a2ef/2Njm/9fX5f/X1+X/1djl/9XY
5f/V2OX/1Njl/9XY5f/V2OL/1djf/9fY3//a1uL/2Nfi/9TY5f/Q2+f/z9vp/9Db5//Y197/3Nbe
/9rV5f/X1+f/0tve/9Dc3v/U2Of/1dfp/9XX5//V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/
1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V
2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY
5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9rZ5//Y2Ob/2Njm
/9jY5v/Y2OP/19fi/9fY3//X2N7/19je/9fY3v/Y197/2Nfe/9jX3v/Y197/2Nfe/9jX3v/Y197/
2Nfe/9jX3v/Y197/2Nfe/9jX3v/Y197/2Nfe/9jX3v/Y197/2Nfe/9jX3v/Y197/2Nfe/9jX3v/X
2N//19fi/9XY4v/V2OL/1dji/9XY4v/V2OL/1dji/9XY4v/V2OL/1dji/9XY4v/V2OL/1dji/9XY
4v/V2OL/1djl/9TY5f/T1+b/1dnp/9ba6v/V2en/1trq/9ba6v/U2Of/1Njn/9TY5//U2OX/1Njl
/9TY5f/U2OX/1Njl/9TY5f/U2OX/1djl/9XY5f/V2OL/1Njl/9TY5f/Y1ej/19Xp/9TY6f/U2On/
19fn/9jV6P/U2OX/1Njl/9XX5//V1+f/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V
2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY
5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1djl
/9XY5f/V2OX/1djl/9bZ5v/W2eb/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1tnm/9bZ5v/V2OX/
1Nfj/9TX4//V2OX/1tnm/9bZ5v/V2OX/1djl/9XY5f/V2OX/1djl/9XY5f/V2OX/1dfn/9bY6v/V
1+n/0NLk/9fZ6v/V1+f/1tnm/9XU4P+vsLf//Pv///z7///Ozdj/zMzX/8/O2v/MzNf/zdDc/8vO
2//Lztv/ys7e/8fQ3//H0N//yNDe/8vO2//Ozdv/y83e/8rO3//IzuL/y83f/8/M3v/QzNv/0Mre
/87M3//Lzd//y83e/87N2//QzNb/0MzW/8/M3v/Lzd7/ytDY/8vP2P/PzN//z8zf/8/M2//Lztv/
ys7e/8rO3v/Ozdv/z8zb/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//O
zdv/0NDd/9LS4P/U0+H/0tLg/9DQ3f/Pztz/z87c/8/O3P/Pztz/zs3b/87N2//Ozdv/zs3b/87N
2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b
/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/
zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//O
zdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3b/87N2//Ozdv/zs3e/8vL
2//Q0N3/zs3b/87M3//EwtX/0NDd/8/O3P/NzOL/zczi/87N2//Ozdv/zszf/83M4v/OzN//zs3e
/8vN3v/Lzd7/z8ze/8/M3v/Lzd//ys7f/8vN3//Lzd//ys7e/8vN3v/PzN7/zszf/8fQ3//H0N//
y83e/87N3v/MzNz/zs3b/8/O3P/Ozdv/zMza/87N2//R0d//1dTi/9LS4P/S0uD/0tLg/9LS4P/S
0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS
4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg
/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/
0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S
0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS
4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/V0uH/1tPi
/87N2//R0d//0dHf/9fX5f/N0Nz/0dTh/9DT4P/Q0+D/0tLg/9LS4P/U0eD/1NHg/9TR4P/S0uD/
z9Pk/8/T5P/Vz+T/1c/j/9DS4//P0+D/0tLj/9LS4//Q0uP/0tLj/9PQ5P/S0uP/zdPk/8/T4v/U
0eD/1dHg/9TR4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS
4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg
/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/
0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0t3/0tLd/9LT2v/S
09r/1NLb/9TS2//U0tv/1NLb/9TS2//U0tv/1NLb/9TS2//U0tv/1NLb/9TS2//U0tv/1NLb/9TS
2//U0tv/1NLb/9TS2//U0tv/1NLb/9TS2//U0tv/1NLb/9TS2//U0tv/0tLg/9LS4P/S0uD/0tLg
/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9HR3//S0uD/1NPh/9TT4f/S0uD/0dHf/87N2P/X2N//
0dHc/9HS2f/V1OD/0dLZ/9XU4P/V1t3/0tLd/9LT2v/S0t3/0tPa/9LS3f/S09r/1NLb/9LS3f/U
0eD/0tLj/8/T4v/Q0uP/1NHg/9TR4P/Q093/0NPd/9DT3f/S0t3/1NLd/9LS3f/Q0+D/0NPg/9LS
4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg
/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/
0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9HR3//R
0d//0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0dHf/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9HR
3//S0uD/0tLg/9LS4P/S0uD/0tLg/9LS4P/S0uD/0tLg/9PW4v/P0tz/zs3b/9TT3v/X1+L/1tfe
/8fHzv+rrLH//Pv///z8///+/////P7///7////6+////v////z+///+/////v////7/8/////P/
///8///+/////v////7///7/+P/+//X//v/5//7////+/v////7//////P////n/////////////
//n////8///+/////v///v////7//////v////////7////+/////v////7////+/v///v7////+
/////v////7////+/////v////7////+/////v////7////+/////v////7///78///+/P///vz/
///+/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v//
//7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+////
/v////7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+
/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v////7/
///+/////v////7////+/////v////7////+/////v///f/+//7//P/9//v//f/7///////Jycn/
///8/////P///////////////////////v////7////+/////v///////////////v////7/////
//////7//////////////v////7////////////////////+///////////////+/////P7///7/
///+//////7////////+/v///v7///////////////7////+///+/////v////7////+//////7/
///+/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v//
//7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+////
/v////7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+
/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v////7/
///+/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v//
//7////+/////v////7////+/////v////7////+/////v////7//9jX3v/18/v//v////z+///+
////+/////v////+//////7////+/////v////7////8/////v//+/////v////+//////7/////
9f////X///7////+//////z//v////v////7/////v///////P////n///76///+/////v////7/
///+/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v//
//7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+////
/v////7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+
/////v////7///z+///8/v///P7///z+///+/////v/////+//////////7//////////v//////
///////////////////////////////////+//////////7//////////v/////////+////////
//7//////////v/////////+/////v////7////+/////v////7////+///+/P///vz///78////
/v////7///78/////v////7////+///8+///+vj//9XT2v////////7//////////v///Pz////+
///+/P////7////+/////v////7////+/////v////7///7////+//////7////6////+///+///
//j////+//z////5///++v////z/9v////j/////+v////r////+///7/////v/////+/////v//
//7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+////
/v////7////+/////v////7////+/////v////7////+/////v////7////+/////v////7////+
/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v////7/
///+/////v////7////+/////v////7////+/////v////7////+/////v////7////+/////v//
//7////+/////v////7///v8///+/////v////z+///7/P///v/////////+/v///Pz///z8////
/v///v36///8/v////z///77///////+/v////z////4/v//+/////r////8///69/z/////////
///7/vz/+/////b+/v/6////+/////z8///8+/j////1//7/+f/3+v//+vz///7////8/Pz///7/
//r69//+//n/+//4//7/+f////n////8/////P///////v////////////z////8/////P////z/
///8/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P//
//z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8////
/P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8
/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z/
///8/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P//
//z////8/////P////z//v////v8///+/P///v7////+///29PX///z////7/////v///Pr7//z6
/v///v//+/v7/////P/4+vn//v////v////6+/7///7////8///5+fv/+Pr5//7////7+/v///b9
///7////////+/v+///8////9/z/+PL4///////3+fv/+/////r//v/6//7//v/8//r9+P/8/fr/
/v/4////+f////n////5/////P////z//////////////////////////P////z////8/////P//
//z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8////
/P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8
/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z/
///8/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P//
//z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8////
/P////z////8/////P////z/+vr3/////P////z/+/r3////+f////n////4////+f/9/vf////5
////+f/8/fr//v/8//7//P/+//////7///r6+v/+/////f/+///8/v///P//+/T////+/////vj/
/v/4//78///+/P////78////+f/7////+f7///7///////z////8/////P////z////8/////P//
//z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8////
/P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8
/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z/
///8/////P////z////8/////P////z////8/////P////z////8/////P////z////5////+f//
//z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8////
/P////z////8/////P////z////8/////P////z////8/////P////z////8//7++/////z////8
/////P////z//v77/////P////z////8///++//6+fb//v36//z8/P/8/Pz//v////7////4+vn/
+fv6//7////7/////v////7//P////j///33///4/v//+/////7///7//////vr////4//3/9//7
//n//Pv////8/////v////7///799////vf////8/////P////z////8/////P////z////8////
/P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8
/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P////z/
///8/////P////z////8/////P////z////8/////P////z////8/////P////z////8/////P//
//z////8/////P////z////8/////P////z////8/////P////z////8/////P////z////8////
/////////////////////////////////////////Pz8//z8/P///vz///r2/56blf8oJiH/29XQ
/8XFxf8jKzP/fo2Q/7G4qP8VFwz/ysrK/7i4xf8ZGin/r7O//8PLu/8PFAb/usSy/8XPy/8VGiP/
srbC////9f///eX/xcqr/wgLCP8mJ0//6uv///v8//////////77////+f/7//z/+v/8//v//P//
//////v////7/////////v/8////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//z8/////v////7////++v///vr///z////8//////j/u7iu/xYTE//MyMb/6ejg/yssJf9/gHn/
ytDL/wsUEP+puK7/29zO/xoaEv+frqL/wdbN/xIaGv+oraz/29DJ/yUiGv+NnI//7v70/ywmLP94
anL/6unj/25zbP89REb/xMzV//b////5////+/////v////6+v3////////+//////z////8///+
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////7////6//7/
+v/+//7///////z////8///++v/Jw7//MS0p/2hjX//i3tn/fHt3/1BST/+Ynpn/WWJe/1FcWP/C
ycb/b2pm/1dRRv/NzLD/k5qJ/yArN/+6wtz/raGg/zMrI/+5wbb/s7q1/zktLf+2paH/yMi7/0BJ
Qf+Nm6L/7/v///v/////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////z////8/////P//////////////
///////////////////////////////+/////v////7////+////////////////////////////
/////////////////////////////////////////////////////////////////////P//////
///8//////////z//////////P/////////8//7+/v////z//////////P///////v77///++v/+
+fT/+fjy//r58/+jop//IyMh/9PT0P/a3Nj/IyYm/4KIhv+8w8D/DRMQ/8DKyf+8x8X/Fhwb/7O6
tf/6/u//1svF/ysRHP8WABH/097s//P////75vb/JBQb/46NkP/o9Pf/Iic0/2tpfv//+P////f/
//7//P/1/PL//v/8////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////////Pz8//z8/P////n////4//768//7+PD/rKmg/w8RDf+Ck5L/4/n5/3yFgf9t
c27/+v///+r29f98iIj/Xmpo/4GMgv9faV//+P/6/+/99P+Cjon/Zmxn/7Oyq/8WFQv/7fXO/7W+
tP8KBzL/8O7///r8///7/////v/5//v+9//7/////v////7///////////7////+//////z////5
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////Pz///////////z////5//759P/X
08////nz///++P//+/f///vz////4//T0bz/CgoK/3t5ff/1+Oj/iJaN/1Fwf//h+f////ra/6CP
bP9ZbWP/ZY6Y/0xujf/a7v////vo/6eVdf9mcFz/q8DF/wwTMP+orNP/+fLh/7Wumf8pJzv/r7Hd
//j8///6/v//9vr///7/////////+/v4///+/////v////7////+///////////////////+////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////+/////v///9jg1//w9vH//ff////7
////++n////m/+Tk1v9SVFP/NzlC/77Eyv/Ayrb/b3tq/6CuuP/1////xMe4/3N2Xf96fWf/eIJ3
/3iJmf/z////5uHF/4iDZP98gXr/m6Ww/yEiNP+no6//t6+U/05MOP9gaoT/7v7///r/////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////7+/v/////////////////+/v7/+/v7/9bZ1f/+/ff///r2///79P//+/j/+fTw
/7m9vP8ACgr/g5CQ/+v4+f+Dh4j/Z2lo//v////1////dYWJ/2VzdP/+//////b5//7l+v8fDhv/
2eHv//b////RvNb/FQkX//r+///w/f//ysje/w8MF//7+///+v7///7////+////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////Pz8//z8
/P////z/7/Dp/0lKRf8AAAD/BQcA/wAEAP8LExf/ZW50//716v96cGb/BQUF/wAKDv9fcHv/8P7/
//r37f+GfnH/AAAA/wcLC/9gbnj/6vb////18f///ez////m/8DGvv8cGjf/9/T///r8///z9/n/
/v////7////+/////v///////P////////////////////z////8////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////////////////vz////+//////n////1//799//Y1NX///f////8/////+b/aWlS
/wgECf8FAAr/AAQA/wQFAP9ZWlX/8vT2/4OKkv8FCQz/BwUH/1xcXP/j8uz/7//7/5ufo/8NDBD/
AAAE/1FVVv/j7/D/+P7//8vAx/8bExb/BQQA/wgKCf+Xmaz/6u3///v+///7/////v////v+9//6
/PP////4////+f///v////7////+//////////////7////+////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////6+vr/+vr3/9rg2//09vX///z///3y9P+MhHX/FhQI/wAAAP8AAAX/
AAcN/yotMP+prpv/wsq3/y80Ov8AAAz/LCsw/62uqP/+//P/2+TZ/1hiY/8ABwv/EA4T/4yIif//
//X/3+fW/2VsZP8EBQf/CgAK/y8oNP/O1uT/8/////v/////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////////////////7+/v//////
///////////+/v7/+/z//9fb5P/3+fv////w//Hp0P9OSDj/CggA/wAAB/8AAA7/BQsU/2Rtdf/7
/vf/fX1u/wUFAP8ABQD/Z3F7//L////1+/////z8//7p9v8jExv/2uvr/+//////+v//wK2+/wAA
Cf8AAAn/ISor/+Xv8///+v////z///b3+v/6/////v//////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////Pz8//z8/P8ADgEAAAMAAAABAeAAAAEB
AAMAAAABAG0AAAECAAMAAAAEAAMyNgEDAAMAAAABAAEAAAEGAAMAAAABAAIAAAERAAQAAAACAAMy
PgESAAMAAAABAAEAAAEVAAMAAAABAAQAAAEWAAMAAAABAEQAAAEXAAQAAAACAAMyRgEcAAMAAAAB
AAEAAAFSAAMAAAABAAEAAAFTAAMAAAAEAAMyTodzAAcAAAUwAAMyVgAAAAAACAAIAAgACAAAAAgA
Af4IAAH+AAABM4AAAQABAAEAAQAABTBhcHBsAiAAAG1udHJSR0IgWFlaIAfZAAIAGQALABoAC2Fj
c3BBUFBMAAAAAGFwcGwAAAAAAAAAAAAAAAAAAAAAAAD21gABAAAAANMtYXBwbAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC2RzY20AAAEIAAAC8mRlc2MAAAP8
AAAAb2dYWVoAAARsAAAAFHd0cHQAAASAAAAAFHJYWVoAAASUAAAAFGJYWVoAAASoAAAAFHJUUkMA
AAS8AAAADmNwcnQAAATMAAAAOGNoYWQAAAUEAAAALGdUUkMAAAS8AAAADmJUUkMAAAS8AAAADm1s
dWMAAAAAAAAAEQAAAAxlblVTAAAAJgAAAn5lc0VTAAAAJgAAAYJkYURLAAAALgAAAepkZURFAAAA
LAAAAahmaUZJAAAAKAAAANxmckZVAAAAKAAAASppdElUAAAAKAAAAlZubE5MAAAAKAAAAhhuYk5P
AAAAJgAAAQRwdEJSAAAAJgAAAYJzdlNFAAAAJgAAAQRqYUpQAAAAGgAAAVJrb0tSAAAAFgAAAkB6
aFRXAAAAFgAAAWx6aENOAAAAFgAAAdRydVJVAAAAIgAAAqRwbFBMAAAALAAAAsYAWQBsAGUAaQBu
AGUAbgAgAFIARwBCAC0AcAByAG8AZgBpAGkAbABpAEcAZQBuAGUAcgBpAHMAawAgAFIARwBCAC0A
cAByAG8AZgBpAGwAUAByAG8AZgBpAGwAIABHAOkAbgDpAHIAaQBxAHUAZQAgAFIAVgBCTgCCLAAg
AFIARwBCACAw1zDtMNUwoTCkMOuQGnUoACAAUgBHAEIAIIJyX2ljz4/wAFAAZQByAGYAaQBsACAA
UgBHAEIAIABHAGUAbgDpAHIAaQBjAG8AQQBsAGwAZwBlAG0AZQBpAG4AZQBzACAAUgBHAEIALQBQ
AHIAbwBmAGkAbGZukBoAIABSAEcAQgAgY8+P8GWHTvYARwBlAG4AZQByAGUAbAAgAFIARwBCAC0A
YgBlAHMAawByAGkAdgBlAGwAcwBlAEEAbABnAGUAbQBlAGUAbgAgAFIARwBCAC0AcAByAG8AZgBp
AGUAbMd8vBgAIABSAEcAQgAg1QS4XNMMx3wAUAByAG8AZgBpAGwAbwAgAFIARwBCACAARwBlAG4A
ZQByAGkAYwBvAEcAZQBuAGUAcgBpAGMAIABSAEcAQgAgAFAAcgBvAGYAaQBsAGUEHgQxBEkEOAQ5
ACAEPwRABD4ERAQ4BDsETAAgAFIARwBCAFUAbgBpAHcAZQByAHMAYQBsAG4AeQAgAHAAcgBvAGYA
aQBsACAAUgBHAEIAAGRlc2MAAAAAAAAAFEdlbmVyaWMgUkdCIFByb2ZpbGUAAAAAAAAAAAAAABRH
ZW5lcmljIFJHQiBQcm9maWxlAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAABYWVogAAAAAAAAWnUAAKxzAAAXNFhZWiAAAAAAAADzUgABAAAAARbPWFlaIAAA
AAAAAHRNAAA97gAAA9BYWVogAAAAAAAAKBoAABWfAAC4NmN1cnYAAAAAAAAAAQHNAAB0ZXh0AAAA
AENvcHlyaWdodCAyMDA3IEFwcGxlIEluYy4sIGFsbCByaWdodHMgcmVzZXJ2ZWQuAHNmMzIAAAAA
AAEMQgAABd7///MmAAAHkgAA/ZH///ui///9owAAA9wAAMBs

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



And here is Stephen's IETF hotel graph, scaled to roughly match the =
above graph:

--Apple-Mail-135-966062994
Content-Disposition: inline;
	filename=nomargin.jpg
Content-Type: image/jpg;
	x-unix-mode=0644;
	name="nomargin.jpg"
Content-Transfer-Encoding: base64

/9j/4QBeRXhpZgAATU0AKgAAAAgAAgExAAIAAAAGAAAAJodpAAQAAAABAAAALAAAAABTa2l0Y2gA
A5AAAAcAAAAEMDIxMKACAAQAAAABAAAB2qADAAQAAAABAAAAigAAAAD/4AAQSkZJRgABAQAAAQAB
AAD/4hn8SUNDX1BST0ZJTEUAAQEAABnsYXBwbAIQAABtbnRyUkdCIFhZWiAH2wAIAAoAEgAxAAZh
Y3NwQVBQTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA9tYAAQAAAADTLWFwcGwAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABFkZXNjAAABUAAAAGJkc2NtAAAB
tAAAAkJjcHJ0AAAD+AAAANB3dHB0AAAEyAAAABRyWFlaAAAE3AAAABRnWFlaAAAE8AAAABRiWFla
AAAFBAAAABRyVFJDAAAFGAAACAxhYXJnAAANJAAAACB2Y2d0AAANRAAABhJuZGluAAATWAAABj5j
aGFkAAAZmAAAACxtbW9kAAAZxAAAAChiVFJDAAAFGAAACAxnVFJDAAAFGAAACAxhYWJnAAANJAAA
ACBhYWdnAAANJAAAACBkZXNjAAAAAAAAAAhEaXNwbGF5AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
bWx1YwAAAAAAAAASAAAADG5sTkwAAAAWAAAA6GRhREsAAAAcAAAA/nBsUEwAAAASAAABGmVuVVMA
AAASAAABLG5iTk8AAAASAAABPmZyRlIAAAAWAAABUHB0QlIAAAAYAAABZnB0UFQAAAAWAAABfnpo
Q04AAAAMAAABlGVzRVMAAAASAAABoGphSlAAAAAOAAABsnJ1UlUAAAAkAAABwHN2U0UAAAAQAAAB
5HpoVFcAAAAOAAAB9GRlREUAAAAQAAACAmZpRkkAAAAQAAACEml0SVQAAAAUAAACImtvS1IAAAAM
AAACNgBLAGwAZQB1AHIAZQBuAC0ATABDAEQATABDAEQALQBmAGEAcgB2AGUAcwBrAOYAcgBtAEsA
bwBsAG8AcgAgAEwAQwBEAEMAbwBsAG8AcgAgAEwAQwBEAEYAYQByAGcAZQAtAEwAQwBEAEwAQwBE
ACAAYwBvAHUAbABlAHUAcgBMAEMARAAgAEMAbwBsAG8AcgBpAGQAbwBMAEMARAAgAGEAIABDAG8A
cgBlAHNfaYJyACAATABDAEQATABDAEQAIABjAG8AbABvAHIwqzDpMPwAIABMAEMARAQmBDIENQRC
BD0EPgQ5ACAEFgQaAC0ENAQ4BEEEPwQ7BDUEOQBGAOQAcgBnAC0ATABDAERfaYJybbJmdphveTpW
aABGAGEAcgBiAC0ATABDAEQAVgDkAHIAaQAtAEwAQwBEAEwAQwBEACAAYwBvAGwAbwByAGnO7Lfs
ACAATABDAEQAAHRleHQAAAAAQ29weXJpZ2h0IEFwcGxlLCBJbmMuLCAyMDExAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABYWVogAAAAAAAA
81IAAQAAAAEWz1hZWiAAAAAAAABvMQAAOWMAAAGDWFlaIAAAAAAAAGDuAAC3agAACBJYWVogAAAA
AAAAJrcAAA8yAADJl2N1cnYAAAAAAAAEAAAAAAUACgAPABQAGQAeACMAKAAtADIANgA7AEAARQBK
AE8AVABZAF4AYwBoAG0AcgB3AHwAgQCGAIsAkACVAJoAnwCjAKgArQCyALcAvADBAMYAywDQANUA
2wDgAOUA6wDwAPYA+wEBAQcBDQETARkBHwElASsBMgE4AT4BRQFMAVIBWQFgAWcBbgF1AXwBgwGL
AZIBmgGhAakBsQG5AcEByQHRAdkB4QHpAfIB+gIDAgwCFAIdAiYCLwI4AkECSwJUAl0CZwJxAnoC
hAKOApgCogKsArYCwQLLAtUC4ALrAvUDAAMLAxYDIQMtAzgDQwNPA1oDZgNyA34DigOWA6IDrgO6
A8cD0wPgA+wD+QQGBBMEIAQtBDsESARVBGMEcQR+BIwEmgSoBLYExATTBOEE8AT+BQ0FHAUrBToF
SQVYBWcFdwWGBZYFpgW1BcUF1QXlBfYGBgYWBicGNwZIBlkGagZ7BowGnQavBsAG0QbjBvUHBwcZ
BysHPQdPB2EHdAeGB5kHrAe/B9IH5Qf4CAsIHwgyCEYIWghuCIIIlgiqCL4I0gjnCPsJEAklCToJ
TwlkCXkJjwmkCboJzwnlCfsKEQonCj0KVApqCoEKmAquCsUK3ArzCwsLIgs5C1ELaQuAC5gLsAvI
C+EL+QwSDCoMQwxcDHUMjgynDMAM2QzzDQ0NJg1ADVoNdA2ODakNww3eDfgOEw4uDkkOZA5/DpsO
tg7SDu4PCQ8lD0EPXg96D5YPsw/PD+wQCRAmEEMQYRB+EJsQuRDXEPURExExEU8RbRGMEaoRyRHo
EgcSJhJFEmQShBKjEsMS4xMDEyMTQxNjE4MTpBPFE+UUBhQnFEkUahSLFK0UzhTwFRIVNBVWFXgV
mxW9FeAWAxYmFkkWbBaPFrIW1hb6Fx0XQRdlF4kXrhfSF/cYGxhAGGUYihivGNUY+hkgGUUZaxmR
GbcZ3RoEGioaURp3Gp4axRrsGxQbOxtjG4obshvaHAIcKhxSHHscoxzMHPUdHh1HHXAdmR3DHewe
Fh5AHmoelB6+HukfEx8+H2kflB+/H+ogFSBBIGwgmCDEIPAhHCFIIXUhoSHOIfsiJyJVIoIiryLd
IwojOCNmI5QjwiPwJB8kTSR8JKsk2iUJJTglaCWXJccl9yYnJlcmhya3JugnGCdJJ3onqyfcKA0o
PyhxKKIo1CkGKTgpaymdKdAqAio1KmgqmyrPKwIrNitpK50r0SwFLDksbiyiLNctDC1BLXYtqy3h
LhYuTC6CLrcu7i8kL1ovkS/HL/4wNTBsMKQw2zESMUoxgjG6MfIyKjJjMpsy1DMNM0YzfzO4M/E0
KzRlNJ402DUTNU01hzXCNf02NzZyNq426TckN2A3nDfXOBQ4UDiMOMg5BTlCOX85vDn5OjY6dDqy
Ou87LTtrO6o76DwnPGU8pDzjPSI9YT2hPeA+ID5gPqA+4D8hP2E/oj/iQCNAZECmQOdBKUFqQaxB
7kIwQnJCtUL3QzpDfUPARANER0SKRM5FEkVVRZpF3kYiRmdGq0bwRzVHe0fASAVIS0iRSNdJHUlj
SalJ8Eo3Sn1KxEsMS1NLmkviTCpMcky6TQJNSk2TTdxOJU5uTrdPAE9JT5NP3VAnUHFQu1EGUVBR
m1HmUjFSfFLHUxNTX1OqU/ZUQlSPVNtVKFV1VcJWD1ZcVqlW91dEV5JX4FgvWH1Yy1kaWWlZuFoH
WlZaplr1W0VblVvlXDVchlzWXSddeF3JXhpebF69Xw9fYV+zYAVgV2CqYPxhT2GiYfViSWKcYvBj
Q2OXY+tkQGSUZOllPWWSZedmPWaSZuhnPWeTZ+loP2iWaOxpQ2maafFqSGqfavdrT2una/9sV2yv
bQhtYG25bhJua27Ebx5veG/RcCtwhnDgcTpxlXHwcktypnMBc11zuHQUdHB0zHUodYV14XY+dpt2
+HdWd7N4EXhueMx5KnmJeed6RnqlewR7Y3vCfCF8gXzhfUF9oX4BfmJ+wn8jf4R/5YBHgKiBCoFr
gc2CMIKSgvSDV4O6hB2EgITjhUeFq4YOhnKG14c7h5+IBIhpiM6JM4mZif6KZIrKizCLlov8jGOM
yo0xjZiN/45mjs6PNo+ekAaQbpDWkT+RqJIRknqS45NNk7aUIJSKlPSVX5XJljSWn5cKl3WX4JhM
mLiZJJmQmfyaaJrVm0Kbr5wcnImc951kndKeQJ6unx2fi5/6oGmg2KFHobaiJqKWowajdqPmpFak
x6U4pammGqaLpv2nbqfgqFKoxKk3qamqHKqPqwKrdavprFys0K1ErbiuLa6hrxavi7AAsHWw6rFg
sdayS7LCszizrrQltJy1E7WKtgG2ebbwt2i34LhZuNG5SrnCuju6tbsuu6e8IbybvRW9j74KvoS+
/796v/XAcMDswWfB48JfwtvDWMPUxFHEzsVLxcjGRsbDx0HHv8g9yLzJOsm5yjjKt8s2y7bMNcy1
zTXNtc42zrbPN8+40DnQutE80b7SP9LB00TTxtRJ1MvVTtXR1lXW2Ndc1+DYZNjo2WzZ8dp22vvb
gNwF3IrdEN2W3hzeot8p36/gNuC94UThzOJT4tvjY+Pr5HPk/OWE5g3mlucf56noMui86Ubp0Opb
6uXrcOv77IbtEe2c7ijutO9A78zwWPDl8XLx//KM8xnzp/Q09ML1UPXe9m32+/eK+Bn4qPk4+cf6
V/rn+3f8B/yY/Sn9uv5L/tz/bf//cGFyYQAAAAAAAwAAAAJmZgAA8qcAAA1ZAAAT0AAACg52Y2d0
AAAAAAAAAAAAAwEAAAIAAAAHAB4ASgCLAOMBKgFuAcACGQJ0AtoDSQPDBEcE1AVtBhEGwgd8CD4J
BwndCrkLnAyPDacO3BAQEUsSiRPJFREWXBesGQQaYRu9HSAejB/4IWQi2iROJcknLyiOKesrSSyf
LfYvQzCNMdAzDTRCNXM2nDfAOOA5/TsXPCs9OT5FP1JAY0FzQoRDl0SrRb9G00fpSP9KFUssTENN
W05pT3ZQhVGSUp9Tq1S3VcJWy1fSWNlZ31rjW+hc7V3oXtxfzmC/Ya9inmONZHplZmZRZztoJGkO
afZq32vGbKltjW5wb1NwN3Eacfxy3nPAdKN1hXZmd0l4K3kKeep6zHuwfJh9hH53f3GAcoF6goqD
oYS9hd+HCYg8iXCKo4vWjQqOPI9tkJ6RzpL9lCyVW5aKl7aY4JoLmzWcX52JnrKf26EEoi2jVqR/
paim0af4qSCqTKt8rLKt8a86sI+x77NbtM+2T7fUuTy6dLupvNy+C78zwFbBccKFw5HElsWWxpHH
iMiDyYfKjcuNzIXNdM5Xzy7P+9DA0XvSNtL209fUudWa1n3XX9hC2SXaCdrt29Hctd2a3n3fYOBE
4SniEOL54+bk1uXJ5sHnu+i56bnqpeuO7HbtXu5F7yvwEPD18dryvvOh9IX1aPZL9y/4E/j3+dz6
wPui/IT9Zf5E/yL//wAAAAYAGgBAAHgAxQETAUwBkAHfAjMCjgLzA18D1gRVBN0FcAYOBrcHZQga
CNoJnApnC0IMPQ1UDmgPgBCgEcES6RQVFUQWeRevGO8aLhtyHLweCx9WIKoh/yNBJIElvyb8KDcp
aiqdK8ss8i4VLzMwSDFbMmczcTR5NX02ejdqOFs5TDo9OzA8Ij0VPgg++j/tQOFB1ULKQ75Es0Wn
RphHiEh3SWhKWUtITDhNJ04VTwRP9FDiUdFSwFOwVJ5ViFZzV15YSVkzWh1bBlvuXNZdvV6jX4pg
b2FUYjRjDGPiZLllj2ZmZzxoEWjmabtqkWtlbDptD23jbrdviHBZcStx/HLOc6B0cnVDdhV253e5
eIx5XnowewJ713yvfYt+bX9VgESBOoI5gz2ESIVYhm6Hh4ilicOK4Yv+jRyOOY9WkHORkJKsk8mU
5pYClxyYNplRmm2bi5ysndCe9qAioVCig6O5pPGmLqdxqLSp96s5rHytvq8AsEGxg7LFtAW1R7aI
t8e5B7pFu4K8vb30vybAU8F7wp7Du8TVxenG98gEyRPKIcsvzD3NTM5az2jQd9GG0pXTotSv1bzW
ydfW2OXZ9NsD3BTdJd4430zgZ+Gj4unkJ+Va5obnqujH6eHq+OwO7SXuP+9b8IDx0PMz9JP18/dS
+LT6GPuF/Pj+d///AAAABAARACoATgCAAMABBwE6AXQBtwICAk0CoAL7A14DygQ8BLYFOAXCBlAG
4wd7CBsIxwmNCmMLPAwbDP4N4g7LD7UQpRGYEo4TiBSFFYYWixeTGJ8Zqxq4G70cvR2+Hr8fviC7
IbUiqyOdJIsldSZcJ0AoIikAKdsqtyuLLFYtIC3qLrUvgDBLMRYx4TKrM3U0PzUJNdM2nTdoODQ4
+Dm+OoU7SzwSPNo9oj5qPzI//EDGQZFCXUMqQ/dEw0WPRltHJ0fySL5JikpWSyFL60y2TYBOTE8W
T+FQq1FzUjtTAlPKVJJVWlYgVudXrlh1WTtaAlrJW49cU10WXdlem19dYB1g3WGdYl1jHGPaZJhl
VmYTZs9ni2hFaQBpu2p2azFr7GynbWJuHG7Xb5NwTnEIccFyenMzc+x0pXVedhd2z3eHeD94+Hmw
eml7IHvZfJR9VH4ZfuV/uICUgXmCZoNchFmFW4Zlh3WIhYmWiqaLtozGjdWO5Y/0kQOSE5MilDCV
OpZDl0qYUZlZmmKbb5x/nZOerJ/LoO+iJaN5pNCmJ6d+qNaqLauErNuuMa+IsN6yNrOLtN+2M7eH
uNy6M7uKvOK+PL+YwPbCVMO1xSfGpMgtycXLa80kzuzQx9Kx1KnWsNjB2t3dAN8w4afkhueK6rfu
D/GI9Rj4tfxX//8AAG5kaW4AAAAAAAAGNgAApeMAAFahAABRWwAApysAACWbAAAOFAAAUA0AAFQ5
AAJCjwAB2ZkAAUeuAAMBAAACAAAADQAnAEYAZgCHAKgAyQDrAQ4BMQFVAXoBnQG8AdsB/AIdAj8C
YgKGAqoCzwL0AxsDQQNoA5ADuQPiBAsENQRgBIwEuATkBRIFPwVuBaEF1QYKBkEGeAayBuwHKAdn
B6cH6QguCHUIvwkLCVoJrAoBClgKsgsOC24L0gw4DKANCA1yDd4OSg65DygPmhANEIEQ9xFvEegS
YxLfE2IT5xRtFPYVgRYOFp0XLxfDGFsY9RmRGjEa0xt3HB0c0B2HHkIfAB/BIIUhTSIZIugjuySR
JWomRiclKAwo9SniKtIrxCy6LbMusC+vMLIxuDLAM8s03jXxNwQ4FTkjOi07MTwwPSo+ID8SQAJA
70HbQr9DokSIRW9GWEdCSC9JHkoPSwNL+EzwTepO5U/iUOFR5FLrU/NU/VYJVxdYJ1k5Wk1bY1x7
XZVesF/OYO1iDmMzZFllf2ajZ8Vo42n9axJsIW0qbi5vLXApcSJyFnMJc/p06XYad014hHm/ev58
RX2TfuuATYG7gzSEuYZJh+OJh4shjK6OQI/gkZGTWJU9l0mZd5vFnhugDqICo/ml8qfuqeyr7K3v
r/Wx/bQIthu4L7pEvFm+acB2wn7EgMZ9yHbKbMxgzovQuNLq1SHXXdmf2+beMeCB4tXlK+eI6efs
R+6q8RDze/Xt+Gb65/1w//8AAAAPAC4AUQB1AJoAvwDkAQsBMgFbAYQBqQHLAe8CFAI6AmACiAKw
AtkDAwMtA1kDhQOxA98EDQQ8BGsEmwTNBP4FMQVkBZwF1QYPBkwGiQbIBwoHTQeSB9oIJQhyCMIJ
FglsCcYKIwqCCuULSgu6DCsMnw0VDYwOBg6CDwAPgRADEIgRDhGXEiISrxNAE9UUbRUGFaIWQRbi
F4YYLRjWGYEaMBrgG5McSB0EHcIegx9GIAwg1iGiInMjRiQeJPgl1ia3J6AolymRKo4rjiySLZou
pi+1MMgx3jL3NBU1OjZjN444vTnvOyU8Xz2bPttAHkFkQq9D+0VFRotHy0kFSjdLYkyGTaZOwU/a
UPBSBFMWVCpVQFZZV3NYj1muWs5b8V0WXj1fZmCRYb5i7mQjZVhmj2fGaP1qNGtpbJ5t0W8CcDJx
YHKOc7t06HYPdzd4YHmLerh7530Xfkl/fYCygeqDI4RdhZqG2IgXiVmKnovkjS2OeI/GkRiSb5PM
lTCWm5gOmYmbDJyVniefx6FpowyksqZaqASpsKtfrRCuw7B4si+z6LWnt2m5LbryvLq+gsBMwhfD
48Wwx3zJSssZzNDOVc/j0XrTHtTO1ovYU9om3AHd4t/G4avjj+Vy51PpG+qf7Cftse8+8M7yX/Pv
9YD3D/iZ+h77n/0a/o///wAAABcAQQBwAJ8AzwD/ATIBZgGZAcUB8wIiAlIChAK3AuwDIQNYA5AD
yQQDBD4EegS3BPUFNQV2Bb0GBQZPBpsG6gc7B5AH6AhECKQJCAlwCdwKTArACzcLugxCDMwNWQ3q
Dn4PFQ+wEE8Q8RGWEj4S6ROdFFMVDRXKFokXTBgSGNoZpRpyG0EcExzrHcYepB+GIGshVCJBIzIk
JyUfJhsnGiggKSsqOStLLGEtfC6aL70w5DIOMzw0cjWuNu84NTmBOtI8KD2EPuZATEG3QytEpEYh
R6NJKUq1TERN2E9wUQxSsFRbVglXvVl2WzRc+F7AYI1iXmQ2Zgxn2Wmaa0ls6W55b/xxdHLldFB1
s3cReHJ51Hs6fKF+C394gOeCWIPMhUKGuog0ibaLPYzJjlmP65F+kxGUopYvl7mZPpq/nDydtp8F
oEyhlaLfpCqld6bFqBWpZqq6rA6tZK68sBWxcLLLtCi1irbtuFG5t7sevIa97r9XwMHCK8OVxP/G
asfUyUDKq8wWzXPOytAb0WjSrNPq1SPWV9eC2KjZytrl2/zdEN4f3yvgNeE64j7jQORA5T7mOuc3
6DHpKuoi6w7r6ey57XfuNe7s76XwWfEK8bzyZvMQ87j0XPUA9aL2Qvbi93/4HPi5+VX58PqM+yf7
wvxe/Pj9k/4v/sn/ZP//AABzZjMyAAAAAAABDEIAAAXe///zJgAAB5IAAP2R///7ov///aMAAAPc
AADAbG1tb2QAAAAAAAAGEAAAnKMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD/2wBDAAMCAgICAgMC
AgIDAwMDBAcEBAQEBAgGBgUHCgkKCgoJCQkLDA8NCwsPDAkJDRIODxAQERERCg0TFBMRFA8RERH/
2wBDAQMDAwQEBAgEBAgRCwkLERERERERERERERERERERERERERERERERERERERERERERERERERER
ERERERERERERERH/wAARCACKAdoDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQF
BgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS
0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4
eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi
4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl
8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImK
kpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP0
9fb3+Pn6/9oADAMBAAIRAxEAPwD9Us0bhjPNYfjHRdR17SYrPS7iGC4jvLe5Dys4UCOVZCPkIJyF
24PHPNcnq3w017WPFJ8RSarZW7Jd288Qi80gCMYbdGxKu3LAE8AEYAIyQD0misyFdQmu7uI6k6rD
IFQCJOhUH096n+yX3/QVk/79J/hQBcoqn9kvv+grJ/36T/Cj7Jff9BWT/v0n+FAFyiqf2S+/6Csn
/fpP8KPsl9/0FZP+/Sf4UAXKKp/ZL7/oKyf9+k/wo+yX3/QVk/79J/hQBcoqn9kvv+grJ/36T/Cj
7Jff9BWT/v0n+FAFyiqf2S+/6Csn/fpP8KPsl9/0FZP+/Sf4UAXKKp/ZL7/oKyf9+k/wo+yX3/QV
k/79J/hQBcoqn9kvv+grJ/36T/Cj7Jff9BWT/v0n+FAFuiqn2S+/6Csn/fpP8KPsl9/0FZP+/Sf4
UAXKTFVPsl9/0FZP+/Sf4UfZL7/oKyf9+k/wosBbxxiiqn2S+/6Csn/fpP8ACj7Jff8AQVk/79J/
hQBbPNAGKqfZL7/oKyf9+k/wo+yX3/QVk/79J/hQBcpMVU+yX3/QVk/79J/hR9kvv+grJ/36T/Cg
C3ijGKqfZL7/AKCsn/fpP8KPsl9/0FZP+/Sf4UrAXKKp/ZL7/oKyf9+k/wAKPsl9/wBBWT/v0n+F
MC3ilqn9kvv+grJ/36T/AAo+yX3/AEFZP+/Sf4UAXKKp/ZL7/oKyf9+k/wAKPsl9/wBBWT/v0n+F
AFyiqf2S+/6Csn/fpP8ACj7Jff8AQVk/79J/hQBboxVT7Jff9BWT/v0n+FH2S+/6Csn/AH6T/CgC
5RVP7Jff9BWT/v0n+FH2S+/6Csn/AH6T/CgC5RVP7Jff9BWT/v0n+FH2S+/6Csn/AH6T/CgC5RVP
7Jff9BWT/v0n+FH2S+/6Csn/AH6T/CgC5RVP7Jff9BWT/v0n+FH2S+/6Csn/AH6T/CgC5RVP7Jff
9BWT/v0n+FH2S+/6Csn/AH6T/CgC5RVP7Jff9BWT/v0n+FH2S+/6Csn/AH6T/CgC5RVP7Jff9BWT
/v0n+FH2S+/6Csn/AH6T/CgC5RVP7Jff9BWT/v0n+FH2S+/6Csn/AH6T/CgC5RVP7Jff9BWT/v0n
+FcF8YPjL4J+Bei2HiL4jeLZrCyvr1bOEixabe+C7DEaEj5FY59qunTnUkoU1dvoiKlSNOLnN2SP
SaKzfDniDS/Feg6d4m0S4M+narax3tpKUKGSKRQ6NtIBGQQcEZrSqWmnZlJpq6EJAGTSb19f0pWG
5SPWvP08A+IW0yw0u5vtOaKz1h9SLKZhJ5bTSShFYscEblXPOQCOM8IZ2ll/x/ah/wBdU/8ARa1d
rItLOdr/AFD/AImdyv71Ogj/ALi/7NXPsU//AEFbv8o//iKALdFVPsU//QVu/wAo/wD4ij7FP/0F
bv8AKP8A+IoAt0VU+xT/APQVu/yj/wDiKPsU/wD0Fbv8o/8A4igC3RVT7FP/ANBW7/KP/wCIo+xT
/wDQVu/yj/8AiKALdFVPsU//AEFbv8o//iKPsU//AEFbv8o//iKALdFVPsU//QVu/wAo/wD4ij7F
P/0Fbv8AKP8A+IoAt0VU+xT/APQVu/yj/wDiKPsU/wD0Fbv8o/8A4igC3RVT7FP/ANBW7/KP/wCI
o+xT/wDQVu/yj/8AiKALdFVPsU//AEFbv8o//iKPsU//AEFbv8o//iKALdFVPsU//QVu/wAo/wD4
ij7FP/0Fbv8AKP8A+IoAt0VU+xT/APQVu/yj/wDiKPsU/wD0Fbv8o/8A4igC3RVT7FP/ANBW7/KP
/wCIo+xT/wDQVu/yj/8AiKALdFVPsU//AEFbv8o//iKPsU//AEFbv8o//iKALdFVPsU//QVu/wAo
/wD4ij7FP/0Fbv8AKP8A+IoAt0VU+xT/APQVu/yj/wDiKPsU/wD0Fbv8o/8A4igC3RVT7FP/ANBW
7/KP/wCIo+xT/wDQVu/yj/8AiKALdFVPsU//AEFbv8o//iKPsU//AEFbv8o//iKALdFVPsU//QVu
/wAo/wD4ij7FP/0Fbv8AKP8A+IoAt0VU+xT/APQVu/yj/wDiKPsU/wD0Fbv8o/8A4igC3RVT7FP/
ANBW7/KP/wCIo+xT/wDQVu/yj/8AiKALdFVPsU//AEFbv8o//iKPsU//AEFbv8o//iKALdFVPsU/
/QVu/wAo/wD4ij7FP/0Fbv8AKP8A+IoAt0VU+xT/APQVu/yj/wDiKPsU/wD0Fbv8o/8A4igC3RVM
2U//AEFbv8o//iK4H4z/ABh8GfAbwrH4x+IGvarFp812llGLWCOaV5GDEYTaCQApye1XTpyqTUIK
7ZE6kYRc5uyR6VRXJ+APFmk/ErwZpHjzwzrGpNpeuWy3doZ4Y45Chzjcu3g8V0P2Kf8A6Ct3+Uf/
AMRUyi4ycZKzRUZKSUlsy3RVT7FP/wBBW7/KP/4ij7FP/wBBW7/KP/4ikMt0VU+xT/8AQVu/yj/+
IpDZzj/mK3f5Rf8AxFAE9zcRW1vJczzJFHEpd3c4VVHJJJ6ACvkTWPCEP7b/AIkn8Q+Jxew/B3wx
d/ZPD0Vu7W8viG7ZhHLe+ZjcLdQSkePvHcc9RXRfFLUNc/aI8f3H7OvgfW7+PwlpLK3xC1yFlUBc
5GmQOE/1z8FyD8q5B7g+9WnhfTvC+g2GiaEDZ6bpv2e2tbOFI0iiiV0CoAFGAAK74SlhIqpF2qPb
+6u/q+nZa9UcE4rFycHrTW/959vRfi/maHhfw5pnhDw5pnhXRYnj0/R7OKxtUdy7LFGgRQWPJOFH
J61qUUVwttu7O5JJWQ0uq/eYD601riBSA0yKScDLYyfSsfxd4em8TaWmnwXVvbyR3dvdpJNbmYKY
pVkGAGXBO3Gc8ZPFc3qvwvuNX8RN4gn1m0ikN1a3a+VZMHR4VKkhvN2ksGI+ZSAOx60mM7Oy/wCP
7UP+uqf+i1q7WPa2U73+oH+07pP3q8Ls/uL6rVv+z5/+gtef+Q//AIigC7RVL+z5/wDoLXn/AJD/
APiKP7Pn/wCgtef+Q/8A4igC7RVL+z5/+gtef+Q//iKP7Pn/AOgtef8AkP8A+IoAu0VS/s+f/oLX
n/kP/wCIo/s+f/oLXn/kP/4igC7RVL+z5/8AoLXn/kP/AOIo/s+f/oLXn/kP/wCIoAu0VS/s+f8A
6C15/wCQ/wD4ij+z5/8AoLXn/kP/AOIoAu0VS/s+f/oLXn/kP/4ij+z5/wDoLXn/AJD/APiKALtF
Uv7Pn/6C15/5D/8AiKP7Pn/6C15/5D/+IoAu0VS/s+f/AKC15/5D/wDiKP7Pn/6C15/5D/8AiKAL
tFUv7Pn/AOgtef8AkP8A+Io/s+f/AKC15/5D/wDiKALtFUv7Pn/6C15/5D/+Io/s+f8A6C15/wCQ
/wD4igC7RVL+z5/+gtef+Q//AIij+z5/+gtef+Q//iKALtFUv7Pn/wCgtef+Q/8A4ij+z5/+gtef
+Q//AIigC7RVL+z5/wDoLXn/AJD/APiKP7Pn/wCgtef+Q/8A4igC7RVE2M4/5i17/wCQ/wD4isa1
8S+F77V5PD9l4/tLjVImZXsYr62e4Qr94GMDcCO/HFNJvYTkludPRVL7BP8A9Ba8/wDIf/xFH9nz
/wDQWvP/ACH/APEUhl2iqRsJx/zF7z/yH/8AEV5V8Xvjz4U+Fc0XhyC+1jxN411EY0vwro6RzX90
xGQWUIfKj7mR8ADpnpV06c6kuSmrszqVYU4803ZHomv+PPBPhS7t7DxR4x0PR7m85tob/UIreSYZ
A+RXYFuSBx3NZ3iL4vfCvwjG8nij4keGNK8sMWW71WCNht4b5S2eCeeK+avEP7G/jj9pK/sfH/7S
fjk6XqdqNmneH9BgheDTrYsHMMlwy5mkJHzMMAdvb3Dw7+y/8CPCkizaB8MfDtrMhVhMdLtpZQy9
DvkjZs8nnOT3rsnRwlOKvNyl1SWnyb3+45KdXFVJNqCjHpd6/cv8zMu/2xP2coJTBZfE2y1iYHHl
aPa3GoP064gjfjoM9MkDrXjnw0/4KOaH4y8c6j4a8R/C3W9H0yximk+3WcdxqMyhJFUGW2jgDxLt
JZmOdpGDya+s7DwzYaVEtvpTGyiUEKltBDEoBOTgKgHXmpk0VI3MkV7OjnqypECfqQlFOtg4xkpU
m29m5bfdH87jnRxcpRaqJJbpR3+9/lY8mt/2yv2b5GC3nxOs9MZmwqanZXVkzD+8BLGuV/2unB5r
Yb9qT9nQaVcayvxq8HyWloypK0WqRSMCxAGEUlj1HQGu+udAt71WS9uZbhWUowlihcFT1BynT2rz
v4i/sy/B/wCJ2gzaB4l8KWaxzBVFzZWdtbXUQVw+I5kiDKCRzg8gkd6iDwbklNSS66p/oiprFqL5
HFv0a/Vnc+DPHXhP4h+HrfxZ4J1211jSLsuIbu2JKOVYo3XB4ZSPwreU7ue1fOmjfsL/AAT8L2cE
PhC78Y6BeWxZk1HTPElxb3JYkkFip2NjJAypGOK1JPgx8ffDSH/hX/7T+rXaJzHZ+LdGtdRVsdFa
eMRygep5POfalOlhnJ+yqaf3lb8r/oEKuIUV7Wnd/wB1p/nY94or4g+I/wAUf2/vBvxQ0Lwlp3hr
R9esLkW3n3WiaPO9hNvmZW824kjY25IHzfeCKQ3Newrov7a2ukef41+GfhSJuCbSxudUmUddw8zy
1J/hII9we1aTwDhGMpVI2l5/pa/4EU8fGblGMJXXl+t7HvrMFUsxAAGSTXH+Jvi/8L/B2iXHiPxJ
8QfD9hp1rgSzyahGQCeigAkljg4ABJxXm83wP+PGv2rweLv2rNdCyoVeHQvD9jp6fMMMN5WRyMdO
QRzzXnv7Of8AwT48I/BzxBfeJPG2q6Z4yvf3R0p5NKEa2DKWLvskaRWc5TDYyu0460QoYRRlKrWu
1sop6/NpWCdfFOcY06Vk922tPkm7nVzfG/41fGpxZfs7fDs6NoUvH/CbeL4Ht7dlP8dpZf6yb1DN
hfUVoaH+xt8O9TmfX/jZqeq/FPxJcLtkv/EE7CCEdSttbIRHCnsMn3r3IaZIvTVbwdv+Wf8A8RS/
2fP/ANBa8/8AIf8A8RWf1ycNMOuReW/ze/3WXkWsHGTvXfO/Pb7tvvu/M8Y8LyP+zdqth8OdZud3
w51GT7N4Y1WcHOjTs426ddSdPLYsfIlYg8eWxJ2k+5Bgc89ODWLr3hDS/FOjXvh7xG0mpaZqMLW9
1aXKRPHNGwwVYbK8p8K6zrnwe1+1+GHxB1/UJfDt9P8AZ/CPiWeVXEgP3NPvJGUlblRxHIxxMoAz
vBBiX75cy+Lr5+fr3+/uXH9y+V/D08vL07fd2PcqKorYzMM/2te/j5f/AMRUGoeTpdpLf6j4hmtb
a3QySzzSQxxxqOpZioAHua50dNzTZsV4h+0B8V/Emn3ul/Bf4SSQzfEfxeGFtIfmTQ7IcS6hOMHA
TPyKfvN0zjB5Dxd8fPE3xcTU/h/+y7peo+KpZ4nsbzxfcyC00TTC4KsyT7A88ijJAizg4OTjFWv2
R/2cfiH8HIvFOsfFfxXba54l1+4gVNUt7yS7uGtoo8LHJLPGHwGJIA46egr0aeGjQi62Ia5ltHq/
N9kt7PV+h51TESrSVGgnyveS2Xkn1b7rY9e+D/wp8PfB7wRZeDfDyySeSWuL29m5n1C6c7pbiVur
OzEnnoMAcAV1mq/8eg/67w/+jFpP7Pn/AOgtef8AkP8A+IqtqNnNHAjnUrqQCeH5X2YP7xeuFBrg
nOU5Oc3ds74QjCKhFWSNaiiipKEJA5JqBdQsGRJFvbcpLIYkYSDDOCQVBzycg8exqZgSpA61xdv8
Op4bGysP7dXy7DWG1iLFjGMM0skhQc8DMhGRzge5oA6iyOb/AFD/AK6p/wCi1q9WPa6cj3+of6Vd
j96vSdh/AtW/7Lj/AOfy9/8AAhv8aALtFUv7Lj/5/L3/AMCG/wAaP7Lj/wCfy9/8CG/xoAu0VS/s
uP8A5/L3/wACG/xo/suP/n8vf/Ahv8aALtFUv7Lj/wCfy9/8CG/xo/suP/n8vf8AwIb/ABoAu0VS
/suP/n8vf/Ahv8aP7Lj/AOfy9/8AAhv8aALtFUv7Lj/5/L3/AMCG/wAaP7Lj/wCfy9/8CG/xoAu0
VS/suP8A5/L3/wACG/xo/suP/n8vf/Ahv8aALtFUv7Lj/wCfy9/8CG/xo/suP/n8vf8AwIb/ABoA
u0VS/suP/n8vf/Ahv8aP7Lj/AOfy9/8AAhv8aALtFUv7Lj/5/L3/AMCG/wAaP7Lj/wCfy9/8CG/x
oAu0VS/suP8A5/L3/wACG/xpDpsY5+13x+lw3+NAF6kyPWvMviH8a/gx8LN0Xjn4mW2n3g+7YC+a
a8c9gtvHukJP+7XlOufF745fFnRdR0n4DfBnxLp1rfW0tvb+J/FmpHSEj3KVEtvb8zMwPKkhecZF
dNPCVppStaPd6L73+hzVMXSg3G95dlq/w2+Z9R7hnGRRnPIr5B+EHhX9uv4XaJfx+MotC+IXn3Ql
RL7xfcR30aBACsUjRGPadpwrY+Zs5xXcp+0TrOgkR/Er4C/Fjw6M4a6srYaxaj1PmWrs2OCfudMc
ZOK0qYGam40pKa7pr8t/wM6eOg4p1IuL80/z2/E+hqQkdz1rwG8/bG/Zc0+BJb/4wPayNkG3mgvU
uIyOu+Ix7l+pAB5xnFcxar8Yf2qnJsbnX/hr8J5cgTvM0WveI4jx8qt/x627DPPLMCOoPCjgqq96
suSPdpr7u79ByxtJ+7SfPLsmn9/Y6rx/+0bqOq+Ibn4V/s7+H4PG/jSL93fXnnY0bQc5G67uBkFx
g4iTLHGODxXmfh//AIJ9ajp3jab4s3fx/wDEtn441CSa8vNR0awgtV+1TZMhVTn90ST8hHI9K+mv
Avwr8E/DPw7b+E/Amkf2NpVtykFtKw3N3d2J3O57sxJPrXQ/2XH/AM/l7/4EN/jVxx0qCcMLono2
0m363vZeS+9mcsCqzU8Tq1sldJem2vn+R4Gyftn/AA22Oj+Dvi7pcIw0bIdD1YgZ5DZaBmxj0yfz
ptx+2r4I8JWkz/GL4feO/h7eQx7xDqujPNDcHj5YbiHdG59ASv8ASvfv7Lj/AOfy9/8AAhv8ayPF
fgDw1448PX3hTxbazanpGpxGG7tJrmQJKnBwSCCOg6EVCr0Zte3pr1j7r+7b8F6lyw9WK/cz+UtV
9+/4v0PAof2gPH/7TH/Eg/Zg0y60TQifK1Xx5rdiVis+Pmis7djma4wRyflXPPUGvVvg/wDAbwT8
H4bu80pLvVfEWqt5ur+ItWk+0alqMmBkySnkL6IuFHp3rZ+H/wAIvAXwr0E+F/h7o8miaUZ3ufss
F1Ky+Y2NzfMxOTgd+1dL/Zcf/P5e/wDgQ3+NLEYiLvSw65Yfi/V/psOhh5aVMQ+af4L0X9MuUtUv
7Lj/AOfy9/8AAhv8aP7Lj/5/L3/wIb/GuQ7C7RVL+y4/+fy9/wDAhv8AGj+y4/8An8vf/Ahv8aAL
tFUv7Lj/AOfy9/8AAhv8aP7Lj/5/L3/wIb/GgC5gelFU/wCy4/8An8vf/Ahv8aP7Lj/5/L3/AMCG
/wAaALlLVL+y4/8An8vf/Ahv8aP7Lj/5/L3/AMCG/wAaALtFUv7Lj/5/L3/wIb/Gj+y4/wDn8vf/
AAIb/GgC7RVL+y4/+fy9/wDAhv8AGj+y4/8An8vf/Ahv8aALtYnjLwjoPjrw1qHhTxNYC80zUoTD
PFuKtjOQysOVdSAysCCpAI5FXv7Lj/5/L3/wIb/Gj+y0/wCfy9/8CG/xpptO6E0mrM+Q9Z/a68a/
Bj4mn9mu/wDBV18SPFkTRQ6NqUN/FZy38csYeAXKsuPOUZDupCtt3YBJFdzY/s6+OvjBeReIf2qP
FqarapIJ7bwPobvDolsQPl89v9ZdOMnljtz6ivdZfB3h+bUE1eawjkv0IK3bqDMuBgYkI3Dj3q9/
Zaf8/l7/AOBDV3SxsUk6EFGVtX1b8v5fl99tDhjg5NtVpOUei6W8+/zuLpGkaXoOmW2jaNp1tY2N
nGIbe2t4ljiiQcBVUcAewq5VL+y4/wDn8vf/AAIb/Gj+y4/+fy9/8CG/xrg16nckloi7VPVf+PQf
9d4f/Ri0n9lx/wDP5e/+BDf41W1DT0igSQXV022eE4adiD+8XqKBmtRRRQBFNc29sgkuZ44lZggL
sFBYnAHPcngCq82t6Nb3H2SfVrKOfesXlPcIr72GVXBOckAkDvVLxV4ePiXTk077X9m8u5gulk8l
ZCGikWQABuBkqOeuM1zN98IrDUNeHiGfWLpbtblbpXSNFZGypfa2MjdtA74GQODQB2dl/wAf2of9
dU/9FrV2se00y1a/1Akzj96vS4kH8C+jVc/sq0/vXP8A4FS//FUAXKKp/wBlWn965/8AAqX/AOKo
/sq0/vXP/gVL/wDFUAXKKp/2Vaf3rn/wKl/+Ko/sq0/vXP8A4FS//FUAXKKp/wBlWn965/8AAqX/
AOKo/sq0/vXP/gVL/wDFUAXKKp/2Vaf3rn/wKl/+Ko/sq0/vXP8A4FS//FUAXKKp/wBlWn965/8A
AqX/AOKo/sq0/vXP/gVL/wDFUAXKKp/2Vaf3rn/wKl/+Ko/sq0/vXP8A4FS//FUAXKKp/wBlWn96
5/8AAqX/AOKo/sq0/vXP/gVL/wDFUAXKKp/2Vaf3rn/wKl/+KpG0u0Azuuf/AAKl/wDiqALtNLAN
t718xftK/tj/AA4+ARs9M0hIfGGvSzlLzSrTXXjksotpPmSMocA5AXYcHnPaq+geAPjZ+0xpOn+K
PiX4tPgbwBrFtHeW3hjwzqEr31/byIGQXl6SCoKsCUjA64ODXbHAVFSVet7kHs3u/Rbv8vM4ZY6m
6jo0femt0unq9v18jvviH+1L4O8La5/wg3gTSL/4i+NXzt0Lw4VnaDGBuup/9Xbpk8ljkeleFx/s
6ftefEz4sjxh8TPiLP4X8G63cebqfh7w/wCLbtXs4PK2iGLCbM5C7iDg5cjqK+qvAPwe+G/wx0Vd
B8A+FbbQrPO50s3kRpW/vSPu3O3uxJrp/wCybP1uf/AqX/4qrp42OHusNHdWvLV/LovxfmTPByr2
eIltrZaL/N/h6HC/Db9nr4O/CYmbwR4G060vH+aXUZ0NzfSt6tcSlpD+ePavRNo61V/sq0/vXP8A
4FS//FUf2Vaf3rn/AMCpf/iq4ak5VJc1R3fmdsKcILlgrLyLeKTaB0qr/ZVp/euf/AqX/wCKo/sq
0/vXP/gVL/8AFVNizz34y/s4/Cf49rpo+JWhT3x0kyG2a3vJbZh5gUNuMZBYYUYz07da9Hs7OCxt
YbS3XEcEaxICckKoAHP0FRf2Vaf3rn/wKl/+Ko/sq0/vXP8A4FS//FVpKrOUFTk20tl2vvYzjShG
bnFWb3fcuUVT/sq0/vXP/gVL/wDFUf2Vaf3rn/wKl/8AiqzNC5RVP+yrT+9c/wDgVL/8VR/ZVp/e
uf8AwKl/+KoAuUVT/sq0/vXP/gVL/wDFUf2Vaf3rn/wKl/8AiqALlFU/7KtP71z/AOBUv/xVH9lW
n965/wDAqX/4qgC5RVP+yrT+9c/+BUv/AMVR/ZVp/euf/AqX/wCKoAuUVT/sq0/vXP8A4FS//FUf
2Vaf3rn/AMCpf/iqALlFU/7KtP71z/4FS/8AxVH9lWn965/8Cpf/AIqgC5RVP+yrT+9c/wDgVL/8
VR/ZVp/euf8AwKl/+KoAuUVT/sq0/vXP/gVL/wDFUf2Vaf3rn/wKl/8AiqALlFU/7KtP71z/AOBU
v/xVH9lWn965/wDAqX/4qgC5RVP+yrT+9c/+BUv/AMVR/ZVp/euf/AqX/wCKoAuUVT/sq0/vXP8A
4FS//FUf2Vaf3rn/AMCpf/iqALlFU/7KtP71z/4FS/8AxVH9lWn965/8Cpf/AIqgC5VPVf8Aj0H/
AF3h/wDRi0f2Vaf3rn/wKl/+KqtqOnW0UCSI0+5Z4SN1xIw/1i9i2DQBq0UUUAFV7u/s7IwLdXUM
LXMohhEkgUyOQSFXPU4B4HpVisrX9Bi14WAlvLm3+wXsd8nk7PnZM4Vtyt8vPOMH3oAyPD/j3wTr
fifVvDui+L9Fv9VtZMz2NtfxS3EWxVR90asWG1vlORweDXVg5r5Kl/Yw1rwf8RfEvxe+B/xQvdJ8
YaheXFxJb6vbRz6dcpcMJnt32BZFQuRhgSRtHfmuq8NftJWXh/WrbwR+0X4L1H4Z69cN5Vtf3N88
2h6g/wD0wvQ21SeoSTBHTJNd1XCQl72Elzq2q2afXTqvNX87HBSxc4+7io8rvo+nlr0frY+jKKzb
a20m8gjurS5eeGVQ8ckd3IyOp6EMGwR7ipf7LsvW4/8AAmT/AOKrhO65doql/Zdl63H/AIEyf/FU
f2XZetx/4Eyf/FUXGXaKpf2XZetx/wCBMn/xVH9mWWcZuM/9fMn/AMVQBdormtG17wJ4jurix8Pe
K9P1S5tRmeGy1fz3i5x86o5K8gjnuK2P7LsvW4/8CZP/AIqm007MSknqi7RVP+y7L1n/APAmT/4q
j+yrP1uP/AmT/wCKpDLlFU/7Ks/W4/8AAmT/AOKpP7Lss4zcf+BMn/xVAF2ori4itoZLidwkcSl3
YnhVAySa5D4g+NPh38LvDdx4s8d+JY9H023GPNuLyQNI3ZI0DbpHPZVBJrw6JPjb+06QNIh1j4T/
AAznJD3c8rjxDrcPpHGxItImHc5cj6kV0UcNKoueT5YLq/yXd+S+ZzVsQoPkiry7L9ey9TrvEf7Y
/wAHrbydM+Hl/d/EjxDeA/ZNH8JxG9lfnAMkg+SJM9WY8ehrEHw2/aL+O3734xeMG+G/hSfp4V8K
3O+/njP8N3qHbI4KxDHuK6/4FfssfDT9nuPWI/As+uy/22YTcm/vg5Xy920KY1TA+c5zntXq/wDZ
Vn63H/gTJ/8AFVvUr0KUmsIv+3pb/JbL8X5mNOhWqxTxTt/dW3ze7/I5b4e/Bn4YfC3RR4e8DeCt
L0uzJDSbYA8szf3pZGy8je7E12aRpGgjjRVVRgKBgAVV/sqz9bj/AMCZP/iqP7Ks/W4/8CZP/iq4
pTlN803dnbCEYLlirIuUVT/sqz9bj/wJk/8AiqP7Ks/W4/8AAmT/AOKqSi5RVP8Asqz9bj/wJk/+
Ko/sqz9bj/wJk/8AiqALlFU/7Ks/W4/8CZP/AIqj+yrP1uP/AAJk/wDiqALlFU/7Ks/W4/8AAmT/
AOKo/sqz9bj/AMCZP/iqALlFU/7Ks/W4/wDAmT/4qj+yrP1uP/AmT/4qgC5RVP8Asqz9bj/wJk/+
Ko/sqz9bj/wJk/8AiqALlFU/7Ks/W4/8CZP/AIqj+yrP1uP/AAJk/wDiqALlFU/7Ks/W4/8AAmT/
AOKo/sqz9bj/AMCZP/iqALlFU/7Ks/W4/wDAmT/4qj+yrP1uP/AmT/4qgC5RVP8Asqz9bj/wJk/+
Ko/sqz9bj/wJk/8AiqALlFU/7Ks/W4/8CZP/AIqj+yrP1uP/AAJk/wDiqALlFU/7Ks/W4/8AAmT/
AOKo/sqz9bj/AMCZP/iqALlFU/7Ks/W4/wDAmT/4qj+yrP1uP/AmT/4qgC5RVP8Asqz9bj/wJk/+
Ko/sqz9bj/wJk/8AiqALlFU/7Ks/W4/8CZP/AIqj+yrP1uP/AAJk/wDiqALlFU/7Ks/W4/8AAmT/
AOKo/sqz9bj/AMCZP/iqALlFU/7Ks/W4/wDAmT/4qj+yrP1uP/AmT/4qgC5VPVf+PQf9d4f/AEYt
H9lWfrcf+BMn/wAVVbUdOtooEkQzblnhIzO7D/WL2JxQBq0UUUAUNY13SdAt1u9Yv4rSFnEYeRsA
scnH5An2AJPArPuPHfhK11VNEn122W/eZbdbfcS5kYZCgAcnH5d8VY8SeGNM8VWaWOq+d5cblx5U
hRuUZGGR2KO6kejGsW7+FPhK91eTXLmK6a8leJ3cTY3eXggcDgEgE45OBzQB0ll/x/agf+mqf+i1
qv4k8L+H/F+kXOgeJ9FsdW027G2e0vYFmikHurAimWmlae9/qBe1UnzVPf8AuLVv+x9M/wCfNP1p
ptO6E0mrM+WPiT8K/iR+y74Z1Px7+zDr+qXOkwzRvN8Pryyl1SzcyOqM1ntPnQ43byoJGFPQcVp/
DL4t/tn+N/BOn63d/AbwjaXN6ZE87UtZudNaIiRkDSWbRPIoGM435YcjGa+lP7H0wHItEH4mg6Np
pOTaIT9TXc8dzU+WrTjKV/id7/OzV/V6nCsC41OanNxj2VrfK97eiPFxc/tr3eIP7J+DmnB/+Xn7
XqVz5ff/AFexN2en3hjOfavKvix4e/4KM3fi/Q28J+J/DK6aEQXknh9I4LZD5vJmju2aRyF5+QgE
cdea+vf7G0z/AJ80/Wj+xtM/580/WlSxzpy5lTg/VX/MdTBe0jyupL5Ox4yfhB+0dq6f8T79qu6s
1l+aSHRPCVlbbCOgjklMjBfXdknnkUw/sv6vqa/8VX+0n8XNV8zmeKDWorCKQjphYIlKYwPukZI5
6mvaf7H0z/nzT9aP7H0z/nzT9az+uVV8Nl6RivyRp9Tpdbv1bf5s+XPh/wDsBad8LNX1PxB8P/jx
480PUdSXa89qLX5hvLYlV4mEo5PXvz1ru28N/tg+Ffl0b4k+AfG8C/dTXdFm0y5b6y2zsmeSc7B9
0epNe0f2Ppn/AD5p+tH9jaZ/z5p+tXUzCvVlzVmpPzS/O1/xIhgKNOPLRvH0b/4Y+Zvid+1p8Wvg
d4YHiL4rfs23FtB9pS1F7pvie3uLJ3bOBu2eYpOOAU5weRgZ1vBP7Yt/4x8K6b4ps/2bPixcQalA
Jo5NO0yG7tmBJGY5jKm9eOu0fSvfLnwzoF6nl3ukWtzHnOyaMOufXBzT4PD2i2sYhttNghiUYWON
dqr9AOBT+sYZ00nR96+93a3pdiWHxKm2qvu+iv8AfZHjn/DT+sH/AJti+NP/AIIIP/j9eUeO/wBu
H4lWvxH0z4X+C/2ftX0/VNfWC30+TxaXsmjnmdo0aSOIODCCAc7wThhxjNfX39jaZ/z6J+ZpP7E0
stuNlGT70UsThoyvKjf5vfuKrhsRNWVW3yR4x8Pf2YrW28Sw/FH42eIT8QvHykPFd3ce3T9K/wCm
dja/dQA9HILHrwa9zCgc45qp/Y+mf8+afrR/Y+mf8+afrXNVrTqu83/wPRdDqpUYUlaCLtFUv7H0
z/nzT9aP7H0z/nzT9ayNS7RVL+x9M/580/Wj+x9M/wCfNP1oAu0VS/sfTP8AnzT9aP7H0z/nzT9a
ALtFUv7H0z/nzT9aP7H0z/nzT9aALtFUv7H0z/nzT9aP7H0z/nzT9aALtFUv7H0z/nzT9aP7H0z/
AJ80/WgC7RVL+x9M/wCfNP1o/sfTP+fNP1oAu0VS/sfTP+fNP1o/sfTP+fNP1oAu0VS/sfTP+fNP
1o/sfTP+fNP1oAu0VS/sfTP+fNP1o/sfTP8AnzT9aALtFUv7H0z/AJ80/Wj+x9M/580/WgC7RVL+
x9M/580/Wj+x9M/580/WgC7RVL+x9M/580/Wj+x9M/580/WgC7RVL+x9M/580/Wj+x9M/wCfNP1o
Au0VS/sfTP8AnzT9aP7H0z/nzT9aALtFUv7H0z/nzT9aP7H0z/nzT9aALtFUv7H0z/nzT9aP7H0z
/nzT9aALtFUv7H0z/nzT9aP7H0z/AJ80/WgC7RVL+x9M/wCfNP1o/sfTP+fNP1oAu1T1X/j0H/Xe
H/0YtJ/Y+mf8+afrVbUNLsIYElitlV1nhIIzx+8WgDWooooAQnAJPasNPHHhOSCG6TXbUxXNz9ki
fdw0vHy/qDnphgc8itt1DqUYZBGCK5E/Czwk1tBZTw3U8FveR3yJLcFx5iAKnXnAVUXHoij6gHQ2
Tr9u1D5h/rU7/wDTNau70/vD864bwl4r8J+K9YurPT9Hl811a4aS4gjCkIUXjBLDIdHGQMhs12H9
k6X/ANA21/78r/hQBZ3p/eH50b0/vD865nxhq3hnwfpaajqmlI8c0wt1ENujNkhiTzgABVZiSeAp
qTwtPoeuWEj22ieStpO1oTcQxkyFAPmDKSGBz1B6gg4IIoA6Len94fnRvT+8Pzqt/ZOlDk6ba/8A
flf8K4bxH468FaDq95YXWizSS6PGs9wYbeIIQyrnG5gW2rKjEDpuFAHoW9P7w/Ojen94fnVVNL0t
lDf2ZajP/TJf8KZcWGj2tvLcy6dahIkLsfJXgAZPagC7vT+8Pzo3p/eH51wPgnxx4G8a6pNpmjaa
RcLbfbZUnt41MQJChSASQ2Cj47B1z1xXa/2Tpf8A0DbX/vyv+FAFnen94fnRvT+8PzrkfG+teFfC
dnANV0sFdQkNsht7dCyfKSWJOAAAOv0q74UvtB8VaNFq9poqW6uWR4LiBFmiZTgq6jO1h6UAdDvT
+8Pzo3p/eH51W/snSv8AoG2v/flf8K4PUfiD4CsPFh8Oy6ZIbyG4FkcW0YiJcIWfJI+VMoC3q+Bm
gD0Xen94fnRvT+8Pzqt/ZOl/9A21/wC/K/4VT1hdB0TSrzWb7TrcW1jA9zMVgUkIiljgY5OAaANX
en94fnRvT+8PzrjfBWuaB4q+0rZeG5YEhxI0lzHAQGdnzHhGYhlKkFWAxxXU/wBk6V/0DbX/AL8r
/hQBZ3r/AHh+dG9P7w/OuK8d+JvBvg9LaDWdOI+2JJKHgt0OxY9uSxOAMs6KB1JYCtnw3caB4n0W
212x0qFILoEqskCBlwSpBxkdQe9AG5vT+8Pzo3r/AHh+dVv7J0v/AKBtr/35X/CuBT4j+AZPFSeH
/wCypVuWvG00M1tGIy4k8vIBO4gyBlBA/hY9ASDyA9H3p/eH50b0/vD86rf2Tpf/AEDbX/vyv+FV
NVt9L0zT7jUDo1vKlvE0rKqRqSAMnlsKOPUgUAam9P7w/Ojen94fnXGeBNf8NeLrRxZeH5rVoFWR
kvYIhIVZpFB+UsPvRSLg4Py9MEGuq/snS/8AoG2v/flf8KALO9P7w/Ojen94fnXI+MNU0Xw4IUn8
MzXSPFLdl7SKAlFgXzGyGZTghQOBjLAEjNb9pYaTdW0VymmWwWVA65hXOCM+nvQBf3p/eH50b0/v
D86qnStKAz/Ztr/35X/CuT0/xBoV54iOlnwtcQyyzyWYd47d4cwqWZhtctj5tpOOGAU4OKAO23p/
eH50b0/vD86rf2TpR5/s21/78r/hWb4jOj6Bol5rEuiRTx2kZkeOKOIOVHXG8qM+2ee3NAG3vT+8
Pzo3p/eH51y/g7UNB8R2U6W+gtayabKLOeK7hi81XCI3JQsp4cd+ua3/AOydL/6Btr/35X/CgCzv
X+8Pzo3p/eH51w/jbxP4X8ISj+2NCfyILaTUPOt4oSCEwuwqWDZYuoHGCT1GDjrINP0e4hSeLT7R
kkUOp8peQRkUAXN6f3h+dG9P7w/Oqj6VpirldLtWPp5S/wCFcf4d8VeG9Y1+TRf+EXubOafe0b3U
MHkyGNmRliZGYMRsYkDtzQB3e9P7w/Ojen94fnVb+ydL/wCgba/9+V/wrG8Xz6L4c0C61SfQRcxR
rtdLaOISgN8uV3lQTkgAZySRigDot6f3h+dG9P7w/Oub8Hal4b8X6FDrWm6UkcMhKBJ4EWRcf3gM
4JBB+hFbf9k6V/0DbX/vyv8AhQBZ3p/eH50b0/vD864nxFr2j6NqotJPCVxctaxxz77dbbY3mv5K
KQzhtxYnAxztOM4rrF0rSyMnTLX/AL8r/hQBa3p/eH50b0/vD86pzaZpkcTuuk2zlVJCiJAW9ueP
zrjvBvi/wn4o1ebRrXQJre6MH24rcwQldh2AbSjMCCHRh2IagDvd6f3h+dG9P7w/Oq39k6X/ANA2
1/78r/hXO+Ob/Q/C+hvf3Ph2S7id1hK2UMRmG7uqsV3H2GTwTjigDq96f3h+dG9P7w/Ouf8ADF74
b8WaLBrumaZB9nnLgBooyQyOyMMrkH5lPIJB7Gtf+ydK/wCgba/9+V/woC5Z3p/eH50b0/vD8685
1D4g+BbHxXP4fk0edrqxYQzFLaLygrFMvywJCkoOBn5uAea73+ydL/6Btr/35X/CgCzvT+8Pzo3p
/eH51ja9J4f8O6Pea3faVA1vZRGaQJAhYgemcc1l+DtU8N+JorltP0cosXlzE3EEY3CZfMG3BPAy
V5x0/GgDrd6f3h+dVNUZTaABh/r4e/8A00WnHSdKx/yDbX/vyv8AhXKeNfEvhfwfNp1tf6Uxmv5c
wG1iiUqUZPvM5UKMsoznoT6UAdtRVLRtSj1jSrTVYoJoEu4VmWOddsiBgCAw7HmrtABRRRQBl2nh
fw3p9+dVsdB0+3vSGBuIrdFkIY5YbgM8kZPrWpRRQBWv9N0/VYPsup2MF3DuDeXNGHXIOQcHuDTN
M0bSdFgNro+m2tlCXMhjt4ljXcepwOMmrlFACVmX3hnw7qdw13qOgaddTOFVpJrZHYhTlQSRng1q
UUAIBgYoYBgVYZB4NLRQBR0/Q9F0og6XpNnaFVKAwQKmFJ3EcDoTz9avUUUAVb/S9N1VEj1PT7e7
SJxKizxBwrjowB6EetGn6Zp2k2y2Wl2MFpbpnbFBGERcnJwBx1NWqKACs2fw54furw6hc6JYS3TS
JKZnt0Ll0+427Gcjse1aVFFgCmSxRzxtDNGro4KsrDIYHqCO4p9FAFPTtJ0zSIjBpWm2tnEcZSCJ
Y1OBgcAegAq5RRQBS1HRtI1fyxqul2l4ISTH58KybCRg4yOMjiprOys9OtksrC1itreIYSKJAqKP
YDgVPRSsAVmJ4b0BL/8AtRdDsBeeYZvtAt083eRgtuxnOOM1p0UwCo54IbqGS2uYklilUpIjqCrK
Rggg9QRUlFAFW00rTdPkmlsNPt7d7mTzZmijCGR8Y3Njqfc1KLiFn8tZFLAkYBGcjr/MfnUtfK/j
aeeH4n6ykUzov9pXbYViBkwWGT/46v5D0pDPpq/07SdUDW2p6fb3SyxNCyTRBw0bY3KQeqnAyOhw
Ks21vb2dvHa2kCQwwoEjjRdqooGAAOwr4/m1HUG1y/ma/uDI8UJZzK248SNyc/3vm+vNbF5q2qj4
dT3Q1O785ddYiTzm3Am3tCTnOeSzH6sfU0kxH1WzKB8xwDxk+9UB4e0Nb6LU10eyF5AHEVwIFEiB
yWfDYyNxJJ9SSa+UNW1C/uNav45764kU6hEpV5WIx5qccnpXon7O+oX9/rRN9fXFwf7BglzLKz/O
4jZ25PVjyT3PWmB73UdxbW93C1vdQRzRNglHUMpwcjg+4BqWimBVsNL0zSkkj0zT7e0SaQyyLDGE
DuerEDqT61aoooArXGmadds7XdjbzGWMwuZIw25DyVOeq+3Sp0RI1CRqFVRgADAAp1FABVGHQtFt
rpL630iziuIo/JSVIFV1TOdoIGQMknHvV6igAqK4tba7QR3UEcyqyuFdQwDKQQcHuCAR6EVLRQBW
sNN0/SrcWemWMFpAGLCKCMIgJOScDjk1YIzS0UAVpNN0+aUzy2UDyEoS7RgklCWTn/ZJJHoScVYA
xxS0UAIyq6lWAIIwQe9U7TRNGsLk3llpVpbzmJYDLFCqt5agALkDO0AAAdOB6VdooAKgurGzvgq3
lrFOqHcokQMAcEZGe+CR9CanooAgs7K0062js7C2it7eFdkcUShUQegA4FTEZ4NLRQBmy+GvDs14
dRm0LT5LoyrMZ2tkMhdeFbdjORng9q0qKKAIbq0tb63ktLy3jngmXbJHIoZXHoQeoqrpugaHo801
xpOj2VlJcBVleCBY2kCjChiBzgcD0rQooAKztX8PaD4gjWHXdFsdRjTO1bq3WUDOM4DA+g/IVo0U
ARW1rbWUCWtpAkMMShUjRQqqB0AA6CpaKKAP/9k=

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



I'm not saying this is the whole problem -- and it would be interesting =
to graph US meetings separately -- but the weakness of the dollar has to =
be a factor. -- Nathaniel


--Apple-Mail-135-966062994--

From tjc@ecs.soton.ac.uk  Thu Aug 25 07:05:14 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE83921F8804 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.842
X-Spam-Level: 
X-Spam-Status: No, score=-2.842 tagged_above=-999 required=5 tests=[AWL=-0.243, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qA8oe8Zi+R9p for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:05:14 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id B409321F86D0 for <ietf@ietf.org>; Thu, 25 Aug 2011 07:05:13 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7PE6K1N008288 for <ietf@ietf.org>; Thu, 25 Aug 2011 15:06:20 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p7PE6K1N008288
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1314281180; bh=AR6bmB/yv6/FJZetHRh6O/moZ7U=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=PrwZE3axlCKfaRapvZtJaoqnz2ziOLWiKFJvQKr2qNk6YKJ8U5Gz17d8YMxFFoc0g R5sgTDl2qoc4PoqFCAp2uEj823aaezW5PhQrszQk7nLlYWe3RHfVBtzIUVSyWxuU0A sb+tokUaX8BXIMbP4++Fr0mErWsSDIwpMA+ZY9UE=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n7OF6K0366119003fs ret-id none; Thu, 25 Aug 2011 15:06:20 +0100
Received: from [IPv6:2001:630:d0:f105:31d1:7522:5788:e144] ([IPv6:2001:630:d0:f105:31d1:7522:5788:e144]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p7PE6BUo017745 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 25 Aug 2011 15:06:11 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: voting system for future venues?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <EEA7A37D-2ACE-41E4-B308-67E12C1A07DF@guppylake.com>
Date: Thu, 25 Aug 2011 15:06:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|8a2d17a7a5c1705b60848bd3251849d9n7OF6K03tjc|ecs.soton.ac.uk|8FF73A4B-DAA9-4813-8427-66E93B28D904@ecs.soton.ac.uk>
References: <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie> <alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com> <20110825032605.GI53261@shinkuro.com> <alpine.OSX.2.01.1108242104570.18070@sjc-vpn5-137.cisco.com> <EEA7A37D-2ACE-41E4-B308-67E12C1A07DF@guppylake.com> <8FF73A4B-DAA9-4813-8427-66E93B28D904@ecs.soton.ac.uk>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n7OF6K036611900300; tid=n7OF6K0366119003fs; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p7PE6K1N008288
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 14:05:14 -0000

On 25 Aug 2011, at 14:58, Nathaniel Borenstein wrote:
>=20
> I'm not saying this is the whole problem -- and it would be =
interesting to graph US meetings separately -- but the weakness of the =
dollar has to be a factor. -- Nathaniel

The graphs are really interesting, but the fact remains you can book a =
room for a week at Minneapolis or Prague in IETF82 week for nearly $100 =
a day less than the cost of the Hyatt in Taipei, and that's just the =
public hotel rate, nothing negotiated.

Tim


From lberger@labn.net  Thu Aug 25 07:06:55 2011
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDD5921F8742 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.897
X-Spam-Level: 
X-Spam-Status: No, score=-100.897 tagged_above=-999 required=5 tests=[AWL=-0.736, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id smm5yaSOHZ-W for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:06:55 -0700 (PDT)
Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by ietfa.amsl.com (Postfix) with SMTP id 1DBA621F86D0 for <ietf@ietf.org>; Thu, 25 Aug 2011 07:06:54 -0700 (PDT)
Received: (qmail 24145 invoked by uid 0); 25 Aug 2011 14:08:08 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy1.bluehost.com with SMTP; 25 Aug 2011 14:08:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=1fqPUr40g07LKX7k1V61Dl3XUTHVLQw7cxQnAfPZfng=;  b=Knw639lXvmnNWscjxbyqbiSWoD1sfRGQ5EkRKEYpV6l49DiooComGJSRQhiZ/unnhy8cmEe3mUfnudxMj42+b2aBz4ttXQ69QdXIpiFcq759UAZnanDgAm5CSi/0QV0K;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1QwabI-0002qt-5b; Thu, 25 Aug 2011 08:08:08 -0600
Message-ID: <4E565744.9010309@labn.net>
Date: Thu, 25 Aug 2011 10:08:04 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com>	<CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com>	<CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 14:06:55 -0000

Ole,
	In the (somewhat far) past, my memory was that the IETF rate was *less*
then the normal available rate.  This trend to higher rates is something
I only remember seeing over the last 5 or so years.  Perhaps my memory
is just flawed, as I haven't done the work to verify this, but I don't
think so.

I think in the spirit of transparency we really need to understand why
this trend has occurred.

>From looking at the list of things we get for the IETF rate, the only
thing I see in the list that is really important to the individuals
paying the room-fees is in-room (typically) IETF-class internet.
Breakfast is great, but it is included only when this is the norm for
the region/hotel, so really isn't a real benefit compared to rack rates.

I strongly feel that the "free or subsidized meeting rooms" should come
out of the meeting fees, not *hidden* in the hotel rates.

You also don't mention the free hotel rooms/suites.  Again the value
here and subsidy in the IETF rates really should be known, but in either
case, these too should come out of the meeting fees.

I personally think the issues to focus on/fix are the lack of
transparency and the current approach of distributing meeting costs to
the hotel rate.

Lou

On 8/23/2011 2:07 PM, Ole Jacobsen wrote:
> 
> You said:
> 
> "At root is that we are trying to negotiate a purchase at a discounted
>  price without committing to buying any particular number of rooms,
>  versus only a limited number of possible sellers."
> 
> When negotiating a group rate we actually ARE committing to buying a 
> certain number of rooms (the "room block"). There are certainly pros
> and cons with group rates. On the pro side: guaranteed rate (but not 
> necessarily the absolute lowest available at any time), included 
> benefits (breakfast, Internet, if applicable), free or subsidized
> meeting rooms where applicable. On the cons side is of course the
> cancellation policy (not that it has to be as onerous as this one).
> 
> Ole
> 
> 
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 
> 
> 

From dworley@avaya.com  Thu Aug 25 07:11:17 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4897821F850B for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level: 
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=-0.353, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhjDiR-YKyZF for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:11:16 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id B85E121F85F2 for <ietf@ietf.org>; Thu, 25 Aug 2011 07:11:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAC5XVk7GmAcF/2dsb2JhbABCqAF3gTkHAQEBAQIBEihECwIBCA0IIRAyJQEBBAESCBqHUJ5qApwqhWxgBJhEi2w
X-IronPort-AV: E=Sophos;i="4.68,281,1312171200"; d="scan'208";a="204047977"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 25 Aug 2011 10:12:29 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Aug 2011 10:08:26 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Thu, 25 Aug 2011 10:12:29 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Warren Kumari <warren@kumari.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 25 Aug 2011 10:10:20 -0400
Subject: RE: [IETF] Re: Hyatt Taipei cancellation policy?
Thread-Topic: [IETF] Re: Hyatt Taipei cancellation policy?
Thread-Index: Acxir2ughUMUgjMhTxaYqaaw+hevRgAgU0TR
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5854@DC-US1MBEX4.global.avaya.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net> <1314217708.1973.199.camel@d430> <201108242128.p7OLSq4i011660@cichlid.raleigh.ibm.com>, <73B65805-9EFA-4D45-A6F3-A71FEE5E4880@kumari.net>
In-Reply-To: <73B65805-9EFA-4D45-A6F3-A71FEE5E4880@kumari.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 14:11:17 -0000

> From: Warren Kumari [warren@kumari.net]
>=20
> And I've concluded that the IAOC have a crappy job to do and that folk li=
ke to kvetch.

+1

The IAOC does a remarkably good job given the difficulty of the optimizatio=
n problem.
Just over the last two years, I'm amazed by the number of vastly different =
places we've
had meetings, and I (as a non-speaking foreigner in many of them) have had =
no serious
difficulties with any of them.

Dale

From mcr@sandelman.ca  Thu Aug 25 07:18:29 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6214C21F8620 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.495
X-Spam-Level: 
X-Spam-Status: No, score=-1.495 tagged_above=-999 required=5 tests=[AWL=0.459,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdkGQg6K3geR for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:18:28 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id D915121F861A for <ietf@ietf.org>; Thu, 25 Aug 2011 07:18:28 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 73661342C0 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:19:04 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 6A5AB98411 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:20:06 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: voting system for future venues?
In-Reply-To: <alpine.OSX.2.01.1108242012340.16097@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com> <tslmxey8sia.fsf@mit.edu><1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net><15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com><4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie><alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com><4E557A33.7050607@cs.tcd.ie><62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com><4E559A18.3090005@cs.tcd.ie><6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com><4E55A126.90102@cs.tcd.ie> <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com> <A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com> <alpine.OSX.2.01.11 08242012340.16097@sjc-vpn5-137.cisco.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 25 Aug 2011 10:20:06 -0400
Message-ID: <10493.1314282006@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 14:18:29 -0000

>>>>> "Ole" == Ole Jacobsen <ole@cisco.com> writes:
    Ole> The Sofitel Manila is where APRICOT 2009 was held. A great
    Ole> venue, possibly even large enough to hold an IETF (I am not
    Ole> sure), *and* the rate (at the time) at 7,525 Pesos was pretty
    Ole> good. Today it is $177 which is still pretty good. The question
    Ole> is: would the IETF go to the Philippines for a meeting. It's
    Ole> worth finding out.

I can't find a flight that gets me there in less than 2 days from
Canada.  I tried for November.  Most transit US (a -0.5 for me), many
connect in Tokyo or Hong Kong or Seoul... hmm.  travel on Friday is
easier than Saturday.  The price is about the same as I paid for Prague.
The cheapest connects in Guam, which I've always wanted to do.

(Of course, the price to Tokyo or Hong Kong or Seoul will be higher..)

But, what will the price be, once we get our "block"?

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From ole@cisco.com  Thu Aug 25 07:31:58 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 136C921F8742 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27v8Cj1N4czf for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:31:57 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4C29021F86B3 for <ietf@ietf.org>; Thu, 25 Aug 2011 07:31:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=2600; q=dns/txt; s=iport; t=1314282791; x=1315492391; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=nPDUF1GhEV6FO9bSOCo14dHyA1XugQ6/AfQDtBSXj6o=; b=KwHgXa0Zp5BoPc5omqvNVxATGWDWSjC3hVPnExk0tKNNyEG6aUSZvIJ4 rYIxSjmSA75SDV/47sguCHwCLMastiskNRRjdbiUqzMLvrJ9IR+Pw2wOM Pktf6KHcKd3GN/hMKYAm4RXRznEPqDbTX1yDSlSkc7lgFY+/2IZK9h1om E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EABFcVk6rRDoI/2dsb2JhbAA/A6gBd4FAAQEBAQMBAQEPAQIBJCwEBAsQCw44JzAGExkJh1ScCAGDIw8BjhSNRINCgwoEh2GVMIcj
X-IronPort-AV: E=Sophos;i="4.68,281,1312156800"; d="scan'208";a="16439584"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-9.cisco.com with ESMTP; 25 Aug 2011 14:33:10 +0000
Received: from sjc-vpn5-137.cisco.com (sjc-vpn5-137.cisco.com [10.21.88.137]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7PEXA7C006837; Thu, 25 Aug 2011 14:33:10 GMT
Date: Thu, 25 Aug 2011 07:33:09 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: voting system for future venues?
In-Reply-To: <10493.1314282006@marajade.sandelman.ca>
Message-ID: <alpine.OSX.2.01.1108250721310.21519@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com> <4E5574AA.3030705@cs.tcd.ie><alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com><4E557A33.7050607@cs.tcd.ie><62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com><4E559A18.3090005@cs.tcd.ie><6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com><4E55A126.90102@cs.tcd.ie> <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com> <A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com> <alpine.OSX.2.01.11 08242012340.16097@sjc-vpn5-137.cisco.com> <10493.1314282006@marajade.sandelman.ca>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 14:31:58 -0000

Michael,

I think we could expect a room block cost similar to that of APRICOT 
2009, but the dollar has tanked since then so even "cheap" places in
Asia like this aren't so cheap any longer. And, yes, it would be "hard 
go get to" for some value of hard. I wasn't proposing we go there.

As Nathaniel pointed out, some currencies have really risen against
the dollar. It isn't that long ago that the yen was well above 100
to the dollar (the mental calculation point), somewhere in the 110-120
range actually, but TODAY it is at 76-77 yen to the dollar.

So, a hotel room back then (the peak was July 2007 at 123 yen to the 
dollar), say at 15,000 yen would cost ~ $121. Today that same room, 
still at 15,000 yen will cost ~ $197, heck let's call it $200.

The Sing dollar and Oz dollar have done similar things, Canadian too 
:-)

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Thu, 25 Aug 2011, Michael Richardson wrote:

> 
> >>>>> "Ole" == Ole Jacobsen <ole@cisco.com> writes:
>     Ole> The Sofitel Manila is where APRICOT 2009 was held. A great
>     Ole> venue, possibly even large enough to hold an IETF (I am not
>     Ole> sure), *and* the rate (at the time) at 7,525 Pesos was pretty
>     Ole> good. Today it is $177 which is still pretty good. The question
>     Ole> is: would the IETF go to the Philippines for a meeting. It's
>     Ole> worth finding out.
> 
> I can't find a flight that gets me there in less than 2 days from
> Canada.  I tried for November.  Most transit US (a -0.5 for me), many
> connect in Tokyo or Hong Kong or Seoul... hmm.  travel on Friday is
> easier than Saturday.  The price is about the same as I paid for Prague.
> The cheapest connects in Guam, which I've always wanted to do.
> 
> (Of course, the price to Tokyo or Hong Kong or Seoul will be higher..)
> 
> But, what will the price be, once we get our "block"?
> 
> -- 
> ]       He who is tired of Weird Al is tired of life!           |  firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
>    Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
> 	               then sign the petition. 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From anshumanpratap@gmail.com  Thu Aug 25 07:33:32 2011
Return-Path: <anshumanpratap@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADAA521F8801 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.846
X-Spam-Level: 
X-Spam-Status: No, score=-1.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SHRSB3tpdSdl for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:33:31 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC4E21F881C for <ietf@ietf.org>; Thu, 25 Aug 2011 07:33:31 -0700 (PDT)
Received: by wwf5 with SMTP id 5so1650850wwf.13 for <ietf@ietf.org>; Thu, 25 Aug 2011 07:34:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=x-rim-org-msg-ref-id:return-receipt-to:disposition-notification-to :message-id:content-transfer-encoding:reply-to:x-priority:references :in-reply-to:sensitivity:importance:subject:to:cc:from:date :content-type:mime-version; bh=lIKJzSiKTtPwYcf4LCRfW+OLs+GXFZs5PlvP9QK/Y+M=; b=NgnHYLHn3E2RMyilEi9XtIV2JbO3QXgSGP5cFwprMA4AhEXhdONkGC/p22fP79eO2K 79sNM3vhiv/IBiypYYFKIqt9FjwZvYICNf5YjYQFAZL0IH+b1U6z3ZFE0mdnfWQXH6mu hiZImoDddbSNo2fg4ia9xUbQgBElBsrzzU7As=
Received: by 10.227.24.18 with SMTP id t18mr1569478wbb.101.1314282884356; Thu, 25 Aug 2011 07:34:44 -0700 (PDT)
Received: from 172.18.196.179 (bda-178-239-83-217.bis7.eu.blackberry.com [178.239.83.217]) by mx.google.com with ESMTPS id 8sm506817wbx.17.2011.08.25.07.34.42 (version=SSLv3 cipher=OTHER); Thu, 25 Aug 2011 07:34:43 -0700 (PDT)
X-rim-org-msg-ref-id: 586477645
Message-ID: <586477645-1314282881-cardhu_decombobulator_blackberry.rim.net-212926249-@b1.c3.bise7.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <20110822191708.652C721F8C19@ietfa.amsl.com><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com><4E5574AA.3030705@cs.tcd.ie><alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com><4E557A33.7050607@cs.tcd.ie><62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com><4E559A18.3090005@cs.tcd.ie><6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com><4E55A126.90102@cs.tcd.ie><alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com><A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com><alpine.OSX.2.01.11 08242012340.16097@sjc-vpn5-137.cisco.com><10493.1314282006@marajade.sandelman.ca><alpine.OSX.2.01.1108250721310.21519@sjc-vpn5-137.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108250721310.21519@sjc-vpn5-137.cisco.com>
Sensitivity: Normal
Importance: Normal
Subject: Re: voting system for future venues?
To: "Ole Jacobsen" <ole@cisco.com>,"Michael Richardson" <mcr@sandelman.ca>
From: "Anshuman Pratap Chaudhary" <anshumanpratap@gmail.com>
Date: Thu, 25 Aug 2011 14:34:50 +0000
Content-Type: text/plain; charset="Windows-1252"
MIME-Version: 1.0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: anshumanpratap@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 14:33:32 -0000

TWF5YmUgbmV4dCB3ZSB0cnkgVWxhbiBCYXRvciwgTW9uZ29saWEgDQoNCg0KV2FybSBSZWdhcmRz
LCANCg0KQW5zaHVtYW4gDQoNCg0KU2VudCBmcm9tIG15IEJsYWNrQmVycnmuIFNtYXJ0cGhvbmUs
IHJlZ3JldCB0eXBvJ3MhDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IE9s
ZSBKYWNvYnNlbiA8b2xlQGNpc2NvLmNvbT4NClNlbmRlcjogaWV0Zi1ib3VuY2VzQGlldGYub3Jn
DQpEYXRlOiBUaHUsIDI1IEF1ZyAyMDExIDA3OjMzOjA5IA0KVG86IE1pY2hhZWwgUmljaGFyZHNv
bjxtY3JAc2FuZGVsbWFuLmNhPg0KUmVwbHktVG86IE9sZSBKYWNvYnNlbiA8b2xlQGNpc2NvLmNv
bT4NCkNjOiBJRVRGLURpc2N1c3Npb24gbGlzdDxpZXRmQGlldGYub3JnPg0KU3ViamVjdDogUmU6
IHZvdGluZyBzeXN0ZW0gZm9yIGZ1dHVyZSB2ZW51ZXM/DQoNCg0KTWljaGFlbCwNCg0KSSB0aGlu
ayB3ZSBjb3VsZCBleHBlY3QgYSByb29tIGJsb2NrIGNvc3Qgc2ltaWxhciB0byB0aGF0IG9mIEFQ
UklDT1QgDQoyMDA5LCBidXQgdGhlIGRvbGxhciBoYXMgdGFua2VkIHNpbmNlIHRoZW4gc28gZXZl
biAiY2hlYXAiIHBsYWNlcyBpbg0KQXNpYSBsaWtlIHRoaXMgYXJlbid0IHNvIGNoZWFwIGFueSBs
b25nZXIuIEFuZCwgeWVzLCBpdCB3b3VsZCBiZSAiaGFyZCANCmdvIGdldCB0byIgZm9yIHNvbWUg
dmFsdWUgb2YgaGFyZC4gSSB3YXNuJ3QgcHJvcG9zaW5nIHdlIGdvIHRoZXJlLg0KDQpBcyBOYXRo
YW5pZWwgcG9pbnRlZCBvdXQsIHNvbWUgY3VycmVuY2llcyBoYXZlIHJlYWxseSByaXNlbiBhZ2Fp
bnN0DQp0aGUgZG9sbGFyLiBJdCBpc24ndCB0aGF0IGxvbmcgYWdvIHRoYXQgdGhlIHllbiB3YXMg
d2VsbCBhYm92ZSAxMDANCnRvIHRoZSBkb2xsYXIgKHRoZSBtZW50YWwgY2FsY3VsYXRpb24gcG9p
bnQpLCBzb21ld2hlcmUgaW4gdGhlIDExMC0xMjANCnJhbmdlIGFjdHVhbGx5LCBidXQgVE9EQVkg
aXQgaXMgYXQgNzYtNzcgeWVuIHRvIHRoZSBkb2xsYXIuDQoNClNvLCBhIGhvdGVsIHJvb20gYmFj
ayB0aGVuICh0aGUgcGVhayB3YXMgSnVseSAyMDA3IGF0IDEyMyB5ZW4gdG8gdGhlIA0KZG9sbGFy
KSwgc2F5IGF0IDE1LDAwMCB5ZW4gd291bGQgY29zdCB+ICQxMjEuIFRvZGF5IHRoYXQgc2FtZSBy
b29tLCANCnN0aWxsIGF0IDE1LDAwMCB5ZW4gd2lsbCBjb3N0IH4gJDE5NywgaGVjayBsZXQncyBj
YWxsIGl0ICQyMDAuDQoNClRoZSBTaW5nIGRvbGxhciBhbmQgT3ogZG9sbGFyIGhhdmUgZG9uZSBz
aW1pbGFyIHRoaW5ncywgQ2FuYWRpYW4gdG9vIA0KOi0pDQoNCk9sZQ0KDQoNCk9sZSBKLiBKYWNv
YnNlbg0KRWRpdG9yIGFuZCBQdWJsaXNoZXIsICBUaGUgSW50ZXJuZXQgUHJvdG9jb2wgSm91cm5h
bA0KQ2lzY28gU3lzdGVtcw0KVGVsOiArMSA0MDgtNTI3LTg5NzIgICBNb2JpbGU6ICsxIDQxNS0z
NzAtNDYyOA0KRS1tYWlsOiBvbGVAY2lzY28uY29tICBVUkw6IGh0dHA6Ly93d3cuY2lzY28uY29t
L2lwag0KU2t5cGU6IG9yZ2FuZGVtbw0KDQoNCk9uIFRodSwgMjUgQXVnIDIwMTEsIE1pY2hhZWwg
UmljaGFyZHNvbiB3cm90ZToNCg0KPiANCj4gPj4+Pj4gIk9sZSIgPT0gT2xlIEphY29ic2VuIDxv
bGVAY2lzY28uY29tPiB3cml0ZXM6DQo+ICAgICBPbGU+IFRoZSBTb2ZpdGVsIE1hbmlsYSBpcyB3
aGVyZSBBUFJJQ09UIDIwMDkgd2FzIGhlbGQuIEEgZ3JlYXQNCj4gICAgIE9sZT4gdmVudWUsIHBv
c3NpYmx5IGV2ZW4gbGFyZ2UgZW5vdWdoIHRvIGhvbGQgYW4gSUVURiAoSSBhbSBub3QNCj4gICAg
IE9sZT4gc3VyZSksICphbmQqIHRoZSByYXRlIChhdCB0aGUgdGltZSkgYXQgNyw1MjUgUGVzb3Mg
d2FzIHByZXR0eQ0KPiAgICAgT2xlPiBnb29kLiBUb2RheSBpdCBpcyAkMTc3IHdoaWNoIGlzIHN0
aWxsIHByZXR0eSBnb29kLiBUaGUgcXVlc3Rpb24NCj4gICAgIE9sZT4gaXM6IHdvdWxkIHRoZSBJ
RVRGIGdvIHRvIHRoZSBQaGlsaXBwaW5lcyBmb3IgYSBtZWV0aW5nLiBJdCdzDQo+ICAgICBPbGU+
IHdvcnRoIGZpbmRpbmcgb3V0Lg0KPiANCj4gSSBjYW4ndCBmaW5kIGEgZmxpZ2h0IHRoYXQgZ2V0
cyBtZSB0aGVyZSBpbiBsZXNzIHRoYW4gMiBkYXlzIGZyb20NCj4gQ2FuYWRhLiAgSSB0cmllZCBm
b3IgTm92ZW1iZXIuICBNb3N0IHRyYW5zaXQgVVMgKGEgLTAuNSBmb3IgbWUpLCBtYW55DQo+IGNv
bm5lY3QgaW4gVG9reW8gb3IgSG9uZyBLb25nIG9yIFNlb3VsLi4uIGhtbS4gIHRyYXZlbCBvbiBG
cmlkYXkgaXMNCj4gZWFzaWVyIHRoYW4gU2F0dXJkYXkuICBUaGUgcHJpY2UgaXMgYWJvdXQgdGhl
IHNhbWUgYXMgSSBwYWlkIGZvciBQcmFndWUuDQo+IFRoZSBjaGVhcGVzdCBjb25uZWN0cyBpbiBH
dWFtLCB3aGljaCBJJ3ZlIGFsd2F5cyB3YW50ZWQgdG8gZG8uDQo+IA0KPiAoT2YgY291cnNlLCB0
aGUgcHJpY2UgdG8gVG9reW8gb3IgSG9uZyBLb25nIG9yIFNlb3VsIHdpbGwgYmUgaGlnaGVyLi4p
DQo+IA0KPiBCdXQsIHdoYXQgd2lsbCB0aGUgcHJpY2UgYmUsIG9uY2Ugd2UgZ2V0IG91ciAiYmxv
Y2siPw0KPiANCj4gLS0gDQo+IF0gICAgICAgSGUgd2hvIGlzIHRpcmVkIG9mIFdlaXJkIEFsIGlz
IHRpcmVkIG9mIGxpZmUhICAgICAgICAgICB8ICBmaXJld2FsbHMgIFsNCj4gXSAgIE1pY2hhZWwg
UmljaGFyZHNvbiwgU2FuZGVsbWFuIFNvZnR3YXJlIFdvcmtzLCBPdHRhd2EsIE9OICAgIHxuZXQg
YXJjaGl0ZWN0Ww0KPiBdIG1jckBzYW5kZWxtYW4ub3R0YXdhLm9uLmNhIGh0dHA6Ly93d3cuc2Fu
ZGVsbWFuLm90dGF3YS5vbi5jYS8gfGRldmljZSBkcml2ZXJbDQo+ICAgIEt5b3RvIFBsdXM6IHdh
dGNoIHRoZSB2aWRlbyA8aHR0cDovL3d3dy55b3V0dWJlLmNvbS93YXRjaD92PWt6eDF5Y0xYUVNF
Pg0KPiAJICAgICAgICAgICAgICAgdGhlbiBzaWduIHRoZSBwZXRpdGlvbi4gDQo+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IElldGYgbWFpbGluZyBs
aXN0DQo+IElldGZAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9pZXRmDQo+IA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCklldGYgbWFpbGluZyBsaXN0DQpJZXRmQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCg==


From mcr@sandelman.ca  Thu Aug 25 08:05:12 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22A3221F856B for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 08:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.524
X-Spam-Level: 
X-Spam-Status: No, score=-1.524 tagged_above=-999 required=5 tests=[AWL=0.430,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UMFDTQhdRkLu for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 08:05:11 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 970DB21F8559 for <ietf@ietf.org>; Thu, 25 Aug 2011 08:05:11 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 3E74D342C4; Thu, 25 Aug 2011 11:05:47 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 45B8398411; Thu, 25 Aug 2011 11:06:49 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Lou Berger <lberger@labn.net>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <4E565744.9010309@labn.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <BF7E8BEF-E29C-42C0-9ADE-49F3F4C8BB36@isoc.org>, <20110823022038.EC4DE21F87D9@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584A@DC-US1MBEX4.global.avaya.com>, <5E1BA899-821C-49E6-AB39-CB6489605E61@lucidvision.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F584C@DC-US1MBEX4.global.avaya.com> <alpine.OSX.2.01.1108231053160.70222@sjc-vpn4-416.cisco.com> <4E565744.9010309@labn.net>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 25 Aug 2011 11:06:49 -0400
Message-ID: <17894.1314284809@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 15:05:12 -0000

>>>>> "Lou" == Lou Berger <lberger@labn.net> writes:
    Lou> Ole, In the (somewhat far) past, my memory was that the IETF
    Lou> rate was *less* then the normal available rate.  This trend to
    Lou> higher rates is something I only remember seeing over the last
    Lou> 5 or so years.  Perhaps my memory is just flawed, as I haven't
    Lou> done the work to verify this, but I don't think so.

Yes, I agree.
It seems that it has occured since we started booking the events many
years in advance.   

When we booked at the last minute, and didn't know even where the
meeting was going to be more than two IETFs in advance, the room rates
were better.

    Lou> I personally think the issues to focus on/fix are the lack of
    Lou> transparency and the current approach of distributing meeting
    Lou> costs to the hotel rate.

It's more than that, but until we have this fixed, we can't know how
much more.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From julian.reschke@gmx.de  Thu Aug 25 09:31:15 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D219721F86AA for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 09:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.126
X-Spam-Level: 
X-Spam-Status: No, score=-104.126 tagged_above=-999 required=5 tests=[AWL=-1.527, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqZBbCCypXbs for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 09:31:15 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 2BE2721F85F2 for <ietf@ietf.org>; Thu, 25 Aug 2011 09:31:15 -0700 (PDT)
Received: (qmail invoked by alias); 25 Aug 2011 16:32:25 -0000
Received: from p508F9FF9.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.159.249] by mail.gmx.net (mp064) with SMTP; 25 Aug 2011 18:32:25 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19L+NdgjCJLLBVWXvenrAmu1DxwAcyrJfhlzK1DO6 ONgGuk24XtRmpX
Message-ID: <4E567918.4090707@gmx.de>
Date: Thu, 25 Aug 2011 18:32:24 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [websec] Last Call: <draft-ietf-websec-origin-04.txt> (The Web Origin Concept)	to Proposed Standard
References: <20110823211953.14482.9265.idtracker@ietfa.amsl.com>
In-Reply-To: <20110823211953.14482.9265.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: websec@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 16:31:16 -0000

Below a few late comments..

6. Serializing Origins

- It really really seems that the two algorithms need to be swapped (the 
first one converts to ASCII, but the second does not).

- Also, I'd prefer a declarative definition.

7. The HTTP Origin header

- header *field*

- the syntax doesn't allow multiple header fields, and the prose says 
clients MUST NOT generate them; what is the recipient supposed to do 
when it get's multiple instances anyway? Is the default approach 
(ignoring them all) good enough? Do we need to warn recipients so that 
they check?

11. References

- the WEBSOCKETS reference should be updated (if a new draft is produced)

Best regards, Julian

From koike.yoshinori@lab.ntt.co.jp  Thu Aug 25 09:32:25 2011
Return-Path: <koike.yoshinori@lab.ntt.co.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38EB921F8593; Thu, 25 Aug 2011 09:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.013
X-Spam-Level: *
X-Spam-Status: No, score=1.013 tagged_above=-999 required=5 tests=[AWL=1.103,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y8jBZ8TZqJ9u; Thu, 25 Aug 2011 09:32:24 -0700 (PDT)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by ietfa.amsl.com (Postfix) with ESMTP id 66B7C21F85C0; Thu, 25 Aug 2011 09:32:24 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama50.ecl.ntt.co.jp (8.14.5/8.14.5) with ESMTP id p7PGXWex011494; Fri, 26 Aug 2011 01:33:32 +0900 (JST)
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 64BFB65F9; Fri, 26 Aug 2011 01:33:32 +0900 (JST)
Received: from imail3.m.ecl.ntt.co.jp (imail3.m.ecl.ntt.co.jp [129.60.5.248]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 5877A65F1; Fri, 26 Aug 2011 01:33:32 +0900 (JST)
Received: from [129.60.11.43] (koike-pc.nslab.ecl.ntt.co.jp [129.60.11.43]) by imail3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id p7PGXWEl028329;  Fri, 26 Aug 2011 01:33:32 +0900
Message-ID: <4E5679AE.8010209@lab.ntt.co.jp>
Date: Fri, 26 Aug 2011 01:34:54 +0900
From: Yoshinori Koike <koike.yoshinori@lab.ntt.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLSOn-demand Connectivity Verification and Route Tracing) toProposed Standard
References: <20110811134542.25435.61281.idtracker@ietfa.amsl.com> <BAEC3B3B486642FB85C57EB439A38A73@nsl.ad.nec.co.jp>
In-Reply-To: <BAEC3B3B486642FB85C57EB439A38A73@nsl.ad.nec.co.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, Zhenlong Cui <c-sai@bx.jp.nec.com>, 'IETF-Announce' <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 16:32:25 -0000

Hi,

I would like to propose that this draft explicitly stipulate whether or 
not it covers per-interface model. I think it is essential to avoid 
confusion and clarify the appropriate I-D to discuss OAM solutions for 
the per-interface model.

"Per-interface model" is one of the two OAM maintenance models in 
MPLS-TP networks which is specified in section 3 of 
draft-ietf-mpls-tp-oam-framework.

The solution for the per-interface model is under discussion also in the 
per-interface MIP draft ( 
http://tools.ietf.org/html/draft-farrel-mpls-tp-mip-mep-map-04 ). If the 
on-demand-cv-06 covers the OAM solution for per-interface model, the 
discussion for on-demand CV and route tracing must be removed from the 
mip-mep-map draft. Otherwise, the mip-mep-map draft has to cover the 
solutions for on-demand CV and route tracing.

I also think that it is important to clarify the comments from Mr. 
Zhenlong Cui in the draft, whose email is attached at the bottom. It is 
important to make clear for what purpose the "IF_Num" is used. It also 
seems important to clarify the responder's behavior, because the 
ambiguity will definitely lead to interoperability issues.

Thank you in advance.

Best regards,

Yoshinori Koike

(2011/08/25 15:17), Zhenlong Cui wrote:
> Hi,
>
> I have sent some questions regarding the IF_Num of DSMAP TLV before. I'd like to make sure it is not lost.
>
>    2.1.  New address type for Downstream Mapping TLV
>     The new address type indicates that no address is present in the
>     DSMAP or DDMAP TLV.  However, IF_Num information (see definition of
>     "IF_NUM" in [I-D.ietf-mpls-tp-identifiers]) for both ingress and
>     egress interfaces, as well as multipath information is included in
>     the format and MAY be present.
>
>
> I believe the "IF_Num" can be used for per-interface MIP model.
> But I'm not sure why we need use both "ingress IF_Num" and "egress IF_Num" in a DSMAP TLV.
> I can't find this case (Ingress_IF::Egress_IF) in [I-D.ietf-mpls-tp-identifiers].
>
>   e.g.) the following are defined in [I-D.ietf-mpls-tp-identifiers] using "IF_Num", but there is no Ingress_IF::Egress_IF.
>   - "IF_ID"
>      IF_ID is a 64-bit identifier formed as Node_ID::IF_Num.
>   - "MIP ID"
>     For a MIP which is associated with particular interface, we simply
>     use the IF_ID (see Section 4) of the interfaces which are cross-
>     connected.
>
> If have any special means in the "IF_Num", I think MUST mention it clearly.
> Also I feeling that this draft have to clarify the responder's behavior for each IF information of the "IF_Num".
>
>
> Best regards,
> zhenlong
>
>
>> -----Original Message-----
>> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
>> Sent: Thursday, August 11, 2011 10:46 PM
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call:<draft-ietf-mpls-tp-on-demand-cv-06.txt>  (MPLSOn-demand Connectivity Verification and Route
>> Tracing) toProposed Standard
>>
>>
>> The IESG has received a request from the Multiprotocol Label Switching WG
>> (mpls) to consider the following document:
>> - 'MPLS On-demand Connectivity Verification and Route Tracing'
>>    <draft-ietf-mpls-tp-on-demand-cv-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
>> ietf@ietf.org mailing lists by 2011-08-25. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>     Label Switched Path Ping (LSP-Ping) is an existing and widely
>>     deployed Operations, Administration and Maintenance (OAM) mechanism
>>     for Multi-Protocol Label Switching (MPLS) Label Switched Paths
>>     (LSPs).  This document describes extensions to LSP-Ping so that LSP-
>>     Ping can be used for On-demand Connectivity Verification of MPLS
>>     Transport Profile (MPLS-TP) LSPs and Pseudowires.  This document also
>>     clarifies procedures to be used for processing the related OAM
>>     packets.  Further, it describes procedures for using LSP-Ping to
>>     perform Connectivity Verification and Route Tracing functions in
>>     MPLS-TP networks.  Finally this document updates RFC 4379 by adding a
>>     new address type and requesting an IANA registry.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>


--

From joelja@bogus.com  Thu Aug 25 09:39:30 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF94221F8997 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 09:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.334
X-Spam-Level: 
X-Spam-Status: No, score=-102.334 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKTALIx1ZeGu for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 09:39:30 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC1E21F89B8 for <ietf@ietf.org>; Thu, 25 Aug 2011 09:39:30 -0700 (PDT)
Received: from [10.101.144.54] (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7PGedTA053049 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 25 Aug 2011 16:40:39 GMT (envelope-from joelja@bogus.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E55BFB9.2070200@gmail.com>
Date: Thu, 25 Aug 2011 09:40:33 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <C4E4BE47-C2AF-4780-93BA-BAAAD0F67E88@bogus.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net>	<15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>	<4E556DFC.5060705@gmail.com> <4E5574AA.3030705@cs.tcd.ie>	<alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com>	<4E557A33.7050607@cs.tcd.ie>	<62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com>	<4E559A18.3090005@cs.tcd.ie>	<6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com>	<4E55A126.90102@cs.tcd.ie> <alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com> <4E55BFB9.! 2070200@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 25 Aug 2011 16:40:40 +0000 (UTC)
Cc: Ole Jacobsen <ole@cisco.com>, Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 16:39:30 -0000

On Aug 24, 2011, at 20:21 , Brian E Carpenter wrote:

> On 2011-08-25 13:42, somebody other than Ole Jacobsen wrote:
> 
>> "I agree that IAOC should
>> ensure that there are inexpensive hotels nearby so that
>> those with a tight budget can save money."
> 
> This is the key point. The anchor hotel, especially when there
> is a convention centre involved, is quite likely to be overpriced.

Overpriced is a value judgement subject to interpretation of market signals.

> The IAOC should, IMNSHO, ensure that an adequate set of moderately
> priced hotels within a short walk of the venue is available.
> That seems to be the problem in Taipei; the backup hotel is
> useless and not particularly cheap.
> 
>   Brian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 


From daedulus@btconnect.com  Thu Aug 25 09:59:28 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9432221F8B12 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 09:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level: 
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYPU-9q-k3iW for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 09:59:28 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr12.btconnect.com [213.123.26.190]) by ietfa.amsl.com (Postfix) with ESMTP id CBA0321F8AFA for <ietf@ietf.org>; Thu, 25 Aug 2011 09:59:26 -0700 (PDT)
Received: from c2beaomr08.ncs.ibs-infra.bt.com (EHLO mail.btconnect.com) ([10.87.14.168]) by c2beaomr12.btconnect.com (MOS 3.10.10a-GA FastPath queued) with ESMTP id AGL24100; Thu, 25 Aug 2011 18:00:36 +0100 (BST)
Received: (from localhost [127.0.0.1]) by c2beaomr08.btconnect.com (MOS 4.2.2-FCS) id EBI24182; Thu, 25 Aug 2011 17:59:35 +0100 (BST)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr08.btconnect.com with SMTP id EBI24150; Thu, 25 Aug 2011 17:59:31 +0100 (BST)
Message-ID: <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Thomas Nadeau" <tnadeau@lucidvision.com>, "Alia Atlas" <akatlas@gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com><801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu><4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu><4E555F6E.3060105@bbiw.net><CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com>
Subject: Re: Hyatt Taipei cancellation policy?
Date: Thu, 25 Aug 2011 17:55:45 +0200
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.0A0B0303.4E567F73.0029, actions=tag
X-Junkmail-Status: score=51/50, host=c2beaomr08.btconnect.com
Cc: Sam Hartman <hartmans-ietf@mit.edu>, Dave CROCKER <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 16:59:28 -0000

----- Original Message -----
From: "Thomas Nadeau" <tnadeau@lucidvision.com>
To: "Alia Atlas" <akatlas@gmail.com>
Cc: "Sam Hartman" <hartmans-ietf@mit.edu>; "Dave CROCKER" <dcrocker@bbiw.net>;
<ietf@ietf.org>
Sent: Wednesday, August 24, 2011 10:39 PM
On Aug 24, 2011, at 4:33 PM, Alia Atlas wrote:
> On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER <dcrocker@bbiw.net> wrote:
>
>
> On 8/24/2011 1:27 PM, Sam Hartman wrote:
> Can you start by backing up the assertion  that the community has
> vigrously expressed a preference for interesting venues?
> I may just need a new IETF community:-)
>
>
> gosh, I hadn't thought that that was less than obvious, given the vote for
quebec and many, many comments about venue choice over the years.
>
> I'm one who really liked Minneapolis - we had excellent meeting space, places
to run into each other, reasonable food access, and a clueful hotel.
>
> Is it interesting to go to new places?  Sure and if I'm lucky I might get a
morning or afternoon to look around.  Would I be perfectly happy going to the
same 2-3 places every year?  Absolutely.

I am with you on that. I do not attend IETFs as a vacation and sight-seeing
opportunity.

<tp>

Yes, I too go to work, and would rate Minneapolis in the top three, with Atlanta
perhaps just above it.

Tom
</tp>

--Tom


>
> Alia
> _______________________________________________
> 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 acee.lindem@ericsson.com  Wed Aug 24 09:04:42 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 805EE21F8C29; Wed, 24 Aug 2011 09:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.502
X-Spam-Level: 
X-Spam-Status: No, score=-6.502 tagged_above=-999 required=5 tests=[AWL=0.097,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AC9ChJ3r0pe1; Wed, 24 Aug 2011 09:04:42 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id E1DE821F8C37; Wed, 24 Aug 2011 09:04:41 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p7OG5iFK004500; Wed, 24 Aug 2011 11:05:49 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.60]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 24 Aug 2011 12:05:44 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Date: Wed, 24 Aug 2011 12:05:42 -0400
Subject: Re: [OSPF] [karp] Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Topic: [OSPF] [karp] Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer for OSPFv3) to Proposed Standard
Thread-Index: Acxid626BeUAPPcnQ2m798unkem+VQ==
Message-ID: <0E0AC0D0-0E8C-4CAE-8FDA-75D1AA4672D6@ericsson.com>
References: <20110719145739.5942.53564.idtracker@ietfa.amsl.com> <tsl7h6ed1sp.fsf@mit.edu> <7C362EEF9C7896468B36C9B79200D8350CFF9A5F02@INBANSXCHMBSA1.in.alcatel-lucent.com> <8D54DD3C-45C6-4C34-9CD3-DF6B6C758B4E@ericsson.com> <1D4A7913-4FE3-4B9F-9D0D-9FBC5E12F56E@ericsson.com> <7C362EEF9C7896468B36C9B79200D8350CFF9A5F06@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350CFF9A5F06@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-122-887293861"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: "ospf@ietf.org" <ospf@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 16:04:42 -0000

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

Hi Manav,

On Aug 24, 2011, at 10:51 AM, Bhatia, Manav (Manav) wrote:

> Hi Acee,
>=20
>>>>=20
>>>> We change the hex that's repeated in the Apad from=20
>> 0x878FE1F3 to 0x878FE1F4. This value will be unique for=20
>> OSPFv3. Other protocols that use this mechanism must use a=20
>> different value of Apad - you could think of this as=20
>> "salting" the Apad.
>>>=20
>>> Could we simply use the OSPFv3 protocol number, 89, in the=20
>> Apad, e.g., 0x898FE1F4,  (or at least the first instance of=20
>> Apad). Otherwise, we probably need a registry for IANA Apads.=20
>>=20
>> I meant 0x898FE1F3 as to not change the last 3 octets of the=20
>> existing HMAC-SHAx Apad.=20
>=20
> We would still need an IANA registry of Apads unless youre thinking of =
using the IP protocol type as the first octet of the Apad.

That's exactly what I'm proposing.=20

> If it's the latter, then OSPFv3 and OSPFv2 would share the same Apad, =
which would defeat the purpose of the whole exercise.

Are you forgetting about the version as the first nibble of the header?=20=


>=20
> This would also not work for multiple protocols that ride over UDP and =
TCP. BFD and RIP would end up using the same Apad as their IP protocol =
is the same.=20

UDP/TCP protocols would need a scheme that includes their well-know port =
- perhaps, the second octet of the first instance of Apad ;^).=20

>=20
> We thus need a unique Apad that each standard can define if we want to =
protect ourselves from the attack that Sam describes.

Thanks,
Acee


>=20
> Cheers, Manav=20


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDgyNDE2MDU0M1owIwYJKoZI
hvcNAQkEMRYEFOpRujaGcdfL0WArkk6oG5jwuoLqMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgB2cY+2KWiyaYGZsTDcuqeClGCQs4v5oTyN97fW9P+R4jIY7pOxLoN5qDyf5LQS5
GMIFSobD/6TNX1UgPgFO8bg4WhynxDg4H5Y4G6WwyyyyOtOlPZZeJ1zh4TIy/Nccs+/RpuEKoed0
xkYazsBbsBbSyG3uLoZP0ZPFbAQL3FM6AAAAAAAA

--Apple-Mail-122-887293861--

From acee.lindem@ericsson.com  Wed Aug 24 09:09:21 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1EC21F8C57; Wed, 24 Aug 2011 09:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.509
X-Spam-Level: 
X-Spam-Status: No, score=-6.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zwq9tDk8zzfY; Wed, 24 Aug 2011 09:09:20 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 8680821F8C51; Wed, 24 Aug 2011 09:09:20 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p7OGARCB005591; Wed, 24 Aug 2011 11:10:30 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.60]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Wed, 24 Aug 2011 12:10:25 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Acee Lindem <acee.lindem@ericsson.com>
Date: Wed, 24 Aug 2011 12:10:22 -0400
Subject: Re: [OSPF] [karp]	Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer	for OSPFv3) to Proposed Standard
Thread-Topic: [OSPF] [karp]	Last	Call: <draft-ietf-ospf-auth-trailer-ospfv3-05.txt>	(Supporting	Authentication Trailer	for OSPFv3) to Proposed Standard
Thread-Index: AcxieFTIhqaGR7zJSAawjNNO3iN7kQ==
Message-ID: <3D1FB5AD-C17E-4071-B20A-5F9B8B2044EA@ericsson.com>
References: <20110719145739.5942.53564.idtracker@ietfa.amsl.com> <tsl7h6ed1sp.fsf@mit.edu> <7C362EEF9C7896468B36C9B79200D8350CFF9A5F02@INBANSXCHMBSA1.in.alcatel-lucent.com> <8D54DD3C-45C6-4C34-9CD3-DF6B6C758B4E@ericsson.com> <1D4A7913-4FE3-4B9F-9D0D-9FBC5E12F56E@ericsson.com> <7C362EEF9C7896468B36C9B79200D8350CFF9A5F06@INBANSXCHMBSA1.in.alcatel-lucent.com> <0E0AC0D0-0E8C-4CAE-8FDA-75D1AA4672D6@ericsson.com>
In-Reply-To: <0E0AC0D0-0E8C-4CAE-8FDA-75D1AA4672D6@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-123-887573852"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: Sam Hartman <hartmans-ietf@mit.edu>, "ospf@ietf.org" <ospf@ietf.org>, "Bhatia, Manav \(Manav\)" <manav.bhatia@alcatel-lucent.com>, "ietf@ietf.org" <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 16:09:21 -0000

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


On Aug 24, 2011, at 12:05 PM, Acee Lindem wrote:

> Hi Manav,
>=20
> On Aug 24, 2011, at 10:51 AM, Bhatia, Manav (Manav) wrote:
>=20
>> Hi Acee,
>>=20
>>>>>=20
>>>>> We change the hex that's repeated in the Apad from=20
>>> 0x878FE1F3 to 0x878FE1F4. This value will be unique for=20
>>> OSPFv3. Other protocols that use this mechanism must use a=20
>>> different value of Apad - you could think of this as=20
>>> "salting" the Apad.
>>>>=20
>>>> Could we simply use the OSPFv3 protocol number, 89, in the=20
>>> Apad, e.g., 0x898FE1F4,  (or at least the first instance of=20
>>> Apad). Otherwise, we probably need a registry for IANA Apads.=20
>>>=20
>>> I meant 0x898FE1F3 as to not change the last 3 octets of the=20
>>> existing HMAC-SHAx Apad.=20
>>=20
>> We would still need an IANA registry of Apads unless youre thinking =
of using the IP protocol type as the first octet of the Apad.
>=20
> That's exactly what I'm proposing.=20
>=20
>> If it's the latter, then OSPFv3 and OSPFv2 would share the same Apad, =
which would defeat the purpose of the whole exercise.
>=20
> Are you forgetting about the version as the first nibble of the =
header?=20

Meant the first byte of course - first nibble is for IPv4 vs IPv6 ;^)=20

>=20
>>=20
>> This would also not work for multiple protocols that ride over UDP =
and TCP. BFD and RIP would end up using the same Apad as their IP =
protocol is the same.=20
>=20
> UDP/TCP protocols would need a scheme that includes their well-know =
port - perhaps, the second octet of the first instance of Apad ;^).=20
>=20
>>=20
>> We thus need a unique Apad that each standard can define if we want =
to protect ourselves from the attack that Sam describes.
>=20
> Thanks,
> Acee
>=20
>=20
>>=20
>> Cheers, Manav=20
>=20
> <smime.p7s>_______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDgyNDE2MTAyM1owIwYJKoZI
hvcNAQkEMRYEFCUqDwi7Yo7Z5jEYg0t/8/94IChDMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgH/OIfOzxr7yz1+wmoWTaSr/nux5vB8brXVB+0LH7dBLmJsTSw0ULOs8EIHrcaMu
cP6dVAAutILAFrwc6MdbnPf1cPlHV+7oOCKcuxWAk7pf6S8RZN0tjOGtVOQLtdmS+Jqvb4/hg7/v
cqoIA23pdehAwwt/hyBG81agE56Fd3iAAAAAAAAA

--Apple-Mail-123-887573852--

From kathleen.moriarty@emc.com  Wed Aug 24 10:12:56 2011
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE5C621F8BB2; Wed, 24 Aug 2011 10:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.381
X-Spam-Level: 
X-Spam-Status: No, score=-6.381 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nEnvhac7XwRO; Wed, 24 Aug 2011 10:12:56 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 43C0521F8B85; Wed, 24 Aug 2011 10:12:54 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7OHE1T9029861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 13:14:01 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 24 Aug 2011 13:13:52 -0400
Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.221.47.161]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7OHDpOY013891; Wed, 24 Aug 2011 13:13:51 -0400
Received: from mx06a.corp.emc.com ([169.254.1.199]) by mxhub32.corp.emc.com ([128.221.47.161]) with mapi; Wed, 24 Aug 2011 13:13:51 -0400
From: <kathleen.moriarty@emc.com>
To: <gen-art@ietf.org>, <ietf@ietf.org>, <draft-ietf-krb-wg-clear-text-cred.all@tools.ietf.org>
Date: Wed, 24 Aug 2011 13:13:50 -0400
Subject: GEN-ART review of draft-ietf-krb-wg-clear-text-cred-02
Thread-Topic: GEN-ART review of draft-ietf-krb-wg-clear-text-cred-02
Thread-Index: AQHMYn/TlKEQOpv20k2kRpn2uHPFZA==
Message-ID: <AE31510960917D478171C79369B660FA0E051CE825@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: rjy@cmu.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 17:12:56 -0000

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

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

Document: draft-ietf-krb-wg-clear-text-cred-02
Reviewer: Kathleen M. Moriarty
Review Date: 08-24-11
IETF LC End Date: 08-25-11
IESG Telechat date: 08-25-11

Summary: The document is ready with nits

Major issues:=20

Minor issues:=20

Nits/editorial comments:=20
Introduction:
Consider changing from:
  There are applications which need to transfer Kerberos credentials
   between them without having a prior relationship with established
   Kerberos keys.=20
To: "There are applications which need to transfer Kerberos credentials
   between them without having established a prior relationship with
   Kerberos keys."

Consider breaking the following sentence into two sentences, it is a little=
 difficult to read as a number of concepts are introduced within this one s=
entence:
   "In the SAML application, the Identity Provider (IdP) somehow obtains
   a Kerberos service ticket from the Kerberos Key Distribution Center
   (KDC) when required by the SAML system and transfers the credential
   to a Service Provider (SP) within an attribute statement."

Security Considerations section:
Consider changing the following From:
   The use of an unencrypted form of the KRB-CRED message MUST only be
   used with a transport where sender and recipient identities can been
   established to be known to each other.=20
To: "The use of an unencrypted form of the KRB-CRED message MUST only be
   used with a transport where sender and recipient identities can been
   established and are known to each other. "

Consider changing from:
   Examples of transports which MAY be securely used to transport an
   unencrypted KRB-CRED message would include Transport Layer Security
   (TLS) [RFC5246] where mutual authentication has been established and
   those encoded within encrypted and signed SAML Security Assertion
   Markup Language (SAML) 2.0 [OASIS.saml-core-2.0-os] statement.

To: Examples of transports which MAY be securely used to transport an
   unencrypted KRB-CRED message would include Transport Layer Security
   (TLS) [RFC5246], where mutual authentication has been established, and
   a SAML Security Assertion Markup Language (SAML) 2.0 [OASIS.saml-core-2.=
0-os] statement that is encrypted and signed.


Thanks,
Kathleen

From geoff@proto6.com  Wed Aug 24 13:32:51 2011
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BFCD21F8D02 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPrXZjcu9flK for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 13:32:50 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id CB2C821F8CFD for <ietf@ietf.org>; Wed, 24 Aug 2011 13:32:50 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id 78A93184E2; Wed, 24 Aug 2011 14:34:05 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id A4F0E15F504; Wed, 24 Aug 2011 14:33:57 -0600 (MDT)
Subject: Re: Hyatt Taipei cancellation policy?
From: geoff <geoff@proto6.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <tslmxey8sia.fsf@mit.edu>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net>  <tslmxey8sia.fsf@mit.edu>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 14:34:01 -0600
Message-ID: <1314218041.1973.204.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 20:32:51 -0000

On Wed, 2011-08-24 at 16:27 -0400, Sam Hartman wrote:
> >>>>> "Dave" == Dave CROCKER <dhc@dcrocker.net> writes:
> 
>     Dave> ps.  As a personal aside, I'll note that I've lobbied rather
>     Dave> vigorously for venues that entail less travel effort, by
>     Dave> eliminating the additional hop needed to get from a major hub.
>     Dave> Note that that has gotten essentially zero support from the
>     Dave> community.  The community has vigrously expressed a preference
>     Dave> for "interesting" venues rather than ones that are chosen
>     Dave> solely for logistics convenience.
> 
> Can you start by backing up the assertion  that the community has
> vigrously expressed a preference for interesting venues?
> I may just need a new IETF community:-)

I agree.  I think that there is a vocal minority that wants this.  I
don't think that community as a whole really cares.

We had this huge debate about the number of times (down to fractions of
times) to visit each area of the world so as to increase participation
and we then have locations that make it difficult to get to or expensive
or both and expensive to get to which limits participation.

I like Santa Clara, CA

	geoff

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



From geoff@proto6.com  Wed Aug 24 16:02:11 2011
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD8F421F8CFA for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKNQY-v8r5Dq for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:02:11 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id 492B521F8C7E for <ietf@ietf.org>; Wed, 24 Aug 2011 16:02:11 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id A4385184E1; Wed, 24 Aug 2011 17:03:25 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id 8D3DC15F508; Wed, 24 Aug 2011 17:03:14 -0600 (MDT)
Subject: Re: Hyatt Taipei cancellation policy?
From: geoff <geoff@proto6.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <tslr54a8v7s.fsf@mit.edu>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com>  <tslr54a8v7s.fsf@mit.edu>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 17:03:19 -0600
Message-ID: <1314226999.1973.211.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 23:02:11 -0000

On Wed, 2011-08-24 at 15:28 -0400, Sam Hartman wrote:
> 1) We don't have to go to any particular location.  There has been an
> assumption made by people in this discussion that sometimes when we pick
> locations with particularly expensive hotels, we'll get particularly
> expensive meetings.  That's great except that we were the ones who chose
> to go to those locations.
> If we can't meet our cost targets at a location, go somewhere else.
> 

Sam makes a really good point here.  We didn't have to go to Taipei.
For some reason we chose to go to Taipei.  When the IAOC was looking at
places years ago was the dollar so strong that the hotel was cheap - I
doubt it.  It was probably just as expensive back then.  It should have
just been dropped from the list and the city as wel.  The hotel (and
host if there was on) could/should have been told - sorry too expensive.
There was never a requirement to go to Taipei.  

There was never a requirement to go to Maastricht with the 3 train
changes and hotels spread out and not under a single roof, awful
cancellation policy (unless you booked it separately from the IETF).
Nice place, but no one ordered us to go to Maastricht.

I liked Hiroshima, but even it was not easy to get to (multiple trains).

We seem to be limiting attendance to people from large companies just so
that we can meet everywhere in the world.  If it isn't relatively
inexpensive then we say, sorry we can't go there.  So what.  We don't
have to visit every country. 

I know that this is blasphemous but why can't we meet in just a couple
of the same places over and over again -- yeah it's boring for those
that want to be a tourist, but I go to work and would prefer a venue
that has good/easy access (major airport nearby) with a "cheapish" hotel
and a decent cancellation policy.

	geoff

PS - Lets just go to Minneapolis 3 times a year - bet we can get a great
rate and the US dollar is on-sale!






From geoff@proto6.com  Wed Aug 24 16:02:24 2011
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E45221F8CFA for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yzolJQPLRS5H for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:02:24 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id 26BED21F8C7E for <ietf@ietf.org>; Wed, 24 Aug 2011 16:02:24 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id 7ECFA184E0; Wed, 24 Aug 2011 17:03:40 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id 0568E15F504; Wed, 24 Aug 2011 17:03:30 -0600 (MDT)
Subject: Re: Hyatt Taipei cancellation policy?
From: geoff <geoff@proto6.com>
To: Dave CROCKER <dcrocker@bbiw.net>
In-Reply-To: <4E555DCD.2000001@bbiw.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <4E555CB2.7070405@stpeter.im> <4E555DCD.2000001@bbiw.net>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 17:03:35 -0600
Message-ID: <1314227015.1973.212.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 23:02:24 -0000

Maybe the majority doesn't care one way or the other - they will just go
wherever the meetings are held in which case:
  let's make them easy to get to
  cheap
  decent food
  one roof (with other hotels near-by)
  cheap
  and easy to get to

You could pick Rosemont, IL (next to O'hare) for every meeting (oops,
sorry - misses on decent food).

	geoff

On Wed, 2011-08-24 at 13:23 -0700, Dave CROCKER wrote:
> 
> On 8/24/2011 1:18 PM, Peter Saint-Andre wrote:
> > As long as a relatively large percentage of IETF folks see meetings as
> > an opportunity to sight-see, I don't think we'll see much support for
> > rotating among a small set of major hub locations.
> 
> +1
> 
> But it's worse than "relatively large percent".  There's absolutely no minority 
> constituency that is vocal about wanting this to change.  That's why I declared 
> myself giving up on this topic.
> 




From geoff@proto6.com  Wed Aug 24 16:08:56 2011
Return-Path: <geoff@proto6.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C5F21F8CA5 for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id euS8IlJaGWlQ for <ietf@ietfa.amsl.com>; Wed, 24 Aug 2011 16:08:56 -0700 (PDT)
Received: from server2.coslabs.com (server2.coslabs.com [64.111.18.234]) by ietfa.amsl.com (Postfix) with ESMTP id 0055E21F8CA2 for <ietf@ietf.org>; Wed, 24 Aug 2011 16:08:56 -0700 (PDT)
Received: from grab.coslabs.com (mail.coslabs.com [199.233.92.34]) by server2.coslabs.com (Postfix) with ESMTP id 270D9184E4; Wed, 24 Aug 2011 17:04:16 -0600 (MDT)
Received: from [199.233.92.6] (unknown [199.233.92.6]) by grab.coslabs.com (Postfix) with ESMTP id 9C9DD15F504; Wed, 24 Aug 2011 17:04:05 -0600 (MDT)
Subject: Re: Hyatt Taipei cancellation policy?
From: geoff <geoff@proto6.com>
To: Ole Jacobsen <ole@cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108241408280.7436@sjc-vpn5-137.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <alpine.OSX.2.01.1108241408280.7436@sjc-vpn5-137.cisco.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 24 Aug 2011 17:04:10 -0600
Message-ID: <1314227050.1973.214.camel@d430>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: Dave CROCKER <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2011 23:08:56 -0000

On Wed, 2011-08-24 at 14:10 -0700, Ole Jacobsen wrote:
> On Wed, 24 Aug 2011, Dave CROCKER wrote:
> 
> > ps. Underlying any sort of change to the model is a change in the nature of
> > host/sponsor recruitment.  The current approach uses new venues to aid in
> > finding new sponsors.
> 
> Not quite. But you are correct that sponsors/hosts often strongly 
> influence the choice of venue and let's not forget that there are 
> places (China for example) where we could NOT do a meeting without
> a host [regardless of any financial considerations]. There may not
> be many such places, but the do exist.

I'm confused.  I heard earlier that we are picking sites 3 years ahead
of time, but that sponsorship is something that happens 18 months or
less.  So we are not picking venues based on sponsorship or are we?

If we didn't have a sponsor how much would the meeting fee increase?
$100 or $200?  That is more than offset by the increased cost of the
hotel ($150/night vs >$200/night).

	geoff

PS - I liked Philadelphia

> 
> Ole



From david.black@emc.com  Wed Aug 24 17:45:03 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31AD821F8B9F; Wed, 24 Aug 2011 17:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.544
X-Spam-Level: 
X-Spam-Status: No, score=-106.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVm5z+JjOUl0; Wed, 24 Aug 2011 17:45:02 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id ED4D321F8BF4; Wed, 24 Aug 2011 17:45:01 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7P0k8Zb032730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2011 20:46:08 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Wed, 24 Aug 2011 20:46:01 -0400
Received: from mxhub27.corp.emc.com (mxhub27.corp.emc.com [10.254.110.183]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7P0k0FA028250; Wed, 24 Aug 2011 20:46:00 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub27.corp.emc.com ([10.254.110.183]) with mapi; Wed, 24 Aug 2011 20:46:00 -0400
From: <david.black@emc.com>
To: <gareth.richards@rsa.com>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Wed, 24 Aug 2011 20:45:58 -0400
Subject: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: AcxiwFrEKzHJob9RQ2KJ4t0eYlZPlg==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: david.black@emc.com, hartmans-ietf@mit.edu, ietf-krb-wg@lists.anl.gov
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 00:45:03 -0000

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-krb-wg-otp-preauth-18
Reviewer: David L. Black
Review Date: August 24, 2011
IETF LC End Date: August 29, 2011

Summary: This draft is on the right track but has open issues, described in=
 the review.

This is a tightly written draft on one-time-password token-based preauthent=
ication for Kerberos.
The text does a good job of tightly specifying the algorithms and protocol =
steps; the resulting
text is a bit dense to read, but provides the necessary precision for imple=
mentation.

Disclaimer - the draft author and this reviewer work for different organiza=
tions in the
	same company (EMC).

I found two open issues, both of which are relatively minor:

[1] In section 6.1 at the top of p.28, I don't believe that the use of lowe=
r case
"recommended" is a strong enough warning about the danger in using
anonymous PKINIT because it exposes the OTP value:

   It is therefore recommended that anonymous PKINIT not be used with
   OTP algorithms that require the OTP value to be sent to the KDC and
   that careful consideration be made of the security implications
   before it is used with other algorithms such as those with short OTP
   values.

At a minimum, that warning should be in upper-case:

   It is therefore RECOMMENDED that anonymous PKINIT not be used with
   OTP algorithms that require the OTP value to be sent to the KDC. In
   addition, the security implications should be carefully considered
   before anonymous PKINIT is used with other algorithms such as those
   with short OTP values.

Beyond that, the security issue in the first sentence may be severe enough
to justify a prohibition, so the following would also be acceptable:

   Therefore anonymous PKINIT SHALL NOT be used with
   OTP algorithms that require the OTP value to be sent to the KDC. In
   addition, the security implications should be carefully considered
   before anonymous PKINIT is used with other algorithms such as those
   with short OTP values.

[2] In section 5, the first paragraph in the IANA considerations is unclear=
, and
following its reference to section 4.1, I don't see any clarifying text the=
re either.
I think Sections 4.1 and 4.2 need to say that the value of otp-algID is a U=
RI obtained
from the PSKC Algorithm URI Registry, and the first paragraph in section 5 =
should
say that URIs for otp-algID are to be registered in that registry, see RFC =
6030.

I also found a couple of minor nits:

In Section 1.1, please expand the FAST acronym on first use.

In section 2.4, the following sentence is potentially confusing:

   For example,
   event-based tokens may drift since the counter on the token is
   incremented every time the token is used but the counter on the
   server is only incremented on an authentication.  Similarly, the
   clocks on time-based tokens may drift.

The confusion arises because the resync mechanism described in that section=
 causes
the client to use the next token value.  By itself, that won't help when an=
 event based
has gotten ahead of the server; using the next value only puts the token fu=
rther ahead.
Similarly, by itself, this mechanism does not help if the token clock has d=
rifted ahead
of the server clock, but does help if the token clock has drifted behind.  =
A little more
explanation of what the server can do to take advantage of this mechanism (=
e.g., how to
deal with an event-based token that is ahead of the server) would reduce th=
e confusion.

idnits 2.12.12 generated a bunch of warnings, none of which require any cha=
nge to the draft.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From c-sai@bx.jp.nec.com  Wed Aug 24 23:16:31 2011
Return-Path: <c-sai@bx.jp.nec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39F9621F862F; Wed, 24 Aug 2011 23:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.167
X-Spam-Level: 
X-Spam-Status: No, score=0.167 tagged_above=-999 required=5 tests=[AWL=0.257,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pvJWI0eo2-Tf; Wed, 24 Aug 2011 23:16:30 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206]) by ietfa.amsl.com (Postfix) with ESMTP id F27F821F8532; Wed, 24 Aug 2011 23:16:22 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.195]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id p7P6HYTc013418;  Thu, 25 Aug 2011 15:17:34 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id p7P6HYW17797; Thu, 25 Aug 2011 15:17:34 +0900 (JST)
Received: from mail01b.kamome.nec.co.jp (mail01b.kamome.nec.co.jp [10.25.43.2]) by mailsv.nec.co.jp (8.13.8/8.13.4) with ESMTP id p7P6Gm6X013440; Thu, 25 Aug 2011 15:17:34 +0900 (JST)
Received: from shoin.jp.nec.com ([10.26.220.3] [10.26.220.3]) by mail03.kamome.nec.co.jp with ESMTP id BT-MMP-534035; Thu, 25 Aug 2011 15:17:11 +0900
Received: from vpcja157 ([10.38.16.157] [10.38.16.157]) by mail.jp.nec.com with ESMTP; Thu, 25 Aug 2011 15:17:10 +0900
From: "Zhenlong Cui" <c-sai@bx.jp.nec.com>
To: <ietf@ietf.org>, "'IETF-Announce'" <ietf-announce@ietf.org>
References: <20110811134542.25435.61281.idtracker@ietfa.amsl.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLSOn-demand	Connectivity Verification and Route Tracing) toProposed Standard
Date: Thu, 25 Aug 2011 15:17:10 +0900
Message-ID: <BAEC3B3B486642FB85C57EB439A38A73@nsl.ad.nec.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
In-Reply-To: <20110811134542.25435.61281.idtracker@ietfa.amsl.com>
Thread-Index: AcxYLQ19hjJdrZawTPmNVdgC6iRmUQKwNaAQ
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 06:16:31 -0000

Hi,

I have sent some questions regarding the IF_Num of DSMAP TLV before. I'd like to make sure it is not lost.

  2.1.  New address type for Downstream Mapping TLV
   The new address type indicates that no address is present in the
   DSMAP or DDMAP TLV.  However, IF_Num information (see definition of
   "IF_NUM" in [I-D.ietf-mpls-tp-identifiers]) for both ingress and
   egress interfaces, as well as multipath information is included in
   the format and MAY be present.


I believe the "IF_Num" can be used for per-interface MIP model.
But I'm not sure why we need use both "ingress IF_Num" and "egress IF_Num" in a DSMAP TLV.
I can't find this case (Ingress_IF::Egress_IF) in [I-D.ietf-mpls-tp-identifiers].

 e.g.) the following are defined in [I-D.ietf-mpls-tp-identifiers] using "IF_Num", but there is no Ingress_IF::Egress_IF.
 - "IF_ID" 
    IF_ID is a 64-bit identifier formed as Node_ID::IF_Num.    
 - "MIP ID"
   For a MIP which is associated with particular interface, we simply
   use the IF_ID (see Section 4) of the interfaces which are cross-
   connected. 

If have any special means in the "IF_Num", I think MUST mention it clearly.
Also I feeling that this draft have to clarify the responder's behavior for each IF information of the "IF_Num".


Best regards,
zhenlong


> -----Original Message-----
> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
> Sent: Thursday, August 11, 2011 10:46 PM
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-on-demand-cv-06.txt> (MPLSOn-demand Connectivity Verification and Route
> Tracing) toProposed Standard
> 
> 
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'MPLS On-demand Connectivity Verification and Route Tracing'
>   <draft-ietf-mpls-tp-on-demand-cv-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
> ietf@ietf.org mailing lists by 2011-08-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
>    Label Switched Path Ping (LSP-Ping) is an existing and widely
>    deployed Operations, Administration and Maintenance (OAM) mechanism
>    for Multi-Protocol Label Switching (MPLS) Label Switched Paths
>    (LSPs).  This document describes extensions to LSP-Ping so that LSP-
>    Ping can be used for On-demand Connectivity Verification of MPLS
>    Transport Profile (MPLS-TP) LSPs and Pseudowires.  This document also
>    clarifies procedures to be used for processing the related OAM
>    packets.  Further, it describes procedures for using LSP-Ping to
>    perform Connectivity Verification and Route Tracing functions in
>    MPLS-TP networks.  Finally this document updates RFC 4379 by adding a
>    new address type and requesting an IANA registry.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-on-demand-cv/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From henk@uijterwaal.nl  Thu Aug 25 05:18:28 2011
Return-Path: <henk@uijterwaal.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D167921F862F for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 05:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eP-bzfby0RdY for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 05:18:28 -0700 (PDT)
Received: from smtp-vbr1.xs4all.nl (smtp-vbr1.xs4all.nl [194.109.24.21]) by ietfa.amsl.com (Postfix) with ESMTP id D5B9221F85B8 for <ietf@ietf.org>; Thu, 25 Aug 2011 05:18:27 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) (authenticated bits=0) by smtp-vbr1.xs4all.nl (8.13.8/8.13.8) with ESMTP id p7PCJ7oQ075003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 25 Aug 2011 14:19:08 +0200 (CEST) (envelope-from henk@uijterwaal.nl)
Message-ID: <4E563DBA.5060402@uijterwaal.nl>
Date: Thu, 25 Aug 2011 14:19:06 +0200
From: Henk Uijterwaal <henk@uijterwaal.nl>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <BCEDB75B-8237-481A-AB4F-428D861F0D8A@network-heretics.com>
In-Reply-To: <BCEDB75B-8237-481A-AB4F-428D861F0D8A@network-heretics.com>
X-Enigmail-Version: 1.3.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 12:18:29 -0000

On 25/08/2011 13:06, Keith Moore wrote:
> On Aug 25, 2011, at 2:13 AM, Henk Uijterwaal wrote:

> But on what basis are the options discarded by IAOC, if the different options
> aren't examined to at least the level of detail that I suggested?

I think it is more a continuous process.  Start with a number of options,
investigate them in more detail, discard options as one goes along, work
out the 100,000 little details that need to be taken care of
with the most promising site only, then decide if the overal package is
a good one.  If not, repeat for the next site.

>> Do we really want to increase fees just to have more options?
> 
> Not more options, but more transparency into the selection and more assurance
> that the selection is made on the basis of what people really want or don't
> want.

There are a lot of requirements, 1,000 participants who all prioritize them
in different ways and there is no venue that meets all requirements.  Thus
whoever makes the selection will have to weigh all requirements and find a
solution that is optimal for most people.

The IETF has picked a model were a small set of people make this selection for
the rest of the group.  If you don't trust that they are trying their best
to make the optimal selection, then there is a fundamental problem that cannot
be solved by providing more documents, voting processes, etc.

>> Not true: it is not possible (nor sensible) to buy plane tickets 2 years in
>> advance and a lot of things can change in between.
> 
> True.  Though broadly speaking, if it's expensive to fly somewhere today,
> it's unlikely to be cheap to fly there in two years.

Not always, here in Europe, one often sees price-fights between various
airlines if a destination suddenly becomes popular for some reason or
another.  (And also the opposite: prices go up if the number of
competitors on a route drops).

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From david.black@emc.com  Thu Aug 25 06:12:52 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 036F621F8801; Thu, 25 Aug 2011 06:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.547
X-Spam-Level: 
X-Spam-Status: No, score=-106.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wPuzbt-Khy7S; Thu, 25 Aug 2011 06:12:51 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id EAE9021F8581; Thu, 25 Aug 2011 06:12:50 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7PDE1G1023032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Aug 2011 09:14:01 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 25 Aug 2011 09:13:50 -0400
Received: from mxhub10.corp.emc.com (mxhub10.corp.emc.com [10.254.92.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7PDDneW012319; Thu, 25 Aug 2011 09:13:49 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub10.corp.emc.com ([10.254.92.105]) with mapi; Thu, 25 Aug 2011 09:13:49 -0400
From: <david.black@emc.com>
To: <hartmans-ietf@mit.edu>
Date: Thu, 25 Aug 2011 09:13:47 -0400
Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: Acxiy1Wkpn0juVxqT8+Kvj0JYZK7NgAXLZWg
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu>
In-Reply-To: <tslliui6ycj.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
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: ietf@ietf.org, gareth.richards@rsa.com, gen-art@ietf.org, ietf-krb-wg@lists.anl.gov, david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 13:12:52 -0000

Hi Sam,

Thanks for the quick response?  I'll watch for the new text on anonymous PK=
INIT.

> Why should we require that alg-ids be registered URIs? =20

That's not my concern - the existing first paragraph of the IANA considerat=
ions section in the draft requires IANA registration (or at least tries to)=
 by pointing to the PSKC registry.  My concern is that if this is going to =
be done, it needs to be done right (duh!), and the current text is insuffic=
ient. Please take the issue of whether to use IANA for this purpose up with=
 Gareth and the WG.

> I have no problem with the IETF registering its algorithms there, or us
> encouraging people to register them there, but it's a URI. What purpose
> is served by forcing registration?

Hmm - more than one URI for the same algorithm might cause interoperability=
 problems.

Thanks,
--David

> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Wednesday, August 24, 2011 10:04 PM
> To: Black, David
> Cc: Richards, Gareth; gen-art@ietf.org; ietf@ietf.org; ietf-krb-wg@lists.=
anl.gov; hartmans-
> ietf@mit.edu; stephen.farrell@cs.tcd.ie
> Subject: Re: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
>=20
> >>>>>   <david.black@emc.com> writes:
>=20
>=20
>     > [1] In section 6.1 at the top of p.28, I don't believe that the
>     > use of lower case "recommended" is a strong enough warning about
>     > the danger in using anonymous PKINIT because it exposes the OTP
>     > value:
>=20
>     >    It is therefore recommended that anonymous PKINIT not be used
>     > with OTP algorithms that require the OTP value to be sent to the
>     > KDC and that careful consideration be made of the security
>     > implications before it is used with other algorithms such as those
>     > with short OTP values.
>=20
>     > At a minimum, that warning should be in upper-case:
>=20
>     >    It is therefore RECOMMENDED that anonymous PKINIT not be used
>     > with OTP algorithms that require the OTP value to be sent to the
>     > KDC. In addition, the security implications should be carefully
>     > considered before anonymous PKINIT is used with other algorithms
>     > such as those with short OTP values.
>=20
>     > Beyond that, the security issue in the first sentence may be
>     > severe enough to justify a prohibition, so the following would
>     > also be acceptable:
>=20
>     >    Therefore anonymous PKINIT SHALL NOT be used with OTP
>     > algorithms that require the OTP value to be sent to the KDC. In
>     > addition, the security implications should be carefully considered
>     > before anonymous PKINIT is used with other algorithms such as
>     > those with short OTP values.
>=20
> I definitely agree that we should use RFC 2119 language.
> Note that WG participants have questioned this text in last call for
> other reasons.
> Many implementations use anonymous pkinit in a mode where the KDC's
> certificate is verified--that is the client is anonymous but the KDC is
> identified through a PKI.
> WG participants believe (and I agree) that the security concern does not
> apply at all in this case.
> So, the text needs reworking.
>=20
>     > [2] In section 5, the first paragraph in the IANA considerations
>     > is unclear, and following its reference to section 4.1, I don't
>     > see any clarifying text there either.  I think Sections 4.1 and
>     > 4.2 need to say that the value of otp-algID is a URI obtained from
>     > the PSKC Algorithm URI Registry, and the first paragraph in
>     > section 5 should say that URIs for otp-algID are to be registered
>     > in that registry, see RFC 6030.
>=20
> Why should we require that alg-ids be registered URIs?  I.E. what is
> wrong with me using
> http://algorithms.painless-security.com/otp/best-thing-since-unsliced-bre=
ad
> (or a tag URI if you like) for my OTP algorithm?
> I have no problem with the IETF registering its algorithms there, or us
> encouraging people to register them them, but it's a URI. What purpose
> is served by forcing registration?


From david.black@emc.com  Thu Aug 25 06:19:43 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1A621F85A4; Thu, 25 Aug 2011 06:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.028
X-Spam-Level: 
X-Spam-Status: No, score=-106.028 tagged_above=-999 required=5 tests=[AWL=0.571, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrxDTnHkunV0; Thu, 25 Aug 2011 06:19:42 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 0FEE321F84FC; Thu, 25 Aug 2011 06:19:41 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7PDKpsu013641 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Aug 2011 09:20:51 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Thu, 25 Aug 2011 09:20:39 -0400
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.221.56.109]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7PDKd0V008090; Thu, 25 Aug 2011 09:20:39 -0400
Received: from mx14a.corp.emc.com ([169.254.1.245]) by mxhub23.corp.emc.com ([128.221.56.109]) with mapi; Thu, 25 Aug 2011 09:20:39 -0400
From: <david.black@emc.com>
To: <david.black@emc.com>, <hartmans-ietf@mit.edu>
Date: Thu, 25 Aug 2011 09:20:37 -0400
Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: Acxiy1Wkpn0juVxqT8+Kvj0JYZK7NgAXLZWgAABq8tA=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CEB@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: ietf@ietf.org, gareth.richards@rsa.com, gen-art@ietf.org, ietf-krb-wg@lists.anl.gov, david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 13:19:43 -0000

Make that - Thanks for the quick response. (off-by-one key error ...)

Thanks,
--David


> -----Original Message-----
> From: Black, David
> Sent: Thursday, August 25, 2011 9:14 AM
> To: Sam Hartman
> Cc: Richards, Gareth; gen-art@ietf.org; ietf@ietf.org; ietf-krb-wg@lists.=
anl.gov;
> stephen.farrell@cs.tcd.ie; Black, David
> Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
>=20
> Hi Sam,
>=20
> Thanks for the quick response?  I'll watch for the new text on anonymous =
PKINIT.
>=20
> > Why should we require that alg-ids be registered URIs?
>=20
> That's not my concern - the existing first paragraph of the IANA consider=
ations section in the draft
> requires IANA registration (or at least tries to) by pointing to the PSKC=
 registry.  My concern is
> that if this is going to be done, it needs to be done right (duh!), and t=
he current text is
> insufficient. Please take the issue of whether to use IANA for this purpo=
se up with Gareth and the WG.
>=20
> > I have no problem with the IETF registering its algorithms there, or us
> > encouraging people to register them there, but it's a URI. What purpose
> > is served by forcing registration?
>=20
> Hmm - more than one URI for the same algorithm might cause interoperabili=
ty problems.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> > Sent: Wednesday, August 24, 2011 10:04 PM
> > To: Black, David
> > Cc: Richards, Gareth; gen-art@ietf.org; ietf@ietf.org; ietf-krb-wg@list=
s.anl.gov; hartmans-
> > ietf@mit.edu; stephen.farrell@cs.tcd.ie
> > Subject: Re: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
> >
> > >>>>>   <david.black@emc.com> writes:
> >
> >
> >     > [1] In section 6.1 at the top of p.28, I don't believe that the
> >     > use of lower case "recommended" is a strong enough warning about
> >     > the danger in using anonymous PKINIT because it exposes the OTP
> >     > value:
> >
> >     >    It is therefore recommended that anonymous PKINIT not be used
> >     > with OTP algorithms that require the OTP value to be sent to the
> >     > KDC and that careful consideration be made of the security
> >     > implications before it is used with other algorithms such as thos=
e
> >     > with short OTP values.
> >
> >     > At a minimum, that warning should be in upper-case:
> >
> >     >    It is therefore RECOMMENDED that anonymous PKINIT not be used
> >     > with OTP algorithms that require the OTP value to be sent to the
> >     > KDC. In addition, the security implications should be carefully
> >     > considered before anonymous PKINIT is used with other algorithms
> >     > such as those with short OTP values.
> >
> >     > Beyond that, the security issue in the first sentence may be
> >     > severe enough to justify a prohibition, so the following would
> >     > also be acceptable:
> >
> >     >    Therefore anonymous PKINIT SHALL NOT be used with OTP
> >     > algorithms that require the OTP value to be sent to the KDC. In
> >     > addition, the security implications should be carefully considere=
d
> >     > before anonymous PKINIT is used with other algorithms such as
> >     > those with short OTP values.
> >
> > I definitely agree that we should use RFC 2119 language.
> > Note that WG participants have questioned this text in last call for
> > other reasons.
> > Many implementations use anonymous pkinit in a mode where the KDC's
> > certificate is verified--that is the client is anonymous but the KDC is
> > identified through a PKI.
> > WG participants believe (and I agree) that the security concern does no=
t
> > apply at all in this case.
> > So, the text needs reworking.
> >
> >     > [2] In section 5, the first paragraph in the IANA considerations
> >     > is unclear, and following its reference to section 4.1, I don't
> >     > see any clarifying text there either.  I think Sections 4.1 and
> >     > 4.2 need to say that the value of otp-algID is a URI obtained fro=
m
> >     > the PSKC Algorithm URI Registry, and the first paragraph in
> >     > section 5 should say that URIs for otp-algID are to be registered
> >     > in that registry, see RFC 6030.
> >
> > Why should we require that alg-ids be registered URIs?  I.E. what is
> > wrong with me using
> > http://algorithms.painless-security.com/otp/best-thing-since-unsliced-b=
read
> > (or a tag URI if you like) for my OTP algorithm?
> > I have no problem with the IETF registering its algorithms there, or us
> > encouraging people to register them them, but it's a URI. What purpose
> > is served by forcing registration?


From hsantos@santronics.com  Thu Aug 25 07:49:54 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40E2C21F8A56 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6CBY1u2GxnG for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 07:49:53 -0700 (PDT)
Received: from news.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3B43C21F8A4D for <ietf@ietf.org>; Thu, 25 Aug 2011 07:49:52 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=966; t=1314283859; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=i80pvT7 crQg32EQqabtn1wERBXY=; b=LTbQP2i4fL5O9VdLmr6dmLA0381UIqhULKJw2o+ d1PZPcVgXj7MyDpfx5+K+ofe2oacPqmojvtOle7G0rNXAWXJXiwNjzM9v6WHS6mQ XJXvAQoqUt6bVg3twNAstEJSTCzuSaNtoySU4kMca9pKtveJ8UolotIWxCoM5ZUA 8BjA=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 25 Aug 2011 10:50:59 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2739273227.36043.2060; Thu, 25 Aug 2011 10:50:10 -0400
Message-ID: <4E56611F.8090207@santronics.com>
Date: Thu, 25 Aug 2011 10:50:07 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net>	<15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>	<7AE9A1D4-439A-4857-85BF-C1BED2FC4309@standardstrack.com> <F1B0F373-B4FB-42D0-B549-CC7F2635E9A3@network-heretics.com>
In-Reply-To: <F1B0F373-B4FB-42D0-B549-CC7F2635E9A3@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 25 Aug 2011 10:07:04 -0700
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 14:49:54 -0000

Keith Moore wrote:
> On Aug 24, 2011, at 5:48 PM, Eric Burger wrote:
> 
>> Let's ask again: what is it you WANT?
> 
> Personally, I want to be able to afford to travel to the meetings, and to be able 
> to do so without having to commit to spending the money months in advance.
> 
> More broadly, I want IETF meetings to be accessible by a wide range 
> of interests: academics, operators, small vendors, large vendors, even 
users.

Whether or not this is feasible and/or possible by the organization, 
among the entire thread, this is probably the best ideal to improve 
the future of the IETF that also takes into account minimizing the 
expensive total hardship (from travel to lodging) to attend a meeting. 
  There are many aspects of the IETF associated with the desires of 
different groups that can be distributed into different symposiums, 
work shops, etc, in different locations.

+1.

-- 
Sincerely

Hector Santos
http://www.santronics.com




From mary.ietf.barnes@gmail.com  Thu Aug 25 10:11:05 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFA2821F888A for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.147
X-Spam-Level: 
X-Spam-Status: No, score=-103.147 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1uLPCWk2iJ5 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:11:04 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 283A821F886A for <ietf@ietf.org>; Thu, 25 Aug 2011 10:11:04 -0700 (PDT)
Received: by ewy19 with SMTP id 19so1188365ewy.31 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:12:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZPVB1x3OQP10gn+IYrbDMUkgyMTeJdrysXq12ODeMD0=; b=C3+LFF4NBBnVNlVUe9P+WBJxaCme8gDD9KUgX3M6GIO1sk9FkLyvSUV8UbptQ/taM9 lZLCzppv2KL0YtZysr1KWJY3AccuiKzpGC7Fxoks8gVz2vj80n+MF5ilFLBWGPKanyY3 n3nfcjVo8BgtWtwm5kArcG/tI878vpnJqUmYc=
MIME-Version: 1.0
Received: by 10.52.180.167 with SMTP id dp7mr1446103vdc.451.1314292336785; Thu, 25 Aug 2011 10:12:16 -0700 (PDT)
Received: by 10.52.160.36 with HTTP; Thu, 25 Aug 2011 10:12:16 -0700 (PDT)
In-Reply-To: <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net>
Date: Thu, 25 Aug 2011 12:12:16 -0500
Message-ID: <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "t.petch" <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=bcaec517a9b8dd77f804ab578797
Cc: ietf@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 17:11:06 -0000

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

I am also a fan of Minneapolis for meetings - the facilities at the Hilton
are perfect for our needs.  There's lots of food options.  It has good air
connections and there is decent pubic transport from the airport to the
city.  However, this seems to be a minority perspective. If we were to do
votes again, the results might be interesting.

Mary.

On Thu, Aug 25, 2011 at 10:55 AM, t.petch <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: "Thomas Nadeau" <tnadeau@lucidvision.com>
> To: "Alia Atlas" <akatlas@gmail.com>
> Cc: "Sam Hartman" <hartmans-ietf@mit.edu>; "Dave CROCKER" <
> dcrocker@bbiw.net>;
> <ietf@ietf.org>
> Sent: Wednesday, August 24, 2011 10:39 PM
> On Aug 24, 2011, at 4:33 PM, Alia Atlas wrote:
> > On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER <dcrocker@bbiw.net> wrote:
> >
> >
> > On 8/24/2011 1:27 PM, Sam Hartman wrote:
> > Can you start by backing up the assertion  that the community has
> > vigrously expressed a preference for interesting venues?
> > I may just need a new IETF community:-)
> >
> >
> > gosh, I hadn't thought that that was less than obvious, given the vote
> for
> quebec and many, many comments about venue choice over the years.
> >
> > I'm one who really liked Minneapolis - we had excellent meeting space,
> places
> to run into each other, reasonable food access, and a clueful hotel.
> >
> > Is it interesting to go to new places?  Sure and if I'm lucky I might get
> a
> morning or afternoon to look around.  Would I be perfectly happy going to
> the
> same 2-3 places every year?  Absolutely.
>
> I am with you on that. I do not attend IETFs as a vacation and sight-seeing
> opportunity.
>
> <tp>
>
> Yes, I too go to work, and would rate Minneapolis in the top three, with
> Atlanta
> perhaps just above it.
>
> Tom
> </tp>
>
> --Tom
>
>
> >
> > Alia
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>
>
>
>
>
> --------------------------------------------------------------------------------
>
>
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

I am also a fan of Minneapolis for meetings - the facilities at the Hilton =
are perfect for our needs. =A0There&#39;s lots of food options. =A0It has g=
ood air connections and there is decent pubic transport from the airport to=
 the city. =A0However, this seems to be a minority perspective. If we were =
to do votes again, the results might be interesting.=A0<div>
<br></div><div>Mary.=A0<br><div><br><div class=3D"gmail_quote">On Thu, Aug =
25, 2011 at 10:55 AM, t.petch <span dir=3D"ltr">&lt;<a href=3D"mailto:daedu=
lus@btconnect.com">daedulus@btconnect.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex;">
----- Original Message -----<br>
From: &quot;Thomas Nadeau&quot; &lt;<a href=3D"mailto:tnadeau@lucidvision.c=
om">tnadeau@lucidvision.com</a>&gt;<br>
To: &quot;Alia Atlas&quot; &lt;<a href=3D"mailto:akatlas@gmail.com">akatlas=
@gmail.com</a>&gt;<br>
Cc: &quot;Sam Hartman&quot; &lt;<a href=3D"mailto:hartmans-ietf@mit.edu">ha=
rtmans-ietf@mit.edu</a>&gt;; &quot;Dave CROCKER&quot; &lt;<a href=3D"mailto=
:dcrocker@bbiw.net">dcrocker@bbiw.net</a>&gt;;<br>
&lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
Sent: Wednesday, August 24, 2011 10:39 PM<br>
On Aug 24, 2011, at 4:33 PM, Alia Atlas wrote:<br>
&gt; On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER &lt;<a href=3D"mailto:dc=
rocker@bbiw.net">dcrocker@bbiw.net</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On 8/24/2011 1:27 PM, Sam Hartman wrote:<br>
&gt; Can you start by backing up the assertion =A0that the community has<br=
>
&gt; vigrously expressed a preference for interesting venues?<br>
&gt; I may just need a new IETF community:-)<br>
&gt;<br>
&gt;<br>
&gt; gosh, I hadn&#39;t thought that that was less than obvious, given the =
vote for<br>
quebec and many, many comments about venue choice over the years.<br>
&gt;<br>
&gt; I&#39;m one who really liked Minneapolis - we had excellent meeting sp=
ace, places<br>
to run into each other, reasonable food access, and a clueful hotel.<br>
&gt;<br>
&gt; Is it interesting to go to new places? =A0Sure and if I&#39;m lucky I =
might get a<br>
morning or afternoon to look around. =A0Would I be perfectly happy going to=
 the<br>
same 2-3 places every year? =A0Absolutely.<br>
<br>
I am with you on that. I do not attend IETFs as a vacation and sight-seeing=
<br>
opportunity.<br>
<br>
&lt;tp&gt;<br>
<br>
Yes, I too go to work, and would rate Minneapolis in the top three, with At=
lanta<br>
perhaps just above it.<br>
<br>
Tom<br>
&lt;/tp&gt;<br>
<br>
--Tom<br>
<br>
<br>
&gt;<br>
&gt; Alia<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>
<br>
<br>
---------------------------------------------------------------------------=
-----<br>
<br>
<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>
</blockquote></div><br></div></div>

--bcaec517a9b8dd77f804ab578797--

From joelja@bogus.com  Thu Aug 25 10:15:42 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B1721F8AD9 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.058
X-Spam-Level: 
X-Spam-Status: No, score=-102.058 tagged_above=-999 required=5 tests=[AWL=-0.059, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VDcKhMT6CRxj for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:15:41 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B76E121F8A64 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:15:41 -0700 (PDT)
Received: from Zorch.local (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7PHGiJ8055213 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 25 Aug 2011 17:16:44 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E568377.20707@bogus.com>
Date: Thu, 25 Aug 2011 10:16:39 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com><801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu><4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu><4E555F6E.3060105@bbiw.net><CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net>
In-Reply-To: <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 25 Aug 2011 17:16:45 +0000 (UTC)
Cc: ietf@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 17:15:42 -0000

On 8/25/11 08:55 , t.petch wrote:
> Yes, I too go to work, and would rate Minneapolis in the top three,
> with Atlanta perhaps just above it. Tom </tp> --Tom
In Minneapolis I think you're talking about a specific venue and city.
In the case of Atlanta I'm guessing not, we've had two meetings, 55 and
21. I'm not party to the details for 21 but I helped host 55 and I don't
not have a lot of love for the Marriott Marquis.

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


From HKaplan@acmepacket.com  Thu Aug 25 10:35:20 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2C021F8BB8 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.214
X-Spam-Level: 
X-Spam-Status: No, score=-2.214 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zc6xbLpAnMDr for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:35:19 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC0E21F8BB7 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:35:19 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 25 Aug 2011 13:36:30 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 25 Aug 2011 13:36:30 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Thu, 25 Aug 2011 13:36:21 -0400
Subject: Re: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: AcxjTYXnKlREDhSFSIKdrVVdmP2kwg==
Message-ID: <AF48D46B-E207-47A1-81CB-3C073239F63C@acmepacket.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com>
In-Reply-To: <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@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_AF48D46BE20747A181CB3C073239F63Cacmepacketcom_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAUA=
Cc: Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 17:35:20 -0000

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


If we use actual *attendance* as a form of voting, Minneapolis would lose b=
ig time.

According to the stats, since IETF-1, there have been 6 IETF meetings in Mi=
nneapolis.  Every one of them had significantly lower number of participant=
s than the meeting before and after them... except IETF-44 which was lower =
than IETF-43 but about the same as IETF-45, but IETF-45 was in Oslo, Norway=
, and IETF-46 went back up to higher levels again.

-hadriel


On Aug 25, 2011, at 1:12 PM, Mary Barnes wrote:

I am also a fan of Minneapolis for meetings - the facilities at the Hilton =
are perfect for our needs.  There's lots of food options.  It has good air =
connections and there is decent pubic transport from the airport to the cit=
y.  However, this seems to be a minority perspective. If we were to do vote=
s again, the results might be interesting.

Mary.

On Thu, Aug 25, 2011 at 10:55 AM, t.petch <daedulus@btconnect.com<mailto:da=
edulus@btconnect.com>> wrote:
----- Original Message -----
From: "Thomas Nadeau" <tnadeau@lucidvision.com<mailto:tnadeau@lucidvision.c=
om>>
To: "Alia Atlas" <akatlas@gmail.com<mailto:akatlas@gmail.com>>
Cc: "Sam Hartman" <hartmans-ietf@mit.edu<mailto:hartmans-ietf@mit.edu>>; "D=
ave CROCKER" <dcrocker@bbiw.net<mailto:dcrocker@bbiw.net>>;
<ietf@ietf.org<mailto:ietf@ietf.org>>
Sent: Wednesday, August 24, 2011 10:39 PM
On Aug 24, 2011, at 4:33 PM, Alia Atlas wrote:
> On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER <dcrocker@bbiw.net<mailto:d=
crocker@bbiw.net>> wrote:
>
>
> On 8/24/2011 1:27 PM, Sam Hartman wrote:
> Can you start by backing up the assertion  that the community has
> vigrously expressed a preference for interesting venues?
> I may just need a new IETF community:-)
>
>
> gosh, I hadn't thought that that was less than obvious, given the vote fo=
r
quebec and many, many comments about venue choice over the years.
>
> I'm one who really liked Minneapolis - we had excellent meeting space, pl=
aces
to run into each other, reasonable food access, and a clueful hotel.
>
> Is it interesting to go to new places?  Sure and if I'm lucky I might get=
 a
morning or afternoon to look around.  Would I be perfectly happy going to t=
he
same 2-3 places every year?  Absolutely.

I am with you on that. I do not attend IETFs as a vacation and sight-seeing
opportunity.

<tp>

Yes, I too go to work, and would rate Minneapolis in the top three, with At=
lanta
perhaps just above it.

Tom
</tp>

--Tom


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

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

<ATT00001..c>


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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; "><div><br></div><div>If we =
use actual *attendance* as a form of voting, Minneapolis would lose big tim=
e.</div><div><br></div><div>According to the stats, since IETF-1, there hav=
e been 6 IETF meetings in Minneapolis. &nbsp;Every one of them had signific=
antly lower number of participants than the meeting before and after them..=
. except IETF-44 which was lower than IETF-43 but about the same as IETF-45=
, but IETF-45 was in Oslo, Norway, and IETF-46 went back up to higher level=
s again.</div><div><br></div><div>-hadriel</div><div><br></div><div><br></d=
iv><div><div>On Aug 25, 2011, at 1:12 PM, Mary Barnes wrote:</div><br class=
=3D"Apple-interchange-newline"><blockquote type=3D"cite">I am also a fan of=
 Minneapolis for meetings - the facilities at the Hilton are perfect for ou=
r needs. &nbsp;There's lots of food options. &nbsp;It has good air connecti=
ons and there is decent pubic transport from the airport to the city. &nbsp=
;However, this seems to be a minority perspective. If we were to do votes a=
gain, the results might be interesting.&nbsp;<div>
<br></div><div>Mary.&nbsp;<br><div><br><div class=3D"gmail_quote">On Thu, A=
ug 25, 2011 at 10:55 AM, t.petch <span dir=3D"ltr">&lt;<a href=3D"mailto:da=
edulus@btconnect.com">daedulus@btconnect.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex;">
----- Original Message -----<br>
From: "Thomas Nadeau" &lt;<a href=3D"mailto:tnadeau@lucidvision.com">tnadea=
u@lucidvision.com</a>&gt;<br>
To: "Alia Atlas" &lt;<a href=3D"mailto:akatlas@gmail.com">akatlas@gmail.com=
</a>&gt;<br>
Cc: "Sam Hartman" &lt;<a href=3D"mailto:hartmans-ietf@mit.edu">hartmans-iet=
f@mit.edu</a>&gt;; "Dave CROCKER" &lt;<a href=3D"mailto:dcrocker@bbiw.net">=
dcrocker@bbiw.net</a>&gt;;<br>
&lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
Sent: Wednesday, August 24, 2011 10:39 PM<br>
On Aug 24, 2011, at 4:33 PM, Alia Atlas wrote:<br>
&gt; On Wed, Aug 24, 2011 at 4:30 PM, Dave CROCKER &lt;<a href=3D"mailto:dc=
rocker@bbiw.net">dcrocker@bbiw.net</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On 8/24/2011 1:27 PM, Sam Hartman wrote:<br>
&gt; Can you start by backing up the assertion &nbsp;that the community has=
<br>
&gt; vigrously expressed a preference for interesting venues?<br>
&gt; I may just need a new IETF community:-)<br>
&gt;<br>
&gt;<br>
&gt; gosh, I hadn't thought that that was less than obvious, given the vote=
 for<br>
quebec and many, many comments about venue choice over the years.<br>
&gt;<br>
&gt; I'm one who really liked Minneapolis - we had excellent meeting space,=
 places<br>
to run into each other, reasonable food access, and a clueful hotel.<br>
&gt;<br>
&gt; Is it interesting to go to new places? &nbsp;Sure and if I'm lucky I m=
ight get a<br>
morning or afternoon to look around. &nbsp;Would I be perfectly happy going=
 to the<br>
same 2-3 places every year? &nbsp;Absolutely.<br>
<br>
I am with you on that. I do not attend IETFs as a vacation and sight-seeing=
<br>
opportunity.<br>
<br>
&lt;tp&gt;<br>
<br>
Yes, I too go to work, and would rate Minneapolis in the top three, with At=
lanta<br>
perhaps just above it.<br>
<br>
Tom<br>
&lt;/tp&gt;<br>
<br>
--Tom<br>
<br>
<br>
&gt;<br>
&gt; Alia<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>
<br>
<br>
---------------------------------------------------------------------------=
-----<br>
<br>
<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>
</blockquote></div><br></div></div>
<span>&lt;ATT00001..c&gt;</span></blockquote></div><br></body></html>=

--_000_AF48D46BE20747A181CB3C073239F63Cacmepacketcom_--

From melinda.shore@gmail.com  Thu Aug 25 10:40:59 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D879B21F8B2D for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.532
X-Spam-Level: 
X-Spam-Status: No, score=-3.532 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p28WyvffqTI5 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:40:59 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 59C2F21F8862 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:40:59 -0700 (PDT)
Received: by pzk33 with SMTP id 33so6671462pzk.18 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:42:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=0DaPWLTQYq1YFMV0xSVVDsOJCfptwM5fzcTbLRnd/oQ=; b=WQwNHIAraG1eiRIfy116Tc4ICgrPQwbH8DvAp3P74EA8MqvZJ2u7BFNF/xJWDVazTm OL1/tZ0mGUp1Gly6DQqSqsyhJcOJrsTH9J8F1wW/4JDQcV//pRmedOa96jSNlA/WoJs4 LUbLOknsh2Z/hh4wYJqOFuPTij704fL7Lvsqc=
Received: by 10.142.225.6 with SMTP id x6mr20136wfg.55.1314294127731; Thu, 25 Aug 2011 10:42:07 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id r9sm653454pbs.11.2011.08.25.10.42.05 (version=SSLv3 cipher=OTHER); Thu, 25 Aug 2011 10:42:06 -0700 (PDT)
Message-ID: <4E568970.2090706@gmail.com>
Date: Thu, 25 Aug 2011 09:42:08 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<4E555F6E.3060105@bbiw.net>	<CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com>	<2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com>	<008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net>	<CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <AF48D46B-E207-47A1-81CB-3C073239F63C@acmepacket.com>
In-Reply-To: <AF48D46B-E207-47A1-81CB-3C073239F63C@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 17:41:00 -0000

On 08/25/2011 09:36 AM, Hadriel Kaplan wrote:
> According to the stats, since IETF-1, there have been 6 IETF meetings in
> Minneapolis. Every one of them had significantly lower number of
> participants than the meeting before and after them... except IETF-44
> which was lower than IETF-43 but about the same as IETF-45, but IETF-45
> was in Oslo, Norway, and IETF-46 went back up to higher levels again.

One could make some guesses about why that might be the case,
but probably shouldn't.  At any rate I don't think I've ever
seen anybody complain about the meeting facilities in
Minneapolis.  Myself, I think they're probably the best
of the various venues we've tried.  Must be some other factor.
Hmmmmm.

Melinda

From hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com  Thu Aug 25 10:49:37 2011
Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B810E21F8C36 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.839
X-Spam-Level: 
X-Spam-Status: No, score=-102.839 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nowQjYUn6-eA for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 10:49:37 -0700 (PDT)
Received: from mail-ey0-f174.google.com (mail-ey0-f174.google.com [209.85.215.174]) by ietfa.amsl.com (Postfix) with ESMTP id AD87421F8C1E for <ietf@ietf.org>; Thu, 25 Aug 2011 10:49:36 -0700 (PDT)
Received: by eyx24 with SMTP id 24so1975866eyx.19 for <ietf@ietf.org>; Thu, 25 Aug 2011 10:50:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=AN/XMH1TwvqcqXiAdKzIV2nHHMW6A/mMGvb+9o+wugo=; b=Sfvcjzis0KOV7m3jSfhNH/Hf8bNC/Eqom9LAbZZDdQjhpnt0vKIO7FYdbPeNMnRWoM axmCU6OOYMNMuCY+VIA8Dnf+qJzqe+E7BounbluIlJpWwlw+TpkhzT26bVrsygYFCnNs iutdzw2OtvSAsVmwAyHSu9O8iVUGDC2f0uREc=
Received: by 10.142.196.20 with SMTP id t20mr7410wff.355.1314294649109; Thu, 25 Aug 2011 10:50:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.98.5 with HTTP; Thu, 25 Aug 2011 10:50:09 -0700 (PDT)
In-Reply-To: <20110825102401.GA10559@nic.fr>
References: <20110825102401.GA10559@nic.fr>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Thu, 25 Aug 2011 19:50:09 +0200
Message-ID: <CAHhFybrv4xt7ZRvjZXUyTODoB8R3_yBUheZo-iOHr+Lnqo9mzA@mail.gmail.com>
Subject: Re: Questionnaire to survey opinion concerning a possible redefinition of UTC
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 17:49:37 -0000

On 25 August 2011 12:24, Stephane Bortzmeyer wrote:

> Since several RFCs rely on UTC and leap seconds (3339, 4765, 5905,
> etc), this questionnaire may be of interest for some persons

Thanks for info.

MJD 55798.740729 <URL:http://tycho.usno.navy.mil/cgi-bin/daterdnm.sh>

-Frank

From marshall.eubanks@gmail.com  Thu Aug 25 11:04:55 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C8E21F8C80 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.15
X-Spam-Level: 
X-Spam-Status: No, score=-103.15 tagged_above=-999 required=5 tests=[AWL=0.448, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtV+Zo7JSBip for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:04:55 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 10C2121F8C7F for <ietf@ietf.org>; Thu, 25 Aug 2011 11:04:54 -0700 (PDT)
Received: by gyf3 with SMTP id 3so2327919gyf.31 for <ietf@ietf.org>; Thu, 25 Aug 2011 11:06:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EO2E7p+0OtAFfm0paPyr3yPdsCwHZGJYo3laSc3wKNI=; b=ofPj1hv5ql6eLj4qPEpOLmCIi0j01skZPeRmlO3aWHZR3QMArAWRt8kgmxmX5vqPCi SekT2N2hbTlYK/6RcDbUy+L2mUDcf8LcfEmrfYguolL29mYnHaCZTUVhxz6z+Q9lk45B CIc32wp16ed+ql92c5GI3SFgO5nuDqkfYsS1E=
MIME-Version: 1.0
Received: by 10.151.78.8 with SMTP id f8mr1263051ybl.12.1314295564574; Thu, 25 Aug 2011 11:06:04 -0700 (PDT)
Received: by 10.150.202.16 with HTTP; Thu, 25 Aug 2011 11:06:04 -0700 (PDT)
In-Reply-To: <CAHhFybrv4xt7ZRvjZXUyTODoB8R3_yBUheZo-iOHr+Lnqo9mzA@mail.gmail.com>
References: <20110825102401.GA10559@nic.fr> <CAHhFybrv4xt7ZRvjZXUyTODoB8R3_yBUheZo-iOHr+Lnqo9mzA@mail.gmail.com>
Date: Thu, 25 Aug 2011 14:06:04 -0400
Message-ID: <CAJNg7VJP4G7LUA86RUFBEvGGXHF73TtQ=tdurHG5iXFpq0AxJA@mail.gmail.com>
Subject: Re: Questionnaire to survey opinion concerning a possible redefinition of UTC
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Content-Type: multipart/alternative; boundary=0015174bebfa41a0e804ab5848df
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 18:04:55 -0000

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

On Thu, Aug 25, 2011 at 1:50 PM, Frank Ellermann <
hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> wrote:

> On 25 August 2011 12:24, Stephane Bortzmeyer wrote:
>
> > Since several RFCs rely on UTC and leap seconds (3339, 4765, 5905,
> > etc), this questionnaire may be of interest for some persons
>
> So UTC would become a YATSCOT (Yet another time scale with a constant
offset to TAI.)

By my count, that would make 4 (not counting time zone offsets).

I would contend that RFCs relying on UTC would be unaffected and SHOULD NOT
change :

- the leap seconds will just stop. Since they are unpredictable, that is
really no change.  (I.e., the Earth already could chose to rotate in such a
fashion as no new leap seconds were ever needed.) That just means little
bits of code that won't be executed any more. Not changing the RFCs will
future proof you from # 2.

- If it is decided in 1000 years to put in a leap hour, that is just so many
leap seconds.

- UTC would remain civil time (the time computers and networks will mostly
be set to, modulo time zone offsets).

- I am not aware of any RFCs for sextant based celestial navigation (which
WILL have to change).

Regards
Marshall


> Thanks for info.
>
> MJD 55798.740729 <URL:http://tycho.usno.navy.mil/cgi-bin/daterdnm.sh>
>
> -Frank
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

<div><br><br><div class=3D"gmail_quote">On Thu, Aug 25, 2011 at 1:50 PM, Fr=
ank Ellermann <span dir=3D"ltr">&lt;<a href=3D"mailto:hmdmhdfmhdjmzdtjmzdtz=
ktdkztdjz@gmail.com">hmdmhdfmhdjmzdtjmzdtzktdkztdjz@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;"><div class=3D"im">On 25 August 2011 12:24, =
Stephane Bortzmeyer wrote:<br>
<br>
&gt; Since several RFCs rely on UTC and leap seconds (3339, 4765, 5905,<br>
&gt; etc), this questionnaire may be of interest for some persons<br><br></=
div></blockquote><div><div>So UTC would become a=A0YATSCOT (Yet another tim=
e scale with a constant offset to TAI.)=A0</div><div><div><br></div><div>By=
 my count, that would make 4 (not counting time zone offsets).=A0</div>
</div></div><div><br></div><div>I would contend that RFCs relying on UTC wo=
uld be unaffected and SHOULD NOT change :</div><div><br></div><div>- the le=
ap seconds will just stop. Since they are unpredictable, that is really no =
change. =A0(I.e., the Earth already could chose to rotate in such a</div>
<div>fashion as no new leap seconds were ever needed.) That just means litt=
le bits of code that won&#39;t be executed any more. Not changing the RFCs =
will future proof you from # 2.=A0</div><div><br></div><div>- If it is deci=
ded in 1000 years to put in a leap hour, that is just so many leap seconds.=
=A0</div>
<div><br></div><div>- UTC would remain civil time (the time computers and n=
etworks will mostly be set to, modulo time zone offsets).</div><div><br></d=
iv><div>- I am not aware of any RFCs for sextant based celestial navigation=
 (which WILL have to change).=A0</div>
<div><br></div><div>Regards</div><div>Marshall</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;"><div class=3D"im">
</div>Thanks for info.<br>
<br>
MJD 55798.740729 &lt;URL:<a href=3D"http://tycho.usno.navy.mil/cgi-bin/date=
rdnm.sh" target=3D"_blank">http://tycho.usno.navy.mil/cgi-bin/daterdnm.sh</=
a>&gt;<br>
<br>
-Frank<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>

--0015174bebfa41a0e804ab5848df--

From stbryant@cisco.com  Thu Aug 25 11:07:26 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7BDB21F8B36 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.54
X-Spam-Level: 
X-Spam-Status: No, score=-110.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ivj-PkBkdaE2 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:07:26 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE0821F8B2F for <ietf@ietf.org>; Thu, 25 Aug 2011 11:07:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=528; q=dns/txt; s=iport; t=1314295720; x=1315505320; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=TbV30POqMJVDhullTzOg+NcYp9SzwjfJtDCUbCrGduM=; b=Sr9y/dtiNz75NbzmKjaAiBy/jgYn41TIz0ORkFxxg+h6r91GxwCIK2ts rOWC7zCWI5/NyxPX+7dQBMFTl/Zm1SwcFLPl95invWlxSHw9deh7Hok8H wtfyaEb8E7qNMxvIxJJP6H+0ct3KQW2ELy2oi/NEBxyvNNahXhTCvMQR7 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvgGAAOPVk6Q/khM/2dsb2JhbABDmG+PFHeBQAEBAQEDEgECASJAEQsYCRYPCQMCAQIBRRMIAQEeozABgyMPAZtOhkwEkxmQfA
X-IronPort-AV: E=Sophos;i="4.68,281,1312156800"; d="scan'208";a="52027439"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 25 Aug 2011 18:08:39 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7PI8dvH026639 for <ietf@ietf.org>; Thu, 25 Aug 2011 18:08:39 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p7PI8bbW001499; Thu, 25 Aug 2011 19:08:38 +0100 (BST)
Message-ID: <4E568FA5.7020704@cisco.com>
Date: Thu, 25 Aug 2011 19:08:37 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com>
In-Reply-To: <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 18:07:26 -0000

On 25/08/2011 18:12, Mary Barnes wrote:
> I am also a fan of Minneapolis for meetings - the facilities at the 
> Hilton are perfect for our needs.  There's lots of food options.  It 
> has good air connections and there is decent pubic transport from the 
> airport to the city.  However, this seems to be a minority 
> perspective. If we were to do votes again, the results might be 
> interesting.
>
> Mary.

I like Minneapolis as well, but then, speaking personally, I like US 
IETF venues in general.

Stewart

From hartmans@mit.edu  Thu Aug 25 11:20:50 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9101E21F8B26 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.567
X-Spam-Level: 
X-Spam-Status: No, score=-103.567 tagged_above=-999 required=5 tests=[AWL=-1.302, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J9CKiXPoQlvJ for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:20:50 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id EEAD721F8B24 for <ietf@ietf.org>; Thu, 25 Aug 2011 11:20:49 -0700 (PDT)
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 E232A203A1; Thu, 25 Aug 2011 14:24:19 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 0FD2E423D; Thu, 25 Aug 2011 14:21:55 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <AF48D46B-E207-47A1-81CB-3C073239F63C@acmepacket.com>
Date: Thu, 25 Aug 2011 14:21:55 -0400
In-Reply-To: <AF48D46B-E207-47A1-81CB-3C073239F63C@acmepacket.com> (Hadriel Kaplan's message of "Thu, 25 Aug 2011 13:36:21 -0400")
Message-ID: <tsl7h615p30.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: Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 18:20:50 -0000

    Hadriel> If we use actual *attendance* as a form of voting,
    Hadriel> Minneapolis would lose big time.


I don't think using actual attendance is the right metric. Actual
attendance of people who submitted internet drafts or chaired meetings
would be closer, but is also problematic.
My goals are to:

1)  Make IETFs easy for people doing current technical work within the
organization

2) Ease getting involved in doing technical work in the organization

I'm not sure what metric is best for judging things, but I have low
confidence that raw attendance maps onto those two goals.

From randy@qualcomm.com  Thu Aug 25 11:41:10 2011
Return-Path: <randy@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F2D21F8B81 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.559
X-Spam-Level: 
X-Spam-Status: No, score=-106.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PgRS5RMPZZdx for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:41:09 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 23FA721F8B7D for <ietf@ietf.org>; Thu, 25 Aug 2011 11:41:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1314297743; x=1345833743; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p0624060dca7c4638be38@12-187-150-172.att- inc.com>|In-Reply-To:=20<BCEDB75B-8237-481A-AB4F-428D861F 0D8A@network-heretics.com>|References:=20<20110822191708. 652C721F8C19@ietfa.amsl.com>=0D=0A=20<801FB726-F672-4F7F- 8D9C-7ED37DB08672@cs.ucla.edu>=0D=0A=20<FE5EB7C9-C395-4B9 8-A0D4-8B2320F78C04@isoc.org>=0D=0A=20<66998320DD3FCC5628 E32634@PST.JCK.COM>=0D=0A=20<F74DDD2D-163A-4CBF-99A5-E452 CBB7C17F@isoc.org>=0D=0A=20<CE8FC485-DA54-491B-B57E-96DA2 FE835FC@network-heretics.com>=0D=0A=20<34E4F50CAFA10349A4 1E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>=0D=0A =20<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics .com>=0D=0A=20<4E554C78.9000504@gmail.com>=20<tslr54a8v7s .fsf@mit.edu>=0D=0A=20<4E555B06.6000108@dcrocker.net>=20< tslmxey8sia.fsf@mit.edu>=0D=0A=20<1314218041.1973.204.cam el@d430>=20<4E55655C.6030502@bbiw.net>=0D=0A=20<15F4BD95- 8858-4E47-896A-703A472412B1@network-heretics.com>=0D=0A =20<4E55E827.4060802@gmail.com>=0D=0A=20<BCEDB75B-8237-48 1A-AB4F-428D861F0D8A@network-heretics.com>|X-Mailer:=20Eu dora=20for=20Mac=20OS=20X|Date:=20Thu,=2025=20Aug=202011 =2011:35:16=20-0700|To:=20Keith=20Moore=20<moore@network- heretics.com>,=20<henk@uijterwaal.nl>|From:=20Randall=20G ellens=20<randy@qualcomm.com>|Subject:=20Re:=20voting=20s ystem=20for=20future=20venues?|CC:=20<ietf@ietf.org> |MIME-Version:=201.0|Content-Type:=20text/plain=3B=20char set=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.39.5]; bh=EE4BeirDJ5h+JIQm4hnagRm3cfRePIxZWZdehev+d+A=; b=b2brpHnfmyMJWp8RyhbhTLRiwnzg6Aoh8CAbqzsQlQgHhgnellSl+xwN oVfqUxvzVXdqKgsvcR2IiHj7dKEBlX8GZ6jVNM+04GWgeKRYyhNM67slD KHxx172t6l+YlDqKi5tjkZCLLbVxHnaXfRPXxiB236z2UkMFTBNiSO1pd U=;
X-IronPort-AV: E=McAfee;i="5400,1158,6448"; a="112765105"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 25 Aug 2011 11:42:07 -0700
X-IronPort-AV: E=Sophos;i="4.68,281,1312182000"; d="scan'208";a="124350683"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 25 Aug 2011 11:42:07 -0700
Received: from 12-187-150-172.att-inc.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 25 Aug 2011 11:42:05 -0700
Message-ID: <p0624060dca7c4638be38@12-187-150-172.att-inc.com>
In-Reply-To: <BCEDB75B-8237-481A-AB4F-428D861F0D8A@network-heretics.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <BCEDB75B-8237-481A-AB4F-428D861F0D8A@network-heretics.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 25 Aug 2011 11:35:16 -0700
To: Keith Moore <moore@network-heretics.com>, <henk@uijterwaal.nl>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: voting system for future venues?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 18:41:10 -0000

At 7:06 AM -0400 8/25/11, Keith Moore wrote:

>  (Admittedly, the real gotcha in Quebec seems to have been that 
> there were so few seats available that the few low-priced fares 
> were quickly exhausted. Everyone could get quotes two years in 
> advance and all see the same cheap fares, even if those fares were 
> only available for say 10 seats per day.)

I think the small number of carriers and type of service (mostly 
commuter) had a large effect on Quebec.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If God lived on Earth, people would knock out all His windows.
                                             --Yiddish saying

From joelja@bogus.com  Thu Aug 25 11:55:43 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132FE21F8B78 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.353
X-Spam-Level: 
X-Spam-Status: No, score=-102.353 tagged_above=-999 required=5 tests=[AWL=0.246, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-8UNSbyc4pq for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 11:55:42 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 91C4A21F8B8A for <ietf@ietf.org>; Thu, 25 Aug 2011 11:55:42 -0700 (PDT)
Received: from Zorch.local (host-64-47-136-190.masergy.com [64.47.136.190]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7PIutvD060784 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 25 Aug 2011 18:56:55 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E569AF1.5010302@bogus.com>
Date: Thu, 25 Aug 2011 11:56:49 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Randall Gellens <randy@qualcomm.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <BCEDB75B-8237-481A-AB4F-428D861F0D8A@network-heretics.com> <p0624060dca7c4638be38@12-187-150-172.att-inc.com>
In-Reply-To: <p0624060dca7c4638be38@12-187-150-172.att-inc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 25 Aug 2011 18:56:56 +0000 (UTC)
Cc: henk@uijterwaal.nl, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 18:55:43 -0000

On 8/25/11 11:35 , Randall Gellens wrote:
> At 7:06 AM -0400 8/25/11, Keith Moore wrote:
> 
>>  (Admittedly, the real gotcha in Quebec seems to have been that there
>> were so few seats available that the few low-priced fares were quickly
>> exhausted. Everyone could get quotes two years in advance and all see
>> the same cheap fares, even if those fares were only available for say
>> 10 seats per day.)

I used montreal by booking viarail, mechanically it worked rather well
but it did take longer.

> I think the small number of carriers and type of service (mostly
> commuter) had a large effect on Quebec.

Not trying to travel on the same day as the other 600 people trying to
get out on friday afternoon is an optimzation of another type.


From randy@qualcomm.com  Thu Aug 25 12:44:32 2011
Return-Path: <randy@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED1F421F8C15 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 12:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.56
X-Spam-Level: 
X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvFnjLQOSpsR for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 12:44:32 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 302D821F8C11 for <ietf@ietf.org>; Thu, 25 Aug 2011 12:44:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1314301546; x=1345837546; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p0624060fca7c54ac988d@12-187-150-172.att- inc.com>|In-Reply-To:=20<CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVx hr2cm2Atp_CR99HnfkQ@mail.gmail.com>|References:=20<201108 22191708.652C721F8C19@ietfa.amsl.com>=0D=0A=20<801FB726-F 672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>=0D=0A=20<FE5EB7C9 -C395-4B98-A0D4-8B2320F78C04@isoc.org>=0D=0A=20<66998320D D3FCC5628E32634@PST.JCK.COM>=0D=0A=20<F74DDD2D-163A-4CBF- 99A5-E452CBB7C17F@isoc.org>=0D=0A=20<CE8FC485-DA54-491B-B 57E-96DA2FE835FC@network-heretics.com>=0D=0A=20<34E4F50CA FA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.c om>=0D=0A=20<E9A8F486-2327-4F48-B21A-6155CF334F21@network -heretics.com>=0D=0A=20<4E554C78.9000504@gmail.com>=20<ts lr54a8v7s.fsf@mit.edu>=0D=0A=20<4E555B06.6000108@dcrocker .net>=20<tslmxey8sia.fsf@mit.edu>=0D=0A=20<4E555F6E.30601 05@bbiw.net>=0D=0A=20<CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbS p-g71d31j2fSee2w@mail.gmail.com>=0D=0A=20<2666D853-85D4-4 8CC-9321-0FBC2F8A3804@lucidvision.com>=0D=0A=20<008101cc6 33f$76a1b3a0$4001a8c0@gateway.2wire.net>=0D=0A=20<CAHBDyN 71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.c om>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Thu, =2025=20Aug=202011=2012:36:43=20-0700|To:=20Mary=20Barnes =20<mary.ietf.barnes@gmail.com>,=20t.petch=20<daedulus@bt connect.com>|From:=20Randall=20Gellens=20<randy@qualcomm. com>|Subject:=20Re:=20Hyatt=20Taipei=20cancellation=20pol icy?|CC:=20<ietf@ietf.org>,=20Sam=20Hartman=20<hartmans-i etf@mit.edu>,=20Dave=20CROCKER=0D=0A=09<dcrocker@bbiw.net >|MIME-Version:=201.0|Content-Type:=20text/plain=3B=20cha rset=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.39.5]; bh=j2+ONjuwRRhHmxnKKdHmyCmm2OwpzFGlu9v/erIVBPg=; b=Zx6sjPZpJLi+5GUB+gdlQMzkCQOgfjKI1h4iBEEc9+6KrHxUJYV8cpph FZ75uSH2vGJtH6bby9IIOzUsp1L6SPQeIqwNHjfQyKDuTvg2QiY3w97Fb VKSWyXE89veNML6PD1IPRxtQy3aaCGu7+vC0LN1g7zBSGAGoG+uCNAaO7 A=;
X-IronPort-AV: E=McAfee;i="5400,1158,6449"; a="112786339"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 25 Aug 2011 12:45:46 -0700
X-IronPort-AV: E=Sophos;i="4.68,281,1312182000"; d="scan'208";a="70519364"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 25 Aug 2011 12:45:46 -0700
Received: from 12-187-150-172.att-inc.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 25 Aug 2011 12:45:44 -0700
Message-ID: <p0624060fca7c54ac988d@12-187-150-172.att-inc.com>
In-Reply-To: <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 25 Aug 2011 12:36:43 -0700
To: Mary Barnes <mary.ietf.barnes@gmail.com>, t.petch <daedulus@btconnect.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Hyatt Taipei cancellation policy?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 19:44:33 -0000

At 12:12 PM -0500 8/25/11, Mary Barnes wrote:

>  I am also a fan of Minneapolis for meetings - the facilities at the 
> Hilton are perfect for our needs.  There's lots of food options. 
>  It has good air connections and there is decent pubic transport 
> from the airport to the city.

I fully agree.  Minneapolis works well for IETFs.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
wabi (wah-BI; Japanese; noun): a flawed detail that creates an
elegant whole.

From jdrake@juniper.net  Thu Aug 25 13:32:07 2011
Return-Path: <jdrake@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42F1E21F8BAB for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 13:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.116
X-Spam-Level: 
X-Spam-Status: No, score=-6.116 tagged_above=-999 required=5 tests=[AWL=0.483,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00hpqTOCB+ee for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 13:32:06 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1F121F8BAA for <ietf@ietf.org>; Thu, 25 Aug 2011 13:32:05 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTlaxj0iEKqqxEg9zV6UKh6vDrpK8viZq@postini.com; Thu, 25 Aug 2011 13:33:20 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Thu, 25 Aug 2011 11:20:29 -0700
From: John E Drake <jdrake@juniper.net>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 25 Aug 2011 11:20:27 -0700
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: AcxjUhERVa4b8xBDT3annEY5CX/2YAAAY7MQ
Message-ID: <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <4E568FA5.7020704@cisco.com>
In-Reply-To: <4E568FA5.7020704@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 20:32:07 -0000

How about Fresno?

Sent from my iPhone


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Stewart Bryant
> Sent: Thursday, August 25, 2011 11:09 AM
> To: ietf@ietf.org
> Subject: Re: Hyatt Taipei cancellation policy?
>=20
> On 25/08/2011 18:12, Mary Barnes wrote:
> > I am also a fan of Minneapolis for meetings - the facilities at the
> > Hilton are perfect for our needs.  There's lots of food options.  It
> > has good air connections and there is decent pubic transport from the
> > airport to the city.  However, this seems to be a minority
> > perspective. If we were to do votes again, the results might be
> > interesting.
> >
> > Mary.
>=20
> I like Minneapolis as well, but then, speaking personally, I like US
> IETF venues in general.
>=20
> Stewart
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From dougb@dougbarton.us  Thu Aug 25 13:35:52 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3BE21F8BA7 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 13:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.496
X-Spam-Level: 
X-Spam-Status: No, score=-3.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MxTmHX5KXAx for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 13:35:51 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 799C721F8BA4 for <ietf@ietf.org>; Thu, 25 Aug 2011 13:35:51 -0700 (PDT)
Received: (qmail 10594 invoked by uid 399); 25 Aug 2011 20:37:01 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Aug 2011 20:37:01 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4E56B26C.7040708@dougbarton.us>
Date: Thu, 25 Aug 2011 13:37:00 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <4E568FA5.7020704@cisco.com> <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.net>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 20:35:52 -0000

On 08/25/2011 11:20, John E Drake wrote:
> How about Fresno?

... just make sure it's upwind from the bovines. :)


-- 

	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 michal@krsek.cz  Thu Aug 25 13:41:58 2011
Return-Path: <michal@krsek.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5F8A21F8BC4 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 13:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.355
X-Spam-Level: 
X-Spam-Status: No, score=0.355 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DEAR_SOMETHING=1.605, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HY4EKI4Sm0Sy for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 13:41:58 -0700 (PDT)
Received: from io.pinknet.cz (io.pinknet.cz [217.31.57.96]) by ietfa.amsl.com (Postfix) with ESMTP id 0269121F8BA9 for <ietf@ietf.org>; Thu, 25 Aug 2011 13:41:58 -0700 (PDT)
Received: from [192.168.100.108] (ip-89-102-141-176.net.upcbroadband.cz [89.102.141.176]) by io.pinknet.cz (Postfix) with ESMTP id 9049E23B129 for <ietf@ietf.org>; Thu, 25 Aug 2011 22:43:09 +0200 (CEST)
Message-ID: <4E56B3DD.1030502@krsek.cz>
Date: Thu, 25 Aug 2011 22:43:09 +0200
From: Michal Krsek <michal@krsek.cz>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <4E568FA5.7020704@cisco.com> <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 20:41:59 -0000

Dear sirs,
I really appreciate your support to US venues, but please keep in mind, 
there are places eastern from Bermuda and western from Kauai. In 
addition there is also some land southern from El Paso.

Lets say - Internet is for everyone. And, trust me or not, there are 
people that have no budget for intercontinental travel and their input 
is  to the community work is valuable too.

Sorry for this social two cents in this engineering list.

             Regards
                 Michal Krsek

> How about Fresno?
>
> Sent from my iPhone
>
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Stewart Bryant
>> Sent: Thursday, August 25, 2011 11:09 AM
>> To: ietf@ietf.org
>> Subject: Re: Hyatt Taipei cancellation policy?
>>
>> On 25/08/2011 18:12, Mary Barnes wrote:
>>> I am also a fan of Minneapolis for meetings - the facilities at the
>>> Hilton are perfect for our needs.  There's lots of food options.  It
>>> has good air connections and there is decent pubic transport from the
>>> airport to the city.  However, this seems to be a minority
>>> perspective. If we were to do votes again, the results might be
>>> interesting.
>>>
>>> Mary.
>> I like Minneapolis as well, but then, speaking personally, I like US
>> IETF venues in general.
>>
>> Stewart
>>


From michel@arneill-py.sacramento.ca.us  Thu Aug 25 14:19:27 2011
Return-Path: <michel@arneill-py.sacramento.ca.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95C621F8C0F for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 14:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.083
X-Spam-Level: 
X-Spam-Status: No, score=-2.083 tagged_above=-999 required=5 tests=[AWL=0.182,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hH2eHxgsNIB0 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 14:19:27 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 73B1A21F8B9E for <ietf@ietf.org>; Thu, 25 Aug 2011 14:19:27 -0700 (PDT)
Subject: RE: Questionnaire to survey opinion concerning a possibleredefinition of UTC
Date: Thu, 25 Aug 2011 14:20:40 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF6AC@newserver.arneill-py.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <CAJNg7VJP4G7LUA86RUFBEvGGXHF73TtQ=tdurHG5iXFpq0AxJA@mail.gmail.com>
X-MS-Has-Attach: 
Content-class: urn:content-classes:message
X-MS-TNEF-Correlator: 
Thread-Topic: Questionnaire to survey opinion concerning a possibleredefinition of UTC
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Index: AcxjUaxPXEwGV6r9RR2J27OZ1BJ9vgAGmdwg
References: <20110825102401.GA10559@nic.fr><CAHhFybrv4xt7ZRvjZXUyTODoB8R3_yBUheZo-iOHr+Lnqo9mzA@mail.gmail.com> <CAJNg7VJP4G7LUA86RUFBEvGGXHF73TtQ=tdurHG5iXFpq0AxJA@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Marshall Eubanks" <marshall.eubanks@gmail.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 21:19:28 -0000

> Marshall Eubanks
> So UTC would become a=A0YATSCOT (Yet another time scale
> with a constant offset to TAI.)

Indeed, why not use TAI instead in the first place?


> I am not aware of any RFCs for sextant based celestial
> navigation (which WILL have to change).

If UTC was to change, that could mean some confusion for some sextant =
users I know who, before using their sextant, check their watch drift =
against the time provided by, ahem, their GPS receiver.

Michel.


From HKaplan@acmepacket.com  Thu Aug 25 15:31:15 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0B6E21F8B20 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 15:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.707
X-Spam-Level: 
X-Spam-Status: No, score=-1.707 tagged_above=-999 required=5 tests=[AWL=-0.713, BAYES_00=-2.599, DEAR_SOMETHING=1.605]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVH3oqfLDqlC for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 15:31:15 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 20D0721F8B18 for <ietf@ietf.org>; Thu, 25 Aug 2011 15:31:14 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 25 Aug 2011 18:32:23 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 25 Aug 2011 18:32:23 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Michal Krsek <michal@krsek.cz>
Date: Thu, 25 Aug 2011 18:32:20 -0400
Subject: Re: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: Acxjdtu0VUNs6gJqRU21nLVRyw29RA==
Message-ID: <60A89EDD-65F3-4795-8789-F035823E75BD@acmepacket.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <4E568FA5.7020704@cisco.com> <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.net> <4E56B3DD.1030502@krsek.cz>
In-Reply-To: <4E56B3DD.1030502@krsek.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAgAAAUAAAAFT
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 22:31:15 -0000

Don't worry - this thread occurs on a regular basis, and let's us vent our =
frustration at having an unsolvable problem.

But you do raise a good point about there being places west of Kauai.  In f=
act, my guess is every IETFer is either west or east of Kauai.  Therefore, =
I propose we hold a future meeting on Kauai.  The Marriott there can be had=
 for ~$220 in November; and although flights won't be cheap, they will be l=
ong so you get a lot more bang for your buck/euro/whatever.  The major down=
side is the sand may be too hot and there is a danger of falling coconuts.

-hadriel


On Aug 25, 2011, at 4:43 PM, Michal Krsek wrote:

> Dear sirs,
> I really appreciate your support to US venues, but please keep in mind,=20
> there are places eastern from Bermuda and western from Kauai. In=20
> addition there is also some land southern from El Paso.
>=20
> Lets say - Internet is for everyone. And, trust me or not, there are=20
> people that have no budget for intercontinental travel and their input=20
> is  to the community work is valuable too.
>=20
> Sorry for this social two cents in this engineering list.
>=20
>             Regards
>                 Michal Krsek
>=20


From marshall.eubanks@gmail.com  Thu Aug 25 16:06:09 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05A0021F8BBD for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 16:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.353
X-Spam-Level: 
X-Spam-Status: No, score=-102.353 tagged_above=-999 required=5 tests=[AWL=-0.360, BAYES_00=-2.599, DEAR_SOMETHING=1.605, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5WFA+VrKrAA for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 16:06:08 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5E89721F8B1C for <ietf@ietf.org>; Thu, 25 Aug 2011 16:06:08 -0700 (PDT)
Received: by gyf3 with SMTP id 3so2585150gyf.31 for <ietf@ietf.org>; Thu, 25 Aug 2011 16:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ndwyhcplCIAM/LKiRjM8UfNwIft5Fv7NnH2ZO09zdPg=; b=iG73hevtu+1HntS5AxxWzG5ys8kwejCCmqMc0sUZuqiLnaORyg6cL6NIzq+VM/HZqv JzXLTy4tX5OCsPQv/46CJimq8da0rIhgdF3Ds1yzZI5rmGVrlix0cGFAXqLdlIGSGLxC zkRcoLILQKNjrX08UVoen0Fkzj9THOZtbKors=
MIME-Version: 1.0
Received: by 10.150.11.9 with SMTP id 9mr1568696ybk.69.1314313642765; Thu, 25 Aug 2011 16:07:22 -0700 (PDT)
Received: by 10.150.202.16 with HTTP; Thu, 25 Aug 2011 16:07:22 -0700 (PDT)
In-Reply-To: <60A89EDD-65F3-4795-8789-F035823E75BD@acmepacket.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <4E568FA5.7020704@cisco.com> <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.net> <4E56B3DD.1030502@krsek.cz> <60A89EDD-65F3-4795-8789-F035823E75BD@acmepacket.com>
Date: Thu, 25 Aug 2011 19:07:22 -0400
Message-ID: <CAJNg7VL-H0igt_oj01YL=Nj1dSm_0efad=OM0hkDCYUBuADavQ@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: multipart/alternative; boundary=000e0cd6b286cced3504ab5c7ddc
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 23:06:09 -0000

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

On Thu, Aug 25, 2011 at 6:32 PM, Hadriel Kaplan <HKaplan@acmepacket.com>wrote:

>
> Don't worry - this thread occurs on a regular basis, and let's us vent our
> frustration at having an unsolvable problem.
>
> But you do raise a good point about there being places west of Kauai.  In
> fact, my guess is every IETFer is either west or east of Kauai.


There are a few in South Africa, the antipodes to Kauai, and thus neither
East or West (or both, depending on your preference).


>  Therefore, I propose we hold a future meeting on Kauai.  The Marriott
> there can be had for ~$220 in November; and although flights won't be cheap,
> they will be long so you get a lot more bang for your buck/euro/whatever.
>  The major downside is the sand may be too hot and there is a danger of
> falling coconuts.
>

Sound good to me.

Marshall


>
> -hadriel
>
>
> On Aug 25, 2011, at 4:43 PM, Michal Krsek wrote:
>
> > Dear sirs,
> > I really appreciate your support to US venues, but please keep in mind,
> > there are places eastern from Bermuda and western from Kauai. In
> > addition there is also some land southern from El Paso.
> >
> > Lets say - Internet is for everyone. And, trust me or not, there are
> > people that have no budget for intercontinental travel and their input
> > is  to the community work is valuable too.
> >
> > Sorry for this social two cents in this engineering list.
> >
> >             Regards
> >                 Michal Krsek
> >
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

<br><br><div class=3D"gmail_quote">On Thu, Aug 25, 2011 at 6:32 PM, Hadriel=
 Kaplan <span dir=3D"ltr">&lt;<a href=3D"mailto:HKaplan@acmepacket.com">HKa=
plan@acmepacket.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;=
">
<br>
Don&#39;t worry - this thread occurs on a regular basis, and let&#39;s us v=
ent our frustration at having an unsolvable problem.<br>
<br>
But you do raise a good point about there being places west of Kauai. =A0In=
 fact, my guess is every IETFer is either west or east of Kauai. </blockquo=
te><div><br></div><div>There are a few in South Africa, the antipodes to Ka=
uai, and thus neither East or West (or both, depending on your preference).=
=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">=A0Therefore, I propose we ho=
ld a future meeting on Kauai. =A0The Marriott there can be had for ~$220 in=
 November; and although flights won&#39;t be cheap, they will be long so yo=
u get a lot more bang for your buck/euro/whatever. =A0The major downside is=
 the sand may be too hot and there is a danger of falling coconuts.<br>
</blockquote><div><br></div><div>Sound good to me. </div><div><br></div><di=
v>Marshall</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color=3D"#888888"><br>
-hadriel<br>
</font><div class=3D"im"><br>
<br>
On Aug 25, 2011, at 4:43 PM, Michal Krsek wrote:<br>
<br>
&gt; Dear sirs,<br>
&gt; I really appreciate your support to US venues, but please keep in mind=
,<br>
&gt; there are places eastern from Bermuda and western from Kauai. In<br>
&gt; addition there is also some land southern from El Paso.<br>
&gt;<br>
&gt; Lets say - Internet is for everyone. And, trust me or not, there are<b=
r>
&gt; people that have no budget for intercontinental travel and their input=
<br>
&gt; is =A0to the community work is valuable too.<br>
&gt;<br>
&gt; Sorry for this social two cents in this engineering list.<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 Regards<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Michal Krsek<br>
&gt;<br>
<br>
</div><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>

--000e0cd6b286cced3504ab5c7ddc--

From prvs=0219b1420e=medel@globetel.com.ph  Thu Aug 25 18:05:32 2011
Return-Path: <prvs=0219b1420e=medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 728FF21F8B21 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 18:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.489
X-Spam-Level: 
X-Spam-Status: No, score=-1.489 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JIkWW8iglxw7 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 18:05:31 -0700 (PDT)
Received: from smtp01.globetel.com.ph (smtp01.globetel.com.ph [203.177.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 7A22121F8B17 for <ietf@ietf.org>; Thu, 25 Aug 2011 18:05:31 -0700 (PDT)
Received: from exgtbh01.globetel.com ([10.225.208.17]) by smtp01.globetel.com.ph (8.14.4/8.14.4) with ESMTP id p7Q16JhT023673;  Fri, 26 Aug 2011 09:06:19 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.145]) by exgtbh01.globetel.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 26 Aug 2011 09:05:40 +0800
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: voting system for future venues?
Date: Fri, 26 Aug 2011 09:05:39 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE1279E67A@EXVSGT02.globetel.com>
In-Reply-To: <alpine.OSX.2.01.1108250721310.21519@sjc-vpn5-137.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: voting system for future venues?
Thread-Index: AcxjM/hjshvxYbK6QcGyACRR7FNFSgAV8OHg
X-Priority: 1
Priority: Urgent
Importance: high
References: <20110822191708.652C721F8C19@ietfa.amsl.com><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com><4E5574AA.3030705@cs.tcd.ie><alpine.OSX.2.01.1108241505570.7436@sjc-vpn5-137.cisco.com><4E557A33.7050607@cs.tcd.ie><62B7EB93-3998-462C-BC2E-A960BB8F3603@bogus.com><4E559A18.3090005@cs.tcd.ie><6359ECD0-2F0C-471A-A112-0577FBD9A12F@bogus.com><4E55A126.90102@cs.tcd.ie><alpine.OSX.2.01.1108241841280.16097@sjc-vpn5-137.cisco.com><A5AD67DA1ACB9648831FD753485B2BFE1279DA32@EXVSGT02.globetel.com><alpine.OSX.2.01.11 08242012340.16097@sjc-vpn5-137.cisco.com><10493.1314282006@marajade.sandelman.ca> <alpine.OSX.2.01.1108250721310.21519@sjc-vpn5-137.cisco.com>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: "Ole Jacobsen" <ole@cisco.com>, "Michael Richardson" <mcr@sandelman.ca>
X-OriginalArrivalTime: 26 Aug 2011 01:05:40.0207 (UTC) FILETIME=[45A75FF0:01CC638C]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211, 0.0.0000 definitions=2011-08-26_01:2011-08-26, 2011-08-26, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1108250280
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 01:05:32 -0000

Ole,
We can actually arrange for a room block as long as we can guarantee
nth number of participants likewise room rates....

Regards
Medel Ramirez
Globe Telecom, Inc
Manila, Philippines
++++++++++++++++++++++++

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Ole Jacobsen
Sent: Thursday, August 25, 2011 10:33 PM
To: Michael Richardson
Cc: IETF-Discussion list
Subject: Re: voting system for future venues?


Michael,

I think we could expect a room block cost similar to that of APRICOT=20
2009, but the dollar has tanked since then so even "cheap" places in
Asia like this aren't so cheap any longer. And, yes, it would be "hard=20
go get to" for some value of hard. I wasn't proposing we go there.

As Nathaniel pointed out, some currencies have really risen against
the dollar. It isn't that long ago that the yen was well above 100
to the dollar (the mental calculation point), somewhere in the 110-120
range actually, but TODAY it is at 76-77 yen to the dollar.

So, a hotel room back then (the peak was July 2007 at 123 yen to the=20
dollar), say at 15,000 yen would cost ~ $121. Today that same room,=20
still at 15,000 yen will cost ~ $197, heck let's call it $200.

The Sing dollar and Oz dollar have done similar things, Canadian too=20
:-)

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Thu, 25 Aug 2011, Michael Richardson wrote:

>=20
> >>>>> "Ole" =3D=3D Ole Jacobsen <ole@cisco.com> writes:
>     Ole> The Sofitel Manila is where APRICOT 2009 was held. A great
>     Ole> venue, possibly even large enough to hold an IETF (I am not
>     Ole> sure), *and* the rate (at the time) at 7,525 Pesos was pretty
>     Ole> good. Today it is $177 which is still pretty good. The
question
>     Ole> is: would the IETF go to the Philippines for a meeting. It's
>     Ole> worth finding out.
>=20
> I can't find a flight that gets me there in less than 2 days from
> Canada.  I tried for November.  Most transit US (a -0.5 for me), many
> connect in Tokyo or Hong Kong or Seoul... hmm.  travel on Friday is
> easier than Saturday.  The price is about the same as I paid for
Prague.
> The cheapest connects in Guam, which I've always wanted to do.
>=20
> (Of course, the price to Tokyo or Hong Kong or Seoul will be higher..)
>=20
> But, what will the price be, once we get our "block"?
>=20
> --=20
> ]       He who is tired of Weird Al is tired of life!           |
firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net
architect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/
|device driver[
>    Kyoto Plus: watch the video
<http://www.youtube.com/watch?v=3Dkzx1ycLXQSE>
> 	               then sign the petition.=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

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From interfect@gmail.com  Thu Aug 25 18:56:38 2011
Return-Path: <interfect@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BEA221F86B3 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 18:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6YD4whOJyq-9 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 18:56:37 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id 991B821F86AF for <ietf@ietf.org>; Thu, 25 Aug 2011 18:56:37 -0700 (PDT)
Received: by qyk35 with SMTP id 35so1864400qyk.10 for <ietf@ietf.org>; Thu, 25 Aug 2011 18:57:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=KjKnQQ01abT+NeVfBGrrqcHMJQJVAT5a0ShOsUI8B3M=; b=bka9mybhc93JveKZFHcNDS5TQqar+0NhhU120UxVLUy0AocmNpwZEdSR6Hih2s8seK lyZ7Syg1SxCV7OZUxTpKkprOOMDJz5YjA9i5k9vI7TZFGWPjEJgGQTwJmXPG9QK+N6pG ckT3oWfApT90YzGAtF1F/J1YOxp7/4gu3B9To=
Received: by 10.229.10.216 with SMTP id q24mr696357qcq.0.1314323872063; Thu, 25 Aug 2011 18:57:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.84.146 with HTTP; Thu, 25 Aug 2011 18:57:32 -0700 (PDT)
From: Adam Novak <interfect@gmail.com>
Date: Thu, 25 Aug 2011 20:57:32 -0500
Message-ID: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
Subject: Routing at the Edges of the Internet
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 01:56:38 -0000

I trust that some of you have seen this article from a while back:

<http://moblog.wiredwings.com/archives/20110315/How-We-Killed-The-Internet-And-Nobody-Noticed.html>

An informative except:

"When I open my laptop, I see over ten different wifi access points.
Say I wanted to send data to my friend in the flat next to mine. It is
idiotic that nowadays, I would use the bottleneck subscriber line to
my upstream ISP and my crippled upload speed and push it all the way
across their infrastructure to my neighbors ISP and back to the Wifi
router in reach of mine. The Internet is not meant to be used that
way. Instead, all these wifi networks should be configured to talk to
each other."

I also trust that you are aware of what happened to the Internet in
Egypt (and elsewhere) this spring, where Internet connectivity was
disrupted by shutting down major ISP networks.

I would like to bring the attention of the IETF to what I see as a
fundamental problem with the current architecture of the Internet:

The Internet is not a network.

As part of the development of the Internet, fault-tolerant routing
protocols have been developed that allow a connecdestined fortion to
be maintained, even if the link that was carrying goes down, by
routing packets around the problem. Similarly, packets can be
load-balanced over multiple links for increased bandwidth. However,
the benefits of these technologies are not available to end users. If
I have a smartphone with both a 3G and a Wi-Fi connection, downloads
cannot currently be load-balanced across them. The two interfaces are
on two different networks, which are almost certainly part of two
different autonomous systems. Packets must be addressed to one of the
two interfaces, not the device, and packets addressed to one interface
have no way to be routed to the other. Similar problems arise when a
laptop has both a wired and a wireless connection. Wired networks also
suffer from related difficulties: If I have Verizon and my friend has
Comcast, and we string an Ethernet cable between our houses, packets
for me will still all come down my connection, and packets for my
friend will still all come down theirs.

The Internet, as it currently appears to end-users, has a logical tree
topology: computers connect to your home router, which connects to
your ISP, which connects to the rest of the Internet. Cell phones
connect to the tower, which connects through a backhaul link to the
rest of the Internet. Almost all of the devices involved have multiple
physical interfaces and full IP routing implementations, but only the
default route is ever used. This results in a brittle Internet: the
failure of one ISP router can disconnect a large number of end-users
from the Internet, as well as interrupting communication between those
users, even when those users are, physically, only a few feet from
each other.

My question is this: what IETF work would be needed to add more
routing to the edges of the Internet? If each home or mobile device
was essentially it's own autonomous system, what would this do to
routing table size? To ASN space utilization? How can individuals
interconnect home networks when RIRs do not assign address and AS
number resources to individuals? How might individuals interconnect
home networks without manual routing configuration? Under what
circumstances could an ISP trust a client's claim to have a route to
another client or to another ISP? How might packets sent to a device's
address on one network be routed to that device's address on another
network, while packets to immediately adjacent addresses take the
normal path?

From marshall.eubanks@gmail.com  Thu Aug 25 19:27:14 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E909521F85B9 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 19:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.151
X-Spam-Level: 
X-Spam-Status: No, score=-103.151 tagged_above=-999 required=5 tests=[AWL=0.447, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PvMOEbR02dPc for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 19:27:14 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9CB21F86FF for <ietf@ietf.org>; Thu, 25 Aug 2011 19:27:14 -0700 (PDT)
Received: by ywe9 with SMTP id 9so2722610ywe.31 for <ietf@ietf.org>; Thu, 25 Aug 2011 19:28:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EuQloQJI2+R/s/wEdROYMZ5T2yxab6IswPsNxs1n64A=; b=lBQiFvpW5KHFvUOLbaFQBjtR/OfC7D9lLma4N9jEL5XyoTmZCv1z6TzBBuDP9hO4ci t3PyP9IlRTEWlZISDLQMfwVMLJTDg8WY1YFRwSlmIykn2VTLKrRkPCJAylFnGtkkbr4L wOqexd2ycdE4oI/KzbB764lhQVZxuQmJgVZcM=
MIME-Version: 1.0
Received: by 10.150.7.2 with SMTP id 2mr102271ybg.69.1314325709136; Thu, 25 Aug 2011 19:28:29 -0700 (PDT)
Received: by 10.150.202.16 with HTTP; Thu, 25 Aug 2011 19:28:29 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF6AC@newserver.arneill-py.local>
References: <20110825102401.GA10559@nic.fr> <CAHhFybrv4xt7ZRvjZXUyTODoB8R3_yBUheZo-iOHr+Lnqo9mzA@mail.gmail.com> <CAJNg7VJP4G7LUA86RUFBEvGGXHF73TtQ=tdurHG5iXFpq0AxJA@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF6AC@newserver.arneill-py.local>
Date: Thu, 25 Aug 2011 22:28:29 -0400
Message-ID: <CAJNg7VJYfDippEgOV-iqNHg7LisFsa_nC5EAJjpWtrmWh6iDKA@mail.gmail.com>
Subject: Re: Questionnaire to survey opinion concerning a possibleredefinition of UTC
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=000e0cd24e8a0324be04ab5f4d9c
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 02:27:15 -0000

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

On Thu, Aug 25, 2011 at 5:20 PM, Michel Py <
michel@arneill-py.sacramento.ca.us> wrote:

> > Marshall Eubanks
> > So UTC would become a YATSCOT (Yet another time scale
> > with a constant offset to TAI.)
>
> Indeed, why not use TAI instead in the first place?
>

I have asked responsible parties about 2 of these cases (and, for that
matter, Dennis McCarthy about UT1) and the answer always is, too much
legacy equipment and software. That will sound quaint in 500 years.


>
>
> > I am not aware of any RFCs for sextant based celestial
> > navigation (which WILL have to change).
>
> If UTC was to change, that could mean some confusion for some sextant users
> I know who, before using their sextant, check their watch drift against the
> time provided by, ahem, their GPS receiver.
>
>
That is the reason for UTC, and the fact that they are getting it from GPS
is the reason why no one really cares about keeping UTC close to UT1.

Regards
Marshall


> Michel.
>
>

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

<br><br><div class=3D"gmail_quote">On Thu, Aug 25, 2011 at 5:20 PM, Michel =
Py <span dir=3D"ltr">&lt;<a href=3D"mailto:michel@arneill-py.sacramento.ca.=
us">michel@arneill-py.sacramento.ca.us</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex;">
&gt; Marshall Eubanks<br>
<div class=3D"im">&gt; So UTC would become a=A0YATSCOT (Yet another time sc=
ale<br>
&gt; with a constant offset to TAI.)<br>
<br>
</div>Indeed, why not use TAI instead in the first place?<br></blockquote><=
div><br></div><div>I have asked responsible parties about 2 of these cases =
(and, for that matter, Dennis McCarthy about UT1) and the answer always is,=
 too much</div>
<div>legacy equipment and software. That will sound quaint in 500 years.=A0=
</div><div>=A0</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"><br>
<br>
&gt; I am not aware of any RFCs for sextant based celestial<br>
&gt; navigation (which WILL have to change).<br>
<br>
</div>If UTC was to change, that could mean some confusion for some sextant=
 users I know who, before using their sextant, check their watch drift agai=
nst the time provided by, ahem, their GPS receiver.<br>
<font color=3D"#888888"><br></font></blockquote><div><br></div><div>That is=
 the reason for UTC, and the fact that they are getting it from GPS is the =
reason why no one really cares about keeping UTC close to UT1.</div><div>
<br></div><div>Regards</div><div>Marshall=A0</div><div>=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex;"><font color=3D"#888888">
Michel.<br>
<br>
</font></blockquote></div><br>

--000e0cd24e8a0324be04ab5f4d9c--

From dworley@avaya.com  Thu Aug 25 20:26:09 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C299A21F8A91 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 20:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.462
X-Spam-Level: 
X-Spam-Status: No, score=-103.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FN5N34CfQFO5 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 20:26:09 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA1E21F8532 for <ietf@ietf.org>; Thu, 25 Aug 2011 20:26:08 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAIARV06HCzI1/2dsb2JhbABDqBJ3gUABAQEBAxIGIi4REAIBCA0pEDIlAQEEAQ0NGqVBApwyhWxgBJhFi24
X-IronPort-AV: E=Sophos;i="4.68,283,1312171200"; d="scan'208";a="299987222"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 25 Aug 2011 23:27:22 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 25 Aug 2011 23:18:35 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 25 Aug 2011 23:27:06 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>, Michel Py <michel@arneill-py.sacramento.ca.us>
Date: Thu, 25 Aug 2011 23:25:12 -0400
Subject: RE: Questionnaire to survey opinion concerning a possibleredefinition	of UTC
Thread-Topic: Questionnaire to survey opinion concerning a possibleredefinition	of UTC
Thread-Index: AcxjmA0dqAWIZwiUSc2CkUFHG4L2dQAB7dfO
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F585E@DC-US1MBEX4.global.avaya.com>
References: <20110825102401.GA10559@nic.fr> <CAHhFybrv4xt7ZRvjZXUyTODoB8R3_yBUheZo-iOHr+Lnqo9mzA@mail.gmail.com> <CAJNg7VJP4G7LUA86RUFBEvGGXHF73TtQ=tdurHG5iXFpq0AxJA@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF6AC@newserver.arneill-py.local>, <CAJNg7VJYfDippEgOV-iqNHg7LisFsa_nC5EAJjpWtrmWh6iDKA@mail.gmail.com>
In-Reply-To: <CAJNg7VJYfDippEgOV-iqNHg7LisFsa_nC5EAJjpWtrmWh6iDKA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 03:26:09 -0000

>I have asked responsible parties about 2 of these cases (and,
> for that matter, Dennis McCarthy about UT1) and the answer always is, too=
 much
> legacy equipment and software. That will sound quaint in 500 years.

We're still using the 360-degree circle and the 24 (=3D12+12) hour day, and=
 those
go back to Babylon.

But my first thought was, We can't decide on how to decide on a conference =
location,
and people are asking us how to reform the world timing system?

Dale

From joelja@bogus.com  Thu Aug 25 20:52:31 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE29821F8AA9 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 20:52:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q67i9B2lI7NL for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 20:52:31 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 33BA621F8A91 for <ietf@ietf.org>; Thu, 25 Aug 2011 20:52:31 -0700 (PDT)
Received: from [192.168.43.44] (md20536d0.tmodns.net [208.54.5.210]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7Q3ravX089962 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 26 Aug 2011 03:53:38 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E5718BA.3050008@bogus.com>
Date: Thu, 25 Aug 2011 20:53:30 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Questionnaire to survey opinion concerning a possibleredefinition of UTC
References: <20110825102401.GA10559@nic.fr> <CAHhFybrv4xt7ZRvjZXUyTODoB8R3_yBUheZo-iOHr+Lnqo9mzA@mail.gmail.com> <CAJNg7VJP4G7LUA86RUFBEvGGXHF73TtQ=tdurHG5iXFpq0AxJA@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF6AC@newserver.arneill-py.local>, <CAJNg7VJYfDippEgOV-iqNHg7LisFsa_nC5EAJjpWtrmWh6iDKA@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F585E@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F585E@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 26 Aug 2011 03:53:38 +0000 (UTC)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 03:52:31 -0000

On 8/25/11 20:25 , Worley, Dale R (Dale) wrote:
>> I have asked responsible parties about 2 of these cases (and,
>> for that matter, Dennis McCarthy about UT1) and the answer always is, too much
>> legacy equipment and software. That will sound quaint in 500 years.
> 
> We're still using the 360-degree circle and the 24 (=12+12) hour day, and those
> go back to Babylon.
> 
> But my first thought was, We can't decide on how to decide on a conference location,

A different slant says we have some moderate trouble  deciding on a
location (we seem to meet 3 times a year), but that there will always be
someone unhappy with the outcome.

I think that's more plausibly congruent with what happens with global
timing systems.

> and people are asking us how to reform the world timing system?

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


From joelja@bogus.com  Thu Aug 25 21:01:49 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB2221F8AB8; Thu, 25 Aug 2011 21:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.331
X-Spam-Level: 
X-Spam-Status: No, score=-102.331 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mBD3gXQqJbLu; Thu, 25 Aug 2011 21:01:49 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 691A321F8AAF; Thu, 25 Aug 2011 21:01:49 -0700 (PDT)
Received: from [192.168.43.44] (md20536d0.tmodns.net [208.54.5.210]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7Q432HO090539 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 26 Aug 2011 04:03:04 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E571AF0.4080801@bogus.com>
Date: Thu, 25 Aug 2011 21:02:56 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>
Subject: Re: Agenda known in advance? was Re: Experiment for different schedule for Friday
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <1314094107.1965.16.camel@shane-desktop> <201108231025.p7NAPchW047526@bartok.nlnetlabs.nl>
In-Reply-To: <201108231025.p7NAPchW047526@bartok.nlnetlabs.nl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 26 Aug 2011 04:03:04 +0000 (UTC)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 04:01:50 -0000

On 8/23/11 03:25 , Jaap Akkerhuis wrote:
>     
>     If the idea of not fixing agendas is to remain, then any experiments for
>     extending the Friday schedule pretty much mean that everyone has to
>     extend their stay, doesn't it? I think if we want to use Friday time
>     properly, then this ideology needs to go.
>     
> Fully agree. We should consider Friday (morning) as yet another
> normal (.5) IETF day or not. 

The schedule for the last few meetings has in fact done that.
not-considering it normal would be a deviation from recent behavior.

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


From narten@us.ibm.com  Thu Aug 25 21:52:06 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2258821F8ACC for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 21:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.838
X-Spam-Level: 
X-Spam-Status: No, score=-105.838 tagged_above=-999 required=5 tests=[AWL=-0.728, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExHhGbYsOylQ for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 21:52:05 -0700 (PDT)
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by ietfa.amsl.com (Postfix) with ESMTP id 463E021F8ABC for <ietf@ietf.org>; Thu, 25 Aug 2011 21:52:04 -0700 (PDT)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e35.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7Q4X97r010789 for <ietf@ietf.org>; Thu, 25 Aug 2011 22:33:09 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7Q4r43a158848 for <ietf@ietf.org>; Thu, 25 Aug 2011 22:53:09 -0600
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 p7Q4r48T020690 for <ietf@ietf.org>; Thu, 25 Aug 2011 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7Q4r3mK020652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 25 Aug 2011 22:53:03 -0600
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 p7Q4r2hK004518 for <ietf@ietf.org>; Fri, 26 Aug 2011 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p7Q4r2U9004506 for ietf@ietf.org; Fri, 26 Aug 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201108260453.p7Q4r2U9004506@rotala.raleigh.ibm.com>
Date: Fri, 26 Aug 2011 00:53:02 -0400
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 04:52:06 -0000

Total of 245 messages in the last 7 days.
 
script run at: Fri Aug 26 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  0.41% |    1 | 14.22% |   319172 | nsb@guppylake.com
  5.31% |   13 |  4.08% |    91519 | ole@cisco.com
  2.04% |    5 |  4.82% |   108223 | stephen.farrell@cs.tcd.ie
  3.27% |    8 |  3.37% |    75750 | moore@network-heretics.com
  3.67% |    9 |  2.75% |    61675 | brian.e.carpenter@gmail.com
  3.27% |    8 |  3.01% |    67584 | sm@resistor.net
  2.45% |    6 |  3.54% |    79526 | wesley.george@twcable.com
  3.27% |    8 |  2.32% |    52198 | joelja@bogus.com
  3.27% |    8 |  2.32% |    51982 | glenzorn@gmail.com
  2.45% |    6 |  2.52% |    56515 | tnadeau@lucidvision.com
  2.86% |    7 |  1.86% |    41671 | hartmans-ietf@mit.edu
  2.45% |    6 |  2.09% |    46934 | randy@qualcomm.com
  2.04% |    5 |  2.30% |    51713 | tjc@ecs.soton.ac.uk
  2.45% |    6 |  1.74% |    39036 | john-ietf@jck.com
  1.63% |    4 |  2.41% |    54205 | acee.lindem@ericsson.com
  2.45% |    6 |  1.55% |    34700 | dworley@avaya.com
  1.63% |    4 |  1.71% |    38372 | marshall.eubanks@gmail.com
  2.04% |    5 |  1.22% |    27425 | hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com
  1.63% |    4 |  1.09% |    24529 | geoff@proto6.com
  1.63% |    4 |  1.05% |    23513 | ajs@anvilwalrusden.com
  1.63% |    4 |  1.04% |    23283 | geoff.ietf@mulligan.com
  1.63% |    4 |  1.03% |    23015 | melinda.shore@gmail.com
  0.82% |    2 |  1.78% |    40060 | lmartini@cisco.com
  1.22% |    3 |  1.23% |    27579 | david.black@emc.com
  1.22% |    3 |  1.18% |    26568 | medel@globetel.com.ph
  1.22% |    3 |  1.00% |    22535 | narten@us.ibm.com
  1.22% |    3 |  1.00% |    22458 | daedulus@btconnect.com
  1.22% |    3 |  0.92% |    20652 | fred@cisco.com
  1.22% |    3 |  0.87% |    19594 | rpelletier@isoc.org
  1.22% |    3 |  0.87% |    19469 | dhc@dcrocker.net
  1.22% |    3 |  0.85% |    18977 | mstjohns@comcast.net
  1.22% |    3 |  0.84% |    18826 | mcr@sandelman.ca
  1.22% |    3 |  0.79% |    17776 | dougb@dougbarton.us
  0.82% |    2 |  1.19% |    26740 | jdrake@juniper.net
  1.22% |    3 |  0.73% |    16441 | dcrocker@bbiw.net
  1.22% |    3 |  0.73% |    16327 | stpeter@stpeter.im
  0.82% |    2 |  0.96% |    21475 | mfberny@gmail.com
  0.82% |    2 |  0.92% |    20759 | venkatflex@gmail.com
  0.82% |    2 |  0.88% |    19847 | hkaplan@acmepacket.com
  0.82% |    2 |  0.76% |    16980 | jmabdp@gmail.com
  0.82% |    2 |  0.64% |    14426 | hsantos@santronics.com
  0.82% |    2 |  0.64% |    14403 | manav.bhatia@alcatel-lucent.com
  0.82% |    2 |  0.64% |    14346 | warren@kumari.net
  0.82% |    2 |  0.57% |    12787 | pk@isoc.de
  0.82% |    2 |  0.56% |    12618 | gareth.richards@rsa.com
  0.82% |    2 |  0.55% |    12415 | d3e3e3@gmail.com
  0.82% |    2 |  0.52% |    11721 | hotz@jpl.nasa.gov
  0.82% |    2 |  0.52% |    11622 | nomcom-chair@ietf.org
  0.82% |    2 |  0.51% |    11416 | shane@isc.org
  0.82% |    2 |  0.50% |    11286 | dhc2@dcrocker.net
  0.82% |    2 |  0.49% |    11006 | chair@ietf.org
  0.82% |    2 |  0.44% |     9955 | ben@nostrum.com
  0.82% |    2 |  0.44% |     9890 | michel@arneill-py.sacramento.ca.us
  0.82% |    2 |  0.42% |     9384 | alexey.melnikov@isode.com
  0.41% |    1 |  0.67% |    15005 | ron.even.tlv@gmail.com
  0.41% |    1 |  0.57% |    12737 | eburger@standardstrack.com
  0.41% |    1 |  0.56% |    12634 | eburger-l@standardstrack.com
  0.41% |    1 |  0.55% |    12369 | mary.ietf.barnes@gmail.com
  0.41% |    1 |  0.47% |    10551 | hgs@cs.columbia.edu
  0.41% |    1 |  0.45% |    10039 | presnick@qualcomm.com
  0.41% |    1 |  0.43% |     9760 | koike.yoshinori@lab.ntt.co.jp
  0.41% |    1 |  0.41% |     9145 | anshumanpratap@gmail.com
  0.41% |    1 |  0.39% |     8756 | mach.chen@huawei.com
  0.41% |    1 |  0.37% |     8293 | c-sai@bx.jp.nec.com
  0.41% |    1 |  0.36% |     8191 | erosen@cisco.com
  0.41% |    1 |  0.35% |     7925 | interfect@gmail.com
  0.41% |    1 |  0.35% |     7855 | c.donley@cablelabs.com
  0.41% |    1 |  0.35% |     7808 | henk.uijterwaal@gmail.com
  0.41% |    1 |  0.34% |     7704 | akatlas@gmail.com
  0.41% |    1 |  0.34% |     7689 | lberger@labn.net
  0.41% |    1 |  0.33% |     7425 | henk@uijterwaal.nl
  0.41% |    1 |  0.32% |     7228 | kathleen.moriarty@emc.com
  0.41% |    1 |  0.32% |     7149 | bortzmeyer@nic.fr
  0.41% |    1 |  0.31% |     7031 | christer.holmberg@ericsson.com
  0.41% |    1 |  0.31% |     6913 | ghudson@mit.edu
  0.41% |    1 |  0.31% |     6898 | tglassey@certichron.com
  0.41% |    1 |  0.31% |     6859 | steve@shinkuro.com
  0.41% |    1 |  0.30% |     6803 | michal@krsek.cz
  0.41% |    1 |  0.30% |     6700 | ned+ietf@mauve.mrochek.com
  0.41% |    1 |  0.29% |     6536 | dwm@xpasc.com
  0.41% |    1 |  0.29% |     6408 | stbryant@cisco.com
  0.41% |    1 |  0.28% |     6330 | chris.newman@oracle.com
  0.41% |    1 |  0.27% |     6007 | agmalis@gmail.com
  0.41% |    1 |  0.26% |     5745 | jmpolk@cisco.com
  0.41% |    1 |  0.25% |     5725 | scott.brim@gmail.com
  0.41% |    1 |  0.25% |     5683 | lear@cisco.com
  0.41% |    1 |  0.25% |     5502 | sm+ietf@elandsys.com
  0.41% |    1 |  0.24% |     5299 | lixia@cs.ucla.edu
  0.41% |    1 |  0.23% |     5137 | jason_livingood@cable.comcast.com
  0.41% |    1 |  0.22% |     4976 | julian.reschke@gmx.de
  0.41% |    1 |  0.22% |     4888 | mohta@necom830.hpcl.titech.ac.jp
  0.41% |    1 |  0.21% |     4708 | jaap@nlnetlabs.nl
--------+------+--------+----------+------------------------
100.00% |  245 |100.00% |  2245289 | Total

From johnl@iecc.com  Thu Aug 25 22:46:16 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D00121F8853 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 22:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.079
X-Spam-Level: 
X-Spam-Status: No, score=-111.079 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lltFnbeeQ8CD for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 22:46:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 22FC521F8841 for <ietf@ietf.org>; Thu, 25 Aug 2011 22:46:13 -0700 (PDT)
Received: (qmail 26070 invoked from network); 26 Aug 2011 05:47:28 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 26 Aug 2011 05:47:28 -0000
Received: (qmail 42163 invoked from network); 26 Aug 2011 05:47:28 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 26 Aug 2011 05:47:28 -0000
Date: 26 Aug 2011 05:47:06 -0000
Message-ID: <20110826054706.93654.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Manila, was voting system for future venues?
In-Reply-To: <10493.1314282006@marajade.sandelman.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 05:46:16 -0000

>I can't find a flight that gets me there in less than 2 days from
>Canada.  I tried for November.

Um, you can fly YYZ-NRT/NRT-MNL on AC and NH in about 20 hrs.  The
return flight is about 18 hrs, same route.  Any chance we've forgotten
about the International Date Line?  I see coach fares of about $1200
which is not bad for such a long trip.

>From YOW, it's not surprisingly 2-3 hrs more with another connection,
but there's a reasonable route on DL via Detroit and Nagoya for only
$917, 22 hrs out, 21 hrs back.

R's,
John

From henk.uijterwaal@gmail.com  Thu Aug 25 23:21:48 2011
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1983621F8432 for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 23:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.878
X-Spam-Level: 
X-Spam-Status: No, score=-2.878 tagged_above=-999 required=5 tests=[AWL=-0.571, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ergow-u++e8P for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 23:21:47 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7907A21F8AFF for <ietf@ietf.org>; Thu, 25 Aug 2011 23:21:40 -0700 (PDT)
Received: by ewy19 with SMTP id 19so1435093ewy.31 for <ietf@ietf.org>; Thu, 25 Aug 2011 23:22:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=QW+cTrMAW//qDF6ekRQkKo0LEZjMQ2aPwgTJrxge9XA=; b=Boe7HjhDBdBYk/SpONr/vso6EQexfLRffw2oXCDJbjiPxKiIeMh/7t8jOPqUKRYjP6 67vi0BpzdyToIDvNEhefVx95Txj4RqwdsI7tEG3XoqR8uVCWSjUWzb4OS+fYnpUNQvpA llT8VTQ1Z96u99rGmRqodJkAsHzyx7GJ0JJ1A=
Received: by 10.14.20.11 with SMTP id o11mr243318eeo.186.1314339768608; Thu, 25 Aug 2011 23:22:48 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) by mx.google.com with ESMTPS id 72sm844968eee.52.2011.08.25.23.22.47 (version=SSLv3 cipher=OTHER); Thu, 25 Aug 2011 23:22:47 -0700 (PDT)
Message-ID: <4E573BB6.5000700@gmail.com>
Date: Fri, 26 Aug 2011 08:22:46 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <1314226999.1973.211.camel@d430>
In-Reply-To: <1314226999.1973.211.camel@d430>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 06:21:48 -0000

On 25/08/2011 01:03, geoff wrote:
> On Wed, 2011-08-24 at 15:28 -0400, Sam Hartman wrote:
>> 1) We don't have to go to any particular location.  There has been an
>> assumption made by people in this discussion that sometimes when we pick
>> locations with particularly expensive hotels, we'll get particularly
>> expensive meetings.  That's great except that we were the ones who chose
>> to go to those locations.
>> If we can't meet our cost targets at a location, go somewhere else.

> Sam makes a really good point here.  We didn't have to go to Taipei.
> For some reason we chose to go to Taipei. 

Not quite.  There is a requirement to have meetings all over the world,
in a ratio of 1:1:1 for Europe, North America and Asia.  Considering
that we have to go to Asia, Taipei looks like a sensible choice: it
is in the middle of the region, it well connected, and it is one of
the bigger economies in the region.

I have a feeling that if we dropped this requirement and went for a
0:3:0 schedule because it is much cheaper for the US participants to
go to M'polis 3 times/year, somebody else would complain.

> The hotel (and
> host if there was on) could/should have been told - 
> sorry too expensive.

I've lost track what has been officially announced, but in one of the
future years, the 1:1:1 requirement has been dropped as there was no
suitable venue in one of the areas.

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From bortzmeyer@nic.fr  Thu Aug 25 23:58:52 2011
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCD421F8B1E for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 23:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level: 
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6914SjjhqbhO for <ietf@ietfa.amsl.com>; Thu, 25 Aug 2011 23:58:50 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by ietfa.amsl.com (Postfix) with ESMTP id 97C8821F8772 for <ietf@ietf.org>; Thu, 25 Aug 2011 23:58:50 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 4EB791C0B03 for <ietf@ietf.org>; Fri, 26 Aug 2011 09:00:05 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 499ED1C0AFF for <ietf@ietf.org>; Fri, 26 Aug 2011 09:00:05 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.6.69]) by relay1.nic.fr (Postfix) with ESMTP id 3BBE2568124 for <ietf@ietf.org>; Fri, 26 Aug 2011 09:00:05 +0200 (CEST)
Date: Fri, 26 Aug 2011 09:00:05 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: Questionnaire to survey opinion concerning a possible redefinition 	of UTC
Message-ID: <20110826070005.GA28404@nic.fr>
References: <20110825102401.GA10559@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110825102401.GA10559@nic.fr>
X-Operating-System: Debian GNU/Linux 6.0.2
X-Kernel: Linux 2.6.32-5-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 06:58:52 -0000

On Thu, Aug 25, 2011 at 12:24:01PM +0200,
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
 a message of 59 lines which said:

> Since several RFCs rely on UTC and leap seconds (3339, 4765, 5905,
> etc), this questionnaire may be of interest for some persons [the Web
> page mentions two articles, if you are in a hurry, the first one is
> the PRO and the second one the CON]. One more week to comment.
> 
> http://hpiers.obspm.fr/eop-pc/index.php?index=questionnaire

I have also been directed at this meeting in october in Exton, PA,
USA, where the organizers would be glad to have input from people
involved in software and computer networks:

http://futureofutc.org/

From HKaplan@acmepacket.com  Fri Aug 26 00:23:23 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75C8921F8B2A; Fri, 26 Aug 2011 00:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRvA9xz2Svbx; Fri, 26 Aug 2011 00:23:23 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id CE04F21F8B23; Fri, 26 Aug 2011 00:23:22 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 26 Aug 2011 03:24:37 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Fri, 26 Aug 2011 03:24:37 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: IETF Chair <chair@ietf.org>
Date: Fri, 26 Aug 2011 03:24:35 -0400
Subject: Re: Experiment for different schedule for Friday
Thread-Topic: Experiment for different schedule for Friday
Thread-Index: AcxjwTXeFTAnXPWvRci37ZO//gKPgw==
Message-ID: <AF3F3E2B-4E50-4B4D-909B-BB83BAE48AAB@acmepacket.com>
References: <0E41725E-77C3-4DEF-BEE7-8220623B4AE9@ietf.org> <4E533D39.5070606@cisco.com> <DC351D99C7573A54509F777F@PST.JCK.COM>
In-Reply-To: <DC351D99C7573A54509F777F@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
X-Brightmail-Tracker: AAAAAgAAAUAAAAFQ
Cc: IETF <ietf@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 07:23:23 -0000

+1

-hadriel

On Aug 23, 2011, at 2:04 AM, John C Klensin wrote:

> +1.  I could also happily live with the alternate, more
> compressed, schedule -- I think both are preferable to the
> schedule used in Quebec and earlier.
>=20
>   john
>=20
>=20
> --On Tuesday, August 23, 2011 07:40 +0200 Eliot Lear
> <lear@cisco.com> wrote:
>=20
>>=20
>>=20
>> On 8/22/11 11:24 PM, IETF Chair wrote:
>>> The IESG is considering a different schedule for the Friday
>>> of IETF 82.  The IESG is seeking your input on these
>>> potential changes.
>>>=20
>>> The IESG would like to try a schedule experiment on Friday,
>>> using this schedule:
>>>=20
>>> 9:00 AM - 11:00 AM - Session I
>>> 11:00 AM - 11:20 AM - Room Change and Cookie Break
>>> 11:20 AM - 12:20 PM - Session II
>>> 12:10 PM - 12:30 PM - Room Change Break
>>> 12:30 PM - 13:30 PM - Session III
>>>=20
>>> The IESG has already consulted with the IAOC because of the
>>> cost associated with the additional food and beverage break.
>>> The IAOC believes that the additional cost can be managed
>>> without raising the meeting fee.
>>=20
>> I think this is a good experiment to run as proposed.
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From daedulus@btconnect.com  Fri Aug 26 01:22:26 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D5F21F8B15 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 01:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.721
X-Spam-Level: 
X-Spam-Status: No, score=-0.721 tagged_above=-999 required=5 tests=[AWL=-1.273, BAYES_20=-0.74, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d61V7k2VzUR5 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 01:22:25 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id 57A0021F84E5 for <ietf@ietf.org>; Fri, 26 Aug 2011 01:22:24 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr08.btconnect.com with SMTP id EBM03174; Fri, 26 Aug 2011 09:22:29 +0100 (BST)
Message-ID: <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
Cc: "IETF Discussion" <ietf@ietf.org>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>
Subject: https
Date: Fri, 26 Aug 2011 09:18:41 +0200
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.4E5757C4.015B, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.26.74214:17:7.944, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, SUBJ_1WORD, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, MISSING_HEADERS, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_300_399, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, __PHISH_SPEAR_STRUCTURE_1, BODY_SIZE_1000_LESS, RDNS_SUSP, BODY_SIZE_2000_LESS, __PHISH_SPEAR_STRUCTURE_2, BODY_SIZE_7000_LESS, TO_MALFORMED, NO_URI_FOUND
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4E57580A.0145,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 08:22:26 -0000

Why does the IETF website consider it necessary to use TLS to access the mailing
list archives, when they all appeared without it, or any other security, in the
first place?

Besides all the usual hassle of TLS, today the certificate is reported by IE as
expired, which sort of sums it up.

Tom Petch


From ole@cisco.com  Fri Aug 26 01:47:45 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D74F21F8B0D for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 01:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.79
X-Spam-Level: 
X-Spam-Status: No, score=-101.79 tagged_above=-999 required=5 tests=[AWL=-0.796, BAYES_00=-2.599, DEAR_SOMETHING=1.605, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PHIhWfzmeOuB for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 01:47:45 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 0258F21F8B0A for <ietf@ietf.org>; Fri, 26 Aug 2011 01:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1921; q=dns/txt; s=iport; t=1314348541; x=1315558141; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=fXbbvckIv0seM2Uh0SQV8gm7I7DNHQ9bIfvSufE/gc8=; b=KVyQ60td2HynON4JWv+NHfjgSXPWIGEKXsE4KA+y0sT6O4mUb4JqHfqn 0xe1G2QWAzuMHKFUBXgB815I/SbWmRAZwVOJyavsdzfgOP5oQyVp6UoRA whT/unVLkILvhp2oG0Ztdfi9jMHSztkw+r0Ar33PqFIUW88JEGhXLj6Kw 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArIAACVdV06rRDoI/2dsb2JhbAA/A5g7j1l3gUABAQEBAgEBAQEPAQIBJDQLBQcECxEEAQEBJwcnHwkIBhMUDodQBJtIAYMjDwGbW4NCgwoEh2KGCo8mhyU
X-IronPort-AV: E=Sophos;i="4.68,284,1312156800"; d="scan'208";a="16719741"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-4.cisco.com with ESMTP; 26 Aug 2011 08:49:00 +0000
Received: from sjc-vpn6-1246.cisco.com (sjc-vpn6-1246.cisco.com [10.21.124.222]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7Q8mxaB019423; Fri, 26 Aug 2011 08:49:00 GMT
Date: Fri, 26 Aug 2011 01:48:59 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Michal Krsek <michal@krsek.cz>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <4E56B3DD.1030502@krsek.cz>
Message-ID: <alpine.OSX.2.01.1108260148430.39308@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <4E555F6E.3060105@bbiw.net> <CAG4d1rdGzxVwR6RYBBzG9CBa6Vk+_cKjbSp-g71d31j2fSee2w@mail.gmail.com> <2666D853-85D4-48CC-9321-0FBC2F8A3804@lucidvision.com> <008101cc633f$76a1b3a0$4001a8c0@gateway.2wire.net> <CAHBDyN71JgeuCgaxoLmjpFuHpR8ONVxhr2cm2Atp_CR99HnfkQ@mail.gmail.com> <4E568FA5.7020704@cisco.com> <5E893DB832F57341992548CDBB333163A0AD091268@EMBX01-HQ.jnpr.net> <4E56B3DD.1030502@krsek.cz>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 08:47:45 -0000

That's why we've met TWICE in your city!


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Thu, 25 Aug 2011, Michal Krsek wrote:

> Dear sirs,
> I really appreciate your support to US venues, but please keep in mind, there
> are places eastern from Bermuda and western from Kauai. In addition there is
> also some land southern from El Paso.
> 
> Lets say - Internet is for everyone. And, trust me or not, there are people
> that have no budget for intercontinental travel and their input is  to the
> community work is valuable too.
> 
> Sorry for this social two cents in this engineering list.
> 
>             Regards
>                 Michal Krsek
> 
> > How about Fresno?
> >
> > Sent from my iPhone
> >
> >
> > > -----Original Message-----
> > > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > > Stewart Bryant
> > > Sent: Thursday, August 25, 2011 11:09 AM
> > > To: ietf@ietf.org
> > > Subject: Re: Hyatt Taipei cancellation policy?
> > >
> > > On 25/08/2011 18:12, Mary Barnes wrote:
> > > > I am also a fan of Minneapolis for meetings - the facilities at the
> > > > Hilton are perfect for our needs.  There's lots of food options.  It
> > > > has good air connections and there is decent pubic transport from the
> > > > airport to the city.  However, this seems to be a minority
> > > > perspective. If we were to do votes again, the results might be
> > > > interesting.
> > > >
> > > > Mary.
> > > I like Minneapolis as well, but then, speaking personally, I like US
> > > IETF venues in general.
> > >
> > > Stewart
> > >
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From sm@resistor.net  Fri Aug 26 02:31:13 2011
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E031A21F8B05 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 02:31:13 -0700 (PDT)
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.273, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0aO-QbHc6GoE for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 02:31:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0D421F8509 for <ietf@ietf.org>; Fri, 26 Aug 2011 02:31:11 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p7Q9WKTG014069; Fri, 26 Aug 2011 02:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1314351145; bh=jYW7JZKo8jZiMt3mCZZuclBm4c5TgbQ31zXXW7/JWIw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=gEtTy/cDggACUbAWm2P1RvgLYdYG/xtaO35A933wyAi18Axs5tBYGF4IaY1GfFGiE pskmkdGQjqfxWfssXA0LDxKbAr+98QPL05O5kR9qScuSpHftzAfIGs/IRjS4RtiZT/ yvqZsgr9c1NqiXMdMSm5uQthGuO/C8mAbqLquQ3Q=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1314351145; bh=jYW7JZKo8jZiMt3mCZZuclBm4c5TgbQ31zXXW7/JWIw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=nau2sG5sFlKEVEi+n/b/IvbVFDJg92j8IbWRBxO1qXM+irDadS5sMzWY399+D1LdW XrF7nmADmKaZU0YU2Sdq8NY6rOL9NGxY/Z4AqA3buwWKncmm9nDjEe58I3AAo2RhJU xWGy6cYGhsZi0pR1/vhYSA5Amj+kE5mkSojrzgkU=
Message-Id: <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 26 Aug 2011 02:32:13 -0700
To: "t.petch" <daedulus@btconnect.com>
From: SM <sm@resistor.net>
Subject: Re: https
In-Reply-To: <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 09:31:14 -0000

Hi Tom,
At 00:18 26-08-2011, t.petch wrote:
>Besides all the usual hassle of TLS, today the certificate is 
>reported by IE as
>expired, which sort of sums it up.

Already reported to ietf-action@.

Regards,
-sm

P.S. My experience of ietf-action@ is that they are responsive and do 
fix problems that are reported. 


From daedulus@btconnect.com  Fri Aug 26 02:42:25 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF60021F8B27 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 02:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.891
X-Spam-Level: 
X-Spam-Status: No, score=-1.891 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZDf06TFBnFx for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 02:42:25 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id 13CF221F85C6 for <ietf@ietf.org>; Fri, 26 Aug 2011 02:42:24 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr08.btconnect.com with SMTP id EBM92554; Fri, 26 Aug 2011 10:43:25 +0100 (BST)
Message-ID: <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "SM" <sm@resistor.net>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>
Subject: Re: https
Date: Fri, 26 Aug 2011 10:39:39 +0200
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.4E576ABC.0048, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.26.84514:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_800_899, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, BODY_SIZE_1000_LESS, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4E576ABD.0137,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 09:42:26 -0000

----- Original Message -----
From: "SM" <sm@resistor.net>
To: "t.petch" <daedulus@btconnect.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Subject: Re: https


> Hi Tom,
> At 00:18 26-08-2011, t.petch wrote:
> >Besides all the usual hassle of TLS, today the certificate is
> >reported by IE as
> >expired, which sort of sums it up.
>
> Already reported to ietf-action@.
>
> Regards,
> -sm
>
> P.S. My experience of ietf-action@ is that they are responsive and do
> fix problems that are reported.

Yup, but why are we using https at all?  Who decided, and please would they
undecide?  Unexpired certificates can be circumvented, but all too often, the
https parts of the web site just do not work and, more importantly, I think it
wrong to use industrial grade security where none is called for.

Tom Petch


>


From bertietf@bwijnen.net  Fri Aug 26 03:11:26 2011
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399E121F8B28 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 03:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.017
X-Spam-Level: 
X-Spam-Status: No, score=-99.017 tagged_above=-999 required=5 tests=[AWL=-1.114, BAYES_50=0.001, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f7OsG0eWQTXW for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 03:11:24 -0700 (PDT)
Received: from relay61.tele2.vuurwerk.nl (relay61.tele2.vuurwerk.nl [62.250.3.61]) by ietfa.amsl.com (Postfix) with ESMTP id 9008021F8B27 for <ietf@ietf.org>; Fri, 26 Aug 2011 03:11:21 -0700 (PDT)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.indetel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1QwtOt-0007Y3-CE; Fri, 26 Aug 2011 12:12:35 +0200
Message-ID: <60F6029C4B324BFB858FB5553DDA017D@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "t.petch" <daedulus@btconnect.com>, "SM" <sm@resistor.net>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net><4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv><001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net><6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>
In-Reply-To: <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>
Subject: Re: https
Date: Fri, 26 Aug 2011 12:12:26 +0200
Organization: Consultant
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 Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 10:11:26 -0000

> Yup, but why are we using https at all?  Who decided, and please would they
> undecide?  Unexpired certificates can be circumvented, but all too often, the
> https parts of the web site just do not work and, more importantly, I think it
> wrong to use industrial grade security where none is called for.
>

I agree with Tom here. In my understanding, all IETF communications
and (mailing list) discussions are open and public.
So why do we need to protect/encrypt?

I would say: protect what must be protected
                   but don't protect what is not supposed to be protected.

just encrypting everything seems incorrect to me.

Bert

> Tom Petch


From lear@cisco.com  Fri Aug 26 03:23:35 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1596A21F8B0C for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 03:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.595
X-Spam-Level: 
X-Spam-Status: No, score=-110.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HEZ9uAMrLK1r for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 03:23:34 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1A35D21F8B06 for <ietf@ietf.org>; Fri, 26 Aug 2011 03:23:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=740; q=dns/txt; s=iport; t=1314354290; x=1315563890; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=0Kk+quXvSq2D08+VOYymUxIpWCnu65daynRAtEpl6Mg=; b=Ebsytg4XQ1d5N5ZDD3bJk1LcewwzzQGAVtINF5P0nUXFziJC3Mx7Pe8Z dYBIkmscemKpZV8n17JWAiFlYM91qOPFu243Yeio46lL4I/Fj55XTwtRN YSXHX5t4wQM06IeTzUGsEQlaoFQHQx8MQTzR98QlDDDumLYPrtI0EP7cP U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAB10V06Q/khL/2dsb2JhbABChEyjTHeBQAEBAQEDEgEQVQEQCxoCBRYLAgIJAwIBAgFFBg0BBwEBEA6jTgGNNpFagSyED4ERBJMakQI
X-IronPort-AV: E=Sophos;i="4.68,284,1312156800"; d="scan'208";a="112585043"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 26 Aug 2011 10:24:46 +0000
Received: from dhcp-10-55-92-189.cisco.com (dhcp-10-55-92-189.cisco.com [10.55.92.189]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7QAOkpZ004450; Fri, 26 Aug 2011 10:24:46 GMT
Message-ID: <4E57743F.6030807@cisco.com>
Date: Fri, 26 Aug 2011 12:23:59 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net><4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv><001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net><6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <60F6029C4B324BFB858FB5553DDA017D@BertLaptop>
In-Reply-To: <60F6029C4B324BFB858FB5553DDA017D@BertLaptop>
X-Enigmail-Version: 1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 10:23:35 -0000

Bert, Tom,


I don't see this as being a matter of encrypting, but rather providing
verifiable information the community.  What's more, in as much as the
IETF is a trusted site by many, it's probably a good idea to have at
least some confidence that when you click on a link, you're not going to
get hacked.  Finally, the IETF designed this system, and if we don't
like the fragility, perhaps we should fix it.  There's a saying about
eating one's own dogfood.  After all, if we won't eat ours, why should
anyone else?

By the way, Tom, you're not quite right.  Mail sent out from the IETF
list (including this one and the one you sent to the list) is signed by
the IETF with DKIM.  Again, eating our own dogfood.

Eliot

From i.grok@comcast.net  Fri Aug 26 03:49:26 2011
Return-Path: <i.grok@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 524FA21F8B44 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 03:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.331
X-Spam-Level: 
X-Spam-Status: No, score=-102.331 tagged_above=-999 required=5 tests=[AWL=-0.332, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJ5e0hkIJ-pR for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 03:49:26 -0700 (PDT)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by ietfa.amsl.com (Postfix) with ESMTP id EF23121F8B40 for <ietf@ietf.org>; Fri, 26 Aug 2011 03:49:25 -0700 (PDT)
Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta01.emeryville.ca.mail.comcast.net with comcast id QykF1h0010x6nqcA1yqddH; Fri, 26 Aug 2011 10:50:37 +0000
Received: from odin.ulthar.us ([68.33.77.0]) by omta12.emeryville.ca.mail.comcast.net with comcast id Qyqc1h00T00PQ6U8YyqdRH; Fri, 26 Aug 2011 10:50:37 +0000
Received: from odin.ulthar.us (localhost [127.0.0.1]) by odin.ulthar.us (8.14.4/8.14.3) with ESMTP id p7QAodhG015167 for <ietf@ietf.org>; Fri, 26 Aug 2011 06:50:39 -0400
Received: (from draco@localhost) by odin.ulthar.us (8.14.4/8.14.4/Submit) id p7QAoc47015165 for ietf@ietf.org; Fri, 26 Aug 2011 06:50:38 -0400
Date: Fri, 26 Aug 2011 06:50:38 -0400
From: Scott Schmit <i.grok@comcast.net>
To: ietf@ietf.org
Subject: Re: https
Message-ID: <20110826105038.GA15033@odin.ulthar.us>
Mail-Followup-To: ietf@ietf.org
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 10:49:26 -0000

On Fri, Aug 26, 2011 at 09:18:41AM +0200, t.petch wrote:
> Why does the IETF website consider it necessary to use TLS to access
> the mailing list archives, when they all appeared without it, or any
> other security, in the first place?

TLS provides more than confidentiality--it also provides authenticity.
If I were living in a hostile regime, I'd appreciate knowing that the
RFCs, etc that I'm getting really come from the IETF unmodified.

Also, as a general principle, I'd rather someone not be able to read
over my shoulder, even if it is harmless stuff. Using encryption only
when I need it makes all of my encrypted traffic less secure.

For example, if I were out to modify the traffic you read to make sure
that you didn't even know that a working group existed, I'd have a lot
easier time of it if you use DNS without DNSSEC, HTTP without TLS, TLS
without HASTLS, DANE, HSTS, etc. Now, not all of that is completed
protocol work, but one step at a time.

> Besides all the usual hassle of TLS, today the certificate is reported
> by IE as expired, which sort of sums it up.

Mistakes happen. Hopefully lessons are learned so that they don't get
repeated.

If it's a protocol problem, whose fault is that but ours?

-- 
Scott Schmit

From narten@us.ibm.com  Fri Aug 26 04:05:52 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C48821F85C6 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 04:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.802
X-Spam-Level: 
X-Spam-Status: No, score=-105.802 tagged_above=-999 required=5 tests=[AWL=0.797, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCrv0QROmRtB for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 04:05:52 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 0157B21F8562 for <ietf@ietf.org>; Fri, 26 Aug 2011 04:05:51 -0700 (PDT)
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7QApf5f019908 for <ietf@ietf.org>; Fri, 26 Aug 2011 04:51:41 -0600
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7QB6von149212 for <ietf@ietf.org>; Fri, 26 Aug 2011 05:06:57 -0600
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 p7Q56uYo019160 for <ietf@ietf.org>; Thu, 25 Aug 2011 23:06:57 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-152-187.mts.ibm.com [9.49.152.187]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7Q56tKc019112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Aug 2011 23:06:56 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7QB6sXZ031100; Fri, 26 Aug 2011 07:06:55 -0400
Message-Id: <201108261106.p7QB6sXZ031100@cichlid.raleigh.ibm.com>
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: https
In-reply-to: <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
Comments: In-reply-to "t.petch" <daedulus@btconnect.com> message dated "Fri, 26 Aug 2011 09:18:41 +0200."
Date: Fri, 26 Aug 2011 07:06:54 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 11:05:52 -0000

"t.petch" <daedulus@btconnect.com> writes:

> Why does the IETF website consider it necessary to use TLS to access
> the mailing list archives, when they all appeared without it, or any
> other security, in the first place?

Archives have long been and continue to be available at
ftp://ftp.ietf.org/ietf-mail-archive/

Thomas

From eburger@standardstrack.com  Fri Aug 26 05:56:55 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2FD21F863E for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 05:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.239
X-Spam-Level: 
X-Spam-Status: No, score=-102.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SMUfTQzOd8tI for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 05:56:55 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 630FA21F854E for <ietf@ietf.org>; Fri, 26 Aug 2011 05:56:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=XEzijj8fWbWMJufOP3UZ90QOWSGnMgFYmVYzwTvxcaID4s7x9Han/BRHAH7EXdLHf6tP5exsi10evofjMfdaf1RizhDmBzsDR2YjVGCoeDVHmz4Gq1aova7KhwdkUpGP;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Qwvz6-0000Ef-NF for ietf@ietf.org; Fri, 26 Aug 2011 05:58:09 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-57-1048836359; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: https
Date: Fri, 26 Aug 2011 08:58:05 -0400
In-Reply-To: <20110826105038.GA15033@odin.ulthar.us>
To: IETF-Discussion list <ietf@ietf.org>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <20110826105038.GA15033@odin.ulthar.us>
Message-Id: <A385DA0D-0701-4F24-8980-AF7B3F1289B6@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 12:56:56 -0000

--Apple-Mail-57-1048836359
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

+100

On Aug 26, 2011, at 6:50 AM, Scott Schmit wrote:

> On Fri, Aug 26, 2011 at 09:18:41AM +0200, t.petch wrote:
>> Why does the IETF website consider it necessary to use TLS to access
>> the mailing list archives, when they all appeared without it, or any
>> other security, in the first place?
> 
> TLS provides more than confidentiality--it also provides authenticity.
> If I were living in a hostile regime, I'd appreciate knowing that the
> RFCs, etc that I'm getting really come from the IETF unmodified.
> 
> Also, as a general principle, I'd rather someone not be able to read
> over my shoulder, even if it is harmless stuff. Using encryption only
> when I need it makes all of my encrypted traffic less secure.
> 
> For example, if I were out to modify the traffic you read to make sure
> that you didn't even know that a working group existed, I'd have a lot
> easier time of it if you use DNS without DNSSEC, HTTP without TLS, TLS
> without HASTLS, DANE, HSTS, etc. Now, not all of that is completed
> protocol work, but one step at a time.
> 
>> Besides all the usual hassle of TLS, today the certificate is reported
>> by IE as expired, which sort of sums it up.
> 
> Mistakes happen. Hopefully lessons are learned so that they don't get
> repeated.
> 
> If it's a protocol problem, whose fault is that but ours?
> 
> -- 
> Scott Schmit
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-57-1048836359
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MjYxMjU4MDVaMCMGCSqGSIb3DQEJ
BDEWBBQge8CvVFEl7YARf9ufnuUb4rURSTCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAFu9gDvR61bYSi40uXyxo0oqJ1ZPYv95HGmC9w1LqUtwPgW5
YY3bigrtNBZMeBbd+H0ZonD1HdQMF02PSLc7t7vbEa5xBKiEaBshibEb6AAfud1qBlgSfc/nUlck
0GWK1xBCMEyYPfow9LnEiUPKmDqbyl8WQbTAUd42L0N41tWQB3anwAgNlvRKLUhgpIyCSolECx+l
IvDU2UIcSakvlOkDSp7c1a4Fiml+FQRyRVrsiwyYYjOP9OU/fzwcqg8idutyLKQFdAFMelUPB65z
+rKkV3EZ54FjrMEvzm9qQBOsXKqfbeDkxf5CG8VnPk9nqGuYxuiwbzTsJrWYugEq8lAAAAAAAAA=

--Apple-Mail-57-1048836359--

From d3e3e3@gmail.com  Fri Aug 26 06:42:46 2011
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 622BA21F8B5D for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 06:42:46 -0700 (PDT)
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.933, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4GCUxSesO6d for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 06:42:45 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id C8A4B21F8A7D for <ietf@ietf.org>; Fri, 26 Aug 2011 06:42:45 -0700 (PDT)
Received: by vws12 with SMTP id 12so282348vws.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 06:44:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=a0IzzoBVl0kA+3NefhBibL4N5rgbea80Z9GObynp+ZU=; b=I49WZCv75rxhDxDeMTbgCizhAqC6Fy030Z4g0T8/SyaMIGAIig5UQb+oHUNye5tV2m 4IF6/QUfYeBYPgjisQsU7i61Vy9mH9xP2BGhbBljiIcTdEFAc7qV5t9y6JGeANWT6V1a zdQHRZRoqXzDnwcJC0MbMdSgTY4nyJVQb5m+Y=
Received: by 10.52.95.52 with SMTP id dh20mr1151151vdb.296.1314366241726; Fri, 26 Aug 2011 06:44:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.155.42 with HTTP; Fri, 26 Aug 2011 06:43:37 -0700 (PDT)
In-Reply-To: <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 26 Aug 2011 09:43:37 -0400
Message-ID: <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>
Subject: Re: https
To: "t.petch" <daedulus@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 13:42:46 -0000

On Fri, Aug 26, 2011 at 4:39 AM, t.petch <daedulus@btconnect.com> wrote:
> ----- Original Message -----
> From: "SM" <sm@resistor.net>
> To: "t.petch" <daedulus@btconnect.com>
> Cc: "IETF Discussion" <ietf@ietf.org>
> Subject: Re: https
>
>
>> Hi Tom,
>> At 00:18 26-08-2011, t.petch wrote:
>> >Besides all the usual hassle of TLS, today the certificate is
>> >reported by IE as
>> >expired, which sort of sums it up.
>>
>> Already reported to ietf-action@.
>>
>> Regards,
>> -sm
>>
>> P.S. My experience of ietf-action@ is that they are responsive and do
>> fix problems that are reported.
>
> Yup, but why are we using https at all? =A0Who decided, and please would =
they
> undecide? =A0Unexpired certificates can be circumvented, but all too ofte=
n, the
> https parts of the web site just do not work and, more importantly, I thi=
nk it
> wrong to use industrial grade security where none is called for.

The mail archives (and the minutes of the physical meetings) are the
official record of the Working Groups, IETF, etc. Those archives
should be available with a reasonably high level of integrity and
authenticity.

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

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

From eburger-l@standardstrack.com  Fri Aug 26 06:55:13 2011
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8627C21F8B5C for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 06:55:13 -0700 (PDT)
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.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pKNgBFGquf1W for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 06:55:12 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id AF19921F86EE for <ietf@ietf.org>; Fri, 26 Aug 2011 06:55:12 -0700 (PDT)
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:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=05QZCmNF89PWThasfSm9UkljqdeBK38PueF6vrUEg3rUYzEACILS90VyxXQ3zuRHqgiVFJ7MeLqTBrcafBdgoNNiKV6kPcys4O94cOnqnh9XQUug2WTA1XFs7rFsC1if;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QwwtU-0003hu-1B; Fri, 26 Aug 2011 06:56:27 -0700
Subject: Re: Routing at the Edges of the Internet
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
Date: Fri, 26 Aug 2011 09:56:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5512775-8B28-444F-988A-0142CEB6846A@standardstrack.com>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
To: Adam Novak <interfect@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 13:55:13 -0000

I disagree with the fundamental premise of this concept, that it is a =
PROBLEM that the Internet is not a network.  Um, last I looked, the =
Internet is an interconnection of networks.  Not a network in that =
sense.

Edge devices can today, in the scenario you portray, pick the "best" =
network to connect to.  Last thing we need is to ossify a method of =
doing that.  Let the edge be the edge and do what it wants.

On Aug 25, 2011, at 9:57 PM, Adam Novak wrote:

> I trust that some of you have seen this article from a while back:
>=20
> =
<http://moblog.wiredwings.com/archives/20110315/How-We-Killed-The-Internet=
-And-Nobody-Noticed.html>
>=20
> An informative except:
>=20
> "When I open my laptop, I see over ten different wifi access points.
> Say I wanted to send data to my friend in the flat next to mine. It is
> idiotic that nowadays, I would use the bottleneck subscriber line to
> my upstream ISP and my crippled upload speed and push it all the way
> across their infrastructure to my neighbors ISP and back to the Wifi
> router in reach of mine. The Internet is not meant to be used that
> way. Instead, all these wifi networks should be configured to talk to
> each other."
>=20
> I also trust that you are aware of what happened to the Internet in
> Egypt (and elsewhere) this spring, where Internet connectivity was
> disrupted by shutting down major ISP networks.
>=20
> I would like to bring the attention of the IETF to what I see as a
> fundamental problem with the current architecture of the Internet:
>=20
> The Internet is not a network.
>=20
> As part of the development of the Internet, fault-tolerant routing
> protocols have been developed that allow a connecdestined fortion to
> be maintained, even if the link that was carrying goes down, by
> routing packets around the problem. Similarly, packets can be
> load-balanced over multiple links for increased bandwidth. However,
> the benefits of these technologies are not available to end users. If
> I have a smartphone with both a 3G and a Wi-Fi connection, downloads
> cannot currently be load-balanced across them. The two interfaces are
> on two different networks, which are almost certainly part of two
> different autonomous systems. Packets must be addressed to one of the
> two interfaces, not the device, and packets addressed to one interface
> have no way to be routed to the other. Similar problems arise when a
> laptop has both a wired and a wireless connection. Wired networks also
> suffer from related difficulties: If I have Verizon and my friend has
> Comcast, and we string an Ethernet cable between our houses, packets
> for me will still all come down my connection, and packets for my
> friend will still all come down theirs.
>=20
> The Internet, as it currently appears to end-users, has a logical tree
> topology: computers connect to your home router, which connects to
> your ISP, which connects to the rest of the Internet. Cell phones
> connect to the tower, which connects through a backhaul link to the
> rest of the Internet. Almost all of the devices involved have multiple
> physical interfaces and full IP routing implementations, but only the
> default route is ever used. This results in a brittle Internet: the
> failure of one ISP router can disconnect a large number of end-users
> from the Internet, as well as interrupting communication between those
> users, even when those users are, physically, only a few feet from
> each other.
>=20
> My question is this: what IETF work would be needed to add more
> routing to the edges of the Internet? If each home or mobile device
> was essentially it's own autonomous system, what would this do to
> routing table size? To ASN space utilization? How can individuals
> interconnect home networks when RIRs do not assign address and AS
> number resources to individuals? How might individuals interconnect
> home networks without manual routing configuration? Under what
> circumstances could an ISP trust a client's claim to have a route to
> another client or to another ISP? How might packets sent to a device's
> address on one network be routed to that device's address on another
> network, while packets to immediately adjacent addresses take the
> normal path?
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From tbray@textuality.com  Fri Aug 26 07:22:49 2011
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3629C21F8B8D for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wdaoUtCgi0x for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:22:48 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id BE3D621F86EA for <ietf@ietf.org>; Fri, 26 Aug 2011 07:22:48 -0700 (PDT)
Received: by pzk33 with SMTP id 33so10159538pzk.18 for <ietf@ietf.org>; Fri, 26 Aug 2011 07:24:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.158.3 with SMTP id g3mr583858wfe.127.1314368645055; Fri, 26 Aug 2011 07:24:05 -0700 (PDT)
Received: by 10.143.60.16 with HTTP; Fri, 26 Aug 2011 07:24:04 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>
Date: Fri, 26 Aug 2011 07:24:04 -0700
Message-ID: <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com>
Subject: Re: https
From: Tim Bray <tbray@textuality.com>
To: "t.petch" <daedulus@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: SM <sm@resistor.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:22:49 -0000

I'm increasingly coming to think that *everything* should be done with
TLS unless you can prove it's harmful.  Call me paranoid, but given
the general state of the world, secure-by-default seems like the way
to go.  -Tim

On Fri, Aug 26, 2011 at 1:39 AM, t.petch <daedulus@btconnect.com> wrote:
> ----- Original Message -----
> From: "SM" <sm@resistor.net>
> To: "t.petch" <daedulus@btconnect.com>
> Cc: "IETF Discussion" <ietf@ietf.org>
> Subject: Re: https
>
>
>> Hi Tom,
>> At 00:18 26-08-2011, t.petch wrote:
>> >Besides all the usual hassle of TLS, today the certificate is
>> >reported by IE as
>> >expired, which sort of sums it up.
>>
>> Already reported to ietf-action@.
>>
>> Regards,
>> -sm
>>
>> P.S. My experience of ietf-action@ is that they are responsive and do
>> fix problems that are reported.
>
> Yup, but why are we using https at all? =A0Who decided, and please would =
they
> undecide? =A0Unexpired certificates can be circumvented, but all too ofte=
n, the
> https parts of the web site just do not work and, more importantly, I thi=
nk it
> wrong to use industrial grade security where none is called for.
>
> Tom Petch
>
>
>>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From daedulus@btconnect.com  Fri Aug 26 07:35:17 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C5921F8BCB for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUfhVvNFWb1z for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:35:17 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by ietfa.amsl.com (Postfix) with ESMTP id 1E21421F8BC4 for <ietf@ietf.org>; Fri, 26 Aug 2011 07:35:16 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr07.btconnect.com with SMTP id EDE12569; Fri, 26 Aug 2011 15:36:31 +0100 (BST)
Message-ID: <002b01cc63f4$a6c992e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>
Subject: Re: https
Date: Fri, 26 Aug 2011 15:32:46 +0200
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.4E57AF6F.0097, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.26.140914:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_PATH, __C230066_P2, __C230066_P5, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4E57AF6F.0182,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:35:18 -0000

----- Original Message -----
From: "Donald Eastlake" <d3e3e3@gmail.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Friday, August 26, 2011 3:43 PM
On Fri, Aug 26, 2011 at 4:39 AM, t.petch <daedulus@btconnect.com> wrote:
> ----- Original Message -----
> From: "SM" <sm@resistor.net>
> To: "t.petch" <daedulus@btconnect.com>
> Cc: "IETF Discussion" <ietf@ietf.org>
>
>
>> Hi Tom,
>> At 00:18 26-08-2011, t.petch wrote:
>> >Besides all the usual hassle of TLS, today the certificate is
>> >reported by IE as
>> >expired, which sort of sums it up.
>>
>> Already reported to ietf-action@.
>>
>> Regards,
>> -sm
>>
>> P.S. My experience of ietf-action@ is that they are responsive and do
>> fix problems that are reported.
>
> Yup, but why are we using https at all? Who decided, and please would they
> undecide? Unexpired certificates can be circumvented, but all too often, the
> https parts of the web site just do not work and, more importantly, I think it
> wrong to use industrial grade security where none is called for.

The mail archives (and the minutes of the physical meetings) are the
official record of the Working Groups, IETF, etc. Those archives
should be available with a reasonably high level of integrity and
authenticity.

<tp>
Yeeees but for the mail archives they provide authenticity and integrity only as
far as the Man In The Middle, namely the IETF server/process; this adds a
spurious, to me, impression of security for e-mails that could have come from
anyone masquerading as anyone.  And when there is some defence against
masquerade - DKIM (and yes I know what it does and its limitations) - then the
DKIM signature is invalidated by the list process, that MITM again.

If there are requirements for archives to be provided with a degree of trust, eg
in response to a subpoena, then that should be a separate process, leaving us
ordinary folk to access them in a simple and straighforward manner.

Tom Petch







Thanks,
Donald
=============================
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
155 Beaver Street, Milford, MA 01757 USA
d3e3e3@gmail.com

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


From john-ietf@jck.com  Fri Aug 26 07:40:10 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 681D421F8BA0 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4glwpVyTF46s for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:40:10 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id C832321F8BA4 for <ietf@ietf.org>; Fri, 26 Aug 2011 07:40:09 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qwxb0-0009Pf-FH; Fri, 26 Aug 2011 10:41:22 -0400
Date: Fri, 26 Aug 2011 10:41:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: https
Message-ID: <8F38C2201545EEF1F78C65E8@PST.JCK.COM>
In-Reply-To: <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:40:10 -0000

--On Friday, August 26, 2011 09:43 -0400 Donald Eastlake
<d3e3e3@gmail.com> wrote:

>> Yup, but why are we using https at all? =C2=A0Who decided, =
and
>> please would they undecide? =C2=A0Unexpired certificates can =
be
>> circumvented, but all too often, the https parts of the web
>> site just do not work and, more importantly, I think it wrong
>> to use industrial grade security where none is called for.
>=20
> The mail archives (and the minutes of the physical meetings)
> are the official record of the Working Groups, IETF, etc.
> Those archives should be available with a reasonably high
> level of integrity and authenticity.

Don,

If that is the goal, wouldn't we be lots better off just
digitally signing those things, just as we are gradually
starting to create signatures for I-Ds, etc.?  Verifying that
one is talking to the right server and that the content is not
tampered with in transit is all well and good, but it doesn't
protect against compromised documents or a compromised server at
all.

   john




From joelja@bogus.com  Fri Aug 26 07:43:12 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F25E21F8B8D for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.056
X-Spam-Level: 
X-Spam-Status: No, score=-102.056 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQOywrxuL7ui for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:43:12 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2C99621F8B8B for <ietf@ietf.org>; Fri, 26 Aug 2011 07:43:12 -0700 (PDT)
Received: from [192.168.43.44] (md20536d0.tmodns.net [208.54.5.210]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7QEiOSv025520 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 26 Aug 2011 14:44:26 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E57B142.4020802@bogus.com>
Date: Fri, 26 Aug 2011 07:44:18 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
In-Reply-To: <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 26 Aug 2011 14:44:26 +0000 (UTC)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:43:12 -0000

It doesn't...

http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html

On 8/26/11 00:18 , t.petch wrote:
> Why does the IETF website consider it necessary to use TLS to access the mailing
> list archives, when they all appeared without it, or any other security, in the
> first place?
> 
> Besides all the usual hassle of TLS, today the certificate is reported by IE as
> expired, which sort of sums it up.
> 
> Tom Petch
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 


From mary.ietf.barnes@gmail.com  Fri Aug 26 07:47:33 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0254A21F8779 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.445
X-Spam-Level: 
X-Spam-Status: No, score=-103.445 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TDNXFF4qXXrb for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:47:32 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B9FF621F8745 for <ietf@ietf.org>; Fri, 26 Aug 2011 07:47:31 -0700 (PDT)
Received: by vws12 with SMTP id 12so351873vws.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 07:48:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=g0WtnZ+vgtKGkLOKnSoNoFTp7RjunuQCDP/OBaUJYF8=; b=Ibw3ycyc0T3srJHE0VuKMtwBXsK2+muhj58v3wk9Ji9VkhZnE4A68I+JqpMLvp9YRG 5yzQIsvauCuRBeaxuKc2K9rT3nQjgRfZgrNCY8KwjB4Q42P+d9chIShzLs2ETjJsnkaQ 2rKwCS7ZZhAnpr4GInRf80WRiNk8KLTz49W9E=
MIME-Version: 1.0
Received: by 10.52.20.175 with SMTP id o15mr617428vde.451.1314370127839; Fri, 26 Aug 2011 07:48:47 -0700 (PDT)
Received: by 10.52.160.36 with HTTP; Fri, 26 Aug 2011 07:48:47 -0700 (PDT)
In-Reply-To: <4E573BB6.5000700@gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <1314226999.1973.211.camel@d430> <4E573BB6.5000700@gmail.com>
Date: Fri, 26 Aug 2011 09:48:47 -0500
Message-ID: <CAHBDyN4ML7PL65=kQXchvvgmtOEX_hK5LB8BPSxjvOL0G11vmg@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: henk@uijterwaal.nl
Content-Type: multipart/alternative; boundary=20cf307ca57e92c01b04ab69a4e5
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:47:33 -0000

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

Henk,

A few responses inline below [MB].

Regards,
Mary.

On Fri, Aug 26, 2011 at 1:22 AM, Henk Uijterwaal
<henk.uijterwaal@gmail.com>wrote:

> On 25/08/2011 01:03, geoff wrote:
> > On Wed, 2011-08-24 at 15:28 -0400, Sam Hartman wrote:
> >> 1) We don't have to go to any particular location.  There has been an
> >> assumption made by people in this discussion that sometimes when we pick
> >> locations with particularly expensive hotels, we'll get particularly
> >> expensive meetings.  That's great except that we were the ones who chose
> >> to go to those locations.
> >> If we can't meet our cost targets at a location, go somewhere else.
>
> > Sam makes a really good point here.  We didn't have to go to Taipei.
> > For some reason we chose to go to Taipei.
>
> Not quite.  There is a requirement to have meetings all over the world,
> in a ratio of 1:1:1 for Europe, North America and Asia.  Considering
> that we have to go to Asia, Taipei looks like a sensible choice: it
> is in the middle of the region, it well connected, and it is one of
> the bigger economies in the region.
>
> I have a feeling that if we dropped this requirement and went for a
> 0:3:0 schedule because it is much cheaper for the US participants to
> go to M'polis 3 times/year, somebody else would complain.
>

[MB] I've not seen a single person advocate a 0:3:0 schedule and it's only
less cheaper for all participants (not just US) because the hotel rates are
extremely reasonable (<$150 as I recall).    It is definitely less expensive
for the vast majority of participants than NA cities like Quebec City and
San Francisco that  travel by air.  BUT, I think you are missing what we are
saying overall - the major reasons some of us prefer Minneapolis is because
it meets what some of us have been saying over and over as far a key factors
for meetings:
http://www.ietf.org/mail-archive/web/ietf/current/msg68656.html
http://www.ietf.org/mail-archive/web/ietf/current/msg68727.html

The expense factor is just one other factor that is higher priority for some
folks than others and certainly shouldn't be ignored in venue selection, but
I don't think there is an accurate way to judge the overall expense burden
for attendees as it is not at all  based on which continent the meeting is
held.  My expenses for  Prague, Quebec City and Beijing were nearly the
same: Prague was $500 less than QC and Beijing - cost for QC and Beijing was
the same!!! [/MB]

>
> > The hotel (and
> > host if there was on) could/should have been told -
> > sorry too expensive.
>
> I've lost track what has been officially announced, but in one of the
> future years, the 1:1:1 requirement has been dropped as there was no
> suitable venue in one of the areas.
>
[MB] I think it's next year that is the exception as we will be in both
Vancouver and Atlanta - although, I would think the West Coast and East
Coast locations ensures that a bit more of the travel burden is shared. I
think what some folks miss is that West Coast meetings in NA are almost as
far away as Western Europe for folks in the Eastern US, so it's really not
at all reasonable to assume that folks in the US have an easier travel
burden only if the meetings are NA. And, you ought to consider that when the
meetings are in the US, the majority of us travel significantly further to
get to meetings than folks in Europe do to get to meetings in Europe.  [/MB]

[MB] So, it's really silly for folks to be assuming that some of us want all
meetings in NA because it's just so much easier and cheaper for us.[/MB]



> Henk
>
> --
>
> ------------------------------------------------------------------------------
> Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
>                                          http://www.uijterwaal.nl
>                                          Phone: +31.6.55861746
>
> ------------------------------------------------------------------------------
>
> There appears to have been a collective retreat from reality that day.
>                                 (John Glanfield, on an engineering project)
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Henk,<div><br></div><div>A few responses inline below [MB].</div><div><br><=
/div><div>Regards,</div><div>Mary.<br><br><div class=3D"gmail_quote">On Fri=
, Aug 26, 2011 at 1:22 AM, Henk Uijterwaal <span dir=3D"ltr">&lt;<a href=3D=
"mailto:henk.uijterwaal@gmail.com">henk.uijterwaal@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;">On 25/08/2011 01:03, geoff wrote:<br>
&gt; On Wed, 2011-08-24 at 15:28 -0400, Sam Hartman wrote:<br>
&gt;&gt; 1) We don&#39;t have to go to any particular location. =A0There ha=
s been an<br>
&gt;&gt; assumption made by people in this discussion that sometimes when w=
e pick<br>
&gt;&gt; locations with particularly expensive hotels, we&#39;ll get partic=
ularly<br>
&gt;&gt; expensive meetings. =A0That&#39;s great except that we were the on=
es who chose<br>
&gt;&gt; to go to those locations.<br>
&gt;&gt; If we can&#39;t meet our cost targets at a location, go somewhere =
else.<br>
<br>
&gt; Sam makes a really good point here. =A0We didn&#39;t have to go to Tai=
pei.<br>
&gt; For some reason we chose to go to Taipei.<br>
<br>
Not quite. =A0There is a requirement to have meetings all over the world,<b=
r>
in a ratio of 1:1:1 for Europe, North America and Asia. =A0Considering<br>
that we have to go to Asia, Taipei looks like a sensible choice: it<br>
is in the middle of the region, it well connected, and it is one of<br>
the bigger economies in the region.<br>
<br>
I have a feeling that if we dropped this requirement and went for a<br>
0:3:0 schedule because it is much cheaper for the US participants to<br>
go to M&#39;polis 3 times/year, somebody else would complain.<br></blockquo=
te><div><br></div><div>[MB] I&#39;ve not seen a single person advocate a 0:=
3:0 schedule and it&#39;s only less cheaper for all participants (not just =
US) because the hotel rates are extremely reasonable (&lt;$150 as I recall)=
. =A0 =A0It is definitely less expensive for the vast majority of participa=
nts than NA cities like Quebec City and San Francisco that =A0travel by air=
. =A0BUT, I think you are missing what we are saying overall - the major re=
asons some of us prefer Minneapolis is because it meets what some of us hav=
e been saying over and over as far a key factors for meetings:</div>
<div><a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg68656.=
html">http://www.ietf.org/mail-archive/web/ietf/current/msg68656.html</a></=
div><div><a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg68=
727.html">http://www.ietf.org/mail-archive/web/ietf/current/msg68727.html</=
a></div>
<div><br></div><div>The expense factor is just one other factor that is hig=
her priority for some folks than others and certainly shouldn&#39;t be igno=
red in venue selection, but I don&#39;t think there is an accurate way to j=
udge the overall expense burden for attendees as it is not at all =A0based =
on which continent the meeting is held. =A0My expenses for =A0Prague, Quebe=
c City and Beijing were nearly the same: Prague was $500 less than QC and B=
eijing - cost for QC and Beijing was the same!!! [/MB] =A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
&gt; The hotel (and<br>
&gt; host if there was on) could/should have been told -<br>
&gt; sorry too expensive.<br>
<br>
I&#39;ve lost track what has been officially announced, but in one of the<b=
r>
future years, the 1:1:1 requirement has been dropped as there was no<br>
suitable venue in one of the areas.<br></blockquote><div>[MB] I think it&#3=
9;s next year that is the exception as we will be in both Vancouver and Atl=
anta - although, I would think the West Coast and East Coast locations ensu=
res that a bit more of the travel burden is shared. I think what some folks=
 miss is that West Coast meetings in NA are almost as far away as Western E=
urope for folks in the Eastern US, so it&#39;s really not at all reasonable=
 to assume that folks in the US have an easier travel burden only if the me=
etings are NA. And, you ought to consider that when the meetings are in the=
 US, the majority of us travel significantly further to get to meetings tha=
n folks in Europe do to get to meetings in Europe. =A0[/MB]</div>
<div><br></div><div>[MB] So, it&#39;s really silly for folks to be assuming=
 that some of us want all meetings in NA because it&#39;s just so much easi=
er and cheaper for us.[/MB]</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;">

<br>
Henk<br>
<br>
--<br>
---------------------------------------------------------------------------=
---<br>
Henk Uijterwaal =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Email: =
henk(at)<a href=3D"http://uijterwaal.nl" target=3D"_blank">uijterwaal.nl</a=
><br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0<a href=3D"http://www.uijterwaal.nl" target=3D"_blank">http://ww=
w.uijterwaal.nl</a><br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0Phone: <a href=3D"tel:%2B31.6.55861746" value=3D"+31655861746">+=
31.6.55861746</a><br>
---------------------------------------------------------------------------=
---<br>
<br>
There appears to have been a collective retreat from reality that day.<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (John Glan=
field, on an engineering project)<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>

--20cf307ca57e92c01b04ab69a4e5--

From melinda.shore@gmail.com  Fri Aug 26 07:50:47 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9431621F8500 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qIvLrdKLTHWv for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:50:47 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 25B1921F84FC for <ietf@ietf.org>; Fri, 26 Aug 2011 07:50:47 -0700 (PDT)
Received: by pzk33 with SMTP id 33so10235551pzk.18 for <ietf@ietf.org>; Fri, 26 Aug 2011 07:52:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ykKUUx9efKp5V/HJgCXhTmKEOLXDduFaPodjO84nar8=; b=n+JFosMeZ1hjvXrjHqPj0FhNmFEeNKaaIq5+242Dx44cc3aohcQ8uBkDkFyOihtyp9 cxq5KpCHq6cRZQYbxS+2KEE7it4KJYHUfE4V1J4mM9kFSCC6nIUDoeedtp81cfYFzdnS 5AFq7m94GuRXBe0IWwKsHgW8FcOi+4ckVQiXM=
Received: by 10.142.186.1 with SMTP id j1mr565675wff.81.1314370323595; Fri, 26 Aug 2011 07:52:03 -0700 (PDT)
Received: from polypro.local (66-230-82-131-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.131]) by mx.google.com with ESMTPS id m1sm2648465pbf.3.2011.08.26.07.52.00 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 26 Aug 2011 07:52:01 -0700 (PDT)
Message-ID: <4E57B30F.7030501@gmail.com>
Date: Fri, 26 Aug 2011 06:51:59 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>	<005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>
In-Reply-To: <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:50:47 -0000

On 8/26/11 5:43 AM, Donald Eastlake wrote:
> The mail archives (and the minutes of the physical meetings) are the
> official record of the Working Groups, IETF, etc. Those archives
> should be available with a reasonably high level of integrity and
> authenticity.

I'm not fully sold, but either way it seems to me that a technology
with such a very, very high error rate in deployment probably needs
some reconsideration.

Melinda

From dworley@avaya.com  Fri Aug 26 08:03:13 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9A0D21F8B6B for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 08:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.464
X-Spam-Level: 
X-Spam-Status: No, score=-103.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hAopA2Wi5G6u for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 08:03:13 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 19ED121F8745 for <ietf@ietf.org>; Fri, 26 Aug 2011 08:03:12 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtAHACW1V07GmAcF/2dsb2JhbABCnDSLbneBQAEBAQECARIoRAsCAQgNAQcYCRAhESUBAQQBEggah1CdUAKcN4M7gjFgBJhFhEyHJQ
X-IronPort-AV: E=Sophos;i="4.68,285,1312171200"; d="scan'208";a="264631367"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 Aug 2011 11:04:27 -0400
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; 26 Aug 2011 11:00:21 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 26 Aug 2011 11:04:26 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Adam Novak <interfect@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 26 Aug 2011 11:04:26 -0400
Subject: RE: Routing at the Edges of the Internet
Thread-Topic: Routing at the Edges of the Internet
Thread-Index: Acxjk5tgaeOlY7/IRcO6L2HXtgXybAAbPdyU
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
In-Reply-To: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 15:03:14 -0000

> From: Adam Novak [interfect@gmail.com]
>=20
> "Say I wanted to send data to my friend in the flat next to mine. It is
> idiotic that nowadays, I would use the bottleneck subscriber line to
> my upstream ISP and my crippled upload speed and push it all the way
> across their infrastructure to my neighbors ISP and back to the Wifi
> router in reach of mine."

This is a valid point, but it's also rather rare that one wants to
send large amounts of data directly to a friend in a neighboring flat
but one has not manually adjusting the local routing to take that into
account.

> If each home or mobile device was essentially [its] own autonomous
> system, what would this do to routing table size? To ASN space
> utilization?

There must be at least a few hundred million mobile phones with data
capability, and a similar number of homes and small businesses with
WiFi systems.  So we can estimate that a large fraction of a billion
entries would be added to the routing tables.  How would that work?

Dale

From simon@josefsson.org  Fri Aug 26 08:47:21 2011
Return-Path: <simon@josefsson.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDC3821F88B7; Fri, 26 Aug 2011 08:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IGD6b7XHaOER; Fri, 26 Aug 2011 08:47:21 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [213.115.69.139]) by ietfa.amsl.com (Postfix) with ESMTP id D375C21F8880; Fri, 26 Aug 2011 08:47:20 -0700 (PDT)
Received: from latte.josefsson.org (perens.inria.fr [128.93.60.79]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p7QFmK17004883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 26 Aug 2011 17:48:24 +0200
From: Simon Josefsson <simon@josefsson.org>
To: <gareth.richards@rsa.com>
Subject: Re: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:110826:hartmans-ietf@mit.edu::KmKG+e77wEOy+lVj:P1O
X-Hashcash: 1:22:110826:gen-art@ietf.org::0Z1/S3Lxj+F/N6dU:0Cdu
X-Hashcash: 1:22:110826:ietf@ietf.org::4GpVs6fjTPV1dnQ2:2MNX
X-Hashcash: 1:22:110826:david.black@emc.com::+hNi4i6fRJAnAOCY:Lrei
X-Hashcash: 1:22:110826:ietf-krb-wg@lists.anl.gov::lTNnjDov+aTD13Hx:6Mbl
X-Hashcash: 1:22:110826:gareth.richards@rsa.com::fgqutUlROOFgND2G:9vpX
Date: Fri, 26 Aug 2011 17:48:15 +0200
In-Reply-To: <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> (gareth richards's message of "Fri, 26 Aug 2011 11:04:22 -0400")
Message-ID: <87sjoocgxs.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.2 at yxa-v
X-Virus-Status: Clean
Cc: gen-art@ietf.org, david.black@emc.com, hartmans-ietf@mit.edu, ietf-krb-wg@lists.anl.gov, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 15:47:21 -0000

<gareth.richards@rsa.com> writes:

> Some form of identifier will be required for the otp-algID in the
> PA-OTP-CHALLENGE and the PA-OTP-REQUEST and from what I remember about
> when this was first discussed, it was agreed that it would make sense
> to use the registry of identifiers already being established for PSKC
> rather than produce a duplicate one.  My assumption was that a
> registry would be required to ensure that the URIs were unique.
>

I think a separate registry is needed, RFC 6030 requires several things
from a profile that shouldn't be required in order to support Kerberos
OTP.  See below.

/Simon

12.4.  PSKC Algorithm Profile Registry

   IANA has created a registry for PSKC algorithm profiles in accordance
   with the principles set out in RFC 5226 [RFC5226].

   As part of this registry, IANA maintains the following information:

   Common Name:  The name by which the PSKC algorithm profile is
      generally referred.

   Class:  The type of PSKC algorithm profile registry entry being
      created, such as encryption, Message Authentication Code (MAC),
      One-Time Password (OTP), Digest.

   URI:  The URI to be used to identify the profile.

   Identifier Definition:  IANA will add a pointer to the specification
      containing information about the PSKC algorithm profile
      registration.

   Algorithm Definition:  A reference to the stable document in which
      the algorithm being used with the PSKC is defined.

   Registrant Contact:  Contact information about the party submitting
      the registration request.

   Deprecated:  TRUE if this entry has been deprecated based on expert
      approval and SHOULD not be used in any new implementations.
      Otherwise, FALSE.

   PSKC Profiling:  Information about PSKC XML elements and attributes
      being used (or not) with this specific profile of PSKC.

   PSKC algorithm profile identifier registrations are to be subject to
   Specification Required as per RFC 5226 [RFC5226].  Updates can be
   provided based on expert approval only.  Based on expert approval, it
   is possible to mark entries as "deprecated".  A designated expert
   will be appointed by the IESG.

   IANA has added two initial values to the registry based on the
   algorithm profiles described in Section 10.

From scott.brim@gmail.com  Fri Aug 26 09:02:43 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D81521F8742 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 09:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.559
X-Spam-Level: 
X-Spam-Status: No, score=-103.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sToMFjnJLFEv for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 09:02:43 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id DBDAA21F86C0 for <ietf@ietf.org>; Fri, 26 Aug 2011 09:02:42 -0700 (PDT)
Received: by vws12 with SMTP id 12so428987vws.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 09:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=SJfvkagkyd3/ATcF+GJUmKpkgPFEgknrSZ5ZuqYjnXA=; b=IfJXJdRumLBPN6jyF1Zvs5+DmoLL18oXiAAVh+e21Erbl+AzngkM54s//pxaDMBMZd 7QeQswzy5ux4Ti557xU5lVX0hpJ+2nWpI4uh9OII4J8jgOX1l02HofWDh+bR0bnL9vop 8LxlD9Myk1d65PaB0NITOQcat0j91WZHBIu4g=
Received: by 10.52.76.8 with SMTP id g8mr1371386vdw.178.1314374639110; Fri, 26 Aug 2011 09:03:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.168.168 with HTTP; Fri, 26 Aug 2011 09:03:39 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 26 Aug 2011 12:03:39 -0400
Message-ID: <CAPv4CP-OiQ3F96skrFO7j7LfF0jBxWNNubOFTLFD_x9AGVDjVg@mail.gmail.com>
Subject: Re: Routing at the Edges of the Internet
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 16:02:43 -0000

On Fri, Aug 26, 2011 at 11:04, Worley, Dale R (Dale) <dworley@avaya.com> wr=
ote:
> There must be at least a few hundred million mobile phones with data
> capability, and a similar number of homes and small businesses with
> WiFi systems. =A0So we can estimate that a large fraction of a billion
> entries would be added to the routing tables. =A0How would that work?

You do it in the endpoint.  The original poster should look at all the
work already being done in IETF WGs (and elsewhere), e.g. 6man and
mif, intarea and tsvwg.

From david.black@emc.com  Fri Aug 26 07:43:00 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1D121F8B78; Fri, 26 Aug 2011 07:43:00 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlfbNWDhM9XN; Fri, 26 Aug 2011 07:43:00 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3F95721F8B46; Fri, 26 Aug 2011 07:42:59 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QEiEBs030825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2011 10:44:14 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 26 Aug 2011 10:43:59 -0400
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QEhwjs020814; Fri, 26 Aug 2011 10:43:58 -0400
Received: from mx14a.corp.emc.com ([169.254.1.143]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Fri, 26 Aug 2011 10:43:58 -0400
From: <david.black@emc.com>
To: <gareth.richards@rsa.com>, <hartmans-ietf@mit.edu>
Date: Fri, 26 Aug 2011 10:43:57 -0400
Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: Acxiy1sLmZxtuKZeRQOoO/Cr6qwdGgBEg51gAAg7JRA=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E058B12FDBB@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <B1371F619AB0A94C9AC73CF2E475485B038C5187CF@MX11A.corp.emc.com>
In-Reply-To: <B1371F619AB0A94C9AC73CF2E475485B038C5187CF@MX11A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 26 Aug 2011 09:05:34 -0700
Cc: ietf-krb-wg@lists.anl.gov, gen-art@ietf.org, ietf@ietf.org, david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:43:01 -0000

> I believe that the WG consensus here was that this security issue only ap=
plies if the identity of the
> KDC has not been verified.
>=20
> How about the following updated version of the paragraph?
>=20
>    Therefore, unless the identity of the KDC has been verified,
>    anonymous PKINIT SHALL NOT be used with OTP
>    algorithms that require the OTP value to be sent to the KDC.  In
>    addition, the security considerations should be carefully considered
>    before anonymous PKINIT is used with other algorithms such as those wi=
th short OTP
>    values.

That works for me, as the use of "SHALL NOT" is clear and explicit.

Thanks,
--David

> -----Original Message-----
> From: Richards, Gareth
> Sent: Friday, August 26, 2011 6:56 AM
> To: hartmans-ietf@mit.edu; Black, David
> Cc: gen-art@ietf.org; ietf@ietf.org; ietf-krb-wg@lists.anl.gov; stephen.f=
arrell@cs.tcd.ie
> Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
>=20
> >
> >
> >     > [1] In section 6.1 at the top of p.28, I don't believe that the
> >     > use of lower case "recommended" is a strong enough warning about
> >     > the danger in using anonymous PKINIT because it exposes the OTP
> >     > value:
> >
> >     >    It is therefore recommended that anonymous PKINIT not be used
> >     > with OTP algorithms that require the OTP value to be sent to the
> >     > KDC and that careful consideration be made of the security
> >     > implications before it is used with other algorithms such as thos=
e
> >     > with short OTP values.
> >
> >     > At a minimum, that warning should be in upper-case:
> >
> >     >    It is therefore RECOMMENDED that anonymous PKINIT not be used
> >     > with OTP algorithms that require the OTP value to be sent to the
> >     > KDC. In addition, the security implications should be carefully
> >     > considered before anonymous PKINIT is used with other algorithms
> >     > such as those with short OTP values.
> >
> >     > Beyond that, the security issue in the first sentence may be
> >     > severe enough to justify a prohibition, so the following would
> >     > also be acceptable:
> >
> >     >    Therefore anonymous PKINIT SHALL NOT be used with OTP
> >     > algorithms that require the OTP value to be sent to the KDC. In
> >     > addition, the security implications should be carefully
> > considered
> >     > before anonymous PKINIT is used with other algorithms such as
> >     > those with short OTP values.
> >
> > I definitely agree that we should use RFC 2119 language.
> > Note that WG participants have questioned this text in last call for
> > other reasons.
> > Many implementations use anonymous pkinit in a mode where the KDC's
> > certificate is verified--that is the client is anonymous but the KDC is
> > identified through a PKI.
> > WG participants believe (and I agree) that the security concern does
> > not
> > apply at all in this case.
> > So, the text needs reworking.
> >
>=20
> I believe that the WG consensus here was that this security issue only ap=
plies if the identity of the
> KDC has not been verified.
>=20
> How about the following updated version of the paragraph?
>=20
>    Therefore, unless the identity of the KDC has been verified,
>    anonymous PKINIT SHALL NOT be used with OTP
>    algorithms that require the OTP value to be sent to the KDC.  In
>    addition, the security considerations should be carefully considered
>    before anonymous PKINIT is used with other algorithms such as those wi=
th short OTP
>    values.
>=20
>=20
> --Gareth

From david.black@emc.com  Fri Aug 26 07:51:27 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB84D21F8ADE; Fri, 26 Aug 2011 07:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.059
X-Spam-Level: 
X-Spam-Status: No, score=-106.059 tagged_above=-999 required=5 tests=[AWL=0.540, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-f94wCboa14; Fri, 26 Aug 2011 07:51:22 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9A121F8B14; Fri, 26 Aug 2011 07:51:20 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QEqUCL030658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2011 10:52:31 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 26 Aug 2011 10:52:19 -0400
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.221.46.114]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QEqIXh010360; Fri, 26 Aug 2011 10:52:19 -0400
Received: from mx14a.corp.emc.com ([169.254.1.143]) by mxhub06.corp.emc.com ([128.221.46.114]) with mapi; Fri, 26 Aug 2011 10:52:18 -0400
From: <david.black@emc.com>
To: <gareth.richards@rsa.com>, <hotz@jpl.nasa.gov>
Date: Fri, 26 Aug 2011 10:52:17 -0400
Subject: RE: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: AcxjfgHOay3VXcEFQNqDiJG7zfycjgAc1frwAANgKGA=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E058B12FDCA@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <C24DCF97-F9D1-49DE-8A6C-F6F6A744B139@jpl.nasa.gov> <B1371F619AB0A94C9AC73CF2E475485B038C5188C9@MX11A.corp.emc.com>
In-Reply-To: <B1371F619AB0A94C9AC73CF2E475485B038C5188C9@MX11A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 26 Aug 2011 09:05:49 -0700
Cc: gen-art@ietf.org, ietf-krb-wg@lists.anl.gov, hartmans-ietf@mit.edu, ietf@ietf.org, david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:51:27 -0000

> Resynchronization in the algorithms I am familiar with involves the serve=
r resetting its OTP search
> window and the system in the ID allows the client to send an additional v=
alue to help the server do
> this.  This is just as described in RFC4226.
>=20
> How about the following clarification text:
>=20
> Methods to recover from this type of situation are OTP algorithm specific=
 but may involve the client
> sending a sequence of OTP
> values to allow the server to further validate the correct position in it=
s search window  (see section
> 7.4 of [RFC4226] for an example).

That new text is fine.  My primary concern with the existing text is that t=
he server has to do
something like this for all the cases except when the clock in a clock-base=
d token is slightly
slow, but the existing text doesn't indicate that such server action may be=
 needed.  The proposed
new text does so, and the reference to section 7.4 of RFC 4226 is a good ad=
dition that makes the
point clear.

Thanks,
--David

> -----Original Message-----
> From: Richards, Gareth
> Sent: Friday, August 26, 2011 10:45 AM
> To: hotz@jpl.nasa.gov
> Cc: Black, David; ietf@ietf.org; hartmans-ietf@mit.edu; ietf-krb-wg@lists=
.anl.gov
> Subject: RE: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preaut=
h-18
>=20
> >
> > > In section 2.4, the following sentence is potentially confusing:
> > >
> > >   For example,
> > >   event-based tokens may drift since the counter on the token is
> > >   incremented every time the token is used but the counter on the
> > >   server is only incremented on an authentication.  Similarly, the
> > >   clocks on time-based tokens may drift.
> > >
> > > The confusion arises because the resync mechanism described in that s=
ection causes
> > > the client to use the next token value.  By itself, that won't help w=
hen an event based
> > > has gotten ahead of the server; using the next value only puts the to=
ken further ahead.
> > > Similarly, by itself, this mechanism does not help if the token clock=
 has drifted ahead
> > > of the server clock, but does help if the token clock has drifted beh=
ind.  A little more
> > > explanation of what the server can do to take advantage of this mecha=
nism (e.g., how to
> > > deal with an event-based token that is ahead of the server) would red=
uce the confusion.
> >
> > Possibly there is something in RFC4226, section 7.4 which could be
> > referenced or re-used?  It seems to assume that the server itself knows
> > the token seed, which may not be a valid assumption, so perhaps not.
>=20
> Resynchronization in the algorithms I am familiar with involves the serve=
r resetting its OTP search
> window and the system in the ID allows the client to send an additional v=
alue to help the server do
> this.  This is just as described in RFC4226.
>=20
> How about the following clarification text:
>=20
> Methods to recover from this type of situation are OTP algorithm specific=
 but may involve the client
> sending a sequence of OTP
> values to allow the server to further validate the correct position in it=
s search window  (see section
> 7.4 of [RFC4226] for an example).
>=20
> --Gareth

From hotz@jpl.nasa.gov  Thu Aug 25 16:21:41 2011
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E95B21F8B18; Thu, 25 Aug 2011 16:21:41 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFNGj6mFgm5F; Thu, 25 Aug 2011 16:21:40 -0700 (PDT)
Received: from mail.jpl.nasa.gov (sentrion3.jpl.nasa.gov [128.149.139.109]) by ietfa.amsl.com (Postfix) with ESMTP id D697F21F88B7; Thu, 25 Aug 2011 16:21:40 -0700 (PDT)
Received: from dhcp-137-79-178-203.jpl.nasa.gov (dhcp-137-79-178-203.jpl.nasa.gov [137.79.178.203]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7PNMpKk013092 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Thu, 25 Aug 2011 16:22:52 -0700
Subject: Re: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com>
Date: Thu, 25 Aug 2011 16:22:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C24DCF97-F9D1-49DE-8A6C-F6F6A744B139@jpl.nasa.gov>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com>
To: gareth.richards@rsa.com
X-Mailer: Apple Mail (2.1084)
X-Source-IP: dhcp-137-79-178-203.jpl.nasa.gov [137.79.178.203]
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Fri, 26 Aug 2011 09:06:11 -0700
Cc: "ietf-krb-wg@lists.anl.gov list \(ietf-krb-wg@lists.anl.gov\)" <ietf-krb-wg@lists.anl.gov>, gen-art@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, david.black@emc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2011 23:21:41 -0000

On Aug 24, 2011, at 5:45 PM, david.black@emc.com wrote:

> In section 2.4, the following sentence is potentially confusing:
>=20
>   For example,
>   event-based tokens may drift since the counter on the token is
>   incremented every time the token is used but the counter on the
>   server is only incremented on an authentication.  Similarly, the
>   clocks on time-based tokens may drift.
>=20
> The confusion arises because the resync mechanism described in that =
section causes
> the client to use the next token value.  By itself, that won't help =
when an event based
> has gotten ahead of the server; using the next value only puts the =
token further ahead.
> Similarly, by itself, this mechanism does not help if the token clock =
has drifted ahead
> of the server clock, but does help if the token clock has drifted =
behind.  A little more
> explanation of what the server can do to take advantage of this =
mechanism (e.g., how to
> deal with an event-based token that is ahead of the server) would =
reduce the confusion.

Possibly there is something in RFC4226, section 7.4 which could be =
referenced or re-used?  It seems to assume that the server itself knows =
the token seed, which may not be a valid assumption, so perhaps not.
------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu




From gareth.richards@rsa.com  Fri Aug 26 03:54:46 2011
Return-Path: <gareth.richards@rsa.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6287B21F8B4E; Fri, 26 Aug 2011 03:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4bvdB2nJ-8oG; Fri, 26 Aug 2011 03:54:45 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id B337C21F8B4C; Fri, 26 Aug 2011 03:54:45 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QAtwAO003015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2011 06:55:58 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Fri, 26 Aug 2011 06:55:40 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.221.56.110]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QAtde4007314; Fri, 26 Aug 2011 06:55:39 -0400
Received: from MX11A.corp.emc.com ([169.254.1.161]) by mxhub24.corp.emc.com ([128.221.56.110]) with mapi; Fri, 26 Aug 2011 06:55:38 -0400
From: <gareth.richards@rsa.com>
To: <hartmans-ietf@mit.edu>, <david.black@emc.com>
Date: Fri, 26 Aug 2011 06:55:36 -0400
Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: Acxiy1sLmZxtuKZeRQOoO/Cr6qwdGgBEg51g
Message-ID: <B1371F619AB0A94C9AC73CF2E475485B038C5187CF@MX11A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu>
In-Reply-To: <tslliui6ycj.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
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 26 Aug 2011 09:06:26 -0700
Cc: ietf-krb-wg@lists.anl.gov, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 10:54:46 -0000

>
>
>     > [1] In section 6.1 at the top of p.28, I don't believe that the
>     > use of lower case "recommended" is a strong enough warning about
>     > the danger in using anonymous PKINIT because it exposes the OTP
>     > value:
>
>     >    It is therefore recommended that anonymous PKINIT not be used
>     > with OTP algorithms that require the OTP value to be sent to the
>     > KDC and that careful consideration be made of the security
>     > implications before it is used with other algorithms such as those
>     > with short OTP values.
>
>     > At a minimum, that warning should be in upper-case:
>
>     >    It is therefore RECOMMENDED that anonymous PKINIT not be used
>     > with OTP algorithms that require the OTP value to be sent to the
>     > KDC. In addition, the security implications should be carefully
>     > considered before anonymous PKINIT is used with other algorithms
>     > such as those with short OTP values.
>
>     > Beyond that, the security issue in the first sentence may be
>     > severe enough to justify a prohibition, so the following would
>     > also be acceptable:
>
>     >    Therefore anonymous PKINIT SHALL NOT be used with OTP
>     > algorithms that require the OTP value to be sent to the KDC. In
>     > addition, the security implications should be carefully
> considered
>     > before anonymous PKINIT is used with other algorithms such as
>     > those with short OTP values.
>
> I definitely agree that we should use RFC 2119 language.
> Note that WG participants have questioned this text in last call for
> other reasons.
> Many implementations use anonymous pkinit in a mode where the KDC's
> certificate is verified--that is the client is anonymous but the KDC is
> identified through a PKI.
> WG participants believe (and I agree) that the security concern does
> not
> apply at all in this case.
> So, the text needs reworking.
>

I believe that the WG consensus here was that this security issue only appl=
ies if the identity of the KDC has not been verified.

How about the following updated version of the paragraph?

   Therefore, unless the identity of the KDC has been verified,
   anonymous PKINIT SHALL NOT be used with OTP
   algorithms that require the OTP value to be sent to the KDC.  In
   addition, the security considerations should be carefully considered
   before anonymous PKINIT is used with other algorithms such as those with=
 short OTP
   values.


--Gareth

From gareth.richards@rsa.com  Fri Aug 26 07:44:08 2011
Return-Path: <gareth.richards@rsa.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1934A21F8B8B for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:44:08 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izEuGe7raAjr for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 07:44:07 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7719621F8B78 for <ietf@ietf.org>; Fri, 26 Aug 2011 07:44:07 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QEjM2w006663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2011 10:45:22 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 26 Aug 2011 10:45:17 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QEjGvv031564; Fri, 26 Aug 2011 10:45:17 -0400
Received: from MX11A.corp.emc.com ([169.254.1.161]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Fri, 26 Aug 2011 10:45:16 -0400
From: <gareth.richards@rsa.com>
To: <hotz@jpl.nasa.gov>
Date: Fri, 26 Aug 2011 10:45:14 -0400
Subject: RE: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: AcxjfgHOay3VXcEFQNqDiJG7zfycjgAc1frw
Message-ID: <B1371F619AB0A94C9AC73CF2E475485B038C5188C9@MX11A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <C24DCF97-F9D1-49DE-8A6C-F6F6A744B139@jpl.nasa.gov>
In-Reply-To: <C24DCF97-F9D1-49DE-8A6C-F6F6A744B139@jpl.nasa.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 26 Aug 2011 09:06:37 -0700
Cc: ietf-krb-wg@lists.anl.gov, david.black@emc.com, hartmans-ietf@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 14:44:08 -0000

>
> > In section 2.4, the following sentence is potentially confusing:
> >
> >   For example,
> >   event-based tokens may drift since the counter on the token is
> >   incremented every time the token is used but the counter on the
> >   server is only incremented on an authentication.  Similarly, the
> >   clocks on time-based tokens may drift.
> >
> > The confusion arises because the resync mechanism described in that
> section causes
> > the client to use the next token value.  By itself, that won't help
> when an event based
> > has gotten ahead of the server; using the next value only puts the
> token further ahead.
> > Similarly, by itself, this mechanism does not help if the token clock
> has drifted ahead
> > of the server clock, but does help if the token clock has drifted
> behind.  A little more
> > explanation of what the server can do to take advantage of this
> mechanism (e.g., how to
> > deal with an event-based token that is ahead of the server) would
> reduce the confusion.
>
> Possibly there is something in RFC4226, section 7.4 which could be
> referenced or re-used?  It seems to assume that the server itself knows
> the token seed, which may not be a valid assumption, so perhaps not.

Resynchronization in the algorithms I am familiar with involves the server =
resetting its OTP search window and the system in the ID allows the client =
to send an additional value to help the server do this.  This is just as de=
scribed in RFC4226.

How about the following clarification text:

Methods to recover from this type of situation are OTP algorithm specific b=
ut may involve the client sending a sequence of OTP
values to allow the server to further validate the correct position in its =
search window  (see section 7.4 of [RFC4226] for an example).

--Gareth

From gareth.richards@rsa.com  Fri Aug 26 08:03:20 2011
Return-Path: <gareth.richards@rsa.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F94A21F8BAE; Fri, 26 Aug 2011 08:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C62Pasd0RqHl; Fri, 26 Aug 2011 08:03:19 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 69EDF21F8BAC; Fri, 26 Aug 2011 08:03:19 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QF4XhC020025 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2011 11:04:33 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 26 Aug 2011 11:04:26 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QF4PCZ007391; Fri, 26 Aug 2011 11:04:26 -0400
Received: from MX11A.corp.emc.com ([169.254.1.161]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Fri, 26 Aug 2011 11:04:25 -0400
From: <gareth.richards@rsa.com>
To: <david.black@emc.com>, <hartmans-ietf@mit.edu>
Date: Fri, 26 Aug 2011 11:04:22 -0400
Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: Acxiy1Wkpn0juVxqT8+Kvj0JYZK7NgAXLZWgADZS54A=
Message-ID: <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 26 Aug 2011 09:06:48 -0700
Cc: ietf-krb-wg@lists.anl.gov, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 15:03:20 -0000

> > Why should we require that alg-ids be registered URIs?
>
> That's not my concern - the existing first paragraph of the IANA
> considerations section in the draft requires IANA registration (or at
> least tries to) by pointing to the PSKC registry.  My concern is that
> if this is going to be done, it needs to be done right (duh!), and the
> current text is insufficient. Please take the issue of whether to use
> IANA for this purpose up with Gareth and the WG.
>
> > I have no problem with the IETF registering its algorithms there, or
> us
> > encouraging people to register them there, but it's a URI. What
> purpose
> > is served by forcing registration?
>
> Hmm - more than one URI for the same algorithm might cause
> interoperability problems.
>

Some form of identifier will be required for the otp-algID in the PA-OTP-CH=
ALLENGE and the PA-OTP-REQUEST and from what I remember about when this was=
 first discussed, it was agreed that it would make sense to use the registr=
y of identifiers already being established for PSKC rather than produce a d=
uplicate one.  My assumption was that a registry would be required to ensur=
e that the URIs were unique.

--Gareth



>
> > -----Original Message-----
> > From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> > Sent: Wednesday, August 24, 2011 10:04 PM
> > To: Black, David
> > Cc: Richards, Gareth; gen-art@ietf.org; ietf@ietf.org; ietf-krb-
> wg@lists.anl.gov; hartmans-
> > ietf@mit.edu; stephen.farrell@cs.tcd.ie
> > Subject: Re: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
> >
> > >>>>>   <david.black@emc.com> writes:
> >
> >
> >     > [1] In section 6.1 at the top of p.28, I don't believe that the
> >     > use of lower case "recommended" is a strong enough warning
> about
> >     > the danger in using anonymous PKINIT because it exposes the OTP
> >     > value:
> >
> >     >    It is therefore recommended that anonymous PKINIT not be
> used
> >     > with OTP algorithms that require the OTP value to be sent to
> the
> >     > KDC and that careful consideration be made of the security
> >     > implications before it is used with other algorithms such as
> those
> >     > with short OTP values.
> >
> >     > At a minimum, that warning should be in upper-case:
> >
> >     >    It is therefore RECOMMENDED that anonymous PKINIT not be
> used
> >     > with OTP algorithms that require the OTP value to be sent to
> the
> >     > KDC. In addition, the security implications should be carefully
> >     > considered before anonymous PKINIT is used with other
> algorithms
> >     > such as those with short OTP values.
> >
> >     > Beyond that, the security issue in the first sentence may be
> >     > severe enough to justify a prohibition, so the following would
> >     > also be acceptable:
> >
> >     >    Therefore anonymous PKINIT SHALL NOT be used with OTP
> >     > algorithms that require the OTP value to be sent to the KDC. In
> >     > addition, the security implications should be carefully
> considered
> >     > before anonymous PKINIT is used with other algorithms such as
> >     > those with short OTP values.
> >
> > I definitely agree that we should use RFC 2119 language.
> > Note that WG participants have questioned this text in last call for
> > other reasons.
> > Many implementations use anonymous pkinit in a mode where the KDC's
> > certificate is verified--that is the client is anonymous but the KDC
> is
> > identified through a PKI.
> > WG participants believe (and I agree) that the security concern does
> not
> > apply at all in this case.
> > So, the text needs reworking.
> >
> >     > [2] In section 5, the first paragraph in the IANA
> considerations
> >     > is unclear, and following its reference to section 4.1, I don't
> >     > see any clarifying text there either.  I think Sections 4.1 and
> >     > 4.2 need to say that the value of otp-algID is a URI obtained
> from
> >     > the PSKC Algorithm URI Registry, and the first paragraph in
> >     > section 5 should say that URIs for otp-algID are to be
> registered
> >     > in that registry, see RFC 6030.
> >
> > Why should we require that alg-ids be registered URIs?  I.E. what is
> > wrong with me using
> > http://algorithms.painless-security.com/otp/best-thing-since-
> unsliced-bread
> > (or a tag URI if you like) for my OTP algorithm?
> > I have no problem with the IETF registering its algorithms there, or
> us
> > encouraging people to register them them, but it's a URI. What
> purpose
> > is served by forcing registration?


From gareth.richards@rsa.com  Fri Aug 26 08:57:55 2011
Return-Path: <gareth.richards@rsa.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E4021F8770; Fri, 26 Aug 2011 08:57:55 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWNwDyOlt3gt; Fri, 26 Aug 2011 08:57:54 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 8549421F8ABD; Fri, 26 Aug 2011 08:57:54 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QFx9KE010181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2011 11:59:09 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 26 Aug 2011 11:58:57 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7QFwvdw016160; Fri, 26 Aug 2011 11:58:57 -0400
Received: from MX11A.corp.emc.com ([169.254.1.161]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Fri, 26 Aug 2011 11:58:57 -0400
From: <gareth.richards@rsa.com>
To: <simon@josefsson.org>
Date: Fri, 26 Aug 2011 11:58:55 -0400
Subject: RE: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Topic: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Thread-Index: AcxkB7unBRSZvmP1T2y7dylyaUSG4wAATmug
Message-ID: <B1371F619AB0A94C9AC73CF2E475485B038C518909@MX11A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> <87sjoocgxs.fsf@latte.josefsson.org>
In-Reply-To: <87sjoocgxs.fsf@latte.josefsson.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Fri, 26 Aug 2011 09:06:56 -0700
Cc: gen-art@ietf.org, david.black@emc.com, hartmans-ietf@mit.edu, ietf-krb-wg@lists.anl.gov, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 15:57:55 -0000

Could we add a URI list to draft-lha-krb-wg-some-numbers-to-iana?

>
> > Some form of identifier will be required for the otp-algID in the
> > PA-OTP-CHALLENGE and the PA-OTP-REQUEST and from what I remember
> about
> > when this was first discussed, it was agreed that it would make sense
> > to use the registry of identifiers already being established for PSKC
> > rather than produce a duplicate one.  My assumption was that a
> > registry would be required to ensure that the URIs were unique.
> >
>
> I think a separate registry is needed, RFC 6030 requires several things
> from a profile that shouldn't be required in order to support Kerberos
> OTP.  See below.
>
> /Simon
>
> 12.4.  PSKC Algorithm Profile Registry
>
>    IANA has created a registry for PSKC algorithm profiles in
> accordance
>    with the principles set out in RFC 5226 [RFC5226].
>
>    As part of this registry, IANA maintains the following information:
>
>    Common Name:  The name by which the PSKC algorithm profile is
>       generally referred.
>
>    Class:  The type of PSKC algorithm profile registry entry being
>       created, such as encryption, Message Authentication Code (MAC),
>       One-Time Password (OTP), Digest.
>
>    URI:  The URI to be used to identify the profile.
>
>    Identifier Definition:  IANA will add a pointer to the specification
>       containing information about the PSKC algorithm profile
>       registration.
>
>    Algorithm Definition:  A reference to the stable document in which
>       the algorithm being used with the PSKC is defined.
>
>    Registrant Contact:  Contact information about the party submitting
>       the registration request.
>
>    Deprecated:  TRUE if this entry has been deprecated based on expert
>       approval and SHOULD not be used in any new implementations.
>       Otherwise, FALSE.
>
>    PSKC Profiling:  Information about PSKC XML elements and attributes
>       being used (or not) with this specific profile of PSKC.
>
>    PSKC algorithm profile identifier registrations are to be subject to
>    Specification Required as per RFC 5226 [RFC5226].  Updates can be
>    provided based on expert approval only.  Based on expert approval,
> it
>    is possible to mark entries as "deprecated".  A designated expert
>    will be appointed by the IESG.
>
>    IANA has added two initial values to the registry based on the
>    algorithm profiles described in Section 10.


From ned+ietf@mauve.mrochek.com  Fri Aug 26 09:25:56 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E60D21F8C4B for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 09:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MI-K3fcPlZr0 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 09:25:55 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8F45B21F8C4F for <ietf@ietf.org>; Fri, 26 Aug 2011 09:25:51 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5AUN3N9OG011VMM@mauve.mrochek.com> for ietf@ietf.org; Fri, 26 Aug 2011 09:25:50 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=utf-8
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O58KAOPFXC00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 26 Aug 2011 09:25:44 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5AUN0VTQY00VHKR@mauve.mrochek.com>
Date: Fri, 26 Aug 2011 09:14:59 -0700 (PDT)
Subject: Re: https
In-reply-to: "Your message dated Fri, 26 Aug 2011 10:41:21 -0400" <8F38C2201545EEF1F78C65E8@PST.JCK.COM>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314375990; i=@mrochek.com; bh=rDN+NTxoQsXva1+MRBnGWrrvkP00gSijQqxxEW02DnE=;  h=MIME-version:Content-type:From:Cc:Message-id:Date:Subject: In-reply-to:References:To; b=YnrCnMldxTcrGfD7Z8Aw6e/Ao7USEhbB3aTW1tpqR2n+cxAyVtMdITkOfZACeFahf cf5GgpTXFe0Zwh7it/o3u8Ykkc2uPF7tifN62Ia/mFO2260iKlEUxTd884jCffANfQ lk9Lalv8wzx9ltozmjWyvYmLuSH5EslWlMSwG7MM=
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 16:25:56 -0000

> --On Friday, August 26, 2011 09:43 -0400 Donald Eastlake
> <d3e3e3@gmail.com> wrote:

> >> Yup, but why are we using https at all? Â Who decided, and
> >> please would they undecide? Â Unexpired certificates can be
> >> circumvented, but all too often, the https parts of the web
> >> site just do not work and, more importantly, I think it wrong
> >> to use industrial grade security where none is called for.
> >
> > The mail archives (and the minutes of the physical meetings)
> > are the official record of the Working Groups, IETF, etc.
> > Those archives should be available with a reasonably high
> > level of integrity and authenticity.

> Don,

> If that is the goal, wouldn't we be lots better off just
> digitally signing those things, just as we are gradually
> starting to create signatures for I-Ds, etc.?  Verifying that
> one is talking to the right server and that the content is not
> tampered with in transit is all well and good, but it doesn't
> protect against compromised documents or a compromised server at
> all.

+1. If you want signatures, do them properly. Don't pretend a transfer
protection mechanism covering exactly one hop provides real object security,
because it doesn't.

And as for the "encrypt so the really secret stuff doesn't stand out" argument,
that's fine as long as it doesn't cause inconvenience to anyone. That's clearly
not the case here. And I'm sorry, the "mistakes were made" notion doesn't
really fly: Certificates aren't a "set it and forget it" thing, so if you
haven't noted expiration dates on someone's to-do list so they can be updated
before expiration, you're not doing it right.

				Ned

From daedulus@btconnect.com  Fri Aug 26 09:48:08 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65DCE21F856B for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 09:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eohGMcZrcLfO for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 09:48:08 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr09.btconnect.com [213.123.26.187]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC6621F854D for <ietf@ietf.org>; Fri, 26 Aug 2011 09:48:07 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr09.btconnect.com with SMTP id EDO43829; Fri, 26 Aug 2011 17:49:13 +0100 (BST)
Message-ID: <005c01cc6407$30500140$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Joel jaeggli" <joelja@bogus.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <4E57B142.4020802@bogus.com>
Subject: Re: https
Date: Fri, 26 Aug 2011 17:45:23 +0200
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.0A0B0303.4E57CE88.00FA, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.26.160616:17:7.944, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODY_PARA_IS_SENTENCE_URL, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1000_1099, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4E57CE8F.0159,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 16:48:08 -0000

----- Original Message -----
From: "Joel jaeggli" <joelja@bogus.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Friday, August 26, 2011 4:44 PM
Subject: Re: https


> It doesn't...
>
> http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html

Try the source of
http://www.ietf.org/list/discussion.html
where https: outumbers http: or
http://www.ietf.org/list/nonwg.html
where I run out of numbers before I run out of https:

Tom Petch


>
> On 8/26/11 00:18 , t.petch wrote:
> > Why does the IETF website consider it necessary to use TLS to access the
mailing
> > list archives, when they all appeared without it, or any other security, in
the
> > first place?
> >
> > Besides all the usual hassle of TLS, today the certificate is reported by IE
as
> > expired, which sort of sums it up.
> >
> > Tom Petch
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
>


From dwm@xpasc.com  Fri Aug 26 10:18:56 2011
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B98221F8BD3 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 10:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level: 
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[AWL=-0.837, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w4zob0cjVehY for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 10:18:55 -0700 (PDT)
Received: from mail.xpasc.com (mail.xpasc.com [68.164.244.189]) by ietfa.amsl.com (Postfix) with ESMTP id C4C9921F8B7F for <ietf@ietf.org>; Fri, 26 Aug 2011 10:18:55 -0700 (PDT)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 4580F100091 for <ietf@ietf.org>; Fri, 26 Aug 2011 10:20:11 -0700 (PDT)
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 iz6Urb8qhkb0; Fri, 26 Aug 2011 10:20:11 -0700
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 004C610008D for <ietf@ietf.org>; Fri, 26 Aug 2011 10:20:10 -0700 (PDT)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id p7QHK9sR023381 for <ietf@ietf.org>; Fri, 26 Aug 2011 10:20:09 -0700
Date: Fri, 26 Aug 2011 10:20:09 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Routing at the Edges of the Internet
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com>
Message-ID: <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Propel-ID: iz6Urb8qhkb0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietf@ietf.org" <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 17:18:56 -0000

On Fri, 26 Aug 2011, Worley, Dale R (Dale) wrote:

> > From: Adam Novak [interfect@gmail.com]
> > 
> > "Say I wanted to send data to my friend in the flat next to mine. It is
> > idiotic that nowadays, I would use the bottleneck subscriber line to
> > my upstream ISP and my crippled upload speed and push it all the way
> > across their infrastructure to my neighbors ISP and back to the Wifi
> > router in reach of mine."
> 
> This is a valid point, but it's also rather rare that one wants to
> send large amounts of data directly to a friend in a neighboring flat
> but one has not manually adjusting the local routing to take that into
> account.
> 
> > If each home or mobile device was essentially [its] own autonomous
> > system, what would this do to routing table size? To ASN space
> > utilization?
> 
> There must be at least a few hundred million mobile phones with data
> capability, and a similar number of homes and small businesses with
> WiFi systems.  So we can estimate that a large fraction of a billion
> entries would be added to the routing tables.  How would that work?

I don't see this as a routing difficulty since the updated tables would be
highly local to the edge routers which would only need to know about
the more precise route between peers.

BUT I see enormous issues in terms of providing the capability in a secure
form that can be successfully enabled by the average end user. Also,
this is more than a routing issue since most file sharing involves
an itermediary with both edge devices connecting to a remote server. Not
only do the edge routers need to be configured for secure edge routing,
but the systems need to have applications which would deliver data
directly.

I think that folks with a requirement for local sharing will figure out
a local solution, often sharing an AP and uplink. If there is a business
case here, it wouldn't be hard for an enterprising AP vendor to offer
APs which create a shared network, perhaps even providing the 'server'
component. Could also be a device which has two radios and hence can
connect to two (or more) in range networks.

Dave Morris

From interfect@gmail.com  Fri Aug 26 10:50:39 2011
Return-Path: <interfect@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D73421F84CF for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 10:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m2ouiVduYxxv for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 10:50:39 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2C78621F8C8F for <ietf@ietf.org>; Fri, 26 Aug 2011 10:50:32 -0700 (PDT)
Received: by qwc23 with SMTP id 23so2675480qwc.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 10:51:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=M9lOAltIyBdcagcX1qsvHMiUqctDHPXD5aGRbbS6xmw=; b=Yben9GEqPdaKps/doGXiCxJlOa5lwHiZ3FNu+EgCEWxDZB0nQ/nRPZdzM7Uo4OfY0Q 6nmg9SBtbq7nvrz9qj3dx5pAnNsB9IG8EhZj+xGpOU0HJgPK4azxBxrq/4Qs4p8gJtS/ v0xXnctpN0kHbmhkp1nOvBPIYTMg+Ic+HQHkk=
Received: by 10.229.43.206 with SMTP id x14mr1826524qce.275.1314381109100; Fri, 26 Aug 2011 10:51:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.84.146 with HTTP; Fri, 26 Aug 2011 10:51:28 -0700 (PDT)
In-Reply-To: <01O5AUN0VTQY00VHKR@mauve.mrochek.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com>
From: Adam Novak <interfect@gmail.com>
Date: Fri, 26 Aug 2011 12:51:28 -0500
Message-ID: <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>
Subject: Re: https
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 17:50:39 -0000

On Fri, Aug 26, 2011 at 11:14 AM,  <ned+ietf@mauve.mrochek.com> wrote:
>
> +1. If you want signatures, do them properly. Don't pretend a transfer
> protection mechanism covering exactly one hop provides real object security,
> because it doesn't.
>

It ensures that what you're getting is the same as what the IETF has
on file, and (assuming you trust the IETF's archive integrity, which
is a separate problem) what everyone else on the list received. It
seems to me it's more important to know that than to know that stuff
sent to the list actually came from who it claims to come from. Does
it really matter if a proposed standard wasn't really designed by who
the archive says it was designed by?

> And as for the "encrypt so the really secret stuff doesn't stand out" argument,
> that's fine as long as it doesn't cause inconvenience to anyone. That's clearly
> not the case here. And I'm sorry, the "mistakes were made" notion doesn't
> really fly: Certificates aren't a "set it and forget it" thing, so if you
> haven't noted expiration dates on someone's to-do list so they can be updated
> before expiration, you're not doing it right.

Yeah, it seems like the IETF would be on top of certificate
expiration, having invented it. But I think having the encryption is a
very good thing. Some government interests would be happy to keep
information about some aspects of IETF business away from their
citizenry, and have the resources to launch a MITM attack. (Of course,
those governments may also have the resources to sign a fake
certificate, but that is, again, a separate problem.)

Once the certificate expiration business is fixed, it should be fairly
simple to make sure it's kept up to date so that this sort of thing
doesn't happen again.

From moore@network-heretics.com  Fri Aug 26 11:07:50 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC5E21F8B5A for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:07:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.607
X-Spam-Level: 
X-Spam-Status: No, score=-3.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mwZdWwOfHuRr for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:07:49 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id B005821F8B51 for <ietf@ietf.org>; Fri, 26 Aug 2011 11:07:49 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 0572A20B0B; Fri, 26 Aug 2011 14:09:06 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 26 Aug 2011 14:09:06 -0400
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=18jImd+lcM+hFbYEAqQjjDYDSSU=; b=tz XUXVADATapgTc17MLYzHogWDIqqiZI2lPrUhFNW8wNJILA/8TQWbUb+nQwOzN2nd cJyeQV6zxiGAPvWMDNhy//Kgpomi2FId0P1kppwZxT5Wh+/qzk5h2Dr8FnV+3MUL j5k48QTVGK7y4s47GCLaKMWDpW4rr+vNak4UTkpQs=
X-Sasl-enc: Qu/yOnvUcR31dXG/rrt/3PSOdZks1nMvEQb+Qu21Fv0a 1314382145
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id AD758920783; Fri, 26 Aug 2011 14:09:05 -0400 (EDT)
Subject: Re: Routing at the Edges of the Internet
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAPv4CP-OiQ3F96skrFO7j7LfF0jBxWNNubOFTLFD_x9AGVDjVg@mail.gmail.com>
Date: Fri, 26 Aug 2011 14:08:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E43B4B4-B39B-49E1-B5B8-FEA71CCF419B@network-heretics.com>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <CAPv4CP-OiQ3F96skrFO7j7LfF0jBxWNNubOFTLFD_x9AGVDjVg@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 18:07:50 -0000

On Aug 26, 2011, at 12:03 PM, Scott Brim wrote:

> On Fri, Aug 26, 2011 at 11:04, Worley, Dale R (Dale) =
<dworley@avaya.com> wrote:
>> There must be at least a few hundred million mobile phones with data
>> capability, and a similar number of homes and small businesses with
>> WiFi systems.  So we can estimate that a large fraction of a billion
>> entries would be added to the routing tables.  How would that work?
>=20
> You do it in the endpoint.  The original poster should look at all the
> work already being done in IETF WGs (and elsewhere), e.g. 6man and
> mif, intarea and tsvwg

In other words, it's not a solved problem, and though there's wide =
recognition that the problem exists, nobody really has found a good =
solution. =20

(Though mtcp strikes me as having broader applicability than most.)

Keith


From interfect@gmail.com  Fri Aug 26 11:23:31 2011
Return-Path: <interfect@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77B5A21F8C0C for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y90im2fHyNhM for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:23:31 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id DEBC321F8B5E for <ietf@ietf.org>; Fri, 26 Aug 2011 11:23:30 -0700 (PDT)
Received: by qyk35 with SMTP id 35so2389951qyk.10 for <ietf@ietf.org>; Fri, 26 Aug 2011 11:24:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=o9jZQRAE0YabzRG9Hr1pnwe7vde9ofj1Cpymeu2rMv4=; b=km/oOwLtZYU1v3NYPyCd6R1GJhqaBDQeW+GDkQ3FwM3Ym19mY7ymhIfnSTFMjvLsnH ApWVrcnAc+g7yDt2pDHJVe/J1/XP50tbxXRRmGtfpgACKMjsvs2t94JHEFd4NSQuSr/h oR/ypKArCuQ3P0dAH6SVmK/9OQF75nIkXX6nE=
Received: by 10.229.239.129 with SMTP id kw1mr1926016qcb.266.1314383086053; Fri, 26 Aug 2011 11:24:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.84.146 with HTTP; Fri, 26 Aug 2011 11:24:26 -0700 (PDT)
In-Reply-To: <4E57E23A.5070605@santronics.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com> <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com> <4E57E23A.5070605@santronics.com>
From: Adam Novak <interfect@gmail.com>
Date: Fri, 26 Aug 2011 13:24:26 -0500
Message-ID: <CADPp2fC6qOvZig34coQ95Nk_yEgsjKRH=NAyvZAEumEx4HxrBg@mail.gmail.com>
Subject: Re: https
To: Hector Santos <hsantos@santronics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 18:23:31 -0000

On Fri, Aug 26, 2011 at 1:13 PM, Hector Santos <hsantos@santronics.com> wro=
te:
> Makes you wonder. Why is the concept of expiration required? =A0Did the I=
ETF
> expire, die? =A0Did its value as an Organization go down and only valid o=
n a
> year to year basis?

As I understand it, expiration is supposed to solve the problem of
someone getting their hands on your old certificates and impersonating
you. In order to impersonate you, not only do they have to get into
your system, they have to have done it in the last year or so.

It also keeps certificates for domains from outliving domain
registrations for too long. If you don't have the domain when you go
to renew the certificate, the CA shouldn't renew it.

I guess it also keeps revocation lists short. You only have to
remember that a certain certificate was compromised until it expires,
instead of forever.

From ned+ietf@mauve.mrochek.com  Fri Aug 26 12:08:49 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE5FA21F8C6C for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7M8Y+0Yj4NFa for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:08:49 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id DB23921F8B44 for <ietf@ietf.org>; Fri, 26 Aug 2011 12:08:48 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5B0C73VGW014G56@mauve.mrochek.com> for ietf@ietf.org; Fri, 26 Aug 2011 12:08:50 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O58KAOPFXC00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 26 Aug 2011 12:08:44 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5B0C4KUT200VHKR@mauve.mrochek.com>
Date: Fri, 26 Aug 2011 11:12:24 -0700 (PDT)
Subject: Re: https
In-reply-to: "Your message dated Fri, 26 Aug 2011 12:51:28 -0500" <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com> <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>
To: Adam Novak <interfect@gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314385770; i=@mrochek.com; bh=tWLgk4/kWg54B3+tyX4OrJkgZT0WGJQw1gmXLG4bJyg=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=pOvC49HU3gmh7HQa5K/ZrbdBlkoS0iypHchQ9382pN1OCBnWbxdqGo1Td82Y6wUlR Lkf7lWxi7LsZSloj9qPT4cQhk4REceAvoX3dpzHJRAj067KuoE11eHy1pw88N7ykgw +xCTJMIWEJjJgF8aEM9g0b8j2k8qse51W+zonXss=
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 19:08:49 -0000

> On Fri, Aug 26, 2011 at 11:14 AM,  <ned+ietf@mauve.mrochek.com> wrote:
> >
> > +1. If you want signatures, do them properly. Don't pretend a transfer
> > protection mechanism covering exactly one hop provides real object security,
> > because it doesn't.
> >

> It ensures that what you're getting is the same as what the IETF has
> on file,

No, it really doesn't do that. There can be, and usually are, a lot of steps
involves besides the one https hop.

> and (assuming you trust the IETF's archive integrity, which
> is a separate problem)

On the contrary, it's the same problem. You're just pretending that solving an
insignificant subset of that problem is useful. It isn't.

> what everyone else on the list received.

This, OTOH, *is* a separate problem, one that isn't addressed in any way by
https on archive archive access. Nor does a signed archive address this issue.

Nonrepudiation of delivery is in fact a very difficult problem to solve - the
algorithms I'm aware of for it either involve a TTP or are exceptionaly ugly -
and the fact that the architecture of our email services isn't designed for it
doesn't exactly help. (In case you care, it's the nontransactional nature of
POP and IMAP that gets in the way of doing nonrepudiation of delivery at the
email protocol level.)

We're very lucky that we don't operate in a regime where this is actually a
requirement. (And such regimes do exist, although the solutions they actually
use tend to be hacks.)

> It
> seems to me it's more important to know that than to know that stuff
> sent to the list actually came from who it claims to come from. Does
> it really matter if a proposed standard wasn't really designed by who
> the archive says it was designed by?

And now you're talking about yet a third problem - nonrepudiation of
submission. It's completely doable, but only by significantly increasing the
barriers to participation by requiring signed messages. I don't believe the
benefits come even close to the costs.

> > And as for the "encrypt so the really secret stuff doesn't stand out" argument,
> > that's fine as long as it doesn't cause inconvenience to anyone. That's clearly
> > not the case here. And I'm sorry, the "mistakes were made" notion doesn't
> > really fly: Certificates aren't a "set it and forget it" thing, so if you
> > haven't noted expiration dates on someone's to-do list so they can be updated
> > before expiration, you're not doing it right.

> Yeah, it seems like the IETF would be on top of certificate
> expiration, having invented it. But I think having the encryption is a
> very good thing. Some government interests would be happy to keep
> information about some aspects of IETF business away from their
> citizenry, and have the resources to launch a MITM attack. (Of course,
> those governments may also have the resources to sign a fake
> certificate, but that is, again, a separate problem.)

I'm sorry, but the notion that the present use of https provides any
sort of protection against this sort of thing is just silly. The simple
facts that the archives are also available via regular http and that
there is no stated policy about the availability of archives via https
means the present setup is completely vulnerable to downgrade attacks.

Again, if you really care about this sort of stuff, the archives need to be
timestamped and signed. 

> Once the certificate expiration business is fixed, it should be fairly
> simple to make sure it's kept up to date so that this sort of thing
> doesn't happen again.

10+ years of experience with multiple certificates having multiple failures
says this is, at best, a crapshoot.

				Ned

From interfect@gmail.com  Fri Aug 26 12:21:11 2011
Return-Path: <interfect@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7EC21F8C8F for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtkBFDJYjaL8 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:21:11 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1B57421F8BB8 for <ietf@ietf.org>; Fri, 26 Aug 2011 12:21:11 -0700 (PDT)
Received: by qyk34 with SMTP id 34so602184qyk.10 for <ietf@ietf.org>; Fri, 26 Aug 2011 12:22:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=sO0aB3XGLCoit2TaMzoOw75AWpV7S6OO4GTeMb3mA/4=; b=uKiEVPSe0rRPW2S92+mqZFtIvkSG1sF61aEHKhXxwubVjXyj5GIQ3g1QhMDCTxPhVu LCCKXLHphCQV3Y5IdoaVmaHd/j8M6hZQSTspgxMBKRq2jF1zaORMs3UdikGZ51cSAHDT NMDFrU9eVrKPFd0eNrl6Z3oAAdXjDpN4c6/Q4=
Received: by 10.229.10.216 with SMTP id q24mr429215qcq.0.1314386547114; Fri, 26 Aug 2011 12:22:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.84.146 with HTTP; Fri, 26 Aug 2011 12:22:07 -0700 (PDT)
In-Reply-To: <01O5B0C4KUT200VHKR@mauve.mrochek.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com> <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com> <01O5B0C4KUT200VHKR@mauve.mrochek.com>
From: Adam Novak <interfect@gmail.com>
Date: Fri, 26 Aug 2011 14:22:07 -0500
Message-ID: <CADPp2fDghwuuY557ps2DAE6zffAoVJobJOsS6wQu3HLQ=KFfLw@mail.gmail.com>
Subject: Re: https
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 19:21:11 -0000

On Fri, Aug 26, 2011 at 1:12 PM, Ned Freed <ned.freed@mrochek.com> wrote:
>> It ensures that what you're getting is the same as what the IETF has
>> on file,
>
> No, it really doesn't do that. There can be, and usually are, a lot of steps
> involves besides the one https hop.
>

What other steps are there? HTTPS prevents what the web server sends
from being tampered with on its way to the browser. If the web server
storing the archives is itself trusted, this would seem to be all that
is needed.

Obviously HTTPS is not a solution to long-term preservation of the
integrity of the mailing list database itself. What protections, if
any, are currently in place to protect the archive from tampering on
IETF's end? Perhaps the whole thing should be signed by someone
official at regular intervals?

>
> I'm sorry, but the notion that the present use of https provides any
> sort of protection against this sort of thing is just silly. The simple
> facts that the archives are also available via regular http and that
> there is no stated policy about the availability of archives via https
> means the present setup is completely vulnerable to downgrade attacks.
>

A downgrade attack is certainly possible. But there are measures
available to ensure that, once an HTTPS connection has been
established once, future HTTP sessions will be rejected client-side.
And creating an official policy and going HTTPS-only could be done
relatively easily. If HTTPS everywhere is where the Web should be
going, then IETF should be leading the charge.

> 10+ years of experience with multiple certificates having multiple failures
> says this is, at best, a crapshoot.
>

For what reasons? Is it that things scheduled every year or every ten
years are easy for admins to miss? Or is it that it's hard to stay on
top of certificate revocations when they occur?

From moore@network-heretics.com  Fri Aug 26 12:26:44 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6083821F8C80 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.607
X-Spam-Level: 
X-Spam-Status: No, score=-3.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vtk6c+qnT94K for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:26:43 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 94AFC21F8C7E for <ietf@ietf.org>; Fri, 26 Aug 2011 12:26:43 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 6A99E20C1F; Fri, 26 Aug 2011 15:28:00 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 26 Aug 2011 15:28:00 -0400
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=wsiIpc8/wKIi5QQjUEdsrUypFpo=; b=RX Ipumc5fWDdzInH1jNiaBTosuuvt/rY9rWjpgb30IxpgyGBy9tApO1xUEaAM1isoZ ffPzdEJm/6X3P0fQ/giNWxIaVOpMhxCNrFvezZYzwtmNaALEX96ZCjAbIjvlhozZ Mp1qqAGGjYYSZM0g6xLPP7tk0fSfzkAiRbGA3AVrg=
X-Sasl-enc: wadosfAPLqqLzxwDJWt7NkY2VL/Rk6Mqv99UEpDiRCH3 1314386880
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 368CD920785; Fri, 26 Aug 2011 15:28:00 -0400 (EDT)
Subject: Re: https
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CADPp2fDghwuuY557ps2DAE6zffAoVJobJOsS6wQu3HLQ=KFfLw@mail.gmail.com>
Date: Fri, 26 Aug 2011 15:27:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D220AF43-15D9-4D7F-ABBD-DDD88449F7DB@network-heretics.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com> <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com> <01O5B0C4KUT200VHKR@mauve.mrochek.com> <CADPp2fDghwuuY557ps2DAE6zffAoVJobJOsS6wQu3HLQ=KFfLw@mail.gmail.com>
To: Adam Novak <interfect@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Ned Freed <ned.freed@mrochek.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 19:26:44 -0000

On Aug 26, 2011, at 3:22 PM, Adam Novak wrote:

> On Fri, Aug 26, 2011 at 1:12 PM, Ned Freed <ned.freed@mrochek.com> =
wrote:
>>> It ensures that what you're getting is the same as what the IETF has
>>> on file,
>>=20
>> No, it really doesn't do that. There can be, and usually are, a lot =
of steps
>> involves besides the one https hop.
>>=20
>=20
> What other steps are there? HTTPS prevents what the web server sends
> from being tampered with on its way to the browser. If the web server
> storing the archives is itself trusted, this would seem to be all that
> is needed.

There can be web proxies on the front end (if the client is configured =
to use them) and the web server itself can be implemented in such a way =
as to retrieve content from other servers (via a number of means, e.g. =
NFS, CIFS, web services calls, sql calls).  Though I don't know whether =
the latter is the case for content served from IETF's servers.

Keith


From melinda.shore@gmail.com  Fri Aug 26 12:31:17 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74DA321F8C76 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.539
X-Spam-Level: 
X-Spam-Status: No, score=-3.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcWKuKMfSPYI for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 12:31:16 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3025921F8C63 for <ietf@ietf.org>; Fri, 26 Aug 2011 12:31:13 -0700 (PDT)
Received: by qyk34 with SMTP id 34so607544qyk.10 for <ietf@ietf.org>; Fri, 26 Aug 2011 12:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=XY45R8iP8W/PZBzhkp/DXd3HA1gAWbDm+lvh6nWkJEE=; b=L7i55EglCxVXxwCXl/KI1S9zPo0Iabgz4vTRVLptAbWBVjHaUvsikXXim1RNFEXreC nbqzWntPjyQVpjZ3qB9Qe6MRxHtkIBC7ZEiFzsqQELX/A0Iyiv+11v96dmI28RMZKs3k Y4DGJL61cqI35rTN55l3M6mcqv4axLD8jLVj4=
Received: by 10.142.185.3 with SMTP id i3mr806260wff.399.1314387149547; Fri, 26 Aug 2011 12:32:29 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id e8sm3423780pbc.8.2011.08.26.12.32.27 (version=SSLv3 cipher=OTHER); Fri, 26 Aug 2011 12:32:28 -0700 (PDT)
Message-ID: <4E57F4CE.6070309@gmail.com>
Date: Fri, 26 Aug 2011 11:32:30 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>	<005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>	<CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>	<8F38C2201545EEF1F78C65E8@PST.JCK.COM>	<01O5AUN0VTQY00VHKR@mauve.mrochek.com>	<CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>	<01O5B0C4KUT200VHKR@mauve.mrochek.com> <CADPp2fDghwuuY557ps2DAE6zffAoVJobJOsS6wQu3HLQ=KFfLw@mail.gmail.com>
In-Reply-To: <CADPp2fDghwuuY557ps2DAE6zffAoVJobJOsS6wQu3HLQ=KFfLw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 19:31:17 -0000

On 08/26/2011 11:22 AM, Adam Novak wrote:
> For what reasons? Is it that things scheduled every year or every ten
> years are easy for admins to miss? Or is it that it's hard to stay on
> top of certificate revocations when they occur?

Firewall researchers have found at least one error of some sort in
99% (yes, really) of the firewall rulesets they've examined.  If
I had to guess how many PKI deployments have problems, I'd put it in
the same ballpark.  They seem to fall into several broad categories
1) naming (including SANs), 2) expiration, 3) faulty trust
establishment.  These may or may not be fixable, but what doesn't
appear to be fixable is that too people don't really understand what 
certificates represent, the difference between a certificate and
a key, or what it means to TLS-protect traffic.

Listen to Ned, Adam.  He's right.

Melinda

From eburger@standardstrack.com  Fri Aug 26 13:14:40 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4BED21F8BD8 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RfUr2GvtvwPE for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:14:40 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0C85221F8AFB for <ietf@ietf.org>; Fri, 26 Aug 2011 13:14:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=zSqI9fRj7OV1ohK7ATJf603+gNpkTSjqWORoYprIghfYSjjohzAxdxT8/q7lGvrysGgHXBUubPQrCqt6joSzANEQioBe6434Q411oswIauTTNgnc9O6dJlHCumSbnwTL;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Qx2ol-0007t3-C3 for ietf@ietf.org; Fri, 26 Aug 2011 13:15:55 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-71--1072377235; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: https
Date: Fri, 26 Aug 2011 16:15:55 -0400
In-Reply-To: <4E57F4CE.6070309@gmail.com>
To: IETF-Discussion list <ietf@ietf.org>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>	<005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>	<CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>	<8F38C2201545EEF1F78C65E8@PST.JCK.COM>	<01O5AUN0VTQY00VHKR@mauve.mrochek.com>	<CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>	<01O5B0C4KUT200VHKR@mauve.mrochek.com> <CADPp2fDghwuuY557ps2DAE6zffAoVJobJOsS6wQu3HLQ=KFfLw@mail.gmail.com> <4E57F4CE.6070309@gmail.com>
Message-Id: <EF4B68C9-C29C-434C-A083-9E8D505904FF@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 20:14:40 -0000

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

Two thoughts.

On the one hand, Ned is absolutely correct: the thing we want to make =
absolutely sure of is the integrity of the object. The way of doing that =
is making sure the object itself can prove its integrity.  In the =
messaging world, we do this with S/MIME.  The use of TLS for SMTP or =
IMAP does not convey any integrity assertions for the object.  Note this =
object should be signed by me when you receive it, by the way.

On the other hand, while TLS is not at all sufficient for the integrity =
of the object, it is necessary to protect the individual accessing the =
object.  There are a number of countries where asking for the RFCs =
relating to privacy, security, and threats to such too many times could =
get you arrested.  Likewise, the presumption is the object might be =
signed, but it would be insane and useless to encrypt the object.  =
However, there are many, many times one would want the object encrypted, =
even if only to compress it.

Given that, the question should not be, "Why are we using TLS if the =
object is not private?," but "What are we not using secure connections =
for all IETF access, over any modality?"

One of the answers seems to be, "Because it sucks."  That is the =
sentiment of the message below.

So we are eating our dog food, and we are getting indigestion.  Sounds =
like an opportunity to fix it!

--
- Eric

On Aug 26, 2011, at 3:32 PM, Melinda Shore wrote:

> On 08/26/2011 11:22 AM, Adam Novak wrote:
>> For what reasons? Is it that things scheduled every year or every ten
>> years are easy for admins to miss? Or is it that it's hard to stay on
>> top of certificate revocations when they occur?
>=20
> Firewall researchers have found at least one error of some sort in
> 99% (yes, really) of the firewall rulesets they've examined.  If
> I had to guess how many PKI deployments have problems, I'd put it in
> the same ballpark.  They seem to fall into several broad categories
> 1) naming (including SANs), 2) expiration, 3) faulty trust
> establishment.  These may or may not be fixable, but what doesn't
> appear to be fixable is that too people don't really understand what =
certificates represent, the difference between a certificate and
> a key, or what it means to TLS-protect traffic.
>=20
> Listen to Ned, Adam.  He's right.
>=20
> Melinda
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-71--1072377235
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MjYyMDE1NTVaMCMGCSqGSIb3DQEJ
BDEWBBQYBx4KyWsiILnsaSvI6ZXjVqibETCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBACQ7gUHl3Mj28S5h/Bp6pG49PXOCVCJpK8MYHAVx9BNxB2eM
oWVQUhP/dM8kBgPx/J4bYAphG+0EbM3ZdLlszW6lxM0FqsySFIVNZBV4VoBiKrcxd2W3tP5ly+Pu
P/GUtIG/MSYX/1RC9mF09vsj0eQ8kabIBwQakZg++OoTj9T+sg+1ljODlRTa6cnpQXKwBopQziWD
2f1IqFSGU07u0Y7hP2AGcn+X2v/zH3jZ9xC5+WSHLj7HRX27tMPcxPrJKeq8pkfQMqVx1ylNyZpT
5WR75STMFPg5qXUIbJfzM4/EuFUzJqoezdgH7wKvcKXFyvlFOS914C6DWZSZoQxmgsoAAAAAAAA=

--Apple-Mail-71--1072377235--

From dougb@dougbarton.us  Fri Aug 26 13:48:37 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1005E21F8A23 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.506
X-Spam-Level: 
X-Spam-Status: No, score=-3.506 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vq20zcJmiWqR for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:48:36 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF8021F87F9 for <ietf@ietf.org>; Fri, 26 Aug 2011 13:48:35 -0700 (PDT)
Received: (qmail 9861 invoked by uid 399); 26 Aug 2011 20:49:49 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 26 Aug 2011 20:49:49 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4E5806EC.5050304@dougbarton.us>
Date: Fri, 26 Aug 2011 13:49:48 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>
In-Reply-To: <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 20:48:37 -0000

On 08/26/2011 10:20, David Morris wrote:
> I don't see this as a routing difficulty since the updated tables would be
> highly local to the edge routers which would only need to know about
> the more precise route between peers.
> 
> BUT I see enormous issues in terms of providing the capability in a secure
> form that can be successfully enabled by the average end user. Also,
> this is more than a routing issue since most file sharing involves
> an itermediary with both edge devices connecting to a remote server. Not
> only do the edge routers need to be configured for secure edge routing,
> but the systems need to have applications which would deliver data
> directly.

I have a related-but-different example of how end nodes being able to
know/discover direct paths to one another could be useful. Imagine a
busy server network with some web servers over here, some sql servers
over there, etc. All of these systems are on the same network, same
switch fabric, and have the same gateway address. In an ideal world I
would like them to be able to know that they can speak directly to one
another without having to go through the gateway (and without my having
to manually inject static routes on the hosts, which of course is both
painful and un-scale'y.


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 interfect@gmail.com  Fri Aug 26 13:56:16 2011
Return-Path: <interfect@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC82521F8B59 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z97fz9VQbauc for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:56:16 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0D221F8B4D for <ietf@ietf.org>; Fri, 26 Aug 2011 13:56:16 -0700 (PDT)
Received: by qwc23 with SMTP id 23so2790946qwc.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 13:57:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=smP4p8vSftGLakxLbXFOaSnvu8qufAFYARsOqW/zLdM=; b=W/FRhqSUZpM5xdeW8lCbzfMWPi1t0tUnIDyqPniz37DlaSP6zSoWEwxEWn27nA7U2T PgErBCmC9UCuNYx7nxhbyvklEIYhJkEh5GcNvrMs3drb0nKEYAEHPgzdRnDAz0B0IbXZ S/yHwoR5nzSwKpEb3B50IHo2jIQY2SxyL23Hw=
Received: by 10.229.240.72 with SMTP id kz8mr2125644qcb.114.1314392253067; Fri, 26 Aug 2011 13:57:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.84.146 with HTTP; Fri, 26 Aug 2011 13:57:13 -0700 (PDT)
In-Reply-To: <4E5806EC.5050304@dougbarton.us>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com> <4E5806EC.5050304@dougbarton.us>
From: Adam Novak <interfect@gmail.com>
Date: Fri, 26 Aug 2011 15:57:13 -0500
Message-ID: <CADPp2fAPN3tOE-XiLuJ71XLQ2oMd5W0D93iPkuuYqHA-fC0=+A@mail.gmail.com>
Subject: Re: Routing at the Edges of the Internet
To: Doug Barton <dougb@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 20:56:16 -0000

On Fri, Aug 26, 2011 at 3:49 PM, Doug Barton <dougb@dougbarton.us> wrote:
>
> I have a related-but-different example of how end nodes being able to
> know/discover direct paths to one another could be useful. Imagine a
> busy server network with some web servers over here, some sql servers
> over there, etc. All of these systems are on the same network, same
> switch fabric, and have the same gateway address. In an ideal world I
> would like them to be able to know that they can speak directly to one
> another without having to go through the gateway (and without my having
> to manually inject static routes on the hosts, which of course is both
> painful and un-scale'y.

Shouldn't that be covered by the subnet mask? As long as they know
they're on the same subnet (and ARP broadcasts will reach everyone)
they should just ARP for each other and not involve the router at all.

If they are on different IP subnets, but the same Ethernet, then we
can either come up with a new way to do routing, or tell people not to
number things that way. Perhaps a subnet mask or CIDR prefix is not
expressive enough?

From dougb@dougbarton.us  Fri Aug 26 13:59:00 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3D8121F8B88 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.197
X-Spam-Level: 
X-Spam-Status: No, score=-3.197 tagged_above=-999 required=5 tests=[AWL=-0.198, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOe3edpB8TLy for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 13:59:00 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id EAADF21F8B5F for <ietf@ietf.org>; Fri, 26 Aug 2011 13:58:59 -0700 (PDT)
Received: (qmail 22484 invoked by uid 399); 26 Aug 2011 21:00:14 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 26 Aug 2011 21:00:14 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4E58095D.2040509@dougbarton.us>
Date: Fri, 26 Aug 2011 14:00:13 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0
MIME-Version: 1.0
To: Joel jaeggli <joelja@bogus.com>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <4E57B142.4020802@bogus.com>
In-Reply-To: <4E57B142.4020802@bogus.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: webmaster@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 20:59:00 -0000

Joel,

I don't know what "It doesn't" is supposed to mean, but visiting
https://www.ietf.org/* today with firefox it is still reporting that the
certificate expired yesterday.

Given the volume of discussion about the topic starting yesterday when
the problem started one could easily make a case for "it's still broken"
being a significant "issue."

cc'ing the address listed as "Report Website Errors" on the home page.


Doug


On 08/26/2011 07:44, Joel jaeggli wrote:
> It doesn't...
> 
> http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html
> 
> On 8/26/11 00:18 , t.petch wrote:
>> Why does the IETF website consider it necessary to use TLS to access the mailing
>> list archives, when they all appeared without it, or any other security, in the
>> first place?
>>
>> Besides all the usual hassle of TLS, today the certificate is reported by IE as
>> expired, which sort of sums it up.
>>
>> Tom Petch
>>
>> _______________________________________________
>> 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



-- 

	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 dworley@avaya.com  Fri Aug 26 14:06:22 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 387C921F8B9D for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 14:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6CcjtJVyHdgW for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 14:06:21 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id AF2F821F8B25 for <ietf@ietf.org>; Fri, 26 Aug 2011 14:06:21 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAOIJWE7GmAcF/2dsb2JhbABDqCZ3gUABAQEBAgESKDETCwIBCA0IIRAyJQEBBAESCBqHUJ43Apw1hWxgBJhFi3E
X-IronPort-AV: E=Sophos;i="4.68,287,1312171200"; d="scan'208";a="300141768"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 26 Aug 2011 17:07:38 -0400
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; 26 Aug 2011 17:03:31 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 26 Aug 2011 17:07:37 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Doug Barton <dougb@dougbarton.us>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 26 Aug 2011 17:05:19 -0400
Subject: RE: Routing at the Edges of the Internet
Thread-Topic: Routing at the Edges of the Internet
Thread-Index: AcxkMccWR3AYRPmiRLmAXvQGbo/6cAAAhZcI
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5864@DC-US1MBEX4.global.avaya.com>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>, <4E5806EC.5050304@dougbarton.us>
In-Reply-To: <4E5806EC.5050304@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 21:06:22 -0000

> From: Doug Barton [dougb@dougbarton.us]
>=20
> All of these systems are on the same network, same
> switch fabric, and have the same gateway address. In an ideal world I
> would like them to be able to know that they can speak directly to one
> another without having to go through the gateway (and without my having
> to manually inject static routes on the hosts, which of course is both
> painful and un-scale'y.

I'm no expert in this, but isn't this what ICMP Redirect messages are
for?  Aren't routers required to generate them in these cases?

Dale

From dougb@dougbarton.us  Fri Aug 26 14:07:25 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DECC021F8C1E for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 14:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.481
X-Spam-Level: 
X-Spam-Status: No, score=-3.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zo6oe2YrPxwp for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 14:07:22 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7783D21F8C1D for <ietf@ietf.org>; Fri, 26 Aug 2011 14:07:22 -0700 (PDT)
Received: (qmail 32525 invoked by uid 399); 26 Aug 2011 21:08:37 -0000
Received: from unknown (HELO 172-17-198-245.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 26 Aug 2011 21:08:37 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4E580B54.2090304@dougbarton.us>
Date: Fri, 26 Aug 2011 14:08:36 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0
MIME-Version: 1.0
To: Adam Novak <interfect@gmail.com>
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com> <4E5806EC.5050304@dougbarton.us> <CADPp2fAPN3tOE-XiLuJ71XLQ2oMd5W0D93iPkuuYqHA-fC0=+A@mail.gmail.com>
In-Reply-To: <CADPp2fAPN3tOE-XiLuJ71XLQ2oMd5W0D93iPkuuYqHA-fC0=+A@mail.gmail.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 21:07:26 -0000

On 08/26/2011 13:57, Adam Novak wrote:
> On Fri, Aug 26, 2011 at 3:49 PM, Doug Barton <dougb@dougbarton.us> wrote:
>>
>> I have a related-but-different example of how end nodes being able to
>> know/discover direct paths to one another could be useful. Imagine a
>> busy server network with some web servers over here, some sql servers
>> over there, etc. All of these systems are on the same network, same
>> switch fabric, and have the same gateway address. In an ideal world I
>> would like them to be able to know that they can speak directly to one
>> another without having to go through the gateway (and without my having
>> to manually inject static routes on the hosts, which of course is both
>> painful and un-scale'y.
> 
> Shouldn't that be covered by the subnet mask?

Mostly, yes of course, but I'm dramatically simplifying my example for
dramatic effect. :)

> As long as they know
> they're on the same subnet (and ARP broadcasts will reach everyone)
> they should just ARP for each other and not involve the router at all.
> 
> If they are on different IP subnets, but the same Ethernet,

Yes, this is more often the case that I'm dealing with. (Working on
fixing a problem I inherited for a new client, so per your comment below
"don't number that way" may be the right answer.)

Doug


> then we
> can either come up with a new way to do routing, or tell people not to
> number things that way. Perhaps a subnet mask or CIDR prefix is not
> expressive enough?



-- 

	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 michel@arneill-py.sacramento.ca.us  Fri Aug 26 14:45:49 2011
Return-Path: <michel@arneill-py.sacramento.ca.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B691F21F8A62 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 14:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level: 
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WC8S8zBk7hIx for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 14:45:49 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 2E4FC21F8A58 for <ietf@ietf.org>; Fri, 26 Aug 2011 14:45:49 -0700 (PDT)
Content-class: urn:content-classes:message
Subject: RE: Routing at the Edges of the Internet
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Aug 2011 14:47:05 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF6AE@newserver.arneill-py.local>
X-MimeOLE: Produced By Microsoft Exchange V6.5
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5864@DC-US1MBEX4.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Routing at the Edges of the Internet
Thread-Index: AcxkMccWR3AYRPmiRLmAXvQGbo/6cAAAhZcIAAArMbA=
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com><CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com><Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>, <4E5806EC.5050304@dougbarton.us> <CD5674C3CD99574EBA7432465FC13C1B222B1F5864@DC-US1MBEX4.global.avaya.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 21:45:49 -0000

> Worley, Dale R wrote:
> I'm no expert in this, but isn't this what ICMP Redirect messages
> are for?  Aren't routers required to generate them in these cases?

Unfortunately, ICMP redirects are often broken. It is a well-known issue
that the introduction of Windows XP SP2 (a while ago) and the Windows
Firewall did that.

The typical setup was a network with multiple subnets/VLANs and a
firewall/NAT/VPN box. The default gateway for the Internet and remote
VPN tunnels was the firewall, the default gateway for other VLANs was
the L3 switch that was doing the inter-VLAN routing.=20

In theory, the host would send the traffic for a given destination, if
the traffic was an inside VLAN the firewall would send the redirect to
the host, forward the traffic to the L3 switch, and further traffic
would go directly to the L3 switch as the result of the ICMP redirect.
Before XP SP2 this was straightforward, a "route print" on the host
would indeed show the new route installed by the ICMP redirect.

In practice after XP SP2, the result was that the firewall indeed sent
the redirect to the host but since the host ignored it and kept sending
traffic to the wrong gateway, a large amount of firewall-to-L3switch was
present, effectively clogging the network at times.

Maintaining a correct routing table in hosts has always been the
Achilles' heel of networks with multiple gateways, which is why many
enterprise network operators tend to design a one-gateway solution.

Michel.


From brian.e.carpenter@gmail.com  Fri Aug 26 15:45:37 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDBC21F8C8E for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 15:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.584
X-Spam-Level: 
X-Spam-Status: No, score=-103.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXgu5p2kuKYO for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 15:45:36 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 71BD821F8C8D for <ietf@ietf.org>; Fri, 26 Aug 2011 15:45:36 -0700 (PDT)
Received: by fxe6 with SMTP id 6so3197078fxe.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 15:46:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=iUhILOGkP4WRrKLjtLzLb91QASnJgGhWRRSpxblzPKw=; b=QrdNmKluZPRgv71lFaGn/3KbeCJtqoUR+tt7SRyuQO3f0qvxw8/mqUVRKC9l9zJ8ks F9iShzp7kN0KQJA2s35HEmmumBiQ6AsoQHrGqpbr8ZTHlXY+KI4TZ5AFqtogLxxmORzh qN19/nI0MYS3Cj6/o6sBKK9kxHU+wC7ruqC6g=
Received: by 10.223.9.217 with SMTP id m25mr2353584fam.122.1314398813139; Fri, 26 Aug 2011 15:46:53 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id c18sm1685845fah.15.2011.08.26.15.46.48 (version=SSLv3 cipher=OTHER); Fri, 26 Aug 2011 15:46:52 -0700 (PDT)
Message-ID: <4E582250.8010901@gmail.com>
Date: Sat, 27 Aug 2011 10:46:40 +1200
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 Brim <scott.brim@gmail.com>
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <CAPv4CP-OiQ3F96skrFO7j7LfF0jBxWNNubOFTLFD_x9AGVDjVg@mail.gmail.com>
In-Reply-To: <CAPv4CP-OiQ3F96skrFO7j7LfF0jBxWNNubOFTLFD_x9AGVDjVg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 22:45:37 -0000

On 2011-08-27 04:03, Scott Brim wrote:
> On Fri, Aug 26, 2011 at 11:04, Worley, Dale R (Dale) <dworley@avaya.com> wrote:
>> There must be at least a few hundred million mobile phones with data
>> capability, and a similar number of homes and small businesses with
>> WiFi systems.  So we can estimate that a large fraction of a billion
>> entries would be added to the routing tables.  How would that work?
> 
> You do it in the endpoint.  The original poster should look at all the
> work already being done in IETF WGs (and elsewhere), e.g. 6man and
> mif, intarea and tsvwg.

Not to mention shim6, which is already a PS with running code.

Get used to the idea of end systems running with multiple simultaneous
addresses.

   Brian

From john-ietf@jck.com  Fri Aug 26 16:42:20 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF03F21F8B6B for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 16:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVJn0iNkvL2q for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 16:42:20 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 127C421F8B78 for <ietf@ietf.org>; Fri, 26 Aug 2011 16:42:19 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qx63k-000JRv-OM; Fri, 26 Aug 2011 19:43:37 -0400
Date: Fri, 26 Aug 2011 19:43:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Burger <eburger@standardstrack.com>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: https
Message-ID: <3D2AEC64C024A55B214440B0@PST.JCK.COM>
In-Reply-To: <EF4B68C9-C29C-434C-A083-9E8D505904FF@standardstrack.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com> <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com> <01O5B0C4KUT200VHKR@mauve.mrochek.com> <CADPp2fDghwuuY557ps2DAE6zffAoVJobJOsS6wQu3HLQ=KFfLw@mail.gmail.com> <4E57F4CE.6070309@gmail.com> <EF4B68C9-C29C-434C-A083-9E8D505904FF@standardstrack.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 23:42:21 -0000

--On Friday, August 26, 2011 16:15 -0400 Eric Burger
<eburger@standardstrack.com> wrote:

> Two thoughts.
> 
> On the one hand, Ned is absolutely correct: the thing we want
> to make absolutely sure of is the integrity of the object. The
> way of doing that is making sure the object itself can prove
> its integrity.  In the messaging world, we do this with
> S/MIME.  The use of TLS for SMTP or IMAP does not convey any
> integrity assertions for the object.  Note this object should
> be signed by me when you receive it, by the way.

And it verifies too... sort of.  Note that the IETF mailing list
machinery tries to prevent it from doing so by appending a
footer to tell everyone who it is (independent of the standard
List-* headers that contain the same information).  Another
separate problem, but definitely falling into the "dogfood...
yum" category.

> On the other hand, while TLS is not at all sufficient for the
> integrity of the object, it is necessary to protect the
> individual accessing the object.  There are a number of
> countries where asking for the RFCs relating to privacy,
> security, and threats to such too many times could get you
> arrested.

Yes, although it isn't entirely clear that TLS actually provides
enough protection in practice.  A sufficiently paranoid
government with those concerns would either force the
connections through proxies that it controlled (see Keith's
note) or would notice connections to IETF servers and "inquire",
through out-of-band means, about what was being retrieved.
There are ways to protect against that risk, but assuming that
unadorned https is sufficient is almost certainly naive.

> Likewise, the presumption is the object might be
> signed, but it would be insane and useless to encrypt the
> object.  However, there are many, many times one would want
> the object encrypted, even if only to compress it.

Sure.  If TLS actually worked for its intended purpose in the
overwhelming number of cases, nothing that Ned or I have said
would argue against using it.  In that regard, the problems are
that it is assumed to solve several problems for which it is
useless and several others, including your example above, for
which its effectiveness is dubious against an attacker with
sufficient non-network resources.

> Given that, the question should not be, "Why are we using TLS
> if the object is not private?," but "What are we not using
> secure connections for all IETF access, over any modality?"
> 
> One of the answers seems to be, "Because it sucks."  That is
> the sentiment of the message below.

> So we are eating our dog food, and we are getting indigestion.
> Sounds like an opportunity to fix it!

I think it is more than that.  If we (and the Secretariat and
IASA) cannot get it together to keep certs up to date, or at
least to get them updated _very_ quickly when someone notices
that they have expired (note that it is now only a few minutes
short of 24 hours since the thing expired), we are sending a
pretty strong message to the community that we don't care and no
one else should either.  Remember that the message browsers pop
up when an invalid or expired certificate is encountered is
totally incomprehensible to a typical luser, offering only
choices of not accessing a site that contains useful information
and that was valid before and accepting the cert, errors and
all.  The more valid sites there are with invalid certificates,
the more we train the user to accept those invalid certificates,
rendering the whole certificate idea (and TLS with it)
pointless.  By choosing to contribute to that problem, the IETF
undermines the utility of TLS for addressing the real issues of
server authentication and client-> server encryption that it was
primarily intended to address.

    john


From mohta@necom830.hpcl.titech.ac.jp  Fri Aug 26 21:30:29 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB3321F87D6 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 21:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level: 
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQDT21OAJ1r2 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 21:30:29 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 2F35A21F87F0 for <ietf@ietf.org>; Fri, 26 Aug 2011 21:30:29 -0700 (PDT)
Received: (qmail 69731 invoked from network); 27 Aug 2011 04:35:28 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 27 Aug 2011 04:35:28 -0000
Message-ID: <4E58730F.4030707@necom830.hpcl.titech.ac.jp>
Date: Sat, 27 Aug 2011 13:31:11 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com> <4E4EEE8C.6050102@gmail.com>
In-Reply-To: <4E4EEE8C.6050102@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 04:30:30 -0000

Before requiring IPv6 support, it is necessary to revise obviously
broken parts of IPv6.

For example, ICMPv6 generated agaist multicast packets should be
forbidden or ICMPv6 implosions will occur. It will let ISPs filter
ICMPv6, including but not limited to, those against multicast,
which means PMTUD won't work.

Another example is lack of guaranteed value for payload size.

RFC791 specifies:

    The number 576 is selected to allow a reasonable sized data block to
    be transmitted in addition to the required header information.  For
    example, this size allows a data block of 512 octets plus 64 header
    octets to fit in a datagram.  The maximal internet header is 60
    octets, and a typical internet header is 20 octets, allowing a
    margin for headers of higher level protocols.

and DNS just send 512B messages (520B including UDP header,
which should be a mistake but is safe as no one use IPv4
options).

However, there is no such size specified with IPv6, because
arbitrarily lengthy header options may be inserted. Note that
some header options, such as mobility ones, are inserted by
IP layers without application control.

Thus, applications like DNS can not specify like RFC1035:

   Messages carried by UDP are restricted to 512 bytes (not
   counting the IP or UDP headers).

						Masataka Ohta

PS

You have been warned.

From glenzorn@gmail.com  Fri Aug 26 22:27:57 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5270521F8AA8 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 22:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gUeJCbOH+QHr for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 22:27:56 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id C819221F8A4E for <ietf@ietf.org>; Fri, 26 Aug 2011 22:27:56 -0700 (PDT)
Received: by ywe9 with SMTP id 9so3967770ywe.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 22:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=RMqhWbBtdaWO+y8KlxWjAIAsFkPH6sAdjWzTy0nvB/0=; b=dT01s7uvZSUrHtCbk8VOtrgUJCYc6p11Y8NP76b/J+5PoptXhLrqkBQnpzXS2A/d8s M2hZ1bS1daoBloaWOituIhHIaHAV9Fp0ozdsQkTmMSE3Um4uzBWS3g6iSndRh/kk18uM qN2pkGpdcHg8tS34FFZrEa2w4YT/3Xhshx2Mw=
Received: by 10.91.158.19 with SMTP id k19mr1898781ago.47.1314422954569; Fri, 26 Aug 2011 22:29:14 -0700 (PDT)
Received: from [192.168.1.98] (ppp-115-87-77-81.revip4.asianet.co.th [115.87.77.81]) by mx.google.com with ESMTPS id o16sm140221anj.34.2011.08.26.22.29.11 (version=SSLv3 cipher=OTHER); Fri, 26 Aug 2011 22:29:14 -0700 (PDT)
Message-ID: <4E5880A4.2050108@gmail.com>
Date: Sat, 27 Aug 2011 12:29:08 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com>
In-Reply-To: <01O5AUN0VTQY00VHKR@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 05:27:57 -0000

On 8/26/2011 11:14 PM, ned+ietf@mauve.mrochek.com wrote:

> +1. If you want signatures, do them properly. Don't pretend a transfer
> protection mechanism covering exactly one hop provides real object security,
> because it doesn't.

I could have sworn that TLS was an e2e mechanism.  Maybe you're using
the term "hop" in a manner unfamiliar to me?

> And as for the "encrypt so the really secret stuff doesn't stand out" argument,
> that's fine as long as it doesn't cause inconvenience to anyone. That's clearly
> not the case here. And I'm sorry, the "mistakes were made" notion doesn't
> really fly: Certificates aren't a "set it and forget it" thing, so if you
> haven't noted expiration dates on someone's to-do list so they can be updated
> before expiration, you're not doing it right.

Isn't "not doing it right" pretty much the definition of "mistake"
(assuming no evil intent)?

From glenzorn@gmail.com  Fri Aug 26 22:48:17 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F48D21F8ACE for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 22:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0v61grPNUsm0 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 22:48:16 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C3F8C21F8AC3 for <ietf@ietf.org>; Fri, 26 Aug 2011 22:48:16 -0700 (PDT)
Received: by gyf3 with SMTP id 3so4012488gyf.31 for <ietf@ietf.org>; Fri, 26 Aug 2011 22:49:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=oNZ3WqclVRpAj9c30yZjCz9HEL6uY4Mo1bx9rCfiXWg=; b=chKpaM3gDtzTLxY4kokMPxYM8c495UlzcJRKXcGQx+ePHr1n3ToOhZ4nKl1vGllZF7 hdk6YTaUWe7Jek3I4ftBoP/8JASun8WkJuFySHr2GkS17s7/JwVj8WusHnRvk7Jv6G/u 0w0ZyD9FQL2/cjgStV9cxsXe388FoEBKOhS2g=
Received: by 10.101.5.21 with SMTP id h21mr1865726ani.123.1314424174696; Fri, 26 Aug 2011 22:49:34 -0700 (PDT)
Received: from [192.168.1.98] (ppp-115-87-77-81.revip4.asianet.co.th [115.87.77.81]) by mx.google.com with ESMTPS id d33sm2311634ano.35.2011.08.26.22.49.30 (version=SSLv3 cipher=OTHER); Fri, 26 Aug 2011 22:49:34 -0700 (PDT)
Message-ID: <4E588567.8080609@gmail.com>
Date: Sat, 27 Aug 2011 12:49:27 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com> <4E5806EC.5050304@dougbarton.us> <CADPp2fAPN3tOE-XiLuJ71XLQ2oMd5W0D93iPkuuYqHA-fC0=+A@mail.gmail.com> <4E580B54.2090304@dougbarton.us>
In-Reply-To: <4E580B54.2090304@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 05:48:17 -0000

On 8/27/2011 4:08 AM, Doug Barton wrote:

...

>> As long as they know
>> they're on the same subnet (and ARP broadcasts will reach everyone)
>> they should just ARP for each other and not involve the router at all.
>>
>> If they are on different IP subnets, but the same Ethernet,
> 
> Yes, this is more often the case that I'm dealing with. (Working on
> fixing a problem I inherited for a new client, so per your comment below
> "don't number that way" may be the right answer.)

Old joke (but apropos):

Patient: Doctor, it hurts when I do this.
Doctor:  Don't do that.

...

From daedulus@btconnect.com  Sat Aug 27 02:48:49 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E012421F8AC9; Sat, 27 Aug 2011 02:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.312
X-Spam-Level: 
X-Spam-Status: No, score=-1.312 tagged_above=-999 required=5 tests=[AWL=-0.513, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cge3b0JyrXji; Sat, 27 Aug 2011 02:48:49 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id BC73C21F8AAA; Sat, 27 Aug 2011 02:48:47 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr06.btconnect.com with SMTP id EIJ71096; Sat, 27 Aug 2011 10:49:58 +0100 (BST)
Message-ID: <00fa01cc6495$c89f75a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Doug Barton" <dougb@dougbarton.us>, "Joel jaeggli" <joelja@bogus.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <4E57B142.4020802@bogus.com> <4E58095D.2040509@dougbarton.us>
Subject: Re: https
Date: Sat, 27 Aug 2011 10:46:10 +0200
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.0A0B0303.4E58BDC5.00EA, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.27.84214:17:7.944, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __MULTIPLE_RCPTS_CC_X2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS, MULTIPLE_RCPTS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4E58BDC7.0012,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: webmaster@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 09:48:50 -0000

----- Original Message -----
From: "Doug Barton" <dougb@dougbarton.us>
To: "Joel jaeggli" <joelja@bogus.com>
Cc: "t.petch" <daedulus@btconnect.com>; "IETF Discussion" <ietf@ietf.org>;
<webmaster@ietf.org>
Sent: Friday, August 26, 2011 11:00 PM
Subject: Re: https


> Joel,
>
> I don't know what "It doesn't" is supposed to mean, but visiting
> https://www.ietf.org/* today with firefox it is still reporting that the
> certificate expired yesterday.

Doug

How I interpreted the reply is that some mailing list archives can be accessed
without using TLS, typically by going to the Working Group page and selecting
the archive from there; v6ops is such a one.

But as I pointed out yesterday, if you go to the ietf mailing list pages, such
as
http://www.ietf.org/list/nonwg.html
then that contains some 250 or more html anchors with a scheme of https:, and
that is the only way I know of accessing some of the archives (I was looking for
the IESG comments on the approval of an I-D, comments which I had missed at
announce time).

I tried editing the URI to remove the 's' but the IETF website puts it back
again:-(

Tom Petch

>
> Given the volume of discussion about the topic starting yesterday when
> the problem started one could easily make a case for "it's still broken"
> being a significant "issue."
>
> cc'ing the address listed as "Report Website Errors" on the home page.
>
>
> Doug
>
>
> On 08/26/2011 07:44, Joel jaeggli wrote:
> > It doesn't...
> >
> > http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html
> >
> > On 8/26/11 00:18 , t.petch wrote:
> >> Why does the IETF website consider it necessary to use TLS to access the
mailing
> >> list archives, when they all appeared without it, or any other security, in
the
> >> first place?
> >>
> >> Besides all the usual hassle of TLS, today the certificate is reported by
IE as
> >> expired, which sort of sums it up.
> >>
> >> Tom Petch
> >>
> >> _______________________________________________
> >> 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
>
>
>
> --
>
> 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 daedulus@btconnect.com  Sat Aug 27 02:56:28 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9B1121F886D for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 02:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.18
X-Spam-Level: 
X-Spam-Status: No, score=-2.18 tagged_above=-999 required=5 tests=[AWL=0.419,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KbYA8GRVlNd9 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 02:56:28 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id CD64121F8862 for <ietf@ietf.org>; Sat, 27 Aug 2011 02:56:27 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr06.btconnect.com with SMTP id EIJ74100; Sat, 27 Aug 2011 10:57:34 +0100 (BST)
Message-ID: <010001cc6496$d7f484e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Glen Zorn" <glenzorn@gmail.com>, <ned+ietf@mauve.mrochek.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net><4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv><001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net><6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net><005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net><CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com><8F38C2201545EEF1F78C65E8@PST.JCK.COM><01O5AUN0VTQY00VHKR@mauve.mrochek.com> <4E5880A4.2050108@gmail.com>
Subject: Re: https
Date: Sat, 27 Aug 2011 10:53:47 +0200
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.0A0B0303.4E58BF8D.008D, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.27.84214:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4E58BF8F.009A,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 09:56:28 -0000

----- Original Message -----
From: "Glen Zorn" <glenzorn@gmail.com>
To: <ned+ietf@mauve.mrochek.com>
Cc: "John C Klensin" <john-ietf@jck.com>; "IETF Discussion" <ietf@ietf.org>
Sent: Saturday, August 27, 2011 7:29 AM
Subject: Re: https


> On 8/26/2011 11:14 PM, ned+ietf@mauve.mrochek.com wrote:
>
> > +1. If you want signatures, do them properly. Don't pretend a transfer
> > protection mechanism covering exactly one hop provides real object security,
> > because it doesn't.
>
> I could have sworn that TLS was an e2e mechanism.  Maybe you're using
> the term "hop" in a manner unfamiliar to me?

Glen

Without a precise context, then e2e can mean anything, from ends of a fibre link
to ends of a communication between two sentient beings.

On other lists, there is sometimes disagreement as to what TLS is, transport,
application or what.  What it is not is a secure channel from application to
application, for that you need channel binding or some such, a problem which a
number of WGs have wrestled with, such as isms for SNMPv3 (which used its own
form of binding for both SSH and TLS between the secure transport and the
application).

I regularly hear, and cringe at, statements in the media that you must check for
the padlock to know that you are secure.

A) you do not know what cryptography is in use (my local library recently liked
SSL2 as a default)

B) you do not know where the endpoints of the channel are

TLS and padlocks are often a spurious miasma of security.

Tom Petch

>
> > And as for the "encrypt so the really secret stuff doesn't stand out"
argument,
> > that's fine as long as it doesn't cause inconvenience to anyone. That's
clearly
> > not the case here. And I'm sorry, the "mistakes were made" notion doesn't
> > really fly: Certificates aren't a "set it and forget it" thing, so if you
> > haven't noted expiration dates on someone's to-do list so they can be
updated
> > before expiration, you're not doing it right.
>
> Isn't "not doing it right" pretty much the definition of "mistake"
> (assuming no evil intent)?
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From daedulus@btconnect.com  Sat Aug 27 03:15:10 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6088D21F8ADC for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 03:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.205
X-Spam-Level: 
X-Spam-Status: No, score=-2.205 tagged_above=-999 required=5 tests=[AWL=0.394,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OW9br99PAklW for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 03:15:09 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB9421F8A51 for <ietf@ietf.org>; Sat, 27 Aug 2011 03:15:08 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr06.btconnect.com with SMTP id EIJ82049; Sat, 27 Aug 2011 11:16:26 +0100 (BST)
Message-ID: <016201cc6499$7a5d23c0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Glen Zorn" <glenzorn@gmail.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net><4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv><001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net><6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net><005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net><CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com><8F38C2201545EEF1F78C65E8@PST.JCK.COM><01O5AUN0VTQY00VHKR@mauve.mrochek.com><4E5880A4.2050108@gmail.com> <010001cc6496$d7f484e0$4001a8c0@gateway.2wire.net>
Subject: Re: https
Date: Sat, 27 Aug 2011 11:12:38 +0200
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.0A0B0303.4E58C3F9.0055, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.27.84214:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4E58C3FA.0079,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 10:15:10 -0000

Glen

Me again.

Just after I posted my last message, I received a post on the ietf-ssh list,
hosted by netbsd.org, and looking through the 'Received: from' headers, as one
does on a wet Saturday morning of a Bank Holiday weekend, there was TLS, used to
submit the message to the server, so even spammers have caught on that TLS
should be used everywhere.  End to end?

Tom Petch


----- Original Message -----
From: "t.petch" <daedulus@btconnect.com>
To: "Glen Zorn" <glenzorn@gmail.com>; <ned+ietf@mauve.mrochek.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Saturday, August 27, 2011 10:53 AM
Subject: Re: https


> ----- Original Message -----
> From: "Glen Zorn" <glenzorn@gmail.com>
> To: <ned+ietf@mauve.mrochek.com>
> Cc: "John C Klensin" <john-ietf@jck.com>; "IETF Discussion" <ietf@ietf.org>
> Sent: Saturday, August 27, 2011 7:29 AM
> Subject: Re: https
>
>
> > On 8/26/2011 11:14 PM, ned+ietf@mauve.mrochek.com wrote:
> >
> > > +1. If you want signatures, do them properly. Don't pretend a transfer
> > > protection mechanism covering exactly one hop provides real object
security,
> > > because it doesn't.
> >
> > I could have sworn that TLS was an e2e mechanism.  Maybe you're using
> > the term "hop" in a manner unfamiliar to me?
>
> Glen
>
> Without a precise context, then e2e can mean anything, from ends of a fibre
link
> to ends of a communication between two sentient beings.
>
> On other lists, there is sometimes disagreement as to what TLS is, transport,
> application or what.  What it is not is a secure channel from application to
> application, for that you need channel binding or some such, a problem which a
> number of WGs have wrestled with, such as isms for SNMPv3 (which used its own
> form of binding for both SSH and TLS between the secure transport and the
> application).
>
> I regularly hear, and cringe at, statements in the media that you must check
for
> the padlock to know that you are secure.
>
> A) you do not know what cryptography is in use (my local library recently
liked
> SSL2 as a default)
>
> B) you do not know where the endpoints of the channel are
>
> TLS and padlocks are often a spurious miasma of security.
>
> Tom Petch
>
> >
> > > And as for the "encrypt so the really secret stuff doesn't stand out"
> argument,
> > > that's fine as long as it doesn't cause inconvenience to anyone. That's
> clearly
> > > not the case here. And I'm sorry, the "mistakes were made" notion doesn't
> > > really fly: Certificates aren't a "set it and forget it" thing, so if you
> > > haven't noted expiration dates on someone's to-do list so they can be
> updated
> > > before expiration, you're not doing it right.
> >
> > Isn't "not doing it right" pretty much the definition of "mistake"
> > (assuming no evil intent)?
> > _______________________________________________
> > 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 nsb@guppylake.com  Sat Aug 27 06:51:56 2011
Return-Path: <nsb@guppylake.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 020A221F87C9 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 06:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIQPVinn22ZL for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 06:51:55 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE8321F872A for <ietf@ietf.org>; Sat, 27 Aug 2011 06:51:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer; b=jzOE13DfS2OG+g7sK5CK95cMp3Soinr3vLWMpIpdhVytme2Cm7KPcNzNPZjiZBDwXhVpEvfwHuobbVr4l6xaIz1osS8rlp5Vw3rKwM6k3kqbJrku/Vwh0rgm3zorKflh;
Received: from [184.244.67.149] (helo=[192.168.0.196]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1QxJJs-0008Jx-Ii; Sat, 27 Aug 2011 09:53:09 -0400
Subject: Re: https
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-206--1008947801
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com>
Date: Sat, 27 Aug 2011 09:53:04 -0400
Message-Id: <21B31DBC-4002-4671-BA6F-36351B5935C9@guppylake.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Cc: SM <sm@resistor.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 13:51:56 -0000

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

On Aug 26, 2011, at 10:24 AM, Tim Bray wrote:

> I'm increasingly coming to think that *everything* should be done with
> TLS unless you can prove it's harmful.  Call me paranoid, but given
> the general state of the world, secure-by-default seems like the way
> to go.  -Tim

You're not alone.  I think one reason this discussion suddenly flared up =
so dramatically is that this is at least as much a political issue as a =
technical one, and therefore not exactly the IETF's bailiwick.  EFF =
certainly seems to think so:

	http://www.eff.org/https-everywhere

Nowadays the only reason I can see for not wanting to use any form of =
encryption you can, anywhere and anytime you can, is a desire to make it =
easier for governments to snoop on you.  Even flawed or partial schemes =
can provide some protection if deployed widely enough -- it's the same =
principle as steganography, more or less.  -- Nathaniel=

--Apple-Mail-206--1008947801
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><div>On Aug 26, 2011, at 10:24 AM, Tim Bray wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I'm =
increasingly coming to think that *everything* should be done =
with<br>TLS unless you can prove it's harmful. &nbsp;Call me paranoid, =
but given<br>the general state of the world, secure-by-default seems =
like the way<br>to go. =
&nbsp;-Tim<br></span></blockquote></div><br><div>You're not alone. =
&nbsp;I think one reason this discussion suddenly flared up so =
dramatically is that this is at least as much a political issue as a =
technical one, and therefore not exactly the IETF's bailiwick. &nbsp;EFF =
certainly seems to think so:</div><div><br></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><a =
href=3D"http://www.eff.org/https-everywhere">http://www.eff.org/https-ever=
ywhere</a></div><div><br></div><div>Nowadays the only reason I can see =
for not wanting to use any form of encryption you can, anywhere and =
anytime you can, is a desire to make it easier for governments to snoop =
on you. &nbsp;Even flawed or partial schemes can provide some protection =
if deployed widely enough -- it's the same principle as steganography, =
more or less. &nbsp;-- Nathaniel</div></body></html>=

--Apple-Mail-206--1008947801--

From johnl@iecc.com  Sat Aug 27 07:30:09 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBFB321F893C for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.113
X-Spam-Level: 
X-Spam-Status: No, score=-111.113 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4n5vkWco+Ig for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:30:09 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3368121F874B for <ietf@ietf.org>; Sat, 27 Aug 2011 07:30:09 -0700 (PDT)
Received: (qmail 67291 invoked from network); 27 Aug 2011 14:31:27 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 27 Aug 2011 14:31:27 -0000
Received: (qmail 3015 invoked from network); 27 Aug 2011 14:31:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 Aug 2011 14:31:26 -0000
Date: 27 Aug 2011 14:31:04 -0000
Message-ID: <20110827143104.89801.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: authenticated archives, was https
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 14:30:10 -0000

I can't tell what problem we're trying to solve here.  The original
question (other than that whoever runs the IETF web site should
buy a new cert) seemed to have something to do with mailing list
archives.  I think it would be swell to know that the archives I
retrieved were the real ones, but what does real mean here?

A - The messages sent by authenticated senders
B - The contents of the archive as of some past time when the
    archives were created
C - The archives as they are on an IETF server now
D - The archives as presented by some presumably reliable piece
    of software (pipermail)
E - Something else

While option A might be nice, it's not going to happen without an
implausible level of S/MIME or PGP signing.

Option B seems useful to me, since it defends against the threat of
accidental or deliberate bitrot.  (An example might be restoring an
archived copy that had the addresses xxx'ed out.)

Options C and D seem less useful.

Harking back to a previous argument about signing RFCs, the way I
would do option B would be to publish hashes of the archive files in
enough places to be sure they're persistent, e.g., print the latest
set of hashes on the back of everyone's name card at IETF meetings.

TLS for session privacy is nice, but I find negligible value in a
little lock icon in my browser that means only that one of the several
dozen cert issuers configured into my browser, most of whom I've never
heard of, and many of whom aren't even the organization in the cert
name, signed something.

R's,
John



From dhc@dcrocker.net  Sat Aug 27 07:43:49 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2B121F8AED for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.091
X-Spam-Level: 
X-Spam-Status: No, score=-6.091 tagged_above=-999 required=5 tests=[AWL=-0.092, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-1izO3-24BQ for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:43:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D0A9C21F8ABD for <ietf@ietf.org>; Sat, 27 Aug 2011 07:43:48 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7REj1xj013792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sat, 27 Aug 2011 07:45:07 -0700
Message-ID: <4E5902E6.9080000@dcrocker.net>
Date: Sat, 27 Aug 2011 07:44:54 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com> <4E5880A4.2050108@gmail.com>
In-Reply-To: <4E5880A4.2050108@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, 27 Aug 2011 07:45:07 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 14:43:49 -0000

On 8/26/2011 12:18 AM, t.petch wrote:
 > Why does the IETF website consider it necessary to use TLS to access the
 > mailing list archives, when they all appeared without it, or any other
 > security, in the first place?

There is a general move towards using https for all web exchanges, as already 
noted on this thread.  When a server-side cert is used, this includes 
protection against man-in-the-middle attacks.

As for providing confidentiality when the data are actually public, yeah, that's 
kind of wasted, but the web service can't know whether the data needs 
protecting.  For example you might be logging in to your mailing list account.

However, as Eliot notes, there is a degree of data authentication this provides.

As for the alternative of object-based signing, that's good in theory, but not 
as well deployed -- and some current IETF wg activity seeks to remedy this(*) -- 
and therefore not an immediately superior choice.  (As a fan of object-based 
signing, I would rather have the authentication be object-based.)



On 8/26/2011 10:29 PM, Glen Zorn wrote:
> I could have sworn that TLS was an e2e mechanism.  Maybe you're using
> the term "hop" in a manner unfamiliar to me?

Evidently so.

The likely disparity is with applications that have their own store-and-forward 
model, as already noted on this thread.  TLS covers only one step (hop) in the 
sequence; by definition, that's not end2end.

And note that this is a rather larger set of apps than most people realize.

The modern web, for example, is highly store and forward at the application 
level.  First, the author is typically far removed from the server that provides 
the data.  Second, caches and proxies mediate the exchange.  TLS protects none 
of the intermediary processes.

In other words, with respect to application-level protection, TLS is equivalent 
to a link-level protocol.  It is 'direct' between two apps participants during 
an immediate exchange.  It does not cover the sequence of nodes at the 
application level.  Having a sequence of TLS sessions provides protection of the 
communication exchanges, but does not protect within the nodes mediating the 
(apps-level) e2e sequence.

In other words, "end to end" is a relative construct.  Even email is not 
end2end, relative to some processes that use email, such as EDI...


d/


(*) A fundamental issue that arises especially for object-based signing is which 
identifier to use.  There is a very large difference between having it signed by 
the author's organization, versus by the web server operator, for example.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From moore@network-heretics.com  Sat Aug 27 07:43:57 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4365721F8B0F for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1eBxCOCLZvO for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:43:56 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 87EB521F8B0D for <ietf@ietf.org>; Sat, 27 Aug 2011 07:43:56 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5D90D20A08; Sat, 27 Aug 2011 10:45:15 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sat, 27 Aug 2011 10:45:15 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Qc8 djoigrfMdyAuguEDLxiwzfhU=; b=Y6lC/94uJ6Dr2SrtioKHS6IDNMCfQvGWHKn Vr0kfe1zQbVswsKdwTTOnIgAEmdA6Ktkb23qaHjieVZLPIVI8RIfqWc6LsbddHAX fuRVQBZCkb8t30VwknqL4+6xEZr4GmyVlQm2iKu0bmi1wT9sRrALCDF1KMKRGUw7 ScA7nzBY=
X-Sasl-enc: Sl3j2mgJVVqlPXfPRryFfcmmRzZdEdCM5M30AntuzOWo 1314456315
Received: from [172.27.105.117] (unknown [204.245.56.3]) by mail.messagingengine.com (Postfix) with ESMTPA id 29FB5AC0134; Sat, 27 Aug 2011 10:45:15 -0400 (EDT)
Subject: Re: authenticated archives, was https
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-4--1005849468
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110827143104.89801.qmail@joyce.lan>
Date: Sat, 27 Aug 2011 10:44:43 -0400
Message-Id: <5199131E-EE60-4506-A674-08533630AEF8@network-heretics.com>
References: <20110827143104.89801.qmail@joyce.lan>
To: John Levine <johnl@iecc.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 14:43:57 -0000

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

On Aug 27, 2011, at 10:31 AM, John Levine wrote:

> TLS for session privacy is nice, but I find negligible value in a
> little lock icon in my browser that means only that one of the several
> dozen cert issuers configured into my browser, most of whom I've never
> heard of, and many of whom aren't even the organization in the cert
> name, signed something.

+1.  IMO browser vendors have made TLS nearly useless for web browsing =
by including so many default CAs; some with dubious integrity, and a few =
with a demonstrated lack of integrity.




--Apple-Mail-4--1005849468
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><div>On Aug 27, 2011, at 10:31 AM, John Levine wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">TLS for =
session privacy is nice, but I find negligible value in a<br>little lock =
icon in my browser that means only that one of the several<br>dozen cert =
issuers configured into my browser, most of whom I've never<br>heard of, =
and many of whom aren't even the organization in the cert<br>name, =
signed something.</span></blockquote></div><br><div>+1. &nbsp;IMO =
browser vendors have made TLS nearly useless for web browsing by =
including so many default CAs; some with dubious integrity, and a few =
with a demonstrated lack of =
integrity.</div><div><br></div><div><br></div><div><br></div></body></html=
>=

--Apple-Mail-4--1005849468--

From fluffy@cisco.com  Sat Aug 27 07:46:40 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 440F821F8715 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.352
X-Spam-Level: 
X-Spam-Status: No, score=-103.352 tagged_above=-999 required=5 tests=[AWL=-0.753, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBOXXRstdQz7 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:46:39 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 7C77921F86F6 for <ietf@ietf.org>; Sat, 27 Aug 2011 07:46:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=2835; q=dns/txt; s=iport; t=1314456479; x=1315666079; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=UVrg/URMXkWPH8mibOFlVVMfO5lFLh0a7beLstNhmUA=; b=QnVexf6gd9l1w6IASFNInkjTeARE2YmcLSvOIlmGJWnvSJ5iXFBABr6O VSrkzHZhDDivIKY9Ayx9QW/L0SbAD2ZwgUx35b/iCOYPB0cVWRcP0aQum WrFyFC/ShtkMtjK4QOig+33A3UulbrOqFqqaIka6fskNe1tjFFT6X16Dq g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAwDWU6rRDoH/2dsb2JhbABCqCx3gTkHAQEBAQIBAQEBDwEFIi4GCwULCxgVGScwBhMih1AEmg0Bnj2DO4IxYASHZIs7hQ6MFQ
X-IronPort-AV: E=Sophos;i="4.68,289,1312156800"; d="scan'208";a="17066066"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-2.cisco.com with ESMTP; 27 Aug 2011 14:47:58 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7RElvZm005755; Sat, 27 Aug 2011 14:47:57 GMT
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4E556DFC.5060705@gmail.com>
Date: Sat, 27 Aug 2011 08:47:57 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AD084F2-662A-4DE3-BF19-30E622647E6E@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu>	<FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E556DFC.5060705@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 14:46:40 -0000

Seems like the public issue could be solved by requiring an NDA from =
anyone that wanted to see the information. I also imagine people would =
only need to see high level summary not the actual contract.=20

On Aug 24, 2011, at 3:32 PM, Brian E Carpenter wrote:

> Keith,
>=20
> I would be amazed if any major hotel or convention centre would allow =
its
> bid to be made public in this way. I too am disturbed by the Taipei =
hotel
> rate, but I know from my own time on the IAOC that matching bids, =
dates,
> hosts and all the other constraints is essentially an insoluble =
problem.
>=20
> It would be interesting if someone with historical data could plot =
IETF
> hotel and meeting fee costs over the years since 1986, normalized to =
take
> account of inflation and trade-weighted currency variations. I really
> can't guess what the outcome would be.
>=20
> Regards
>   Brian Carpenter
>=20
> On 2011-08-25 09:12, Keith Moore wrote:
>> Maybe there needs to be some sort of voting system for future venues.
>>=20
>> You'd be eligible to vote if you'd attended an IETF anytime within =
the past, say, 2 years - or if you were willing to commit to attending =
the one you vote on if it wins.  (say by putting down a deposit toward =
meeting fees).
>>=20
>> Instead of picking one venue, the committee would solicit bids from N =
(say 3-4) different venues within a geographic region.    The bids would =
include:
>> room cost per night in the conference hotel
>> room cost per night in each of some small number of alternate hotels
>> locations of said hotels and nature of transportation between there =
and the conference venue
>> meeting fee for the entire week if that venue is chosen
>> other pertinent information (like what kind of food is nearby, what =
kind of facilities there are in or near the venue for impromptu =
gathering, what kinds of sightseeing opportunities there are, etc.)
>> The committee would survey attendees from time to time and tell the =
prospective venues what kinds of criteria the attendees found important, =
so they'd know how best to make their pitch.
>>=20
>> Every eligible voter would get one vote.  There would be a strict =
deadline for submitting bids, and a strict deadline for voting.
>>=20
>> That way, everyone could figure his own travel costs, factor in his =
own willingness to stay further away for less cost, etc.
>>=20
>> Keith
>>=20
>>=20
>>=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 fluffy@cisco.com  Sat Aug 27 07:46:53 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9264021F8B19 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.343
X-Spam-Level: 
X-Spam-Status: No, score=-103.343 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vXASS9NBRJU for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:46:53 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF7F21F8B16 for <ietf@ietf.org>; Sat, 27 Aug 2011 07:46:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=692; q=dns/txt; s=iport; t=1314456492; x=1315666092; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=lO+zL9Th1jwp+4J7fPyZpuVG0nGuIgYnl29GXbKZ6kk=; b=m5krzz6GDkHQeWgSLZt7ctmBtJ0kEoVsKhllOcbcLSs9zSSdJGUkPEje YlUPsN9I28cCWMioJJh1xnRFIT318koj9fomlSh381XP9OpBDQIIQOQnc KyGQzp5DyKn6QLaXpHZcLe8P4esEfZrVjLKkLs5VnjIqZi2DF6FbSm5ff 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlcHAAwDWU6rRDoH/2dsb2JhbABCmRGPG3eBQAEBAQECARIBJz8FCwsYLlctDodQmhEBnj2FbGAEh2SLO4UOjBU
X-IronPort-AV: E=Sophos;i="4.68,289,1312156800"; d="scan'208";a="17066118"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-2.cisco.com with ESMTP; 27 Aug 2011 14:48:12 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7RElvZo005755; Sat, 27 Aug 2011 14:48:11 GMT
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4E55E827.4060802@gmail.com>
Date: Sat, 27 Aug 2011 08:48:11 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com>
To: henk@uijterwaal.nl
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 14:46:53 -0000

On Aug 25, 2011, at 12:13 AM, Henk Uijterwaal wrote:

> On 24/08/2011 23:12, Keith Moore wrote:
>> Maybe there needs to be some sort of voting system for future venues.
>=20
> First of all, remember that the community asked for venue selections
> 2 to 3 years in advance.  I don't think that many people can predict
> if they will attend a meeting 2 years from now.
>=20
> This proposal would require that the secretariat works out 3-4 =
proposals
> for meeting locations in great detail.   That is a lot more work than
> the current approach:=20

Really? that is fascinating in itself. I had assume that the current =
meeting selection did consider more than one place.=20



From fluffy@cisco.com  Sat Aug 27 07:47:32 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58AF321F8B1D for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.335
X-Spam-Level: 
X-Spam-Status: No, score=-103.335 tagged_above=-999 required=5 tests=[AWL=-0.736, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id un+aS+iNQHNc for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:47:31 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id C0E7A21F8B0C for <ietf@ietf.org>; Sat, 27 Aug 2011 07:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=987; q=dns/txt; s=iport; t=1314456531; x=1315666131; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=JF8dMdALEyGoLXaz7jZNSAjVS15bt1Afss68PCKOly4=; b=QH+Qv2oXZc0CGgF9h1HkRlXJH2TAGTkzIrCxJb3KbxBc+Cv/x2wQwgp5 VqkQ0Fb2u7Do+t68E1LU2lGVBYDzf59+xUHLGTiCRDNPLWYSDuRPOug8S fbl8ztdacdXI617XW4+aOUIGsYd4aniqu+I3TNizEWGTAX2mH5bKaebWH 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHYDWU6rRDoH/2dsb2JhbABCDqged4FAAQEBAQMSASc/EAtGVwYTFA6hZAGePYVsYASHZIs7hQ6LPlc
X-IronPort-AV: E=Sophos;i="4.68,289,1312156800"; d="scan'208";a="17074299"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-7.cisco.com with ESMTP; 27 Aug 2011 14:48:40 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7RElvZp005755; Sat, 27 Aug 2011 14:48:40 GMT
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <tslmxey8sia.fsf@mit.edu>
Date: Sat, 27 Aug 2011 08:48:39 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1084)
Cc: dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 14:47:32 -0000

On Aug 24, 2011, at 2:27 PM, Sam Hartman wrote:

>>>>>> "Dave" =3D=3D Dave CROCKER <dhc@dcrocker.net> writes:
>=20
>    Dave> ps.  As a personal aside, I'll note that I've lobbied rather
>    Dave> vigorously for venues that entail less travel effort, by
>    Dave> eliminating the additional hop needed to get from a major =
hub.
>    Dave> Note that that has gotten essentially zero support from the
>    Dave> community.  The community has vigrously expressed a =
preference
>    Dave> for "interesting" venues rather than ones that are chosen
>    Dave> solely for logistics convenience.
>=20
> Can you start by backing up the assertion  that the community has
> vigrously expressed a preference for interesting venues?
> I may just need a new IETF community:-)

What I have heard is that the community would prefer going to locations =
that were easy to travel to over "interesting".=20

I'd be perfectly happy with every US meeting being in Minneapolis.=20



From dhc@dcrocker.net  Sat Aug 27 07:56:23 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762CB21F8779 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.385
X-Spam-Level: 
X-Spam-Status: No, score=-6.385 tagged_above=-999 required=5 tests=[AWL=0.214,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wz76gIGzSQOn for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 07:56:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BA49721F8770 for <ietf@ietf.org>; Sat, 27 Aug 2011 07:56:19 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7REvWkl014043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Aug 2011 07:57:37 -0700
Message-ID: <4E5905D5.40607@dcrocker.net>
Date: Sat, 27 Aug 2011 07:57:25 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.com>
In-Reply-To: <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.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, 27 Aug 2011 07:57:38 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 14:56:23 -0000

On 8/27/2011 7:48 AM, Cullen Jennings wrote:
> What I have heard is that the community would prefer going to locations that were easy to travel to over "interesting".


How do you reconcile this assertion against the clearly positive group reactions 
to Prague and Quebec?

FYI, in relative terms, even Minneapolis is second-tier.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From johnl@iecc.com  Sat Aug 27 08:01:18 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A34321F86C1 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.124
X-Spam-Level: 
X-Spam-Status: No, score=-111.124 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6d5tkKioyVq for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:01:17 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 35F9021F86AF for <ietf@ietf.org>; Sat, 27 Aug 2011 08:01:17 -0700 (PDT)
Received: (qmail 67467 invoked from network); 27 Aug 2011 15:02:34 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 27 Aug 2011 15:02:34 -0000
Received: (qmail 17932 invoked from network); 27 Aug 2011 15:02:34 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 Aug 2011 15:02:34 -0000
Date: 27 Aug 2011 15:02:12 -0000
Message-ID: <20110827150212.98321.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: fluffy@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 15:01:18 -0000

>What I have heard is that the community would prefer going to
>locations that were easy to travel to over "interesting".

Well, some of the community.  I expect that's because we just came
back from a meeting that wasn't great for travel (insert shout-out to
the gang who were all stuck for the night at the Phila airport
Marriott) but once we got there, had good food and interesting stuff
to do nearby in the evenings.

If we'd come back from a meeting that was within walking distance
of a hub airport, but all the places to eat had bright lighting
and laminated menus, I expect the set of complaints would be
quite different.

R's,
John

From fluffy@cisco.com  Sat Aug 27 08:05:19 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C17FB21F8B3C for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.327
X-Spam-Level: 
X-Spam-Status: No, score=-103.327 tagged_above=-999 required=5 tests=[AWL=-0.728, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkETY-jqViEU for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:05:19 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id B10ED21F8B3A for <ietf@ietf.org>; Sat, 27 Aug 2011 08:05:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=483; q=dns/txt; s=iport; t=1314457591; x=1315667191; h=mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to; bh=5EnyAFqatGbw3ZOb9jbT88RPdS2PlViaFhoNGdUWrO8=; b=Wq/wb5MWYVwa1KG4dSP+Wrrl8DZmjhGDOPKsgbOsZ4keXhh+M5iOFXTJ ACPLda8nWdzqUyxw27zp8CCSkA0w5LNADHLjjpVPztU1/ZrEWoUfLPedE pMmeq4JF1jxJGYki6TWa1HZd9Vje+ybtq1Tij9PtkHB0fT+o1TDqXEAN4 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EALMHWU6rRDoG/2dsb2JhbABCqCx3gUABAQEBAgESASc0EAsLGC5XBjWHUJp8AZ41hWxgBIdkizuFDoMwiGU
X-IronPort-AV: E=Sophos;i="4.68,289,1312156800"; d="scan'208";a="17072646"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-8.cisco.com with ESMTP; 27 Aug 2011 15:06:17 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7RF6GGa013048 for <ietf@ietf.org>; Sat, 27 Aug 2011 15:06:17 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: subject_prefix on IETF Discuss?
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4E39B358.7060409@stpeter.im>
Date: Sat, 27 Aug 2011 09:06:16 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <9BB37CCE-E641-4B5A-892A-7FC911C4B9C6@cisco.com>
References: <201108031926.p73JQdHj019455@fs4113.wdf.sap.corp> <4E39B358.7060409@stpeter.im>
To: IETF-Discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 15:05:19 -0000

On Aug 3, 2011, at 2:45 PM, Peter Saint-Andre wrote:

> On 8/3/11 1:26 PM, Martin Rex wrote:
> 
>> subject_prefix will work even with very ancient MUAs, such as the
>> one I use, so I'm OK.  But the subject_prefix does not scale well
>> when multiple IETF mailings lists are CC-ed and discussion ensues
>> (replying to all lists).
> 
> "Doctor, it hurts when I do that."
> 
> /psa
> 
> 


Yah, I find this particularly bad when reading email on my Datapoint 3300 



From ekr@rtfm.com  Sat Aug 27 08:29:50 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7EFB21F8563 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:29:50 -0700 (PDT)
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=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m2f7ca4pHRAg for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:29:50 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1245821F84D6 for <ietf@ietf.org>; Sat, 27 Aug 2011 08:29:49 -0700 (PDT)
Received: by ewy19 with SMTP id 19so2031165ewy.31 for <ietf@ietf.org>; Sat, 27 Aug 2011 08:31:05 -0700 (PDT)
Received: by 10.213.112.198 with SMTP id x6mr1407595ebp.52.1314459064734; Sat, 27 Aug 2011 08:31:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.213.13.141 with HTTP; Sat, 27 Aug 2011 08:30:44 -0700 (PDT)
In-Reply-To: <4E5905D5.40607@dcrocker.net>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.com> <4E5905D5.40607@dcrocker.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 27 Aug 2011 08:30:44 -0700
Message-ID: <CABcZeBM4CUggUqgKALjktQDrAvthFGJM3FChh3nqBj+k2_TXwg@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: Cullen Jennings <fluffy@cisco.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 15:29:51 -0000

On Sat, Aug 27, 2011 at 7:57 AM, Dave CROCKER <dhc@dcrocker.net> wrote:
>
>
> On 8/27/2011 7:48 AM, Cullen Jennings wrote:
>>
>> What I have heard is that the community would prefer going to locations
>> that were easy to travel to over "interesting".
>
>
> How do you reconcile this assertion against the clearly positive group
> reactions to Prague and Quebec?
>
> FYI, in relative terms, even Minneapolis is second-tier.

I have no idea what the "community" wants--and I'm not convinced that
the data we
have available lets us assess that, for the usual reasons about the
difficulty of doing
accurate surveying--but speaking solely for myself, I'm at IETF to
work, so my priorities
center around the things that make it easy to get work done. This
basically boils down
to cost  and convenience.

Within these general parameters, my priorities are something like:
1. Cost:
    - Travel
    - Hotel

Rationale: airfare tends to not be that flexible, but it's generally
possible to find a cheaper
hotel if you try (as several people have observed). However, if the
conference hotel
is $300/night, then this is probably going to trickle down some into
cheaper hotels so
it's not like hotel doesn't matter.


2. Convenience:
    - Length of trip.
    - Local services

Rationale: travel time is time I'm not working (yeah, we all try, but
I'm not that effective
and I suspect most people are not.) Lack of local services means less
time meeting
and more time rushing around trying to find lunch before the next
meeting, walking to
and from the hotel, etc.


I'm certainly not opposed to interesting venues, but I would say it's
worth about $200-300
to me on a typical IETF trip.  I would be more than happy to have all
IETFs at some small number of convenient, economical venues. E.g.,
Vancouver, Prague,
and (insert Asian Venue here.) [0] Obviously, we can't optimize for
these criteria
at once for everyone, but it's equally the case that there are plenty
of venues which
don't really meet them that well for anyone.

-Ekr


[0] Prague isn't actually that convenient since it's one hop away from
Frankfurt. None of the
European venues have been that great for me from the standpoint of the
two criteria above,
since they're either far from a hub (Prague) or expensive (Paris). My
vote here would
probably be for Frankfurt, but that's probably just Star Alliance provincialism.

From marshall.eubanks@gmail.com  Sat Aug 27 08:42:06 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 640D321F874B for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.157
X-Spam-Level: 
X-Spam-Status: No, score=-103.157 tagged_above=-999 required=5 tests=[AWL=0.441, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qad6swr21wVk for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:42:05 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 80FDF21F86C0 for <ietf@ietf.org>; Sat, 27 Aug 2011 08:42:05 -0700 (PDT)
Received: by ywe9 with SMTP id 9so4254180ywe.31 for <ietf@ietf.org>; Sat, 27 Aug 2011 08:43:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JrEv59OQxFeOO/Wab+ekTgqcN11bgNE8/QxffSdwe1w=; b=QkZf2oyjkJa1BQKTketxkpIkc5pAl9sAR0Ln+wpbC6npUuYdphutWlETdnX70NyO0K jztU1yKKNGMtmp6ZX9t3uTrCHjcLYvj+meTDf7VR8whfLJSFDENdBbAUIHCb5sfbJvm3 EXy3tmDPM+ay+dKkw//h76k7q9plaD3zPzxOU=
MIME-Version: 1.0
Received: by 10.150.150.41 with SMTP id x41mr2906669ybd.255.1314459804495; Sat, 27 Aug 2011 08:43:24 -0700 (PDT)
Received: by 10.150.185.9 with HTTP; Sat, 27 Aug 2011 08:43:24 -0700 (PDT)
In-Reply-To: <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com>
Date: Sat, 27 Aug 2011 11:43:24 -0400
Message-ID: <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com>
Subject: Re: voting system for future venues?
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=000e0cd70c92b7f05004ab7e85c3
Cc: henk@uijterwaal.nl, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 15:42:06 -0000

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

On Sat, Aug 27, 2011 at 10:48 AM, Cullen Jennings <fluffy@cisco.com> wrote:

>
> On Aug 25, 2011, at 12:13 AM, Henk Uijterwaal wrote:
>
> > On 24/08/2011 23:12, Keith Moore wrote:
> >> Maybe there needs to be some sort of voting system for future venues.
> >
> > First of all, remember that the community asked for venue selections
> > 2 to 3 years in advance.  I don't think that many people can predict
> > if they will attend a meeting 2 years from now.
> >
> > This proposal would require that the secretariat works out 3-4 proposals
> > for meeting locations in great detail.   That is a lot more work than
> > the current approach:
>
> Really? that is fascinating in itself. I had assume that the current
> meeting selection did consider more than one place.
>

Of course it does. For example, for the last meeting there were a number of
venues considered, most of which were knocked out quickly, say because they
were already booked for "our" week. Eventually, it boiled down to Vancouver
vs QC, which were pretty even in every regard except for the travel
situation. Thus, the survey. That rarely happens if the past 5 years are any
guide.

I think that the meeting selection process is inherently iterative. Pseudo
code might be something like

- Find a list of all venues we can in the target area for the target week.
The number of these is rarely if ever more than 10.

- do an evaluation of  venues for availability and suitability

- remove any sites that are not available or are unsuitable.

- rank the remainder for suitability, and do a more thorough evaluation,
focusing more on the higher ranked locations.

- repeat the last 3 steps until convergence, tightening the filters based on
what's learned about the sites

At the end of the process, there may be only be one place left, but it
certainly was not the only one considered.

Until recently, sponsor availability was an important part of venue ranking.
Now, with the 3 year out meeting selection process, that coupling will
largely (but not entirely) go away. Basically, this change IMO increases the
risk of not getting a sponsor, in return for a better choice of available
venues. I suspect it will take a few years before we will see what the
actual cost/benefit ratio is for this change.

Regards
Marshall




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

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

<br><br><div class=3D"gmail_quote">On Sat, Aug 27, 2011 at 10:48 AM, Cullen=
 Jennings <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@cisco.com">fluffy@=
cisco.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"><br>
On Aug 25, 2011, at 12:13 AM, Henk Uijterwaal wrote:<br>
<br>
&gt; On 24/08/2011 23:12, Keith Moore wrote:<br>
&gt;&gt; Maybe there needs to be some sort of voting system for future venu=
es.<br>
&gt;<br>
&gt; First of all, remember that the community asked for venue selections<b=
r>
&gt; 2 to 3 years in advance. =A0I don&#39;t think that many people can pre=
dict<br>
&gt; if they will attend a meeting 2 years from now.<br>
&gt;<br>
&gt; This proposal would require that the secretariat works out 3-4 proposa=
ls<br>
&gt; for meeting locations in great detail. =A0 That is a lot more work tha=
n<br>
&gt; the current approach:<br>
<br>
</div>Really? that is fascinating in itself. I had assume that the current =
meeting selection did consider more than one place.<br></blockquote><div><b=
r></div><div>Of course it does. For example, for the last meeting there wer=
e a number of venues considered, most of which were knocked out quickly, sa=
y because they were already booked for &quot;our&quot; week. Eventually, it=
 boiled down to Vancouver vs QC, which were pretty even in every regard exc=
ept for the travel situation. Thus, the survey. That rarely happens if the =
past 5 years are any guide.</div>
<div><br></div><div>I think that the meeting selection process is inherentl=
y iterative. Pseudo code might be something like</div><div><br></div><div>-=
 Find a list of all venues we can in the target area for the target week. T=
he number of these is rarely if ever more than 10.</div>
<div><br></div><div>- do an evaluation of =A0venues for=A0availability and =
suitability</div><div><br></div><div>- remove any sites that are not availa=
ble or are unsuitable.</div><div><br></div><div>- rank the remainder for su=
itability, and do a more thorough evaluation, focusing more on the higher r=
anked locations.=A0</div>
<div><br></div><div>- repeat the last 3 steps until convergence, tightening=
 the filters based on what&#39;s learned about the sites</div><div><br></di=
v><div>At the end of the process, there may be only be one place left, but =
it certainly was not the only one considered.=A0</div>
<div><br></div><div>Until recently, sponsor availability was an important p=
art of venue ranking. Now, with the 3 year out meeting selection process, t=
hat coupling will largely (but not entirely) go away. Basically, this chang=
e IMO increases the risk of not getting a sponsor, in return for a better c=
hoice of available venues. I suspect it will take a few years before we wil=
l see what the actual cost/benefit ratio is for this change.</div>
<div><br></div><div>Regards</div><div>Marshall</div><div><br></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;">
<div><div></div><div class=3D"h5"><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>

--000e0cd70c92b7f05004ab7e85c3--

From ned+ietf@mauve.mrochek.com  Sat Aug 27 08:51:52 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2FF221F8634 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level: 
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMrKC-v51g2m for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 08:51:52 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2956D21F8620 for <ietf@ietf.org>; Sat, 27 Aug 2011 08:51:52 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5C7QF735S013OWR@mauve.mrochek.com> for ietf@ietf.org; Sat, 27 Aug 2011 08:51:54 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5C6AOYDC0014O5Z@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 27 Aug 2011 08:51:50 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5C7QCRHMK014O5Z@mauve.mrochek.com>
Date: Sat, 27 Aug 2011 08:25:45 -0700 (PDT)
Subject: Re: https
In-reply-to: "Your message dated Fri, 26 Aug 2011 07:24:04 -0700" <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314460352; i=@mrochek.com; bh=lkAS4LacKcFOcVw9S7RpSYfInE7llVtonCOzwv7fXhs=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=lMddJS0D6jzix993aXkYjZxJ8yIQxCnBsJbdACiC2obhnB8xJZ3bksvjSo47eJt6u 8gig7P9g9XN8AWFbVkU+exKtSrU3gyjoa725sQaGtNCbyXqjCuL8jfh4Dd3Jxc4/0R H1izQ/t1nf+P2LpvifB8yMOrPMjkXaBz5KVjLu1U=
Cc: SM <sm@resistor.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 15:51:52 -0000

> I'm increasingly coming to think that *everything* should be done with
> TLS unless you can prove it's harmful.  Call me paranoid, but given
> the general state of the world, secure-by-default seems like the way
> to go.  -Tim

This sentiment always sounds nice, but the devil is in the details.

Back when STARTTLS was added to SMTP, a bunch of us thought this provided the
means to do opportunistic encyption of email transport, so there was a push to
deploy that. It was a total failure - it seems a certain large vendor with a
very popular implementation borked their server so it advertised STARTTLS even
though no certificate was installed and any attempt to negotiate TLS protection
would end in failure. And since the negotiation failure left the connection in
an unusable state, a new connection had to be tried, along with all the logic
to prevent the new one from ending up in the same state.

It tooks years before enough of the broken servers were fixed to try again, and
by then service defaults and deployment guidelines were well established and
the opportunity was gone as well.

Of course this set of issues was unique to the situation. But with TLS it's
always something - if it isn't broken default configurations, its incompatible
cipher suites, or problems with certificate formats, or expired certificates,
or dubious CAs, or major security holes in popular implementations, etc. etc.

The bottom line is this stuff is just too complicated for mere mortals to get
right, and the fact that they then proceed to get it wrong more often than not
causes an enormous amount of trouble.

In the present case, for example, you may think that an expired certificate is
not a big deal. Not so. For one thing, the more people have to click on the
"this really isn't secure, proceed anyway" button to get things done, the more
likely they are to do it when it's a real attack and not a maintenance problem.
And for another, there are some browser/certificate error combinations  where
there's no workaround - no amount of clicking "I agree" buttons will get you
the data you're after.

I don't have an anwwer here, but the one thing I'm fairly sure of is that
blindly pushing TLS everywhere is not the solution a lot of folks believe
it is.

				Ned

From melinda.shore@gmail.com  Sat Aug 27 09:23:47 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 070E321F8ABD for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 09:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0m4b4pFzJ+cf for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 09:23:46 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 873B821F87E2 for <ietf@ietf.org>; Sat, 27 Aug 2011 09:23:46 -0700 (PDT)
Received: by pzk33 with SMTP id 33so13939633pzk.18 for <ietf@ietf.org>; Sat, 27 Aug 2011 09:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=pXmwJVd9NzOVdAlg+iI/h+ffckoqpw7iNLGPdLNemak=; b=f8/u95lrPAClK7+ZXd/CLjuiFdefE+IUYVi882j3ZIh68lFhVeLml2NR2FiHFJtDoc KgF2OJo3I6pbGQZ+QL9/emvV5EAPQfqnlddeqrUtHojCqdlVscQrBXClaYThraOmqmvV PpLl8QVoLgq8lm6+FASg4LBnuf1XDXPZxJVXU=
Received: by 10.142.174.3 with SMTP id w3mr1392273wfe.244.1314462305947; Sat, 27 Aug 2011 09:25:05 -0700 (PDT)
Received: from polypro.local (66-230-82-131-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.131]) by mx.google.com with ESMTPS id x6sm7823006pba.5.2011.08.27.09.25.03 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 27 Aug 2011 09:25:04 -0700 (PDT)
Message-ID: <4E591A5D.1060909@gmail.com>
Date: Sat, 27 Aug 2011 08:25:01 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>	<005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>	<CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com> <01O5C7QCRHMK014O5Z@mauve.mrochek.com>
In-Reply-To: <01O5C7QCRHMK014O5Z@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 16:23:47 -0000

On 8/27/11 7:25 AM, ned+ietf@mauve.mrochek.com wrote:
> I don't have an anwwer here, but the one thing I'm fairly sure of is that
> blindly pushing TLS everywhere is not the solution a lot of folks believe
> it is.

I tend to think that the problem here (and I agree that it's a big one)
isn't TLS, but that PKI as defined by pkix is very difficult to deploy
correctly.  I've seen similar sorts of problems with digital signatures
on email, but in those cases as often as not someone simply got
the certificate contents wrong (or the user doesn't understand how to
configure his mail client correctly and is using a name that doesn't
appear in the certificate) rather that the cert has expired (although
there's a lot of that, too).  There's a substantial usability problem.

Melinda

From daedulus@btconnect.com  Sat Aug 27 09:37:38 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B3321F8B04 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 09:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XotbyARy-ygD for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 09:37:37 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id D77D721F8ACE for <ietf@ietf.org>; Sat, 27 Aug 2011 09:37:35 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr08.btconnect.com with SMTP id EBW39956; Sat, 27 Aug 2011 17:38:50 +0100 (BST)
Message-ID: <02ba01cc64ce$e6970800$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "John Levine" <johnl@iecc.com>, <ietf@ietf.org>
References: <20110827143104.89801.qmail@joyce.lan>
Subject: Re: authenticated archives, was https
Date: Sat, 27 Aug 2011 17:35:02 +0200
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.0A0B0303.4E591D99.0083, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.27.154814:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_PATH, ECARD_WORD, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4E591D9A.0136,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 16:37:38 -0000

---- Original Message -----
From: "John Levine" <johnl@iecc.com>
To: <ietf@ietf.org>
Sent: Saturday, August 27, 2011 4:31 PM

> I can't tell what problem we're trying to solve here.  The original
> question (other than that whoever runs the IETF web site should
> buy a new cert) seemed to have something to do with mailing list
> archives.

John

Yes, more generally it is the creeping changes to the IETF service that
makes work progressively more difficult.  https: access to the IETF web
site quite often fails for me, indeed access at all quite often fails.  It never
used
to, and I am hard put to say just when it changed, but it was a year or two ago.
In the case of http: access, MSIE just times out.  Repeat the request and it
usually works; something has changed (could even be DNS).

With https:, the CRL downloads as does the source of the web page and
then the process stalls, permanently; leaving it a couple of hours, or
refreshing
the page, with CRL now in place, and the little icon just goes on turning until
it
is time to stop work. Perhaps when I upgrade my PC it will work - or
perhaps not, without a diagnosis I cannot tell.

In the mean time, I would like TLS exterminated from the IETF website - any
reason
will do - since the cost to me far outweighs the benefit.  So who decided to put
it in, and on what grounds?

Recently, DKIM was added to outgoing mail.  The mail still works, the cost to
me is small and the benefit - to me -is nil.  Who decided to put it in?

There has been a discussion about adding 'subject_prefix' on IETF_Discuss.
(This is a welcome change, actually discussing it before doing it). For me,
the added cost would be small, and the benefit nil.

What is going to come next, and will we get any warning, or will the cost of
IETF activity just go up again?

Tom Petch

                          I think it would be swell to know that the archives I
> retrieved were the real ones, but what does real mean here?
>
> A - The messages sent by authenticated senders
> B - The contents of the archive as of some past time when the
>     archives were created
> C - The archives as they are on an IETF server now
> D - The archives as presented by some presumably reliable piece
>     of software (pipermail)
> E - Something else
>
> While option A might be nice, it's not going to happen without an
> implausible level of S/MIME or PGP signing.
>
> Option B seems useful to me, since it defends against the threat of
> accidental or deliberate bitrot.  (An example might be restoring an
> archived copy that had the addresses xxx'ed out.)
>
> Options C and D seem less useful.
>
> Harking back to a previous argument about signing RFCs, the way I
> would do option B would be to publish hashes of the archive files in
> enough places to be sure they're persistent, e.g., print the latest
> set of hashes on the back of everyone's name card at IETF meetings.
>
> TLS for session privacy is nice, but I find negligible value in a
> little lock icon in my browser that means only that one of the several
> dozen cert issuers configured into my browser, most of whom I've never
> heard of, and many of whom aren't even the organization in the cert
> name, signed something.
>
> R's,
> John
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From johnl@iecc.com  Sat Aug 27 09:52:13 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22DE021F8A55 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 09:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6dPPNoaEV9Og for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 09:52:12 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 73A9521F8A51 for <ietf@ietf.org>; Sat, 27 Aug 2011 09:52:12 -0700 (PDT)
Received: (qmail 68208 invoked from network); 27 Aug 2011 16:53:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=10a6f.4e59210b.k1108; bh=+0vpKopZ4xaJWpt7arscqKKCVxlOeDyYILKthI+SGXo=; b=ZZn+GtT5qH1fioaSR4NV0zQxl6bdm6dsgTGlhjv49j/PSDFmC4HjJheYKkMKykOdF60p7kWpx7qi3ilbvuFg8SWC42StkgTbSiGcg5KBkJlVPhh/ZNkr4NGcbJBE6CpgtUO6V79XyNPqUJMmiwBuzx4Upnete1unlnfBuUg9OXY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Aug 2011 16:53:09 -0000
Date: 27 Aug 2011 12:53:30 -0400
Message-ID: <alpine.BSF.2.00.1108271245590.96409@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: authenticated archives, was https
In-Reply-To: <02ba01cc64ce$e6970800$4001a8c0@gateway.2wire.net>
References: <20110827143104.89801.qmail@joyce.lan> <02ba01cc64ce$e6970800$4001a8c0@gateway.2wire.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 16:52:13 -0000

> In the case of http: access, MSIE just times out.  Repeat the request and it
> usually works; something has changed (could even be DNS).

It works fine for me in IE on Windows 7 on an ordinary consumer DSL 
connection, click through the warning about the expired cert and the pages 
come right up.  I suspect you will find that "my tools are broken" is not 
a persuasive argument to get people to remove security features, even 
fairly lame ones like this.

> Recently, DKIM was added to outgoing mail.  The mail still works, the cost to
> me is small and the benefit - to me -is nil.  Who decided to put it in?

The IAOC, I expect.  I find DKIM useful to skip mail filtering.  Are you 
saying that people are not allowed to use RFC-standard security features 
until you, Tom, approve of them?

R's,
John

From ned+ietf@mauve.mrochek.com  Sat Aug 27 10:10:11 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4573E21F876F for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 10:10:11 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t-MUtDwf+EVy for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 10:10:10 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 608C221F86AB for <ietf@ietf.org>; Sat, 27 Aug 2011 10:10:10 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5CAH3TO80010GYL@mauve.mrochek.com> for ietf@ietf.org; Sat, 27 Aug 2011 10:09:54 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5C6AOYDC0014O5Z@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 27 Aug 2011 10:09:50 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5CAH1JXX2014O5Z@mauve.mrochek.com>
Date: Sat, 27 Aug 2011 10:07:03 -0700 (PDT)
Subject: Re: https
In-reply-to: "Your message dated Sat, 27 Aug 2011 08:25:01 -0800" <4E591A5D.1060909@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com> <01O5C7QCRHMK014O5Z@mauve.mrochek.com> <4E591A5D.1060909@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314465032; i=@mrochek.com; bh=Orj86AhoRPs8TURhuGV/HrPZyrayD9z7Gn8tPz4sUac=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=fFG0sgQW4Nc+1z3J+ALTshHOB/eJ5v6YDOrhvp04SYIffKYVtYwYookGUg3Sdw2EK 7ehJHwl1sJe5YYUeKtz3eM1KPf4EimKgFTq30H9wwucD8v0wbno8etmQOqhENYR/QF 3S8V8az89ux+R/eeTZESxt++/HRShCpC21FzcZ0Q=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 17:10:11 -0000

> On 8/27/11 7:25 AM, ned+ietf@mauve.mrochek.com wrote:
> > I don't have an anwwer here, but the one thing I'm fairly sure of is that
> > blindly pushing TLS everywhere is not the solution a lot of folks believe
> > it is.

> I tend to think that the problem here (and I agree that it's a big one)
> isn't TLS, but that PKI as defined by pkix is very difficult to deploy
> correctly.

Agreed.

> I've seen similar sorts of problems with digital signatures
> on email, but in those cases as often as not someone simply got
> the certificate contents wrong (or the user doesn't understand how to
> configure his mail client correctly and is using a name that doesn't
> appear in the certificate) rather that the cert has expired (although
> there's a lot of that, too).  There's a substantial usability problem.

Absolutely, and it's both architectural and operational - PKI is
full of complex and subtle concepts that implementations don't exactly
help you with.

				Ned

From joelja@bogus.com  Sat Aug 27 10:41:20 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 683E421F85F1 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 10:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T45WRbJsMXDS for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 10:41:20 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1713321F85C0 for <ietf@ietf.org>; Sat, 27 Aug 2011 10:41:20 -0700 (PDT)
Received: from Zorch.local (adsl-99-191-195-38.dsl.pltn13.sbcglobal.net [99.191.195.38]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7RHgU68014511 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 27 Aug 2011 17:42:30 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E592C81.4040402@bogus.com>
Date: Sat, 27 Aug 2011 10:42:25 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: authenticated archives, was https
References: <20110827143104.89801.qmail@joyce.lan> <02ba01cc64ce$e6970800$4001a8c0@gateway.2wire.net>
In-Reply-To: <02ba01cc64ce$e6970800$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 27 Aug 2011 17:42:32 +0000 (UTC)
Cc: John Levine <johnl@iecc.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 17:41:20 -0000

On 8/27/11 08:35 , t.petch wrote:

> In the mean time, I would like TLS exterminated from the IETF website - any
> reason
> will do - since the cost to me far outweighs the benefit.  So who decided to put
> it in, and on what grounds?

The datatracker, wikis, working group chairs pages, registration,
mailing list management and tools sites all support authentication, I
would find it completely unacceptable to pass my credentials  or
activities I engaged in once authenticated in the clear.


From fluffy@cisco.com  Sat Aug 27 11:20:43 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8BA321F8AB0 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 11:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.319
X-Spam-Level: 
X-Spam-Status: No, score=-103.319 tagged_above=-999 required=5 tests=[AWL=-0.720, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ol1JfNJpm1L for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 11:20:42 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id E0FDB21F8A71 for <ietf@ietf.org>; Sat, 27 Aug 2011 11:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=2856; q=dns/txt; s=iport; t=1314469321; x=1315678921; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=+nbx+jFjSdZgnQDOx1elZAO3RZG0R919aSCBqMM3YMw=; b=cT4G7cwpiZPWg0gB+8I2NVYKvii79wRXq90JSDYBoEfAbI6wpliCQbhy nd5Gi3debW504A7ezjfs1vlYvH1+12gTpVocQWudX4qdp085FN7W486Qy mAS2V3Oz8NOgEUYqPfbrSWqbwTxv6hzHMQ9XUjydXqpUFGpHUfqffkdft 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAOo0WU6rRDoJ/2dsb2JhbABCqA93gUABAQEBAgEBAQEPAQUiNAsQCxguJzAGExQOh1AEmigBnh6FbGAEh2SLO4UOjBU
X-IronPort-AV: E=Sophos;i="4.68,290,1312156800"; d="scan'208";a="17094518"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-7.cisco.com with ESMTP; 27 Aug 2011 18:22:01 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p7RIM0Nk009215; Sat, 27 Aug 2011 18:22:00 GMT
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com>
Date: Sat, 27 Aug 2011 12:22:00 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <D4AC0228-C124-4E0C-B28B-DD36400046D4@cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com><801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com><tslr54a8v7s.fsf@mit.edu><4E555B06.6000108@dcrocker.net><tslmxey8sia.fsf@mit.edu><1314218041.1973.204.camel@d430><4E55655C.6030502@bbiw.net><15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com><4E55E827.4060802@gmail.com><13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com>
To: "Marshall Eubanks" <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: henk@uijterwaal.nl, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 18:20:43 -0000

Thanks Marshall, I had suspect the process was something like that. I =
had not realized how much the pre picking the dates reduced the options.=20=



On Aug 27, 2011, at 9:43 AM, Marshall Eubanks wrote:

>=20
>=20
> On Sat, Aug 27, 2011 at 10:48 AM, Cullen Jennings <fluffy@cisco.com> =
wrote:
>=20
> On Aug 25, 2011, at 12:13 AM, Henk Uijterwaal wrote:
>=20
> > On 24/08/2011 23:12, Keith Moore wrote:
> >> Maybe there needs to be some sort of voting system for future =
venues.
> >
> > First of all, remember that the community asked for venue selections
> > 2 to 3 years in advance.  I don't think that many people can predict
> > if they will attend a meeting 2 years from now.
> >
> > This proposal would require that the secretariat works out 3-4 =
proposals
> > for meeting locations in great detail.   That is a lot more work =
than
> > the current approach:
>=20
> Really? that is fascinating in itself. I had assume that the current =
meeting selection did consider more than one place.
>=20
> Of course it does. For example, for the last meeting there were a =
number of venues considered, most of which were knocked out quickly, say =
because they were already booked for "our" week. Eventually, it boiled =
down to Vancouver vs QC, which were pretty even in every regard except =
for the travel situation. Thus, the survey. That rarely happens if the =
past 5 years are any guide.
>=20
> I think that the meeting selection process is inherently iterative. =
Pseudo code might be something like
>=20
> - Find a list of all venues we can in the target area for the target =
week. The number of these is rarely if ever more than 10.
>=20
> - do an evaluation of  venues for availability and suitability
>=20
> - remove any sites that are not available or are unsuitable.
>=20
> - rank the remainder for suitability, and do a more thorough =
evaluation, focusing more on the higher ranked locations.=20
>=20
> - repeat the last 3 steps until convergence, tightening the filters =
based on what's learned about the sites
>=20
> At the end of the process, there may be only be one place left, but it =
certainly was not the only one considered.=20
>=20
> Until recently, sponsor availability was an important part of venue =
ranking. Now, with the 3 year out meeting selection process, that =
coupling will largely (but not entirely) go away. Basically, this change =
IMO increases the risk of not getting a sponsor, in return for a better =
choice of available venues. I suspect it will take a few years before we =
will see what the actual cost/benefit ratio is for this change.
>=20
> Regards
> Marshall
>=20
>=20
> =20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From glenzorn@gmail.com  Sat Aug 27 21:41:57 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDD621F8BB9 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 21:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMLt3Umyf0Ot for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 21:41:56 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 87D9821F8BB7 for <ietf@ietf.org>; Sat, 27 Aug 2011 21:41:56 -0700 (PDT)
Received: by ywe9 with SMTP id 9so4585970ywe.31 for <ietf@ietf.org>; Sat, 27 Aug 2011 21:43:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7ZoDdvNT4p/dKT+mmvHzfWq14zk0W7u0uLCaUIn07CI=; b=nH3zRDwV8u3PuF2Q2A4xgu0B1DyAsA6VukHhvZJ73GhlnwrfBWIfh53w5X3jOItdl9 R7JW8H/KSHNq2zxY3vhHvXDFSOxy0gXPo/94lu0+DvxAZ+V8jAq45kiBRXgORx4Or7zW q19T97O4YuNBNGxiwMJzyCdkONfJDiEzfGscM=
Received: by 10.231.29.138 with SMTP id q10mr6650243ibc.87.1314506597102; Sat, 27 Aug 2011 21:43:17 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-121-237-150.revip2.asianet.co.th [124.121.237.150]) by mx.google.com with ESMTPS id a18sm1802881iba.54.2011.08.27.21.43.12 (version=SSLv3 cipher=OTHER); Sat, 27 Aug 2011 21:43:15 -0700 (PDT)
Message-ID: <4E59C75C.3010807@gmail.com>
Date: Sun, 28 Aug 2011 11:43:08 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net><4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv><001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net><6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net><005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net><CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com><8F38C2201545EEF1F78C65E8@PST.JCK.COM><01O5AUN0VTQY00VHKR@mauve.mrochek.com><4E5880A4.2050108@gmail.com> <010001cc6496$d7f484e0$4001a8c0@gateway.2wire.net> <016201cc6499$7a5d23c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <016201cc6499$7a5d23c0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 04:41:57 -0000

On 8/27/2011 4:12 PM, t.petch wrote:

> Glen
> 
> Me again.
> 
> Just after I posted my last message, I received a post on the ietf-ssh list,
> hosted by netbsd.org, and looking through the 'Received: from' headers, as one
> does on a wet Saturday morning of a Bank Holiday weekend, there was TLS, used to
> submit the message to the server, so even spammers have caught on that TLS
> should be used everywhere.  End to end?

Apparently, from the POV of the spammer & his SMTP server.  Email is a
store & forward system.  In any case, my original question was not about
the definition of end-to-end, it was about Ned usage of the term "hop".
 Upon further analysis, however, it seems clear that he was referring to
the email archives as if they are something other than simple files (as
betrayed by his statement that "Don't pretend a transfer protection
mechanism covering exactly one hop provides real object security,
because it doesn't."); thus, the retrieval of the archived data would be
the last "hop" in the email system.  There seem to be two problems with
this statement: one is taking the file transfer mechanism as if it was
part of the email system itself, which it obviously is not (downloading
an archived message is no different than downloading an RFC from a Web
site); the other being that someone, somewhere was pretending that TLS
does something that it was never designed to do (a straw man of, AFAICT,
Ned's invention -- I don't recall anybody making such a claim on this
thread, nor for that matter saying they _wanted_ "real object security"
applied to the archives, merely that it's not really a bad idea for a
person retrieving them to have some assurance that they came from the
IETF server and that they weren't modified in transit).

...

From glenzorn@gmail.com  Sat Aug 27 22:04:47 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F6821F8BA9 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 22:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N997bvhRazEG for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 22:04:46 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 62C2921F8BA6 for <ietf@ietf.org>; Sat, 27 Aug 2011 22:04:46 -0700 (PDT)
Received: by gxk19 with SMTP id 19so4641679gxk.31 for <ietf@ietf.org>; Sat, 27 Aug 2011 22:06:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=4HArKl5Jh/91Eu8CFKxW1zTySKVtLJpIg9SeYn1cYQo=; b=IepXHKbgmdhx5kt/W/rSfP/gcBVyamhAmdumJMl0ZslB7JlIZzqz/dqnJrYASiGE8H 6+TxwHpmpENVKt3lgdhg2vbFXMCFzEjPM1dki7/H7gm/xuH1nAtnmTfVyF6yyx2mKXjN fBy4noztaHQyK+hXAjUfFRGKCHl/1DsOeHmEo=
Received: by 10.231.29.138 with SMTP id q10mr6692354ibc.87.1314507966905; Sat, 27 Aug 2011 22:06:06 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-121-237-150.revip2.asianet.co.th [124.121.237.150]) by mx.google.com with ESMTPS id m21sm1815984ibf.8.2011.08.27.22.05.59 (version=SSLv3 cipher=OTHER); Sat, 27 Aug 2011 22:06:05 -0700 (PDT)
Message-ID: <4E59CCB3.6060904@gmail.com>
Date: Sun, 28 Aug 2011 12:05:55 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.com> <4E5905D5.40607@dcrocker.net> <CABcZeBM4CUggUqgKALjktQDrAvthFGJM3FChh3nqBj+k2_TXwg@mail.gmail.com>
In-Reply-To: <CABcZeBM4CUggUqgKALjktQDrAvthFGJM3FChh3nqBj+k2_TXwg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 05:04:47 -0000

On 8/27/2011 10:30 PM, Eric Rescorla wrote:

> On Sat, Aug 27, 2011 at 7:57 AM, Dave CROCKER <dhc@dcrocker.net> wrote:
>>
>>
>> On 8/27/2011 7:48 AM, Cullen Jennings wrote:
>>>
>>> What I have heard is that the community would prefer going to locations
>>> that were easy to travel to over "interesting".
>>
>>
>> How do you reconcile this assertion against the clearly positive group
>> reactions to Prague and Quebec?
>>
>> FYI, in relative terms, even Minneapolis is second-tier.
> 
> I have no idea what the "community" wants--and I'm not convinced that
> the data we
> have available lets us assess that, for the usual reasons about the
> difficulty of doing
> accurate surveying--but speaking solely for myself, I'm at IETF to
> work, so my priorities
> center around the things that make it easy to get work done. This
> basically boils down
> to cost  and convenience.

Good to hear.  Getting rid of cookies can save a _lot_ of money & since
you're "at IETF to work" I'm sure you wouldn't mind if the conditions
more closely approximated those of the typical office; no office I've
ever worked in has provided free cookies & beverages twice a day...

> 
> Within these general parameters, my priorities are something like:
> 1. Cost:
>     - Travel
>     - Hotel
> 
> Rationale: airfare tends to not be that flexible, but it's generally
> possible to find a cheaper
> hotel if you try (as several people have observed). However, if the
> conference hotel
> is $300/night, then this is probably going to trickle down some into
> cheaper hotels so
> it's not like hotel doesn't matter.
> 
> 
> 2. Convenience:
>     - Length of trip.
>     - Local services
> 
> Rationale: travel time is time I'm not working (yeah, we all try, but
> I'm not that effective
> and I suspect most people are not.) Lack of local services means less
> time meeting
> and more time rushing around trying to find lunch before the next
> meeting, walking to
> and from the hotel, etc.

So, do you live in your office?  Next door to the building?  Across the
street from the office park?  If not, why are you applying criteria to
the IETF "workplace" that you don't to everyday employment?  For that
matter, for one whose (not primary, but _only_) purpose is work, finding
lunch is a non-problem: you simply eat whatever is closest, quickest,
most efficient, without any regard to taste or surroundings (e.g., the
company cafeteria, analogous in this case to the hotel restaurant(s)).
WRT walking to and from the hotel, I know that I, at least, am not paid
to type (if I was, my clients would be getting a really bad deal ;-).  I
get paid to think, and I'm pretty sure that you are, too.  I don't know
you very well, but I think it's a sure bet that you can think & walk at
the same time :-).

...

From interfect@gmail.com  Sat Aug 27 22:24:06 2011
Return-Path: <interfect@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E409121F8BAD for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 22:24:06 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssXVsn08g2sC for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 22:24:06 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 440D821F8BAC for <ietf@ietf.org>; Sat, 27 Aug 2011 22:24:06 -0700 (PDT)
Received: by qwc23 with SMTP id 23so3246876qwc.31 for <ietf@ietf.org>; Sat, 27 Aug 2011 22:25:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=cBE+FEAx6Wp1bwKJjzAK2qJbQLAFCvNlKeIJb3b7Rfs=; b=mOeXSESGvRlkDS25KbX12aFx9WcCZchmDHsOB7u4TnxVgEqyq66Gwr3Bwq2CGG5jxJ hvtYrJd36ry4/M0bYlQ+UcXqi0HS3NSEBkjEC+Eggnd272qGNNmb3LycZqJqpx9DEwpQ IaRiNBhqj30emM58E2ah0+L2hYRkSsjGvny8c=
MIME-Version: 1.0
Received: by 10.229.240.72 with SMTP id kz8mr4121142qcb.114.1314509126958; Sat, 27 Aug 2011 22:25:26 -0700 (PDT)
Received: by 10.229.84.146 with HTTP; Sat, 27 Aug 2011 22:25:26 -0700 (PDT)
Received: by 10.229.84.146 with HTTP; Sat, 27 Aug 2011 22:25:26 -0700 (PDT)
Date: Sun, 28 Aug 2011 00:25:26 -0500
Message-ID: <CADPp2fCaCvddvP5P2AwLmBLpMcfVuEt7OhVe0Ft=SeW1Yca4ew@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
From: Adam Novak <interfect@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
Content-Type: multipart/alternative; boundary=0016364d2fa7910c6304ab8a01dd
Cc: Cullen Jennings <fluffy@cisco.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 05:24:07 -0000

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

On Aug 28, 2011 12:06 AM, "Glen Zorn" <glenzorn@gmail.com> wrote:
> Good to hear.  Getting rid of cookies can save a _lot_ of money & since
> you're "at IETF to work" I'm sure you wouldn't mind if the conditions
> more closely approximated those of the typical office; no office I've
> ever worked in has provided free cookies & beverages twice a day...
>

In my experience, computer industry employers often provide free snacks and
beverages, since hungry/thirsty/caffine-deprived developers write bad code.
It's also a better value than paying them more, in terms of how much they
like you.

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

<p><br>
On Aug 28, 2011 12:06 AM, &quot;Glen Zorn&quot; &lt;<a href=3D"mailto:glenz=
orn@gmail.com">glenzorn@gmail.com</a>&gt; wrote:<br>
&gt; Good to hear. =A0Getting rid of cookies can save a _lot_ of money &amp=
; since<br>
&gt; you&#39;re &quot;at IETF to work&quot; I&#39;m sure you wouldn&#39;t m=
ind if the conditions<br>
&gt; more closely approximated those of the typical office; no office I&#39=
;ve<br>
&gt; ever worked in has provided free cookies &amp; beverages twice a day..=
.<br>
&gt;</p>
<p>In my experience, computer industry employers often provide free snacks =
and beverages, since hungry/thirsty/caffine-deprived developers write bad c=
ode. It&#39;s also a better value than paying them more, in terms of how mu=
ch they like you.</p>


--0016364d2fa7910c6304ab8a01dd--

From glenzorn@gmail.com  Sat Aug 27 23:34:28 2011
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB44F21F8B28 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 23:34:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSM+hoa1U3nL for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 23:34:28 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA8C21F8B18 for <ietf@ietf.org>; Sat, 27 Aug 2011 23:34:28 -0700 (PDT)
Received: by yie12 with SMTP id 12so3221728yie.31 for <ietf@ietf.org>; Sat, 27 Aug 2011 23:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3Aria2xaP7Zbf1F+lvwzKW0hSISSSQdLffKo+8RIJdk=; b=Z0gdEGJR8uJYfJkT9JDCL0n5sU+QrwQYJVknpyhrotJfc7u58aQMbPOQpBi5orwweF pDVfVzJDgwbJSQTbe8gSw76kyymN/yOAjpTN74wMsFTCdFosYCv3YcQVJar8JBVqOZ/C yD0U4X96ZYwKXFl5UWjjGRkMuEzZQaU/7hD7I=
Received: by 10.42.129.135 with SMTP id q7mr3448220ics.84.1314513348944; Sat, 27 Aug 2011 23:35:48 -0700 (PDT)
Received: from [192.168.1.98] (ppp-124-121-237-150.revip2.asianet.co.th [124.121.237.150]) by mx.google.com with ESMTPS id b9sm1851254ibb.49.2011.08.27.23.35.43 (version=SSLv3 cipher=OTHER); Sat, 27 Aug 2011 23:35:47 -0700 (PDT)
Message-ID: <4E59E1BD.2000606@gmail.com>
Date: Sun, 28 Aug 2011 13:35:41 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Adam Novak <interfect@gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <CADPp2fCaCvddvP5P2AwLmBLpMcfVuEt7OhVe0Ft=SeW1Yca4ew@mail.gmail.com>
In-Reply-To: <CADPp2fCaCvddvP5P2AwLmBLpMcfVuEt7OhVe0Ft=SeW1Yca4ew@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 06:34:28 -0000

On 8/28/2011 12:25 PM, Adam Novak wrote:

> 
> On Aug 28, 2011 12:06 AM, "Glen Zorn" <glenzorn@gmail.com
> <mailto:glenzorn@gmail.com>> wrote:
>> Good to hear.  Getting rid of cookies can save a _lot_ of money & since
>> you're "at IETF to work" I'm sure you wouldn't mind if the conditions
>> more closely approximated those of the typical office; no office I've
>> ever worked in has provided free cookies & beverages twice a day...
>>
> 
> In my experience, computer industry employers often provide free snacks
> and beverages, since hungry/thirsty/caffine-deprived developers write
> bad code. It's also a better value than paying them more, in terms of
> how much they like you.

I'm familiar with the refrigerator full of caffeinated sugar water, even
the occasional tray of treats or keg of beer, but cookies (often 2 or 3
varieties)/brownies (ditto), fresh fruit, crudites & dip, twice a day?
Wow, I've really been working the wrong places...


From moore@network-heretics.com  Sat Aug 27 23:41:21 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B729B21F886A for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 23:41:21 -0700 (PDT)
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, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4Zrc9Fq-HM9 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 23:41:21 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 2844421F8783 for <ietf@ietf.org>; Sat, 27 Aug 2011 23:41:21 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5BE7A20740; Sun, 28 Aug 2011 02:42:39 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 28 Aug 2011 02:42:39 -0400
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=XY/k5Cona26cwG4wgpjjfYVwgoQ=; b=JM alPee98Mhsnt7M82DXkaX/BnHMa2rWFJU4aztiyHZjghCCSXmTw5FaDER0RkaAE+ 0OFJJmWY5yK1lnsJlR7FuWlX0LKPykbFbUPw39r2w9n4d8rjNrk+SOOdO66mu3/0 Bwf1KxCx6yjTv9ag6v4Pg60RTXA1YxN7HbefdTdLc=
X-Sasl-enc: IDt6kpgYzMphgVqXvMrnNEImowzXTzrNAyIfjdJ/irvd 1314513759
Received: from [172.27.105.117] (unknown [204.245.56.3]) by mail.messagingengine.com (Postfix) with ESMTPA id 1CEF4B600DE; Sun, 28 Aug 2011 02:42:39 -0400 (EDT)
Subject: Re: Hyatt Taipei cancellation policy?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E59E1BD.2000606@gmail.com>
Date: Sun, 28 Aug 2011 02:42:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3769C84B-6B39-46FD-AFD2-74614BC53A78@network-heretics.com>
References: <CADPp2fCaCvddvP5P2AwLmBLpMcfVuEt7OhVe0Ft=SeW1Yca4ew@mail.gmail.com> <4E59E1BD.2000606@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Cullen Jennings <fluffy@cisco.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 06:41:21 -0000

On Aug 28, 2011, at 2:35 AM, Glen Zorn wrote:

> I'm familiar with the refrigerator full of caffeinated sugar water, =
even
> the occasional tray of treats or keg of beer, but cookies (often 2 or =
3
> varieties)/brownies (ditto), fresh fruit, crudites & dip, twice a day?
> Wow, I've really been working the wrong places...

some companies will do almost anything to keep their employees at work =
as long as possible every day.

Keith



From yaakov_s@rad.com  Sun Aug 28 05:42:32 2011
Return-Path: <yaakov_s@rad.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3F521F8853 for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 05:42:32 -0700 (PDT)
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_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aUzpr6HQSzav for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 05:42:30 -0700 (PDT)
Received: from antivir1.rad.co.il (mx1-q.rad.co.il [80.74.100.136]) by ietfa.amsl.com (Postfix) with ESMTP id 495BC21F85A3 for <ietf@ietf.org>; Sun, 28 Aug 2011 05:42:28 -0700 (PDT)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 28 Aug 2011 15:43:36 +0300
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.323.3; Sun, 28 Aug 2011 15:43:35 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%14]) with mapi id 14.01.0323.003; Sun, 28 Aug 2011 15:43:35 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Questionnaire to survey opinion concerning a possible redefinition	of UTC
Thread-Topic: Questionnaire to survey opinion concerning a possible redefinition	of UTC
Thread-Index: AQHMYxEh+65TtlZ60UCoHwPbrsrzFpUyNobw
Date: Sun, 28 Aug 2011 12:43:34 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903FA7286@EXRAD5.ad.rad.co.il>
References: <20110825102401.GA10559@nic.fr>
In-Reply-To: <20110825102401.GA10559@nic.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {E2577E3E-881A-4D75-8CD4-C98ED4AEFD45}
x-cr-hashedpuzzle: K64= AuPJ AwKn A1LM BZmI CKmo CVyc C8dW FU9x GZXs KzEA Llrf NsAw N0GW REqA TR/T; 2; YgBvAHIAdAB6AG0AZQB5AGUAcgBAAG4AaQBjAC4AZgByADsAaQBlAHQAZgBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {E2577E3E-881A-4D75-8CD4-C98ED4AEFD45}; eQBhAGEAawBvAHYAXwBzAEAAcgBhAGQALgBjAG8AbQA=; Sun, 28 Aug 2011 12:43:33 GMT; UgBFADoAIABRAHUAZQBzAHQAaQBvAG4AbgBhAGkAcgBlACAAdABvACAAcwB1AHIAdgBlAHkAIABvAHAAaQBuAGkAbwBuACAAYwBvAG4AYwBlAHIAbgBpAG4AZwAgAGEAIABwAG8AcwBzAGkAYgBsAGUAIAByAGUAZABlAGYAaQBuAGkAdABpAG8AbgAJAG8AZgAgAFUAVABDAA==
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 12:42:32 -0000

On the one hand, abolishing leap seconds would help us with the problem of =
conversion
from the UTC-based NTP timescale and the TAI-based IEEE-1588 and GPS timesc=
ales.
On the other hand, it will require updating all software that computes
local sunrise and sunset times (e.g., for radio propagation).

However, the real problem is not related to communications or software.
The real problem is that local time is based on UTC since it needs to be as=
tronomically meaningful.=20
If leap seconds are abolished and local time starts drifting away from "ear=
th time"
then in a few hundred years we will accumulate an hour of error,
and in a few thousand years it will be dark during much of the working day.

This is similar to the draft of the months of the Islamic calendar,
where a particular month may appear in the winter or summer.

I know that most of us don't worry about what is going to happen hundreds o=
f years hence,
but think of the Y2K-like fixes that will have to be made for leap-hours !

Y(J)S


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ste=
phane Bortzmeyer
Sent: Thursday, August 25, 2011 13:24
To: ietf@ietf.org
Subject: Questionnaire to survey opinion concerning a possible redefinition=
 of UTC

Since several RFCs rely on UTC and leap seconds (3339, 4765, 5905, etc), th=
is questionnaire may be of interest for some persons [the Web page mentions=
 two articles, if you are in a hurry, the first one is the PRO and the seco=
nd one the CON]. One more week to comment.

http://hpiers.obspm.fr/eop-pc/index.php?index=3Dquestionnaire


QUESTIONNAIRE TO SURVEY OPINION CONCERNING A POSSIBLE REDEFINITION OF UTC

Universal Time, the conventional measure of Earth rotation is the tradition=
al basis for civil timekeeping. Clocks worldwide are synchronized via Coord=
inated Universal Time (UTC), an atomic time scale recommended by the Radioc=
ommunications Sector of the International Telecommunications Union (ITU-R) =
and calculated by the Bureau International des Poids et Mesures (BIPM) on t=
he basis of atomic clock data from around the world.

UTC is computed from TAI by the introduction of leap seconds such that UTC =
is maintained within 1 second of UT1. Since 1972, these leap seconds have b=
een added on December 31 or June 30, at the rate of about one every 18 mont=
hs. Since 1 January 2009, 0:00 UTC, UTC-TAI=3D -34s.

After years of discussions within the scientific community, a proposal to f=
undamentally redefine UTC will come to a conclusive vote in January 2012 at=
 the ITU-R in Geneva. If this proposal is approved, it would be effective f=
ive years later. It would halt the intercalary adjustments known as leap se=
conds that maintain UTC as a form of Universal Time.
Then, UTC would not keep pace with Earth rotation and the value of DUT1 wou=
ld become unconstrained.Therefore UTC would no longer be directly useful fo=
r various technical applications which rely on it being less than 1 second =
from UT1. Such applications would require a separate access to UT1, such as=
 through the publication of DUT1 by other means.

The objective of the survey is to find out the strength of opinion for main=
taining or changing the present system.

Your response is appreciated before 31 August 2011

From ekr@rtfm.com  Sun Aug 28 06:02:15 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0972E21F8AD3 for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 06:02:15 -0700 (PDT)
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=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3qL-xGSVW3LE for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 06:02:14 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 21B3821F858D for <ietf@ietf.org>; Sun, 28 Aug 2011 06:02:13 -0700 (PDT)
Received: by wyg8 with SMTP id 8so3927539wyg.31 for <ietf@ietf.org>; Sun, 28 Aug 2011 06:03:35 -0700 (PDT)
Received: by 10.227.35.2 with SMTP id n2mr376144wbd.26.1314536615217; Sun, 28 Aug 2011 06:03:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.3.5 with HTTP; Sun, 28 Aug 2011 06:03:14 -0700 (PDT)
In-Reply-To: <4E59CCB3.6060904@gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.com> <4E5905D5.40607@dcrocker.net> <CABcZeBM4CUggUqgKALjktQDrAvthFGJM3FChh3nqBj+k2_TXwg@mail.gmail.com> <4E59CCB3.6060904@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 28 Aug 2011 06:03:14 -0700
Message-ID: <CABcZeBNwU6wedD7ed=buHwWpE5EtPCLpD=pVmHb5qj_Mi5HSeA@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
To: Glen Zorn <glenzorn@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cullen Jennings <fluffy@cisco.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 13:02:15 -0000

On Sat, Aug 27, 2011 at 10:05 PM, Glen Zorn <glenzorn@gmail.com> wrote:
> On 8/27/2011 10:30 PM, Eric Rescorla wrote:
>
>> On Sat, Aug 27, 2011 at 7:57 AM, Dave CROCKER <dhc@dcrocker.net> wrote:
>>>
>>>
>>> On 8/27/2011 7:48 AM, Cullen Jennings wrote:
>>>>
>>>> What I have heard is that the community would prefer going to location=
s
>>>> that were easy to travel to over "interesting".
>>>
>>>
>>> How do you reconcile this assertion against the clearly positive group
>>> reactions to Prague and Quebec?
>>>
>>> FYI, in relative terms, even Minneapolis is second-tier.
>>
>> I have no idea what the "community" wants--and I'm not convinced that
>> the data we
>> have available lets us assess that, for the usual reasons about the
>> difficulty of doing
>> accurate surveying--but speaking solely for myself, I'm at IETF to
>> work, so my priorities
>> center around the things that make it easy to get work done. This
>> basically boils down
>> to cost =A0and convenience.
>
> Good to hear. =A0Getting rid of cookies can save a _lot_ of money & since
> you're "at IETF to work" I'm sure you wouldn't mind if the conditions
> more closely approximated those of the typical office; no office I've
> ever worked in has provided free cookies & beverages twice a day...

I'm not sure that getting rid of food at breaks would save a lot of money.
Do you know what the actual numbers are as a percentage of the
overall cost?

With that said, it's actually quite common for workplaces to offer free
snacks and/or beverages, not only twice a day but 24/7. Maybe you
should consider a different class of employers.


>> Within these general parameters, my priorities are something like:
>> 1. Cost:
>> =A0 =A0 - Travel
>> =A0 =A0 - Hotel
>>
>> Rationale: airfare tends to not be that flexible, but it's generally
>> possible to find a cheaper
>> hotel if you try (as several people have observed). However, if the
>> conference hotel
>> is $300/night, then this is probably going to trickle down some into
>> cheaper hotels so
>> it's not like hotel doesn't matter.
>>
>>
>> 2. Convenience:
>> =A0 =A0 - Length of trip.
>> =A0 =A0 - Local services
>>
>> Rationale: travel time is time I'm not working (yeah, we all try, but
>> I'm not that effective
>> and I suspect most people are not.) Lack of local services means less
>> time meeting
>> and more time rushing around trying to find lunch before the next
>> meeting, walking to
>> and from the hotel, etc.
>
> So, do you live in your office? =A0Next door to the building? =A0Across t=
he
> street from the office park? =A0If not, why are you applying criteria to
> the IETF "workplace" that you don't to everyday employment?

Funny you should mention that, since I work from home most of the time
in part to minimize commute time.


>=A0For that
> matter, for one whose (not primary, but _only_) purpose is work,

**** Strawman alert ****


> finding
> lunch is a non-problem: you simply eat whatever is closest, quickest,
> most efficient, without any regard to taste or surroundings (e.g., the
> company cafeteria, analogous in this case to the hotel restaurant(s)).

Maybe you've noticed that the hotel restaurants are (a) expensive and
(b) tend to fill up quickly, which often makes it hard for people to actual=
ly
get in and out in the relevant time. This would of course be far worse if
there were no reasonable restaurants in the area.


> WRT walking to and from the hotel, I know that I, at least, am not paid
> to type (if I was, my clients would be getting a really bad deal ;-). =A0=
I
> get paid to think, and I'm pretty sure that you are, too. =A0I don't know
> you very well, but I think it's a sure bet that you can think & walk at
> the same time :-).

I find that I work more effectively when I have computer and Internet
available, neither of which is the situation when I'm walking to and from
the conference center. Your  mileage may vary.

-Ekr

From ned+ietf@mauve.mrochek.com  Sun Aug 28 09:47:31 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B22D921F8829 for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 09:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.279
X-Spam-Level: 
X-Spam-Status: No, score=-2.279 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vcQj+12C7omL for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 09:47:31 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id EE76C21F86B6 for <ietf@ietf.org>; Sun, 28 Aug 2011 09:47:30 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5DNYQECF4011CBS@mauve.mrochek.com> for ietf@ietf.org; Sun, 28 Aug 2011 09:47:33 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5C6AOYDC0014O5Z@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 28 Aug 2011 09:47:21 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5DNYISGAW014O5Z@mauve.mrochek.com>
Date: Sun, 28 Aug 2011 09:25:09 -0700 (PDT)
Subject: Re: https
In-reply-to: "Your message dated Sun, 28 Aug 2011 11:43:08 +0700" <4E59C75C.3010807@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com> <8F38C2201545EEF1F78C65E8@PST.JCK.COM> <01O5AUN0VTQY00VHKR@mauve.mrochek.com> <4E5880A4.2050108@gmail.com> <010001cc6496$d7f484e0$4001a8c0@gateway.2wire.net> <016201cc6499$7a5d23c0$4001a8c0@gateway.2wire.net> <4E59C75C.3010807@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314550090; i=@mrochek.com; bh=wtGVO7DkkhOxn2rN/3ab2Jk7U3c7cHUgw7prarZZsQc=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=e1Jyw+WokiL8CbtMB8Tonww2nqPy+inHCT8YEtTCMPUbeCQiPCIE5qK0DQyamDa4J nwnceoPW4UcI3Dsu/Raks+Ep5ZuAkjw4O3IL+bHt1+ezmj17pqOehk0IWXUUnd47G6 ZPOPqX4hJJceP7oova5/10ROapHC/F512tcS1xLE=
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 16:47:31 -0000

> On 8/27/2011 4:12 PM, t.petch wrote:

> > Glen
> >
> > Me again.
> >
> > Just after I posted my last message, I received a post on the ietf-ssh list,
> > hosted by netbsd.org, and looking through the 'Received: from' headers, as one
> > does on a wet Saturday morning of a Bank Holiday weekend, there was TLS, used to
> > submit the message to the server, so even spammers have caught on that TLS
> > should be used everywhere.  End to end?

As a side note, the reason spammers use TLS to submit mail is obvious: It's
required by many submission servers so they really don't have a choice. (The
reason it's required is to protect the authentication exchange, not because
there's any real expectation that it provides useful privacy protection for the
submitted email itself.)

> Apparently, from the POV of the spammer & his SMTP server.  Email is a
> store & forward system.  In any case, my original question was not about
> the definition of end-to-end, it was about Ned usage of the term "hop".

I used the term "hop" in a very generic sense to refer to moving the
data around.

>  Upon further analysis, however, it seems clear that he was referring to
> the email archives as if they are something other than simple files (as
> betrayed by his statement that "Don't pretend a transfer protection
> mechanism covering exactly one hop provides real object security,
> because it doesn't."); thus, the retrieval of the archived data would be
> the last "hop" in the email system.

And that's incorrect. For one thing, I often retrieve material from web sites
and save it rather than looking at it right there on the screen. So the
transfer of the material from the web server is in no way, shape, or form the
final hop the information takes before it is consumed. As as Keith points out,
I and many others am often forced to do such access through corporate-mandated
proxies of various sorts - another hop.

> There seem to be two problems with
> this statement: one is taking the file transfer mechanism as if it was
> part of the email system itself,

Nobody is making any such claim.

> which it obviously is not (downloading
> an archived message is no different than downloading an RFC from a Web
> site); the other being that someone, somewhere was pretending that TLS
> does something that it was never designed to do (a straw man of, AFAICT,
> Ned's invention -- I don't recall anybody making such a claim on this
> thread,

I was responding to the justification given for the use of https in this
context. The exact words used were:

> > The mail archives (and the minutes of the physical meetings)
> > are the official record of the Working Groups, IETF, etc.
> > Those archives should be available with a reasonably high
> > level of integrity and authenticity.

Nor was I the only, or even the first, to suggest that object security
is needed for this sort of protection.

> nor for that matter saying they _wanted_ "real object security"
> applied to the archives, merely that it's not really a bad idea for a
> person retrieving them to have some assurance that they came from the
> IETF server and that they weren't modified in transit).

And once again, nobody is saying that TLS doesn't give some very limited
assurance along these lines - the notion that there are claims to the contrary 
is your own strawman. What we are saying is that there are also significant
costs, those costs appear to be greater than the benefits in this case, and if
there is real concern about archive integrity there are better ways to secure
them.

Anyway, this discussion is now well past it's sell-by date, so this will be my
final response on the topic.

				Ned

From joelja@bogus.com  Sun Aug 28 11:23:10 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE4AD21F886D for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 11:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ItbB1+A6fNfR for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 11:23:10 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4A00321F8754 for <ietf@ietf.org>; Sun, 28 Aug 2011 11:23:10 -0700 (PDT)
Received: from Zorch.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7SIOQEH092532 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 28 Aug 2011 18:24:27 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E5A87DA.9090504@bogus.com>
Date: Sun, 28 Aug 2011 11:24:26 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com><801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu><FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org><66998320DD3FCC5628E32634@PST.JCK.COM><F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org><CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com><34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com><E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com><4E554C78.9000504@gmail.com><tslr54a8v7s.fsf@mit.edu><4E555B06.6000108@dcrocker.net><tslmxey8sia.fsf@mit.edu><1314218041.1973.204.camel@d430><4E55655C.6030502@bbiw.net><15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com><4E55E827.4060802@gmail.com><13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <D4AC0228-C124-4E0C-B28B-DD36400046D4@cisco.com>
In-Reply-To: <D4AC0228-C124-4E0C-B28B-DD36400046D4@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 28 Aug 2011 18:24:28 +0000 (UTC)
Cc: henk@uijterwaal.nl, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 18:23:10 -0000

On 8/27/11 11:22 , Cullen Jennings wrote:
> 
> Thanks Marshall, I had suspect the process was something like that. I
> had not realized how much the pre picking the dates reduced the
> options.

It does, it also decreased your leverage in a negotiation because you do
not have the luxury of shifting the event timewise and hotels know that.

From joelja@bogus.com  Sun Aug 28 11:30:25 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2E9721F886D; Sun, 28 Aug 2011 11:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.909
X-Spam-Level: 
X-Spam-Status: No, score=-101.909 tagged_above=-999 required=5 tests=[AWL=-0.510, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, J_CHICKENPOX_23=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CiYixnFon2ll; Sun, 28 Aug 2011 11:30:25 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 69CC121F8751; Sun, 28 Aug 2011 11:30:25 -0700 (PDT)
Received: from Zorch.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7SIVdr7093055 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 28 Aug 2011 18:31:40 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E5A898B.5050300@bogus.com>
Date: Sun, 28 Aug 2011 11:31:39 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <4E57B142.4020802@bogus.com> <4E58095D.2040509@dougbarton.us>
In-Reply-To: <4E58095D.2040509@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 28 Aug 2011 18:31:42 +0000 (UTC)
Cc: webmaster@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 18:30:25 -0000

On 8/26/11 14:00 , Doug Barton wrote:
> Joel,

"it doesn't" means that the mailing list archives do not require the use
of https, if the entry point urls point to the https server that bad in
this case...

If one has forgotten to renew a certificate before it expires, it takes
time to get a new one issued. as an operational pratice is is necessary
to track the issue and expiration dates  of such resources.

> I don't know what "It doesn't" is supposed to mean, but visiting
> https://www.ietf.org/* today with firefox it is still reporting that the
> certificate expired yesterday.
> 
> Given the volume of discussion about the topic starting yesterday when
> the problem started one could easily make a case for "it's still broken"
> being a significant "issue."
> 
> cc'ing the address listed as "Report Website Errors" on the home page.
> 
> 
> Doug
> 
> 
> On 08/26/2011 07:44, Joel jaeggli wrote:
>> It doesn't...
>>
>> http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html
>>
>> On 8/26/11 00:18 , t.petch wrote:
>>> Why does the IETF website consider it necessary to use TLS to access the mailing
>>> list archives, when they all appeared without it, or any other security, in the
>>> first place?
>>>
>>> Besides all the usual hassle of TLS, today the certificate is reported by IE as
>>> expired, which sort of sums it up.
>>>
>>> Tom Petch
>>>
>>> _______________________________________________
>>> 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 joelja@bogus.com  Sun Aug 28 12:32:31 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3F621F87C5 for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 12:32:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7fVKeqITeA0 for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 12:32:30 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7026821F886A for <ietf@ietf.org>; Sun, 28 Aug 2011 12:32:30 -0700 (PDT)
Received: from Zorch.local (adsl-99-191-195-38.dsl.pltn13.sbcglobal.net [99.191.195.38]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7SJXmas096301 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 28 Aug 2011 19:33:48 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E5A9816.8020608@bogus.com>
Date: Sun, 28 Aug 2011 12:33:42 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com> <Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com> <4E5806EC.5050304@dougbarton.us> <CADPp2fAPN3tOE-XiLuJ71XLQ2oMd5W0D93iPkuuYqHA-fC0=+A@mail.gmail.com> <4E580B54.2090304@dougbarton.us>
In-Reply-To: <4E580B54.2090304@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 28 Aug 2011 19:33:49 +0000 (UTC)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 19:32:31 -0000

On 8/26/11 14:08 , Doug Barton wrote:
> On 08/26/2011 13:57, Adam Novak wrote:
>> On Fri, Aug 26, 2011 at 3:49 PM, Doug Barton <dougb@dougbarton.us> wrote:
>>>
>>> I have a related-but-different example of how end nodes being able to
>>> know/discover direct paths to one another could be useful. Imagine a
>>> busy server network with some web servers over here, some sql servers
>>> over there, etc. All of these systems are on the same network, same
>>> switch fabric, and have the same gateway address. In an ideal world I
>>> would like them to be able to know that they can speak directly to one
>>> another without having to go through the gateway (and without my having
>>> to manually inject static routes on the hosts, which of course is both
>>> painful and un-scale'y.
>>
>> Shouldn't that be covered by the subnet mask?
> 
> Mostly, yes of course, but I'm dramatically simplifying my example for
> dramatic effect. :)
> 
>> As long as they know
>> they're on the same subnet (and ARP broadcasts will reach everyone)
>> they should just ARP for each other and not involve the router at all.
>>
>> If they are on different IP subnets, but the same Ethernet,
> 
> Yes, this is more often the case that I'm dealing with. (Working on
> fixing a problem I inherited for a new client, so per your comment below
> "don't number that way" may be the right answer.)

overlayed subnets are pretty straight-forward with ipv6 RA.

> Doug
> 
> 
>> then we
>> can either come up with a new way to do routing, or tell people not to
>> number things that way. Perhaps a subnet mask or CIDR prefix is not
>> expressive enough?
> 
> 
> 


From joelja@bogus.com  Sun Aug 28 12:53:49 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32EF621F87E2; Sun, 28 Aug 2011 12:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.849
X-Spam-Level: 
X-Spam-Status: No, score=-101.849 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, J_CHICKENPOX_23=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DghBgD22u2vy; Sun, 28 Aug 2011 12:53:48 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 93F1621F87C5; Sun, 28 Aug 2011 12:53:48 -0700 (PDT)
Received: from Zorch.local (adsl-99-191-195-38.dsl.pltn13.sbcglobal.net [99.191.195.38]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7SJt6AV097421 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 28 Aug 2011 19:55:07 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E5A9D15.7020908@bogus.com>
Date: Sun, 28 Aug 2011 12:55:01 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <4E57B142.4020802@bogus.com> <4E58095D.2040509@dougbarton.us> <4E5A898B.5050300@bogus.com>
In-Reply-To: <4E5A898B.5050300@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 28 Aug 2011 19:55:07 +0000 (UTC)
Cc: webmaster@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 19:53:49 -0000

On 8/28/11 11:31 , Joel jaeggli wrote:
> On 8/26/11 14:00 , Doug Barton wrote:
>> Joel,
> 
> "it doesn't" means that the mailing list archives do not require the use
> of https, if the entry point urls point to the https server that bad in
> this case...

To be still more specific the mailman archives do not. the ibin archive
does.

> If one has forgotten to renew a certificate before it expires, it takes
> time to get a new one issued. as an operational pratice is is necessary
> to track the issue and expiration dates  of such resources.
> 
>> I don't know what "It doesn't" is supposed to mean, but visiting
>> https://www.ietf.org/* today with firefox it is still reporting that the
>> certificate expired yesterday.
>>
>> Given the volume of discussion about the topic starting yesterday when
>> the problem started one could easily make a case for "it's still broken"
>> being a significant "issue."
>>
>> cc'ing the address listed as "Report Website Errors" on the home page.
>>
>>
>> Doug
>>
>>
>> On 08/26/2011 07:44, Joel jaeggli wrote:
>>> It doesn't...
>>>
>>> http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html
>>>
>>> On 8/26/11 00:18 , t.petch wrote:
>>>> Why does the IETF website consider it necessary to use TLS to access the mailing
>>>> list archives, when they all appeared without it, or any other security, in the
>>>> first place?
>>>>
>>>> Besides all the usual hassle of TLS, today the certificate is reported by IE as
>>>> expired, which sort of sums it up.
>>>>
>>>> Tom Petch
>>>>
>>>> _______________________________________________
>>>> 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 joelja@bogus.com  Sun Aug 28 13:11:31 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 303C721F89B8 for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 13:11:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2InnO-pFPni for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 13:11:30 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9F03221F891D for <ietf@ietf.org>; Sun, 28 Aug 2011 13:11:30 -0700 (PDT)
Received: from Zorch.local (adsl-99-191-195-38.dsl.pltn13.sbcglobal.net [99.191.195.38]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7SKCkei098432 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 28 Aug 2011 20:12:47 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E5AA139.3010002@bogus.com>
Date: Sun, 28 Aug 2011 13:12:41 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 28 Aug 2011 20:12:48 +0000 (UTC)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 20:11:31 -0000

On 8/26/11 08:04 , Worley, Dale R (Dale) wrote:
>> From: Adam Novak [interfect@gmail.com]
>>
>> "Say I wanted to send data to my friend in the flat next to mine. It is
>> idiotic that nowadays, I would use the bottleneck subscriber line to
>> my upstream ISP and my crippled upload speed and push it all the way
>> across their infrastructure to my neighbors ISP and back to the Wifi
>> router in reach of mine."

there are other ways for devices with proximity to discover each other
and establish a relationship than via existing networks.

> This is a valid point, but it's also rather rare that one wants to
> send large amounts of data directly to a friend in a neighboring flat
> but one has not manually adjusting the local routing to take that into
> account.
> 
>> If each home or mobile device was essentially [its] own autonomous
>> system, what would this do to routing table size? To ASN space
>> utilization?
> 
> There must be at least a few hundred million mobile phones with data
> capability, and a similar number of homes and small businesses with
> WiFi systems.  So we can estimate that a large fraction of a billion
> entries would be added to the routing tables.  How would that work?

putting device mobility into the DFZ is just dumb. it was a fairly bad
idea when boeing did it and at any kind of scale it would be still more
obvious.

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


From daedulus@btconnect.com  Mon Aug 29 04:22:33 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81C5D21F8B0C for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 04:22:33 -0700 (PDT)
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=-0.247, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTevYaYDLwbH for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 04:22:33 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id 67F5221F8B0A for <ietf@ietf.org>; Mon, 29 Aug 2011 04:22:30 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr10.btconnect.com with SMTP id ECH37541; Mon, 29 Aug 2011 12:23:49 +0100 (BST)
Message-ID: <021001cc6635$37c41940$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Joel jaeggli" <joelja@bogus.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <4E57B142.4020802@bogus.com> <4E58095D.2040509@dougbarton.us> <4E5A898B.5050300@bogus.com> <4E5A9D15.7020908@bogus.com>
Subject: Re: https
Date: Mon, 29 Aug 2011 12:19:56 +0200
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.4E5B76C4.00DE, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.29.93914:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4E5B76C5.013B,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 11:22:33 -0000

----- Original Message -----
From: "Joel jaeggli" <joelja@bogus.com>
To: "Doug Barton" <dougb@dougbarton.us>
Cc: "t.petch" <daedulus@btconnect.com>; "IETF Discussion" <ietf@ietf.org>;
<webmaster@ietf.org>
Sent: Sunday, August 28, 2011 9:55 PM
> On 8/28/11 11:31 , Joel jaeggli wrote:
> > On 8/26/11 14:00 , Doug Barton wrote:
> >> Joel,
> >
> > "it doesn't" means that the mailing list archives do not require the use
> > of https, if the entry point urls point to the https server that bad in
> > this case...
>
> To be still more specific the mailman archives do not. the ibin archive
> does.

Joel

Um, I do not understand that statement; mailman I know, ibin I do not, but
either way, I am an archive user, not an e-mail administrator, and while I can
access some archives with http:, notably from the web page for specific WG,
others I cannot, notably from
http://www.ietf.org/list/nonwg.html
which is the only way I can access some of them, as far as I know: and on that
page, there are some 250 html anchors with a scheme of 'https:'
Edit the scheme to http: and the web site puts the 's' back in so either way,
I am stuffed.

Tom Petch

> > If one has forgotten to renew a certificate before it expires, it takes
> > time to get a new one issued. as an operational pratice is is necessary
> > to track the issue and expiration dates  of such resources.
> >
> >> I don't know what "It doesn't" is supposed to mean, but visiting
> >> https://www.ietf.org/* today with firefox it is still reporting that the
> >> certificate expired yesterday.
> >>
> >> Given the volume of discussion about the topic starting yesterday when
> >> the problem started one could easily make a case for "it's still broken"
> >> being a significant "issue."
> >>
> >> cc'ing the address listed as "Report Website Errors" on the home page.
> >>
> >>
> >> Doug
> >>
> >>
> >> On 08/26/2011 07:44, Joel jaeggli wrote:
> >>> It doesn't...
> >>>
> >>> http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html
> >>>
> >>> On 8/26/11 00:18 , t.petch wrote:
> >>>> Why does the IETF website consider it necessary to use TLS to access the
mailing
> >>>> list archives, when they all appeared without it, or any other security,
in the
> >>>> first place?
> >>>>
> >>>> Besides all the usual hassle of TLS, today the certificate is reported by
IE as
> >>>> expired, which sort of sums it up.
> >>>>
> >>>> Tom Petch
> >>>>
> >>>> _______________________________________________
> >>>> 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 wesley.george@twcable.com  Mon Aug 29 05:02:00 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D163C21F8B0D for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 05:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.102
X-Spam-Level: 
X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[AWL=0.361,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dd8A18zQDlGw for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 05:02:00 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id CBB5C21F8AD6 for <ietf@ietf.org>; Mon, 29 Aug 2011 05:01:59 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.67,442,1309752000"; d="scan'208";a="252808347"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 29 Aug 2011 08:02:40 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Mon, 29 Aug 2011 08:03:23 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Eric Rescorla <ekr@rtfm.com>, Glen Zorn <glenzorn@gmail.com>
Date: Mon, 29 Aug 2011 08:03:58 -0400
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: Acxlg84NTLfMH6J9QnKZrOUSFFdvzAAveVJA
Message-ID: <34E4F50CAFA10349A41E0756550084FB0DBB412E@PRVPEXVS04.corp.twcable.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <DBA69BE1-B180-4D3B-8BDB-E464C1113A62@cisco.com> <4E5905D5.40607@dcrocker.net> <CABcZeBM4CUggUqgKALjktQDrAvthFGJM3FChh3nqBj+k2_TXwg@mail.gmail.com> <4E59CCB3.6060904@gmail.com> <CABcZeBNwU6wedD7ed=buHwWpE5EtPCLpD=pVmHb5qj_Mi5HSeA@mail.gmail.com>
In-Reply-To: <CABcZeBNwU6wedD7ed=buHwWpE5EtPCLpD=pVmHb5qj_Mi5HSeA@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: Cullen Jennings <fluffy@cisco.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 12:02:00 -0000

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Eri=
c Rescorla
Sent: Sunday, August 28, 2011 9:03 AM
Subject: Re: Hyatt Taipei cancellation policy?

>I find that I work more effectively when I have computer and Internet
available

WEG] Me too, emphasis on the Internet. And this is exactly the reason why I=
 simply don't buy the "just find a cheaper hotel instead of the IETF one" a=
rgument as the only solution for people put off by the price of the main ho=
tel. Those staying in hotels with non-IETF internet access find that the co=
mbination of some non-trivial number of heavy internet users plus underprov=
isioned wireless, DHCP pool, and uplink, lack of IPv6 support + NAT =3D int=
ernet service that is somewhere between annoyingly crappy and unusably crap=
py.

While I am somewhat sensitive to hotel price, for me, first-class internet =
service in my hotel room is worth a small bump in price so that I don't hav=
e to spend hours before and after sessions are over squatting in the confer=
ence area or hotel common area to get a decent connection to get work done.=
 If you're willing to make that tradeoff in the interest of cheaper hotel, =
more power to you, but given the number of complaints about Delta's network=
 in QC, I think that this is something that people tend to forget until the=
y get there... (and before you say anything, I realize that Delta was the o=
fficial overflow hotel, but I think the point is still valid).

I'll also note that I don't think that it's strictly necessary for the hote=
l and conference center to be connected. I thought that the arrangement in =
Stockholm was quite nice.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From hartmans@mit.edu  Mon Aug 29 06:56:51 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F40A421F8B1E; Mon, 29 Aug 2011 06:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C0GHbdOzl27W; Mon, 29 Aug 2011 06:56:50 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 892E721F8B1D; Mon, 29 Aug 2011 06:56:50 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (mcd0536d0.tmodns.net [208.54.5.205]) (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 57D6E203CB; Mon, 29 Aug 2011 10:00:22 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6B91642B7; Mon, 29 Aug 2011 09:58:03 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: <gareth.richards@rsa.com>
Subject: Re: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com>
Date: Mon, 29 Aug 2011 09:58:03 -0400
In-Reply-To: <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> (gareth richards's message of "Fri, 26 Aug 2011 11:04:22 -0400")
Message-ID: <tsl62lgpbf8.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@ietf.org, david.black@emc.com, ietf-krb-wg@lists.anl.gov, hartmans-ietf@mit.edu, gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 13:56:51 -0000

>>>>>   <gareth.richards@rsa.com> writes:

    >> > Why should we require that alg-ids be registered URIs?
    >> 
    >> That's not my concern - the existing first paragraph of the IANA
    >> considerations section in the draft requires IANA registration
    >> (or at least tries to) by pointing to the PSKC registry.  My
    >> concern is that if this is going to be done, it needs to be done
    >> right (duh!), and the current text is insufficient. Please take
    >> the issue of whether to use IANA for this purpose up with Gareth
    >> and the WG.
    >> 
    >> > I have no problem with the IETF registering its algorithms
    >> there, or us > encouraging people to register them there, but
    >> it's a URI. What purpose > is served by forcing registration?
    >> 
    >> Hmm - more than one URI for the same algorithm might cause
    >> interoperability problems.
    >> 

g>Some form of identifier will be required for the otp-algID in the PA-OTP-CHALLENGE and the PA-OTP-REQUEST and from what I remember about when this was first discussed, it was agreed that it would make sense to use the registry of identifiers already being established for PSKC rather than produce a duplicate one.  My assumption was that a registry would be required to ensure that the URIs were unique.

I don't really care so just fix the current text to resolve David's
concern.  My point was simply that whatever spec tells you how to use
some algorithm with Kerberos can provide a unique URI and I'm
unconvinced that it matters where that URI is drawn so long as everyone
agrees on the URI.  Having a registry for everything the IETF does is
fine; reusing an existing registry is better.  Constraining what
non-IETF people do seems kind of silly but they will not listen to us
anyway, so no harm is done.

From hartmans@mit.edu  Mon Aug 29 07:02:16 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C307B21F8A35; Mon, 29 Aug 2011 07:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.349
X-Spam-Level: 
X-Spam-Status: No, score=-103.349 tagged_above=-999 required=5 tests=[AWL=-1.084, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjhGKqOPjBiD; Mon, 29 Aug 2011 07:02:16 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3258921F8B09; Mon, 29 Aug 2011 07:02:16 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (mcd0536d0.tmodns.net [208.54.5.205]) (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 9485B203CB; Mon, 29 Aug 2011 10:05:52 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 1C74D42B7; Mon, 29 Aug 2011 10:03:35 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Henry B. Hotz" <hotz@jpl.nasa.gov>
Subject: Re: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> <87sjoocgxs.fsf@latte.josefsson.org> <D59A1036-ABCA-43CE-B3D3-1D3334CABE2B@jpl.nasa.gov>
Date: Mon, 29 Aug 2011 10:03:35 -0400
In-Reply-To: <D59A1036-ABCA-43CE-B3D3-1D3334CABE2B@jpl.nasa.gov> (Henry B. Hotz's message of "Fri, 26 Aug 2011 20:20:54 -0700")
Message-ID: <tsl1uw4pb60.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: Simon Josefsson <simon@josefsson.org>, "ietf@ietf.org" <ietf@ietf.org>, "gareth.richards@rsa.com" <gareth.richards@rsa.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf-krb-wg@lists.anl.gov" <ietf-krb-wg@lists.anl.gov>, "hartmans-ietf@mit.edu" <hartmans-ietf@mit.edu>, "david.black@emc.com" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 14:02:16 -0000

What information required by the PSC registry do we not need?
The only thing I see is the XML information, but it looks like that
could be blank.

From iljitsch@muada.com  Mon Aug 29 07:40:23 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6488121F8B0F for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-nwuBwSURDe for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:40:18 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id CE64B21F8B0E for <ietf@ietf.org>; Mon, 29 Aug 2011 07:40:17 -0700 (PDT)
Received: from dulcinea.it.uc3m.es ([163.117.139.50]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p7TEfOwt034852 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Aug 2011 16:41:25 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com>
Date: Mon, 29 Aug 2011 16:40:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: Cullen Jennings <fluffy@cisco.com>, henk@uijterwaal.nl, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 14:40:23 -0000

On 27 Aug 2011, at 17:43 , Marshall Eubanks wrote:

> I think that the meeting selection process is inherently iterative. =
Pseudo code might be something like

> - Find a list of all venues we can in the target area for the target =
week. The number of these is rarely if ever more than 10.

So the most important objective is having the meeting during a week that =
was selected years in advance.

I think we are now paying the price for that inflexibility.

Obviously the date needs to be fixed at some point, but does it really =
have to be six years in advance? ( =
http://www.ietf.org/meeting/upcoming.html )


From iljitsch@muada.com  Mon Aug 29 07:46:53 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6ACB21F84E6 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level: 
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBDrkD6sNrbI for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:46:53 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 25D2621F84D1 for <ietf@ietf.org>; Mon, 29 Aug 2011 07:46:52 -0700 (PDT)
Received: from dulcinea.it.uc3m.es ([163.117.139.50]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p7TEm6M8034893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Aug 2011 16:48:06 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: https
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com>
Date: Mon, 29 Aug 2011 16:47:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0250963E-709D-433C-9D2B-FC29130DA078@muada.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net> <4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv> <001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net> <005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net> <CAHBU6ivL65M5mgyD4bvTaS_UjmNn4=zNbpQAOMYkKi96KSnrGg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: SM <sm@resistor.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 14:46:53 -0000

On 26 Aug 2011, at 16:24 , Tim Bray wrote:

> I'm increasingly coming to think that *everything* should be done with
> TLS unless you can prove it's harmful.  Call me paranoid, but given
> the general state of the world, secure-by-default seems like the way
> to go.  -Tim

That would be nice in a world where such security didn't slow everything =
down, especially on high RTT links. HTTPS really makes everything a =
whole lot slower on a mobile device, not to mention using extra battery =
power.

There is absolutely no reason mailinglist archives or most other stuff =
on www.ietf.org needs more protection than any other random web page and =
as such imposing the additional overhead on other people is very =
annoying.=

From moore@network-heretics.com  Mon Aug 29 07:50:20 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8DD921F8B6D for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.606
X-Spam-Level: 
X-Spam-Status: No, score=-3.606 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xFEY+upA1eFp for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:50:20 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 2C9EA21F8B64 for <ietf@ietf.org>; Mon, 29 Aug 2011 07:50:20 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 46F7E20802; Mon, 29 Aug 2011 10:51:44 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 29 Aug 2011 10:51:44 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=+Cj HjOz9jE7dgqyZ/63x1N3kHIY=; b=JpbBQE5vgkU1lDl0MXrJDP0hVHEfN2gSb/k 3NpPKZPPU3bukZOCmkcQj8vZ3LFE6Ytzx33RQ4DR5GHBdDGj/AZPE+J8a1X5HC9S qrzA4fg+TNz9gChXV41vDZH2sH/80MObEjVAwEfyXmv6/STV9Y0TQSQLfkZPkphZ iRLm6JdE=
X-Sasl-enc: sC8gHYIkeotGbuQ1JU4kCZBG2AYGyimX0gRQQ+jgvwGb 1314629504
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 0C149A00440; Mon, 29 Aug 2011 10:51:44 -0400 (EDT)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-27--832630402
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com>
Date: Mon, 29 Aug 2011 10:51:42 -0400
Message-Id: <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
X-Mailer: Apple Mail (2.1084)
Cc: Cullen Jennings <fluffy@cisco.com>, henk@uijterwaal.nl, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 14:50:21 -0000

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


On Aug 29, 2011, at 10:40 AM, Iljitsch van Beijnum wrote:

> Obviously the date needs to be fixed at some point, but does it really =
have to be six years in advance? ( =
http://www.ietf.org/meeting/upcoming.html )

I've been wondering the same thing.   Would it be reasonable to specify =
ballpark dates (say +/- 1 week) six years out as long as the actual =
dates were nailed down say three years out?

Keith


--Apple-Mail-27--832630402
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 Aug 29, 2011, at 10:40 AM, Iljitsch van Beijnum =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Obviously the =
date needs to be fixed at some point, but does it really have to be six =
years in advance? (<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://www.ietf.org/meeting/upcoming.html">http://www.ietf.org/mee=
ting/upcoming.html</a><span =
class=3D"Apple-converted-space">&nbsp;</span>)<br></span></blockquote></di=
v><br><div>I've been wondering the same thing. &nbsp; Would it be =
reasonable to specify ballpark dates (say +/- 1 week) six years out as =
long as the actual dates were nailed down say three years =
out?</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-27--832630402--

From iljitsch@muada.com  Mon Aug 29 07:57:58 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E50E821F8B3A for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22Yndz76Mel8 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:57:58 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 351FA21F8B39 for <ietf@ietf.org>; Mon, 29 Aug 2011 07:57:58 -0700 (PDT)
Received: from dulcinea.it.uc3m.es ([163.117.139.50]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p7TEx4SQ034958 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Aug 2011 16:59:04 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: authenticated archives, was https
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4E592C81.4040402@bogus.com>
Date: Mon, 29 Aug 2011 16:58:34 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <177A3F06-8892-4278-BB87-690F4F416431@muada.com>
References: <20110827143104.89801.qmail@joyce.lan> <02ba01cc64ce$e6970800$4001a8c0@gateway.2wire.net> <4E592C81.4040402@bogus.com>
To: Joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: John Levine <johnl@iecc.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 14:57:59 -0000

On 27 Aug 2011, at 19:42 , Joel jaeggli wrote:

>> In the mean time, I would like TLS exterminated from the IETF website =
- any
>> reason will do - since the cost to me far outweighs the benefit.  So =
who decided to put it in, and on what grounds?

Good question. For me it also causes more trouble than benefits. But =
let's split the difference and let the HTTP and HTTPS sites exist side =
by side for all pages that contain public information.

> The datatracker, wikis, working group chairs pages, registration,
> mailing list management and tools sites all support authentication, I
> would find it completely unacceptable to pass my credentials  or
> activities I engaged in once authenticated in the clear.

There's more to life than HTTPS. Such as digest authentication, which is =
probably sufficient for most of the above.=

From henk.uijterwaal@gmail.com  Mon Aug 29 07:59:41 2011
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 717C621F8B3C for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:59:41 -0700 (PDT)
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.218,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A6S0TcBu2lP9 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 07:59:40 -0700 (PDT)
Received: from mail-ey0-f174.google.com (mail-ey0-f174.google.com [209.85.215.174]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA0C21F8B3A for <ietf@ietf.org>; Mon, 29 Aug 2011 07:59:40 -0700 (PDT)
Received: by eyx24 with SMTP id 24so4150088eyx.19 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:01:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mU+qHEfGnIpK31B48rdhnSAl1f5h9jKMhCugzBeb5XM=; b=gbZhOz3S3etNmGapPq/8qXPgHQYU9zqEDmdZZ4DW+n6GOhHfMzLpRYndDgJQLmCBpn hcugeo272gz3OcBvi56f3KounoqoZwq3S3R+BK1I/cH/TSoIU6eouFXBkGOTSirJFnxc l2diaEM0BtafSUHVSz4PHovC1NBFUZoErdQKQ=
Received: by 10.14.19.69 with SMTP id m45mr1511432eem.215.1314630064316; Mon, 29 Aug 2011 08:01:04 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) by mx.google.com with ESMTPS id b49sm771544eei.54.2011.08.29.08.01.02 (version=SSLv3 cipher=OTHER); Mon, 29 Aug 2011 08:01:03 -0700 (PDT)
Message-ID: <4E5BA9AD.7050908@gmail.com>
Date: Mon, 29 Aug 2011 17:01:01 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com>
In-Reply-To: <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 14:59:41 -0000

On 29/08/2011 16:51, Keith Moore wrote:
> 
> On Aug 29, 2011, at 10:40 AM, Iljitsch van Beijnum wrote:
> 
>> Obviously the date needs to be fixed at some point, but does it really have to
>> be six years in advance? ( http://www.ietf.org/meeting/upcoming.html )
> 
> I've been wondering the same thing.   Would it be reasonable to specify ballpark
> dates (say +/- 1 week) six years out as long as the actual dates were nailed
> down say three years out?

Discussions with the hotel starts only 2 years out, so fixing dates 3 years
out won't change a thing.   There is also the clash list, which limits the
weeks when we can have a meeting.

If we want more flexibility in order to find better hotel deals, then we have
to do something like: dates are fixed approximately 1.5 years out, and we do
not mind having meetings back-to-back with other organizations on the clash
list.  That means that some folks will have to travel around the globe between
Friday afternoon and Sunday morning in order to make it from one meeting to
another.

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From joelja@bogus.com  Mon Aug 29 08:00:20 2011
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6652821F8B8D for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level: 
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dc+zaHduWY4o for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:00:20 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 002A921F8B78 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:00:19 -0700 (PDT)
Received: from Zorch.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p7TF1f2x058928 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 29 Aug 2011 15:01:42 GMT (envelope-from joelja@bogus.com)
Message-ID: <4E5BA9D4.7020100@bogus.com>
Date: Mon, 29 Aug 2011 08:01:40 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com>
In-Reply-To: <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 29 Aug 2011 15:01:43 +0000 (UTC)
Cc: Cullen Jennings <fluffy@cisco.com>, henk@uijterwaal.nl, Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:00:20 -0000

On 8/29/11 07:51 , Keith Moore wrote:
> 
> On Aug 29, 2011, at 10:40 AM, Iljitsch van Beijnum wrote:
> 
>> Obviously the date needs to be fixed at some point, but does it really
>> have to be six years in advance?
>> ( http://www.ietf.org/meeting/upcoming.html )
> 
> I've been wondering the same thing.   Would it be reasonable to specify
> ballpark dates (say +/- 1 week) six years out as long as the actual
> dates were nailed down say three years out?

You can refer back to the ancient history. both on this list and in the
plenary minutes as to why the dates are fixes as far out as there are.

Suffience it to say that if you want to not conflict with other
networking and standards events you have publish your dates before they
publish theirs and number of people some of whom have contributed to
this thread stood at the microphone in more than one admin plenary and
asked for that.

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


From hsantos@santronics.com  Fri Aug 26 10:07:15 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C6F21F8B6B for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 10:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obkNWMlKfID0 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 10:07:14 -0700 (PDT)
Received: from secure.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id DE71921F8B53 for <ietf@ietf.org>; Fri, 26 Aug 2011 10:07:12 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5176; t=1314378501; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=JwA8+qc zNH+rLq2wxZf3wyTJRyI=; b=nt739H1nmVTzbYmneZJGCWeVNuUkYAXXheVaJKB cgJWzpKpafQRrA8c72on6E/sWrkoKTX4WRT6+yZ9vZKd5bKTTHfC4qSu7IdmIVZx TARgzSrYVS4y9q75d2APVV9u6LQcoRchp/KcD6qFHETQvEXjitN6w6Xw3HpAP+7C UA5Q=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 26 Aug 2011 13:08:21 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2833916647.38576.5400; Fri, 26 Aug 2011 13:07:34 -0400
Message-ID: <4E57D2D2.2030805@santronics.com>
Date: Fri, 26 Aug 2011 13:07:30 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Adam Novak <interfect@gmail.com>
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
In-Reply-To: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 17:07:15 -0000

This sounds like yet another repeated cyclic centralization to/from 
distribution viewpoint.  The more things change, the more it remains 
the same. Inevitably someone will get the bright idea to be more, to 
consolidate more and once again offer central/services for its 
surroundings and then at one point, we want to go distributed again 
once Apple is able to stick an iPAD in your brain!  He also seem to 
mix in the commercial interest has being a conflict and incorrectly 
stated Fidonet prohibited it.  Well, it was because of the commercial 
conflict with the FTSC (Fidonet Technical Standard Committee) to take 
over the nodelist (akin to DNS) and begin charging membership fees 
that got it disbanded in a vote at the next to last FidoCon Meeting 
(1994) - the last one was empty so I heard.  Very few choice in free 
software in Fidonet and clearly the commercial better supported 
Fidonet mailers were dominant. I don't even recall the original 
inventor and fidonet mailer was free, no it wasn't he wrote it under 
contract to connect two company division computers with a simple 
XMODEM-based protocol 24x7 data exchange mailer.

Adam Novak wrote:
> I trust that some of you have seen this article from a while back:
> 
> <http://moblog.wiredwings.com/archives/20110315/How-We-Killed-The-Internet-And-Nobody-Noticed.html>
> 
> An informative except:
> 
> "When I open my laptop, I see over ten different wifi access points.
> Say I wanted to send data to my friend in the flat next to mine. It is
> idiotic that nowadays, I would use the bottleneck subscriber line to
> my upstream ISP and my crippled upload speed and push it all the way
> across their infrastructure to my neighbors ISP and back to the Wifi
> router in reach of mine. The Internet is not meant to be used that
> way. Instead, all these wifi networks should be configured to talk to
> each other."
> 
> I also trust that you are aware of what happened to the Internet in
> Egypt (and elsewhere) this spring, where Internet connectivity was
> disrupted by shutting down major ISP networks.
> 
> I would like to bring the attention of the IETF to what I see as a
> fundamental problem with the current architecture of the Internet:
> 
> The Internet is not a network.
> 
> As part of the development of the Internet, fault-tolerant routing
> protocols have been developed that allow a connecdestined fortion to
> be maintained, even if the link that was carrying goes down, by
> routing packets around the problem. Similarly, packets can be
> load-balanced over multiple links for increased bandwidth. However,
> the benefits of these technologies are not available to end users. If
> I have a smartphone with both a 3G and a Wi-Fi connection, downloads
> cannot currently be load-balanced across them. The two interfaces are
> on two different networks, which are almost certainly part of two
> different autonomous systems. Packets must be addressed to one of the
> two interfaces, not the device, and packets addressed to one interface
> have no way to be routed to the other. Similar problems arise when a
> laptop has both a wired and a wireless connection. Wired networks also
> suffer from related difficulties: If I have Verizon and my friend has
> Comcast, and we string an Ethernet cable between our houses, packets
> for me will still all come down my connection, and packets for my
> friend will still all come down theirs.
> 
> The Internet, as it currently appears to end-users, has a logical tree
> topology: computers connect to your home router, which connects to
> your ISP, which connects to the rest of the Internet. Cell phones
> connect to the tower, which connects through a backhaul link to the
> rest of the Internet. Almost all of the devices involved have multiple
> physical interfaces and full IP routing implementations, but only the
> default route is ever used. This results in a brittle Internet: the
> failure of one ISP router can disconnect a large number of end-users
> from the Internet, as well as interrupting communication between those
> users, even when those users are, physically, only a few feet from
> each other.
> 
> My question is this: what IETF work would be needed to add more
> routing to the edges of the Internet? If each home or mobile device
> was essentially it's own autonomous system, what would this do to
> routing table size? To ASN space utilization? How can individuals
> interconnect home networks when RIRs do not assign address and AS
> number resources to individuals? How might individuals interconnect
> home networks without manual routing configuration? Under what
> circumstances could an ISP trust a client's claim to have a route to
> another client or to another ISP? How might packets sent to a device's
> address on one network be routed to that device's address on another
> network, while packets to immediately adjacent addresses take the
> normal path?
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Sincerely

Hector Santos
http://www.santronics.com




From hsantos@santronics.com  Fri Aug 26 11:13:03 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA79521F8C09 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBYN9jMbhk05 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:13:03 -0700 (PDT)
Received: from news.winserver.com (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BB31021F8BF9 for <ietf@ietf.org>; Fri, 26 Aug 2011 11:13:02 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=931; t=1314382458; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=0d6PX+Z 6japOA2EbwTmrVcmt7Yk=; b=WKWAG1CLD7dkvLdKd3l2ajB3Sd2yIR5jJdewq4Z yZhKvD87ap4Q9+CpoCV/DMLvOjgX/3+30AWhGjWdMkHA7LMm+TRs19hvtle8Zmqo acO0Nd0NoiHttl1cQt3hKW7aKsIzbWIYGaeQeC/QhKM7qAl6ulslHItVRUM5CD2L xcE8=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 26 Aug 2011 14:14:18 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2837861039.38697.2720; Fri, 26 Aug 2011 14:13:19 -0400
Message-ID: <4E57E23A.5070605@santronics.com>
Date: Fri, 26 Aug 2011 14:13:14 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Adam Novak <interfect@gmail.com>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>	<005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>	<CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>	<8F38C2201545EEF1F78C65E8@PST.JCK.COM>	<01O5AUN0VTQY00VHKR@mauve.mrochek.com> <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>
In-Reply-To: <CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 18:13:03 -0000

Adam Novak wrote:

> Once the certificate expiration business is fixed, it should be fairly
> simple to make sure it's kept up to date so that this sort of thing
> doesn't happen again.

Makes you wonder. Why is the concept of expiration required?  Did the 
IETF expire, die?  Did its value as an Organization go down and only 
valid on a year to year basis?

It just seem so arbitrary for one to certify another and say to the 
world come X day, you are no longer the same trusted entity when what 
he is really saying "He didn't pay me like he suppose to every yet" 
Does that imply the IETF is now downgraded, in debt and can not be 
trusted?

All rhetorical questions. After all, they did "Invent" it. It should 
be free to the IETF. :)

Just consider there are some in the DKIM arena who wanted for the x= 
expiration tag to be deprecated and removed.


-- 
Sincerely

Hector Santos
http://www.santronics.com




From hsantos@santronics.com  Fri Aug 26 11:49:14 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46C6721F8BEE for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REQZCEcWMtCr for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 11:49:13 -0700 (PDT)
Received: from news.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACD421F8BD8 for <ietf@ietf.org>; Fri, 26 Aug 2011 11:49:13 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1488; t=1314384621; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=7hC1g17 BzhSTwwoIbKnKqLQB8yY=; b=CgNcGIjiJ4jsFl4zBF2XpspctDxv7BH97VxH5W/ /kx0A5UwB0rEQ01QhoGLtQg2FZIJi8uF6p7YKwhVKLqGsMuoYNjQOhpluoc24Tpy HJFSfyFTJT4bDRcOKxhIr5fNDLUaHAFnroFBxFQAag8A0CN823xuiwiznFzwDpZ1 Fov0=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 26 Aug 2011 14:50:21 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2840038891.38759.5912; Fri, 26 Aug 2011 14:49:36 -0400
Message-ID: <4E57EABD.7090708@santronics.com>
Date: Fri, 26 Aug 2011 14:49:33 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Adam Novak <interfect@gmail.com>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>	<005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>	<CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>	<8F38C2201545EEF1F78C65E8@PST.JCK.COM>	<01O5AUN0VTQY00VHKR@mauve.mrochek.com>	<CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>	<4E57E23A.5070605@santronics.com> <CADPp2fC6qOvZig34coQ95Nk_yEgsjKRH=NAyvZAEumEx4HxrBg@mail.gmail.com>
In-Reply-To: <CADPp2fC6qOvZig34coQ95Nk_yEgsjKRH=NAyvZAEumEx4HxrBg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:50 -0700
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 18:49:14 -0000

I see, so as long as its not revoked, if compromised, you are hosed 
until it expires.

I wonder if OCSP (Online Certificate Status Protocol) can help 
addresses this? Expired or not, it can still be revoked with dynamic 
checking as long as the browser as OCSP enabled.  So I guess its a 
matter of reporting the theft as soon as it is discovered.


Adam Novak wrote:
> On Fri, Aug 26, 2011 at 1:13 PM, Hector Santos <hsantos@santronics.com> wrote:
>> Makes you wonder. Why is the concept of expiration required? ï¿½Did the IETF
>> expire, die? ï¿½Did its value as an Organization go down and only valid on a
>> year to year basis?
> 
> As I understand it, expiration is supposed to solve the problem of
> someone getting their hands on your old certificates and impersonating
> you. In order to impersonate you, not only do they have to get into
> your system, they have to have done it in the last year or so.
> 
> It also keeps certificates for domains from outliving domain
> registrations for too long. If you don't have the domain when you go
> to renew the certificate, the CA shouldn't renew it.
> 
> I guess it also keeps revocation lists short. You only have to
> remember that a certain certificate was compromised until it expires,
> instead of forever.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Sincerely

Hector Santos
http://www.santronics.com




From ben@nostrum.com  Fri Aug 26 14:39:37 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A40AF21F8BA8; Fri, 26 Aug 2011 14:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NnpukAsWTpcO; Fri, 26 Aug 2011 14:39:36 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id AF93E21F8B98; Fri, 26 Aug 2011 14:39:36 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-187-75-59.tx.res.rr.com [76.187.75.59]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p7QLeplL059892 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 26 Aug 2011 16:40:53 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Followup on Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <EEBDA95D-FC72-4498-A9D1-D7F4E7596314@nostrum.com>
Date: Fri, 26 Aug 2011 16:40:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <12A87CC5-8141-45C0-BA40-025F8784B93A@nostrum.com>
References: <EEBDA95D-FC72-4498-A9D1-D7F4E7596314@nostrum.com>
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org
X-Mailer: Apple Mail (2.1244.3)
Received-SPF: pass (nostrum.com: 76.187.75.59 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 21:39:37 -0000

This is a followup on my previous gen-art reviews of =
draft-ietf-dime-ikev2-psk-diameter based on version 09. I realize that =
came out a couple of weeks ago, and this followup may be overtaken by =
events. I am sending it anyway on the off chance it's still meaningful.

This version partially addresses my concerns (below), in that it now =
specifies a default mechanism for PSK generation. If I understand =
correctly, use of this mechanism is completely optional. That is, the =
actual mechanism chosen is still a matter of out-of-band agreement =
between the HAAA and the IKEv2 peer. And if I read correctly, there is =
still no way for either to declare or negotiate what mechanism they plan =
to use.

I realize the draft assumes that this will be used in the context of a =
"protocol leveraging this diameter application", and that said protocol =
should specify the key derivation mechanism to be used. I interpret =
(perhaps incorrectly) to mean that a given IKEv2 peer and a given HAAA =
are expected to be implemented for a particular context, and that the =
authors do not expect an IKEv2 peer from one context to work with an =
HAAA from another. Furthermore, it appears to me that if 2 such =
mismatched peers tried to communicate, the only way they could determine =
they were incompatible would be through authentication failures due to a =
key mismatch. I'm not sure that's an appropriate assumption for an IETF =
proposed standard.

Ideally, I think things would be improved if the  included key =
derivation procedure was promoted to MUST implement, and a mechanism =
were added where the peers can declare or negotiate the intent to use =
some other procedure if they choose to do so. At the minimum, it would =
be good to have a way where two peers could detect a key derivation =
mismatch early in the process.


On Jun 17, 2011, at 5:10 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 wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-dime-ikev2-psk-diameter-08
> Reviewer: Ben Campbell
> Review Date: 2011-06-17
> IESG Telechat date: 2011-06-23
>=20
> Summary: This draft is almost ready for publication as a proposed =
standard. I still have a concern about the generation of the PSK.
>=20
> Major issues:
>=20
> In my initial Gen-ART review, I made the following comment: The draft =
says that the procedure that the HAAA follows to generate the PSK is out =
of scope. But doesn't the IKE2 initiator need to understand the =
procedure? If the procedure is not defined somewhere, how you achieve =
any degree of interoperability?
>=20
> The author responded that the PSK generation was in fact important for =
interoperability, but that the specific procedures have been =
intentionally left to other specifications. It is up to specifications =
that use this Diameter application to define the PSK generation =
mechanism. Further, the author indicated 2 3GPP2 specs that have done =
this.
>=20
> I am still concerned that this means that this specification cannot be =
implemented in an interoperable way without effectively profiling it. =
There is no apparent coordination on how such profiling may be done, and =
by whom. I think this is likely to result in implementation islands that =
can't talk to each other. I recognize that there is precedent for doing =
this, but I think it is something that should not be done without =
careful consideration, particularly in a standards track RFC. I leave it =
to the IESG to confirm whether it is appropriate in this circumstance.
>=20
> I further note that there is  no apparent way to negotiate or declare =
what PSK generation mechanism might be used, if an implementation =
supports more than one.
>=20
> Minor Issues: None
> Editorial Comments: None
>=20
>=20


From hsantos@santronics.com  Fri Aug 26 15:41:05 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B713521F8B27 for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 15:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[AWL=-0.742, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_15=0.6, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MyS-lRs1fsy for <ietf@ietfa.amsl.com>; Fri, 26 Aug 2011 15:41:05 -0700 (PDT)
Received: from ntbbs.santronics.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id AD41621F8B22 for <ietf@ietf.org>; Fri, 26 Aug 2011 15:41:04 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1497; t=1314398532; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=LGOGnWP aD1V3Zcq5lJHr+Jp/0Pg=; b=nXKSeYVB2GbChcwzff9hzwI4fzuueQQWwI1qwVq Me4S0aWkTkvk2UkdTCep61kzBKDy+5Idd5IHbE+eHNZGFTUWBVr/QayR07eKjDj8 kUrN0DJr2Qy62F0+45oDxCvEdwVc77OhNIkyFY6mRahLgYOwPiND7IJEiIbgMiwD X2Ew=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 26 Aug 2011 18:42:12 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2853957846.39005.484; Fri, 26 Aug 2011 18:41:36 -0400
Message-ID: <4E58211B.8020709@santronics.com>
Date: Fri, 26 Aug 2011 18:41:31 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: https
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<4E57B142.4020802@bogus.com> <4E58095D.2040509@dougbarton.us>
In-Reply-To: <4E58095D.2040509@dougbarton.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:50 -0700
Cc: webmaster@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 22:41:05 -0000

Try it with Chrome and it makes you feel like the world blew up, I 
suppose intentionally as a fail-safe for the user-sake.

Doug Barton wrote:
> Joel,
> 
> I don't know what "It doesn't" is supposed to mean, but visiting
> https://www.ietf.org/* today with firefox it is still reporting that the
> certificate expired yesterday.
> 
> Given the volume of discussion about the topic starting yesterday when
> the problem started one could easily make a case for "it's still broken"
> being a significant "issue."
> 
> cc'ing the address listed as "Report Website Errors" on the home page.
> 
> 
> Doug
> 
> 
> On 08/26/2011 07:44, Joel jaeggli wrote:
>> It doesn't...
>>
>> http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html
>>
>> On 8/26/11 00:18 , t.petch wrote:
>>> Why does the IETF website consider it necessary to use TLS to access the mailing
>>> list archives, when they all appeared without it, or any other security, in the
>>> first place?
>>>
>>> Besides all the usual hassle of TLS, today the certificate is reported by IE as
>>> expired, which sort of sums it up.
>>>
>>> Tom Petch
>>>
>>> _______________________________________________
>>> 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
> 
> 
> 

-- 
Sincerely

Hector Santos
http://www.santronics.com




From simon.mizikovsky@alcatel-lucent.com  Fri Aug 26 16:22:57 2011
Return-Path: <simon.mizikovsky@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C770421F8B2F; Fri, 26 Aug 2011 16:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.36
X-Spam-Level: 
X-Spam-Status: No, score=-7.36 tagged_above=-999 required=5 tests=[AWL=-0.761,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 311+Mqb30dE6; Fri, 26 Aug 2011 16:22:56 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B795A21F8B2D; Fri, 26 Aug 2011 16:22:56 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id p7QNODuY016921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Aug 2011 18:24:13 -0500 (CDT)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p7QNO7re001163 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 26 Aug 2011 18:24:07 -0500
Received: from USNAVSXCHMBSA1.ndc.alcatel-lucent.com ([135.3.39.127]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Fri, 26 Aug 2011 18:24:07 -0500
From: "Mizikovsky, Semyon B (Simon)" <simon.mizikovsky@alcatel-lucent.com>
To: "'Ben Campbell'" <ben@nostrum.com>, "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>
Date: Fri, 26 Aug 2011 18:24:07 -0500
Subject: RE: Followup on Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08
Thread-Topic: Followup on Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08
Thread-Index: AcxkOO4ORyORMc0ESgy+sfNUOgLcowAC9NUg
Message-ID: <E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F20@USNAVSXCHMBSA1.ndc.alcatel-lucent.com>
References: <EEBDA95D-FC72-4498-A9D1-D7F4E7596314@nostrum.com> <12A87CC5-8141-45C0-BA40-025F8784B93A@nostrum.com>
In-Reply-To: <12A87CC5-8141-45C0-BA40-025F8784B93A@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 23:22:57 -0000

Ben, thank you for your comment.
We do not specify the protocol between IKEv2 Peer and HAAA. We specify the =
protocol between Diameter Client and Diameter Server. The Diameter Server h=
appens to be the HAAA. The Diameter Client happens to be the IKEv2 Server. =
The protocol we specify simply delivers the key material to the Diameter Cl=
ient. Nothing else. We also allow the HAAA the benefit of using the freshne=
ss elements that became available from the IKEv2 layer. But it is entirely =
up-to the HAAA how these elements, namely Ni and Nr, are used, although we =
provide the hint as a RECOMMENDATION.
Use of a MUST in the draft that does not specify the end-point affected by =
this MUST is entirely incorrect.=20
Now, allow me to examine your assumption that the Client and HAAA somehow m=
ay use different rules for choosing or creating the PSK:
The Client is surely known to the HAAA, otherwise we would have to assume t=
hat there is no prior relations between them (no shared secret) and therefo=
re the PSK scheme can't work by definition. For instance, this could happen=
 if the IKEv2 Server can not resolve the IDi reported by the IKEv2 Peer int=
o a correct User Identity, and therefore can not associate it with specific=
 proper Diameter Server. In such case, the default AAA will be accessed, an=
d due to the lack of a common shared secret a failure is the only possible =
result. Any attempt of negotiations will also fail.
On the other hand, if the IDi is resolvable, and the proper HAAA is located=
, than it is obvious that HAAA surely knows about this Client with proper s=
ubscription and has the shared key with it. It obviously knows also which P=
SK computation procedure is pre-configured in the Client, so no negotiation=
s are necessary either.
But my point is: all these procedures and assumptions are completely and to=
tally outside of scope of the draft which simply describes DELIVERY of the =
already computed PSK from the Diameter Server to the Diameter Client.
Yes, we specify the default PSK computation procedure in this draft on insi=
stence of reviewers. It is specified for those external applications which =
do not specify their own, so "here is the right way to do it". But it is en=
tirely up-to the external application how to use it, configure it, benefit =
from it, or even ignore it.
Simon.

=20
=20
=20
Semyon (Simon) MIZIKOVSKY
600 Mountain Avenue
ALCATEL-LUCENT
DIRECTOR
WIRELESS SECURITY STANDARDS
600/700 Mountain Ave., Rm. 3C-506
Murray Hill, NJ 07974-0636 USA
T:  +1 908 582 0729
M: +1 732 239 7533
F:  +1 908 743 4361
Simon.Mizikovsky@alcatel-lucent.com
=20
Note:  This message, and any attachments, is intended only for the recipien=
t(s) identified above.  The information contained in this message may be pr=
ivileged, confidential or proprietary, and its use or disclosure by other t=
han intended recipient(s) is prohibited and may be unlawful.  If you have r=
eceived this message in error, please delete it, and do not distribute or r=
etain a copy of it.
-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]=20
Sent: Friday, August 26, 2011 5:41 PM
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org
Cc: gen-art@ietf.org Review Team; The IETF
Subject: Followup on Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-d=
iameter-08

This is a followup on my previous gen-art reviews of draft-ietf-dime-ikev2-=
psk-diameter based on version 09. I realize that came out a couple of weeks=
 ago, and this followup may be overtaken by events. I am sending it anyway =
on the off chance it's still meaningful.

This version partially addresses my concerns (below), in that it now specif=
ies a default mechanism for PSK generation. If I understand correctly, use =
of this mechanism is completely optional. That is, the actual mechanism cho=
sen is still a matter of out-of-band agreement between the HAAA and the IKE=
v2 peer. And if I read correctly, there is still no way for either to decla=
re or negotiate what mechanism they plan to use.

I realize the draft assumes that this will be used in the context of a "pro=
tocol leveraging this diameter application", and that said protocol should =
specify the key derivation mechanism to be used. I interpret (perhaps incor=
rectly) to mean that a given IKEv2 peer and a given HAAA are expected to be=
 implemented for a particular context, and that the authors do not expect a=
n IKEv2 peer from one context to work with an HAAA from another. Furthermor=
e, it appears to me that if 2 such mismatched peers tried to communicate, t=
he only way they could determine they were incompatible would be through au=
thentication failures due to a key mismatch. I'm not sure that's an appropr=
iate assumption for an IETF proposed standard.

Ideally, I think things would be improved if the  included key derivation p=
rocedure was promoted to MUST implement, and a mechanism were added where t=
he peers can declare or negotiate the intent to use some other procedure if=
 they choose to do so. At the minimum, it would be good to have a way where=
 two peers could detect a key derivation mismatch early in the process.


On Jun 17, 2011, at 5:10 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 wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-dime-ikev2-psk-diameter-08
> Reviewer: Ben Campbell
> Review Date: 2011-06-17
> IESG Telechat date: 2011-06-23
>=20
> Summary: This draft is almost ready for publication as a proposed standar=
d. I still have a concern about the generation of the PSK.
>=20
> Major issues:
>=20
> In my initial Gen-ART review, I made the following comment: The draft say=
s that the procedure that the HAAA follows to generate the PSK is out of sc=
ope. But doesn't the IKE2 initiator need to understand the procedure? If th=
e procedure is not defined somewhere, how you achieve any degree of interop=
erability?
>=20
> The author responded that the PSK generation was in fact important for in=
teroperability, but that the specific procedures have been intentionally le=
ft to other specifications. It is up to specifications that use this Diamet=
er application to define the PSK generation mechanism. Further, the author =
indicated 2 3GPP2 specs that have done this.
>=20
> I am still concerned that this means that this specification cannot be im=
plemented in an interoperable way without effectively profiling it. There i=
s no apparent coordination on how such profiling may be done, and by whom. =
I think this is likely to result in implementation islands that can't talk =
to each other. I recognize that there is precedent for doing this, but I th=
ink it is something that should not be done without careful consideration, =
particularly in a standards track RFC. I leave it to the IESG to confirm wh=
ether it is appropriate in this circumstance.
>=20
> I further note that there is  no apparent way to negotiate or declare wha=
t PSK generation mechanism might be used, if an implementation supports mor=
e than one.
>=20
> Minor Issues: None
> Editorial Comments: None
>=20
>=20


From ben@nostrum.com  Fri Aug 26 16:48:07 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E36C21F876F; Fri, 26 Aug 2011 16:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqozKcIFva8W; Fri, 26 Aug 2011 16:48:06 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 69C9B21F874E; Fri, 26 Aug 2011 16:48:06 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-187-75-59.tx.res.rr.com [76.187.75.59]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p7QNnKgP070740 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 26 Aug 2011 18:49:22 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Followup on Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F20@USNAVSXCHMBSA1.ndc.alcatel-lucent.com>
Date: Fri, 26 Aug 2011 18:49:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <94507CCD-66F3-42AB-9AAC-B2A2D084FE8B@nostrum.com>
References: <EEBDA95D-FC72-4498-A9D1-D7F4E7596314@nostrum.com> <12A87CC5-8141-45C0-BA40-025F8784B93A@nostrum.com> <E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F20@USNAVSXCHMBSA1.ndc.alcatel-lucent.com>
To: "Mizikovsky, Semyon B (Simon)" <simon.mizikovsky@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1244.3)
Received-SPF: pass (nostrum.com: 76.187.75.59 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2011 23:48:07 -0000

Hi, thanks for the response. Please keep in mind that my comments are no =
more binding than any other, so if everyone else is convinced I am =
wrong, that's okay :-)

Specific comments inline:

On Aug 26, 2011, at 6:24 PM, Mizikovsky, Semyon B (Simon) wrote:

> Ben, thank you for your comment.
> We do not specify the protocol between IKEv2 Peer and HAAA. We specify =
the protocol between Diameter Client and Diameter Server. The Diameter =
Server happens to be the HAAA. The Diameter Client happens to be the =
IKEv2 Server. The protocol we specify simply delivers the key material =
to the Diameter Client. Nothing else. We also allow the HAAA the benefit =
of using the freshness elements that became available from the IKEv2 =
layer. But it is entirely up-to the HAAA how these elements, namely Ni =
and Nr, are used, although we provide the hint as a RECOMMENDATION.

I would concur that, if this draft was being produced in conjunction =
with, or normatively references other drafts that describe the =
relationship between the IKEv2 peer and the HAAA, then it would make =
sense to defer this to them. But if you want an arbitrary IKEv2 peer to =
be able to interop with an arbitrary IKEv2 server/HAAA pair, then this =
sort of thing needs to be defined _somewhere_.

> Use of a MUST in the draft that does not specify the end-point =
affected by this MUST is entirely incorrect.=20

I recognize that this draft can't specify the IKEv2 peer behavior, so =
maybe it can't solve the problem by itself. Is it defined _normatively_ =
somewhere else?


> Now, allow me to examine your assumption that the Client and HAAA =
somehow may use different rules for choosing or creating the PSK:
> The Client is surely known to the HAAA, otherwise we would have to =
assume that there is no prior relations between them (no shared secret) =
and therefore the PSK scheme can't work by definition. For instance, =
this could happen if the IKEv2 Server can not resolve the IDi reported =
by the IKEv2 Peer into a correct User Identity, and therefore can not =
associate it with specific proper Diameter Server. In such case, the =
default AAA will be accessed, and due to the lack of a common shared =
secret a failure is the only possible result. Any attempt of =
negotiations will also fail.
> On the other hand, if the IDi is resolvable, and the proper HAAA is =
located, than it is obvious that HAAA surely knows about this Client =
with proper subscription and has the shared key with it. It obviously =
knows also which PSK computation procedure is pre-configured in the =
Client, so no negotiations are necessary either.
> But my point is: all these procedures and assumptions are completely =
and totally outside of scope of the draft which simply describes =
DELIVERY of the already computed PSK from the Diameter Server to the =
Diameter Client.

You are conflating administrative relationships with implementation =
relationships. If the IKEv2 client _implementation_ does not share a key =
generation mechanism with the HAAA, then no amount of prior =
relationships and configuration are going to make them work together. =
Basically, you get a high chance that an IKE client from Vendor A =
cannot, under any circumstances, interoperate with a peer that depends =
on an HAAA from Vendor B.


> Yes, we specify the default PSK computation procedure in this draft on =
insistence of reviewers. It is specified for those external applications =
which do not specify their own, so "here is the right way to do it". But =
it is entirely up-to the external application how to use it, configure =
it, benefit from it, or even ignore it.

Can you remind me again what you mean by "external application"? =46rom =
most of the draft, I assume the external application is "IKEv2-PSK". Are =
we talking about something along the lines of a 3GPP named interface, =
where implementations for that context would not be expected to work =
with implementations from some other context?


> Simon.
>=20



>=20
>=20
>=20
> Semyon (Simon) MIZIKOVSKY
> 600 Mountain Avenue
> ALCATEL-LUCENT
> DIRECTOR
> WIRELESS SECURITY STANDARDS
> 600/700 Mountain Ave., Rm. 3C-506
> Murray Hill, NJ 07974-0636 USA
> T:  +1 908 582 0729
> M: +1 732 239 7533
> F:  +1 908 743 4361
> Simon.Mizikovsky@alcatel-lucent.com
>=20
> Note:  This message, and any attachments, is intended only for the =
recipient(s) identified above.  The information contained in this =
message may be privileged, confidential or proprietary, and its use or =
disclosure by other than intended recipient(s) is prohibited and may be =
unlawful.  If you have received this message in error, please delete it, =
and do not distribute or retain a copy of it.
> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]=20
> Sent: Friday, August 26, 2011 5:41 PM
> To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org
> Cc: gen-art@ietf.org Review Team; The IETF
> Subject: Followup on Gen-ART Telechat Review of =
draft-ietf-dime-ikev2-psk-diameter-08
>=20
> This is a followup on my previous gen-art reviews of =
draft-ietf-dime-ikev2-psk-diameter based on version 09. I realize that =
came out a couple of weeks ago, and this followup may be overtaken by =
events. I am sending it anyway on the off chance it's still meaningful.
>=20
> This version partially addresses my concerns (below), in that it now =
specifies a default mechanism for PSK generation. If I understand =
correctly, use of this mechanism is completely optional. That is, the =
actual mechanism chosen is still a matter of out-of-band agreement =
between the HAAA and the IKEv2 peer. And if I read correctly, there is =
still no way for either to declare or negotiate what mechanism they plan =
to use.
>=20
> I realize the draft assumes that this will be used in the context of a =
"protocol leveraging this diameter application", and that said protocol =
should specify the key derivation mechanism to be used. I interpret =
(perhaps incorrectly) to mean that a given IKEv2 peer and a given HAAA =
are expected to be implemented for a particular context, and that the =
authors do not expect an IKEv2 peer from one context to work with an =
HAAA from another. Furthermore, it appears to me that if 2 such =
mismatched peers tried to communicate, the only way they could determine =
they were incompatible would be through authentication failures due to a =
key mismatch. I'm not sure that's an appropriate assumption for an IETF =
proposed standard.
>=20
> Ideally, I think things would be improved if the  included key =
derivation procedure was promoted to MUST implement, and a mechanism =
were added where the peers can declare or negotiate the intent to use =
some other procedure if they choose to do so. At the minimum, it would =
be good to have a way where two peers could detect a key derivation =
mismatch early in the process.
>=20
>=20
> On Jun 17, 2011, at 5:10 PM, Ben Campbell wrote:
>=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 wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>>=20
>> Document: draft-ietf-dime-ikev2-psk-diameter-08
>> Reviewer: Ben Campbell
>> Review Date: 2011-06-17
>> IESG Telechat date: 2011-06-23
>>=20
>> Summary: This draft is almost ready for publication as a proposed =
standard. I still have a concern about the generation of the PSK.
>>=20
>> Major issues:
>>=20
>> In my initial Gen-ART review, I made the following comment: The draft =
says that the procedure that the HAAA follows to generate the PSK is out =
of scope. But doesn't the IKE2 initiator need to understand the =
procedure? If the procedure is not defined somewhere, how you achieve =
any degree of interoperability?
>>=20
>> The author responded that the PSK generation was in fact important =
for interoperability, but that the specific procedures have been =
intentionally left to other specifications. It is up to specifications =
that use this Diameter application to define the PSK generation =
mechanism. Further, the author indicated 2 3GPP2 specs that have done =
this.
>>=20
>> I am still concerned that this means that this specification cannot =
be implemented in an interoperable way without effectively profiling it. =
There is no apparent coordination on how such profiling may be done, and =
by whom. I think this is likely to result in implementation islands that =
can't talk to each other. I recognize that there is precedent for doing =
this, but I think it is something that should not be done without =
careful consideration, particularly in a standards track RFC. I leave it =
to the IESG to confirm whether it is appropriate in this circumstance.
>>=20
>> I further note that there is  no apparent way to negotiate or declare =
what PSK generation mechanism might be used, if an implementation =
supports more than one.
>>=20
>> Minor Issues: None
>> Editorial Comments: None
>>=20
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From simon.mizikovsky@alcatel-lucent.com  Fri Aug 26 18:29:46 2011
Return-Path: <simon.mizikovsky@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD4E521F859F; Fri, 26 Aug 2011 18:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.733
X-Spam-Level: 
X-Spam-Status: No, score=-6.733 tagged_above=-999 required=5 tests=[AWL=-1.135, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oj0FNn9WcZ2C; Fri, 26 Aug 2011 18:29:41 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id CA53C21F85A1; Fri, 26 Aug 2011 18:29:40 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p7R1UrPn002209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Aug 2011 20:30:54 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p7R1UlBk030490 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 26 Aug 2011 20:30:47 -0500
Received: from USNAVSXCHMBSA1.ndc.alcatel-lucent.com ([135.3.39.127]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Fri, 26 Aug 2011 20:30:47 -0500
From: "Mizikovsky, Semyon B (Simon)" <simon.mizikovsky@alcatel-lucent.com>
To: "'Ben Campbell'" <ben@nostrum.com>
Date: Fri, 26 Aug 2011 20:30:46 -0500
Subject: RE: [Gen-art] Followup on Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08
Thread-Topic: [Gen-art] Followup on Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08
Thread-Index: AcxkSsnrk4IUE9LTQeeDQL/zEJivKAAC2nug
Message-ID: <E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21@USNAVSXCHMBSA1.ndc.alcatel-lucent.com>
References: <EEBDA95D-FC72-4498-A9D1-D7F4E7596314@nostrum.com> <12A87CC5-8141-45C0-BA40-025F8784B93A@nostrum.com> <E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F20@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <94507CCD-66F3-42AB-9AAC-B2A2D084FE8B@nostrum.com>
In-Reply-To: <94507CCD-66F3-42AB-9AAC-B2A2D084FE8B@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/related; boundary="_004_E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21USNAVSXCHMBSA_"; type="multipart/alternative"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 01:29:46 -0000

--_004_E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21USNAVSXCHMBSA_
Content-Type: multipart/alternative;
	boundary="_000_E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21USNAVSXCHMBSA_"

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

Ben, please see in-line.
Simon


[cid:image001.jpg@01CC6437.6A2E4D60]

SEMYON (SIMON) MIZIKOVSKY
600 Mountain Avenue
ALCATEL-LUCENT
DIRECTOR
WIRELESS SECURITY STANDARDS
600/700 Mountain Ave., Rm. 3C-506
Murray Hill, NJ 07974-0636 USA
T:  +1 908 582 0729
M: +1 732 239 7533
F:  +1 908 743 4361
Simon.Mizikovsky@alcatel-lucent.com<mailto:Simon.Mizikovsky@alcatel-lucent.=
com>

Note:  This message, and any attachments, is intended only for the recipien=
t(s) identified above.  The information contained in this message may be pr=
ivileged, confidential or proprietary, and its use or disclosure by other t=
han intended recipient(s) is prohibited and may be unlawful.  If you have r=
eceived this message in error, please delete it, and do not distribute or r=
etain a copy of it.

________________________________
From: Ben Campbell [mailto:ben@nostrum.com]
Sent: Friday, August 26, 2011 7:49 PM
To: Mizikovsky, Semyon B (Simon)
Cc: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org; gen-art@ietf.org=
 Review Team; The IETF
Subject: Re: [Gen-art] Followup on Gen-ART Telechat Review of draft-ietf-di=
me-ikev2-psk-diameter-08


Hi, thanks for the response. Please keep in mind that my comments are no mo=
re binding than any other, so if everyone else is convinced I am wrong, tha=
t's okay :-)

Specific comments inline:

On Aug 26, 2011, at 6:24 PM, Mizikovsky, Semyon B (Simon) wrote:

> Ben, thank you for your comment.
> We do not specify the protocol between IKEv2 Peer and HAAA. We specify th=
e protocol between Diameter Client and Diameter Server. The Diameter Server=
 happens to be the HAAA. The Diameter Client happens to be the IKEv2 Server=
. The protocol we specify simply delivers the key material to the Diameter =
Client. Nothing else. We also allow the HAAA the benefit of using the fresh=
ness elements that became available from the IKEv2 layer. But it is entirel=
y up-to the HAAA how these elements, namely Ni and Nr, are used, although w=
e provide the hint as a RECOMMENDATION.

I would concur that, if this draft was being produced in conjunction with, =
or normatively references other drafts that describe the relationship betwe=
en the IKEv2 peer and the HAAA, then it would make sense to defer this to t=
hem. But if you want an arbitrary IKEv2 peer to be able to interop with an =
arbitrary IKEv2 server/HAAA pair, then this sort of thing needs to be defin=
ed _somewhere_.

[SBM] Ben, assumption of our draft is that the pair is IKEv2 Peer and HAAA.=
 The IKEv2 Server is a contacted intermediary. The IKEv2 Peer and IKEv2 Ser=
ver in our assumption very rarely have relations. The Server is discovered =
and contacted for resources. The HAAA should have business relations with H=
AAA for at least accepting and trusting Authorization, but subscription-bas=
ed relationship is still between the IKEv2 Peer and HAAA.

> Use of a MUST in the draft that does not specify the end-point affected b=
y this MUST is entirely incorrect.

I recognize that this draft can't specify the IKEv2 peer behavior, so maybe=
 it can't solve the problem by itself. Is it defined _normatively_ somewher=
e else?


> Now, allow me to examine your assumption that the Client and HAAA somehow=
 may use different rules for choosing or creating the PSK:
> The Client is surely known to the HAAA, otherwise we would have to assume=
 that there is no prior relations between them (no shared secret) and there=
fore the PSK scheme can't work by definition. For instance, this could happ=
en if the IKEv2 Server can not resolve the IDi reported by the IKEv2 Peer i=
nto a correct User Identity, and therefore can not associate it with specif=
ic proper Diameter Server. In such case, the default AAA will be accessed, =
and due to the lack of a common shared secret a failure is the only possibl=
e result. Any attempt of negotiations will also fail.
> On the other hand, if the IDi is resolvable, and the proper HAAA is locat=
ed, than it is obvious that HAAA surely knows about this Client with proper=
 subscription and has the shared key with it. It obviously knows also which=
 PSK computation procedure is pre-configured in the Client, so no negotiati=
ons are necessary either.
> But my point is: all these procedures and assumptions are completely and =
totally outside of scope of the draft which simply describes DELIVERY of th=
e already computed PSK from the Diameter Server to the Diameter Client.

You are conflating administrative relationships with implementation relatio=
nships. If the IKEv2 client _implementation_ does not share a key generatio=
n mechanism with the HAAA, then no amount of prior relationships and config=
uration are going to make them work together. Basically, you get a high cha=
nce that an IKE client from Vendor A cannot, under any circumstances, inter=
operate with a peer that depends on an HAAA from Vendor B.

[SBM] Allow me to disagree. Case in point is the subscription relations bet=
ween mobile-based credentials and authentication functions and the HSS-base=
d same. The authentication cryptographic functions (Comp128, Milenage, Sha1=
, etc.) are agreed to between the UICC/USIM/SIM/UIM placed in the mobile, a=
nd the HLR/HSS. One operator may use Comp128, another - Milenage, etc., and=
 it would still be irrelevant because in any case the USIM will provide the=
 session-specific computed CK/IK or Kasme, and the same will be provided by=
 the HSS. Similar solution is in 3GPP2 MIPv6 standard, where the MN-HA is c=
omputed from the EMSK derived from the prior EAP authentication. In other w=
ords, derivation of the IKEv2 PSK is done by EXTERNAL APPLICATION which has=
 nothing to do with either IKEv2 or Diameter. The resulting computed key is=
 PROVIDED to the IKEv2 application. This is what RFC5996 expects, and this =
is what we specify in this draft, for the Diameter side.

Why don't we specify it for the client side too? Because the reference poin=
t on the client side is not defined. The IKEv2 Peer and external client whi=
ch supplies the PSK to it are likely co-located, and not externally standar=
dized. While the IKEv2 Server and HAAA are very likely dislocated and the r=
eference point between them uses Diameter protocol to communicate. We focus=
 on this reference point.

> Yes, we specify the default PSK computation procedure in this draft on in=
sistence of reviewers. It is specified for those external applications whic=
h do not specify their own, so "here is the right way to do it". But it is =
entirely up-to the external application how to use it, configure it, benefi=
t from it, or even ignore it.

Can you remind me again what you mean by "external application"? From most =
of the draft, I assume the external application is "IKEv2-PSK". Are we talk=
ing about something along the lines of a 3GPP named interface, where implem=
entations for that context would not be expected to work with implementatio=
ns from some other context?

[SBM] No, this is not correct. The external application has nothing to do w=
ith IKEv2. It supplies the key material. How it obtains it - is outside the=
 scope of this draft. We provide one default example of how to obtain it. T=
he key material is supplied to the IKEv2-PSK application as the PSK expecte=
d according to the RFC5996. We hope to make it clear in the draft. If you t=
hink we need to clarify it more, please let us know which wording causes co=
nfusion.

Thank you very much again for spending your Friday evening thinking of us :=
)

Simon



> Simon.
>



>
>
>
> Semyon (Simon) MIZIKOVSKY
> 600 Mountain Avenue
> ALCATEL-LUCENT
> DIRECTOR
> WIRELESS SECURITY STANDARDS
> 600/700 Mountain Ave., Rm. 3C-506
> Murray Hill, NJ 07974-0636 USA
> T:  +1 908 582 0729
> M: +1 732 239 7533
> F:  +1 908 743 4361
> Simon.Mizikovsky@alcatel-lucent.com
>
> Note:  This message, and any attachments, is intended only for the recipi=
ent(s) identified above.  The information contained in this message may be =
privileged, confidential or proprietary, and its use or disclosure by other=
 than intended recipient(s) is prohibited and may be unlawful.  If you have=
 received this message in error, please delete it, and do not distribute or=
 retain a copy of it.
> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Friday, August 26, 2011 5:41 PM
> To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org
> Cc: gen-art@ietf.org Review Team; The IETF
> Subject: Followup on Gen-ART Telechat Review of
> draft-ietf-dime-ikev2-psk-diameter-08
>
> This is a followup on my previous gen-art reviews of draft-ietf-dime-ikev=
2-psk-diameter based on version 09. I realize that came out a couple of wee=
ks ago, and this followup may be overtaken by events. I am sending it anywa=
y on the off chance it's still meaningful.
>
> This version partially addresses my concerns (below), in that it now spec=
ifies a default mechanism for PSK generation. If I understand correctly, us=
e of this mechanism is completely optional. That is, the actual mechanism c=
hosen is still a matter of out-of-band agreement between the HAAA and the I=
KEv2 peer. And if I read correctly, there is still no way for either to dec=
lare or negotiate what mechanism they plan to use.
>
> I realize the draft assumes that this will be used in the context of a "p=
rotocol leveraging this diameter application", and that said protocol shoul=
d specify the key derivation mechanism to be used. I interpret (perhaps inc=
orrectly) to mean that a given IKEv2 peer and a given HAAA are expected to =
be implemented for a particular context, and that the authors do not expect=
 an IKEv2 peer from one context to work with an HAAA from another. Furtherm=
ore, it appears to me that if 2 such mismatched peers tried to communicate,=
 the only way they could determine they were incompatible would be through =
authentication failures due to a key mismatch. I'm not sure that's an appro=
priate assumption for an IETF proposed standard.
>
> Ideally, I think things would be improved if the  included key derivation=
 procedure was promoted to MUST implement, and a mechanism were added where=
 the peers can declare or negotiate the intent to use some other procedure =
if they choose to do so. At the minimum, it would be good to have a way whe=
re two peers could detect a key derivation mismatch early in the process.
>
>
> On Jun 17, 2011, at 5:10 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 wait for direction from your document shepherd or AD before
>> posting a new version of the draft.
>>
>> Document: draft-ietf-dime-ikev2-psk-diameter-08
>> Reviewer: Ben Campbell
>> Review Date: 2011-06-17
>> IESG Telechat date: 2011-06-23
>>
>> Summary: This draft is almost ready for publication as a proposed standa=
rd. I still have a concern about the generation of the PSK.
>>
>> Major issues:
>>
>> In my initial Gen-ART review, I made the following comment: The draft sa=
ys that the procedure that the HAAA follows to generate the PSK is out of s=
cope. But doesn't the IKE2 initiator need to understand the procedure? If t=
he procedure is not defined somewhere, how you achieve any degree of intero=
perability?
>>
>> The author responded that the PSK generation was in fact important for i=
nteroperability, but that the specific procedures have been intentionally l=
eft to other specifications. It is up to specifications that use this Diame=
ter application to define the PSK generation mechanism. Further, the author=
 indicated 2 3GPP2 specs that have done this.
>>
>> I am still concerned that this means that this specification cannot be i=
mplemented in an interoperable way without effectively profiling it. There =
is no apparent coordination on how such profiling may be done, and by whom.=
 I think this is likely to result in implementation islands that can't talk=
 to each other. I recognize that there is precedent for doing this, but I t=
hink it is something that should not be done without careful consideration,=
 particularly in a standards track RFC. I leave it to the IESG to confirm w=
hether it is appropriate in this circumstance.
>>
>> I further note that there is  no apparent way to negotiate or declare wh=
at PSK generation mechanism might be used, if an implementation supports mo=
re than one.
>>
>> Minor Issues: None
>> Editorial Comments: None
>>
>>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

--_000_E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21USNAVSXCHMBSA_
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"place"=
/>
<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"PostalCode"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"Street"/>
<o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"address"/>
<!--[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:PMingLiU;
	panose-1:2 1 6 1 0 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"FuturaA Bk BT";
	panose-1:2 11 5 2 2 2 4 2 3 3;}
@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;}
@font-face
	{font-family:"\@PMingLiU";
	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";}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:.55in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l7 level1 lfo10;
	border:none;
	padding:0in;
	font-size:18.0pt;
	font-family:Arial;
	font-weight:normal;}
h2
	{margin-top:9.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:.65in;
	text-indent:-.4in;
	page-break-after:avoid;
	mso-list:l7 level2 lfo10;
	font-size:16.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:.65in;
	text-indent:-.4in;
	page-break-after:avoid;
	mso-list:l7 level2 lfo10;
	font-size:14.0pt;
	font-family:Arial;
	font-weight:normal;}
h4
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:70.9pt;
	text-indent:-70.9pt;
	page-break-after:avoid;
	mso-list:l7 level2 lfo10;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h5
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:85.05pt;
	text-indent:-85.05pt;
	page-break-after:avoid;
	mso-list:l7 level2 lfo10;
	font-size:11.0pt;
	font-family:Arial;
	font-weight:normal;}
h6
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:99.25pt;
	text-indent:-99.25pt;
	page-break-after:avoid;
	mso-list:l7 level2 lfo10;
	font-size:10.0pt;
	font-family:Arial;
	font-weight:normal;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:99.25pt;
	text-indent:-99.25pt;
	page-break-after:avoid;
	mso-list:l7 level2 lfo10;
	font-size:10.0pt;
	font-family:Arial;}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:0in;
	text-indent:0in;
	page-break-after:avoid;
	mso-list:l7 level1 lfo10;
	border:none;
	padding:0in;
	font-size:18.0pt;
	font-family:Arial;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:0in;
	text-indent:0in;
	page-break-after:avoid;
	mso-list:l7 level1 lfo10;
	border:none;
	padding:0in;
	font-size:18.0pt;
	font-family:Arial;}
p.MsoIndex1, li.MsoIndex1, div.MsoIndex1
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoIndex2, li.MsoIndex2, div.MsoIndex2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:14.2pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoToc1, li.MsoToc1, div.MsoToc1
	{margin-top:6.0pt;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:28.35pt;
	margin-bottom:.0001pt;
	text-indent:-28.35pt;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:"Times New Roman";}
p.MsoToc2, li.MsoToc2, div.MsoToc2
	{margin-top:0in;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:42.55pt;
	margin-bottom:.0001pt;
	text-indent:-42.55pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc3, li.MsoToc3, div.MsoToc3
	{margin-top:0in;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:56.7pt;
	margin-bottom:.0001pt;
	text-indent:-56.7pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc4, li.MsoToc4, div.MsoToc4
	{margin-top:0in;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:70.9pt;
	margin-bottom:.0001pt;
	text-indent:-70.9pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc5, li.MsoToc5, div.MsoToc5
	{margin-top:0in;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:85.05pt;
	margin-bottom:.0001pt;
	text-indent:-85.05pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc6, li.MsoToc6, div.MsoToc6
	{margin-top:0in;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:99.25pt;
	margin-bottom:.0001pt;
	text-indent:-99.25pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc7, li.MsoToc7, div.MsoToc7
	{margin-top:0in;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:113.4pt;
	margin-bottom:.0001pt;
	text-indent:-113.4pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoToc8, li.MsoToc8, div.MsoToc8
	{margin-top:9.0pt;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:134.65pt;
	margin-bottom:.0001pt;
	text-indent:-134.65pt;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
p.MsoToc9, li.MsoToc9, div.MsoToc9
	{margin-top:9.0pt;
	margin-right:21.25pt;
	margin-bottom:0in;
	margin-left:70.9pt;
	margin-bottom:.0001pt;
	text-indent:-70.9pt;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:22.7pt;
	margin-bottom:.0001pt;
	text-indent:-22.7pt;
	font-size:8.0pt;
	font-family:"Times New Roman";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;
	font-weight:bold;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:9.0pt;
	font-family:Arial;
	font-weight:bold;
	font-style:italic;}
p.MsoIndexHeading, li.MsoIndexHeading, div.MsoIndexHeading
	{margin-top:.25in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:0in;
	border:none;
	padding:0in;
	font-size:13.0pt;
	font-family:"Times New Roman";
	font-weight:bold;
	font-style:italic;}
p.MsoCaption, li.MsoCaption, div.MsoCaption
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
span.MsoFootnoteReference
	{position:relative;
	top:-3.0pt;
	mso-text-raise:3.0pt;
	font-weight:bold;}
p.MsoList, li.MsoList, div.MsoList
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:28.4pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:28.4pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoListNumber, li.MsoListNumber, div.MsoListNumber
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:28.4pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoList2, li.MsoList2, div.MsoList2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:42.55pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoList3, li.MsoList3, div.MsoList3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoList4, li.MsoList4, div.MsoList4
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:70.9pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoList5, li.MsoList5, div.MsoList5
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:85.1pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoListBullet2, li.MsoListBullet2, div.MsoListBullet2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:42.55pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoListBullet3, li.MsoListBullet3, div.MsoListBullet3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoListBullet4, li.MsoListBullet4, div.MsoListBullet4
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:70.9pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoListBullet5, li.MsoListBullet5, div.MsoListBullet5
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:85.1pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoListNumber2, li.MsoListNumber2, div.MsoListNumber2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:42.55pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p.MsoDocumentMap, li.MsoDocumentMap, div.MsoDocumentMap
	{margin:0in;
	margin-bottom:.0001pt;
	background:navy;
	font-size:12.0pt;
	font-family:Tahoma;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p
	{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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
span.CharChar
	{font-family:Arial;}
p.11BodyText, li.11BodyText, div.11BodyText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:11.0pt;
	margin-left:64.9pt;
	punctuation-wrap:simple;
	text-autospace:none;
	font-size:11.0pt;
	font-family:Arial;
	color:black;}
span.11BodyTextChar
	{font-family:Arial;
	color:black;}
p.B1, li.B1, div.B1
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:28.4pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.B2, li.B2, div.B2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:42.55pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.B3, li.B3, div.B3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.B4, li.B4, div.B4
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:70.9pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.B5, li.B5, div.B5
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:85.1pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.CouvRecTitle, li.CouvRecTitle, div.CouvRecTitle
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:70.9pt;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:18.0pt;
	font-family:Arial;
	font-weight:bold;}
p.DefaultParagraphFontParaCharCharChar, li.DefaultParagraphFontParaCharChar=
Char, div.DefaultParagraphFontParaCharCharChar
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:8.0pt;
	margin-left:0in;
	line-height:12.0pt;
	font-size:12.0pt;
	font-family:Arial;}
p.NO, li.NO, div.NO
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-42.55pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.EditorsNote, li.EditorsNote, div.EditorsNote
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-42.55pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:red;}
span.EditorsNoteChar
	{color:red;}
span.EditorsNoteCharChar
	{color:red;}
p.enumlev2, li.enumlev2, div.enumlev2
	{margin-top:4.3pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:79.4pt;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-19.85pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.EQ, li.EQ, div.EQ
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.EX, li.EX, div.EX
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:85.1pt;
	margin-bottom:.0001pt;
	text-indent:-70.9pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.EW, li.EW, div.EW
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:85.1pt;
	margin-bottom:.0001pt;
	text-indent:-70.9pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.FigureTitle, li.FigureTitle, div.FigureTitle
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:24.0pt;
	margin-left:0in;
	text-align:center;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
p.FP, li.FP, div.FP
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.Guidance, li.Guidance, div.Guidance
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:blue;
	font-style:italic;}
p.H6, li.H6, div.H6
	{margin-top:6.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:99.25pt;
	text-indent:-99.25pt;
	page-break-after:avoid;
	mso-list:l7 level2 lfo10;
	font-size:10.0pt;
	font-family:Arial;}
span.Heading1CharChar
	{font-family:Arial;}
span.Heading2CharChar
	{font-family:Arial;}
span.Heading3CharChar
	{font-family:Arial;}
p.INDENT1, li.INDENT1, div.INDENT1
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:42.55pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.INDENT2, li.INDENT2, div.INDENT2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-14.2pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.INDENT3, li.INDENT3, div.INDENT3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:85.05pt;
	margin-bottom:.0001pt;
	text-indent:-28.35pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.LD, li.LD, div.LD
	{margin:0in;
	margin-bottom:.0001pt;
	line-height:9.0pt;
	page-break-after:avoid;
	font-size:10.0pt;
	font-family:"Courier New";}
p.NF, li.NF, div.NF
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-42.55pt;
	page-break-after:avoid;
	font-size:9.0pt;
	font-family:Arial;}
p.NW, li.NW, div.NW
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:56.75pt;
	margin-bottom:.0001pt;
	text-indent:-42.55pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.PL, li.PL, div.PL
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Courier New";}
p.RecCCITT, li.RecCCITT, div.RecCCITT
	{margin:0in;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
p.TAL, li.TAL, div.TAL
	{margin:0in;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:9.0pt;
	font-family:Arial;}
p.TAC, li.TAC, div.TAC
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	page-break-after:avoid;
	font-size:9.0pt;
	font-family:Arial;}
p.TAH, li.TAH, div.TAH
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	page-break-after:avoid;
	font-size:9.0pt;
	font-family:Arial;
	font-weight:bold;}
p.TH, li.TH, div.TH
	{margin-top:3.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	text-align:center;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
p.TAJ, li.TAJ, div.TAJ
	{margin-top:3.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	text-align:center;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
p.TAN, li.TAN, div.TAN
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:42.55pt;
	margin-bottom:.0001pt;
	text-indent:-42.55pt;
	page-break-after:avoid;
	font-size:9.0pt;
	font-family:Arial;}
p.TAR, li.TAR, div.TAR
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:right;
	page-break-after:avoid;
	font-size:9.0pt;
	font-family:Arial;}
p.TF, li.TF, div.TF
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:0in;
	text-align:center;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:bold;}
span.TF0
	{font-family:Arial;
	font-weight:bold;}
p.TT, li.TT, div.TT
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:9.0pt;
	margin-left:.55in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l7 level1 lfo10;
	border:none;
	padding:0in;
	font-size:18.0pt;
	font-family:Arial;}
p.ZA, li.ZA, div.ZA
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:right;
	border:none;
	padding:0in;
	mso-element:frame;
	font-size:20.0pt;
	font-family:Arial;}
p.ZB, li.ZB, div.ZB
	{margin-top:0in;
	margin-right:1.4pt;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	text-align:right;
	mso-element:frame;
	font-size:10.0pt;
	font-family:Arial;
	font-style:italic;}
p.ZD, li.ZD, div.ZD
	{margin:0in;
	margin-bottom:.0001pt;
	mso-element:frame;
	font-size:16.0pt;
	font-family:Arial;}
p.ZG, li.ZG, div.ZG
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:right;
	mso-element:frame;
	font-size:10.0pt;
	font-family:Arial;}
p.ZH, li.ZH, div.ZH
	{margin:0in;
	margin-bottom:.0001pt;
	mso-element:frame;
	font-size:10.0pt;
	font-family:Arial;}
p.ZT, li.ZT, div.ZT
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:right;
	mso-element:frame;
	font-size:17.0pt;
	font-family:Arial;
	font-weight:bold;}
p.ZTD, li.ZTD, div.ZTD
	{margin-top:0in;
	margin-right:1.4pt;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	text-align:right;
	mso-element:frame;
	font-size:20.0pt;
	font-family:Arial;}
p.ZU, li.ZU, div.ZU
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:right;
	border:none;
	padding:0in;
	mso-element:frame;
	font-size:10.0pt;
	font-family:Arial;}
p.ZV, li.ZV, div.ZV
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:right;
	border:none;
	padding:0in;
	mso-element:frame;
	font-size:10.0pt;
	font-family:Arial;}
span.EmailStyle106
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:-129;
	mso-list-type:simple;
	mso-list-template-ids:1280856010;}
@list l0:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:-128;
	mso-list-type:simple;
	mso-list-template-ids:-1815473752;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.25in;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2
	{mso-list-id:-127;
	mso-list-type:simple;
	mso-list-template-ids:1690969754;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l3
	{mso-list-id:-126;
	mso-list-type:simple;
	mso-list-template-ids:1832962776;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.75in;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l4
	{mso-list-id:-125;
	mso-list-type:simple;
	mso-list-template-ids:-168638942;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l5
	{mso-list-id:-120;
	mso-list-type:simple;
	mso-list-template-ids:-521472336;}
@list l5:level1
	{mso-level-tab-stop:.25in;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;}
@list l6
	{mso-list-id:-119;
	mso-list-type:simple;
	mso-list-template-ids:392711260;}
@list l6:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.25in;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l7
	{mso-list-id:1116025932;
	mso-list-template-ids:-423323362;}
@list l7:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.55in;
	mso-level-number-position:left;
	margin-left:.55in;
	text-indent:-.3in;}
@list l7:level2
	{mso-level-style-link:"Heading 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:.65in;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-.4in;}
@list l7:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.75in;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.5in;}
@list l7:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.85in;
	mso-level-number-position:left;
	margin-left:.85in;
	text-indent:-.6in;}
@list l7:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.95in;
	mso-level-number-position:left;
	margin-left:.95in;
	text-indent:-.7in;}
@list l7:level6
	{mso-level-text:"%5%1\.%2\.%3\.%4\.\.%6";
	mso-level-tab-stop:1.05in;
	mso-level-number-position:left;
	margin-left:1.05in;
	text-indent:-.8in;}
@list l7:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:1.15in;
	mso-level-number-position:left;
	margin-left:1.15in;
	text-indent:-.9in;}
@list l7:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.25in;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-1.0in;}
@list l7:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.35in;
	mso-level-number-position:left;
	margin-left:1.35in;
	text-indent:-1.1in;}
@list l8
	{mso-list-id:1762792831;
	mso-list-template-ids:-344151206;}
@list l8:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.55in;
	mso-level-number-position:left;
	margin-left:.55in;
	text-indent:-.3in;}
@list l8:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.65in;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-.4in;}
@list l8:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.75in;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.5in;}
@list l8:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.85in;
	mso-level-number-position:left;
	margin-left:.85in;
	text-indent:-.6in;}
@list l8:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.95in;
	mso-level-number-position:left;
	margin-left:.95in;
	text-indent:-.7in;}
@list l8:level6
	{mso-level-text:"%5%1\.%2\.%3\.%4\.\.%6";
	mso-level-tab-stop:1.05in;
	mso-level-number-position:left;
	margin-left:1.05in;
	text-indent:-.8in;}
@list l8:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:1.15in;
	mso-level-number-position:left;
	margin-left:1.15in;
	text-indent:-.9in;}
@list l8:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.25in;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-1.0in;}
@list l8:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.35in;
	mso-level-number-position:left;
	margin-left:1.35in;
	text-indent:-1.1in;}
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=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Ben, please see in-line.<o:p></o:p></s=
pan></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Simon<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3DTahoma><span style=
=3D'font-size:
12.0pt;font-family:Tahoma;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblue face=3D"Times New Roman"><=
span
lang=3DFR style=3D'font-size:12.0pt;color:blue'><img width=3D286 height=3D2=
7
id=3D"_x0000_i1026" src=3D"cid:image001.jpg@01CC6437.6A2E4D60"><o:p></o:p><=
/span></font></p>

<p class=3DMsoNormal><strong><b><font size=3D1 color=3Dblack face=3D"Futura=
A Bk BT"><span
style=3D'font-size:4.0pt;font-family:"FuturaA Bk BT";color:black'><o:p>&nbs=
p;</o:p></span></font></b></strong></p>

<p class=3DMsoNormal><strong><b><font size=3D2 color=3Dblack face=3D"Futura=
A Bk BT"><span
style=3D'font-size:10.0pt;font-family:"FuturaA Bk BT";color:black'>SEMYON (=
SIMON)
MIZIKOVSKY</span></font></b></strong><font color=3Dnavy><span style=3D'colo=
r:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address w:st=3D"on"><font=
 size=3D2
  color=3Dpurple face=3D"FuturaA Bk BT"><span style=3D'font-size:10.0pt;fon=
t-family:
  "FuturaA Bk BT";color:purple'>600 Mountain Avenue</span></font></st1:addr=
ess></st1:Street><font
size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><span style=3D'font-size:10.=
0pt;
font-family:"FuturaA Bk BT";color:purple'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><=
span
style=3D'font-size:10.0pt;font-family:"FuturaA Bk BT";color:purple'>ALCATEL=
-LUCENT<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><=
span
style=3D'font-size:10.0pt;font-family:"FuturaA Bk BT";color:purple'>DIRECTO=
R<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><=
span
style=3D'font-size:10.0pt;font-family:"FuturaA Bk BT";color:purple'>WIRELES=
S
SECURITY STANDARDS</span></font><font color=3Dnavy><span style=3D'color:nav=
y'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:Street w:st=3D"on"><st1:address w:st=3D"on"><font=
 size=3D2
  color=3Dpurple face=3D"FuturaA Bk BT"><span style=3D'font-size:10.0pt;fon=
t-family:
  "FuturaA Bk BT";color:purple'>600/700 Mountain Ave.</span></font></st1:ad=
dress></st1:Street><font
size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><span style=3D'font-size:10.=
0pt;
font-family:"FuturaA Bk BT";color:purple'>, Rm. 3C-506</span></font><font
color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:place w:st=3D"on"><st1:City w:st=3D"on"><font siz=
e=3D2
  color=3Dpurple face=3D"FuturaA Bk BT"><span style=3D'font-size:10.0pt;fon=
t-family:
  "FuturaA Bk BT";color:purple'>Murray Hill</span></font></st1:City><font
 size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><span style=3D'font-size:10=
.0pt;
 font-family:"FuturaA Bk BT";color:purple'>, <st1:State w:st=3D"on">NJ</st1=
:State>&nbsp;<st1:PostalCode
 w:st=3D"on">07974-0636</st1:PostalCode> <st1:country-region w:st=3D"on">US=
A</st1:country-region></span></font></st1:place><font
size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><span style=3D'font-size:10.=
0pt;
font-family:"FuturaA Bk BT";color:purple'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><=
span
style=3D'font-size:10.0pt;font-family:"FuturaA Bk BT";color:purple'>T:&nbsp=
; +1
908 582 0729</span></font><font color=3Dnavy><span style=3D'color:navy'><o:=
p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><=
span
style=3D'font-size:10.0pt;font-family:"FuturaA Bk BT";color:purple'>M: +1 7=
32 239
7533</span></font><font color=3Dnavy><span style=3D'color:navy'><o:p></o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dpurple face=3D"FuturaA Bk BT"><=
span
style=3D'font-size:10.0pt;font-family:"FuturaA Bk BT";color:purple'>F:&nbsp=
;&nbsp;+1
908 743 4361<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dpurple face=3DArial><span style=
=3D'font-size:
12.0pt;font-family:Arial;color:purple'><a
href=3D"mailto:Simon.Mizikovsky@alcatel-lucent.com"><font size=3D2 color=3D=
purple
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma;color:purp=
le'>Simon.Mizikovsky@alcatel-lucent.com</span></font></a><o:p></o:p></span>=
</font></p>

<p><font size=3D2 color=3Dgray face=3D"Times New Roman"><span style=3D'font=
-size:10.0pt;
color:gray'>Note:&nbsp; This message, and any attachments, is intended only=
 for
the recipient(s) identified above.&nbsp; The information contained in this
message may be privileged, confidential or proprietary, and its use or
disclosure by other than intended recipient(s) is prohibited and may be
unlawful.&nbsp; If you have received this message in error, please delete i=
t,
and do not distribute or retain a copy of it.</span></font><font size=3D2
color=3Dgray><span style=3D'font-size:10.0pt;color:gray'><o:p></o:p></span>=
</font></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font siz=
e=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span style=3D'font-si=
ze:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Ben Camp=
bell
[mailto:ben@nostrum.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, August 26, 201=
1 7:49
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Mizikovsky, Semyon B (Si=
mon)<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> draft-ietf-dime-ikev2-ps=
k-diameter.all@tools.ietf.org;
gen-art@ietf.org Review Team; The IETF<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [Gen-art] Follo=
wup on
Gen-ART Telechat Review of draft-ietf-dime-ikev2-psk-diameter-08</span></fo=
nt><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p style=3D'margin-bottom:12.0pt'><font size=3D2 face=3D"Times New Roman"><=
span
style=3D'font-size:10.0pt'>Hi, thanks for the response. Please keep in mind=
 that
my comments are no more binding than any other, so if everyone else is
convinced I am wrong, that's okay :-)<br>
<br>
Specific comments inline:<br>
<br>
On Aug 26, 2011, at 6:24 PM, Mizikovsky, Semyon B (Simon) wrote:<br>
<br>
&gt; Ben, thank you for your comment.<br>
&gt; We do not specify the protocol between IKEv2 Peer and HAAA. We specify=
 the
protocol between Diameter Client and Diameter Server. The Diameter Server
happens to be the HAAA. The Diameter Client happens to be the IKEv2 Server.=
 The
protocol we specify simply delivers the key material to the Diameter Client=
.
Nothing else. We also allow the HAAA the benefit of using the freshness
elements that became available from the IKEv2 layer. But it is entirely up-=
to
the HAAA how these elements, namely Ni and Nr, are used, although we provid=
e
the hint as a RECOMMENDATION.<br>
<br>
I would concur that, if this draft was being produced in conjunction with, =
or
normatively references other drafts that describe the relationship between =
the
IKEv2 peer and the HAAA, then it would make sense to defer this to them. Bu=
t if
you want an arbitrary IKEv2 peer to be able to interop with an arbitrary IK=
Ev2
server/HAAA pair, then this sort of thing needs to be defined _somewhere_.<=
font
color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></font></span></f=
ont></p>

<p style=3D'margin-bottom:12.0pt'><b><i><font size=3D2 color=3Dnavy face=3D=
Arial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[SBM] Ben, assumption of our draft is that the pair is I=
KEv2
Peer and HAAA. The IKEv2 Server is a contacted intermediary. The IKEv2 Peer=
 and
IKEv2 Server in our assumption very rarely have relations. The Server is
discovered and contacted for resources. The HAAA should have business relat=
ions
with HAAA for at least accepting and trusting Authorization, but
subscription-based relationship is still between the IKEv2 Peer and HAAA.<o=
:p></o:p></span></font></i></b></p>

<p style=3D'margin-bottom:12.0pt'><font size=3D2 face=3D"Times New Roman"><=
span
style=3D'font-size:10.0pt'><br>
&gt; Use of a MUST in the draft that does not specify the end-point affecte=
d by
this MUST is entirely incorrect.<br>
<br>
I recognize that this draft can't specify the IKEv2 peer behavior, so maybe=
 it
can't solve the problem by itself. Is it defined _normatively_ somewhere el=
se?<br>
<br>
<br>
&gt; Now, allow me to examine your assumption that the Client and HAAA some=
how
may use different rules for choosing or creating the PSK:<br>
&gt; The Client is surely known to the HAAA, otherwise we would have to ass=
ume
that there is no prior relations between them (no shared secret) and theref=
ore
the PSK scheme can't work by definition. For instance, this could happen if=
 the
IKEv2 Server can not resolve the IDi reported by the IKEv2 Peer into a corr=
ect
User Identity, and therefore can not associate it with specific proper Diam=
eter
Server. In such case, the default AAA will be accessed, and due to the lack=
 of
a common shared secret a failure is the only possible result. Any attempt o=
f
negotiations will also fail.<br>
&gt; On the other hand, if the IDi is resolvable, and the proper HAAA is
located, than it is obvious that HAAA surely knows about this Client with
proper subscription and has the shared key with it. It obviously knows also
which PSK computation procedure is pre-configured in the Client, so no
negotiations are necessary either.<br>
&gt; But my point is: all these procedures and assumptions are completely a=
nd
totally outside of scope of the draft which simply describes DELIVERY of th=
e
already computed PSK from the Diameter Server to the Diameter Client.<br>
<br>
You are conflating administrative relationships with implementation
relationships. If the IKEv2 client _implementation_ does not share a key
generation mechanism with the HAAA, then no amount of prior relationships a=
nd
configuration are going to make them work together. Basically, you get a hi=
gh
chance that an IKE client from Vendor A cannot, under any circumstances,
interoperate with a peer that depends on an HAAA from Vendor B.<font
color=3Dnavy><span style=3D'color:navy'><o:p></o:p></span></font></span></f=
ont></p>

<p style=3D'margin-bottom:12.0pt'><b><i><font size=3D2 color=3Dnavy face=3D=
Arial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[SBM] Allow me to disagree. Case in point is the
subscription relations between mobile-based credentials and authentication
functions and the HSS-based same. The authentication cryptographic function=
s (Comp128,
Milenage, Sha1, etc.) are agreed to between the UICC/USIM/SIM/UIM placed in=
 the
mobile, and the HLR/HSS. One operator may use Comp128, another &#8211;
Milenage, etc., and it would still be irrelevant because in any case the US=
IM
will provide the session-specific computed CK/IK or Kasme, and the same wil=
l be
provided by the HSS. Similar solution is in 3GPP2 MIPv6 standard, where the
MN-HA is computed from the EMSK derived from the prior EAP authentication. =
In
other words, derivation of the IKEv2 PSK is done by EXTERNAL APPLICATION wh=
ich
has nothing to do with either IKEv2 or Diameter. The resulting computed key=
 is
PROVIDED to the IKEv2 application. This is what RFC5996 expects, and this i=
s
what we specify in this draft, for the Diameter side. <o:p></o:p></span></f=
ont></i></b></p>

<p style=3D'margin-bottom:12.0pt'><b><i><font size=3D2 color=3Dnavy face=3D=
Arial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>Why don&#8217;t we specify it for the client side too? B=
ecause
the reference point on the client side is not defined. The IKEv2 Peer and
external client which supplies the PSK to it are likely co-located, and not
externally standardized. While the IKEv2 Server and HAAA are very likely
dislocated and the reference point between them uses Diameter protocol to
communicate. We focus on this reference point.</span></font></i></b><font
size=3D2><span style=3D'font-size:10.0pt'><br>
<br>
&gt; Yes, we specify the default PSK computation procedure in this draft on
insistence of reviewers. It is specified for those external applications wh=
ich
do not specify their own, so &quot;here is the right way to do it&quot;. Bu=
t it
is entirely up-to the external application how to use it, configure it, ben=
efit
from it, or even ignore it.<br>
<br>
Can you remind me again what you mean by &quot;external application&quot;? =
From
most of the draft, I assume the external application is &quot;IKEv2-PSK&quo=
t;.
Are we talking about something along the lines of a 3GPP named interface, w=
here
implementations for that context would not be expected to work with
implementations from some other context?<font color=3Dnavy><span
style=3D'color:navy'><o:p></o:p></span></font></span></font></p>

<p style=3D'margin-bottom:12.0pt'><b><i><font size=3D2 color=3Dnavy face=3D=
Arial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>[SBM] No, this is not correct. The external application =
has
nothing to do with IKEv2. It supplies the key material. How it obtains it &=
#8211;
is outside the scope of this draft. We provide one default example of how t=
o
obtain it. The key material is supplied to the IKEv2-PSK application as the=
 PSK
expected according to the RFC5996. We hope to make it clear in the draft. I=
f
you think we need to clarify it more, please let us know which wording caus=
es
confusion.<o:p></o:p></span></font></i></b></p>

<p style=3D'margin-bottom:12.0pt'><b><i><font size=3D2 color=3Dnavy face=3D=
Arial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>Thank you very much again for spending your Friday eveni=
ng
thinking of us :)<o:p></o:p></span></font></i></b></p>

<p style=3D'margin-bottom:12.0pt'><b><i><font size=3D2 color=3Dnavy face=3D=
Arial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>Simon<o:p></o:p></span></font></i></b></p>

<p style=3D'margin-bottom:12.0pt'><font size=3D2 face=3D"Times New Roman"><=
span
style=3D'font-size:10.0pt'><br>
<br>
<br>
&gt; Simon.<br>
&gt;<br>
<br>
<br>
<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Semyon (Simon) MIZIKOVSKY<br>
&gt; <st1:Street w:st=3D"on"><st1:address w:st=3D"on">600 Mountain Avenue</=
st1:address></st1:Street><br>
&gt; ALCATEL-LUCENT<br>
&gt; DIRECTOR<br>
&gt; WIRELESS SECURITY STANDARDS<br>
&gt; <st1:Street w:st=3D"on"><st1:address w:st=3D"on">600/700 Mountain Ave.=
</st1:address></st1:Street>,
Rm. 3C-506<br>
&gt; <st1:place w:st=3D"on"><st1:City w:st=3D"on">Murray Hill</st1:City>, <=
st1:State
 w:st=3D"on">NJ</st1:State> <st1:PostalCode w:st=3D"on">07974-0636</st1:Pos=
talCode>
 <st1:country-region w:st=3D"on">USA</st1:country-region></st1:place><br>
&gt; T:&nbsp; +1 908 582 0729<br>
&gt; M: +1 732 239 7533<br>
&gt; F:&nbsp; +1 908 743 4361<br>
&gt; Simon.Mizikovsky@alcatel-lucent.com<br>
&gt;<br>
&gt; Note:&nbsp; This message, and any attachments, is intended only for th=
e
recipient(s) identified above.&nbsp; The information contained in this mess=
age
may be privileged, confidential or proprietary, and its use or disclosure b=
y
other than intended recipient(s) is prohibited and may be unlawful.&nbsp; I=
f
you have received this message in error, please delete it, and do not
distribute or retain a copy of it.<br>
&gt; -----Original Message-----<br>
&gt; From: Ben Campbell [<a href=3D"mailto:ben@nostrum.com">mailto:ben@nost=
rum.com</a>]<br>
&gt; Sent: Friday, August 26, 2011 5:41 PM<br>
&gt; To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org<br>
&gt; Cc: gen-art@ietf.org Review Team; The IETF<br>
&gt; Subject: Followup on Gen-ART Telechat Review of<br>
&gt; draft-ietf-dime-ikev2-psk-diameter-08<br>
&gt;<br>
&gt; This is a followup on my previous gen-art reviews of
draft-ietf-dime-ikev2-psk-diameter based on version 09. I realize that came=
 out
a couple of weeks ago, and this followup may be overtaken by events. I am
sending it anyway on the off chance it's still meaningful.<br>
&gt;<br>
&gt; This version partially addresses my concerns (below), in that it now
specifies a default mechanism for PSK generation. If I understand correctly=
,
use of this mechanism is completely optional. That is, the actual mechanism
chosen is still a matter of out-of-band agreement between the HAAA and the
IKEv2 peer. And if I read correctly, there is still no way for either to
declare or negotiate what mechanism they plan to use.<br>
&gt;<br>
&gt; I realize the draft assumes that this will be used in the context of a
&quot;protocol leveraging this diameter application&quot;, and that said
protocol should specify the key derivation mechanism to be used. I interpre=
t
(perhaps incorrectly) to mean that a given IKEv2 peer and a given HAAA are
expected to be implemented for a particular context, and that the authors d=
o
not expect an IKEv2 peer from one context to work with an HAAA from another=
.
Furthermore, it appears to me that if 2 such mismatched peers tried to
communicate, the only way they could determine they were incompatible would=
 be
through authentication failures due to a key mismatch. I'm not sure that's =
an
appropriate assumption for an IETF proposed standard.<br>
&gt;<br>
&gt; Ideally, I think things would be improved if the&nbsp; included key
derivation procedure was promoted to MUST implement, and a mechanism were a=
dded
where the peers can declare or negotiate the intent to use some other proce=
dure
if they choose to do so. At the minimum, it would be good to have a way whe=
re
two peers could detect a key derivation mismatch early in the process.<br>
&gt;<br>
&gt;<br>
&gt; On Jun 17, 2011, at 5:10 PM, Ben Campbell wrote:<br>
&gt;<br>
&gt;&gt; I am the assigned Gen-ART reviewer for this draft. For background =
on<br>
&gt;&gt; Gen-ART, please see the FAQ at &lt;<br>
&gt;&gt; <a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br>
&gt;&gt;<br>
&gt;&gt; Please wait for direction from your document shepherd or AD before=
<br>
&gt;&gt; posting a new version of the draft.<br>
&gt;&gt;<br>
&gt;&gt; Document: draft-ietf-dime-ikev2-psk-diameter-08<br>
&gt;&gt; Reviewer: Ben Campbell<br>
&gt;&gt; Review Date: 2011-06-17<br>
&gt;&gt; IESG Telechat date: 2011-06-23<br>
&gt;&gt;<br>
&gt;&gt; Summary: This draft is almost ready for publication as a proposed
standard. I still have a concern about the generation of the PSK.<br>
&gt;&gt;<br>
&gt;&gt; Major issues:<br>
&gt;&gt;<br>
&gt;&gt; In my initial Gen-ART review, I made the following comment: The dr=
aft
says that the procedure that the HAAA follows to generate the PSK is out of
scope. But doesn't the IKE2 initiator need to understand the procedure? If =
the
procedure is not defined somewhere, how you achieve any degree of interoper=
ability?<br>
&gt;&gt;<br>
&gt;&gt; The author responded that the PSK generation was in fact important=
 for
interoperability, but that the specific procedures have been intentionally =
left
to other specifications. It is up to specifications that use this Diameter
application to define the PSK generation mechanism. Further, the author
indicated 2 3GPP2 specs that have done this.<br>
&gt;&gt;<br>
&gt;&gt; I am still concerned that this means that this specification canno=
t be
implemented in an interoperable way without effectively profiling it. There=
 is
no apparent coordination on how such profiling may be done, and by whom. I
think this is likely to result in implementation islands that can't talk to
each other. I recognize that there is precedent for doing this, but I think=
 it
is something that should not be done without careful consideration,
particularly in a standards track RFC. I leave it to the IESG to confirm
whether it is appropriate in this circumstance.<br>
&gt;&gt;<br>
&gt;&gt; I further note that there is&nbsp; no apparent way to negotiate or
declare what PSK generation mechanism might be used, if an implementation
supports more than one.<br>
&gt;&gt;<br>
&gt;&gt; Minor Issues: None<br>
&gt;&gt; Editorial Comments: None<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Gen-art mailing list<br>
&gt; Gen-art@ietf.org<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/gen-art">https://www.=
ietf.org/mailman/listinfo/gen-art</a></span></font><b><i><font
size=3D2 color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-fam=
ily:Arial;
color:navy;font-weight:bold;font-style:italic'><o:p></o:p></span></font></i=
></b></p>

</div>

</body>

</html>

--_000_E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21USNAVSXCHMBSA_--

--_004_E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21USNAVSXCHMBSA_
Content-Type: image/jpeg; name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=2219;
	creation-date="Sat, 27 Aug 2011 01:30:45 GMT";
	modification-date="Sat, 27 Aug 2011 01:30:45 GMT"
Content-ID: <image001.jpg@01CC6437.6A2E4D60>
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAaARQDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD2aisZ
tR1safqUw0MG4t5mS0h+0r/pKAjD5/hyM8H0qwbzUxqVlANMBtpoma5uPOH7hwOFx1bJ4yKANGis
V9S14aXqFwuhKbuCcpa2/wBqX/SI8jD7ui8EnB9KtG71Iata2400GzkhLzXPnjMT9l29T9aANCis
RtS18aPd3K6ApvYpylva/al/fR5AD7ug4JOD6e9XGutRGsxWw04GxeAu915wykmfubep470AX6Kw
21PXxok10PD6m+ScpHafal/eJuA37ug4ycH0q811fjXFtRp+bA2+83nmjiTdjZs69Oc0AXqKwzqn
iD+xWuR4fH24T7FtPtS4Kbsb93Tpzir32nUP7c+y/wBnj+z/ALPv+2eaM+Zuxs2denOaAL1FYY1P
xAdFjuT4fUX7T7HtPta4WPdjfv6HjnFXVutROtyWp04CwW3Dpd+cPmkz9zb1HHOaAL9FYa6nr/8A
Y1rctoCi9knCT2n2pf3Ue4jfu6HjBx7+1XVutROsT2zacBZJCHiuvOH7x+6beo+tAF+isRdS106R
Y3J0EC9mnCXNr9qX9xHkgvu6NwAcD19qtC71M6rdwHTALSKEPBceeP3znqu3+H6mgDRorFTUddOm
afO2hKt1POEu4PtS/wCjx5OX3dG4wcD1qwLzVP7Qv4f7LX7NDErWs3nj/SHI5XH8ODxk0AaVFYy6
hrhs9MkOiKJ7iULeRfaV/wBFTnLZ/ix6Cphe6qbvUov7KHk28atZy+eP9KYqSVI/hweMmgDTorIX
UNZNtpbnRQJblwLyP7Qv+irjk5/i+grifG2vJb+MEuFuJ1/sJYXEUcblZGdwZASBgfusdSOtAHpt
FeewarfLqtzp1hfR2n9pa5Mn2t0EmxVgjYKoPGWPTNP17xBrWmSzrZalJetpnk/bMWkSxDeR98lt
2SD/AADigDv6K8yj1fVtMi1KS2vJD9t8RzWa5jRzCMk5XcRkkKFAJxWpZXWtSeJdFXVYnWdFv1j3
hUaZAIirMFJAPJH4UAdzRXJzXlzJ4o8Ny6hCLGV7e98yEyhgpHl45HB45/GoZ/Et8lrqTpcx+ZDr
kVpD8q/6pjFx75DNz/hTas7AdlRXAnxJrS+F9Q8UC/iYRvJHHp3kLiEiTYNzZ3Ej7x7Uy51vxXZw
QxNMyrdX9rBBeXNvEGIk3BgURiCBhSDx1pAeg1Wv7630yxlvLuTy4Ylyx/p9a4S4vNZudStNLuNW
xPa60YFu0hVSym3Ljcn3SfmxV34mtOdIsLWMlzNcYIA5YgcfzrWjT9pUUX1Gld2M1fGviLxDqLW+
iRQ2kKgsZJADsUfxOx4A/D86mXxxq2gax/Z+vC3u48KxmtxggMMgjpnr0wKkh0/TtKisPCoLTX15
Isl6ImwMAZwx9AM4XvjJ688vq18dZ1zVXlWJoU8x1k8sBlC8J83U5O1cHPX6V6kKdObso+7b5+po
kmex288V1bx3EDiSKRQyMvQg9DRXMfDieSbwmiyHIimdEz6cH+ZNFeVVhyTcexm1ZnV0UUVmIKKK
KACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKq/2bZbLqM2kJW8JNwNgxLkYO7144q1
RQBmy+HtGmsZLGTTLZraR97RGMYLYChvrgAZqF/CXh6QxFtHtCYVCJ+7Awo6D3x71sUUAZkvhvRJ
5rmaXSrSSS7AE7NED5gznn8QD+FSWeiaXp/k/ZLGGHyN/lFV5Tdjdg++Bn6VfooAo6loml6x5f8A
aVhb3flZ8vzow23OM4z9B+VQr4Z0JL2G9XSbQXFuqrFIIhlAowuPoAAPTFalFAGd/wAI9o32+a//
ALMtftM6FJZPKGXB6g+ue/rTLXw1olkgS20u2jUSrMAE6Ov3WHoRk49K1KKAM+70HSL+KWK7063n
SaQSyB4wdzgYDfXHGfSqvifQF17Q2skKxyxkPAx6Kw7fTGRW1RVRk4SUluhp2PGNIup/C/i2O61u
3uN8e4SbhljlSMgnr19ae8I1900nw3pcqwCTzJJ5jmR2xjc7dFAyeB/OvYJYYp12zRJIvo6giljj
jiTZGioo7KMCvQeM+3y6+un3F8/UpaHpMeiaPb6fE27yl+Z8Y3MeSfzorQorzpNyd2Zn/9k=

--_004_E413B3F92D9EAC45A9C3CE54B0C685A31350AC6F21USNAVSXCHMBSA_--

From hotz@jpl.nasa.gov  Fri Aug 26 20:19:43 2011
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A405321F8862; Fri, 26 Aug 2011 20:19:43 -0700 (PDT)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkjw3DfnNB9e; Fri, 26 Aug 2011 20:19:43 -0700 (PDT)
Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.105]) by ietfa.amsl.com (Postfix) with ESMTP id EFA0221F8841; Fri, 26 Aug 2011 20:19:42 -0700 (PDT)
Received: from laphotz.jpl.nasa.gov (laphotz.jpl.nasa.gov [128.149.133.44]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7R3Ktoi010183 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Fri, 26 Aug 2011 20:20:55 -0700
Subject: Re: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <87sjoocgxs.fsf@latte.josefsson.org>
Date: Fri, 26 Aug 2011 20:20:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D59A1036-ABCA-43CE-B3D3-1D3334CABE2B@jpl.nasa.gov>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> <87sjoocgxs.fsf@latte.josefsson.org>
To: Simon Josefsson <simon@josefsson.org>
X-Mailer: Apple Mail (2.1084)
X-Source-IP: laphotz.jpl.nasa.gov [128.149.133.44]
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gareth.richards@rsa.com" <gareth.richards@rsa.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf-krb-wg@lists.anl.gov" <ietf-krb-wg@lists.anl.gov>, "hartmans-ietf@mit.edu" <hartmans-ietf@mit.edu>, "david.black@emc.com" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Aug 2011 03:19:43 -0000

Could we define a new section for the PSKC registry instead of a whole =
new registry?  (Agree we don't need all this info.)

On Aug 26, 2011, at 8:48 AM, Simon Josefsson wrote:

> <gareth.richards@rsa.com> writes:
>=20
>> Some form of identifier will be required for the otp-algID in the
>> PA-OTP-CHALLENGE and the PA-OTP-REQUEST and from what I remember =
about
>> when this was first discussed, it was agreed that it would make sense
>> to use the registry of identifiers already being established for PSKC
>> rather than produce a duplicate one.  My assumption was that a
>> registry would be required to ensure that the URIs were unique.
>>=20
>=20
> I think a separate registry is needed, RFC 6030 requires several =
things
> from a profile that shouldn't be required in order to support Kerberos
> OTP.  See below.
>=20
> /Simon
>=20
> 12.4.  PSKC Algorithm Profile Registry
>=20
>   IANA has created a registry for PSKC algorithm profiles in =
accordance
>   with the principles set out in RFC 5226 [RFC5226].
>=20
>   As part of this registry, IANA maintains the following information:
>=20
>   Common Name:  The name by which the PSKC algorithm profile is
>      generally referred.
>=20
>   Class:  The type of PSKC algorithm profile registry entry being
>      created, such as encryption, Message Authentication Code (MAC),
>      One-Time Password (OTP), Digest.
>=20
>   URI:  The URI to be used to identify the profile.
>=20
>   Identifier Definition:  IANA will add a pointer to the specification
>      containing information about the PSKC algorithm profile
>      registration.
>=20
>   Algorithm Definition:  A reference to the stable document in which
>      the algorithm being used with the PSKC is defined.
>=20
>   Registrant Contact:  Contact information about the party submitting
>      the registration request.
>=20
>   Deprecated:  TRUE if this entry has been deprecated based on expert
>      approval and SHOULD not be used in any new implementations.
>      Otherwise, FALSE.
>=20
>   PSKC Profiling:  Information about PSKC XML elements and attributes
>      being used (or not) with this specific profile of PSKC.
>=20
>   PSKC algorithm profile identifier registrations are to be subject to
>   Specification Required as per RFC 5226 [RFC5226].  Updates can be
>   provided based on expert approval only.  Based on expert approval, =
it
>   is possible to mark entries as "deprecated".  A designated expert
>   will be appointed by the IESG.
>=20
>   IANA has added two initial values to the registry based on the
>   algorithm profiles described in Section 10.
> _______________________________________________
> ietf-krb-wg mailing list
> ietf-krb-wg@lists.anl.gov
> https://lists.anl.gov/mailman/listinfo/ietf-krb-wg

------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu




From hsantos@santronics.com  Sat Aug 27 16:29:33 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C825721F8B7F for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 16:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.234
X-Spam-Level: 
X-Spam-Status: No, score=-2.234 tagged_above=-999 required=5 tests=[AWL=0.365,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id geoK-GbcPncl for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 16:29:33 -0700 (PDT)
Received: from ntbbs.santronics.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id D0E2021F8B7E for <ietf@ietf.org>; Sat, 27 Aug 2011 16:29:31 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1300; t=1314487840; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=n86zb8A 5jbFzcjbv9bXgfZY7pNs=; b=CNUzenfPmWMIp6CUB4vvvhWe1v1aTtYPXNnRXb9 SUyDLLjQdEIibmWn4G5QYv0KTvnMs01NyZ+VOQwXmUbQIU6LV1MwoAinN+frhdbg Llv7LA8rXyYwku+8SxYxcIOr603k9SCLBI/i5vQ6oqqLHNjvs7F5w5toWwwKluNQ VnmM=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 27 Aug 2011 19:30:40 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2943284237.40767.1292; Sat, 27 Aug 2011 19:30:23 -0400
Message-ID: <4E597E0C.7050708@santronics.com>
Date: Sat, 27 Aug 2011 19:30:20 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: authenticated archives, was https
References: <20110827143104.89801.qmail@joyce.lan> <5199131E-EE60-4506-A674-08533630AEF8@network-heretics.com>
In-Reply-To: <5199131E-EE60-4506-A674-08533630AEF8@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:50 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Aug 2011 23:29:33 -0000

Keith Moore wrote:
> On Aug 27, 2011, at 10:31 AM, John Levine wrote:
> 
>> TLS for session privacy is nice, but I find negligible value in a
>> little lock icon in my browser that means only that one of the several
>> dozen cert issuers configured into my browser, most of whom I've never
>> heard of, and many of whom aren't even the organization in the cert
>> name, signed something.
> 
> +1.  IMO browser vendors have made TLS nearly useless for web browsing 
> by including so many default CAs; some with dubious integrity, and a 
> few with a demonstrated lack of integrity.

Interesting viewpoint.  Are you advocating for a monopoly or oligopoly 
centralization?

I having read anyone mention OCSP (Online Certificate Status Protocol) 
which use to be off by default, but appears to be enabled by default 
now by updated browsers. It was a painful to solve a customer problem 
when most browser work fine with a brand new certificate but failed 
when newer browser had OCSP enabled.  Some miscommunication issue on 
the type of certificate brought and wildcard domains.  The CA has 
revoked it but only via OSCP was it detectable.

The ongoing direction of dynamic tracking of anything and anyone 
continues to amaze me.

-- 
Sincerely

Hector Santos
http://www.santronics.com




From henk@uijterwaal.nl  Sun Aug 28 03:23:48 2011
Return-Path: <henk@uijterwaal.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6988A21F8B02 for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 03:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.451
X-Spam-Level: 
X-Spam-Status: No, score=-0.451 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Pq7-99FMq-n for <ietf@ietfa.amsl.com>; Sun, 28 Aug 2011 03:23:47 -0700 (PDT)
Received: from smtp-vbr5.xs4all.nl (smtp-vbr5.xs4all.nl [194.109.24.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9E0AA21F8880 for <ietf@ietf.org>; Sun, 28 Aug 2011 03:23:47 -0700 (PDT)
Received: from geir.fritz.box (thuis.uijterwaal.nl [82.95.178.49]) (authenticated bits=0) by smtp-vbr5.xs4all.nl (8.13.8/8.13.8) with ESMTP id p7SAOYRr026691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 28 Aug 2011 12:24:34 +0200 (CEST) (envelope-from henk@uijterwaal.nl)
Message-ID: <4E5A1761.8030600@uijterwaal.nl>
Date: Sun, 28 Aug 2011 12:24:33 +0200
From: Henk Uijterwaal <henk@uijterwaal.nl>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <1314226999.1973.211.camel@d430> <4E573BB6.5000700@gmail.com> <CAHBDyN4ML7PL65=kQXchvvgmtOEX_hK5LB8BPSxjvOL0G11vmg@mail.gmail.com>
In-Reply-To: <CAHBDyN4ML7PL65=kQXchvvgmtOEX_hK5LB8BPSxjvOL0G11vmg@mail.gmail.com>
X-Enigmail-Version: 1.3.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2011 10:23:48 -0000

On 26/08/2011 16:48, Mary Barnes wrote:

> [MB] I've not seen a single person advocate a 0:3:0 schedule and it's only less
> cheaper for all participants (not just US) because the hotel rates are extremely
> reasonable (<$150 as I recall).    It is definitely less expensive for the vast
> majority of participants than NA cities like Quebec City and San Francisco that
>  travel by air.  BUT, I think you are missing what we are saying overall - the
> major reasons some of us prefer Minneapolis is because it meets what some of us
> have been saying over and over as far a key factors for meetings:
> http://www.ietf.org/mail-archive/web/ietf/current/msg68656.html
> http://www.ietf.org/mail-archive/web/ietf/current/msg68727.html

I like Minneapolis as meeting location too, assuming that the visa troubles we
had there last time are solved, and I'd be happy to make it the default location
for US meetings.

However, we have said that we want to meet all over the planet.  That means that
we have to go elsewhere somewhere, even if there is a good and cheaper
meeting location available elsewhere, but in the wrong region.  The same goes
for the meeting weeks, if a good hotel option isn't available in a meeting week
but is available a week or so earlier/later, then under the present rules,
it has to be discarded.

Henk


-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From mrsmarryesmith@gmail.com  Sat Aug 27 02:40:25 2011
Return-Path: <mrsmarryesmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EDC21F8AA9 for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 02:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.501
X-Spam-Level: ***
X-Spam-Status: No, score=3.501 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXgMS1fugVIf for <ietf@ietfa.amsl.com>; Sat, 27 Aug 2011 02:40:25 -0700 (PDT)
Received: from nm16-vm1.access.bullet.mail.sp2.yahoo.com (nm16-vm1.access.bullet.mail.sp2.yahoo.com [98.139.44.167]) by ietfa.amsl.com (Postfix) with SMTP id 47CBC21F8A71 for <ietf@ietf.org>; Sat, 27 Aug 2011 02:40:25 -0700 (PDT)
Received: from [98.139.44.104] by nm16.access.bullet.mail.sp2.yahoo.com with NNFMP; 27 Aug 2011 09:41:44 -0000
Received: from [98.139.44.89] by tm9.access.bullet.mail.sp2.yahoo.com with NNFMP; 27 Aug 2011 09:41:43 -0000
Received: from [127.0.0.1] by omp1026.access.mail.sp2.yahoo.com with NNFMP; 27 Aug 2011 09:41:43 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 852571.53161.bm@omp1026.access.mail.sp2.yahoo.com
Received: (qmail 35794 invoked by uid 60001); 27 Aug 2011 09:41:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1314438102; bh=tAlzSYlNclC1tyRg/FKSUTmITiOYKfYvweNNw+eVDJM=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=HjGr8OmHkMz7s30zZM/+jgYDadFuqnz16oFF0mMEhf+GlZykCxmjwuZttRVFSuPHHOoDZhhQvWAc+MLG1gQGTEHz6iVpW4ZdtytLsPp+Y9UUpy0AUginWS8yQ4vuBbC1PRMDKlTH7GL7mmWlNigQgWdKh3wvwiSSbYn/jtf6PZ8=
X-YMail-OSG: u.q.eq0VM1m0bIaRGm3lhGZFmEB8A5xGtoyav3zXElbtq5V DNoaJqB_j2v6RQS0p3KJFQVVGxzH6ffh3eDTwr9_AXCznmv7Xa1R58Oh0bVm qI4QFR9OJVwV11.SAt_5C0hzpvkBldzWIzNeEBSSGE29Tq769EBYOPblM5fN c79MpP5hb6KUWmC1aNbFHROblBqvqUNAuwBti5DbyIPO0cs.rXyIOXp1RvVM 1CDjiiVis2Iz7Sv5yN9TGIN.UcSWqAZY_zyW4_xUrghsTbCRYJFNCvnuI2Nk ZKGXy81xBzYKwgFCou7OFvsHrV.rRnV4ZIDnv41XwYvclmbAZHnrv7NEjBeY ccRoCAjc1JMyy6dganOD.wr6O5aDUUDEUcdqkNV18URmsobBnhQcJdyt68ZB nHYF.b41TN14fFWFDY7k0YpArzjWDQr3DXtcI4jNAEEm7p9X1EHD2TKMTBkZ iR9baJ44XjYKMh6kWMVaL26azKjBtudC.kfJNOH6uFQSEh5ywiwBM
Received: from [41.133.95.94] by web181214.mail.ne1.yahoo.com via HTTP; Sat, 27 Aug 2011 02:41:42 PDT
X-RocketYMMF: webhhhrrrttt55@att.net
X-Mailer: YahooMailClassic/14.0.5 YahooMailWebService/0.8.113.315625
Message-ID: <1314438102.19139.YahooMailClassic@web181214.mail.ne1.yahoo.com>
Date: Sat, 27 Aug 2011 02:41:42 -0700 (PDT)
From: AWARD CENTRE <mrsmarryesmith@gmail.com>
Subject: Please view attachment for a very important notice
To: undisclosed recipients: ;
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-522882420-1314438102=:19139"
X-Mailman-Approved-At: Mon, 29 Aug 2011 08:11:49 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: yahoosponsoredaward@ananzi.co.za
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 08:48:59 -0000

--0-522882420-1314438102=:19139
Content-Type: multipart/alternative; boundary="0-486282226-1314438102=:19139"

--0-486282226-1314438102=:19139
Content-Type: text/plain; charset=us-ascii

Please view attachment for a very important notice
--0-486282226-1314438102=:19139
Content-Type: text/html; charset=us-ascii

<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Please view attachment for a very important notice</td></tr></table>
--0-486282226-1314438102=:19139--
--0-522882420-1314438102=:19139
Content-Type: application/pdf; name=Government
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Government Accredited Lottery .pdf"

JVBERi0xLjcNCjEgMCBvYmoNCjw8DQovTWV0YWRhdGEgNDcgMCBSDQovUGFnZXMgMyAwIFINCi9U
eXBlIC9DYXRhbG9nDQo+Pg0KZW5kb2JqDQoyIDAgb2JqDQo8PA0KL0F1dGhvciA8NzA2MzMxMzc+
DQovQ3JlYXRpb25EYXRlIDw0NDNhMzIzMDMxMzEzMDM3MzIzNjMwMzUzNDMzMzUzMD4NCi9DcmVh
dG9yIDw1MDQ0NDYyMDUwNzI2OTZlNzQ2NTcyMjAyZDIwNDY3MjY1NjUyMDQ1NjQ2OTc0Njk2ZjZl
Pg0KL01vZERhdGUgPDQ0M2EzMjMwMzEzMTMwMzczMjM2MzAzNTM0MzMzNTMwPg0KL1Byb2R1Y2Vy
IDw0NDZmNzc2ZTZjNmY2MTY0MjA1MDQ0NDYyMDUwNzI2OTZlNzQ2NTcyMjA2NjcyNmY2ZDIwNTA2
NDY2NTA3MjY5NmU3NDY1NzIyZTYzNmY2ZD4NCi9UaXRsZSA8NDc2Zjc2NjU3MjZlNmQ2NTZlNzQy
MDQxNjM2MzcyNjU2NDY5NzQ2NTY0MjA0YzZmNzQ3NDY1NzI3OTIwPg0KPj4NCmVuZG9iag0KMyAw
IG9iag0KPDwNCi9Db3VudCAyDQovS2lkcyBbIDUgMCBSIDI4IDAgUl0NCi9Sb3RhdGUgMA0KL1R5
cGUgL1BhZ2VzDQo+Pg0KZW5kb2JqDQo0IDAgb2JqDQo8PA0KL0EgPDwNCi9TIC9VUkkNCi9VUkkg
PDY4NzQ3NDcwM2EyZjJmNzU2YjJlNzk2MTY4NmY2ZjJlNjM2ZjZkMmY+DQo+Pg0KL0JvcmRlciBb
IDAgMCAwXQ0KL1JlY3QgWyAzNTcgMTMwLjUwMDAwMCA1MTkgMTg1LjI1MDAwMF0NCi9TdWJ0eXBl
IC9MaW5rDQovVHlwZSAvQW5ub3QNCj4+DQplbmRvYmoNCjUgMCBvYmoNCjw8DQovQW5ub3RzIFsg
NCAwIFJdDQovQ29udGVudHMgNiAwIFINCi9NZWRpYUJveCBbIDAgMCA1OTUgODQyXQ0KL1BhcmVu
dCAzIDAgUg0KL1Jlc291cmNlcyA8PA0KL0NvbG9yU3BhY2UgMjQgMCBSDQovRXh0R1N0YXRlIDI1
IDAgUg0KL0ZvbnQgMjcgMCBSDQovUHJvY1NldCBbIC9QREYgL0ltYWdlQyAvSW1hZ2VJIC9UZXh0
XQ0KL1hPYmplY3QgMjYgMCBSDQo+Pg0KL1JvdGF0ZSAwDQovVHlwZSAvUGFnZQ0KPj4NCmVuZG9i
ag0KNiAwIG9iag0KPDwNCi9GaWx0ZXIgL0ZsYXRlRGVjb2RlDQovTGVuZ3RoIDcgMCBSDQo+Pg0K
c3RyZWFtDQp4nO19C5hV1ZXmKYoqyiqCpMcomnR745d035tQp877YTOxEB8QlSCWHxgwUBbPWBTF
GwzhEdMx2skYTfdoOg4yrWntGIXoxCcqEB8xiTLBmWgyiiBjTCYqGEeFaHDWPvucvdc5Z+1b5xa3
0nzfdKwv3+E81l5777X+vV573yUlQzetksH+Sy56FrV2TA1K85e1Lmk1Sl7oh7rnlxa1OqEbiH/2
8n+6nu55AfzLkJcLWqeV+lqXlFzLDiKCXmjZpXY/0MPQM+P3XN6MaZTOWtx6Ify3pGSFVsRHyQoc
vxT4Lnu/ZFmezRrkr1v8df7e1HPji6XzgdVAt9n/ohv4umdR6cwu9q1dMk2gFAalrnmtBhAPHduN
XgGmLN31Sr7l6AE8XtQ6o3xOxdGdwPHKSyumHnq25ZYXV9pNmzFllRdVTEP3DLgqVWzdCizTKnfB
Y90MHc8pL6i0h7oNA+SV54rP5ZsXV9p9PfBtv3xexdcNw/Hjh6YTlidXLN0xXDcsd1fabd03XS8o
LwduDMcM3fLCiqE7jgm3GT/J8z64GwC30GB3xYO+OJZT7pWvloA3X7f8wCmfz9m07QATkA3Iq5j1
IEjGAK7WVFzDuLTrs2xAHTygQEUPrRBGs2tOK7TX9cXWs7vYVEFbQei7pfwFmz/102KT6lSZVBhq
3bXQrGK2hkiCQCwCh0vQ56K5dUOvPK/S7umW7dsuvuQzadmOXe4RQkKJy3ghEXP4NBtuAJdCxGB2
LN1ybAvN2DI2y57theLS98zy6WJuS4yPMAygcU8IjJkIuFluF2/6UkgM8Sb6/CIpekieVlRgqEwP
9Gd53GPgZAGWUt6U64EuWew2NNof9wkakFKYkvKEKJLnqWJ0FkfsWWFYXsUVjN0cyzn1TaZjlhvJ
7r+5YHqWHiBZGXq59EJPj4HtzBimYGh7pQTGo+zZZhrmkqlB8nSZFMIV8lIK4RpJKpZh341Qx9Qd
3w0UsDVHzO1iKRrouQTIGD0d20YCsZCJTgD8pQGsHcbL9AwXkUeie57Q0PhzUDdEc75khOQuuwgw
5qYx5oC1wC9PiATTsZleJYJ5plwjEhH2zbIjno+XgsvlGlZKKbdZsbJcR3cd51jCXNsImVALeaO5
8gyYfqAKyu6DJGa4yj6tmxIElu57XAskapwtp+ScSrur+zC1Nr5LvipXaT7NnmVFj2MZp5ZzuR5g
GE7euwA+tnTDTgHqtAqbdtMKdDe0+TTPQNB8vuSnQ671FgbsDHbbPoZ29KYnL0OB8ra8Ga8CXmgf
QzDqhGCioWk9poTNC3Tf4sI2DWQAbFoAxEkSRqVgTE4JGJMgwBkpddIQwLIE02H5Dtwk13RLzCES
ARNfJtLQkTISk++ZNOq+axsesj4kS+dLPlPfR8IMcosEE7WPxEnK/bEjTZYbIZeYt2NKmgDpKRPW
TEwFs2BT7sBNOTChXG4bKu1wK3RBTIaBwJiOD2tdY6Xd0MErc2FVHQ7T6NlMCpvYwuVbBpgKzYBz
oeEBko0AgQFxAblvYY9N8APZpa0bAaM0DKQEnCwToHN4hS2qplM+rmJ7pm5bASUSf+6xN+1Qt+SA
8LFvd+F98FVLkR1gcUyWOhorkR+k7g3tU65HQnnxzaF6HFlkYo5MOeqR8Zr699HPQ+DrIJewPDqx
YE4gFtXJ0iw8V9yUkCVhDPnpyJREkEW+OimCvNAEWxa3KUFajNAlwnCTL15MvThetj5V2IpnYwsx
sZ7Hi8cl6c7wVSUAQzRZVcCpnCzenEyRnAqXgW66rouoczZ9sH3joEdo4XYuljZpJlzBPpbNSCbj
YfOdQAwbmFSfSz6mPjk/ZRgnTaN1RnyN5qQrkkDbd0GgrMQ8yq2hjPwl8ZUVS23OkgYJA/Q4lixp
jsZuGOheXZzEAm0FDjJZwOa0vEwAKwGgbnFvqYxnzBUeoHyxn9sZAPa93MNixrGk2C0+WZbISYiC
GHOw0Zlg0XIyACafp1y5xAqaR4UTlsrIxCJuT9lhyj9cUzHBjXFcJx3ZIIIgiKkF8tVu0ZPlZCgu
pu9YceiCEV2B+UOWXfJNMsqCZxeWT96QBcOMwoO9ciCWSYCQmis/miP8zzmJ7x/GrUdBJaYxluPq
nhsmWhZTtAHlSOIL5NTJdlaKduaKe0jbL5PfyOfyqi8rDawd1Lh8E/Vc3uwRV2gy5hJjgDiKo3We
b6HgkhgY9GI36k/CmmxQPkXsLqAa7Jd9FM0ggb6CT77l0gO4WH49L/l6npzGKBjiJ5QN36R7QM5n
rCtgwSFC87lk2GAPCsFYSEodOeQpmul5cFHUo91hqQAwJZi1aDi8mUViaU2CPJ6Pbl4mcAc95v22
XB8B1GLxIh8oywlkZMaH5QvatME1ENIHFuxyGTZDESaprRJ25ioAIIGNs/l6Cxy1k1jULcmnFDtq
30gZEwg3llXYmsFsbRzBT7jTKVPvEhRErY50C8RNiW4r5Tdxi7ZCR1dICb1MyD+pw0skEq1I4UKs
AAgNlnMxdG3dNESUBDDAgtXYDEyAWVjewcsIsLyvEraB1GwSYZZLgV5A4hfdzYT5RXmTiVLTZIQN
ZukIe6uPQkRJ6AL4OrQ8sK1y0pFdAfJpI0a0T4QB0MigGCXCIPE5kmRa10lgm8IDqLZYSh0ps+yy
L1H7OfJekrgw6u1rFDCFWJaSm10zmNkFH/n4IxuWbQtucXuxIX4l5cO4ehAgs9SU+DFWuG8yKGfI
x8mllX4z9zy6TNBLF4gm7xmqXB3zsF0n4f7SobMrTVA88NnkaM5AmCNtMmSIIfiRaI6NP25FBhiI
EAhL7/QS6Vx1C5MJ2WaL8SWZ1koi/v3kRxLkUX6NNi4HMDJS/hVw6nFoFngwWT7vpmwYpIUklHUj
uyi3CBksWAdrnO85AfocgZ5q6QbT1YVlNTFirRABE4KLFE4jStIYScA7sAR4k9ynuozRLIHaPsF+
tS6zIZcdSRvR8dqCRrQ3G95k3aOsNISqAvLxeKqnyxWD5DgOKHLSyjETGXUNV7cwJPI4mANQGYQe
Msv+DC4qS4XEKRwZpkF5TORmyihZv0RM6XEizxUZdGRSHt1Mk4qfSyxYLptHsCDxa5XgGZtmGaRg
N+UniI583JtTJYZ+nGPXtPNKy91pAucwCiMfWeY48yC8ijIW5deIN+ROSntrYep5NftGfiPxgjQb
F8Yuqq/bToIhJG6Rvk3eeVdpNrJE5wvYW0BZjamPKM8xyf1eUDFBuwwvlYPuyfhqaS5QJyhTMu9q
MMjrEehGIVU/xe5yyo1eKl1i2dvLUngdt9NLomjceug4aUaxFR0HDGX4JeVJEkwtEhFMSQgZkvEa
44ArF5WkRfLB1RfWPSRmfYTzGTJIClLR/nnCkZQuJSqgyOoMgyBLPlZYgoRRh25KSn1SObuFmGB3
ODF2EHCMpXw+lI4bK26mMsbUpRzgPirQhZzXXDFSGgoHATwI6uQKL8MspONByj1tlKQihwQwCelA
MliKzRewoAIBPTPLiS5OkL5UN6JDWDccnE3LRPfGIltAAIaMmacAUPSC/lxmEoQxuYJCUtQ1pOmk
Uhdu82KkX6LnKY8Sq3TcUC72m3Gx0UeSOxIcKJbO5pUevmtiJzQOjHkhdlL7Y5l0cPQhVVWWdsdZ
FjO1xHHsMfUg8RdnyCBXL9V1DD4eS2umIl9nJ4Wp0v5AxVnIlBkrXEKqlJDCsIXSepHGj2wmFf+P
QQaFxcho/eekG9Yj8EAigwQOaUMtlJGbbhFNmlkRIEGCWXd1sOmnsEriTm4lYt8g40ZiFbKcUk5O
xgDkE5qJDdoW6aIM0pXjoVf4t28mYoVg7zT2EUvBWSgk156wUUPq4DSGw4HlpkJE/cikISLkyAGi
cZaORVEGTmGnaz7FUnfGQgCWSEyVFoBcQ1LmWKKapK1Hh8GoRAA5qchQWZHgAk5WCG3AcQTxCZXP
6YsXJVh6Akv61DFtBHikn4wmX1pg+aQIC9sLB1YiJwKvACTQtVPghdwnbDolBs+ibEEmg6I+FMuX
HhcVjZcAJQmlZoTrLnApa+BSzkxifEhkIH0mGRgnnTPk0JFgJBGINpFJCFpJJBWWUrBEpyKlWYhe
zTlyKeXqJf00ajUlTRsy1rUcAxxfGC3d932JYAnNrNnFCGFFonwywXo3SlElbpp0IQcR20c6Q2Yr
Uo5f4vKi4D4BFX0KPytGGrRkEKYo7eN1U9kR0pBSKD7hMa/EJhs2uTAnbB8CORr9ctyQSbUygQ0y
Fxinc2xLD2X4nESibA4nBURIt4S5hYMQ6KlgbG7FcZxjIuQWgOEXlJzAi8NdQx9ac/xot0wmtIZM
S1U8TVSCJHhOInIu0apIw67IrhCpehISb6VhSRZPpD0NmRRMai9IKzGfknDS2IqgWbYvMwn03qsB
Cj7wEkHklano4HLKYkQqskTcRDhJm2WU/i4XZqZvCzNzAYYE8XnO9HEtjwZLCeMUdtOOIc4ypMLi
gymCrbqBgVV7OiltQE48ys2eJS9lGv/0Soqzuqopq3PDaoogwUzaMmtoq1rFpe0HehoS4opwM4j3
J4B2m6gEEZWBJzsZQPpkrEKW4qE3p4ub00Xiy5AiEarylyGQD8XSgC2SoxaNaoPi+J6elox02WZc
dciLKMHjp0sRU5tIhAhNoJ5TVZayWPN0VMbDDW4LbgQpexvV8V8k92rxbSVWqJu+55ZS20oYLOeq
+yMoRxHMfITSMtH3qW0lCcyF8mZqW0k8xUMjxqYDwAtT5gZso0g0ZfnoQbTPJrNBgy0weIOGCGKQ
+4Lo3T7tg96hwYZT7hnrkCgolZDSrNR2IJEnT+3FSGjaqXGvP1RFGeXUuJNGd2rJSpzxNRXbhx5Z
wUBWfjrKm7dnydCGCATQ0d751CKK3Ym8l4ANedGMng0QMjGTceGpUsXmEsS7kV0cfzGHXHQVnCv9
G1dROYjsdDIIKhNSZC5toLQaohRjFdsCazvptEpsNxpWiIzJbsrnR1aptCbnEqYoKuWLLQiUNLPN
vLWJzVIR6LLFRHB7EtVjCjNNOtgphBGXl6P4Znb6mOrPQaYjsnqiyjXHxPrRI1pKlaOIy+VZNy1t
Iw9ciiwoyTgHGWmQjPRmQ7YKpTNr0SpueQJXIZXTRYQo7UYRTqr8hsxdkH44dM1mBWYD1xHSNXJk
xJCsdKY9cYSBsqkBAgoi8ECFdcjYby3RWVwULGqLUdlmOpHspnhMl/xG0pMKgKZgE10eEz45iDhA
leM4KZ+83fHAVrbcOtbBDLwf0AFttXKboRCwJbvY493wHEnFvn6Z3VmOUC9x7yegwhoRhe0WSJjk
Z6Li1uR8gNS2puTz+an4o0j0iO3N6GgI0kZCnoQ8gUQn9qehPUHUoSX4+BLC2f4sLvBLEC85wsVy
0IkA8boTyLMuuG5EPTKDWFBjOTi/tetTM4TBCD1LarxtFw1ct5wzVGaEKppOzy1mODsnAyd90r5H
m2mSczjwqoLPeiFKj5YKWEej9UUqR79ADEyfHK1UOWQymuh5J1AKDJaYWoNKyUVDMc10cRG61FPr
j4i7oOdsWg0eWGFtejDDl2dmiE1Ml5wYaTmoxj2XSP00SyB7vuuH8ekNbAqcbL0GM/p8eRPVc9ji
I0ndFOOBzlxxKIlFLoMvPgrwTeFHxCLJrSwukuJoIyR7q+Xl6QQkFOsuezOQN1M9z6RR/ACdeoF8
QxdzTlSqOIIQOrHAzHU30UD499/kjyqy2V7qRD3jsSAS2XIDRWqr2kr5GAHuUmLUUCB0MTVWKEOc
W5WZWNNV/cgflHlp+dFqLDB0VghlktJJIWSWMabmC6MQw7dQ/x75Jo6mDmRTEiFaqioIeXy0ZYR4
nkMYkMsHcAQz2+PimrMSZXbmN7A40vxVZYUVG6qQm5tENAd0c/P1kLQLSJfXJDPmhSgbRpvPMYHA
twbY+ibs7EGVMeAaZzEek3I71gYeLMJXl6KQcjozRWuZhBRZiSh9XvRmnyglNMJAuiVELRK53zDV
pcibcFPkk41DKT8cp9SZNWilQnw92cWL+c/Sa0ZGRT4pHmV15OFCKbvThnFwA9HHmWVpvYynttqT
h+Mgw2xmpQKGLhXOdWCZdnyxgzCVoBYNVfWuGJrQbrVEFrSmWtnVKL2xbSC0IpP6imohYtcyzXOK
qJDmvqw0q0tpkMKiu9Qm1ALOXtLqWNIfw9pIpJeoAB06kS1XN5VBBxV0cWB2dFNmhckIYA4h3GxN
ekGHvKqji/LiKOV/OSo3yBTrKIFvWsUMwCIOFBHJPmJtk9hAry3dqIwg63BbmTcTkBNJ8pUSjuj0
3gB1SKq4XwJiYDHovp3ezns5tV9XHiiAEs7YuhLO6QKiRAgBH7XxV9a+oBcRcMhhz08Lez4fYchR
Hj2QIGg3tX1Ddd4ngXCK5HjVTDJZ+ZiL0GegUopXWgsIDSa1DUEVUbKzItb0QHd9kZ2akwUax7Hp
ghW6tpuqxiucKlCukZ7BViei7hudyCJzNlOiTXPg+obyNBOZvemSKQGZ3JmcejzgSgrmAVNhAh77
CRQhi7UGTovUXDyVqilPgAvXjMXAg8zweSnYyqEecoF6qNL01Fa+JDJNbRIB3LcclqazkT2GoAoG
1DDdVJYihmtP4HW6RlEsWbjwVgKQLuDrmNneF9osSWcbjk6dM1PXDDoPXlphdNb0n6WqyfI93c7U
cYRuOlIqJmw+FwHbJfNPyJtHaSMUMSJfRUKSCodlUllKYxIhPVVAn0bl+KZcm+gDJJAT9HGxJlBX
Q1xQAU2gCfozCIMHqICO0UsFaqfieKCwQeaLrGE3dZDIHKH3yKXKbrwwA7wTrJ5HwA3tGW91eExl
Qo8V3sjHUfTQS0V/5GoxZGwYVqquFbeYafvfHxd+zOoP4XGSPmxPphUv5vIEFanTSJPxap1onvwk
hQj8PATfRnUGUm/jKDO4hfm6EIudNSGyI4sqzDML3JQhRqSTrVTKLZZbN8oJcjiLbVHWIZmQ60st
ezKKTRTfouc9wg8jz1pCUeyc7c0OKUJbt4rpSuBVffz/DxjV63EkHIGv24ZHBNmyhI5hlf73x3V+
LJ1IW/eY5yhMJysp5QsCthPBMkNWWxrZ0RcxWmDmhuwXG3ywOR0/2uoHzrBlujzIHuqe4YfMLGLp
3MBLv7A0ug4AXVjJtOX7rEnKoc1W4Npgn3uImXIpPnopxF+B3+ZE223bXS+q1Z0THWZsAQqx6Eru
ynFquAKwA8PeCdKXg6TDzk9UvwiYWQs7A9ysrTMwY4Pp1ZCyOHCDVqia1CimZISwRouUxtHOuZIz
P6w2q4MesupXtmuyVVx4a0tawc8G78sP/fj3m9iBZck/e+N/2q7D/2m7noH+yb8V/1zQOu1T/Eed
HK6KVskxwXcy/cCJf53pzEmtHRMu6ph67pmtHdNKXmvHxJLZ2nHmlAmloHXSWaUf9T/x8Pqfw9/j
1+7e8+gr8Nd69qQS+90n0zcTmtAqY9G3SJpmmCLacU7HOb2tHWdNGTeuY8rSuXMW9ixfvLRkuvDJ
4t4Vi/qWRR/A9eKly0r2Zz7DuFh9U8/7R468+lbb4jETh1/ffJrWvrNpX8KIb2X6puAjqJGNgODi
pv1bDx/ZOH/k7dv/dc8YbfrEplb1cHjGEA7HCzPWz5u1/5Lm3Q3anuuHn6gcCwUT9RiLmX+x9a0/
fm3EyNtL7601tEtebLpFPRZOMIRjMe5vP/jNm1ffcPOs1T/rbJl4Ssuylq2NJ39sWO8/HWnV1v3X
lnMTtsKEKdC5sApTWR1498Bh0TMjEERCdiq/kohVa88somdrV33w7J8ad50x7tD7+/a9+u7xjxjb
N2wedu2GcVtu3bj1n688Qbv28CihB56dmXsFa36NnPlVxO8Tpdu3t2nn/XF4lxjkUE69zbiwPXqA
zFoHyFSjwp4zDt1958Hnrz3+0TFTNl74lVO0aU996Jk8R/G8DylHCUIEG27daGhf+p/DlwrZccUE
gXUWVGGk1hkyqSlisvPm1dPuWrz64JEd85vP7LQ7d3xq1ght1xltX1WKjIKjuorM7Is3t2kXuMNf
T7gIEFp4JnBh0YtTrWBBYcXalUeenvnk02d85v3LOpt+8fsXtVufb5lHzRA4+GpO6jNDiaicpZ09
olI6+eE9H9J+5st1LSe3KmbqIrcMRN/+5vHr1h5a8cF2GxR7YekHvy19b0HHcdrJu9vkEAWSq8A3
1FxZtXJlqfT73p09r574wmXbm0/4y1s3zVr91v4fd5xfuWW4u2Xdp7UpX6uCfwrO6irMo9msTe5o
mkcJczQ+Jm2N1FuYh8GC96tXr2z43ustO8RkOU5GnhXMmF6tIuRRg/L5/tee/+rPRj7WcNsVPdpD
vcg4sjzBiO15VRhxamXEIRj5wbwbn+r8mKaN7W0QlpEtOXBdV82Bk139b+q850vad+APjGBCNb3A
rNKduqgmm2ZY5JgV8P7L/+vUU9eZ2zf888OfuEr7LjMB5mwadUte+OzAq8JXPYRv230f/G739kuZ
8G1oGNXg3TJ8xQXr12i33dgilpfQkMZS4FcZJqPWYTLUxtKujm0Rgo35ljN68p4DbXM0bdjNbQIl
cp6QgqecJwTTz+VA/JEqz4DaoI3uuqv89c07n3rvyw3/8ruWfZSmsYorJTP10TTGzrXHn3Hg1NVH
9u/fsqyt78ihg3/fcFz59ImTTmk577dtjZO0T7754VvUODCk3DEP5cmrZo0cORLGa+26fe2Nnxrd
tfcjU/Y2WSe8/smG2bvaWpXwoGCsEDxgO8JznSrdrKel90z7/YdhbWze1jll43PGF57+fudJ2i8W
thF+sh24VSSjHr7htnuPHAFwGDlx+/c7n2Ou8qwRTdRCbZhVRqceCzVj5NePNTJ90Rqf1ppKx2lr
3hixRYkGClYGQgOQgvwwWyGz8r2AdsPqMczMaHvwscaRt28vj/+QdsmB4c/kx9g23VDNRT3GmIFA
149/NNLYfPLm0eNeatCmouiMHGHbMSw1I7kRhiEVupVWr6yuqkgW09VALlIeUFZSs2pdpCxqkWIG
7SNP3PPkX8+cF5ls1zef1vk1WMy/tW39wfDr4w6OvAu01//iwx/VTnxErutoNgPHHuLZBDSB2YzW
9Y2bD4/SrlgkQyhYda2hZiQWq4lRfGnKKhlfymptYZnKaC0SA6y1IZgqnk97wnXR2l+vXzhj35Lm
rtEOKMvnr2k6l1AW0zXUXOQ6tufRV64cfTPvFVz8cstLhKlqOVVI1sdUZUYh2GAn92t3DLtU++4X
quBA0a7VgAMKkjkcEENFCoDtWUMsAAwEwIgDS3XuhgbwZH+29lLt21taKHX3vSpjVQ8tY7w80OS/
627605v7TmpsbLxKm/GHdbO0zR9tI/Qthp+ic/ej/iewvt05+1FChQ27FnEAGpgktKBEhaIkM6iA
chxIKAyDrQ0eHVKoSzj9u1s/eOErM+Jw+udPp+DONh1TzUWuY0/f/CvRq38wfvDGS38gPDOOCgqS
9fHMEjPl+Q2bh3VoS1bJaHEOFYp2LYMKj1+7W4kKCpI5VKguUzEqFOUPhhsP/W92vUaQ9IMqQ58j
CTQwxqOsRE4/i5L8RulfsOQjAcnpZ1GSoD2YJPQ9Iem4Gf1UkHQH0E8i2MGKvU3PHbpgx02Xbf3N
4b+7b+REZp2Bfn6rQettlIub7Bp3ulWs5LqGARKhI8IdywnV9Oq1GIGH9Jw/bvaGhvFNe157a4f2
7dUt6oVbwctAKopgNaeiCpJqFUX+FlZRM6iBP4yOaX1C0+kHVYa/qqQCeYIe18+i9BQBp5xyFu1y
RjkRyZxyDqbLSNlzyukMXUwMJHj+tS/fzQKjpQaWSjlO+955I66jlk8WblCxkhstkAgswGhCc/qp
IFkn/Yx7t7C5PPOlgxsaRt69a0Sjds+N0kDDWRmupAqG6pOVuWn/1u9s3LiP5a5mlxaWfv7x7c9o
jaf+1dp1H+y1G0dt/m2pSbvzwdbrCPHnGqpgLidbeHlCK3xOPYvSw+KP0DannkXpFVXPogJXg3oW
ZRGrJ7JrTFv22bAYQUtRx+DWagC6VVz5Mdv/dc90u7P7kr13vXv8Zxof+NiwXhbAbm6XopxTLQVj
9VCtJIvX/LWX37vurY/dt239wZN/4n12SqN2w1utz6iVS8FS3ZXr1kZAM+3AycPVqqRgpaqo0isx
K8JU0qt1JeZ6pCBW1VgewAwtShIv7mkuc6pUdAixKqEAixn9PkysSjbrtqmIsNi1qpJdxZcas2HC
htefvGrW6HOYt/7gLTJ6gOaU+3YKfnJzCusddzBobLQCV00sN1qA15RplVcmBcGhWqlGnXb4V2Nm
a2O/vrfv0+OOvL9zRmnCL8a3apOfqbJeFe2zQsly61VReuDxFdIzBb0awp85PStKEhtIKqM31rOi
vcZcIslBgUzDYSwaQ1kOk0Rjnteu0ma8c3i2tv7Gph1KDVOwktMw0TUEcTkNUxDLjRPQoKyjnL+m
oHc0IZWi/RX0SPyNtatof7GcVbMGi9JTWIO5XIuCXp2Cr4nnsqEhDrx+6ZUWKtHB0y1F51KgL/fK
kGMm5zJWy5plF6xyIowY6aQbDmWBB4tUgBV54NS187ZrrNbpoR/KocJ5Dtuswkp9SnJWfXDRlpeX
Njc3j2/as/nwOyNnb73z4KG32hZ//CvaE8+2KuObKq6OIuuhIllIGbPBk8L8YdcMrqsET1Qkq8bC
kH2F9dGtMoT1SjnG1TVa46iGe3/7dp92xWstVL1sVLkwlLwkWUJj7+jZ5/E6pq4RTYSVx/W4sBjA
0HLhQjJl+ZKY76mJ2UpMpjImLlPDYAg3ICQZk05mwU1vkm4SLtPnaKBgoz5l+gkj94//v1f42jWP
y2rQnP4r+Dga/VeQLKT/SLm4/iuI1bNmNinM06Z0khH0KCuiYiSHGpkcl6oSUkWvXjV5d2+/lK1L
Gxqe1ppuWe0yv/2Ogy1U7VVUCTmUasHY+VPjrv/0uW1/YIX/Bgz3qH86oGmPPCyjLKHUd68KOyah
73kSFttzNhgSObDwhj7W0xWFJ6c/gMACOfCWZanZqI8DL02HUQ3eHWsvndTYXWr8yZ/e3PccK5ib
HbH3zm7pjSJJBoNUzV2dIulsO829H/mr+bNnr2YFk2MWNJdXvz1jmPa80baDUFbX8dQsUS6LiPWQ
JXMxCg2hHKRqL8Y3feHJK3q0666kKpx47YWKl3qZG29efcOu9vsf15rj+v0v+6h+H9WmRZstVMzU
vzatKa5Ne+KqETe/dMahb/z177sW97KNO2M3yB0XCEXcKtNWDQJyloeCxsCWB8Ijs5oS14JH7tDV
AKnxCEcXIjhScKFe4JH1jFTVjmBaQSynqrjOBkUrchXcKoL1qeB+7cLp7yS71xq0zd3DReVudneU
ko+6+HvJVi1WwbKle9sp2pd/gna3oJhmVCWi4qV+e6J+eNwN77qb5nY2XTNqKtPUP+7c1fFI09L1
aw+9/f7Oj5au/kFpwSP/UXv0wAnkXqBo96FywOqyF4hVkR554p7nvHGHWFlZX+n27ZeP2TKPIcjd
P20jzD7HCN0axJMHb7iVjPJaWURS9bEKCJhBBpFUk0kjkgqOBsFJDo6coas+KwZH7Fg4FRc5OBLx
NTr4x+FIQaxqsBMF6/JwpCBYx41lw6cs/9YwrX1hw3VKLFIxURcsSrbZBRvY9q8vl5Eli/edOG4V
Ruq27+Rw033PdGx7O73D+D+3kVvAzGoc1SVCmJQfjxmzadba9/b/uKM0YXfnjVfe/KGJnx3T0qi9
+z8oGzZGnqKSiMPGeEtgBnlU/SzkUXHgOToSoXO0JDhwDYJEDrjsoStfUwMXcpzMwFNzUZcQAFeF
N05du47tPTRGd+11vzHt287oZu2lh+TuaQx/0eAqWCpqjYUZ8FOQy80VNuhQqMzzq/BUvxMt/r5t
8c2zVr+3f39H6Smt8Zp3ri/tHj91d+dw7bodo9SWQdGhwvqJ0pHZiEfRoaoS8RgEiZxmWEMXBxKa
UVpYGqlNv0KeRJHTDAUX9dCM5JSYMVGQtuf/kLUsXBkUXFRNi5OlCrHEFKUH2gBkuC2JCrVzrqmC
XgHXNJsmMxS+aX32Qa888vSDjzWyCEecJruwhdohzqdewUpdpv67W2d1brqhobGlfHCY5uwcdi4x
IFa0Tg3pgMTbgN89flxPtOcOfCZwmLQHtrUgF05wxPd/OaHC6q9LpIVN0b079yclk5VINz7xSitl
UUZFASp26nfAACvPu79BW3eBPEwqPyiKU8PqMyjJnmFe9fbaK8PVo6Hgo65nCo3pb9Ru/4emr+bh
wHbsQM1EDg7eeePQCw/979dffJOiFNg1UAIaQAno5X1V7ngoJyhL6ZWf/x7+CIailFKNDCFKyFmM
IiEqSjlnETr10+/8Ev5Q7xBbvlmFWI4t3jvEFs4usaCuilJuaYDeiT80g7gCix1ypaKXS+themmS
aCqDqrpWfSoRmdCvIqU5Mju+vgtGnwiCRPVgR82NY7DVpjCZtFThUjKzisLkpo+rnvhTqrLixMCc
YAENWNZhqJSqXJQS0ABKiKecKiso5YZq01n/Df6o7DBLzajI5BQQhvurH978j/adSAFz2lyU2DdP
uw2IcXpKbS46VLyDqI94B12kzQpKOe3DFWTwh+Q9p9CDJIlEI6fQRz2hoVdFLnJzwGUV5oBE1Fit
a5gDlbjGml20d0AG9Q6f2WVW0Z+6HAVyz3tPrX3uzpFG6dbHTvrhT5u0KTuaNikhQXFw5iAgoSil
HCQgoeSQoKCUE0ouQTDvoIdpjc4WX6pIUgshMPfs91/kXCqVumhnc0qN1IUrtYISJVD06EfVZ4UZ
AvzjqEXpbwQJg2MoBwNFyQwAAwoyORjYOm8n9CvNE/aU7SpjnZMCDgMwSGC4kLZLDAY1DFU1MFCQ
qSMYXP3Qw03/uPrAG2sevOPlE24r/a22cVrrdCUmKA5UHQQmFKWUwwRcehFhgoISNXUABfAH0lBt
iVfQy8kVCAGQhP8HAVOiQdFuDowGCkrFlS/a3lSYDIzTl6jddzEUFB10Lt/AEP9TYkJRttKDhNgK
2SnghdkC1eXjBMRAHJSwUINscezkEqaEhRomEXUTx+HMWpSHqyFp9/MkzeDVMAcNioNzBwENRSkN
DA0KSgpU53+IXrY2VEWvLsXOzy9ZN+3xSnNzc6Xnusde3PPpne/cv+rGRm3usy2UicbRpehIDexA
KChR1j4IOodSuH5g1VNKiCg6+BkHQgkRCnoDQATqKYeIoj3l0gVAASYfN/zyKYwYJRQk63Lc/qt3
/93GjeP/pmthzx+7Sz++64W9U15tmnvSQm3miSNuVOJDbbpYDR+KUuKDpNDqCB8UZxFTEbW0YOXw
oSgloMFnUOlOKChR7gRIPVDiII+sBwwRRhWSddkr9c4b597x38/8L1M+Ofek333zd1eFTb/a2KL1
hiMoe40DRNGhygFELl6ooERpMwcIuLjt4oeUvoTq0OwafYmiZAYAhaKCAJOPsYq012JQGBxn2AJx
q8hTbtzBCIW/HFs5aCgqEQNDQ1FKnC0UzMRbQhw2iUUPIAYafNnhfaSDvlyzFSQHGP1cGkBBRmGK
IEHNmQ4KSnUxHdy3fn3XNRe99NIHJ0x92Z70bPDCGnPJfb72jafb1KZD0Z4N7JgUHer0AOFzF4Iq
M0blSUAL0z5cLnhZVKLUwUt8VnBYZcDqtMi/8sam20Yae3/ZvXLu2w+femB9g9b/l6QfHoZeDbPH
F1PkoOZg6mgVxTH8WsSJB9lJKI4BqujUcYDifyANaOpQLbLHKKqOniYki5O4sMiv9obET8/FpQUl
1/B0frIG+/Ve9nNvDezn3tod19Z9xy61R79LmfyYl6GbRhB4To2XgR6ErmUOnkDmMqQe21aQvmSt
8t9Yo5/X5zJ0/i1araEx33JdwavpYrbR75lV/4VCy2O/Z8hqP4gfkh7Sn1UHQQ11j3EimEqAoRT4
usdOR0r9UOHgf0bbVbcUQr9xUzPKM9lvmht69PvjbZV2eGDYvlMeVml3dN/zg6DcyH6W0bUcvzyS
/dqt5bLBH1YBns3As8pNcNPX7dCwyjOXsl979L0gtMrDK6buOYbjlkdV2n3dAEpe+Xj23AWltcsj
gIAdmJZbHg0EQt10oYEUVcaK44TlD1egO35oh+W/gDehx67n0G/+B2gT+LQdaNNlv2AK3LfJx+gy
5sm33fIJ8JFhhoYDLInnLRVPh24Cnx+RXUItJTzbZsyJb5rAaLul+4ZnezBm7EcrgUHDxGQRB8lY
hpkOgOTajscYhAYcDy5hJB3dsHwfv5kMte+Y8VCbYeqrE6EHlgsLTjKVrmdCo+wXNm0jQM2nes3H
1w+h29GPIPrsh3sZxEa42STmDDXEB53NLmLvJGg9MIPAxLM/RpKXLKOPTqzAYxg9k41TIlOx9Nkp
Rk9m02u6oVs+pQLvgy77qV+er/X34C1LrTKO4zKsQOrZIH5HNNCt0PLQj4964qOA+ihi8MLW/wef
6fXkDQplbmRzdHJlYW0NCmVuZG9iag0KNyAwIG9iag0KMTA4ODINCmVuZG9iag0KOCAwIG9iag0K
PDwNCi9PUE0gMQ0KL1R5cGUgL0V4dEdTdGF0ZQ0KPj4NCmVuZG9iag0KOSAwIG9iag0KWyAvSW5k
ZXhlZCAvRGV2aWNlR3JheSAyNTUgPDAwZmZmMWRjZDhlYWUwZGRkNGQ3ZjdlM2RmZWRlMmQ1ZTll
NGRlZjBkNmUxZjlkOWY0ZTdmZGYyZTVmYmYzZmNmNWU4ZGJmNmVmZjhmYWRhZWJlY2ZlZTZlZWQy
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwPl0NCmVuZG9iag0KMTAgMCBvYmoNCjw8DQovQml0c1BlckNv
bXBvbmVudCA4DQovQ29sb3JTcGFjZSA5IDAgUg0KL0ZpbHRlciAvRmxhdGVEZWNvZGUNCi9IZWln
aHQgMjY5DQovTGVuZ3RoIDQ2NjQNCi9TdWJ0eXBlIC9JbWFnZQ0KL1dpZHRoIDQ0OA0KPj4NCnN0
cmVhbQ0KeJztXel64roS/EiIGWVISIizr2Rf5r7/611myQyhGpddSLLN6fpzzgRLllR2q0vdkrcG
AraHbQLbs1MIGGE939rsVtiF9nxnfRjvjfcVAgeTFju6kfyFA2jN3pixdzgYFMV0RyHwqGytqxvI
X9jGxhwT+sbTn1f96smJwmDRFoMbx184PYOmnE9J86dHg0/+zL5wXJyGVrq7afwFnMIuGXt/p73P
f18pDO60QuCG8XeK7aBtH8Ol4/GWwuC4BQY3ir9v19AKajpHNxbV42OFwNuQncEN4q9E3/GOms7Z
4uWLv0zPFQZnuRncGP6C0YQRY+/46wu79OudwuB93m5vDH8P0AAq2Iu9pRJAr0LgIKuU2Az+AnqM
XLCjpwrXaHL+MeOCzCbwZwn2fUbf1Bh447LtJ4XB42yz4AbwF3Ce4l6nKRBqE03x/JKJwf7zh2aQ
e52H9qivuPy7wuAsD4F9588Q7MxyLgj2evwVxaXC4CgHg/3mb3ILtz2nE99qMlYzLgWWLjKIwT7z
Zwj2Myr5qmR5FesYkqqB1+QE9pc/S7BTzXCMK2z1+JsziAqzBlL7Mb3lzwgTUc1QvFUPdnVhUc6n
JbCn/BlhoiPWxnHBhpr6rZIRTSrne8lfuIe7vUuCfRlXjMFtzKupgYRyHm/Wef5CiTPRgSbYAScs
0WK1+KjCbrJpEO/Vdf6Mtc4H6nV+1B7qA9rXFeK/GueJRgPv1HH+At6JC/b3JkNNc500OZ/mFcT7
dJq/Ev3/KzrxNU2GeKevs5YnmkLO4106zN8E/b8bmlqmmLsftNZXodbBa/zQIN6ks/wFw4McM1t3
jCtstfCdvdUjyRONviaKt+gof+EUzeAhdRal1+QXLtgrWEhy/iLyK4h36CZ/imAvtGnqE9yIzqRq
ozKI9XeRv2C0kwp2IyrfENw1koxoEdGIYu0d5C9gEsMOfTlusEmNcVLU2jfRFBHlPFbeOf5KFN8P
24y9+oJ9AWE5IW0wmNEpVsoT/Yg1OFh1x/gLSoS9kLzOcn4z1JfHjMBCSraPtN8FK+4WfyWaTu51
4mtUA79npdLwedjLPpYSZN7LGAxivV3ir5xBtTdU8knrk0d/F0cmR/hjGjm/F8ETxVq7w58ZYWfs
jS+UobxffBdK/J2+89q2z/V3LGGdXeEvDPFFoMlJYxJht7G/PIwvcMktHQLJE71el0Cssiv8GYKd
+i2SYL80xjBgatRbs71MdfG2HoNYYSf4C0aYiAp2aePzV9P5rwEv6IkyIzrWUpym6zCI1XWBP8Pr
pIK9ZoR9CR8rfYiA6TInfPZV2nCyhpbA2trnzxDsuywkpwn23crUovJH88HR5PyhPFZYV9v8WbuJ
mm7ErAn+2GPgnq8dSAt3thXnwJpa5q/EvE66jKyFiaY1WmMYUZ5lKMl5cbywnlb5C2h+tih70ngd
Des98Yacf2TmYCSpGEnOYzUt8mfkddY4OUkS7Nv17ZXhClOLMJLsuSDnsZLW+AtD9CBn1Fihj1ED
h80edZTzTyywJMr506aDhnW0xV9A3/uG70dRRums+WOOiVOvaQJLs4ZGFGtohz8rwk5zoaVnXErE
tOQ8W08YT6UDSJrJeSzfCn+TfIJddNQDeklczkvreU9N8kSxeAv8lWhqntbaiLkSD2vsBZo8QnXU
iGqnOH3U9I2HneBPE+xSvKb+uNQdLS7ntW2feoty8xdQsB+y26UT7KStOOOmSravaSiwYF7+AkbL
j2jSl+R11hXs1SjRiFI5P5XyOfZqMYjlcvJnCXaauT5ttJvoEw0Ee3WTjeg8lfPbyeQ8lsrIXxAE
+1QS7OcRk54NI/pATYYUWHrigSUslI8/XBveTbM2vI7XaWIGt+ByXjqUmaodLJKNPyzC9JRoOuPv
nAz3mGBKV9S080SJ3ccCefiboP/P97BjKKAGvifZ91qiIXhOEyg5qZTzeH0O/gzBTiPsmgF6iJIl
a2GCu6j5pgzpPNHzii7g1en5swQ7X6mWtvpE0QyrYHii+2ygptJ5oqvDEnhtev7wwaWaoZAEe+pj
VA1P9JYm20ty/n1VT/DSxPwFFN+XrHbN+35M+vL96Q1K80dqRKXo/JvtQ+OFSfkLGAqtIdiV/uY5
ftNMVD2kpzhJct7c9omXJeQvlGg6X6nXiStWNdA0DqrDiDtTOV/Qo9gsnBlyHq9Kx5+xh52HiaTd
RE9ZP8lnJNuf0xGLJOfxmmT8Ge4arXcqbcTMQ9s/hHvMoaIragXGXWpg+RXEKxLxZ6TE86OOOyTY
q2HI+WtqWiQ5f/1VzuMFSfiz9rDTsItkOs/yf0Pqdw/xdaI7lrTA0pepHX9OwJ+0EbNoJcK+BibY
Gr5lSurkQrI9/hidvzDEkA9PiZ8pHWvDdP6DJedrfzuyEa7/voL4W2z+FMGunU0VJ8K+BkJAab6X
Zk307Q+D+Etc/ix9SwW7dnJSHsFeDWt9gu6dnz4r3f0dnce/x+QvBNxMxWd1yeuctfkV9gUocl5b
H/wl5/HPEfmzcl7p+q7kdT639wV2QMAFow82ftp0f5iYP/wjrWgs2ZIOWM4FhBdDzrN+a9s+jcOp
YvH3P0xc/aAzgbQ0367XaaFEI8IDS5LhQcTiD3BHNYPUg5uWBHs1Jvg6UU90JMn5ZaTij5/dsK6W
7RakE1CkwNJXpOGPn8MofZvmsKvs/QTKIJripAWWviAFf5dp2n3WNkMEhpxPlOK0eIf4/PHD3KWW
xkqJT4fwggmrXM5L88hfROePCnYtrzNfhH0dGDHrO750r4zHJyLz95wmr/O6I8stHME4RpENp+YM
/EZc/uhXFMQwUY9gnQBNwxKFlGz/EzH54xF26UE7bpuShjDWES/SmKVBTP74UcdSBsFl22EiAZac
p6c4aXI+Gn/85CRprbMLYSIBShxN2m4Vi797UkTbw37VC6/TBMr5B/7lwuYjlIk/KeT1kPbdmyTF
t8kMB3ub4L7xuaax+HupbJfC3mD4Le0IS43qGpLFHxxZ4Pz1G85fv+H89RvOX7/h/PUbzl+/4fz1
G85fv+H89RvOX7/h/PUbzl+/4fz1G85fv+H89RvOX7/xH+ZvugngW00stN3qKJB67nA4HA6Hw+Fw
OBwOh8PhcDgcDofD4XA4HA6Hw+FwOBwOh8PhcDgcDofD4XA4HA6Hw+FwOBwOh8PhcDgcDofD4XA4
HA6Hw+FwOBwOh8PhcKzA3iZgX+n5+EfbzY6Bts+/j4L/8PcDNgLOX7/h/PUbzl+/4fz1G85fv+H8
9RvOX7/h/PUbzl+/4fz1G85fv+H89RvOX7/h/PUbzl+/4fz1G/9h/oZJEQ6UNn1Uf88dC2Tib7dg
H5ofY6GXkHaIU+JUIG+wxQYJi2R7/3ZY24pDKHPZVwJLYYAGg+9siLaNYc3F32DAXsFxcQZl9su2
qRAweVSG53VKRn26ZZTKOf/dThmD+1iod0Y0HCtj8zRi7F2Z5fL6L/wZe4Uye6FPDIbhtTIwbFyK
41u7YG7/k9r46ROUKfpDYJCySq+oc/e2qmh2/XDLDIVlRHsyCwZpYC4pe+jZ/UUL+u+RGtEdKPPQ
AwbDqWQ6qVs3raq2Ff1+yBgcnUCZq64zGM6VoZjRlw89gkW0s/7ycMweOkPO33d6GjS0GQc1nQVz
ZttaPztn9xh/QJm97hI4kQZhnzpztIr21j/pK1jcYJluMlgeKQOwQ2cRS7AvV9Iaf4PbbXKb8Xcs
NOweg6WxLMlxQv1wNEAGYvFX4eKuxh71RFFOPXaMwHD6rHSdsneMLtxLwHpi8fetXLFAUA06A4xw
dMZdYlALE3HBjl7nbH43rCkaf2btHLd85QgLdYbAwB0MA1vj5uvAT7/WgbGumPyFWhZ7GW/UiOIj
fjZpm7mfCCGJzRlPL7DM70cWK4vJ3zCUu0qHDqkb3Uk5H2ZKZ2fKnP/5uGJ1Ufmb9+le6dMDXUNC
Of/espwPkmB/oBOf4cz+6yj+Fpm/eb8Mp5/jnPZrBmXeWuHtD7QIO9O8lmBffE7x1+j8DYend0rX
6JxuyPnWAktahJ0LdlwHeP3SRaPO+PyJXtnFiDFoaMxWYrulFGFXBPv7Uv+w1hT8zXtYvWi+Aj9Y
D0c4tW9l92PCC3pTNcDtC/p+0+WnE6tNw9/cwqAPXAM8Oo+xsMxyPth5KATUxS4w5nmAHcOKU/En
ZkCe0HsbgaUctP2BGGGnnUKv89lK3MKq0/EneqJ0kh+jnL/JJOdDmciqvEMZO3HSGK50/M37+5Ci
u+MpzhRXOYxokGZ1+kAagv1oxQNp1J6SP1nkMgbRAbxILue1pYkTak4MK7XSJ8NL0/KnronyrBA0
oonlvBG7qQG67WOES6jbq59EvEFq/uaQ1kTpY1ugba7o+LqYrEzArMIBnfhQsB9URajxFhn403y2
Cyp3DTmfKDqfKCXe6MFFdQ/wJhn4yynnLxN4ouFUsiB0Tf4Yq2ULgniXLPwNh9+kSBlVvaOVkbKI
kGZwGmEvcAbfoU3H+2Tibzh8UUbhjjYluZyXliFuaLNRsL/X2GmFd8rGnyrnhcDSZbw1Uc3r5Bsx
UbAf12m0MT7Z+JvPI1Jgicd20RONtO2zlLxOnhDyA8rUXIbHm2XkT5Xzu1TO45sdIzqv+c0nNKvV
8Jvrel1YMit/8zHBZfYa4DoKnYFXmbfPpkq7iY7Z2I2x2lHtNuH9MvM3HxbJGafe3Bi3fa71Cmqm
k64bGWudRphoJfCO2fkTo/PXVAxb64gqg8Fwazl26f5+bONto/39eM/8/M2fbcmI/hDcAi2wJAp2
HmFfe2s43rQN/uYMppHz2yjnvwueaKIl9xmUabyXA2/bDn/DICXbn9HlfCN78rTZIGkt44Idl1Df
m6/W4o1b4m8OaccSf8rx5TlqMkwlKusa4JbBiLALkzPeuT3+wiket1QDSh5X7VlGCxPxbXCYLroq
wl4NvHd7/Kme6Ing5dU7xUnzOp+VQJfoGWNFbfKneqJczqPKeuWZvgHdwxqgM3KB6aKyMsXbt8vf
fNCk3at0lWOK1ZJVDi05iQt2fEJ3xKEadpE/cU2UGy3DiFZMOakSrQzBvs6yEDahdf5UI6rsnb9Z
IQbDqWQ6eWQETWetMNFKYBs6wN98/CQ5T6NsRm6XKeeDJGXoLGzkyK27WwNb0Qn+5i+AMoJUzlvb
PtETlTIDzviKOhZaO6aFVXaDvzmkbSE8y2QGZd6+juIkjWAfYbURditiQzrDX6rovJEnujCQpXRe
5x7NjMOldE2wLwGb0hn+5gxq5xgp8e4/YlAT7DyUZdiSOJmpWG+H+JvbMkmDvVINhm/DTyMqep08
MxwX8GJtzsDWdIq/+ZhKsxE9FmBkJC1o53XygxYSpHL8BbanY/wNg+QN8l0+xqHMAu6EnVHXEU/Q
xxZ1jT/1RDG+y04KLXwF35mIgv0wZj640e/O8TcMpZT5xXe5SqsEC0NFX3Kcvrfi7scwGtU9/tTV
SEXO18eTIthjDspP4B06yZ+6pHVFh1iyzT/BjzrG3Bs4/mNtYLs6yt/cj0mUAyZtyaeL5YZgf0xw
Mg22rKv8qXKeB5aaL9Td0pOhjDqTnAyFt+kuf3M5Ly1u0W8sjRoeXsbfaVz5S3SoEDauy/ypx/Lz
U/4aHOPywQbDmFP5RkwR2Lxu8ycGd3Z5UkrNmugGUsOnTXiUCTaw6/yJB5AcUK1WS85zTYl5NocJ
T9TDFnaePzXFiZ8yTavgGzEx8yPtUV695E/cSHnD/A5S/llZU018mmU/+VO/7UViBdWFeUwDzUJ8
wb6EvvI3DKfSoamVYrCqoLKHPcPntXrLX4rk9tWlrpUvM+U4yrnH/A2HJT7yNfC6ksGVRZQPnef5
Mlqv+VPl/CoRsOLyDyoecTJ+y8Je7/kbDqUzOG9sRsxr75QgVLZPifSeP1XOW6RYF/K8TowtK1u0
RfSfP9UTNV4rvIgfkYAR9rOcHzDYAP5UOY8J78tX8LxOQ7Dn/RDaRvA3Z1DKRVp2TJZ+3me9NtY6
pzl7PdwY/tQ10a/m8es4CPlrb9m/3rMx/KnJ9osmcuHvfK1T3VMfF5vDnxqdX1gY+/dHLtgxwt7K
p8w3iT/1G3x/5fznH/hGzDXPlImHzeJPPCvp82tEv/9FBXuEM52iYcP4G4pnlf0OLP36X35yEmZt
p4ywV2Pz+FvjrMD5fx6Z5DMOQWjz29ebx58aWLqbjge3yiEkrXzx8xObyJ+6Cfrj/9Z3eEQNCmVu
ZHN0cmVhbQ0KZW5kb2JqDQoxMSAwIG9iag0KWyAvSW5kZXhlZCAvRGV2aWNlR3JheSAyNTUgPDAw
ZmZmZWY2ZjBlZGVlZjRmYWU4ZTRlMWUwZGZlY2Y5ZmRlN2RkZTNlYWZiZTJlNmU1ZWZlOWViZjNm
MWY1ZjJkZWY3ZjhmY2RjZGJkYWQ5ZDhkNmQ1ZDdkM2QyZDRkMWQwY2YwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAw
MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwPl0N
CmVuZG9iag0KMTIgMCBvYmoNCjw8DQovQml0c1BlckNvbXBvbmVudCA4DQovQ29sb3JTcGFjZSAx
MSAwIFINCi9GaWx0ZXIgL0ZsYXRlRGVjb2RlDQovSGVpZ2h0IDk5NA0KL0xlbmd0aCA2MDkwOQ0K
L1N1YnR5cGUgL0ltYWdlDQovV2lkdGggOTQ5DQo+Pg0Kc3RyZWFtDQp4nOydh3biyBKGz4AkUAQF
lIUkskje+/4vd7u6lSWCDcbjob7dszvjJIH5qeqKf/4gCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIg
CIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIg
CIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIgCIIg
CIIgCIIgCIIgCIIgCPIWDIYczwuj8U/fB4Ig98CJkqwoKqBI2uSnbwdBkKtMdVkh/1DIH1TDMK3Z
T98UgiCXmOiybMqybdoA/JfoVjWc4U/fGIIgvXAuUSmoFZDof4lwFUVxhZ++NQRBevBMmWiWqlVy
JReQJJP8Kyu2gD4ygvx1WESb1MBKkus4ui6Kok4g8jVNVdbRRUaQvwxLzR1jolhR9K1ACwi+74uO
45i2qoY/fYcIgtQIJcWkkpWIkfU1XuAiLoo4T9ACyyIWV5IUw/npm0QQpESUZdmE46zr6JbmReFo
PpzPR2EccQJPZOs7rqkkNlZbIMhfwkihKR7TdXU/EKLRMF0sFulwzkRLjK0v6q4tK3iwRZC/g4kk
y7YtSRLxjHkuHKaT8WSySImlpQ4y85AdqJPS05++VwRBCLpsQqrHhdMsN0rH49kMNEvsrAd2lhha
YmnBQVYN+6fvFUGQP388RbZpoke0+Gg+mU2XszExszGXSxY0KxL/2DVVxZB++m4RBPFkGaLGxDfW
vDCdTQfT2WIecoLGEj4sW6sTSyuZcqKspOVP3zCCvDmRCaK1XUfUouFkOhgsJ2nI8QEcYwluCTnz
2raarNDWIsiPMnNosseVdI0bjqd//kwn81gIoKSC6hTqGBlQiCzLapLwP33PCPLWiLSrR3J13xvN
Bn/+DMbzSLDgBMt0Wse2bUVNDJv76ZtGkDdmoMg0CuX4Wrggmv0zGxLXWIQDbCnUumhlotqVGf/0
bSPI+6KpoFnTJQfaBfGN/0zTmPd1t9BoB+ivTdbGT982grwtY0UBSyqJGpeCnR1MYl50pF69Us3C
IJpEXWO6FkF+CF+lmnUCbk4zOeOQF93LmqWiVRLVWLs/fecI8qYQFRL32NXzyYvLIWcRO3tDtMTU
GgqGkBHkJ5iDZiVJt6IF/fsEDO2l4yxolvnHapKsTKyxQJAfwFJk4h67Ps+c4+ncs5wrdrYQLZHt
ytB++uYR5A2ZSgrN0QYca5RdxLx4zTmmqoXBqkqSGCo6yAjycjwVROuK3pz9feT57jXJNkS7kr2f
vXsEeT8WjgpttHoQslGLsyjQpauapaEoGotSVWO1+eH7R5C3YyRBktYV+ZT9fSFY9RStfFW1YGv1
H719BHk/eFpZ4VgcM7TTuSZW3rFc0RGtrCrUQU5w+gyCvBSReseiNmJ/nYWWXhpa+YpoFbuwte7g
Zx8BgrwXoaRCltbyUvb3BddvaFvipX+CQy0xtSuMICPICwlsIlrJ0fIw1J+hoLt9hrZtcYlki7qo
VYKbMBHkdbi0HEosDO0gDBwzD0D1irUVi4IAsrFysTAKQV6GrSiy7VpRbiyXUXDB0F4LICdYGIUg
L0NVFdl0tFFuK2ee3xuGuixaMLVr3DqAIK9inCjkSKsLRdpmIohSkZy9LVpmag3DSMQffRQI8kaE
RLTkSMsVoaRU0y/Eji+KljrIq+mPPgwEeR8EVVFs149z73g6z+NQd4oWVKskxNhusB8eQV6Dpaqy
7QbzvD5iGVpuETy+S7Rs8AzxkDfRzz4QBHkXdCJaU9eKI+0szjt85LtSPnLeWEtEuzZ/9HEgyNvg
QPBYFIoj7TjypV7JXkbJ66IMnIOMIK/ABdH6QpGxmXCilHvHt8RafEEh2g0uCkGQV2AS0UoWV1Q0
LbxCtPca2jKAbKzQ1CLIC5BVxZasqOjTGQr6J0UL4WNQrWFspMWTb27KwWYSWObniMHoyT8cQX4n
A5WI1g3C4q9zQTe72Z6bqs1ztc90kGPflaHCEtoSYKEBuYhsBk+8AIL8TsYJiLbopf0zGPHOZ0Vb
Ochr9VnzosYwpqq6AOwhUYhsFdnhsF4SeXMWRLSmwxeinYbahR6fW6JNaN+A/JSbmkV0iV87yQTW
NpHFGFvukbeGiFYmos3nMP5Z5qK9N+VTVkXBoTZZrTZPaKwd8ya9frmmL9+1Kdtge4lynWcfnRHk
NzE0QLRlu8AsDJy8tOJ+O1s1+6weX8k11qmBLeQqSa7juo6us+XWJlvY5zx6FQT5vVDRVj0+szhw
Py1apWobWK8f21k785W6ZolcHV0Ufd+yLN8XYS09sbqKvJLnt38WgvybENEqNdGOvyBaZmpVlqvd
PGJq566tmqad21iiV98KNF7wPI7gCbwWWD4xuZIpJ4n1jEePIL8QZmm9UrSR9XnRyuWpljjIq68f
OGNy6UKyxCMW/YD3uDgczYeE+SiMOaJby3fIqVtRFcz+IG9Kaigg2jT/6ySypC+Klql2vf5yN3wo
yaZsS8wr1v1AE6Jwni4m49lsNh5PFsN5GHECUa3uurCT5DFHHEF+K4umpf2qaOmSaUU1kvVaTb90
I8tAhh25pu1SKxsIHFHseJmndwbT5WyREtV6fOD7DjHJauLijHTkLRk3A1EL7mvucRGKSlbrjfOF
yYxT3qSSpVZWtDQvHk6W9XzsIBctRw625Fxr2rJqKM94AhDkt7FMniZaJUmIqV19pSxqSROzcJSV
XHKU9eL5pDm9ZrAcF+4xsbS6K9mykqwxGIW8JUpSz9MuOF/qmTRzr6mFU+1qY6efvIdQUWgASpKI
Y6xxo8Ws8enBjCqW41j8WNQd1wTRGmvsIUDeERnKGJ8nWsjVrj4ZiwolmUaNJVf3AyFuSXY6WwxH
ccQUC5LVIVkLNRbJBkdAIu+ISUVb1CqkuXv8JdEWbbXr5FN3wJlyXkqh+zw3mjSOsrPJcB5zHq9p
UF0BhVFQGWXatgKWNsEaC+QNkb5BtNvPZGMCm9pZyXVEYmaHjSaeWR4wpoIFuboSFCLbtJgRruQ/
74lAkN+Cm9S7fJ4i2tXm/mafhSjbEg1BETMbD+ue8XIyjKlgdVArkysINtcsBL22anjxJyPIv4pO
ROtqYe6TPsfSrnf3jlOdmbIMhYuuK1p8XPeMl4tR7GkWRJ3yLp/acnqZ7TUgV0JTi7wfVgJN8GGe
YVk8KNpctbs7x6nGIFlmZjVuXjOz0zQWiGJzwXZHt+aiJab2+c8IgvzlaIZqu0GxYOAZol2tV9vN
XfMlIlpsDIXGlhClVU3GdDzkeCrZrmILQ8s6AbcrDEUhb4e3UmQ3iHIrB6I17a/Itiba1Xqzucdt
jV0wtFADZQnhoqqmmA1DLxB1N4859dnZohNws8YJkMjbERmKLAVcIdpqO+2XNJtHotY75bapHTq0
cNElvrEwqn35ZE7MrH7RylZ1HPTdARfjIm/H3FBlyfLyMTGlaL9SxliJdrXd3jS1ggualWA4qjev
XOPlMGKS7Qq20mwZ8tpscUI68nZMDVWRfCHvgp1EgfOIaJM8fLzeqjdytSOFhY0dPeBqmp3NiWfs
1vzixg6hxpXgOpsd1lcg7weMY/SFlGVbJnFQDHb7sqGlFnC3uT7HSVBsWrjo+EKclsfZZRoKviM1
sjslxXG2bCgC73i34r/36UGQvw9YMSDyQ2bsxrH2FdFWmqWGFkS7S66FiCBuDKJ1fC1clNnZGXGN
QbMN02p3rlQFvNbbHWZqkfdDIqLVtTxJ+phok8LQEhO4vbb6MnTA6ZVcV+ejmmZHnNbULBVtw+iW
dpaOttlsd7jMGnk/HEWxnWD0qGhLQ8uCupvtdnvxkmNXhvQs2Nk4LT+6nAuB6LQiUC3RNt4dIA61
2z48tBVBfhuWTKsrWPh4HPJ63pv3yQ0DNSmBaLe7XXbJcR25UG9Mq42jMtUzWIS8D8u2+o6zvVda
MdHi/Ark7RBAtH7upY5HXxdtaWeJd0zs7G5/qcTQViXZdImd5Ss7O13Egk+jxvLdooXr7HZYyIi8
HSMzkSXRY5Go2Uj4tGireC7L0dIT7RZMbe+U06Wt0skyji+E5RKR2ZwLRLdZTXFVtAYMfqQG/XPN
uwjyD7B0E0XSBRaJIqIVvyLahmaZoSWi7evQW4qQn5Uk1+dHpWaXI08jx1nbvKHZumjp0Xl7OBgv
e6YQ5G9BpG3wrJBwNv+SaKtjJmgWRLsD0fakagcaKNN0HZGPSs1Oh14VgpIvSzbvFKgdaVG0yFvC
K6rp8DE91M7msBj2TtF2kjCVZkG0h3VPsZJmyjLEjUWLS4uPDRYR1ax5w8w2jrQrdqRF0SLvSGxD
+JijrXHL4f2ibVcVFudZqtnDYbftGSbO0enGki5qVX4WzrOO2870XBctC3htUbTIezInopUsj456
mQ25z4u2o1liZYloexKokcmKKsQgKhUN1cZ6ZWblK5ptH2lRtMibMnZUWfIFGhaaDSPfKc+Wt2Qr
N1puirgxSHaX7fTulYYKtbOOzsdpYWeXI8FqVy5eu1oV8qKizQ4YPUbej4GfKKaoxdCGPksjC0Qr
3ynahnOca/awPWyzzO0uB5np0CVA7KwVlT0Cy6EAuZ77NNsV7SE7YJ4WeUO8RLV1jc57WaaxpUvm
vaLt0+xuS3zjLEm719FgViqdLTMsNDsYclZeBnU1aty8WlEsSd4gsgNWRCFvyEJRbcfy5rMBiDbI
RXvL6pWWr6VZothDtpl0rrIMoJBYov2zhWanKTnP3m1nm8klFjze3ztDDkH+JQamKrtQnzQdzNJY
08sT5mcMbZGepZo99hxoNXgnMF3X58uxi9M0avrGnxLtZkMutt9d79tFkH8TBwoZ+XixnM7SUMur
K+4Tbd3Q5mHjQ3bqieimYGdNySHXKZoEBmnM645EI9V3XbC6nlFkac877KdF3pEgUUzitQ7HSyJa
XpSKI+b9drbSbJZl+6zrHI8kusuS2Nl4UXxsyGki3aVVNODdqdmad5ydt8JLnyoE+TvgEsXWyaF2
shwT0fr3i7asTlpVB9qs12N1qS5dKKooPjSONd8xq/zS3Ya9IdoVLgZB3pFZosqOL4wWs/EiFHz3
ek9ro3yRDWtiHbQ0mLvfH3pCQ55MRxw7VlQmaGcj3telG5cqL1kbd1zVQ5Ej7TmZdq+GIP8+dqJI
ohYPx5N0JFg3RFsNfqnKgDe0Sw7MbG+GNpYVqIRyLG5RFVV4jdEy141sQ7RGHveCONQep80g74mb
yKZuRfPJIh15llPlTW8Z2iooRAxtRpzj/X7VXc++kBQTNEuMeS3ZY92vWbmqmGx4x4fzGeNQyHui
GzJkasMFiDaoiemiivqyPdnufM6O3c73majItOJYKwPHfxaxVW96v6HZxttE2Uu7g/cI3DCAvCce
bOES+XiYfkK0DasHZg9844+eAiVdUaCqQtTKiVCDRaTdnAfVe8naNal3nN27VBNB/i0miWGbusbN
h8ORV6uuuNZuo3QOtId9tt8tOj+cHGhl2ZT0oOqgnYR8Ee662tVDsatr1rO0MLUiO2a4YAB5U2xD
Np3AG83noafVCguvWb2kNvUlT/bsT90j5sSB3h7JtbyyenEwqg60t1NLXdGWR9rsuL1rpyaC/HvQ
ffA+H4/mIVQ83BItNbRt5zjLzllPnxytnDAdv9qyNU2Lbry7aip6RZsfac/YmIe8K7yR2KaoceEo
5ngoU7pao1QPCRHNrneFoV13Kx2EhPbjidqoXPS+iOuTKm5Iluk23/5eeMer3NCe97g0D3lXRisV
kj5eFBLR0vzpDdE2m3ug5Hi/P+6szg9eKArUHDsBV41eDAXytvAZzXZEm3vH++Ohe0UEeRMSVbGJ
f8xFt0WrNKJQ0GxDDe35vBc7P3ZhJrRNwOLKANVyDkGoexuJctF23ymYaDe4CB55W2QVOn0Cj4s8
3qqc1z7Jyk3nmNnZbJ8dV7POj7USWgnl82UQ6s+Cs+5v/msYWqXhHcOR9tRTyYEgb4Iow/Rji/c4
DxaxXxFtNyC0ZQfaHldVMCHbA1UVpZ4nYT1De59o83eLjnd8PsndkkkEeRMiEK3ra7wnaNdEqzRr
jvNSKMjQHru9Pamtsgxt1dozie8ITvdrtlxLW3T47M9nrIdC3peplKi2pFuawINopSvucV09rB8P
+gSOPRNmxIR8Axxoy9aewUgo2/E+pdlyt0DRBwhXPe7Slz5JCPJXEagQP/YDHkTr3BJtLR7ETrTn
YzcKJdpQviiJfJmh/TOBGce2eecIqo5ok+q9Alzy07p7ikaQtyG0E8V2fMvig5qlrZTV2sRez/Zk
e+Ierzo/cZioMs3Q1jQbBbr7BTNb76VdFVna/fkDF0oj70wqGQrEea0gsETnmmir5h425hhKoY4b
r/MTnUSRTdMNuLLScDrir8W47hFtbWhFdvzALC3y1liGapuOaFmBL1aJ2oa2lKZmy/rF/fnQrUyK
oBRKckWhKulf1Pvevyza/LrknWLf7U5AkDdipEL9se77li/2N+cpjSjUutYokJmduv05DKuAbM+o
co7ZTOWvaFZu1nMwQ3tev/YZQpC/jCk51MoSUa3l65c6atsp2i0bc3zudrVOdJW41K5jcWWsaNx0
jj8ZO26XQxGf/NS3tBpB3gjHUMDUir6ou/2iVXprobJ9j3p8FRryXN8rS5amQ88qf678FdFW3jGN
fh3/6w7JQJC3wltRU+uIl0Tb1Ox6W55oV51NtLGs0lIooYocw9YelqGV5dtNtP2irZdD7Y/HQfuy
CPJejBNDkWERpdjvHiv1tEuti3Z/5Ns/aiCCLiVdi6veHhgwYz8s2lor7Xn72ucHQf4+FAO66Fxd
v3CmbTvHec3xsduIDru2ZNPxqwEzg6FQLL79dBCqlfChot1nxz0uuUTeHt1IFCJax3F63eN2LRSL
Qu33WacsaaKo5AdJvlCWL/5JOctxe94IPi3adb5463zc4ZEWeXs0Q1XhVOteFG0rVUpjuFl3/qKe
2DB+MYjLA+0y1i7kfu+TbNc7Ph5X2OGDvD2LVaIotkRUS0TbcWV70j07qIVape2fE9P6Rcf3ys+A
c3xr2ch9hpb1KBD7fj7jjksE+WMmtIpJ6hNt1zkGe3c4bzpb6+Zywsoq5qVzvOBqvT1fFm0VO4aT
dNYtnESQt8MyWI0/wWxVQXQbBfJ0T6e5Z2oRHxumYNTKKkLNuXvMca9oq5kVRSvt6dDJMyHI+zFa
J9CgZ/aLtmfn+/647nTRetCQZzqWUIpqOvfypV5Ugl8tYWwMmjn3xKwR5A1RQbS2Sbkg2ppzDI0C
nT6bMUyYsSWrXlbhFWUV7Od9WbRFBy9o9tDt30WQN8RUE5qsqVlau9fQFoOOk06jQEA16/DVrq1Z
rYn2K/keuVF3TMNQ2fmEcxgRBAhUQ4V9AJLZJ9rGXKjD4XDeHzuNAiE1tK7Ilc7xYCiID0SO5eJI
W7a/E9Gez/+p3ek2CPKGDE1DpaptilaRK+e4nDFDfNSe+f4qm1bBD8uRqSn3SLanYWjXVVfeuRO0
RpD3xEoSaM9pIHdOlfmk4/1+2v5+IaGLe4KojBwv43u28N0j2lUVhjqetmhoEYQSKYaqtFQr13Mu
VeQ4O2edEU0DW4ZCSNGr0jGpYPVMnPqsaBvt78Q7/sBWWgRhTFxaytgSbe+OvH3WLdiHLlrT1YNq
WsUith42tM3YMRVt9zCNIO+KZnT840K0TDbrbdH63p3lFqt02Zbllb7rLOQhcvy1muO6Zot5xyw7
/LF57bOCIH8xKU3Vym3RticdQ7rH7XyzQ/NFIh+Ws8lTzvrkgryLoq23v39gVx6ClEjgHyuNfc8s
ElQ2CmwPbFB4JwrlKVBOpQdhmaJNucD5smbb5ZPFFMb9+fQfescIUlL3j+VKtLW+OIjfHs5Zx9Au
dBV6hKxa53vIf21xT8vQqklzONQxe+lTgiB/NwsiWqj4N+1i/FphaI166/tx1Zk57NMtILpQi0J5
1qW5jp8SbXMK4/7Ys84AQd4Ys0+0lX9KT5XZ/tCJQvG0UaDuHI/rc44fNrR5CSMYWpxZgSB19LVa
pGoL4TQ6Bdi+LaPzfURfMGKGT8uPzGv1i1+SbG+vABFt9+II8s54K3KoBdXKRdlx80QLoj2fwva3
jeAkLLlBVDrHY4hCmY9rtj2F8dizoA9B3hqFhqLkqimPGdp1EYWCqWrdZlaJDTrmyqPuchSIkv3F
tvdLhpa8X5zP2ahzdQR5axwDugYAJtqyiLAwtPvzKm5/U5RAR56uzWuNAiKdmfrpGcdd0SbliRam
MJ4wDIUgTcIVTdWWuqlnXOio46wbCJrbELvSa5t7FlHA5hx/vuldbuVo86uvd3Sg2ylD7xhBWqjQ
6qM0HVRq6jZ5AaPZGV5qQS2Ua1VrLZdzwS9npj7F0G7yfsDTunOeRpB3R1Zp1kepdMN6WXc0dLzP
ujvyZqYK4yq0uFYLZTmPZXvkZqPCZkPMPIShPszXPhsI8guwFGpqwdgqjXzPbrcjzvGpW/ir0e4e
saqFmj5eCyW3m/K20A54Pu7R0CJIm7EJVVFUtjVDW05zO3SmM0VE30ozCkU0K+WlkF+tq+jEjvdQ
DfWfgbvyEKSDlhhJUmm2DB0fqKHttL7PdJhO7lhcrRYq76KVHxBtlaRdQ0cg20Fy+uis6EMQBEZF
5Q5yLd9T9L5vOwMYHTj+un4VhRqEfKHZL4i26FKorl7MhtofzyfspEWQHgb+ylAgGNWYdQwn2kPP
Cp0p3Sjg1qJQE7bzPS+r+KJoa95xLtr9fn/s2nkEQf7ACq0ETrWqWj9TQh/tfn/utNH6CoSOa3Oh
pnNNzOsXPyfXOlUjrVH195yPHxiGQpA+BvaqIdpitSU50nYKGCcK3ZFnjaq6imrd1pNEWy5//zi8
9olAkF+Dtc5tbV6PRFUDnQLdNlodNu2RE205FwrWbT3YKCB3u9/Zesv/oXeMIP2khpHkNPI93QLG
CGbTmKJWViNP57VdtA+KttX9fj59zNvXRxCEYa+MQrOVqTv0DHNzFVrAWHX30Fqoh0XbbMrL+3uO
R4wdI8glxPWKGluj1kibZYeOoRspdMYMXy6QHoSaWK3beqahPe9PWXcPCYIgjHBt5NQmVpw7c/1n
OnT3uH5UnmjpXKjnirYYwng8bXCRNIJcJFlXmi0qK/Za+6s8RVbB0Jb7tpZ5uueB8eS5aMuxrdUQ
xnPXO0cQpEDcrFbJapWvyaO27tzpr4klSPfU22iHXhmF+oJU8++qtvTVdoHAXoFO7z2CICXDzXpt
rOqG9nDojHlxIHQs1QoYl3GR7pG/JtrczPZMOz6fTmhoEeQa6mpN/qGaZYfKbgFjahCj6DpaWBja
wZD3H6mFapUdl+twWSPtNn3tM4AgvwzdANFSzdLZpdlh1vkSOoGx1kY7icvW9y+JNqdlaItqKOx+
R5CrROp2A5Kl+Z7tLtt1pg1PVFmxpdpiy0E16Vj+kntcF21tmhxdK4BlxwhyC3ezoWYWTN32kK06
ve9iQgyt6wtlXcUkKvdtPSDayjtuiBbXWyLILbhku6GiBdXut3rn8zBjxqwvtoQZM09J0bY1u4ck
Le4CQZAbjM3tdkt3W0I5lJy2P6/TwVBBVcA4YXUVX+p87xPtquy9h7UCx5c+eAT5lcRUsOAc73a7
Too0pAWMojAsDO0s1PSqFurzoi2+Q6l671fF/p7zCfdII8htxsZus93s6IRytT1ObeaDoXWs2tTU
qq7iS4a2Idp6GIrufj/hHmkEuY15IIrd7ja7bea3P8fJ1NBWS/JmxWCoL5dDlaJt53vO5ER7fukj
R5BfSkA1S9iv2pX6E4fNq4hqBYzW45OO5VZ/D9Ms8Y7PyosfO4L8SmZJtoMD7XYvtD9FNEtPtFUB
YxTojzjHNdG2JlYQQ3s6bbD7HUHuwSWihRztujMgXIXed0eLq8FQT0n3yD2tAhlxjvedhBOCIH0M
d4cDtAp06ip82GxZ3wMyi2tttA9oVm5NrDiw/p4VrqRFkPtIoLnnsG1/eAqGVnKqAsY/Q0GnJ9rP
jzm+INqqkTY7Ho+dOBiCIP2Ie6LZXWfICyzcahQwzkINBkM9svW90Gx9QnluaE+7zgxIBEH6GZ+z
wz6ZtD/q0t73IK4MredLj09grOVo6420ODgVQT5BcthvOkNmLNopYHlp8YFZsfb9SaJlmi0aaU/n
TlMggiCXEHd7sy2ZpckmMFYn2lSoQsdP0WzD0P6HOVoE+QTKrtPGyitQwFibwPik3vdWf0/Z/H5M
X/qIEeSXI3bOk3M40UqOVo46ns69qvf9YUPbnlhx/OgErxEEucKwU6ivyapsuiJXjToue98f1myn
kfZMRNuZTYUgyGcITVp1XPW+/xkJvvs00SalaNnOrePpI/3BR4sg/wAQhYLlPdWJ1iuHzDynrqJq
FdjvT6fj6icfLYL8fiYKFEPp/KjYKTAYauITtuTJPRWMh/3xeNrxP/p4EeTXo7d732GF9JMKK1qt
AgcwtD2L+hAE+QQTG+oqRL7sr12OHux9rzTbrjren8/njw1OrECQh7AU1bYdi6sMbb0Y6rFZx0rH
0B5PH7jcEkEeghpaSeSrTrkRL0pPFu266sn7L8PmdwR5CF+F3vegKoYawzS3fOPWo6Jtesc0R/sf
rgJBkIcYmESaki7Mi9DxNF9H+4R9tPWePMj37KH5/Zz+5MNFkN+PoMoQOg6rITMcHZv6aOd7a/N7
uVXgP+zJQ5CHGEqtsanLERtY8dBGga5oi1aB0wmnzCDIQ/CyDYaWqxlaFjp+hmjhREt78vIB5efj
8ZT95KNFkN/PSIK973oVOh5A6PgJQah+Q7s/4cQKBHkMF5xjt1YMBRu3njTrODe09cKK0/HjJx8t
gvx+hgkNHVdDZpajQK9mHT8rR7su+mj/28s/+GgR5B9AVGRZcqxqPnnKPa1ToFq5lRdWwIkWtwog
yENMbboIRGtUHT9VtLl3vCvGuWGrAII8hAAnWsfyaqFjyzGfNBqqZWj32fH8scZWAQR5hIHDcrTV
mLd61fHTDO1msz2wyVAnNLQI8hAaHTJTqzqePGm1Za3qeF1UHe+P5/82y2u3gyDIDQYuPdF6w3IE
40jTpXx5z3MHlGf0RPvRGZGOIMhniNiJtj6wIs/RPipapVYMVe62PP63+clHiyC/n5kPxVCiVjO0
+cAK+SmFFd1WAfFHHy+C/HoiCU60zYEVrFPgUdF2m99pT96ps8YaQZDP4BBDa+paNet4LviS+QxL
2xBtUQx1PKF3jCAPYdm06pgr18SOuUB/ZkteY2DF8fjx0dk9jyDIZ4CNW82BFQE90X5LH+3+eDyi
oUWQhwhp1XFtTd448p+1VKA9NzUjmv3YWT/5cBHk9wMnWlcP5tVSAaGsOn5Us0VPXlVYcT6dsL0H
QR5iAgUUjihUhjYO8o1bz91tyZZInz62wU8+XAT5/QSKbdq6FhWG9s/Q86VnGFq5M6A8o5vfk/G1
20EQ5AYLU5FN16o1vz9pqUC127J2oj0f/9thHy2CPISfQI5WCMsC/pQXnzuwYpVXHefFUNjegyAP
MZVk2ZRELi0+MA6fs4+2Kqsoq47pEulseuVuEAS5SSgrtuQEo8rQsgHlT++j3e2yMzTSYugYQR5i
JrLdlmnxgWWoOUVhxbNEu2aFFVB1fPwYXrkbBEFuEpusVaAa55Y3vz+rjzapiqHO++PpdPjJR4sg
v5+Zo8KJVigDutNYe86A8mYYCpxj2vz+P8zRIshD6HZrQPlC8J84oJxqdkU1S+sqjufdTz5aBPkH
UGTaKlA2vy9hysyTlki3lgoczjg3FUEeZq6QE63rR7Xmd995nmhzQ1sbUK5i8zuCPIRPe/KCWk+e
wHryZPlJ7T31quPzR+b/6MNFkF/PVFZs2/FbrQImG8L4uGibze/kSPtfkv7cg0WQf4EgoePcqikz
3zCgvJwMRbzjLLx2NwiC3CK1FdOuT5mZsbmpdGDF8/bRFgPKj/8zf/LRIsg/AA8Dyh1t1G4VkL+l
j/Z42s+u3Q2CIDdxFNt0xaonbzYqWwUe1Wx+ojUafbRYdYwgjzGxFSisCDsLaeUHA1E1zZbj3GDz
O/bRIshj8KopS3rVKjAdCU6xvuchD7lniTSIFquOEeQxRtBI61hRzdDW9uR9XrPl99ROtMzQZgei
2eN/WHWMIA8xEFXZJoa29FkHcb2C8fP2tfgmpTUZ6gD9PefjcfuTjxZB/gE4UzVN16otpBUs5xkL
aVuh43yrwCnDqmMEeQzdlk3T4ct8z2Cuie4zmt9bhhY2v2fZ8aj+6KNFkH8AWZElSayt74kt/RnV
UE1DC2GoHZxocakAgjwIpxLROvV8j0cM7ePTjpVWTx71jrPjh5r+4INFkH8BCaqhRKFmaDXnGRPK
O4YWKiuyjy3maBHkMSIIHYtaXG0VEPyn7MlrFUPlZccn6ScfLIL8C4iqbUu+V05GnEK+53mLQGon
WihhPO5w1jGCPIgNZcdBLd/jFcOOnyJao9oqQER7/EBDiyAPEio2VDDWlluyGYxPHFhReMfQSZvh
rGMEeRARdm75UT3f4zxxYEVlaFllBRZDIciDzGH1e3OLNNu59aBoy3RPfqJl3vH5JPzoo0WQ388s
D0OVMxgn5XLLR+1ssxiK5nvO2ap9A8v2BxAEuUoM/T26FpejoeZ8uXPrCYaWteTlJ1oIHbfbe1J3
8gdBkE/gy7ZtNlaBBKyCUX5sNlRDtOxEC+VQdvv6wQr9ZQT5DKGrwM6tKt+z8KwHvOPym5p9tJsd
NOUdsuPGa10/lTfY8YMgn0GHMJRTrQKZzstG2kdE2znREtFm2X4vtq/vbDbKix8ygvxuVOIFO2Kt
sCKCE+2XW/Jqom1UHUN/T5ad1+3za6xuVusXP2QE+dXwRLSmHswrQ0tXgTxhtaXaDR3vz52WPDVZ
r7c4tRxB7sclxtERq1Ugkzh4Uk9e29AessN50778ZK2qxgq7axHkbhYyhKGCqMz3DMuy4wcnMHaK
oSAM1ak6DlTyhQYWIyPI3WiqIpmOMCr+DvPczKeIVm1sAmGFFbtOH60tm7Ks4txyBLkbGxbl1Va/
T2qG9iHRqvV9tCxHm+07FjVWHNeR7AQ3hCDIndA10k4wKrzjor/neb3vbEA5OMf77LxoX9+UdNFx
pKSdvEUQ5AKWSjTre7V8zyOFFQ3NdkLH2b7jBXOy7luW7ygYiUKQ+5hAGEoPyjEzA8j3PMnQsmlu
qyJ0fMj2STuzs3RNP9A0S7QxEoUg98ER71jyhbIpnc5z+xZDSzS71duXj2zJ4gVes1wFO30Q5B4m
OhFtvew49azHx8xUqy3L9h56pE3aoeOxbjuBwHmepivRix86gvxOBCIxSeRHpXecz3N7rPm9plkm
2h21tNtOL49PLq5xYRwJouy/+KEjyK9kDGukJYsrDe3Ye3zMjNJvaLN9ZxFIbMuuKITzeehZJjb6
IMgdWCasFagZ2qK/55F1tKVo8xxtYWgPafvyiWw6ATdMF/NQk0wc9oYgtzHpiPLG/p48DPXAobZd
wLjZbXeHbbZP2lePVdnV+XAyGy9GvKNor33sCPIbmSqQ77Hixv6er2+RrkSrNkS7Pex2WZZ1yiec
xHYtb7GcLsdzwZF1LIpCkFvQpjxRK/3SJTF4j6yRbhnaolWAzWA02lefUENL3zGWQ0GXXVzvgyC3
kBTZlHyuLDtecJb7cK9A29CSE+0W8j1x++puYpMTbQp/nKaebss4KApBbjBSYcxMbQjjiBcl88Es
raJ0WwV22eHQ6aPlEthpwFZrDhaeaCqdOTQIgjQRaRjKS4u/jznr8cGpHUNLx8zsN3zr4nNFlR0r
32lARZsoOL4CQa5jg6H1a2ukBfFh0RaarYl2Bzitaw988o4h8iNWvDgllzYVFZsGEOQqQ1i6JQbV
EMZRkPcKPMXQ5s3vrMEnaZ9oBVtRyHE6TzZNh4JuqgnWVyDIVSwahqpmQy0iv0zSPtXQHnaH9nE1
lRTFdrXCys9GvG4qSadkCkGQGmOJyEbXoqIaajmqhjA+lu4pl0gXljaT2zukZZohLo/Ti1hzTMVY
D/4gCHIRXlVsSaxmQ02i4OExM0yzZRiKTigH0bbrKjxybVuyCkO7nEMITDF2mPRBkMssXBV2v8el
dzwS/KLs+KuiVVrecS7arO32Tg3ZhprntLiXGHJNitHtt0UQpESwwUEtwrdESFGgl4b2IdEmZTUU
Fe1ue2ineyDXJLsiVxpa2ltE3GOcyYggl4Hud9eqkrQTIZ8N9XVLW+vJKxt8IEvb7hQIyaUVSbQK
z3xCDK1jykS0uB0EQS7CmbJsulo5OXUw1/Ik7WOibXrH1D1uG9qJnsi2JImFd7yck/cL15aVZLXF
ngEEuQTxRm1JF9Li7+O4Nu34a6JVut4xFW2rU2DhJOSNQdL5YpjcIoJtuLKiJutte900giA5A1Uh
htaPyl6BoccM7QMjK+qGFtzjvLZi3ZojI6p00rLlFc1FI14kdhZEu9qaL3wOEORXwSV0U145onwa
By6xdk8Y51aJllnaTauuQgPN2q4vFCGwGUcO06BZEC2WVyDIBSRawihUIytor4D8hJVbdfcYwsf2
qHFhzlQU+n5R5pqGvE58dUJirLab9vJaBEEoM0WG2HFUxn2GPOwCeUi0lWYrS0tE26qrgJ9v07B1
USQVBhA5VlRQ7SZrZ4cQBKHAyArJ1cLCO16Cch7v72mKlkh2vbWb8WBLgbXzkB8uPj7jyNsFq6My
Vuus3Q2EIAjFJR6q61cD3VJOLEeUP1BY0ba0q/WuOWJRS1TZNCUnqKeawNDmxY/rTG1XKSMIQlgq
0ElbDXRbjng2ORU0+xzREtUa6/W2WeLEJwq5humK9VSTRQ0tfFtCRL7CQy2C9MCrRDoiX3bSLsqR
FV+PH3dFCzmfxiwKR1FtyPaIWhW1HvGOqTDJQmPQ9oCZWgTpwYESxqqTdjkXfPcJJ1rq5KqJahSi
3TRW4XEyhL9MSQ+4Wg9vIEGGFnQOZ9ptZn5qEVcaeUJgETQvxmoq5N9lTquhgqiQxzhf4POwaPOj
KUiQznVb1dM9sZNAhhbKKuaFoR2HvGgX2wggTbTN1LsHqQ5SDjb8sWuTn+zz4fj2dyHIb0RTaRlh
qaihZz0ldpxbWkOlkaj1aqXULjpVFVWGKJSvldqazj3fzQ3tivrT28PqzpXwKfjVxHbbxfXJpRWT
R9ki/yJzlxxpHauMHU9DTX/GQLdCtESCzM7KNUM7VFTiHMsm1BxXezWhGKrsmV+t19vtYXvP9rxx
IKtw1apYGu4crm+IOPIc+ffgbdm09creTTzr4dlQlWgTsLU0FJXUhiuGZkIlJpE3i7R0jiPilsv5
FDi2QGR7yJT2/XaY63A2pvdrMmyY1qzYsgpWW8cANPKPMXfpQLeyk3Yw5GmS9oGJFXLjTAv/QPrG
qUJKGnFd4QKS41elUGDhTVlt7A/ZHc5r7vr9ezbMlzKZYCWCC5D/034H6p7f6WEjyC9Bg5EVblAu
f5/FFtsj/QTR5pEoKlqlqquIbUj2kIO0o/NhIeUBjFkmn0iqjiC2evrqzJmFT+4V5GlKIFnH0XVR
9H1fFHWH6JbciaoYCuaNkH8KE3zL2pyZBSc6jw50K0VblDaRf6qzKeeq5PPQdC8GcVmFtYhhmJtS
GycFmj3sD9dmzsS+XVhZYmF13feDQOMFgde0wPd1x4V+IfIz0dYi/xKQHnF1tvgKmFfVUI9QE61i
EEurlifLOTQDsAytJZTO8Tik3T1qkp9n2VDzQ7bvbv0pGfumkh9kJdfRfUsTvCgOR/P5KIw5QbN8
3ZVs8LgTVC3y7yDQTlqrDEPNuCDflPcs0RL3lNja0kPlFQMyM7ZE7CxX7pyfhLyfB6EK33ibwaau
/f6iaAVFMamNBcWKgebF88V4OYW41mA5nsxDTgh8CITLiqGih4z8M0hwthS1eaGehSdKD64CqYsW
euwSMLf5m8JSTFTySRY49kaF+Z3Egu/SqJFR7bAF53h/3l5o9Fm6ik0dY+IXO6LFc+Fw3OgumC2G
sacx1aqrZNT/YxDkt5EadM5MVcI4CnTTfFyzdWMLsaC8L3ZI/ky73skbBdFsYd7HMe/TmuPKzh4O
GdjZs9rZY8sQFAhAma4pEb848OJ01llHMBino4gPfNo2tJZvRKER5JcA1VCmU5UwwgKfZ4m2TPwk
Sp5s5Vz6AYj1Or4QTnKdLUegWXCOa7keYmaz/TFZ9N720oK5GjTFoxMrGw17K5+WkzmxtZboQj2z
IWGZBfJPAOOOayWM0znzjr8+zq1XtjY7UY5sYnVlmqDVRT5e5N7sMuWYNUyonaXLMImhJb7xUenX
7B/RpEkeSXJEn+dGk96lP4PZZEjOtZbvuLaiGInU90UI8stYygptf0/zv09iNrLiaaKlupVpLdTC
UhIbioNt6tHGaW7dx3RzT6FZIlpqZrPsfD63x5rnzF0opzLpz9G8eX998WA5XgxHscfzAY0hJ8Y6
evKzhyA/gKfSPptycMTQKztpn0eiQ11FCF09LNUj6cQ8FlojmtVgCQjUKNc1u9/vD/3n2Ykk0zwP
5GX5KO2ZbTFYziaL4XwURpzAa77vwBzlZHW7IhJB/nqgalfStSLzMgt5UXq4sKKFIsPyO551zIFm
Xb3m0s7mnibmPbQsBsUkSwxt1r9UOjTzTI8jBtW5uGI2Tole44jjPA+qLCxfdKglN9batz2RCPIi
UuKumo7vFSfHlAueUA3VRoSmHhAsdWqJT2vxUa7ZwWQkwL55hc1xy+0sdY3Pm/5wryWDZiUifUsI
F03JQrw45jyoh4JOeJ8CFY0urdtYXzoiI8ivQVMUcjAMisUCg5AXH95J24UPOYl6xlSzRGzEzqZ0
rsR0EnoW1WxSBqEgakx84+O2/wQqSrQ7yHVFSxg1T7PLxTwm7nBggU513alwYTu2Skyt1fszEeTX
sIA5M5JYFu0v6RadZ2tWtnRbsQvN0thRmEIdxHS2GHka3duTa5Ya2gw0e+rsw2RwxDUgmoVyKm/e
mESzXIygcpGYVYc2+RTQph8T5p+rq7X97c8pgnwrHrTauH65RWch+A+PrOiD/DgFLmWySgghmk/G
y+lsMowFH+xsUXHMair22fG4P/dr1oOfReys4wtcwzWezSMvgA4BySyo+mvhY9TSrowLpRoI8kvQ
2UaOKD/pLUflyIrnSJX9IKIyYmiphCAGRQ60YToZz8aLUcRDu30+XqY80O735/1Hf2tPDGdw03Ud
i4/T2scHi5CWGUu5VluwUmpVJabWwXFvyG8mkqD9XeSLo+EkIhp6esKHCZhq2IQiYU2IR+liMUlH
HE/Os6aSB46pc8w0ezzteyNGkapIxHiCnW1odjnkNCbZjl7ZmwYbPgOd+CrmapHfjCMrignecZ7w
GQriUxp8CqEWP4ft66Gl/cQ55r04nM/n5ABqiTA8sQhCFc7x/nw+9wehNJlljIidHdWOs8thzPt6
bZuuXB8WxW5BYQOjyHuD2PeTEeSXAAFdGJ2aNwssQ60wtM+ztDbbUsDOl1B0qPHQ8hpHHjGzrlTO
SwVDu9vtD8Q1Ph83vQfaQKLHYiJ8L6wVVMxGxMw6fVa2ptm8G99Yb2Ts9kF+L6max47zY94EOmlz
iT1Rs5VoiY0UiaUVPI7zBM1ina5q0SbAAsf7/fG4603MjG3WaaBb/Lx2MIVEL4za6NesXdcspII3
xj3THRHk78RXaWVFMQ1xOudF6TtEW4aDmGgDLa9SonPF1aIdj2VoqXPcW7c0gLJlEzRbzTaHCFRE
zWy/YivN5oYWaq5wTzXye4E8jOlYhXc8DvNO2ieKtqlZOmDCt6wAkqmwaF5hzrGxzjV7AMme+gPH
ItMsdM5XdnY5jAKRONl10baGH5eiZeOXiRf+iucWQb6DUIVtIKKWa2BK++Oar/YnSrYYMaGLgOPS
Ia1KK9sDBcfHY29SBhbswU8QhZpmZ3MOklRmTaw9t6E0RLu90IWAIH8/vmrLkusL+a68cSjo7rXX
/oOapaolthbqlWhVocIMbe4cU83uj/vTR69zzKtsQo3Iz6sY1CwULL3qb7h03+X+PoPt4cM91chv
RYIwlGPlG+sGaRS4pQC+RbRs0ARg5mZWrWd7smx/OB7PRt+9CjBVCjretVrceBzyVj3Tc93QsjjU
arXZXhvJiiB/MUvaJqdr+UbI5VywmqnO7xBtUV8oFxHd0jmmrT3H89Hoy8jELkxJpuMbqxUfsK3r
Ds1WoqUbhdbb3fpFzzCCPBleJaqCIyIzXWmkPWcKY49YOxSarR9oiaEl59lV34FzqtBeAxcm1JQf
HI94322EjTv3UWmWrZYvPPGw5xoI8vcDDT7QSsuOtIO5Z+lPmjPzCdEaxYAZamiz06H3QCuqzM5q
UbmrC3rnraojya7Kr9qU45dL0e5xBDLyK0llumeyaBaYxVUn7beLVu4YWjZe5tjfJjCkC/Ykt7Zf
789sVFvtl9/zJYvbFu2hfyAG8q5QA+CwVjB4vRQvJiIPfjjunRn4MwQJ3aWTL0sfpM9Yb3lbtEWE
t6lZGoXKzvuP3hTqWGX7CPyaZpchbzVKKq7cTsfSHpS/6PeA/CDTYcQHdFVbrtfmy5ieyaC0AMZq
//S9EoYOhHYcX2AVgbM5L7rPFm2PiKtzplpmezYwMBX6BE7n3gyqnkBvnePwVc/7dC40yqCu3U19
DVguWmPZdx3krZjNI8F3C63atZdp8cfixUOH6zuBwA1/uK2TM+m8Y+Jx0jjUJA7yQKz8raItS5Sq
bA+LQtFSqN5sT0S+h1YvhtVTlnJWu/FXuaXZSrS7FU6KemuWIy/QzeZr06yQiq3k9OOVawjtNcTm
9g/sfQUiFN9DaIfOV4PsSW65vkG09c80NFs6x0y0Wd8bWWTCCgRJLKst/8AyzqDV96tch2m2FO0W
F4S8L8sRL1WvUpMJVJJq+8graEmBWemCvJCUxBa9n3nTj4kUYNBMfqSdhbyee8cvEG2ZgWFraGm6
h2h23xeFSl2VLp+2vGqnxyQMxEqzN/RaM7RlZ0KGjT5vyiCqGdjSsoJYHVhHrrMi2wI2HJAW8FWb
cojFVVXbSV9/8yK0uZkgBTjeTRdR8PxO2q5k2f+UHueYGNrjqu95gHlwpgnvLqUZnuUjI+XiHaCm
zJJroj1kuB/kHRlrEttJY9fEStTKmlhgFbnncUAE//FgaDYPo3h9n8jXcaVSutTgJpL2YoNLJ/1L
uhbBao7BmO4VeJFoq0LgfPwi6xM4rft8Vo5FjquJOLRG2nfNuplVL1BXLGi2dI8znMn4fixYHUKl
2EKv0OBNN5EPU5iCRFks0nRIV5NHnCcIoF0/H/PJhAuvLPK6jF4YmloYEBAj9iuGiYbTRag9f6/A
JWrlSUW6B0S77218l1WYvagHcXmgHYyKiZFVn2xuSGu09Zswzeai3eN6kHdj7DkKrFmUaaBJYv1m
xLyCXkfzdJLvIq8zmC5n4wksqwhjolw+CHwmXFY6Dw0viem/Li7FQ6wVDop0qcZsGNWbZV4j2lrn
OxQwfiS9UShWvuhzw/IZXXhsNHOttb2t2JZuk+LTcElmaS/s9UL+TZaRZRLJgtYk6hRTwfIeyHW8
vJG0HzDpMuXmFhdcZSoU8vKSHW9y/Sc8CQkeguQE3Hw8+LNchMJ37BW4otlWXcX5eN6lPbc5BkNr
ujpfaXYWs6KKfFJbaWKNGl3ZVqKlp+hs9ZJnGfk7GLly7hQTrcEpFiaCEsXeFmzOYDobL4huia8s
FLotW9UUNZG1F5jbiUq9Y52PhrPBgBhaTX+VaBvFSevK0PaGhnwYciy5fnVymM55nSXEix/UEmxL
uHW/2aiJFkui3oYJDPeGfCvkX+kx1tK8eE5XXNxNLlu61i0/4Oqua4L5UBRZNRTn25tQeEijQDlU
mM6m08nIC5zndtLeJdp6XcW5760qSsAhcHw+LT+Ucr5rmtUAmVKxqwZNi1vZ4kK068/8wpBfzNyB
mUp5yYTjOGLAc+HnBAtMl+Akg7UNwyh3k3XRdfLjrQyBVf976+xc6uDrPjeaLKfE0PL+kztpb4g2
aXT37PfH3rFQI3DiJcj2lE8xpKZMOe+fV0slAusauW5biq2JdoNrBt4DzS3ixTT05IONXXxKXAPQ
62w8nkxoQHnEAsqQC2LbGPPTLdQ6Otx32gJQDxQGRvPJcgmGtghDfZ9Y2zlaamh3u112oPMX+x6t
xXx4KyrTYWO6Pbf2Q5hiC61uNpuaalcNY1vTLIj250rRkNcx5WUoQywlGwjx/E4jO5hOqVQh95MO
CTBen5jZMI6jiE4A1iwWk3LzZgPyipT973OSRyprKdfi4WQ2W8TCty0D6dA0tGxzz/mY9aVgBJu1
NJT7D2C4hu+YslzmjGqS3ZRUui3Pt0bD0BLRblG0b0Ao5QEoiBeLFvGLF9cVCydX8IEhy1PIE4os
2ggCD6Y2sCyxkQNSVcX0vsnaWgm4DI7Fh+lkNplzwdM6ae/SbKMYihpatc9bhd4K2/WFapDb3LMc
urGy0H2u2A2sj69RKJfKtpRuQ7SvCdIjP8hAkGS5qKJg61UvHooGyxk7sDIzSkuhNKJKghUUaE3g
c1aVuYXySAUWMzrfssFiCmdFKOcVRulkvKATDV8p2qTVknfa9U2SoNNwTEeryipmHLjxcjlXkUmW
KXZXp9RtLShlFN+Bon0PFqIim7LpFmY2mvdLdrqE+onyoEqFSKTIKo/r0Gpk+JxVkH8hVW3eQU9f
3t9RlxxDg4/k6oE3X0wmw1gTne8vYZRpBUnT0G7zNlqlr4ZTgaifJHpVinauEY9ALlW/KhQLOj3U
KXRbhKRWNUNL7Xu2w968f5wRHd8JxU+Oo4Nke6JP0/FiOIo5VqRI64vLbeQ0pSu1cWmpMu0saDYV
0O/K48jkBWoo8+7VHmIqqnQQhMhzQ9g36Vn6C+qOK9Em9arjLNsfe+sqOJhNLjlBtR1v7PmuWY43
Z5KlNpYKNSvJdQuyLWNSBfk6zT2K9h9nLsn5aVZyxMDrOcwuJ8NRBMWJVq7WUq5XaGq3pOjhk8zC
mZR6Z519nSFL+MCK1+FiAbvYn9dJ209tKmK7GAoMbe/scHJ0NU1X5MqI0XKukZO3UowcZ5KligWl
7mvkygXdbtZN3TJLi6L91xnQGiiwl67ja92JE8vJnCiWD4r4b02sdg/FJ4qqqqJBqNF4m3fe5iUE
cvDUE5ggQypF0i0QbTrnyoFu3y3abo4WaqHOh7TnJmNYKCDpQXWoTzma7Uly55qazF0+EI5mjQqY
bgvVVrKF/6KlfQtSkYagTDCzFh+2ftmzBRWsL1K5XlTqBbqGV6qb6LImPrGD5/nIM52WQ5EjLRfC
CVwIXhWGUirR5qFjUFtvXcXEpIPUg8rQTmLNtetDV7dMsWwH9fF4Op5Op4+PU87xDMJlsi2TQDRu
taWixUDUP8zCUVmuxyWusdBqwxmnIUcUq7OQL0yt+IxkL8m3stP5Sx1cyudtQuYk2qHqiBoXDolb
X5v4/QrNFt4tM7Rnori+YW6wucd0RL7MVS9HvGjmO+ML6bGt8Ucq2Q+i11yoxafgb9mO5YDKWqkN
e7NA0f7DLJzSzuqB0LSz42HkaWBjL+0gf1C6djmbQU6UxOhtN/0CIh02J+k+H42IofVgcsurRNud
DHU89TXczF2VGtpqLFTKWQ4xtPk3swwv9YuPRLGn/z7+++9/58xQXPKo4lgjX2tsz6czcZJ3h+2m
Zm3Zt56xuOIfRlZttqKR+MaN4+xyMaKKlTqzd6+8+D8n3vJnQhuBqhqy8JSHREdBkCOtL0Qjchov
k7TyE1YL3BZto+r4cM7OH1HPPeqw7dq1vLT4AHGOdVNRa7kiepY9E8EeT//973/Hnem1f8jMMg7H
M7G1h21ZKLVB0f7zaArzjYmdtYRacnZAjrKwsE2qG9nbL/pPW95CtbRJPrH9Jzh1i0SmR1rREuJw
FHOan+d7XiraXHfEO9723KPHTrRaNRZqJIiSzJberUszC24xsbL/fWykC0f+VDf2+0OVtd2Uov18
w8BgvPh0bwjyesYgRGpoiTNZVeaAY0yOso7bd4a95+X7OenKrKuF2BlFfzzoydPrm44fCFEYRlUY
6rtFWyusWBUjGLNj1rehQ4L4tuRXhnZGnGNiaKtNtjTszI6yR8O5osCFuzkTH5nZ2k1ei5GdN5/r
oprEHnmPZhXnaKP/bqAVj3ZhQ5luVU2XgpWF3GaR3SzF9S2izU043dVo848+JrfwjjUvCmOPHP/M
V4lWbed7zvu93NONvlBhUqQu1Guhcue4KlgGO0ske1BvPSMLBQqk6qIlFn59fxP8MuQltgCbnlJU
RedQt38vQ1ruB86xqOWD+P/8mU5GxKWsnWWvTPm9xCdFS/VE6+SVxHiw0mIm0/FWrg7d+zExtKJr
vqbBpznOjRna064vvOaAZiU/qhUd+66t0G/dFC24YGg/jhv/toDmLownz1uAaKboE6KdChLdXVA8
Q/Sd5/G3TuS7EOnWZZNW6RbHq+UwFgLnjk3G9/AZ2dJ4VKIayaXz230I+TIraFSKImJoq22RTxJn
L2VhRbH3fUsDSadk2HOPCVudMi+FNdSYc1xmbNgSkY/TNr3rQVs0fpz/B0R77N0/0kPQ+C2x3wKR
7UpCY/t3EqsyE61jCWG+r2088gKxsa3tNaKtrcBJjEcmbev51kiYuhFxQlBbY/UMcV6mnu9Zb4pM
aifkS/AMOt2VK0+qk8g3IQpllPnZ83n/cTru7s5dp6vtZp337YF3fb5rGuPSt4mrZZt2PQnHJnkZ
Ku6l/hsZ+Gz9ODjHEcv2TCfQxuZK/Yr6OnfbWlmBcaHqA0stbOodS46v8RwHhrbsFXhBGKowtJtN
PmWmd2yqzcaol4qcznmXPPDaIDii9tMpMz8RlYvX20K21D1W7/ieVDeLuQe5ZvMx1TIcU0xU7V8I
Z7MhbpJueSM6VmaWxrzvVFmeL5xm+/mErWVdLlL6xQc1SqjtgCpq3vME6jW8UrRG1f0Oou0ztHFC
95VU0Z7U8xtRKLp9+mR87ilIQa6FaPfH2xsGUksq90cUXVq1BiwlUfBg+/fh0/gDOdGCoYUM3Qwa
YvRGZvbJ3FItG/arKEnifrGqUYPYmkzjUES0fN3Qfu+ZtlENtcmTNrueOxxA3SgxtGFxop2NeAcG
AuRRKDa9cX/vobREL91jcK9vroKfuGbR22XmC18oeY05pM1lXL33t0FePCw54vh8uJgNBss09oJ6
2ObVomWmnTW4GW6fkbqNy7wHB0QrCJr/UtHm3nEZTPromww1V9lisLT4ADG0rK6iTPec93u7L4B1
/fdp73aFaLPzrZrQuZQnDqhkiWJ9n44dscr58uR3gLtF/jZCiYmWDniYzKZ0aGFjltLrRZtfkFbd
K+IXHtQEXH5YLSCCaLVmTO3Zj6YOjd5UY2ZoJ+3x2Je+ClRZrhdDzULNsfM+gW2xYW/9hQmoo+TA
htEQ2R9uGEmN3EPejykRyYo+7GiChWq0aRrqzU3ya1g9qxwceRKWrdKMjyPyxDsezxYwaJTNti/t
3rNf2rdFy4oa6aK91ReCyAHdLADeQ8Dz5OXH9gpUy+q/jUq0tYW0fRWMnE28Y3KiLYNMI8GXlKQZ
hrrp3PYS7wrRZpv02hfO/Fyz4BfrIi1DmQ/TBYz+moeRJ2iWqLvkrLLGYNTfhQO1DDD+zBdi8vua
zCMoqSi91O99jd8ytnBvhvLpN3pYkJDXQ8FoOct/wU5adr/dMTP786lPexZMhtL5csjMEqaT550C
rDLinH3FxwDkDCRL/tmvrqVZFz48IyathHP0gPeieTqjS1+m09k4BdnyFvgostE7cwP5McxEBUfN
zQc80KksxVbU73+ZX1ctVEcpiaF+NogcmdTQFqL1xdfMhurpFdiDpe2p/43hDiWLq1ryNB2iPuX4
RqL2r53mCeEGegfAPVavVP7PTKZZSXLYEL/GQPrBbAGjhbRctd8yLRP5KnYh2sCLh9B3Wu6o+uYX
OOO6qWUFRobqfi4e4yu0lpqKNoCBVi/qpJVbnbSHHTnRHjY9d+hCOYOujQpRDUKLGdrcr95m+6/5
xuynZ1swtIdz37CMnKWvFDPpdVHzwtYOicFsAgP8YPQBeTkkXzX6yLcALzNo6hSJaOfEJeKtwjn+
7hY2xhVbC5kfOgciMezPnKoWEDsGU+uKVLQ6eUSva3+vece7/SE7HvrO5AmUHYvViXbM6RJdblSk
d7frB36nIVhaEO3lcADRLN2vBitMLT5qTwQbLCfEPyaipb3U5IE9e1Qm8giymoBoYf5iHJJjTBk5
/gtEW5SuJ2qy+kSLrWbSJC15QcLOesv/9vWWVUFI0zveQfHwrmfMzBzGV7lWWFo3qDqWyxkzu81h
82XnGFjB2CjinF82kKJKyxbpRDAvTltu9JTYWfIGzgkaDBki/jEGkP8qXOJ9MtEKURR5vO+Yr3KN
81f8Fc0WDQSwpeb+93pXpuVQ8IL0IeFYy/d800Ng/6vNhlqV1VCZ3vukQ5JWqAxt5Jt2ObBisz2o
n87PNhBgRuMhO19S/pTu/JLo4E0+akl2OYZB9HT1ErzjOa5kK4ncN+EK+SG0SrQe5/FFuueFXBOt
LbNN6FAEe7etlfO6TCZaUXdfKdp6J+1uvz9v+4RDvtR0/Kg0tKmgFxMYqWhXj3qjMFf1kB0upXkt
SPVIdOhBayDYYLZg2Z6gGEYvSTBoboWn2r+IuZkkKpxpLR4y6pDuoX3Q7D/5f7+Xq7aWDY8CF1np
m7LUw0jNRQvVAvDC+/bCij7R5iPKj2ZPABcqo029Ghc7iS1Xrol2/ZidJazodPO+WXKAy8J0MJOe
G9YDULN0FAkaMa96OYmejaU2VnL66D0hz8M0iB5M8p4bwP5YnWm2TkNc3/Oiv4acG1sjMe9TraXS
JC0MvBLpsq9vb8qrNxQ2NuVl56zP0MKIaUkUStdh6IkSHZuasMWYjx8gxQ3R7P5C/SHP3tNcmHkw
r3XJTxcjj2eH2GKcVvHAknXStzwM+SFEKlp414XsCF2xeEm13/aivyFaasQSI7nP1rq5aN1ctO6L
RKu0RAuDFPsLERXi2uhBVK6jDaH5XSnnSt3VBHudMIFG3v7gcVw4ImLQOM6O5xzv02dLlss3bpUl
scgjupI+Ql5NpK6of6wTVxKSIzSaUvAa5V4VrV0KwkhWd7SWzhSlEi1dPP+aprye0an7/t64IfGO
pdqA8gVnuTZ7gPC9u2fsNFIycvleiz00VVZTIQZeTbPLlPV2lcnmGuC1b/uKMZGfwieiVWwXerKc
fC1qg+/X7XXR2sU7P5z5blfQe4bMGkSpaOlWhIbR/jYaMyuK0al9QVcf3iOrAeXTkBfpeyUz0hdq
rQfL2Wx5/2hTCTI+fcntqc3qjV2dj6q3wMEENjDYMnsATKh1yJvQxagW8gOMkpVKV7fB61uuvcl2
ZPtdL/dbooV4FMunGNLN162o2sWZDURb34vwXfdP6fGO98c+8wQtSJLOl9VQYyg7LlZbGiu5Ezme
cJpPtxQ6UNYvpPf8UjU41PZ9IrAVaJ91dCtKy/PsYBhZUN2Ra3XFts+v8gXVLK7WezpHfopgs1JV
ma62k1uO0WvM7W3R0pHI5GWtrqRbkVWT/UAqWl13Xi1aoy7ac18oyEsU2bW4tPj7kKdr8pidXtsN
27yMfZedWOhzT/+F1vmbx4S5etj1NdBb+YBrcp6tmgkmoSYWlc+1ZZnram3mhoj2kZFdyLMZKBsD
Ni5CcF+t/KKWdL9RtW1RdexsLgtVMVRDvJ6vTZXcO2aidaUXddI2WmmL/ZbHnlPl0lcajbSDUNPN
XLTkOa8Pd5lwOrQnqvVnnb2HOvyNKeQz87DtCR3REe7gVAVc9eaXRhAIS/Kl833QjqVLCSTkR7BW
a6hllBuabei2KdtnK/eWaNneIFqFTF7X1yvpPTU3tFS0za1hz73rFo15x7lo9z1uQWgS71gUys/Q
rQK5aFXDrt6S5j4tMWWKre5eyYeb3uhvd7NNt6FuwIblurpV5WcHCw+yxGwZ7npT0hAtND/sPret
APlm1J1hwFs6W89YHWgq3Ta95G999fe7y8XrNTGSq8kHsRAt2zxfivZ777i2SLqYDgXDofoafAJy
FJGs2p486h3n3r9RGtohFL2otMpFbj8R7Erm1cpCMVt1o9BsZS9MFioXNk2HnC/JiZFrs2Szba3z
OmTYNPB3sd4SkVJDUZxkasJt6PYVsr1wri1CyElfOW/O2KR+fiHayjv+1hvu2f4O9VCnnmPgAFqQ
3CoM9WcEbVXFVtviGzQ5SYhbLOfpK7aCmxUpsfGmUNiZXBsxy2fdua08zKgkz4wvjKocceBA7QQV
LJt3kU+roZOmGvsKfqr8OOVceOx+iMt2GwzlzdpYG7kzlC8Urwn3tbK9JNrS1l4ORnGqXBOt675q
J21zhQ/xJqGy4tRTDBKbsmLqVVPeMvJptTd9TldMF4Jo56EnNnMPHH3R96EYWNTZY5LBL1KvTJQQ
tp23thGdSQ7JnrAIQo2JZm11RfsI6WD1LDswCtmCcKmcD+dn5I8/y1h0dVeiv0qInjsYwq5jbbYr
6gflb6814dbsbV223yeBXtGWA2jIyU+5NElh6atlHMp16ifa77tbeltK/UgLooVN0H2jUyVVsSW/
aspbCLpULuKghnahk7MsDR3IrNjQtzTB46I4jiM6uAnKliAFBvOzLhofYd1e8ztw6LQ7R9RGhQ1e
cJakJKt8nwE9hTMypt5SuFS0Vxycb2IEUgWPCdwM3SSi1SUd7W2FsCl+QZVb1NBtZW1/pLyxVAcR
x8pJ+x/EXJLtUrSu+zLRto60rFsg64u3ki80Xa08Hk7ngZPX+RIVwok21uEsC44x2z0aaEIUztPF
ZEyYQA+OoMFEIBY11C+VPHhG25uN5HzqZjnkZsz5rmIU+an9/gyrg87nSrilbulsx9uTz59LSH+F
tHXBYX/SJfjrA4sn/jn4DTRhkn+LUERDty82tpQLx1py3FuJ/aHMYl1CLlrp9aKtsrTHg9lzh4ba
7KSNfckuZuvIyz8zC46yssLmx+uwiiicT2ZVWT/0zsUwqoB8U6KuLm4XjNrbRIYOW0lmlcmeWUjs
rFGkp0CuxxIm3qw64d67GOh5+FSoYGklXQjJKYL8RYISE0dvOxFvjLeF3xKd41eeaPp0+zLV9njI
rIqd3ER/f6cvF96x1DS0r5sOVRYeHzc9CzWgb1DSo9I+ppxYLOCQbYe86ciqWkiWLsSeL2btdZXL
yZyuR6MVTMkF1UZtZ9anY2Vd3RvlB9pxHBDN5kXSbN38x8fHf//9d6JbrE+n43nPjrjMdz4/MgHn
04ypQAla7e15LsIYOvKrxUEaFcIqOzdiEUy2xfH21artPdgWp8e+Ap0wH9eci/ZlhRVyOw5FhdBn
mRw67nhU7gIJNbecFGKL5LOKrcjlks4w7fd+p2msiY4pQzNfkvZ+yaj1YZ0ekd3qQDsltisx1uW6
+dPpv/+d17LDgyGejjTJOFSyzUC0fQms7yKiHrHjdMqnLRqRcnCoaw3ByI7FcYawzSP/P2Ns+0NR
1EFWDbUnA+GbrMGnEO2rCiuqcqhimiI5Ix76nAGZlkOV0W9o8KnC2/nMEJCsAxMS2+PWKmZDWN1C
92Ku+o9489Z0RTDfpkkOtLmdHcwDSSZ2lq31O3/893Fe62nzIpZB3GR4LcA/+3NvLfP34LFjbG8B
SX6+fd3N/ALm5jo7H2k0At5gYew185OpbntU+8pGApmaWlpdsLK7k7gl+QdFW3nHdMPled2XnkgU
0/XL9vfpHCoryjvMNUs3Iwjx4lpbzQQWG9p0M6ba257eirE60EZhViXP5MrgG0MRCJxm/zuv/L7L
hXJ2Zm/hGfnD/U1GD5JSWToXSrA8GpxC1TaY8PZ2RyMRGfWL4Iybe8m5tX2Rse1xj4vxMwkxMt0U
hFKEoahoiwEMLxTtqlotcEx6KoiGiWo6QTkcihwr9VakjAZ4fRhEfFUiY9ggzFZQG70BouZBeAiL
w4lzLBQGeCiIcrKiHkF2Pp22zqVEir45kzfvjEaXX7YWHuJPzuVz64R2PGEQucnM8w3y+yQGlx1q
WFyK6rbykb9ftb2izWPIqmIkbe9pmJSxY7pktabZF/TS1hZvQbD1KPUYCk1V7Np6S9r+LtfWr9j5
BiIvTK9W+tK13zB1VYXNmLczl7AnxZT0oKiqmHG+maxgkwH4xvv1lUJma0PzPxCselWG1HWgnoT+
cRjlpRXkkF/FjCfUEOOAyDZTQUr2HyeWtoOo1HZX+sg1Y/utDnKvZG2Z7a6FHYytyiitqKwwWeHf
y0SrNERLs7TnfV9Y11ShWaAwwdO5AKmbmmRp/ZNIfOPhVas2GKcxWFqF/ApW6+3NSYmxCvt63bIX
dwkH2hUt3DrvT5lyVY38/gyjYLPz+RMr6R9Bc0ydnVlZ0ClP/ZBTrlO82w3xWHuRkbvKjqcjK5Bh
seR17Wj73bb2kqHNK5AUw2xWRkkKWxqWi9Z8tWiLicdbmKq27nmJDxLVdqtVebNQ06Xy9uxcs7ol
NBbrDJaTRTofhWEchqPRfJgOh8Mw5ulUeeqS3x4q5VJDa3n5uwU90CZwo/tsf7w5Bz7ds3qLV4nW
dfX8xJqXL7ps3TX8qYgT8GCN0UG+wFJTNsRNLspjmLUtje33qvaie0yFAjkWsXHwU4pyKLoluaHZ
715w2Sit2NIjbc+ZdAgJn6BspZ1EgSM1Hptpuq5IRDtKx/Dtg+lsAevrYF+sBvD5/liB7rPLJziu
tzf2Y41gW5PpaHEuTzjQqis6mfm87/PiW/ibPWzLfZFofVAne0S6wzI/ru5IrKCx3OqEpvYGnLM6
0LBUXbWr7z/Y9ovWzo+10A+u1IuO5qr9d4iWxqH68sheQrzjqsNnKFhuS7SQ7LF4Lw7nKbGoo5jI
U4Ot7DBuhgHT6nxRhMH/bKTTer27XhU8dMktSm5QaHbiiZJqQDY52+/uWpIU0PKLF4mWesPsjxIr
gXKZvWWZ2/yrBvA5nKB+jVmkrKGsjeg295F/NorMpAINqDUjwxedp9Q7Nl9VwSh36qGope070urk
SOt7afHXES+6ZvOBQWG8r/HEmkZgX6lgnXxueEFeVV3MGSGW9npVsCZD5JgcaNmJcDmCDC01tIfV
nQWBBtQlH18iWg/qFvMTvcvwozjU3LyMsQgIUIP8ihv6xUwEZXMg1nbHIlIt1f6MaAlGzdS6PyVa
pRDtion2sDvszz3tgzNTlV2rHIIIg2aklmjztp4gCOhiDt1pZa6YH0E/UsyCW613yTUXdwjPCySa
cq889RxTIfe52x6MezvdrN3+fMpeIlodvOH8z7loi7/Q3oHic1PwnB9exfDPoyWH05kFpFhlYyuI
/G2i6HeQ88RP1bNafKX5I6KtB493h3NfW95IVcmRNi4Cw7D9vSNaqlqKzlpnzdZXVHvJivmN680q
vfJrc6GAkRj4/AU+ji1TNozNZptt71y08ufPQj1m5+NLUj6u7uq1g2slWmZrK+sKGn59t+AvxN0e
92dWI1VzkXNbK780XwufoCNyCg1EaqlZsxE6/qa7qujJ+Oz72vK4RDF1flSYxYnnt+JQtXRV51De
fDTVMRos7bX55suEpmiLy06Joykb69V2m21ujJmqM8+O++MrhkSNHF0qwwEN0YZ500/xSQ/s7gvu
6B/AXe+Itd3mHvKqlfr5HlH0ijZf8qOU/T6B0hRt62X+HfeV/7+YyV9UHoN3rPY8dxoRregNi2Rj
2j3Slg/gkl6rlR31U/TuSv08jAUgJ9piKNXCE03VoPmeT2j2z0A5Hfef+Pov40PAuPhLLlr2hHFs
dkX5yUEtLIXcgFMOWVZGkVvn2u8RxwXVKjaVLQumDHS5JtqXVDA299JW7QLE0h57YiQzEUa6VZNm
5p0j7eWHWj0TctGfWOsqysyLdcoTyF27Ip+yv45DixhaAwbMfEazf/7E51Ofx/90QJel39A80zYz
tdA54LgvSh3/fmZiArUWpWqNenHUt4ij+9ItTa2tKmws4dAuw1AtU/Udt8Tug/1P6Wum7eullVS5
tg5kEFqdI22/YtvyzTWrllfM5IvHTR7qKvSy3HkuOCb5vvVmc2Gl3kU2p5ds84FwU1j9haLFYeg5
kkvzP80vvZGhRio8A0Zc1FX7rab2gmjpR4jzp+jgP3nyXyTa7NzzahIUKtrCKC45n+0G62n2tyur
W3/MxeWKFVlFrXN2cXP8WFLIidYX8tuZxYEkq8ba2Mh3B6Fy5I+X9NPqRJllWUouWkmn2R7YW1Mf
WgGVjVh/fD9zZbeH1h+IRq0bqv02hchd37H4uOkTCVhKU7Tfr9mChmjpYENyfOh50iyoh6rHoeiR
9spSlIuXY3a2jHzt9uqlmcSeqti1bV9zGPRIDO2qZyjyDfz/9a0ZeTqNg6pbQVQLySCv8aUulld8
ioXBwlEbGo56ReLnsmgVdfkndYtP/4xok5poD4dz3wtcJwJy+LI7PRV0t9fOXrtzuy7a0rTvk0tu
oqvapiQW6Z4lR0604FWve7z3G6QfL9lQ69biw4VoaTWUDn8at75UQtF+ioEIqyKK4qgfKrIoHFTr
TyRVn35dASO7ejPjQwzt4dh3YnRgl7QwzJ2/5UhjCZ/L5Zp9T0HdPS6H21wU7ZyOnvLj3CVf8LoJ
67nXXxmseOqbU/d0HLcrWpicSv/frLmEvp/POvlvz8xgdRartmq/Sx2XXtnkP4J70WR9192UNDRE
g8eHc18uwiWiJUYvF+04DPKEz2dEK7dEy6LVF0VrkSdHKkPHy9BybYhftXsa72LXOyHj2YBoywdT
Wdq88thrfWl3hhRyg6WzAlu7ran2R5ribZkuSr7eFfR9dEW776s8ntnQTMsVW2EXEIf6yg22DC24
4/u+KRl/YDyaLEuOzxWGltMlEO3VfSIXubvm8SEgQlwGm3LRLv5Mct023gshloz7hT7NwIeNBKt6
uvbVTfGASYV7KXvyPfdSUU/TgrcKadq+hSBDBdoFCtFOh54o5bHjr12vJtrzhUCUqNi2pBeh4+mc
d+iMc7WT1R1M23Nau8gvidQ6dWnW8rS5va3PoKm6gZBP4ex26019lsVPiFYxYYHjjf7bb6O3tqIn
6c8pqi350YLJYzYS6Ew3+bN3qLSuR0WrpH2/nIWrKiYx7vnNjGNLgiVBDUO74ESYn0y3GojRtXkZ
5kusWlSXYr24Qmelx4PaVzoStvl8ifmaOMj1/QM/IFr62r9YpvA991JRxaGqKsas55myVMWGHh/2
slvEmlMkaT97OaVpaIlo+4srYDil5PBhOcyNbq9WywrLgSdXZaj5G4F8MRfkXJsO+TycWpC4LlqR
BZErU4tt8A+g7DbUPa6rVpa/rXvgmnR/QLL5kbZZW3HoG8bvqzIRbcxEuxxygful1blN75hlmPZS
r3erQmGFWKzumcaBA3u77Px178nN1UwKHb2lGobT7yp/Pkv0JWhuJ/8zHUsuMcM7pZqVSis8ABFj
HOqLDETiIK+TldFU7RuLNjv0pWlFKtqIjUadjTzrMdEalWizfW+6MoYFfY5VGFqYwCgT95gVHE0C
ume+URHDlGso/THZF1UMam7VfgcqLc0plWw1OdXHzrxHmFp0e7xaLuhiHvJrY8h/lWh3fT0+kKYl
ok2pZhYh/0jwuOaN0/VZvQMo6PrqMt/zJ+V1iXjHEm0UCB0VtlYzvRbPFdE0+a2RX6H5k+lPWJKX
OwN0uWVhd0d04Jvj5L4zuNE42e0BnO2mvlXv5SUWf51oe4qHZpCmdYKYDjSeppEmSl80tErT0ML1
+mJEU2gVqPI90zk5RMuyCi/6gSAreQe0nQ/6gDnRbPkR+MjKS3Ky/fjgEbNEss+ys/knHLZCzy0+
5bgvm57+LzKWiWpXrQW23yORXyHabU+AJK2LdkaOtLXpqZ+6WqM7gR1p131xqJC446auFa7uLLZc
iajUAzOrGHDbcr5nHobF+T7smRd1qNJSEyP5wdNiNUL1jy7VTrgQegIHGc4CHNRIYQ3jY7jbLVFt
cz7j92hEvlqu+1eIdr/t8dtCiYo2SmeDP4PJCBYEfOUG20laWuncN64VtgrYklWOkUs9ETZum7M/
gpLkRlaCrdWWxgscLJqPOM7jNYsurDaMn2t608CgMgd56Zj1WmQRZpbDczumnT8/dH//DlI16a3w
kL9FIlS0n1DtN91ERbd8/7Dv20zr2QoV7XA8HSxT2J/1ZdEmjTDUITv2VQXHEDuumoqmI54YUXLI
9UVYN8B28+l+4EXhfDGeLaeDwXT6f/auRDtRJIqexJUCNCwRxA33XdP//3NTrxaoggIxUcBM7sz0
dHeMAuHy9vuW/UZn0hqBovJKFZaXBBBdRHnx6gfZCn/fFP8fFAhW6/JIW5y1TzqIGCrSqnbj9LBt
Q5i00/7y43OKQ9rv5qEiQwvyE5S0qixq24S248jQfs5G8JQwHIdlCB3H09JLq98/Fx26RbOouuoT
0CfRazZr+3Q9fIlH9FvxroE8Y1iOg1wTwgIE0tqctCrfErY6O57bxCxZ9jvN0fdImxoDhILPRZXs
tQzD8YJI+pFtwtVZrza2s17Qm3QW6ZpsdwqsNcJsNYynY0iaFrNY24DR2j/n+CH40Emx1jafPltb
d9LuQ0UXo2+YhLQd7IwuxpgXjyPtUSGT+AneuDWaxtsMSLaaN2CRpfBN9Zqv/qwd+Hp4/5z849D2
fPCR56qvQd4Y/a2nfRDGqyMp/DydtbUnranoKRqYhLTDcWPRb8xakT7UvZ+W6HOGBX0qudYZDlyR
1o6eHnzXF8sJONhTb3bUjYkfjcnIcozVoEIpcGJrka+lrH2HDcX/VXsehIa9Xcuaqs/hSd1Je1TN
mBskMQSknS9wSBtJHt//YdKADza0yjwUCMp6oxk3tMsmz1YTwELN9jjL/+132hoImlfpgU7Ipjwk
b6H96Pm+40lz8n/4KebbDU1HVSKpWi5ZORSkVS7EYqRtz6bzRqfZ075J2lS9Z385K5UfjYGjtSNb
uWgHosay4+PHxzTLWvU7Qxfp4TpTeaoMfJBRPNB586xmZzYe98iyWshReX+dUI+EG27pxA+3tU/h
Sd1JqyrTvpngHvtBe9ZpTHFIG+mU3/1ZckSLSXtRVGlHOvaOg2Yk19qIGrAYaS0cXffVkwHLOQ5q
gbSrahO0PZ8uzGPCbszykqH4PzwSLtxPzza1lZAzCyrSuoorY4aUtJNxpwNr3L9L2rjtmA4UHfYq
aVOLFIX5rAAIzVgJ0uLHRyOu9kCV9gP++/joLjpDTHE9xE7TU+6R4tBipRkqyAjc/VNNfTSWGg5r
V/ZzU1F1J+1G1bkLU+aYtK3mrDOetH5IWtbCiO3s/nBUtEH0fSoiF/15ookhLbjHWq+JPfVFt9uH
RfPTDsEUozMZ9kaWA9swS9kpkIsmE4diplaRmfqFmBGR5xLTgJ/YQSZTeqbxdEnVWoC6rFJzxUZV
LOGkHU7G42YvsO5IHsc7gyLvmHB2C5y9qCLolmM6gnf81gCNZTkRZbmj9nAymZE9uHTRfKvVwr9r
9UaB5Q9Me7Xd1oEi/SZ1iz1/XM4YfpVo9OjjiTypygvdO+aO2trwucM+dYGiIyqbtCjoDSez2fBH
pBV2V2Pn+GIr8kmOaTi+24m94568nw82alqWFriuS8YE4j3z8FufbJnHlvZYipbbHzg6iBKWehW+
hUob25iuN3zg539GWjuPtCHVkei1m5PJcHRX8ljezhdHtLv9/nLZqwJo2xw48SQtb4cSWUt4S5du
IK7uTv8DtS1ww1frzfFvlWS5YOG7x8UnvdJ6SXuYtUIu6omEqQMKkzaEqRtt1Bo2m21X+0ZvRcLQ
ghbVYX/aK/qcP/FnoWAYmWDWDiXb2hjJvDv5HBuEJcMn3iZ/SANxkWdKXlSisLO5stmmkP8TacOi
pB02W67m/4y0PHV8OW0U3vEkNAbWqBl1N3Z6lnLhrQT2EfwRRNRgS9m59YcIFs+5kVqXB+PEZX30
2FjbZCaesfZX8zaSNI0WweeS1u21h0NIHt9NWoN7x5GhhTTURbVhR4Pt1b1oamE5GXm5pNUF0nLO
Ut31Mpa//yHC0Pe4a+wjjVS4SstGtVdre22brO6j/2prmyTtJoO0JiGt5Y5a7XYvuIu00YrL1ELN
w2mn+izd1J1AKPgMgyRpydtyOQGuly6dCqzQPB7/+hhKRVdoJPERXe+pEjh4Cppr1oRs/PoU8l2k
dYC0rRbUVO4o0wpGkNpArud2uJxVC0G62DtG7iQi3Lyl+ZkmVtfjUFbeewvPhQpnBv6X4A1gAsor
/GgbtmzagLXPvxpCUJtLWhM0mzxt1OtBITRKDBX/FG5oo65j7ByrNs6DaIXj9YR2qJFc8FFFs1xA
VYrO94e/XTnlAqVJW95wxKfOM8i/3NAmSYvv9eNaRVqDkNbX3FFvFCePC5LWSBpawtnD5bpW+a8t
GAJsN3iPYhck3YqRVqg4w4Nhf6hGKerTJStAerP/nXeusLQlzlp1bLJs+v9I2t1GVTqNSOuO7iat
wFnZ0H4pH8N+OIg3+GDvuKnJVdrM8zCS3vGlCtKOPeRbXtS76P6fmo0nCtKWeP4WCWv/B6ZWJO06
m7QO6a4A9UPoQrrT0qqyUGBolZawTzd98VLQe6NtoWKkjUPadXWkbZHUKYwHkP0CYHuQ1f6/DL2n
OYvKHGverlbP1nirBQpaWg/6GAeYtJi1gXWveywZ2g0v95xVO4PeOqY58OMJn89xi5G22GeIEhyX
8mPaGe8siHsMKHG19v+h/pQmbakT/8Nws+LSjA/gRm0h5G9W1K3cquZQezqp+XgaIa1/L2nNqEbL
dFOBs19KGaehaThWKwppF1GVttBnCMux8WfMn3Z7ZMFCnKfRf3RfHnaZkfXrE2OpoBZ5pQqIjMx1
NKP3AHLUFamaz+6o0n+ZDEjNx7O0AHvHd5HWMFK9UCRzfDpmXHcDBbE61HRYaGuQytAeLqV7pX2x
/ZbSFglGBz/tqtwz9HyMFJa21B+ChR1k2wx/uX+czLpi59VQOHIdFMJyHR92cNxFWlUWCiYFLqeD
6uFA1vN5btx43GlpqMAHCR8SrTe57Ev3SImoTNyA68X/97zob1qlNRyUjgYlqmBwLb/UWat5CKRN
WtqaDK8/CkaKtNujOU9fjD7NRCEgrSWQ9ubVMEQ6RYb2cDqd14qPwfBN3XcnfPb0Y9ajIa1ewNLG
uwtox9X2WbdGJnxF0SMNz/u1Q4O+OJxH/eNyVX+8rbmibVFC//HvJW1UqA0VSdclAtIOkE9mVoWR
9CIfIJVod4Szl+tJPTi31I2B1Yt0GD+bIypaUZi0UYL6cCpfb6YQZ+FO9rXqtg09E8jzEtfAKndA
cmzjqNZOmNrfRlp5zgeM1HGlWjPjEdI6sKRONLQF3FZRr4L3L55OX3v12NYclGZaHZ6H6g/dIqSV
A3MW0p5VWrDPRUFDSytCv1F8ho/SxidbtmBsa2ezBov49viNpJXnfHbKPsYAfA66WhJIW9TSKtoq
DuAcXy+G+pqPTUMUT220Atp4XIC0YSi3XJ1VtavnohBnEV0KD3Mwv67zounFUT1nbck5c4OKvIms
/WWk1ZOKM5vNbqPanNoKmaklzQNFSRsbWimgPZ/+2Rnz0UNTR0Fzzv607PBFuLdImza0p3P5FRZU
wNTSnDIi9tbzK9xe8gwsE94x8LdknefZhs/VRrfHLyYtH2nbqKKQsUlJSyoYRUlrJCu0pBBzuZyu
ylEBQI/koXjFpzt2o2mB/A8S5Tc4actvZyjiHjNDy8q3fsk1kWfD95OG1itb9Sfkpja6PX4laSX/
eLdRea59HV8IIC0qTlrRhsdJKMzZ8z8zi1CuMfBHEx7tLSZ0AYme/0npNBT5nCfdFDnoFUgfx8lV
C1ou4Pe/yEtOktYvf0OgZv5fSBsKpFVtZH53bBLUYlOLULFElFztWccDedfzOavH4CMwHa8XrbiE
aYHipLVF0l5OFegez4rUfFj1lsiyIKaL/GtWTAckZpefUSXXpZeDdRTU8pu0aLGjKKp+CqSG2jaq
PXZvvm2GsLAO21qU2Vsh/J3UVQFU2m13e2por1+ZxZiFBQvguUTwx3So+c5NzuqJhwPIoF9Oh4xU
1zMxZqRESWtzg8QeslQS8S+IGRGHkk+v7C6wpkkTyIPnkbZqiKS1aeipuhIWFQUYIJG02RchHkqn
Pc0wlA6tUKfT6Xy9Zl7vjmM4XptLHn926LRAPmkTFp0Z2vO2gmXwM95tnKxW5pPWI73Jv2AxVyOI
h5uikyt/g/ZohTkb0vzx7yWtpPmwO6oK/20jhJlaXa1bmvGmvAhDO/iPJAl1uirFjvmnGMgaThlp
+7PebbFWBWeJd2xX0C3YF6cE7gG71V94bL7fposCo/waPS+vgkzU2yJc2dg9NklU+z8gLfiXR5WN
WiAS1OqDBGlT18HQJc7yMd0jbTk+n7/OOeX2kakjbdhgpJ1PRrdl0cWBBPLM2RFx1ou6tfnJ8B1x
6dY9rPWIAKn3irT9mFh8PAIePvL5W/gPpR+RDwoWhsk6GX8haSXW0kqtqlD75pI4QaeszTe0yccA
0ya/7C/n0/mct2NnZA78mLSNoVtAQi5paGkaaptVVHom3iPR3/sIy1W+4d/X6pOauqSA5XF3gTR7
efLJeaWfUnuF7wdmaQl+K2nDqFK7Vfozw5VNSTuISZv5dgnOMpf1gCPaf4e8EMc1dCAt9WzfYS4P
FSrSJvfLX85hJVKM0WLL4rSNGMuzyv6LtCV32544OExPhjQfJ2Pa0ucjuvo6DA2Ts3bw+0grpKJI
1mizVeZdpyaE9+ShRUirfCc9VUKKpMkvF2iF+rqqJv8iBGBpm8zSLsftAN0kbULLhnZKns6lZz8I
wBkEZf07MlHRBC6KLW7trS3dZxkffUzQRBcj/avSj68JDRZRJ+PvI62RIC0OatdKXlmgKotfDguw
lKdvGLKZXcWcZXPvp+s/VRE4hiaS9pPP5RXwjuMa7Y5MJOwrnDbvTIJ7/GMvss5x4rnGtJ2O7kuz
eaXPDABC2477K55HWaOybQYC09itr4wHO2s686THF0A4XE7YuCeSthTStT1QoD1dztcvZQ04hmY6
fsBI+76YjG6SNpU6hiQ1NrQ12Ji3HAdwzyJyi6N4l5ywZToPVR++Ap9Ndjb3cLaac2kxMVX9uXbW
4P+WjgRpV2ulTNTbG+hThoy09CET/RJDmPMj8TG1s2Qc73S9Xm7UYcDSYtKS5oqPRTPa4pN37PIG
TXhAnC7X2oyZL5qWw2RnKFGL3vY1q9uO3ViJ417SehWIY62pVhS5SZ5BWiNmDsEj37vQ50upIzu0
t+pyiYVNrRGy4zNSMBkiytIQk3EWqj3n3a2+HwtIO5wS0i4bMEybT9qkod2yGfvL+40PKhdTN9ra
GpnaArd7TQSlGj1ok46rOveWtFAVzx8jtMNoPu/hpDVY9obcgBWy1hRMrTrwbIDLEW04UtCV5p9o
fEkNH/WNiXMM1Z5b2aF3j5KW9B53p+3AL0LaiLNUseJyuFwraGG8hX6bDvjI6dZ82nqft9/3qVgO
/UQFR/i10CmQAKEC/3iiw836LNLqKqv10LcveABxyne1Vo+LhatwxVeAJtjKCQuMFSjL4lmShfra
3/zZEdJqw04fG8r3fqcV3CjTKgztkYwRlbbN+D5M3YJW1udJqQrnbcdadLCsHOUVf94IpK2kvQIa
LMKkqX00Y/DdNwDXM6yGt0JUC7Tbqu+VYLOm67YTCDnsiLKRmaVTcphH1/PtHqUPQtr2eIFD3+V8
3NPySaviLNRorzfSXVViObK4k5kP3lpUzWF2fLmiE4XkPkL31rPw91ag1D4bhHHV5/HuMSOp5+mG
YMUe9wk3jyDRy2jb64zk62ZF1wmGSbYmGCtkoDhnz+cCRuPdCzFpW7P558dHtzEZabkT8Nw9iDlL
B2nP53q3J3z0fNV+ueT9zlqrvApOZhp7wZFt5fXku/uq4bsq8Hw+tNXzSRt6LizfqIK1MmnxfytT
HUwhew20DZOwGVYpzjLXGJO2SFshkBZZrUmju1z2p3HFJ5O08Yz9esvrwadLBZO0d6IbFCEtHfFD
pQ/bDu9m5c2TKfsUMCZRqVYcGXgQdSP3eNZ2iP2qjLUGZ61tq2+U+WCzWgNr7TRhCWMpZbeEQLs9
zRoDZ0+7Yj82IK3Wm3QW3e6i03StTEtrpNXctsctkY07K/fL1w23WRvf8eVKB781H87ZSkj7aaxY
qRZun6eQFpO10xkxt7N81gqkBawttant2Wsc1hIf2baThCWMJVaWZqDAyIKdhRJMwfvOMgeONRqO
5/1+YzwM8gSi4ocM7+I4snqP/sCf/JMwvuuOL3lC3vmGA3wLpZ4AgyZqqT6JtPaou8R3ocDah7z9
PUdB4lSQ2FkbGbpFo80aPGRM2xUjKyMsZSxzjHmhByiLDe15VXTkRgt1x3Pbs+l83pm080gbZ854
WwV7TpzN2u+5Gt6VgYUm/DJ7Rax7+yeKoIq2zIm9MqNexmeQljB18RbAw4Gv2KQF3Id8RvHDCAlp
bTujHt4Nt2tgKAS3MThhRcruicAxZuzlui6sXBbAGni3NRlPp+NmS/Myx4lEzvLMMZGzOV3q7hz3
HM0rkIiKOAsUskpMv/rIejxrK+lQQ3bsHz+WtELFs/n2TvxTU2TtIz7jvuMg/rGR0Y7T32w32Nqu
FYQFv5iVeZgaFDGzX3eEZEFoDHxt1J6Nx7N2XPFJT9qrMsfHA6ShqhnvKQwtGj4tSlrI2Ja4m3ny
DENbSVD7NnwuaYErdqi9v7XsMIy2WVeUQSYusp11mZvbLZB0HWPDGbsTrSxxjE/Xs3r6IAMukNZy
W83ZrNkeWXmkFZWOabUHSHve1VlG+NNyijYxxrc7HdorrWjyDMr6fiUDHF077q94DmmN0HY6b2+G
ZGsf8QF3H4lJGiwyZ+gG++12I2MbM5bGsrTOg83s3s4oM2YkukxjgKygN2w2hz03k7Rp35hF0aeU
oV3WpzlqYjm0i/GuURlEpg3Kayq6u+mpEKrxf4xYAPk5pAWujiCqC23ZQS4NYi7KtjfzjCsxt3fY
Rd5KjBUoy0uz4Bmfjk4GZ6fqn2LLgKBWG7WGw/bI9TJIKyeh+MQu6XDeJTMerlI7pwKM4hmZu0wt
H40vK5VT8Kh84RxiJWfygLFUL69ESMRd2cz4DUQ8iCsslAQnQgslD5kHtWUM3YstFvY6s+twqm+O
W44dBeUrISypzRLKXgZZZm5m2EpTOx4YxD8etVq9keYhR3WtY86mxhIuqZTXqhKBtyQat0iAqLCb
MAaURFmTMsWmeKSWKbEtE1nDvqKgVc2g4ZQKvBmDZ5EWiKLjx2ljsIa5VZM15pdJWmncZxXOs65F
Qz8ed7vtDjK2NPPEbGxkZUEpNUcQsWFsTaXu4MID/9jT3F5v5AqkTV+vuEDLOHsAscdU0/FkX/3A
z3svV7ycGShExmE8P2vOvCwHs2hiOx5XisYIrBGzp4pXV6NKAMUQw4x3DTzc0oJfDFX0MQikk2xQ
hckoTIlNntTp8bDf7glXuYm97C+XC2+AOl+vx2wTt4RSr9JvfndtQ3d8K3BdN7B8VZlW5uw6srOQ
OU6tCHrXd1UPDwx58ikLKBZ2Q+5b36NqqqlvKOuut4r57nEKnHAWeaKPk3oD/CQq6fBlaIS1cNs8
y9KGLGUbrEJia+MUcnnEFVi7DnMmyRv25bDnFpYaWO4WX87n03WTp3LkrcNVqC4p9UJiaq0gCLQ4
DzVIHp+szkrH7A+nVeo9mzj2rnIevqP5ifhPeftzlSjaPArdFAp7V9Js7eReVTpkNVOJBMXrKtCO
h3ArjFYN6E8i7cqBbp6lSZt7S09GCeM+RMIlr1iz0LeYKNgpZXM8tMuY6FOcDzsn7w7r2aERhuo3
H5I1X75laZrCOzbiZ4o4907i2f0prYvxiTBpK6sBTeicDjGhquwMv6E9tpQgcoCHIOmYellJafCP
QpaWHTRyle1nM8U3VCPD4RH9Crh3nkNaMsxKGhG0jS0no8oCF74hrLVtI+9+n/f0HfCVFnguvMZz
Ouw3Tu4anQ5xIkJ1y8UME1qHhfOWZaVIKyXKJN8Y7KwihB7a+DWV5C3fWimBmRxjRSS+hRmNhsrW
ldWAjIoZWqRNso2n4iRLnnpgGIMYofk0S4tZsrLXZJ/chwPdvVVWa6kHurbyfZrOyN6CoPGJ8vVy
2e+PRu/G/OfQgGefGTrKZ3TfpKaWrpiQlm+JWTImjhFzFh/EOvVm7zqIy1UxXNuj6SQv0l7M2xFv
kUKJ5MW30y9HZd31RQzt8EYBSvU95Rx9AgvDNu1nuscmpioVehmuV9zWlp6LEmhrZ/iwMfqBvt5e
rl/X6/XrfNwY3s32J9egJ2Ua6pcOwNQOot3VbIESV2iN5vT5kAAv0GLSpqcJ2zCQtKlgZbPF7Qt1
cr0840U5nXQe0yQvrb0iYHLjXMJNGHsHpzgo8hDkIs7C0Vdjad+8MB71keo+P6NuZNlwKLta0cBG
DzFtV/hv+FT8I8h43yGBE2tnMCuBRrM5mRSbrdHZ3AX+AHUNQ1uZoW44yEGYs454iURF5XiwZ09q
PafzNX2ks4GNHzx3tVE+BsV1oKgkP0qvEewryF3S0Y95OYcdH3mAQk4ZabOi2aRWgrPw+2r014dG
3ID8QNLGQa0d2mtaVuw7MPNWUWcUf44APwYPvYIfbqzAaqpLQi180roxGABnRcfYTHA27oPan/an
017RdenBN4Xr0tc1FxySYZYMeUiVtfPi1/DXl3X8ssAMM7W9u/b5Lci5IcnUVrAvGKPh2ObzSGtQ
EYY1tVhDA5ta064mrI3jxywJi29iZJJ3J1rnZqh8yThc8T245MLGW0tkygq9i4Sz6ef4J4mdzXXZ
fYwt6JHIThbHtzFJKXue+gq3IwtVPmmpsjpfpeUF38hb+5Jb7VfnH39otmJo4DGk5bVHe836vVx8
c0IuqpqwFmCSsFZ/YHmwZwBp6QIvPVwpHequDhuD2AUW/WIuOscVbSINqsPpclK1amgmEN5cld2r
jrz8vFN0FwOsrEfKe/r1ZZ2AJ3xmToY4F47cYU3quY89yqKYYtPHCPQE0rKlVSHzQ7y1vQ5pb1QV
rDV0E+JPc/UwB7njkb5tHKxCWlg3MubsRyvexCIljCNJ5bXcbny4HM5nXeG7jW26xG9V8s0yIo2I
TgGNVPwS946qSWkeQ4s8crz7HOIEEg0lxOo+7ADvA7JZf8XgcaQ1JFOLb0qWOOmv1yDpYsbq4A+g
4l0Hhj8RPOQHxYSjAXi9AyKbiyO5gWGr2TTfgPSlyXbwRUqtoj6rJPUIIlSK22s5COHjDONxT51i
oEsgi7jH+XvfU68vbcZwoWk//qypn0xFVaIFCxhF+m4PJK0R5X0oax32o3RBZZi1RpVIWn46A3Jk
+LNXj9Bv6TvEM4a2CS1woUNRD231Pauv+RmbSspKZhYmE/aKos6HhX1sRx9ABvwBh38H/OSG1izO
ovyuj9RblHT8D0L6KlS1UWzOpVQfS9rI1ML0+TrkJDEwa1dsurY81vKzIckiIjin/9zWzn3ILUHT
hOb2yNSdg6NNdTGmtYaTZrqUnLKrlJmN5FkvKv2hFg7J4Sdj4Ijmx0d/D8asOnuTtrfKx8kcdM1l
dJLoeX78j08d5IoOZUCKPg8lLUBoqcX3Jn+mTiNl8HJJK5wUdQEGPy11jlk4i5+2o9aw2ewFhLQZ
P8U1FLvCKJRNmVk2icdIe1S9ywcy6UZOTFr7hwd/H3pJclpItDn8t7c7PsbkteBrE3+7CpH+HwFq
WfGkrVXhYyewhb3KTyLt2uADZgOiDC7nop7OXPmk4Lh0M0szphg+XR3GkB0HWVprCJptLddDukHG
hxXQ+fKRSAp9Fe8Hiqd6oN34dNopKwktvkYXSFvqmE96pI5XPWlblFdU8KnPaqWMsy9maMG58qRa
M/YcKhn0gZSk+WzS2uvYbfRsuZ/xx4wsgPik+LZ36Gz4flz70SKOKhkCGLXHjcWiMW67FjIMO6Pv
YapTZWXK18SukVikAsQxzltllRM7x/CQcAhpV6Vuf0rP1Hl8JoaPnha0mTTlSr7DQqheC3eLoGlF
S/d82kVSQUMpwXMsrchafJNGadWpUb6HLJxUdF4D2/wua6eOYUBl1gE9iuF48blcLjqYtPivQ9tR
52KCtaSqTI1sUgUdJnevu3QDIABfK/hIIG1oZ+ztfBLSPcOeYGqx1SzczefFt3xWB0a9MYzrPiRE
KG3kIQnfUJnan1NFIK29MqOOr3m4TbC2PPdYsrhGmOppL4KhYziEso5vjVqTOXRqkMWznqPjk80w
4B++qKwsyKCLynGX8+lro84/+yB/gaAREh/3al1q06tqlJR23Vswy3NH7ZN0aFi0car2SxOU6JKW
rygwqMzFH9EhlYeTltckSSfjKm6kbcLda5epz5jiLJQ74fCcu43twkLwhs4AYTMLG3pIUPO+mPU0
f2CE4SqjVPvWWG03kq7yNkFZOg2YoSQzBPELB57vlLQ/aRK4GylRMy9uDQru8nF9tlfS8+siKHk/
XBKRO+BsuFU5x/g+dJ5EWll/O/5Ah+zOKXEkXjorgbimod+XRH5vewaZh8WesReMJtMuvWc/pk38
sxwYkCMyMmqV1ppItHIbm6QsWZ55zBBgaTjhQCfpH4SPOlxlasE+BSolQgjoLP/eFDzrz2hVM8T/
KHSb2FOYVLBUWoRGyPNE0mK7uhFmQMcRaUtykBNnFTvJ+PCC4kbrs+mZLGcM/RTtyZz/4D7Hbdj3
gWPabEWbhSHpKgsy6JFIxk5TJyMXlqlj59gD5Qt8zJi0pfqWKvcYcqf13nP9yzEhLfy6QdveRSfy
IbM+IDkDVZ/4A5tk45WoGVWerRVAZm5Ms2AGcOZBMRtiWaCs22s2Iqu4bLRxRIsvFnlCDTIY9Wns
dpiswNc4/0QJi4PZ8/miZx2Ib0BACyJTnk8s7bbcgJAnjCPtbvCLK7Y0/3fMDRvcY4Pdx48lrcGW
JG9E62BsNitzLa34MZ66TU/JWYcINsFo/E3azt0B5s2A5owxZ3vD8SKK5mhE65AoGeYhspITc7Ct
0nqgy4UM9GB8nb8ym/p60OKMfC0INLC0ob3elmvkrChZCtzFbnFFkmZ/EICovtuTSEtXcqy24r2M
Vhs+72NyJYsySesQi0mkJMDYhqbfzqyi9JsDg1wdZmVhL0+nHzuymLMtwlkSDkAvSVbFfQGK6Efa
/EQE5EDr8QSG9noIMx8cPn5fx8HGnWidkzzUrlzSIiZH4SMNAutRRR0FfxAxCuno2FNIC5aMTNWK
PUgNtBFSyM93kVWkRQQOjW11x9KG3VQqtD/rBZAvxheG8ty3tFFr1hB9Q8zZwCOTeToJ4bMaLDDe
R7sLlVVmuspUPu5rb2d3J3SgqwIhzNnRCH8OeMfrXbkNgD4XhsJ2NqjzCr//E2Z6GBrPIy1h7Wot
3ctjc0NahETWPoafSqhJ65N/HVL/wQcx0NxWc9zodz+Xn91FYzxp9zTEvpe+3sOUbU860n3bJc1Q
REeGKMjg55ORXQdpmTtQaGVdxhccyl4vO7OdPZbf96ATCnlur9Uakf5mu3TSoqiV4jWLq78SC583
RT2HtLBpcrXeSBma9gYGfuySslGKgJawEOQRMeGcgR4580Q4kTm7bI7CYa/GLmpr0llIKZg+9EL5
VEiGmlocCuSUfzva6ngknRTQsni57Ld63mj2RxCSApPWaw/bI6gFY9JuSiYtFUNzSy0Ovw6Ww2qe
ZbD3+YGkjZS4xQG91WYl9XxZ603URf90U6tKQzkOq18grmwai5tK3wKONKiouL3hrCHbxI/FpKXR
9ZW0y4rWpc28mPNjPHJWJB+1WfmjfDXAuQ+ScMgLes1mE5MWvGN7XTZpYW/cXxyrwkeTJNbVnadP
xpSuB3kYaeVFNUy1fLWRZrc/VpuoC/nprE2TdkAzUbSaQWgbMY+/2qEvQ9QvJq5zIqD7bExGgc9E
FvGLyVMKn87qVjvuvNnutYbjW2JV7w7Rg4Peq9ls0hpZjg7e8fZYLmn/CKvExOKLxqqZ5gfRGd3Q
E5Xax3UgU1VG2W38gL4+pmQhZqMez10FZQUP2WPwSWuvw3NOLFeFv2xpMDI7nncTN+9HY9IeJVa7
03aSlfmQRvKpZ8Jx+tjOjqfTScv1oOCz2pRN2j+k0PG4+LlXGWkDttTnOaQ1+FitXMFsh5GtlbJR
JZGWWlG48hYBZa5Pk8qsV8/ChHV77eZsOk9Zxe602QpYOJsgrREaDwhz3n2SG8ScHY6n82mzF/iU
tLs/0laJhksbTYTVmJXUrSe2bZhPIa205NyQZVTccLOxo9ao57nI2aR1mCmlINS1KIk1TNfAHfVa
bewVL5JGFgZ7xkN5sTs/XaqO+oCOeNcEqWRfG006i/5iOhxZPKQ9/nUQVoRFL1KaiWeK8cO9imN5
NxlpB08krW0nZQTdzWpDRsNlB/nRiM5GbWuJA4zhAtj/RpiurfawOetM5+nyLTazDeytWr7AWWF1
AIzo6T9NTrz3TDJnb42G08Xnso9J6zlgaDFp93+krQD9VrQRSFqTAEmRSg7I501RDyetyNpNcrPq
iE6Zyqx9mnusqwq2xEPWiFnFTMVUbbXbw+FkNsZ0VVhYwHu/M2knKBsn7gwmHvczF3bsgZ1FFraz
8+U7GHYY/jNpSLt/7TGZF8SyKUwlsk4TLp4Df1XJQfVWTN7NSdyIP0dEWuzZpRZamDsyO/Dc3ijx
bNS2lvnCPczX5gQI25j3u8uMrOlyOmuPAk+mrJRth3Sarf+kd6jjgJ11vGDUpHXhxWxkMUOLSTv/
wVv/4V7MtHh7VzwSzP9MiFvJZG3/eaSNE8gQjyXu5CWZDWf12mexNo+0bAQAh7WB2yMO8XiKGZtF
2LflojPpYSvrO/xKiZ9Cz5eIohuhPv/2j8MikQqy3PaMFY8azYAaWkza/b6aPofXE3X6OcY8QSwM
JSokAaoZ6jdLIC2m5jYZ6s03G65k8bTmKOlslKxFJK51R612czLOdIsxZedj6HEQcsbxVYp/Z4Cp
HZiG910vtgeHNfA9t91hnP0Yt6BIyy1t6aRdBiA+6DlEbGX2P2FvIygg9uxVWPRxTB7UPstBJvum
1imN0cDermFffCjbWoG2j3l06DdKP55lgYfcbs46jUVXNS360cWUbbmahZKesfJ64XPQvnV3f44c
eHj6XtCO2py7kxGt96zX291+X3bXPlAWeVFhcl7yx1eA/sii84gFUJlqeU/nnYxPJe1qlcqqDg1s
bGF6IEwM2EZce8QxkDfKRBTZYmM7nGDa9pcy3z4+F50ZYaxH18wWIq2pze//SYwxO2FxgTVqNrjB
/5i2NFCHIoZ2tz+WbOpcFHmIXoVqZmWh3/O5TGwBxtKLUsmBdnTWXvGkVBQb9rHXRiqrOlptiYO8
ymLto5BNtXiKB3opoNKDXeTP5cf7+/vHB4z8AGNhntXPZWzigg0M07lX4GHZckiQ4kGpJ/rm/gy6
oUxQAAHvePfjH/ddCDBnLUSrkuANvqL4aVF8tDVENTpIk1wBU0tfUc3RetFM7aNJa0TCjKDGskoX
ooPdFuLa8KnZKD2XtLypkVpbzFtS82lgTDvjSXMIjMVGVg5l80lL/mDemY1q0J8AQlqvOY3s6Wen
bSE6YI+94+Nl++Of9j2YxWUOejuX+ullYohEh6KIZ+wT4fXKtiUM46D2waQFGLxTCNvTdDO9tduu
eOXnmQVbhmziRs3GpLsCqra90cgNMF99hJysdjGZxaz0Q0reYGzv2Kw2RgY9DMttj+PL9Dltuz41
tKsNkHad8x6PB/KZ2C+j7e8k7cxy2LZ7T4gFinCW/FLNQXdM42n5YxbWGiTZtFIIO/hHNl5bCmtv
2VtC3Li3kez8Fio8qYuSIK34XoOB4YwK5nqXQx8yUPDx2DUWep0bTTLfw3LHu+Op1K15Q3wrI95E
QDSiyvz0UjAl3cSwm0ekaVFbC99V0c7LrmErNGcelgQyiO4MTMCsnHTuc2mCJPCKtTSWpdKYy1sO
OvuTviaZllZ4pwFykG4MrELNUeMAGUTuEZaNdIRYuD/pab5u0JkLQlr9YT/1AoAF72T9Drc+v0vV
reEi2a4KfRSFbC15SakrHwRYtso/fhhDeF8U/lfhSyzRekcbGjlpS5Axzza4EX3jPxFO6oL3m0Na
nbOWqlDpZnCrtPk5DJiksme5rVlfePliMtKQAxEtC2mPpzI3wS94q57H+uS936MStRgVDVyVXOVj
A/ipVtUZuGAJ9ecUfXQxF2WrQrKGvwNTu1rHrOU+8tOYm0naG7j1jvw31GIT1hpB3qxed2hRsXiy
bKTZEZ/b2M5a/sCgpCWGdn8u8x7pxfc1698r8cOfiGXTR16hok4+b8lan+9vYPwhZnrIFg08nbQq
ucKFuduQwHb17CRyhGeRdhCpwRE3G4wt5pwzUgtVdGcDNsoMMz1uqylpPZJBAUcnmj2ctKcy5U0s
Oczzqsq5PBRdjQboBbsnshgbuc+VncgC2YS0znNIGynPAGuVt2+4E+PaUqRVKb5P0vx3IjQEEIFV
OB+/PRWdy+645+vMuSGUDXoTSYVq2SB2lnHWXjPStpOX7olAXuJOfX3S9qO9d2xdwjdJyzorUIVX
5F1bkUyUk/CPH0UNTloMtTLwArN2rQpsy1k9HeP7Zz5IspbK2fhE8RGfve5gYgYwq9vrjQLLgoVa
kVG2gtZwLEazsNiL2llCWliRucGcPZxKTAX1E5Ojvv/yyeMAWahQiqkIbaHkU6WG1iR8KmljD9m0
dWUVZLrebrermLVlWtvHIE1axBKRCBJaZMGmTsS4dFH0kUwsEBV0KcmzbAxHdLEXiWjBO6akLVGy
cyJHfRDWvrjWDckcWXFj5ncpy9PLlUgxRvjUbd4T9TTSsrjWVrfSN/QtU3tjtra0DV0PQtKxpqko
lu9AiF1Olqly2HIgIlPl9pps2W2E7rgdEHlWshDJjkLaw6XEIR8XSaaW/Frepz8BQXweP+Gsjyht
K1+069m8vUJk7eNu6Zi0YUItiqMz2B7pxnQW2D6zFfkJSJGWytlomuVF9ja+trQgDKu1QFI5IR33
vhjTdSM0oqUFH0Lay6HEjXWpfj7rtdPH41hC8WcgO1JqsHEhYKQdPIu0sYMcOupDaIQ7amvT3VGv
QFuZsno0PuRpgWZppEmOrv1yuOgjKCqDQGsjUZ7vNiY9zFm2bYQMI69YHupS5ryAdJ+y7Evl1uUH
+H62OBKIYr51DQgLGK9J+lh/UqVWj+Z9AGpT+/Zm7jdrTFt7zQNbydjWmrlJOxvbWtITGTDFR6az
bFlsFLDZafQT0cLHHHTjEF02Ehna1Wa7PR4PpXYxKk3S6/ZEdb/LWcJb+AVZVUmmZsCIB+GfmYoi
G2+yIqOucdytV0DbNGv1J4giPxBq0nLWgt4jiD4GTPpxNGq16Mh9ytv9pGaWcFYg7RpIuz+cM7yU
p0DFWQ9V1kzwUwQ/sLSsAWpYs3XaTpyJeg5p2eAA8FbP+sH37c2Oa9Ak26P0WrNWRVphUpcQddTr
9YjoI0jIjTFjP1MpuY85kVSmqwsSpIU81LnMfKWKtMjy0IumkNH3SQv/tmu4IcWNGxmfSFrqH9uZ
Tt7SWzPWrlKsrTFlM5s04kFdMvBHFB+54KPi7BezYU/jo7t8Z4EQ0h5OZUr/KVM24CL6QSUKhD+E
/+1mCrgOtXQwJqS9gjXoPMU9ZhlksLaqET2KT20LLY0sH5VsRX7c0TwamaTlGlRkZQGj7EIp0bqc
d5o9V4sWgkmGlpO2TFk3pf4gCLzRgXhsuUbjaQ3tTwZ+QFkP/wxR5j1bHZarSCfqOaTVo7oPTJpl
/6z1/W67FWs/L0HbDNJGtMVxLSVtZwpWNl2qXi46oEMVSypHs1E8pN0dD5dTmRzx/HSnHylewWyL
TyUeEOtPTlWa64cf9BpDnzJ+VlU0OZsDHWzgIOkfP/bWjsLaVU7pIDgeqY8cz9jWv2SbSVquruxF
go/TRf8zcYN/LqYTIs/KPWPB0MbeMSykfu49IKOnvIEJk9lwGrFAfiQgRbI1s3FNN1D/dKgHTrtm
iag3Hzb6GM8krcFJaxihmRMVjXbHLQlsiVBjtb3IRZFDWtZJQdZm9kDwEcSVPz+YsX3/+Fw0Zs32
KMA2iy3KHQwGkmQ0Ju2aeMeHfTn3AkUjg7PxyjjqJJO/isZuyX4b8rtmp1b3uOJkovYojx+6F6kZ
88kCuZWzqon3DLis6OMkHOTHEFdYUkXYF+Y9tIL1brfZSnoWGQmpB3sCD0AWbyPBxxZd7bXoE8wb
0/Fk2BpRfVbpkgvLy9YbqPgcLodVeffD289sEwOyaqNunnYcHC/SvuLdE4y7w86sRxJXSGwLg4C+
XjIAM8eMSSvdcI+5l+n/eYeTaeT11kwHkI5aR2lkvu7nBdLIN/LI0AQFio9DHN42m8Nhu9UbBZrn
yxu94H3kkJbO5R3LbSN8wDiMVZ9pvkb22bCBeJAtsITmiTEJZuPAnoz0VXcCCrz7cfdxCaQ11dM+
DA1zu9tu4nyU/SL5KEAmayPeEsVHDFivSdTjUHIJn85IK4W0+9O2zGla7HxZD2BtqUeci9TJeJSG
sUxsM5lM465y/C01egoBXDN8nqXliAxtaOb2CXTs/W7LTK00rleGgNQPkcHaAU8lw4+eb6BHaXlW
cUV1ZGh32+N+f1mX3PT6g8pmhHKPOA/ps/E87hP7XksZr1kiZ2nqvFYV25kuuMdParDQI9rqppl/
9tp+d9zEJVs7wdoa81YioNLiRkj2siRISyNaGtLu94dLWHKA+CMZJXafl3vEebDSB8d428rMLy1F
O4ugxFXRFukMzPW4Uvt80sL25fzj0Ta73W4rs/Y1fORsU0tYK1BX9XX6HkaCtDDiU65+Kkb356a2
RhO40zRpsYPs5u831BKW1kNanSadloOQdR/Har/CEseH3M266CDbNxbDtMzjdstZK3Uj131gL5+1
2RCXU8e5Y9Z4vL/sSw8Qgx+TtkYxbbro4xYIN0RTyypbzz/S4vB4I+OzSDuI8qKMt/P8A/p0wNZu
eWSr6Gs0ajpEUICeeuLP7HrzdxBDWt7DuMmaaXwefsrZWk2yQYsLE2HEfm7B/mnFSdWpodEV0sfP
c4/JDWlA/GyGt55ZfbQlrI06LcKUj1xP0kYobmNlCLlj2EtLR3zMeRm3gYQhWZrHtbnvYSszTOUf
cjYCMqXkWMhqFk8OTBQN2E88xnsx0YmpdYipfTZpoT0qzByHj+BdjtBosSZq5rBcT5WQqjFxs8h5
J2l3u+PhcEIVtPdqHrIiHhafbmPy+3VKHkOLF3Rw3TkU+644uxr1RTXITO0gxdrH38pMiMK09Zs+
Snu1329pPop2NaaqPy9gb+9HMqTd7Q+XUyUN64HHRgPuVvcmL6/ikDPhjb7R0KQYT6yRf9z3MWkN
qiP4XNICY0lUG97+ofbR7gikpS5yoq/xJXqkvgNFSHu5VLPRWYs6c+9hrUXrKdWKjD4Eqgx61cck
YGSHLBMlsfY5NyWhbajfTlS8e9v9lrFWTCO/TmfjNyB6x5vNjuahKhqf6bHx8btYy+YGajrxcw9S
5d16bVqYQU8UX/j2NNLGGWQT1twUyLrPB/s9ySLHRdt01fZ38Vacfyfr8vaXc5kL8+TrT7do3LlI
g9C2qkN+INKk9b382m6p6EImipEWPY+0EWshg2wWuRUXxuYo+siyhFT9uy3uRso7Ph4u5wojqYAu
PS9uaak3jTrVHfLDoMq+1SiofUM0ffxUSzuIBs9g7N4M10V0wpbOds/7oxTGVtBH/h3MVYW050pL
niN0B2W5oa1TbeS7mKnOuk4tI65NSUuXoD8jFSW8I/OQbbtQAr1vHvZHKNpu862tIX/W4478x6Ap
80JOAeNsNJYH3vHpUvFIedOXeRv9ga+N9OK//g1LRBiUz6M6ZaKaK1qohYUVzyatwVm7KlbJWFqb
A8sjb2nVdqVMJNfY2sYVqmKkFbxjTNrNk3/4BbBocTeZthVFWWUvUqDh5PUsr07lzG9DtTC+XqT9
xATAvCL5hqdbWnoPh3poFCxlDFdga2lGKs4ki7SNUsm1o62RQv6LY+3UyDsue1ogG8vOTPMEQ0sH
U4W/oJJKVR/mI9D0VR0lXq18CBrUMtI+I6oV3WOuzhg6RXtqXfuy2x23TGWV+8iq4PZxR/zd84x/
nybsjUM05Pl3RtpazXEyfIxnAdsihzy+QpLmmn9DDurN8pIqUQxVH5gIzWakxQf6bNKy2zk0zLBw
MWMS7g4Q2fIWKTEllR3c6uXFtslPyiBsPmuNeCwv9o6vNSozKNDtNC3mOXu+Nfq8/R31x9yXZuBr
6h5jDzSEligSpDyl6CO8I0tGkfU+ha3I1Djtj1C0jRNSsZOcpG0F9la6VgJBTQG3js4whCrthnvH
pQox/gE2Y4IcI4p7rwXS1il7/PZmQ1Dr0JVDMWsfeVPHpB3oRiTPWLyttrG+sNCW0jYyt0riPu7I
74aSsEVYa0jz79Q7Pl1/Q5/C62AaxEqNipaSOs3Bg2S5aTjlkFYf0DIIMbXmHQMsvdX+cDzSmT2x
/sNYq7C3JZPXYK3VKsJ+m7Tlz9L+X9EfWchT+sUR6rWDzDKJpQXpMUJa/cG0TWWk6a1thPdMsHQG
uwOUf0j9Z7NOZJLjXHIOO358SonrEv8ursbyowhF3HQD2HeK60BgWOCrVsLfvxbLNuaqFVWv1PC8
eoXsk4Fp6GBpQSnwCUWf9Dsy1tqtew5z6uz2e+wlH3eQSsb3duQjVxzepsLYMIn4gWIqj0ok7Zqr
Q11KXQH/f0XbojtObg8hVn2kMpZ+aEBLlGfxLRWlkNbQQ/2uGsGnt9nxFinW3JgMbsPb9vbxyCcs
PSwuc5Xhtsu54w3pOz4djGf9xP9AMPPINCEZ3L8lQlm7TVy90BwMwNJaTwlqFbab3uW6XWTeR8DE
vODQFt/SW8rbTZxKTvvJmcS99wTzXil7xewQbAECa3mwrXwbU2yHOoJ3fNre5Yg8A93xbDyt11KM
R6ERgJXyuaaqx7f7ZKJuA4cdMyT+MShp++WQltgWXTcHd6qpzMITNrZHmP8Rc1LcT86wtz8zuVkX
Q+kT22nIcW3GO1HSUs5i0h4Ol7Nd5UqcRYD4Ykt8a7u/om2CY0qEo3wvas3k1jQnE1W7RP6nzkkr
mtof3Obpm158SzY6QLUs7h54am/3F2i24F7yRqZtZmLq+8xVXIlEEGvKfF0xpFibdRCqqbzTocL7
xI1U2jzE9Lqt39BV/Ab7q3zLZ3PCdEeI50Wd1dmkrd9TK4D8MXo2afnvoh6LgaGb+v2xQs/Yn/Z7
ztuNEN0KglJCKPkYm2ukIFpYytWIrjFi2pIyl9LXlnPHG9INdTmvCup9Ph6usDcOCoHIQ8Qwzas6
oMdB4x2XgmWNDWyOf1z1gacxNAhpiX9cCmnpyA+5Yb+hEdrV7P1hD14yo23MWrnJUZlTjlh7H4vT
dBWSTpGBXZN/V8LRiAG34VgWSn+ewfuOVzQNtdsfDqfzvZHDowDrIeni6MhnZIYJvbr60ygnZs0E
6a+uYT/pFNnGgAW1iW1uT8kis4kf+NU0nG+EbhMfwj5WAAK1Vcnc2gnaqrJTxUxvhnWVGCt6xGsR
5I82PR54uan7k3FvIF8LgbSyd1yVaEXO7YtqJZR0P767xtPz65Y6BnxYK3MQZaLKIC2/WQeGGX6r
qdNd4aiP1W1pn9RmLRjcRPJWpK2auSKJlX8rvYFEWE5Zga/sWDBlaVGKvNCApdqezjYN8P0CuhjS
rqlIOaShjpVEUf0bNqdW82l3IkDFNZxFxtZsViBCxwhh0CdR9HkmaVlYi91j0/5eV+dE311hkoDy
dhfJScUGN210zSTy6ZvkapquScJuBOA/sBaQlb1eIZgg/gzIuD69ANG1jbzjaJJ2fzk7j/0JF0PT
s7LNEXGUKy9DfRtj73sLAXFkUM+q1ztaG7qDWPuxcnfqo0kb0Rb/8k0lpKm/OZ0OR9KULGWT4wg3
WS/NIm8uSEpLhJR2kui65WC8xQeyWWNz67dJEBDgkx2knWNDrPeQFsbTtQrB4ybKrVWSlFQFh/UY
kBNTyCzeoKxfq+UCEnorwyBNUaWRluWQ8a+G6Xz7+d0K9+fLhWSlBN5ulLxNUbcAexMvT1V1lISN
aAv6rzjgNgLm6iJS5UrUwFIRLaShTsdH/WTvQAN7Wig9lRYDu5dWHcO7Ivjw/XsFYRlqO7axMEOT
tDKWaGlZSgZo63zbrnR7+uaCaXs8yrxdSwZXpm6auzchfjfn6yomLOPpLgYcBflnpWtzdqxD1nmc
dDbSk7Sn641Fvs/Axy1tcrjnnVeNamdeliJFPupcn3ZsNlTrp9LHTyQtcRWNAb6Xv3/ki3a4vUAq
eU9bpaLybdJVTlL3Nn3l1wrVV9ElFul6pIi99VUYzHh2vEOaj410hBCnoZhkBSZtBbljVt3IvK8t
2kZU45s4D5BRuns1Eb4adZ60Cmw2NeCnMlHPJC28uYP/s3+SoPt0N5frKUlbIaMs8pYxV6ifiv8n
v09RW8XYTURZia8SbY8rFPtW80FIklBG4tLK4lA70sJ4+Zr/+Cd6LwKSHc63tPBr/Dh5f6XuxoKL
O6k59ujzq26T70l8rMlUreOhp5M2brKI/l7XQ+9HvQRdzb6eT5i4sZ9MiLtdb2Pmqsibh5UMsaTD
LGzE1z1JY+8h8Qt/OsIW963TFo9QTznH5MTFtuN1hd6xUqBbifh74O7uVdQDci/yx2V9rgIr/uJ5
dZsSSGJASYvKIy23tPA77CH/tN1miLYXSEoRi0stHzW4241oc2XiFkOCrqJHzAm73x8A8H/858Nl
p8t+ZF8zTEO6DJF7DKQVGytOh9NX+ZsFijuO8fewEZl29rvWB0yC7ubZ8RkC/E/9/YieEW3iKou0
Ay4mAb83jJ+XAMfe6nI6UeIeCGuPR25ypShXRh5JZbYKfOWOMGPr4QKUPUBO7HDaGm4iFOr4vPUq
ZWiFNNR2R3PH58OPL8W9aBXmrGhpod4ALY/z0o/3bkyoaORtvvqMtPWnLA4MkY1tLeyWTqaPn0fa
AeufHzjE4j6gcP/u6ps9EHdPrF4cX+6k+qmavBmQCjpiALtnBvZCSHvB/55Ab8J2xqnOTISpKV+F
LEMLKoyX8sff72g8iL9pSCiLSYsq3TlUCHM61pMFsRaEya29iNM/CuG+GsAertJIS1jLm4NM/RHa
3J9Nf7Xbg72ltk/MDHHmRtTdxKRMG9UIW4mwO25gqY3FH3MibIVPvBx3odtJN1O7Zqgnmo5VhpYW
ac+nbemdFUFhyoqk7Th8IaZX22JmhPzGCrbzBP5nteucMZYxNleQKnGcMknLR2zhM3Vj9RiXpOua
h+v5fLpQn5VnlSPqxuRNclhF1VRBZx9FsEDT0+l0PpFfrtfz0Wmpxh9GNu2DUnZyCt1Q1NCezvZD
LsM9uK23oiIt6wwkkqM1nIORcSOepUJRfqvuuacE0IosCEnhWaSNOubpH/GTwlg9zM2aefb+60wD
3AOnLuduzF4lhxN9EnEhZy/zFQgLbD1jfH3twyDjBx6YA0dHyusaGdo1HRWAqPi6Kz2zM/KRVbhZ
KP62GdcJ9uraVC8gPwsFXwtq/+BJo2XCghCJUc8lLWuZjxxk8JAfOPnddQfrw/l6JvyizD2IxFXR
V8IxSVeBr4ywlK/Xy8ppZUZBTepIKMMOlaG9DkpvUL+rlz7+tg7dVIVI30Id9w6JmMTs5Iv/+N4/
IOx9amW1Qd9f2aERF2QeTdokeYW7N/qdMXhsSuNz6Nnb0/l6xQy7nIBwmLgkuXxgpRpS101gL+Fw
iLmKOYXdV2pcz9evf9ev89bwmjlB0IfLVnajVF5emu+BDsY9SR1fSo9oFxYSF8WR1gKPNhiIy2lZ
3Bd/31j6etlHfSeWKNrSY1k+kzmGPBqy6p9Gy0YbOuiNakgLf0viWv/RKivvc9cJN8cLUI3liw4S
GDcjqsakjV5yuXDzeibm9fqFgUPYjT1o3xCxdge64xAmAGkd6bR1vkha1HM7m6XnQVxfTKySZIyP
6M9hKDmVJO6Lv68lfV/db33EjWz0AIKDH75O1kmJvmHbJmft/VKj3ybtQI9DW8NwHv/D/1hMXH0D
nDjTrBFJLl9S9KUE5jyNuHpioBb263o9Y8O9320Gvcn8luxGO9TpIAbxIyVTK4kwQup4Dwrlp2v5
fmZC9xeJm2abApnhdZaQJ7Yk0tbd1DJDi6hbDANtrRcnLIG2sUPIIJdNWvHzdMOeP+XkGkPNWF+x
jcRBKGPuiXq8Mk6XBFdpehibV+IQf339+/d1sg2rXSTybMFyM0Q08ywyiyFucDCENFQ0SHu+lH4n
LRIBLdzU8VdlQ+uLS2jlHqO6z/+M/Xihve/3XixNnImlHeKolrBWL5u0wr1sPzGoWzRHjrk5XDHz
wMEFcOObwpniivEPgBl7WBtolBfCyrBMg4pvaUGgadLYo07rPcJMHja0+AHyr/zt76OoP55R0/OF
rJrMWUlwhmaOo6/X3W5Rh8fzkDvPf+Fy3GOnayG3U0/dihjeCso+iYa7ckir0zQywHyChywD/1Q0
37DX2/3l+kUCVParEtfL/rgJdU8b3VlHbsNCQkxaK3DdkRtYKdKKM3lsVOCr/O1sFo9kI4iT7mIq
Cm5k8Utyqqpee+XSIK7/raxTIyCysWSMz+PPslGd5xG7MKTGhfBLtrRR4ccZGHppCdSPznDkYhvo
6AbElrzteGXbVMBdc0eT+ffeeqGBB+w4vhaMWq3WKLDkpSvM0EoqM6drBQt8mEyqYFClryY85/gr
n/Kwm1eRfmRheDdzZQ2eoELMrYgKQ75WX97q2D9mm6JKd491nkLGv3UqaIt7f/8gWJJf33+8lMPS
QZscYd732s3msOdqEmmFZijCWdhIezpfK8jBJrsOZM1F2dKKkWuHN/5xlH3gj8V7kNt+YT28rvEo
9AybCCdxB/nRhC1CYKCtob+6MPZbABcR7Kzbbs7Gk2ZvlCRtNCoQbaQ9Xcuf74Fqa6KJUeoMksys
L965fkKfpu6ZqFz082U7IIsoJeHqBMcOwyisrYi0CDxks+7OVj4+rBASepizo/as02iMJy1saZ0E
aSGiXUfNUIfztYL5nreJJa2hSpDvU85QiSkqJN/k3itbWloG8rN7OT2qMVX1cSrRCXE4Z/KB7adD
6Sc70PanmzXbvX0X5g7Uux3sG7eanUW3u5hOWoEV56EEQytkoU7XVQUZWCu1nlX86lC8b+WvJQRc
XlhetccfWrmiz4S5tRxn0m0W1ioXqZZBWhjEx/8ZevAiQ41pdDxoB3WQ5bbG88+P94/+dDIKoj1J
cOZCRMu7ji9f+yo0idhtGRkZmXyWfOcK6yCmnpcQgyj7yB+EvhedXiaQx/Wj6qghOzRXJINslrJG
XZ2SoqP4g0HtiwgZCKCJ2kG+1mt2upDQel90hq4Vecd6stxzpGLHV1TFSlo+S6omn9ST7PvCAFKQ
1G+p4+1cAEOPiph7+TEt/TXhbNQEn94awtoKSetQ0RvMWt2rQmf/x2iRE4NwdtKgLv77fNYOxIWE
qSwUmcnbV9K+m7QxSFyu9I7kG3eZ+D7RPa5787EaLl0KyCs82YDGaxL31jCwnYXE1FZHWrjhCWmR
Y5h1TbPnoAfaxpA2HjXn7B5fTocjK5k6lg3t5XI+Dyo5XurkigJJwheHiTtX+JKfUCV9BaWoNJhi
qtDgmGFpI9Vkq46sdUr0jxWEhV8dbGtJp64evlwS2TOBs8gPhHGC/qwVSOu6CWnFpQLQdfxVTUUh
ZTElZopZZantouknKz6vmILIM60qkNgWfWvR41Mx36xs0zZ5Y1TpxKVRLaPtwEAvlUSe0Q4R5Lmt
uGn1s9Ny49Rx1FexYpwluy0v539hNYdMbIgUugp12oT1EcIV6T4m31f+of8Yd8z+R1cHP7yc+nUR
eOtVyLZAVkVazlofB7jWC6mAtJADXVC+NRqOo4fNstFUZqFWVDZ1ewSx49O5kkV5bzAvwNMwjIRW
TL+F6DN6UquU2PZIv6/8Q/8prPtJS2MJp3Y6HUt8O4VxD3IlpB0w0oJTWcPnmhp9j3jGyNN6s0Xk
LL7Pmz3RzqayUEDZy/Va/ngPRcdPZU2jx6SLsiq4veSN/IKWtv0NQ0vHCDy/dvI0Tkj6oswqTS3T
aIH2sYE+qqIUcje6FpwLouFs/Nf9SS/wpXhWzkLtSUT7dZ1nve+T8enJe1vFqobkN/ueUNSR7nfy
h5dYNCDi41tbpln6rXZh7Vi3V3Z5pjbTQ0aINn06pjev+prcxtSidtYKWjNhwrrfIb1QchIKG9qV
HUsdYzt72lR24HS7h8jAyA+WvGPfiwOVlpy6Ate57uO0KWCT+Y0l0/SSIK92DnKw4mWfCtsZwT+G
y2QhCBRr32cxAvEN5ABnx8IYV7czlCq0aalj2CZy/jpWdxOghIQbjnFZVWOGBBvsiVFrwqN+BQ3V
JEboG4bWQ4gN7NUuhP80CGvLs7U5ptYny4wHhl/TEQuKsamTphAPuqAEm9OdtdxE+6K0vAdU5C7n
0/lSobvlIkmBgk67kL4WqXgpuoRkh49ofvwalkFu4Fs7pvFDjBRsMXVrtwYzsFelhrVZrVHEQQYN
Lh8zosZZ5CHSWQpqNJmLnE36xrGhXUcl2hM2tGaFkkWdRAMfo7A3e5On1eL1eK7vo0RQa71aSOsm
hpRSNpXPCESn6MvfULvE24e3XrHJ2ipdZGJrPToVhQaOVruUHUVHo8fqeW57LJaVF7OWxu2sLvjG
wuj7gUz3bCv1/vOabsW7lD+NJgNNyCqzPFaVJ/AdyIF8+mTpY4lrWPgWsjxZ3gPVru9nGq5tOzTD
ElmrJK1DTS1oGfq6btWRte9Nj5hZ39fc5lSQAXvvz3pupAulKzLHfCLvWq1vqRXcMMBeHpAdIqI7
jfDfVHoG96N1q20RHGH+4g6iI/LydzhVHr8S7mZFBKPCSlPIjLWWpVmQHhmoF1xVClLowcfp43B2
KLrG74txK5WDEgJaVu4BBfR9tV1f3RueIruPaRA38xK1W/iD5ddyzjQHfoqDydP1kPAgGiYleeAF
tTvnz9U6Ji2w9vnMzWIt8qhusIUQMgY106sdElEZB7LGvVlDeKS8NyYtWWAmXaIl/Yun87+qn9nF
EjLubDb2qDMsZ6jQ6+WO+5R5OaN48Gz6EL/Bs+QX+DU86eaW5aJqENYSW6vhXzBra1WznfgGpMvA
zIqNixif0/Yo7l2kuj3pzDHRhbruqnYfOoVW5rH1rZ4oLsrv8FebpQ0SI0pp0sI5imfVla4R8TZq
l4p6ezO2K5CeqZ61sFbD0gJN0yAXMBiguszr9VtgSOH4tKDFZ2cpoDxrSYM9vKsi4ixzjs/nf9W7
WVb+ymWBnZitSMqqEpP0WlMdb3whb14iCj+VLImVPdG9oGms+jUPTLEPB8kos9rhAYezVsO8xV4y
JgJCraovDsZ8RDdYIohm21Pxtv1YTHr4We6ofGOh2kMD2lP5O6RT6BdykC2yzYfOlcqKFjW0Ofng
z55s0pIvSmLH6X6S+vnHbwMbW1o7LJO0StaSci1hrRZ4RFhcH2QtcC4PHUsfEM56mtuaNcRh0uV0
MtI8YUQg4mxSYgYb2uumDl0jWpFMlI+ilVtSSGuhuq/OSKKhPD1/NI1/T/4nZfU7iZCglpH8WF+v
Sq/WqnjrRKwNsLHFT/mBEaJqlWjmbnRc2qg9WYhR6WdnCBrH8fEnOMsHBQ4nKPfs69FKFDUgF+4S
4ikpv5YWJx9t1dn4c94DFnvB0nclE1e1FI0d2RvbjllbaTbKp2usYJEVxIp6GFaxhYChCzN4lLTQ
tziVDE13CpwV9uOJnJUyxzBF+1X+Ololxiz3ckdnH20+qK0acB5SETw4y9Bx10zEulIXXks8d/Ky
umRXRIy2a5islVj7dOoqSDvgHjJlLXaRYfnOyh5Vkv+Ye7rOniRQm51Kgc+y0expnlzpEUgr2Nk9
GNp/27p4li0IWaHNuziYoa3fwMtNKB5NbBURSow8id8lRP6MtLVMmvvbVcLWlmBv81hLaQu7XmF5
iBmW3iO1bDk6k57zvWDU7kiUhYYKQVmGrN2VOBtnjmm151yfGz7ALHTuGDG1kE8nXuroJN5A+tHE
XV0rESJI35bs0K7nqXftDWdtiQ5ydkejhY2tS2mLWaPD9tegTNp+zizHoRlt34JgtiE5t8vGhDRB
ZdpZcU4AMsdfVbdViPCQZaE7WEvnr7xXFHRLnaTHd/7N/GhZHvl7KQYTJ5voWEUVB38TbVKsrQFr
Hd7RqAFtNYuw1sFk0FGvNA9z6vqRY2y5OJjtS20R4Brf4KygmXq4Xq/7Wi1QzFllo6Ysjmhfr4ER
oHgyCV/y/Cg9Lm8QTJy/X09L+/ZmEtaGJbNW6SA7UWCLeQu0Bdk3HfvIg1YZBaCPsUY0mclsAPaM
h+OFbGO643iNAFuRTRmbCmipzvH1+lXpoIifmgj1ivVYsHsWkeGXVxHwkqA4G/4lL9He2FV+G39B
BcdeAJCLklhbtQANdDSCgxyAsfUJMczQQM+Wt++2yHoeuv0ASrOJnPHbx2KGXWM/GsQbkJOIORvp
HO+4zvH1fHnyQeeijxkXJJyU/BWtyfsc/n1Jzirc44h+06gWneZl+upUcOxFoK82K6rOKLC2spUh
KMpHQV+jRXTfBlST9InSFouWb+jxY0Nz27OGnLj+mM+g1zjOGg/ifuNEV8VufyTFnut1M3/aERcA
yf4iSz4Gov0UdwtlzOyxgXDsHr8mZ/Ms7ZvcOSL6x8v0xajg2AsBEVO7MkXWVrF9QHCRWRqZdCMT
lVV8REAMp/WEGLEzgpNlH42DOIVj/NYft12x0BMHtIYc0PLB98v5fN1UWuX7ILSDpmMpthjTXh9P
7i+WYNHYF4ojL8rZPEub8DaQ8JVe+oJUcfBFMHegWmuXbmuVHjLjTlz9IbEtsEUf4ANzfLfx0JGZ
7izwBjpPGJP003A2T/RD0KSxL2SgJEOb7ISCluPD9XqpVqAlIJYSCjeJaqMGay+J64uUtPXYQC3+
5lfMQRHkJKKgGhu3mIB8VjQWoHiAVXL0RdAJwUGWWFvG9lo1aamLSkNbTltqbQcGoYgftB/lJy/H
I83XdVi7yQpObq85biTiwI9+B5LGMmf5SURz7yspcXy6ns8VbQHhoOpklH8yaztEtUHSRkqwljX7
1VFHpBhG6XOKvyi1RAkdxh5K5+kqOfpCGG22MWtLLf0oySv7yMzYkl5fHXhrGqbW/rkI3Gen5ZNH
EynMIgd/nDvCVrabsOSf00lb2PohUTbiLE8cswotZI4P1W6GDLx4lN1LNnK3aLeTuhUZ5sPBP66d
GuEdGKfOSlCpGEktFD5r0+z7SPOc1yHtm7nZrOxV0kOuirSiCg2w1qXmlozC6bDPGdM21K3h94n7
MW0NTJ2lnoj+k+dpxDFO9k2+L8ZDuuNdYWYl53hNA9r9/gIB7flfxeEgH2X3LGQpmgR6iDnISnia
Y9Wqwnw38iytnCS24g1jikdYZSdQAJvtel2Vrb3hI1PWQr+FR3nr0DqLjg9U91qdO0u489nIJ3k2
hz0dSCSrua3WbNpN9v4sF+P2SCP14piwA0UOyhbs7OF8Ol//VdxkP/KFNmP823R0Os3OROHvrEvH
9HeRPiXhcSyfN2u1kAXdX4G0nQ2Ua6thbVZkG1dt3cB1XeAtbZRySHRJaEOSyrrvNlP53iS6jVnb
ArbCiVELiz8A21jLCtxWc9JIusXYMW7MhiPNS+afBnKxJ57sYQEtVHu+js/6SRUESw7zu9NS3n1N
pYgSdjrqMZj0E/gphSihCbwRpc+VzyzOZIz6SVeI8FaYtdDPSKUsqu6OikNb2iLlEpCmZBLfIhCV
iKijw8JYTwtGrcl00e9+fi4xPvB/n5/dRWPWbI3YDIIuvDdposCPBLfXnnRSbjEswxsPe64lzs1S
ugrNi6JvTJNQFxBy+7puK57pGskLabOlJ6Yj3+Oj7+R7rOHrM/YNlv4lCSleAfBBUHZ04DPb61s1
V9nx4cbDgW1YG9IKjY1A2xEjLphbMqoRCQ7zVkJ8wA6fpacghV7kDMTPciIj7mEb22s3O42UWwwp
42mzFVienyzzKJxjljg+stGe8/V6LLV9sZXeyyivfocm4rw3+OjMZuPZbDatWoDucejzPQpK0rZI
X3WeWqP/EhqU88FuRUgrmtoyk8hZS7p4RgoTdgRgBpcsJQCDS1hFv1+gL601G9I7O+wxAM9XsN8j
zNjxdLFM36rv/ekEglkkt1NQRfLMAi2MvWPn+PRV8uIefDaOXAXrJW9A3/89fCwGur9IEGqT5nn8
W8JvHmm9ruU4rYiOfWSmVqrXltLRmElaqdeCkrYnMddHjLmOk2uy6VtFGw1ixqouRbeBKRvQMo90
XPHBqjgLSajTGdoXS/3BzahZEB1ylBQWfEHxiR9ilJJpE5+kLuksyfOOCW3rn45rrCGs5cMDtSj9
DKLokzKNWNseoNVq9Xoj5i17JMyN6Uvtb/QLXV/t89LvqNdqN2fTeV9hYjE+59BLYSV6FgdxLKvm
LB+hPZ3/bcutlkQplcgnnyU3btXf0Xs45slEk+eJASpitjSPtfkxRU3Q2NIUMmdtybRNE1ZP8JaZ
W8zYdnuI0W63CXdHUajrpTrgyV/R7ir4zvZw0sF8/czwFpeLTpP5xUnOJiibtrNE5Ph0/XcsOXvB
e/99i2dIPdmKeDWVKHsu5OYmkFQVEw0jyRlRAb+gDjKaN6FtttDQuJJZWxZps8krjMgTc0vIN2w2
JxjNZpOQF8zviGaYAzZtQJNR4FT34Buak9l42lh01QYWgCk7abvEL5Zk2xKsVXOWSVV8nUve2DmG
hefcqiCg7diXV7PCb+shCVkmesmlvLLh9PxUUSjxrH+VkMJcQ5MFV42qIhuVQVrebcGtbQ9IO8Es
BMwAwN4mtb7EAIM1pvYYvwyzddrA9jWbr5B8aownLVfz/JRjnGBtirOxMPn5a1+2T6X5LNNJ6Wlp
XW5cY0dPcJ3/P0gouOH/xLA/yCBtVN+2al6kjTA2NmvSGmXbppyOqpy0g7hLisWlxHSOO1OODsE4
Av7DFLg6h9JtHl0BH/3GZNijlE1mjPlxJTkrKFWQ3dHQVHEZlPOTipHn4sV3YtlHVQPQrUTxk8uT
r4K6H4xMM5Ilg/XbBJ+Fpgkp5JWiEbnqDinmJDPaBm6vx1hLeDlfYPQ5ugSkx+KjSKnjozuHUFZJ
2UQ4K84IUM5G8jKk49govRxfiLOvOhf7E3RFS0tW9yAxcukp2zijNuRXWsjbANaubUraSuYHckgr
mVvsJBNri21tAxtT0gj1UYijEt4/51NsY6HDWNynlUlaca4nbl4kjVCnr68K1vbcVH1KRnP/G0hJ
SSosKX5ZHdAyKlv+Kw1MfNjbDba1a0bb2EWugaXl5jZqb4SUFEswzcEHvpOzS2xhZ8PWKLBoo4ZA
0yzSZtR6TkRe5p/5pB9KHgooLHr/R0ObWF5JXWWRiXPREovsJqx9rfn/7nq7oWJvFZV+bpLXiYcJ
Aom3i+5nYdouu/1GZzJs4TjW8pMVHqFbUYYyB0Xrs9fzv3UVbUe3ldqKGNpG5QvPngALCTEtKf5J
UW2A0ktSyOvw31e7Sep+tLbbzWa1rpy1N8wt9ZI9zFuo6Ai8Xd4S135ffvaxiQWnmA4SJJsVVW4x
p6wyb0wajr/2lbSX3+asV6B2MfL830fbpYaEq0DmZqXSq6cILYC1TjCv6Ii/D2ez2dDeqIptLUXM
IpW5jVouIMCdQYBLksVqT/l9iQ3sfNoZExNLvWI1Y1V2VlGfJZwF5/h6PW+qqYXetLSoSHhGHMUX
qXEUhybVvdJNJsp1ZB6yXrBRuzvAtnYdeciV9DQKyDa3NCsVaVxA+ZamlDF1SXIKEsmfgG6331/M
G9PxeNbEfB25GidsclY2+zjy7Cwm7aWiWvzspqktUu9ht/Vvoy2f5InJKxVyuryi7UVjejhWqlaQ
79sIdoS1oovMs1EVmVv9hhBcJAUH3cm0swJ6pjhoyyM0PAYBm8jlFjZ63xsfL1FWqM+Snorr16Uq
SaglVynORuv2u3BN1aeLwpeLOUkgW2IWeS69INrrw2u6r6r0jDE87oitXVfWiZxGpsWNBngQfVpi
9opDtfFkLR2fR066Fqsirfw3BlsjIMy87460dREajvfVZS68hDFROHw3RdqGdACeFEZKOeiy0AM/
TNoVmHCIAkTTVVQIoP7DeHloE1tLK7aVNjXGyCGtwFwa6EY/IaFWh9ggUNb3pz+P/Yb2ljDOUtc4
nsWDZe9fX/sKDRRRJsud5769KiAaCwItuJKOuxwEPhINrSROTuGSEg8oRKNXjw6sHQS2K6BtHQJb
/TZpBd6qoSJpMUtrCJyVZ96hDerrfK6yqtfwmDRZJiyyeCtH+alPMqv0CeehAt70CyHphaC0NV2M
NX84rbm0TCGYG1KvVSSRq/SR9ULkFfibbVcVPFXDMATfeJWc68GcPVRrnJzEVE/KOSacBiHVrDSy
GyVk/CwRuNdFIM7Nkgv1umHrLcwNno1axba2kgmCBCLaDdK/y/srNXVvwBCzxgnf+EKH8f5dKu4S
dFF+TEsNsUMm+NS0pSswo61cr9ZZcAM9cUQP/fLpYm17XG/ogG29aCtAQcIiRC1IWc5ZSlmxPMsW
CZzP/74qXiWAYeXFs0yEge8TUFV1evxVPlNLLv8UnoqGMKEHTon2MBmZGuatZpsj9FnQim0isq20
+pPCoEDp5m4rS3SVZTMrcJZIy5y/vnbVZy96yPOyBY88Ps7CneiUIEPkRIMp+pXaNGMmLgN5tsfp
UXzcTstXgA6+QSlrhXxULQLbkiBnoIhnvN0e93SsB9ZG/9vUofuPu8C5YgwRiZEvqzK7qe+p6DSe
ihnkkYeP3Ck2QfVsR2lvt5S1tr1OuchVM+r5EDNQ8fQs1zc+X7+uu3pMcFG2otyElGB6kdj103Qs
T9ouXaRX+Q+QSqipNLK1xqxdQe3Hrm9g+1gMRImKNGeh1nNhyz/Om5rkbPpkE03kCOdz1if85msy
+NafePPPq4gjVYoGizZqmdTSsGXZrVebVTytV4OabRmQwll7Ja7roXb2+m9deQ6Ko09CNnSbsn40
Mep7k8asBfoqKKnrXfXZ1B/RKILn9W6/unRMw+NxQwcIpCzyr7a2eoZrzKRSIW18/vev4rXRMoi6
ke8pB1fU3I0pnhhR+38KXdyBZdTPAte7ZPnNYvD3ULHdZtG2anY9A0Yqa7xhZpZNCJyv/841yxzO
/JtavqKxFXJXvuxV/8W0N9D0WSjC8n5VH48S3gEHtrGx/f20VUSzWz48S9PGX1+X+nX7NQrlofhU
EPLi/kdZcrWGGdE6IUBCCxr8r54dVj6+Y7cbBWt/p4vM7WyYco3Z5o+vr+umhnV1aCIuUPIRSrfk
1YmGqv+pDFxRzKUAhD7taikotfRWR0zb9Wa9sVdSW2OatgUbeusG5XgAG8Ojdna3P0B5Fgber1/r
+tlZii7ZD0JGSD1PZuNtNntkOq+e7l5N0ENWmrU1lbpwt/vtZkelzHlg+yuNrSG7xryjAoZnqUrF
6Xr6+nesswcZOGxa78YG1rQFpr/UpIxVS0SOikRap6ZbVz7tw3G73sa0TfG2aro9BCJl+UhPnDUm
nYvXf19GPZ+sEQKY6UE0nVyYtMxXrmlepRYYU5IiSeWRLKiu60PcP+xYZJuVkHp53iYTUIlo9nK6
nq9f/75ewBT16OBOsRYp2W7UMlivBQKaLiZTjtKTrsZbMbXNcbfd8oTUr3OSU45x7BlHGSjoXFzV
pqMigmq8vUX2XXro5gaC6O6jYTCqR2Nm/fARp9gTQS38Wr+bgqFtHPc7ibVp2r4qb+PKrNgCRYuz
x6jSc/13cuZV/xhSaHlKAcEW8u7MQ3l/7VCZGCIey1IFZYmz9exmpBgPtsct0aFR+cjCtq6qKXgv
DLHKQykrFGdpAopEsyd0Swq9fExBAFT5lbFXrLFRsLV+tijN/xoksS4WyhgsxDZj1mHaKwPuBmo/
GcY2dpJfjbXcMY5Ks7FrHDdUYNd4XcdwNq9WOLuv4uP5fxGtCo3bV6/OF6512B+PPLJdr21etZWt
7WuRVqSszaPZ9TZuNYY6D5D2WMd4j+tWZPi13WgGPstVjrw+iIDLPfYXgVvkmVf1Qeah6+Ag74it
0GZLnGQ74SMLBaDXoG4q/0SsbFTnOcACAWJmr7Vcpz6PqThTv2JhUWrKwzyCheXMxV/OeIv/NZYF
pjDw5atf3CSiaR+wsaXdyEz4TWlta+8mC6ptiZwxpSwzsxeYnP1Xm9nZBMQbJ+sI+4y2StZGMwM+
ep3t5yWiXVBaoObPu76xI6zdbPJj23p5yYNI6jj6K0N0jBWcPZDR2ev1fP13QfOqL7sS8Y4pIGb2
6wKW9FTdftTKIq2+1cYKoXl+gRXAfs39Y4yGs93vd6QbOYO2NYxtVTvdhfanMOUZ02iWKEFd9zWY
5AgUmd2xZDK1PEsJO8eya0AeiKw+79hfFQ0Peo2LyIG8wBNvaG7B2O4IaaPyT4aTXA+oOCtkjGPK
xtEsFSO/Xi+DGgw6NzzfSqkkiHoTN0c7WyjTzyONyk879JfFiK0lK6S8VfXB3kbXOZ5IzXa74Z2N
grmteZ9UbGS5WwyUFTugGGUhA3X9dxhUfbUB+NaxkqzU4luG7M+6NQrbVmei6Hc/79BfFVHavYil
fYnr1zcu+7j8k3CS60vbKN6WjSxtgIoajZmVJa3GTi3GA1osXSTWYztyigRaKW69TU91w0Gtp5ap
8Uoxvqdv+2VayQJ8e9Nei20U2yZ6kgtkpYqu1LkPGe8qMtYUrGzKMYbaLCn0bGsywBHfHsLfyUNi
XnolnAIz1vYuaFXgb/xrhErCtYoloF6MtG9DY4NtLR3+UVnbgrQtDSrKMr9Y4uwBO8anr8vX1/VS
l/Y0sSeHG9tA6oKlI+xF3msZwCwBSybj70L+w/Zk/Bp8+Cgx7n4TVR9yUfS19RESUscUbdXmtlaU
jf1iujkgoiwb6Ll+nbe16RCSJE5py9wEeVJmiay+KPh2H5PoO+teYKwETUxZHxW3td5LaVh++uvL
Hpta2pEc81YwuLnZ5Oc4x+y9Mwib8IuJkd2yZgrGWEhAXbej+nS5xLcP6VAHotGFAgljUPVx/g4U
EX1P0vZV3GOC3vZ02O+PhLbJVHKWn6wwuQ8jr+KNUoxNUnYnBbNkbvbrWos1PRyi8BoQNXjzyAhP
woNTzuj94T5MCxRm06a2jqLlORiuLofj4XgUaLvOoG3p9VvZxKZLPDFlD4yy5zMsnT1v60TZt3ls
UWGu07M8hGLV4pjPtUh0vzhcZHHJj3u4W4NS/n1obS4w/aOmbZq4ksV9Dn0NI1ndiQkrJZ+ijkVO
2fPX17/rqmZqix0x10vuJis5ugO/+esd/jE+yIwsm1S8I3/8Ut4xxRTt9vu9zNp1zNokbY0EHk9Z
Q2KsyT4/QdnNNhoMiBxjmA7YanWbwRvLz3yPDWRLmSj859qKnrwMJmTXb8rCongBMLJUBvgFuhjT
+AhCEAbGtD2S9ZggkpxOJqsdZRVrf5SgkgnLKRsxVqbs/ngQYllM2UNYv3menEK/x325PyHFnyPI
6PSklCXX2VK/pM5D8DmYObsDNre7vdzeyHouVhJxlTY3h4YFNrcbEl1lvkpxrOQXs8EAGJq9Ys6e
rzunJt0UEsaK2yQirU8V2axXfNjXCg2i8o4U5VmogRPeJnb5clh+3Xyzwgi258vhgI0tdZNZfyPP
JktNjiJxk96yQMJihlViqxGbciHvRJPFqwRl91GTMeSfcDD7L6zlioe3WTZp49Gd+jkIr4VW9mZu
RBKA0UMy/QKn6oP/AVqrPSkA7UifVMzb2Npm+crpQDfP/vIclowEWyOXmDrFnLEyZePC7L9/Z6eu
KcAc9xh53NhWfZCvjXeBkwqlAKr7QbJ9KlnamiUu78TEOZ4OwNtjzNs4nRzRVjS5Eows8uZBfguJ
sUIYywgbJ5/AL4b90KQu+3VE9e0N6udVDqke4J9z/COMfdbYmTW/yNIGnvoVVR/+T9E2d8Da/V5N
WyVxU9zNNLz5hE3wVTSxEmWFhDFtpTjvUF2tLEEOZZl/3Kn6EF8aLlkdgNgDMENJy7GafcLr1Ndr
oJHwQ/Q1e7u/UNpm8FblKiupWxDCO8h8jQnL3GLBL6aUBSN73Rs17yXKJi2lLXr926ZC9L3YL85O
0yPr/Q0qPr/Q0BJMtfWemNujxNs1T0wlfOUEcwl5s5icemmarzJh4ziW2tjDQazKYhxWVq2tLCBv
uwcZ1amva19/DPPraVTx3fJHb29zmCGQfxaw2udF6z0pdJzL9cLMLdGB25K527WcmRJ4q+RuUYhv
IjM2MrFbXuA5XVjyCTbN/vv6OmifVV+s2xjyUCrz/qpjpeo1kDeBByvywPxaiIRPlm9JzjMZbPwl
hpZiqB/PmCHgiwoGN/KU17K7vKKVmdsEtlNYieGrZGBJFMvCWGDsnuaeqJE9//v3b18H+aciQMiC
WCqns+62g/wip1ouun6u3KLlOcRnJle3DwN7iZgX87Y2A5wPQddanU8kmUxoy+u3lLib28S9Bfot
wvdHhI0Yu2NeMSyFBr7CLneae/r6Opu9+gzf3QCfw8vx5G5uSf01btwD0feS/m7C0tLrTsv3iIxW
ydnjvCHmFy0EvVvGZn/C9pYMFAi83WxE4sq8ZYQsyFo1YbmN3SVt7Il2K36dtvorXdM+Y2Zu6Sef
lOBiz8s52pfBR46RpZSEViimxgO7GryEe+xlR7QfN4X2aot+29jscBgZ5aWIoyyZ3NhblvlbBMJ3
sudARFfBKT7gz6fNitgr/vq6ni8bp/kyVpYguDksBjfYNOcdrMjN+wMHAjPr5GWMsWnl1wxGIr10
y1TGW08c6zUkGtVYzvTNbo890wMv4CqJK3E3l7+J120kugqEZcUdYmTPZ9JG8XW+nvbb+qeL0/B9
nsjMsLPEl8uezusiahhe8NSfhh6lZfZzEAYEInPJEwrxN8BvMqbfA6S9uph0I9hg2pwvh33MW8pc
RrRtxLwkdXOwUdFVsLBCeQcqslcIZf9dQrdWA+5FMb8pggLVB5RJyqh48RfZRuDTyZkQjWWAPN5+
FlviDGM6R+ydX0zQIon34WB3wo5pZHDjKFckb8zeLP6mqMrJKtjXyMCyKBY2BXz9g17F1zU0Q4Um
VMIskFeo75Mu8qJXlHzgtUU//2KC7yIMkCjYjV+hFIyO9o/63ksaCBEfE9/eX7GjCiFuTF1ayk1w
l/NXYrFMVZGvhKz038OB9ihGxR1iYP/924Uv3oIw42Yhd1GF5ytVjKUXlH7o9cQoh7LYLUGeI5Tw
3eLD76I0wW9QE1k2/XBzwFQipIqYu2c2l3M3TeCtkquxeWUOcTQHAMUdPgvwdT1sQmv++gpKDlQn
rFw3GSqJiqGT+P4EW/sncUGQm9bD0a5EONVFV7q/TSR8Hf2SaGTe9O3tERP3xGkrUjdOU+XiGCMi
K6Erpywr7Vyv19NhZ1rNedWn/RAMWXtstqmlVcRUvV+wDfBrFcdeP+RxFl9JaQaj5ysLuuk3DUQ3
GrLNv2bO+XM2ctbAXGAXJy9pntrv92LAm429QFYyF8scYux9n4gMxfXrfDkc14NW57WKO7lYClPv
WXcbbOpKjMTLqwj8v50CBHlXMZlhUr8u5bJ0iYqU+Da/6wnZb3sQ4X5dweRSyl04BQ8RGfcZiMh6
oQM7hPwQw0JL8fkfZJ2+zqE7+0WEpWjBHHYObSMNc+F7enLjnef9+ceAvCdfIsLowQj87fGeFhLa
Lzx2tX9dbXzZDAZbIg5+JSaSkVegrwqXCKcTyw/TjBOMAOB//l3XyB3/Or5SLC0/Zz05FHYQXXwZ
GdueEAXT3/yG9MjPoWVdRN+fJ16qztwnO56Q5VlR6EKLPvBrSadTLhZNDZnr/ZlSl5KX4qJG/IIz
4yr+Xmpc92vDc4cvn2jPRZCbivIQW/qOLCI31pXuNkQmVX7nfXQvMvXyUraRiHSlEwnyizqQ1pc7
pijXX7fMeAvdievrIQ50L2TK9Ur5KxBYBmfrlVnpw3G7Nga+2/k/bG1sJO8ekbNczUjIV4mi5khx
u/1fQdvImMYWrc3CL+nUUcrQkj4quYIYKLwf+j2/I4GcheV8Nhz55mqz3XFpU5ihOxMCX5M404rv
cbfdrgZWq9npvn5RpyiiVuR7ZPApIFHyqp3sDwY3hR6jLIk6vHRYNeWdKSIZ5VTVh0rvjWcYSjuh
SvHRbXQmw5ZrIcNepzoqyAprW/eDUbs5mfb/D7Y1hSmpJ8AT37vZ35h4+OM78GVleh+LLlkYgNjz
j0xUKId2GE/FxIAnz/AMI5MtX2v6yrLOp0ZYfvbnjel02gFMp435orv8XxJVhhbdRTl5qTSIylHV
x14XuJ7jRdu2SG+xak6qT/J6iZk8SbOW1MbVPwTv73L/IUbH0SInuTBnqUGo+tBrA6IfQycBYN5C
nVWnGQK51i16Kw3YAAT0VzIW/cnb/kGAZbH77Q7SgvJCzbUnS0SDOCmIdRurm5e6fNJC5KLQdBaQ
xidhSVeCtun+tD/8nzHkI7Z3sNb3XnmJxaPhsklk/PSzMgr7vOIqXkPL51XFJW2BgsuqiGmJI/17
Sz5/+BYIa/MUVtOc/ZOvEEGvCdKypaMZ9xJlWvbFJkg1shx01gUv6Uz+8DKYoFyNbRWqPuRa4YNx
MnNsU1NeW9a97SqVLxCflSdJLuXI7R/+34hTUXmDthZ/WcaU/P8WkxtVGeUlpdZzaknzAfFXEevU
cP4M7R/UaEUyKPkTooqegD+Q2lnOc0xTXlWSOm5ZjpfhF7MI+G8z2v8W74vxeNzJWYSw9GnGI4+y
pNkHfvfXDZVEbq+JirP0wedDbRaptuiRsQHWI1nSOfyhPphqVpwgRr41ypiE7fm3G6NIM/KfYvl9
aGUZ2jF9DCqX7DFT6yHrLxT5v6HH7om4PRaKgZZS3PgdwlmUKwdK36Tsk3hxqEMOos1IpwtUs818
p7z6R/WHX4s572H34tI+b1tUNke4uXko0tHjIfRLh4yfhZGyp3i29C3+A1Fdcvqc/ds/+j/DOJ4X
43cFvXfgFsJusqrfbprlqsW8/ds9fSf+a+9MtxPXlTC6+gRI0I8QLcgt4ZCwSN7/Ha812Ro+CWOG
BFO7z+nOYBuDVVKpxmrisp9GkSGqFXYuD/JQvKhog0pdpmf3U1Io5K6piSzOFGVq7E/yf3vVyHzN
Os1jgd35CUKB7OFDN3SSS1BR0JkKUsiT4lZ0P1Ib1Miq8UOxGhTfpPUvtLVtVNTFlsLjD7d+K/fO
k4g/zQEPxe6Bif1qD8V2WE67UcLQzvaQJpEpd0H2GJ6MSd85IYfKZvuUGvwwU0VnndQauYUjpCCI
i8505Y4zW+J76sb7R/g5FrGSYrpOF/r7MJOlGRAk0Qmk7tMIrzIzLtmgEA2HVIxh48LIhq+05qFw
JfjHolFuE3V0nHjPbSHBerW0EitEu26rLT6IqdNVtRyK1pB4enwwTPVsabpoHR0fejC18ijKW9XV
58dSzT+nXQP6iry4tKlTCgxwZPejsXEDZMieVkdKmA2U4GImV6Lm9U4ehtF7ZG0GZabJtjCpH5Ng
7vFxHQbLrI+qAC1GmWnzTYSCh6kY4ep+TZzVfhV+TpFZ8+QOv33LzK3BhSd8BGMJcwpHFF+BzxP2
sut2vmUL1OPRkEC+HlPbs6Ih24YVv33zU2SYt9zSHovL0r7sPtpfTa/hKqM5iEJ7d5JVA6YUurQY
G0Auz2nV8lDLixfnKDf/fDxOo6mHwZQnQXJLCiR0hr839XaLtQSZsdAJhWmRLfDHb2tcqvxa8kOa
FnO7oc3HiWlXUdGPyZlBfvsNTI8TVlrknP30j0cp1XWtZfPylFDBI06kcrvf1IYPmTD1Wj1BZhT1
egK9QOIA8JkgUFyVOPhiOnzkBf3MdqgTxbfGBq+TceGjlfc3b3+S1GTWBHbbwm4KWqBWpmlBdp5g
nWg65DmbWlmOd0rzTpaRxYqzeC5NRWhtZoA1McHyqyuFA1HNo+NSBJNgD0xNkrIw/4Z0RV2F975c
FPvC1LYkuj6F0XsKztlScx8Tdsoe3UkAO0uA1JytVoylImRllpzKc1nqZig7zRaiWkzWJJZZ86iJ
kzjuH5ErUziT+q39zZqgNZnLJVyYusgKre0UzlyqYmUpX8SaOwTfOwsUqFg4VodTSJHvgbnR06Wp
yaxZSUsGe5MdBHP6bJK8cchz4bc7BwVPFB3xG//0M1g/vii1ihXHy+Ttt9B/59M/iKX2zkFb1PLR
Td7g2I2j293xI7D3a2VYJo9834chxiRTPqRz54bPSrtw2Rx1z/zEQiio3i/1XyHrlgOQL0wnsp2d
ULod6XC3zVzvfskUfAtXbhPZyGvtHbNPpFB/V32gSGa1tN/qhh8Ep83KSNhsYWOUHlBAkjVAULRg
a+Myu37uGKmSYdH+XY0tT6Xcw46Ei/JtJ9DI5mek9rRSIYdSnSluQ3DHRJUp3A6oHqLawLwf4o5P
l8VFK8Z72hGNGhq7YPdqNnmlm22H90ovq73gHon/z4WWuLjxxVmJJLDJVNIbcaGt3dXGC7bQzjtW
ju4UmUif0Y/rpzQgspULWFycjYj9PjS2h9nPMkr5sZVZ9d9cSvNOiVdZ51M45ZxOc7vJ7T4SUiT6
8QkWqPRK6cxszdCsHd0nJt8ultujowPtaTnr6+I82R7e7dJoJPccCWvMQ86SbDkM+T4RqN7ikUy7
TyC0nOhzeT6Uzrcygf7iiHXwqXFT5xZm6/1r1tLk+IQhqJLza+8UPffmscT1c76BzLIH4Qp0hihZ
fSIrF1QsbNzEEqX/zFxroNC/J2j9daU7Z66JQqXbxJFaxrnIEld3uwJvPnaxZs//T6qltg8L16hQ
tosqUJVm3mQRP7ir3TtzPYRE9Y6P6Lq50Co63OR2H4yZCSsVT7VDTA2gThydZVjkyZVzERcesdsi
3tXeIe5Bp1JYd9Xmx5PiyrrXoCkXqLAsTYcB76vr5FaJXGwbSaFWZevTs9vnDtkXkrhqk/t7fgLH
Hl8Jygv/hHQqr00nUORaUZvaFYfkYBNRQeFTZvf6XfJfHE3eP9HKOTOgHvOMfR2equ4351dXrqh8
V1bEqMHZGn3I8yrrszPzRwECa53vJ53CJUx+gyWsjRk8lSRUGZQKIp5t7xDYf4LWsrx2rtAZo6N1
mNE0R1qAy7T44hZU5WNX7R0yKxTbJFUKKIepXre9aeafTrurN/xx5WWCM97cnnfwk/vv63MnXz+f
ccQGcw5fjQ51kWJUehwqR2QqNK4ljML5QOODG4PcnrWx/8K65FZmhVlYA2fcChWtLl3+W2csGMu0
1IYtWKCTGcvOtfHQC+SIHEnUMcA0AFmusZMeze/nvwvmRF6to7WsHguXFtAXpX5Fe+DC1V1NR5vH
R+ZKvAW6FD9haWoJ+x7WQZHETnLbP2lH4i2sXc/pIrfHpupUOpFKn9DTWZHjPkxUFtqdUtR5k/xL
0IjBxSAW3qtuKh2IMYFpa1gi1101eVBL3HHiUu+GGcyh88qWJl0f19iV3dvEiT5OGMG1l0Gohluw
XdzGbd/jNPmx2xrvrDOf88k2/AV68tJsh0ziXtOpRXOBFTJOFrg9dj9b8/h4r62PoTDFC4YYouIR
5YaV+ef95m9zeryazWf3sZpamSPq7MEHbi9pmk23y+38ea+LDUlcJ+wa742pAx6Zi2X0wYzSxxe3
Xwh5WKTtQqRedUF2nn3Ioj/MB1uxenwBoLC1CtCpRuTXrtbXqdCQmlLMNcjVI+eo6yIohP/aZORK
L3yhkLeT/Dq98GZN0cwsummAQ1XPZgELrOlP+WQFWci4nPVgmV2bgXKNd8fUWeX5lNJZi8nbkISv
U278gXm8qm2il1x4u06HgjeYcPbl2bzikGGzlTlVQT4oBbt9HBVaI+ypgZm5Ac/gcRgjk9Diab01
5OTXyi5RvrWhvEqJ8oLeHeO/4YDH8wGby85GX69NkqOztpQ8WWoFeurMLcgddVrpUdJsO382yomo
kWMKvDaRwOrxkoS9LTvrU3CkXb5/421OjR/Qkb376tSL6c1QxX1QQL8eW45/hU/09IM8vo0yDeOF
/XG7dspMFO2uNr7sgbyYUnjcoMn501W84SLoFV5BlIPbzpxc0HRFeaWoIVLLlVN/CaQeU9gM/Emu
jVDK2MkTdfVpd7XJnNu5IbLq5seU46VtdW3OZytzGSi0Gnl6XesFqsp4VGY5u+e3eEPPPp5BpatT
Ee9QRXhCWkT1wxuVI1+CcRvVy4atBPV+YXH6/uxx+Emfm/SKzYgGEsvT7VAtL9d4X8wACMyyiWA1
RyZi/bv4jNzC7A+tL555tua4ZgiPgI1QQsHAIyLOGnfqADXZRchxD6dfxEc79UhK63TNCJTa7B9i
+3886drVEo2mIy5aGbfkbBEstSXssoo+5xGNXxq7RqeBM/CBm8r3xA/m93Bm4chglB00q6y0Qqpl
vNDuFBRyPSrqT3qTLBzEG6caJm4RPBj9SE++WJOOg7LM0rLdMbHM/iJfmdc1c9+0vFe870Tr2MUu
kNKmxftILNRbvAN2A5LduiU+ha4Mkz+P9RgF+Z8NLz4msoa1Ii5n8KtkAga7PMwrM3CSUdm4CGNw
YD1QdRkXjHNXEWzvKIFNDeZzE6eHPWxxFg+4Pgei/jbLPgPHP/NcuXqpPsXo0B/qV8n4WberQtUO
RZlf1+QTseOnCNJ/yOZvjAgw/B4UzNjOFJz2/tu8C+edcZhv04Mqe520cUE8BYRCa3ZblcDjOIaq
c2FwCFWRLUrP0R/cUozKWW6GrLSC/XC/D6mkY0D7J5lLq2pTbJLYKlWyQznvUrGHRGwH0fXQrVPj
Ku96GsDn4qbNMXHBu+NCy7l4f4GXsNCQcsHE0bZW2ztQKpiZ5jP5PkK5DVgWrOy40vueBF0Pw/z5
0Ci7+4fzJPUtw7sv9Ndcl++PEHvnTB0LKQKpLRiWtE4tUk26OS607YYXd8ZUBOops9BWmXmZzfvM
jv3gZkKFs4B5+LYeJyf1/CHi5pXG+ye7KLUnKoRWoOD0ryHO+XZhh6YMa5jMX+bab/9XOSx1tHD7
tg/jzteeGh2tjWpPjNVkX5pebMn/EXSkcS1zU9LqXq5qlPx8+/dsk95BPXP7VJNqTwPizslWeANB
cEsJ98IT3tN+Ga3TlAsQVRtdBV+eFnxwNL4W1/vO2Dbsg5b/oy1nu/81whRoKXS2OwWPfk24hlB7
UOJjfx1St8QrwZn/dWU79SWIqbp8XhpbJMRtHGmkc2snqFAuZrSCzNwFUQqdzYyTPkWOlkrBJVBk
MeNDErzcBplAw1xYypWmGVwxp17zVD7+e1RS+ca56bLPeew0wNwHoanfpcUpCjrD44k8lVk1JBAu
dAsnHr93tGRMUjve2mlL2E+LvPCOS48ohQyLI/2hmTtnG8qs7KZ+9wOsf6Ur5W5owLneNBuLdSqQ
WcdiNVUNz34QJKn7TOzfY9w0O1yQ2BoQh1+mmehHPWF0v8u8RwQUOuf/ybRbQdgz1I3KdFDlKZlN
d7BffSa6VCD3qnm/Yy62KaVoqBP6Bs+4/d39oc38ckDEuK3JKHKjbtQEJB6LqIcBrVHc+ayzgZkR
nXSzng5PytYzDAuAGHfrKL9KZVcSNDusMtM2ionOkBNm08rREOOv+y89/U3BhbargQKug3TBN+vM
txvrCdtRlGuZlS61oxJodpUiBcOU3oVx7XD2zt2xHNYdQksVeLxlk5WA2lsW4Ox5czqyaqbsG9yo
VDFxBrpCC/Y6lUC0QRbkhStszfk7d8cMRhGmwqajb/Ik162peA3OJ9VAP2/VRlJMKpgMP5l9T1p3
7bik/9oTO56VM7Nb7PYpsYJ8d9TKynTCptfNvHBBZ3FCwjlHQRPBWGrU5uFKIdigzfgD19+MU1Gf
0Kzovzh28kyRr0o/SQfbxKkmu/dCm0vY0sUsg+R38/u87UQ4PPS3EmcRTJa5iPMwnOdWoQDPAeQK
cn/tIwryRinnlG+fH1uQ75ABUgtk9okoU/ccbhTs058HZ2+cbeux8r5kMsF5V+1Id2nledVD/fuQ
LGhgZO6AhkQgfoHOSzbuQqDHitOARDQI5l1Ic7skx/m6tv2tkCMqG90v1k0D9hPj7G9PouCwQ5VI
erJS07zU3iM7cgXWyEeyB/GM2FuP9qzWPxs5WpcutVrEyQI7O9Xro9XJTZHvly/rZck/t5Em3GXJ
70MgEMYze4yw0QegEdQtispvjshEA2DXaWGGby+THn7Y7zNjpn+xdgjTmh6nE1sfXBZ/bmO9pYTy
BlwYeSGoGfQDYV/tnfK17gMi/AprXTpwd2RjnvLhQoPG30oIV9re5O2Kiab15CxhrHb7o5EmuRVB
h7g0MRzoQ90hw6Gcsnd82sxFZFUyEXZU6DK+wyFPOqpiSNaKH7tm3dGBGI9S6fgbfGR25hp5wVdU
CNnKJdrWNnCyHRdIyfwJdM/JblNr97UHfKTzF4ApftD+yEXKK9st75EsmDCPYrz92KUh5Jcjrb+k
z2Jv1Zv8Bg7nvSnmV1kIYd2rRmxlKfzhA6UDmMEih4TkfZDymzFbPkw8jItfqzOwUdnYRjk/8Dn4
cMnoUGl1J3D8+e+L+VU+7SgQlUaxP/2oSJ7+sLoJKpjuXcVOJQ+XegN/G7ynTeXrBF5zIVR9jkcf
o7gJS6QmXOSdMX+a0tQ+MAF7h8+/9l3/DUrqrBjdKjB8BPmFrerzhR265mYkW48fABz4aJy7gywa
8PRHEdov4Kc9LzbsP1s3Ezpsu1q4AhqsbDQMb2kfAKjeWbvVkNNXeMp/EKH9Vyj1IdejrzhXAu9W
ZFdFTtn8ezhbPIwR8JF5BxE9Ns1rmJpViLt7FGvIBuqprdiNz54wEaEoxzL0rIFPXZrYVfFw2VYP
CAipITsEFoPOL3VYvfJt/xW+sWydNWvpxkswsblbgQtudf3Tx4lHe2BQH1o1vGwKqrigz36Y9u9Y
ds6atT5FWfuNBBjNFpd7Z8xf5QsvtO2YOAw6v7CnGxaVMQXmSHj0X2Ndtf9cJz04mYZV87Lfi6yb
GjNJwOM3pRrLaSURWxxbMNDDazjceYvjgiHvLPnBm1avHpf96uzteQhK7r6BQ67gUBzSQu7pQ8Y1
unejfZu/Si+pCWe8nZk3IA8piWs+cLM48372MSh48Qcqd995ERp3gSMnbpWt0Ry9PKVN6e+CnQpd
MQHn1ANoFHWJAkclVume4UrSY9UNeVz+wwaPoVE1acGVjuqc/yVMcEBmbDFFjpZ3l6NiKlWCz+Es
XTVYao8hdGaHkGuuw/ggHHDN1IEr3nsp2q7mLNwrnzKfnGvlWMi/Ui/l52shTaMUoo+a6t4YC1C+
Cz0r/vrFvrJAjYXTz9sk6HHB44dhXwiXG3b2kiSW2rLD54d8n0zf8KfDN7elIYV+r8uPaWcWbLn1
P/NCcvkK1pvQUnvOLcxUIV8SfNx/4BNjbscedogfKrTe0Z9STp1vjJWKOmmIfY99vA/9olFq6zbb
riUe+b4ooJ2vRRApFAx8nv/l05SOHyS2x0qsMpPiq2DpGHSyqQaHdrUlmX+zAuAcwUERq/ALZ5z6
pbKOW++mJt951qnypGu4LWFV4YVCm4yW82rcbUw30QEtI9TdmQGYs0DFydv5fVC9mNT6212gYMbc
dS8WLLXxQkvSKcntgL3k2xzGW9OHClJ/T91NthtuIXMd4KcQDHyu23RTDleMXua8V2HuDrBtGhob
8ZxaTZ3fvzRWF3ADXBmMNw59/5HlLrEhuY5s3jmKMjlTyV+6OTGuLGJVAfu3QLfDTBxsnBRDWkHL
tNGjb9eKp/5tdvwxblvVsSn6r9Lbygy1WxjgT+Ls0u0z2UWVpnHH3jl85iswd8gGDst2Bj+6zL0E
IXX2LGvvLPR63KqCElnjtLX2/VP2r6E19/1h8Lk7UmKQMgpbfCoFtIiyzjGcvUm+sFfrLyy8RYAL
Lz4ksAqoceofcyI0WVi7D41FR+sG8TRQKvzl2mMHr7XPS6MyxmWTzNfbIWWAl8LZmwZ4WVrxTqVW
CqAc6wlsVK/a5NLZztZ8o3/8SD1YmAC0QrSDd03H/AixDbiTEQVLyL2E420gZj0Z1Of2m1zVSb37
8/q+Gepml0pHozWW9iSzRwTil3w+QspkI3lY4hiVS2Qoztyn1k9FNqNjZB9cZgLMYZqOcWLI2mCf
q3TpJFdIFR3tdmWnGaKM1B1/B6b+r21WL6Li3b39BvUJDLCVX7XNGqm56NbS7bYACbAXS2+dr2N3
LfEq++jAHu/ePlkeGsqHIgZCYoQdnRKkyp+wrzW3cSw879lWWu4zFyj8am3Ccs0cVLbkLlUQ6zHA
GiXyHgJzHFkmLhSptIhsB6Q256vdzD2T9Z21fbr81w3eEu5s2xlKYmMJdsTYBWMOuUYK2HW8Oux/
XKgfdYdn55PTG4ri/0rdtpFw8fEYY9FNoix+kOZvzNFDHsEQdkt/2d2gLQMzaXAbKTvq7S/ASWCQ
2qORaBT2ss5qJPqmezq4Iju0cuuz01RuOP+8+d92r0y9pmHvKjYsuxz05C3C6Ir2/bCEMddApe57
P+b0Kop7fHwXAvegvXehcA/HXsMmE5Bs/EX5SldWkJcDQ3P9y0Hvc/Dr7q663tk2oDHNGjY/jMO+
8jax7k1z7ANzDV6w+UULk1F+wSl4XSlYXtaSFAGrrIlapMXq37/3hXNjKJRBWvL7qMGu1U7U8kyG
l+i+nK9ZpVaz2JEkQOE7oHmgwxjmMqxwNokZnQI6TASorC8K/h7TvQ9lc+u+mL1Vd2ldLiAvtaAg
t7+Qpyy1RhvP1tplLJtK+fml87OQSMP2hbFTxxY3sBe2ss91iJmroJcbkKNXDJSb4y0cLnBeyoFp
Lx+J+JvVxcGRcC9qroozFgoYZT/dY4bCRnYrSzZMQ9isfLKl/UPfltOfo+s8Y0ctSU6bY67DCwgq
cEMV7wNhrK1CLWxejZ0ZCRelwkhQvnGYh62iVMo/h1gpTN9KbP0OlGA53+12+1dhl38R/MaFa8Zq
O7hvjg5mrgrWMyUsY7LHjhFosvqnMu3SA44t+EnRLSha40L8JaQN2k1mgPCNWBeW3vqGOu23tJXT
OlxiRLJvAGXb7bTHRSWYa7HNx5yWCeSywDEIBA29qzQguANs9t6gXQnFQXvb0EnWY6s6ROt7Um+n
XV8XeRQGCbmmWD3O19Af9IKG+ufOMGegG4tTPORgKdV3gi4igpvPBlm49IiHC9ArNktnERsNLJiR
/kW4mmF4oW8iF35pDi/UyUH2sUzxtdo6+FwKHzfDXIBD7P7IdUnLIgg9iE8ABxfsM6W+IYUmNslR
34VeNjZFjhLpTQ+LlnhnsdZ/lsVIR4lUi3Te2Xbl6hL+SHVJZqK4ytvkEumw5bOTkHQUg/aOK3Cg
LERZaWCSW+Y3gcEazpgsnM3XbVHB1aL5oguAqll598DD1Z6TnGJCOlGQReXKDHM+740P11Vyjw8R
CkQJKawHvkLpxvYtzRcsf5MsViuc9eoziagPR8bG5eTNGBmvlur4T63h0h4fVdhjs6uWuQHPc6k+
ikZPvaWF1mO0ISxYiui9dHXkekrFA2uhwuzJfQAiebsTePFwCpA2pOPIJ4LCKzNj+ZfAm+ijmUoM
c2We3YjNxiY6GBmMZM04A65LaYsNUei5LAU1PmntUx9T2IuGS+1M5Xpuxgqm/mQuWAX91+yqZX6d
hVc+U8CxP9j9W+kVhQ5PtqHGOYW7ZYSHfS7XhbU2NEa/qXpbz/+ejREaWqtTF+wH1kBEOims2DTF
3BbspcWr5w4ajGq7PCjksa3ZhxFmpMKHisDoGxDhBraSRvQ91xXKjWYMozjSii/f+MbaNxzm+szZ
C8TcGmfhGSS0TWFPW756foIutB+pxyoNBfaGp/xi0OobW8VLN5MHm2SymJ1akO12AfZtBGfGw00F
Ex/DXAdkOC5JYqEpcmWlwX7d8NrvtglBEAtsvwaelU9doO7I68OYr6MSa184fR+vMMRaWVuXUkHv
sfIHwDCXp1GFrSI4FotsbczCw6MTtibuKF7StLUY9cQt9Ouoy8zBLO5HAyQJTD6EZgnvfPL/CjZN
MTdmV9hSopEI7TKKKp2psKczvDT54N/+1+YHyIu0WcMgjJrM6C2nHFLfTc8baTgJXtd9qAf1N8Cm
KOaWrOwQBObbfK1TMESoVqwNb4LDJc1WpUmuiHa0LV9Qlaeym/jVF5gcstKmQR86NgRNEunUpd9A
9SNmmAuD96nG6JMeiurY1EcsEo54Eack8Nmuu4UYKxzuWGqnsbehYAPLYSD9GE5S5OM8ujX35t3F
mAdH6hhb5CclksvYrIPj+ipbymcsH6GRiZQf/ZH84NW7EBWBD258M7ohC60VvvQSm0ImQ3dJHzTF
BS2YW/KJU8/tT0mG+XmFGk7la2/wnjYy96bhWFYYcIpOIYoSuVxWLt3AR0KWZLUDFar8Ltih/FdO
s5elLCeGuQ4Smo/Ja6rr/ki47tQGLBQVGYk5EgpVmggK5WhARFbu5fHN6fwKmb0wgalC2f5BNZm3
VVkHftYMcxH2eBA7A6k49EfC0Vtr8o6uSnHgIXrdouu3ID15H4S8cDF1OX4FZVlLZ5aNuDXKhajU
wbE1szhfj7ktpY4EIjUa4WpS5YCgWWGcL4JjwK9VWWgHBoI8wbrMwT9Yaxf5ki1MlanqSiuxf4xh
rgmO/LHJrGGG3gtekYv5AthDFPWp/q8gCoUbxXvMbJ0r9aU1P5YwMVdIGCaysOZnnNDgziSOiWJu
zlMhXE+ldRqQy6W8qf0ZsDAewAtTwU1bbIWQBw2jw8i379yvYOE7bYrKX9KEeVaqqFv/D1uPmVuz
xYYZlUYToi55cKgbGqhNx8fvoBCWVi6oEmQhj89CQBdWqzNvfEbQCgofeCeHY0GQpt8K+2mZm7OH
wpDt1UAxRr0I4aqHK5hfIEWkcedCa6+Kb7OwGU3iKBUszdyusnEOHzoCvGYThCzCWyUUPMYwV+c9
FwU9UBO177swcOElJWwYIGKNOxNaFw+B7xKnyiXBFU8KynYSN5Vfp2QIV7ageQEwtTHMjVgK6WMR
zP8CGWac7zaQCmPUQVs6GFhhtMnwKNAE24DvsSA2sdAm/hnhHLPJpShz2GL12FwweM/JWSyzzG/y
LoyRVCfF2GgfQVk71gYM29TGbJmZlpgUHWf/jZTZKwhtELQUvHR6qa0PcTz+st+S7EcSpdG6K1Me
os0wt+PZ9J3uV1uwgJoghGgpM4K5TtPztq7GY2+JIigYlxfadzv1xK8r5umldmmkUzG36J8tp0x9
KLMLYbS7fi7OyPwu3+RXklZ+UdBEVnffLECtnMRjd6OrIUMLjowPvLzQ7rwGHwgjyN57hlkSpc9l
oy8k+vmMrDGaYA8jhrkxT0ur8i7gb1eCkiWKjELdCkC/mO3tUowjEmLxubzQfihgh8rDDD8zK1m1
keVBF2Em8ttbI7LttFRqa88wf4imb6zei4QyvZqF2sx2u50JEVKlKN/EtnV5oc2Thgi5kDYqmXzq
Qqv1aSGtA9jWOif1AdtjM8yfIzHzkAtkcMYrJ8UU6JGxhH3HV7u80KZThVke85Rb5Yta9McVX9bx
tpBuRpBCbov9vRjmr/FKccMsu4XsO9+QW4lEZsTV36cJOddYaUUUW2xXxfSCr/5mg8uUDVEMc994
+TRt7GqR9IlsEVJTM6Gt1jcsXDoS2iYRRke8MMKSGiy0zFT5r1tCCTafLMisaFdAmVm38pU2SwgM
wFGMsZn7M68UZwiPmcPLkMr80gwzDUw/OQo04kFCq2AGGwpjLG8u4eslTXgO/jLpdf1Rb68KpO61
MwoptiwxU8XVhSDkhy1LLUwHglk+xfxU2BELRURh4fYXF7ADl2LtmJkw2ziYb5DMKthbHgltLZ8W
rKBpKoDA6jH5OAvcnFr/OAubYpjpsO1WrcFCK9IMOsNnfiCVq38XdtBxVJKEt0U+/lBIgacbucYv
yjDTYCvFKSKrxQVaebD1uVRLGXZmT+u6PeEbE11xcRz0oQSOAWOYqfAch+UfB4sEEB5jk8YvirTe
XJfGQmvrQwVlVLMDLvsBMczfQ4ouu6Dz2yapeG5V0zYoXN0CFpA4zeWjMqFtvMlpiCpgvVa6aS7H
ETPTZ263iF1rGxcK1YuekVkhdDFDYIMynCi0mPQwYeYJqtSbCF/O3Xql9x/DTAfq7bGdwMXCYHJ9
KoH4pwotFMP0sC25piYDYj9c1KMoaAIMMzUOVjJlH3bcCYMQXUJ9pRdmyTcz+GgktP9MFgMN65hn
E39ZZpnHYSXXknShGhSBb76rej8XJwnt4JgIEkSD3cgyjUxmmKmzcEHIFNY59t3qjoTzgsj9Swht
p0gflVvezjIPyt7sYMMdpFnqXo8G84K2IDX1eHj0oRq81nIcFPOwvHxGoQ/bYdWTThNaLHbw2IWW
2nK3u+42x75dhnlUTAF/EdUVRnm3Fih2JQn/6dIaVHdt6k/S/y/ZN8swJ7PSOTdL4WskC1UT2leb
IBDHIZYdSqsgxqIPYVQuP+kjq9DIMMwQlq7bs68qXOqEpXmzx8SRTqVAZcNWRvk9xg8kSc2/K+cw
DFOnCzd0NmhVKYsoOkEdstJaXlyPWSe7r8//XfwtMMyD0e02qV9EC4e+ZMkAhIoaMwxzXRpvf1Je
Oy42aZ75HWloUbrlvTIMo3mRJHvBJdTQy2MSeaPFtrqnZRjmWnzPu6WzFcnnypELlYrtzW6SYZiR
vOxfvcAKEmkBdIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZh
GIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZhGIZh
GIZhGIZhGIZhmF/m/yVoOmENCmVuZHN0cmVhbQ0KZW5kb2JqDQoxMyAwIG9iag0KPDwNCi9CYXNl
Rm9udCAvVGltZXMtQm9sZA0KL1N1YnR5cGUgL1R5cGUxDQovVHlwZSAvRm9udA0KPj4NCmVuZG9i
ag0KMTQgMCBvYmoNCjw8DQovQmFzZUZvbnQgL1RpbWVzLVJvbWFuDQovU3VidHlwZSAvVHlwZTEN
Ci9UeXBlIC9Gb250DQo+Pg0KZW5kb2JqDQoxNSAwIG9iag0KPDwNCi9CYXNlRm9udCAvRURXTEtS
K1ZlcmRhbmENCi9FbmNvZGluZyA0MSAwIFINCi9GaXJzdENoYXIgMQ0KL0ZvbnREZXNjcmlwdG9y
IDE2IDAgUg0KL0xhc3RDaGFyIDI2DQovU3VidHlwZSAvVHJ1ZVR5cGUNCi9UeXBlIC9Gb250DQov
V2lkdGhzIFsgODMwIDY2NCA2NjggNDk3IDM0MiAxMTI4IDM0MiA3MTIgMzYxCjczMyAzNDIgNTkz
IDY5OSA2ODcgNjUwIDY5OSA0NTYgNzEyIDQyMgo5NzkgNjk5IDU4OCA2NTEgNzEyIDEwNTggMzYx
XQ0KPj4NCmVuZG9iag0KMTYgMCBvYmoNCjw8DQovQXNjZW50IDc2NA0KL0NhcEhlaWdodCA3NjQN
Ci9EZXNjZW50IC0yMDYNCi9GbGFncyA0DQovRm9udEJCb3ggWyAwIC0yMDYgMTA5NiA3NjRdDQov
Rm9udEZpbGUyIDM2IDAgUg0KL0ZvbnROYW1lIC9FRFdMS1IrVmVyZGFuYQ0KL0l0YWxpY0FuZ2xl
IDANCi9NaXNzaW5nV2lkdGggMTAwMA0KL1N0ZW1WIDE2NA0KL1R5cGUgL0ZvbnREZXNjcmlwdG9y
DQo+Pg0KZW5kb2JqDQoxNyAwIG9iag0KPDwNCi9CYXNlRm9udCAvS1BTSEJPK1RpbWVzTmV3Um9t
YW4NCi9FbmNvZGluZyA0NCAwIFINCi9GaXJzdENoYXIgMQ0KL0ZvbnREZXNjcmlwdG9yIDE4IDAg
Ug0KL0xhc3RDaGFyIDENCi9TdWJ0eXBlIC9UcnVlVHlwZQ0KL1RvVW5pY29kZSA0MyAwIFINCi9U
eXBlIC9Gb250DQovV2lkdGhzIFsgNTAwXQ0KPj4NCmVuZG9iag0KMTggMCBvYmoNCjw8DQovQXNj
ZW50IDY3OQ0KL0NhcEhlaWdodCA2NzkNCi9EZXNjZW50IC0xMw0KL0ZsYWdzIDQNCi9Gb250QkJv
eCBbIDE3IC0xMyA2MzggNjc5XQ0KL0ZvbnRGaWxlMiAzOCAwIFINCi9Gb250TmFtZSAvS1BTSEJP
K1RpbWVzTmV3Um9tYW4NCi9JdGFsaWNBbmdsZSAwDQovTWlzc2luZ1dpZHRoIDc3Nw0KL1N0ZW1W
IDk1DQovVHlwZSAvRm9udERlc2NyaXB0b3INCj4+DQplbmRvYmoNCjE5IDAgb2JqDQo8PA0KL0Jh
c2VGb250IC9RVFBKT1orVmVyZGFuYQ0KL0VuY29kaW5nIDQ1IDAgUg0KL0ZpcnN0Q2hhciAxDQov
Rm9udERlc2NyaXB0b3IgMjAgMCBSDQovTGFzdENoYXIgMzQNCi9TdWJ0eXBlIC9UcnVlVHlwZQ0K
L1R5cGUgL0ZvbnQNCi9XaWR0aHMgWyAzNTIgNzMyIDY5MyA2MzMgNjAxIDM5NCAyNzQgNjA3IDI3
NAo2MzMgNTIxIDYyMyA1OTYgNjIzIDU5MiA2MzMgNDI3IDUyMSAzNTIKOTczIDYyMyAzNjQgOTg5
IDYyMyA4MTggMTAwMCA2OTggNjM2IDYzNgo2MzYgNTU3IDY4NCA2OTUgNTkyXQ0KPj4NCmVuZG9i
ag0KMjAgMCBvYmoNCjw8DQovQXNjZW50IDc2NA0KL0NhcEhlaWdodCA3NjQNCi9EZXNjZW50IC0y
MDYNCi9GbGFncyA0DQovRm9udEJCb3ggWyAwIC0yMDYgOTQzIDc2NF0NCi9Gb250RmlsZTIgMzkg
MCBSDQovRm9udE5hbWUgL1FUUEpPWitWZXJkYW5hDQovSXRhbGljQW5nbGUgMA0KL01pc3NpbmdX
aWR0aCAxMDAwDQovU3RlbVYgMTQxDQovVHlwZSAvRm9udERlc2NyaXB0b3INCj4+DQplbmRvYmoN
CjIxIDAgb2JqDQo8PA0KL0Jhc2VGb250IC9IZWx2ZXRpY2ENCi9TdWJ0eXBlIC9UeXBlMQ0KL1R5
cGUgL0ZvbnQNCj4+DQplbmRvYmoNCjIyIDAgb2JqDQo8PA0KL0Jhc2VGb250IC9LUFNIQk8rVHJl
YnVjaGV0TVMNCi9FbmNvZGluZyA0MiAwIFINCi9GaXJzdENoYXIgMQ0KL0ZvbnREZXNjcmlwdG9y
IDIzIDAgUg0KL0xhc3RDaGFyIDENCi9TdWJ0eXBlIC9UcnVlVHlwZQ0KL1R5cGUgL0ZvbnQNCi9X
aWR0aHMgWyAzMDFdDQo+Pg0KZW5kb2JqDQoyMyAwIG9iag0KPDwNCi9Bc2NlbnQgNTQ1DQovQ2Fw
SGVpZ2h0IDU0NQ0KL0Rlc2NlbnQgMA0KL0ZsYWdzIDQNCi9Gb250QkJveCBbIDAgMCA0MzcgNTQ1
XQ0KL0ZvbnRGaWxlMiAzNyAwIFINCi9Gb250TmFtZSAvS1BTSEJPK1RyZWJ1Y2hldE1TDQovSXRh
bGljQW5nbGUgMA0KL01pc3NpbmdXaWR0aCA1MDANCi9TdGVtViA2NQ0KL1R5cGUgL0ZvbnREZXNj
cmlwdG9yDQo+Pg0KZW5kb2JqDQoyNCAwIG9iag0KPDwNCi9SMTEgMTEgMCBSDQovUjkgOSAwIFIN
Cj4+DQplbmRvYmoNCjI1IDAgb2JqDQo8PA0KL1I4IDggMCBSDQo+Pg0KZW5kb2JqDQoyNiAwIG9i
ag0KPDwNCi9SMTAgMTAgMCBSDQovUjEyIDEyIDAgUg0KPj4NCmVuZG9iag0KMjcgMCBvYmoNCjw8
DQovUjEzIDEzIDAgUg0KL1IxNCAxNCAwIFINCi9SMTUgMTUgMCBSDQovUjE3IDE3IDAgUg0KL1Ix
OSAxOSAwIFINCi9SMjEgMjEgMCBSDQovUjIyIDIyIDAgUg0KPj4NCmVuZG9iag0KMjggMCBvYmoN
Cjw8DQovQ29udGVudHMgMjkgMCBSDQovTWVkaWFCb3ggWyAwIDAgNTk1IDg0Ml0NCi9QYXJlbnQg
MyAwIFINCi9SZXNvdXJjZXMgPDwNCi9FeHRHU3RhdGUgMzQgMCBSDQovRm9udCAzNSAwIFINCi9Q
cm9jU2V0IFsgL1BERiAvVGV4dF0NCj4+DQovUm90YXRlIDANCi9UeXBlIC9QYWdlDQo+Pg0KZW5k
b2JqDQoyOSAwIG9iag0KPDwNCi9GaWx0ZXIgL0ZsYXRlRGVjb2RlDQovTGVuZ3RoIDMwIDAgUg0K
Pj4NCnN0cmVhbQ0KeJzNnFmzHTcRgAsSkvg6lZANwn7gaYbCE+0LbxACxRaIy0BRwINxnIWyDXbC
A/+eltSSWtKcc4+c5Ob6PvhIo9be37RaGj0+sI2LAwt/+ce9hxdv3XaHDz+5eHxhLDsYLvxm7OFh
DGnnWQg9uFDa2T6Y0z64+OjCSpBlxiXZENJe85xYmD6Y0wbZv/z48Ogi1El665WHH44x6/jhyYdN
LaTn9iCkPzy5f/HBxXvHRGjh0npz4CAWRfgh/N3+Ff6AtI8v3CbDv9gZ9Pe9h4ef34G+kfwAjfRK
HO58cME2773iLqbgB2HUwXKzWXj48OJvy59XzjatjVzeWW/xzQmv1HJ7lZsR2vDl1xDpN6H98ssV
pJSTNO7t9ZbgG1fw82ercKFlfLmzqo15K2VIaDZnpVDLH0BGbcYZv7yLmcvlUJ8fSDlZHGTEJhnn
hlTo96uTIjTpH3d+c/HOHehSIVjsPB06z2lzwM6G+eKdt/ow/oDuPPH0rD4WJ/pYmti/tZuheXf+
lWp7bM7AsOS5Kb1wB50aEeK1c7bEixzvQzymh5INrw/yRO0eqCKhD0KxFI1KMsQ/xmnsdFUtyZUh
utQFc9qsWtoJVVVLCmaJLnXBnLaoVpnttNykTLZqU0klvYFMjIo6pw0MglO5HVaFunCOdQkho7Cm
0msxBDFtbAf0nrap+x+mEFQoJw6N7IKYtrSDFicFAIxDRbH2NDvJYdyK0qdpFGZp/PGZld7zTYqD
cTLpPA+aLrVTdvlJUkFuZVFBq1FFLRfL3Zr0YVBHa4Vzy/0Ua0HbP1mht5hwWZlDTh/Xn4+iNsPM
oM8/COKKa26X/5bnD1a9aa4Yh1+lIj9doZlF0788jeZGb0Bl7EGqzpuHioIOww+ovJFBq5U1gKGM
dZwSMOdxdJNycJdiTY40JVIKoXJ8mB1YgDGMQ77wI/wvcd7vlXC6Vkmor8DpgqxURTFInfciibrB
jHc1/9N10q6I6XMbvycTK4UkMBmjlw3TjghqLivtwPhUakbN6dgz+hTZYCoYzukolNJVKk6q0gau
7PnTZ5TquKqMKFy1ruGqkZnxIaSygZRA2gUxbeGqYZ5wVXlJQdoFMW3LVcx/l6soj1w1XyhXDd+s
SWgVA1oF8xStbxe0/rugr0Kw4vLTysgnUdoKL5b/rVJv1vuIUwkTX8mQUbTMlKFgJUXeLkU23C4/
Ca7fL+U3DL/lNhFMtw9LST8FcRnslwb8zc+M88MqrLsGDIeB2GAi1NGawzjOQIAsn1CtXijpfFKE
lqNDJFGvWY6i2BRHe5lYKdR8c17huyKoqaJvRyo1o+V07BkcRRZMchSleo6WNkxxdJTqOCqcOsZR
pQ3hqMhr1gTOLohpC0eV5ISjkisKzi6IaVuOYv67HEX5K7FP4T2kEkblU1mon4a1rLfMUHr9eweu
dyv8HuyarUBfYTbujAXkKge/tDzKvGvANm5gEW9qD86hDV4iSCk2Mdt7oaSG2rZW1G5kmvG2N63O
0tgkdqaJtS8TK4XKOIO2XiQpjxsQnUrN2n469gy0oXoGtJ1p38eCPMtoo+uO0gau3PmDPUp1aONp
OZ/QZhu0wdufoI1zSVnWBTFtQZvQiqCNS0tZ1gUxbYs2zB/Rphu0ofyVoI1H2yOyTV1mIg72Wkj6
Sf25a6/dz+vwXRPy45r73ZzwwS5YfxZMPMaFJ3nXX2CK2k0qqXSsm9yskpraksUdcG1W7t5vzJEB
mEMjTqo5NA5CSY1tv+LfiyQaM2v1odiU1dfLxEqhMs+gsRdJysfsPhozLU7HnoFGVG9TdfucjkIp
XaXiWJc2TFl9o1SLRuWTV3fP6uOMVTTCipW6IbtgTlvQyKypaFRee8LCLpjTNmjM+e+hMctfBRq1
t5tLZNSXWX2/2Lf6Cubu7zgjq/23vzr+ecnz47JkJZj7NBt9fvmorH7fqotv3PdwBhbHlcWFh9cG
g/AC96Sz5yjIrJ2n4CCEoNjxIQ6RSTmeyoeIYlMU7GVCpbLeTlBwEEl6hrs6PQULGE7HXk7BrMlz
a98s1a19axtmDMQdqY6CVhMfYmMggqwkFLSaOg37IKbNFFTOEx+isk5QCnZBTNtSEPPfpSDKfw4U
FJdSEAiNO7JfiewC61QsX13FJo1TanlmvaU24WDMlmdXvgkv7PI1AA6HuvnluZUBeoR30i3PQ6zy
XvPlBaAUAw55A0kBXZqB0I2ANueMkDTPvz9aYZ3PuDoiBZHARuf4chMew+TiXi8vrrfYBnOKSbv8
/UnIzDsOSUJmgFQnYxIOfWiEWl5aPcAT/i0vr9JIKJhfBy7CnHC196ewmCfUFBZHISSHHLA4RhJt
mcRiFpvB4iATK4WKPIPFXgQVb98lWEhxOvYMLKJqzxmHWaozDmsbZozDHakOi9oecwkqqzTBonbU
B9gHrdINFq0gLkFlGPUB9kFM22IR89/FIspfCRZhJZVPqnz9Ei6+Ep57J3gBk/USeKcAYUyYBlGv
BguNWeVdpKhhWgZC3RKb8wZsuWuFKAUVJD0xxygr5n17o1DSp3QKo2XUEJmmrnkaRqHYFKN6mVgp
1KoZRvUiSQvsvm+vqO3p2DMYhXo2abqhVG+6lTZMmW6jVMco6Y/59pQ2xLenFBMUSl1Qm8a3p7Qi
vj2lBHXm9UFM2zIK89/btsjyV7KAlbA+xH0Ld9kK9vew2uSgy2TT9p90zzWnI845spoky9p3+33k
sCd7HWileVxolk6ZwxUO9ByuBqGkWmb0t42RZBbP4kqbaX/bIBMrhQo2cVplEIntwMjhtErR4NOx
Z+AKVW4SVyjV46q0YcqkGqU6XIl0sCnhyje4kp7624RQlE9dUOZNV8SVNJrgSqjG39YFMW2LK8x/
F1cofxWnVTQsyBQ63PwxXOWf+QiuF8u9mvZecrPB8/+WoyH/2dtcbXcgqkcuCz0i50muiZ9Me9JD
c+wKx37N5AmRUQjVe/SSjZFpSj+NlyyLTbGrl4mVEsMxwkvZ1Ysk7eADg1OpWZ1Px57BLtS/uW3U
LNVto9Y2TJlao1THLqb4MVNLcOolY8pSWHVBwVsvGXeOsIvZxi3WBTFtyy7Mf5ddKH8V7FLwn1DD
IWZ2GcbeDsSBhb2hh+UegpQGYwwsp/+UyLt1V/MRsC8MKiwd67G768MpHfYza4fMoQoHec7MGoRQ
m2VriexGkhk8eeIji82c+BhkYqVQuWZQ1YugMgzITaVm7T0dewaqUN0mzSyU6s2s0oYpM2uUalEl
nZHHPFdMEs8VJPSETV0wpy2oYpxVVEnXnALugjltg6qc/x6qsvxVrAoVVMMlI4IHzey8XXqDlnMF
AnfeB5i9dsS3FXYe+fL6estvGtDhljeCa4s5L5havhGOuwmnbXDKA8Aks3b55uo2ZaT1xGf/THwM
Y86XN1cwbgTjEqTBtOOMsSBTfPrXyvFldVhKkp6cYhzLHybMMG4QSvqYN9jMqUgy9WfNMZb34ibM
sV4mVCpr5QTjBhHUomGXIZZa1P507OWMy3o6x7gs1TGutmHGHNuR6hhnnDlijkmnLWGc8dTV1Qcx
bWacdFISxlluKOO6IKZtGYf573nns/yVME6BQTCaY+M3EJ05lr40DcvK/FGZNIquGz/e+xaMZECS
vl9Mt6On1MYvHsgptet7pNeJaOGRPj5WxctQmCfRFApHoaS22g4oHCOJhkyiMIvNoHCQiZVC5Z1B
YS+SlM0Nmxmp1EyH07FnoBDVeW6jMkt1G5W1DTPm3o5Uh0LNiFetMfeksZ6gUHPqRuuDmLag0Gji
VZNaOsq+LohpWxRi/rsoRPkrQaGwYDUNKDz2HQN+EfXWbS4PwYizjmZtMgKY3XSb9+0ILG+UTIfd
rDEuHGyD5ak1YOrdDydBnNYGLLwn5DcmtnFZqzaYdtIv95oEQm5KxYPIdmNgnIYv9QHOYAuasF3h
Azv1NfLUBUvAkc6Zsg5hMpl5JA5CSA02InGITChhT4NEk7f7JpDYy8RKoRLPILEXSUrH9p11hRKn
Y89AIqr1pHWIUr11WNowZR2OUh0SpahnN9rrBkBWECRKSb1zfVDnbVJEorLEWSel4ZSBXVDZ0VmX
899FIspfCRJZXL5lyyWbcbxsHjQfQtSvRUvKv8BK2DiYyfsXCtTNA7JvWh9/uHfzwLvUEZifXx+i
2WDq1X6bI5qy8z69UQiVXoxEGyLJRJ8lmmYzp7n2ZWKlpJz16Q0iqDP7Pr38QJ+OPYNoqJWTRh5K
9UaelKxjU4oW/bmX09XaEQn3UORIeg9Fmi5juRjf5bIfW/hJL4Rprzv6IvUr3JIBawW7FShV6FT1
Pxy9nydfcNPew6PC9TSqj6/31wBoyf017UU9+dqb5sGJGuSMNLkFp7mKhz54nO/OwVdRCAnP0J0Q
xbpgTptv8JHM5WOEMsgalRML0wdz2vIqosX1t2DR7L7g6664CF/7w1ummNB/qu+A35ZDNM2nxeV5
/bjj8kutyE1Y8Qs6rpbflSuz8m0N8KqrkUT8TtoSd4pen9VcyFWy/+sqxAaNJVdm/bHc4VXvySKZ
pzNH0vm2xP0G5Ru3Ui8ALDjqidCkRJEdKGXrTeZlT/CvsBVqU1SKWyvDcMc3DbfMf/k3dCluw/Gk
Oi3Ou6ErK0hPAOF8vaFLV/2G+S92FT9ry3BDV5bob+jaiQ9MB93xh/FH7L2jT8/qPe4P0EVCS9J9
RmL3aRG+NpdSl93Yr4ZVpZawqHxmhb6FxWj4jiG6Ivny7Bq2VE04axs2H4wUy3MhvbNB9Z5fYUWr
YZW5vLA6mMYSZueOxI0wvcCGVS7mDBam9fFbgyHlzbBHAutiA3OXJK25vxgWs0KC5UiqUeWfTyUx
WOymesAAxNPDYQQMaN5LRZ5k//IaqBEuwKsFfb2IvxLPFitQMyrzaq6ptEPjg9RzcQtaCBaqB92q
lVeNEKk/ybbWD2odv78wlzf1RhoGUPObpACS62v1J2lNqjaoe9qlkox5D1JB+aHaG3c+73G9UWpV
u6WORC2e1AmbGno918Rb1w4QD9/3Ok/bl8fKyVzTcKa7GcvYKzCVxg4MBdwk5dYGDqMZcqVVJOXe
XONS1MR9NrUpo1nozPiRDTD3m4GuWnjZCOHzZlhxgodS92ryZh3qR3Ta1EblIslcIknrtCLPSU/E
WW24drulk4SvXtJlN+qYUfVJ8wSeMJfnyYt09tauKSVRiMB7T6W5netOhmZQmVi5IpRzV1pjlawo
wDCs6ZHaIvL8xTVab0w2WZEEb5RcU53BvID6hdNl3oidDg8ytaTX8mxAkBpQvP2J8TxR3TztvrJK
zYHSOvTwLQV2GLyjDtF5KBp99EVJnKAIfn0FK0bJ0vgQR6p8ktqEGt8C44FbePEQiXEqVhnj7WcG
KCHRG3GMjNFk2lQQvBxMH+2kNMu34bFlYQeddPd3VngHMhW/pRMyfhtCMFaJD5XjDowT7shYvBky
Z9wbflQ3Szu+u4Y3pYWlyPfKr+93cbBUoSL4xlXQ8meg7kpy1ijks0THd9+6RR9fSFoIQ6Jk0cI9
8aLDTUE/WOMXOI2WkBEe9K2lcgUMybL2Mfas8z4PgWveNE2RnUUBY1AfP9tAK/SnCL7ukKUCy/fG
3ouQpPzhGjKH1XgzwJexl4iH7uD9O2L31UGa/KMwezlT8ZWlvYYZKq7IUcXVIR6F8K7af1Jn81nY
TangLQmOvtZ85tmZyM93JobCju6CpGU7s3gIJKzbA+OcdXSv4ukiz5cJ52sMs59nOTXLz63CT5Fw
97HQ7Do4RK0Nd37XsW9XafCHPmv2OUwzyTUMByy01Din37v4P835b4UNCmVuZHN0cmVhbQ0KZW5k
b2JqDQozMCAwIG9iag0KNDM2MQ0KZW5kb2JqDQozMSAwIG9iag0KPDwNCi9CYXNlRm9udCAvSGVs
dmV0aWNhLUJvbGQNCi9TdWJ0eXBlIC9UeXBlMQ0KL1R5cGUgL0ZvbnQNCj4+DQplbmRvYmoNCjMy
IDAgb2JqDQo8PA0KL0Jhc2VGb250IC9HTVRYU1UrVGFob21hDQovRW5jb2RpbmcgNDYgMCBSDQov
Rmlyc3RDaGFyIDENCi9Gb250RGVzY3JpcHRvciAzMyAwIFINCi9MYXN0Q2hhciAyNA0KL1N1YnR5
cGUgL1RydWVUeXBlDQovVHlwZSAvRm9udA0KL1dpZHRocyBbIDYzNyAzMTMgMjkzIDg5MyA1OTkg
NDM0IDMwMiA0MTYgMzAyCjYzMyA2NDAgNTk0IDU3NyA2MDQgMzYzIDYzNyA2MTIgNTgxIDYzNwo2
ODUgOTU0IDYxNyA2NDAgMTAyOF0NCj4+DQplbmRvYmoNCjMzIDAgb2JqDQo8PA0KL0FzY2VudCA3
NTkNCi9DYXBIZWlnaHQgNzU5DQovRGVzY2VudCAtMTgwDQovRmxhZ3MgNA0KL0ZvbnRCQm94IFsg
LTIgLTE4MCAxMDEzIDc1OV0NCi9Gb250RmlsZTIgNDAgMCBSDQovRm9udE5hbWUgL0dNVFhTVStU
YWhvbWENCi9JdGFsaWNBbmdsZSAwDQovTWlzc2luZ1dpZHRoIDEwMDANCi9TdGVtViAxNTENCi9U
eXBlIC9Gb250RGVzY3JpcHRvcg0KPj4NCmVuZG9iag0KMzQgMCBvYmoNCjw8DQovUjggOCAwIFIN
Cj4+DQplbmRvYmoNCjM1IDAgb2JqDQo8PA0KL1IxMyAxMyAwIFINCi9SMTQgMTQgMCBSDQovUjE5
IDE5IDAgUg0KL1IyMSAyMSAwIFINCi9SMzEgMzEgMCBSDQovUjMyIDMyIDAgUg0KPj4NCmVuZG9i
ag0KMzYgMCBvYmoNCjw8DQovRmlsdGVyIC9GbGF0ZURlY29kZQ0KL0xlbmd0aCA1Nzc4DQovTGVu
Z3RoMSAxMDI2OA0KPj4NCnN0cmVhbQ0KeJztOnt8FNW555yZ2Z3Z18xusptNNsnsZDfPTdwkCyTh
lSUvDOERkoC7gZWEJBgiSICgEsVESHkERaWAqZRWrRbN/bVuQAV8Yu/tva0VK/VRW4uP21irFyjW
aPuTZHK/M5sg2qdt7x/393POfmfO+c7re53zfWd3EUYImVEvYlDtonp/IdKe9D9CtrRlbXNnrO5d
gxC+ruX6LvdSZVUeIH4F9d+v6rxmbXfleS9C5CWEuGevWbN5Vay/8W2ErHva25pbf/pW4mKEMocB
Oa0dEHa3sQsh/k46afvarhtj/TNqYb6uNetammP1FFhXN7q2+cZO3QCBtflHAem+rnlt2wR9sD5K
7Fy3sStWz/wP2t65oa3zzZvOnIb+ryDECLp4ZAC6TiN5Mr/8YVuQh77H39HyM5NltXX8Y/QvevgJ
+DIPPk2y/9l18R14O+7FDfgGvBZvwqtxELfgMOTboLYOfV/r9CB6H7txIrZgjD3YivXoIk7HKTgO
s8gA9bPQZ0TreUjLR/B09BHRpIV2AzyLXkHD6BxSsQU9A+kaSIPoPhRCIZyKM3EJvhKdh9mToe89
aAidgD4/gjFvoN+gC5jHjfh63I/3ETOZSxqhnxOX411kAbnIepEe30Bs+BrmCTyCddiOvegJ9AL6
JRMd/y2+F73N5JGj6EY0H72Mp+Ag8yCTw8jkNHkQoeD0huKiaVOnBAoL8v1X5OX6crKzMjPSvZ40
xS2npiS7khKdCQ57fJzNKokWs8loEHi9jmMZglEujjrLQ0OJep9LUZRw3kQ96fP1KJMu/V6JItvn
Orm+MCj5C/WUL9RTL9UXRlF8tMpTXkEnHkJVv4miuCiOjyK6Co5bACtNDKps7fBUro4mlrc2NcGI
Co/kjlZd8E+Qos09ZDSUe8rbDHm5aMhghKIRStC3cwhXzcZagVRVTh8iiDfn5UZtvihJr6TQEQ3u
boKCpwJmgpa4z1qOj5+87fImBMMmS3GxEo7qyqN6bV336miwOYp2u4dyT/bfdlxCK5t8plZPa/Ny
kFwz0DiEmPTK9gYqx0oKTe3uKAuTa5kLMO7Kdne/h4qjsr0Jck8FjPqzeEAL5aEdyklX1AbvyqjV
F50LPeZ2D7uY/krnajet9vfvcEfvXRy6vFWheTgcdgLB/ZUemBAmq+woA1ac/rzcGE8TAmht6qBr
djRTOis73P272zRab9No0LpWtoNimv9Wr/7+ylZPZWtza1ls9vJosEF7oYbGkMYgiK4iPIGa6AAt
rNbSVBFWYsKuqQuVU8I8zRWumNovYZomMIConGx0UwqqYYKou8UdRXUhD3QtpllbMepvKdaMRwlj
GFX72agoly553P0foyhu8pw7+3lM8wRGly59jGixylPV1N9f5XFX9Tf1Nx8f713pcUue/qGamv7O
yiZYtTYEo46PP7HbFa26LRyVmtrxdJA9tYCqulCpS7GGJ6u1k1UEJgWGZdTYASnAp3riBVJGDSHF
DYJaEgq7QE4hWm6AcuxNDQkMtxh0PCE2KqO24kviKZ8oKgq1zt3Hg2glVKK9i0OxuhutdB1BQb8P
9NFEW05OttiX0JbeyZZLw5s8sMqjiDpUe5TPuPQRJUdcZfv0KHb8lea2WHs0rjzEuEg4ViIuhpYM
PtjpM6MJPihn+fpBCS95opIvyoVOumaG3ZIVTgCqvXpPzeLGkLuy/5IVxDATnFI7AFP3NLf3T2wl
avRwFJQNefDOxUNBvLO+MXRCAk+6syF0hGBS3lQWHvJCW+iEG45WDUsuYWnNTWuohhrgEcJrTa4T
QYR6tVZWQ2j1luMYaTh+EodRy3ESw0kaDh4ILUA+vFGtQ8hSPN5xcY35IU1ilz8RimG2oKuRHrUj
DhFIQbQEopBHx8chjsFBoeG373nl935jlcEEgq2vmaRpwV/gn++1yqcAXgD4CcDzAD8GeA7g4YNe
+ZsA9xx0y984mCUf3OuSPxywy4cHEuW7B3LkAwPp8n4oBwfwAHQXf4/37U2Uv77XJ9+1V5HRXkwX
Wr7XKE0Tn5Kf8j/F+J/E6IR0gojA92PY/ceePxLpD+4/BP/A9HyMpRH3CHGfrz1P/GdLzy46y+S/
2vkqOXokSz5y1Cr7j5YebYp2Rjtf4d4d9sq/BvAP0wWO/gAYoQuNPwqFn/VcIZ8GeKnHLf+0xyqf
BHgW4I5nxp8h4tN4/Gk89IhV7nwESw+5HyK7d+XL/bv88q6egLyzzynvANjeVy1/rc8qb+ubLvfB
NOsG7x2MDl4YZIP3YWm5e3lwOfMRzLi1xynf2jNP7oX3LbDiFoDanqaezh5GEhXZYc+R9TpFTnTm
yCyjyHG2HDk3T8zxWbKyxYxMizddTPNY3IqYKltcySlmZ2KS2e5IMNvi4s2iZDWZzBaTYDCadHre
xLCcCWFiksRekQR1vToSZHoZIqJStAj1IFZEfigGU9ZB5Vn0UzSOeNcMXhan8zJTwsuomJdrAzhq
q0E1DWXROAzv+rJowFdznEd10UJfTVSoXRYawnhPGLBRshPU0xBld4IlNoAPaVwWOo4TafPXNJcC
peO492u33+66VAqHfSnR1pr6ULQzJRwtpIU7U8LIB8/Gro0bN/r+wjMk0NVb68qG3mepw2mOvu+p
GPrgfc35RD/wVOCJoZfPAUWY9FIt9rnsQb5NGr7rT5bTBtHdQuj20SMdbBl4xR/TERZR8J86c0rL
CvIVq2JNhwxDr097OXSRvhEU6G70qHtIB94FowuCXhGLxIlkLEOI6sd+UoJKcSkxkjeYX7AQ2ZEe
OB78kXNIGjlXkI8jAvbEkQ514K0f4l1jHLlI5zsGJOVp87mCVvILjF5CeBFegdfhHsxhOtgPY7Ox
VSF5aj+EiLtgAESOSDcLYngLSkEzgzlh2xJXG+kwX082m3WOvTyTsFcvbjGgbuh6XJbloFwrMwk9
+sdSpU/ORaQRbdZSmDeC44lex3qA20I2wWHjpmRkXoF92BoonFY0G+tmPXPXWnX0yNhHJPlxzDfe
M6RuvLZrxk03Nzfv6p21eiV57yX1WKhsCnd6VvHV6nOvfv30jBT76PJEZeaPJ6jkdgOVEtw15gYT
66VV4iaWSdyr1wvOvQZGsG6ZjuZREmEPWwVTEUKKrAQVkqjvER5zSyNjhRFrwO+j1Jaes5X4YwTr
9BZKISXZkZCKv0Ayt7tqTviN7/xO7SU37vn3msYV6saKvJkbVpRdt7LHl64wF1ufnRNqVF3c6YKC
Gcf7S5fZnJxa5vS6w1QbZXDa/hAoNuFQMAURHWE4XoCtSHQM4UVLN9qkY3SKQSwCmt8KWmgBWWRL
0NJkYXR+jVpfBJWW2hJKyhtCJ5Bx/O2jglTEHx9/+xi8GTdkYIjhgnxoDnZ08V1GwgQTUoqYBotU
tJDMYav5BUKZocq4gtSyIX650GBYR5rZ1XyH0GZYZdzM9widhuuNu0kfu1voM+w0HiT72IPCPsMI
vsi5zYSwMpFYP3Gzs0kBW8LPEgoN04wmFggICqmFRcQNmWGyJtAaS8UvAA2EEgJtrwVn2VOKhBzI
esDrGU23gmQ6Wczy+h4dp9NhgbPhFC4N53EBPJMrx/O5pTjMrcRruQ14CyfhyA5p7OTJiRxPbsFI
BE6FSFjACnywEgdZHP9DdZ16lfqxOgr5OnzXu9hG7f4Cd/pTP/P86DTu9MVxFlOg9rR0/L/ZY+w2
JKJ8tCo4V3RyuYnOaq46OcyFk6/lVovXJl+fviG7M8+MP5RlnyMzaBaLMjM9h32S+bDDkS/j/D7/
E4X+QixmyVkkK0vfl/hkAWyJgD8SkT4ZKyykhlY6Vuj3WSfNbaoFg73Z46mpgYUlaFVPWsbUKdOK
pnmLpk7J8KTp9B7rNG/AzdqtClNXPZg7rcTkTAhWTFuXk7I0Y+qGintfv66tFWd9e2Bf+PlcpQTj
W3EAW9WDOP0Dnd1inTPVkxsfH5fb75htcyb85z03fTMvL0PQReaWWrEoZj/9/BgLGggB9+vZrSgT
7Qx68plSYUZigSvIVLLz+fnC/MQKV428TL5WvtltyXCbpKJ4UORRs1Rkocq2A0IKgvHlS1iSEu42
SaVe7KWKlwHp9abcjRwS8kreHi/j9Wdjb3ZTNk7apnsyC44uMOuIPxJApefoZqR5xFeQTzXKpdG9
R0UxG4TjSLB6rsCAAImAwGL7sShgtWDy0dc/agyvXH31svO9G3/QELDP8GWvnHPnwW/vrVjrTZvi
CCw5kVpVXf3m/kPDNXPLCrPUU7b8BEfKsUP3PyTb43Pt6qksP+i/cfwd9rwuHsUhN5odzJpnmJe0
XmLcOWa6s0DVNuS82yLh1AOcwxpP+tATaa5t/JMKsBBTbuk5ql5KeiSbKtaTRqyf0a5g62Wks+fV
gcj9Hac+qb+y4gfNbbdW4HZ1IKPBs2fPhlsKrts0/0o8E5vuOLOopt6n4DcvppFMyTJ06MH96UAn
1dQoux3ZUTK6LljvJT5DgMw0lJMF3AJDuWW+1MgtMyxxrdZdKzTFNyV0kc1Cl6UrPh5/mJxsSjxs
kxAv8fV8C7+R53ieHTA5BMHRh55K9afiZNwnPplC+YFzHFShaSXy2fGoaGaqSd3jRlYJKZCna4zp
2dHRH/EnHt3w2uys7te3qd9XB/ASnA1bLl69h+nobN/O49/13VbnV98qyMX5OBE7cKX6P+rokvUb
1twAFggOlNmqS0VOFAx6EWIH7NjIWw5bRbPBgFCSmCQnwSnJW0194grzOjMxg9WcKynxawdjiZ9u
rpISur3AGXo0klKwYqfu1jM1AFZE1cBsdTkX5HbUYIf6iTpwzz1vvFm7tZAz6W3z1wojo3cx60bk
F180CtQa1DB7HvZDBgqgJcHihY6FeQsDEUcksNrREdjCd5s2eboDRrvX6btbkTLEggNOg8Fyty5Z
EFzeTDtYx9QrtrmenALbn3qaQhAgorSBY6TSLAFhpmu+BjZ7pjUQE+tsPAtTDPrMboq+aDeNixe/
e+emX9fnlj1T07pFkZPnfKv57DhaOLfsubZl+2eZcUQdkBu9e/ZsvmFa+63fen3W7KLkeJyY5EtP
c7dW2afOBh2n7X6+pmqhL6NwdByPmcXv7L2/N436p0HwqDbYAQ5UHPRge5x9prXTzmLJzO+PkyzI
jIEtZ76zyUkkY5/5RELMTj6hDnSSKQglNI9JDYI6UavGhp2zqQcs1vgFlQVtM8Au2puG1jx+iuRV
7HADWZ7RYV382Ms1ta+8TM/heyFLBipoBFUQVLhvIZ2kc4NnRETE7CHUxx1CWMIE1wpNQqfAwOkx
PDZMaYhMxDJFsDCx0XUMah++mW25F1sn+CM2beaUoI0Aom9iIq6J6+ToRJSViXhIGw+dY+P0r4Et
ZKGrg3NYB5NsT85yHnZ813XM8biLz9ifJFkTZMJahP3xkihaUvvkwQTcR6zmPssggvsWPDnZKCc/
pzanM4eN0NM/AkYhnSsZmZBdQkksXgKBfU589pgVxIR4WSM7oh7gbbbqsqmtWZTOyOA16wbz17yw
8vGn1QN6m3Veed5SJnl0mBTUbfR6FZ9zdJhtubm6rqVpWfsvT42lk4L6DYCXL2kduPvzWhf/Ea3b
/z6tA0ma0umZdobLgDPNiDxICdrsA4KkDDAOcRt6Kt0FjsKr7aNzcBxROeHYuaPleDZ4iMm1L3Ol
XIb6tPorSE/jSpyGM/ActdLj8brdjVOmLE5XMtMUd7ikIEwK4Ah6DpdiO07As9WTY7/0bb62ZXtW
dlpyTubOa5bvyM70KtQqB9VWbjZIiXqH0qCvglSIFe46sS6uTWyNg8ApWUg4YJVMYurdOofRFQ+E
p1lcQp/phKJ5ByovEFdp6WdRprbzJ4VlwzFXb40RP3tJ5ZWPtzdtr6Jiq//e+p+9r97euTmwpsBb
l3XHbWTO7uF5C2uz09VcbnxTWZ36gnr2gX1yythPLPzhmEaZ19lrkA0VH8OmThOB05R64wSDVMTu
F0WjKPAIxfvjsUnfJ5yI0zRqpad9aemYjx6gkYkT9HIjZF53J6xKW3B9BaXphui8uHwbY+L5eOeY
xLY8uKqcEGpNK8CLdoOc8tHWoFTor3bO9W/Cm42bXZs8epkGCwqEopwbshlW2JVJWWwKUwsBGw0f
FCX9cIqkp6TGQVWvtxxmHErWtiTrNiVJrwXyBsECQXFhZyHWxwJiMMBz/nMxR+WLxRBW2E4RzQ/j
eFaZOF9jVhEzFS2q8CoTIUXscE3QurDd6o/UDw+MzFNcc+cU71ncsWpmQ9au4m/sg4jKcMt7c+Ta
U6uvumFaa1FPcM9O3Pr9V4vTcFZcXlKC4r8iO90q2MWsh2+5/+eBFHW4qDI/NyvHbrRL6d+m3m38
A+ZG7gHkQvOCuQbOxRHR2GkkRsmsP2w0iC5XAvBqoV/UoBQxBfNmqc/Ar9NTNgMBcByUWRolQbFU
c3sR6kJiwSJ1cJqiFOuk+RcFmBunb736Z6f27cPteLH6CBEtcyuSl9lSDaJ18EViHoEN8eyIumFG
yOPJdhpg3fvG3+EEtgXOgdnBbIMuSTc/blncmrgefXecntg5QbTu5xxYi3xix4Gxj6enwTktuNVi
28nTYOoEXZfRY1U4QR1o/e7GJ36MO4zxcQsqr+icgttvnr/otdPkjbGXl6xPT09LU5hkoCQVTiQ7
UKJDa4LeKAeBQiKZy4U4FpJuB3Tg2O0MYVrxtaQL3wTXa3pdUgSxiKEZ4ggjErhMMWCQvJ9fxBPE
SNAfwnAqRKBUoxOuDtolAoA/iSMool0cBMzZ1UVqu1qHt2AWY7bl4iG2ZXSUYal154EneBgoM6Ej
wfUC0bGJxMFmkwy2BG7m+ewMIWCoxotIkK0Ryg3LyBJ2uVBvWENa2TVCs2EL6WS3CBsMycS43YRN
lBGWZ/XxejICet4Ol5/F+GquDXdw63EPp9vEbzR+dkMUCa+xmQgbQ6dABldD6hgli1u7IOomL4ix
+2GEfiMAnEXWn6QMQk6/IFCMlEUX/egfVh9Qt777jrpFPYy7T17ApcNPU17Jx2NG4PdTRkeB8pwK
J18C8KxHtwdLeW4eF2LC3CqGAwSn49h/wyfAhe4gIO0H9I/ricaIkdFzTiad8XHFTAd3E9nEdHNd
OiOhHHhARzqqKIK4qbpKyhvHuggR/MIigVCeiC6mKlTqL41crqvISS3jT/IxdrR7HnkQI7xh7E61
+4hag7vx7eS1TzF+gF2mfX8p/9U0F9LKL5Ee+/MJorbL05k/TWQ5pDNMAXOIGWavZu9jX9TSB1yY
O8id1ZVB6tWb9BH9/frf8ash/ddX6av0VfoqfZW+Sv9Ior9GTPyaR2+89OeFJABw6SjzyoolzPT5
i8XAoqX1deG5V9VUN86rWh6qtf6zf4X5//GwqEHL6fee6ELS+DjkmOY0IoM8E12JKtASkNp0NB8t
RiIKoEVoKapHdSgMEcNVqAZVo0Y0D1Wh5SiEalFMcBhuXPT3UQSRqx6hpW0bWpuva461IHwn4v5u
Cr/wN6YL6ML45xB4shu+BOQp9OVgGHkm4Nj/BegeQM98GeDO/GUQ9Kjs7wEuhJZSYB9DIW4ANXK1
KMQ0I59WPooGge97L4NB/gY0SPHcLVr/QQrMp2iQfRatYB6EcUfRfVwApepfQ3kUuKlwN2H+hu5w
DIaijzyxQpz5MXLFlPm9NfX0f37o8fxuZrxDvcr8EA9xKxI0e4HnfwF5VI/IDQplbmRzdHJlYW0N
CmVuZG9iag0KMzcgMCBvYmoNCjw8DQovRmlsdGVyIC9GbGF0ZURlY29kZQ0KL0xlbmd0aCAyMjYx
DQovTGVuZ3RoMSA1NDM2DQo+Pg0Kc3RyZWFtDQp4nO1YW2wU1xn+z8xeDmsbr40xCxvjGQa7dm3H
Fy4m1IWpd2exWQy7XgOz5jZre806wTAKLqKFNKuUqmgBO+oDPISKFgUJVYo8exKp6zyUqH0obSHk
VlqpqcpD1KhKkHgoj7D9z+yui1HbtGmiqhJn9pvv/N//n3P+c87cbCAAUAFpECGyI9beBXapOYmn
XaOTCbNgL5EASM/osSnpBXfvVRQ+BBDMcfPgZP/v/vQDAHEbgMtz8NC3xgvxi9GGSCqZGLtx0/dH
gKUOtNenUKj8Dv0DwCId7dWpyanjxfE+wJP30JHRRLH9RQDHS5OJ46bzigt9i3g+0uHEZLIYvxdP
K80jR6eK9kfcbz6fNJvb7tZiPG//mvPPAM45WI6ocbRDDUD+Y8SnHA+xB+cvAB4OYfYbsP4+ziiG
fB088EWX63ATj/PwBh6F8jPUrsNZ+BG8gvrfFYCf4MHLGLwAL2HEeYwp1V+B9x7VhQ6ynvjIq+Q2
hAQfaSU/x126DZ/AJ+Rd8iIZIkuIRlKkFc4J60hc3Ox0Yv0NOIyt9pMb5Ibj93AYrdvY6wHyV/Qd
F94hL4svQlpIo4fneuXhZeiCORzvvy4UPms/SoXvBy98P76U8iXth7p+KCxv7e/bEtKCgd5vqJs3
fb3naxuf2dC9fl37022tTY0Nq5VV9b6aKm9lRZlnEXW7nA5RINCqKSFDshoNy9Go9PW1cVtJoJB4
RDAsCaXQwhhLMuwwaWGkipHjj0WqhUh1PpJ4pR7oaWuVNEWybgYVKUeGozrWzwWVuGTdtesDdt3R
aBsVaMgytpA0XyooWcSQNCt0LJXRjCD2ly3zBJRA0tPWCllPGVbLsGY1KWaWNG0idkVo0jZmBaAV
fFhLbNASY1YkqmtBvyzHbQ0Cdl+WK2C57b6kCZ4znJGyrW9lzua8MGK0lI8pY4m9uiUmsFFG1DKZ
71tVLVazErSav/2RD6ectFqVoGa1KNhZeHB+AGI5G7yKlLkPmLxy99OFSqKouBq894FX+RTnlwn9
pTpgbpghzk+WeS5nciqMoGGlo3rBlmDEz0Btb4lbgsE9b5U8S3dyT7rkmW9uKDLfKs0o/o6lfFZ6
RGprxdW3fw34Q79kiY3GyGiKcyKZUYLBwroN6ZYaxIqaKM5Vy3a0Y3zCwElM8GWI6la7Ylo1Sm8h
AAWJ78FETLebFJtZNQELjNFiK6tdC/K8JC1jBAsJ8r6UqD4Ha/J3smsl/+trYC3EeR5WbQA3pVHL
6GPjVr3hH8Prc1zS/bKlxnH54oqejPNdUrxW8x0cTrZHtFvh3B6LLgXzmbsbqKQLfjHOdwsFKYQn
pbcHHV7cLtvkO9rbI+nED6UwHKUYwWsL+kFDbAj0cZfImwb6/HJcLpR/kZK/mJOzwaKP9OVFYT6n
wjj/NLVCNE+oWdKSwUcSXNCps5hgsbd/nKfA16I4MLagfDv7Si6xAe9c1ATsxpb4LvokCyKSriSV
uILXkBrR+dz4Wtv7G44p4eiwbu928Z7MUCUcy3BV2VCQQMr0W4CXk4o3zobqtQU1hE+eTCakSKGM
kUnk8ukRRfIqmWw4nDE1gw+r4xLm8m+e8Vuhs3HLa6TIRt6/0j+WUWJ6j9++KCPzN6slBIb0YkIb
iheo7cAnSG9WIaejWZWcjg3rc158+Z8e0plAhIDRG8+uRp8+JwGotipwlYvckLgBYYJPBSZQO94/
pwKkba/DFmx7NEfA1mhJIzCaEwqat6QJqDkKmmprvLTh+wK/q9zfffgMvvf+ko/kj9OrXFlQHFwR
VBgAN4TBiV15oR12onYvn8fvMaJ6hq5dIeqVqqWhV3OknHXV/zhHlqqsvv7ILzvlw4hJxCHEc4hn
EROIFOIgYhyRRIwhRhEjiATCQBxA7EfsQ+xF7EEMI+IIHbEbsQuxEzGEiCEGEVFEBLEDsR0xgNiG
CCO2IvoRfYgtiBBCQwQROdLNjlCk9ewwp3VsktNadojTGvYcpy72LKdONsGpg6U4tbODnJ5m45za
WJJTKxvj1MJGOX2VjXBqZglOTczg9BV2gFMj28+pge3jtJrt5aSwPZxWsWFOMotzkpjOqZ7t5rSS
7eJUx3ZyeooNcfKzGKcVbJDTchbl5GMRTsvYDk61bDunpWyAUw3bxmkJC3OqZls5VbF+Tl7Wx6mS
beG0mIU4VTCNU7maD1J5YndnvY7YhYgOdtaHgp31GmLH9s76AYR0oeOCeiFywdFxmlSeJTOnLp2a
PXXt1K1TzpnUpdRsSjQmzAlhZg+ZGSbmbjITuRSZjVyL3Io4Z6KXorNRcWbw0uDsoLj55I6TQuSE
ccI8IZrbiTlDOmaMGXNGhGmCP3XanBZgumNanY5MG2i4vKZqCsYUMY4SM0igqQkv5uoqqnZXbn67
llRerr8s+HDTaxCLERWIckQZwoNYhKAIN8KFcCIcCBEhIAhCPQl4vuOj8oc1VL69mMq/raDyB+VU
fr+Myu95qPzuIiq/Q6l8y03lt11Uvumk8g0HlX8jUvnXApV/Rah8HaisLNZWlWuyR5OoVu/SVjq0
OkF7CrQV1EdraQ2tpl66mJZTD6XURR1UoEDDOXd+MGzRyB49S8h03KoOQ3iodw4IyX/vXMvnLEd7
SV3Y8sd063xdPGx1YQXqsrXQGw9LaCnWeXzQWR118RaC7+Rego/CLEVvYG+Ba73mpmx3tzYhFd72
RjyY7QDz9S7ogOWmzzxql6mpo4+Xz5vwf1CmWuwPdkiT/WLasR+fXm5oVGudF8UfOi66YRl0owTu
iwRNgPYHD+6S9gP7kDo7llTJVQ1ylZwW4UFagIeAXcAD/BuE99j05HhyPDmeHP+jo/BUK3y51fBH
GH7YrUC4sCJ+kf+S+D8sDlhln+3v2HsEv1mLZ7T5//tEu1aN68cf5S4oBxh6PjnyzdFUckoaiNle
IC/jl++/W+hC8x7cyy8QSCkxSJcgTMBn7xQpIGvNvnmgsuc++AsDvZb46XLOOW1ZLB958DG96j6D
pqc0zt8ASWAgbw0KZW5kc3RyZWFtDQplbmRvYmoNCjM4IDAgb2JqDQo8PA0KL0ZpbHRlciAvRmxh
dGVEZWNvZGUNCi9MZW5ndGggNjM2Ng0KL0xlbmd0aDEgMTQ1MjANCj4+DQpzdHJlYW0NCnic7Xp7
fFRFlv+pqn7l0UknIQ9I4HbSSQjdCYmdhIQASefREYgNATKaIAwdIDG8g4mMqEsCM6wacMyurgo6
ioqOK7PDzW3EDohmZXachwrqqIy4JI7MiA8e60+Y3yik91u3A8h+3P3s7j+7n/3kVs6j6pw6derU
uVV182liRGSlbhJUP3dBvpv0p6AN6MZla5rbR+oSVS3b0Gn3bzl1EvyHRBZLa/sta7SZa9DHgjbj
sVtWb2wN69tVIl7a1tK8/Mj64jlEpd1onNKGhgRD/AWimJdQz2xb03n7iP0BIvOu1euWNYfrGafg
VNKa5tvbY15KqIH+kDS6tnlNy4g+2ii9fV1HZ7he6pfy9ltb2lf1zjtCFItqnGr8MSnGG3RIEw9S
KlHoIwB8DZ0anh26aFxFjuGVoSGRQMQywzDyZNGPKJNO0UP0Ci2m33JBXjaZGsnAUmgscTaV6piN
ksnIIimHHFRH9ZRIs+mPzEp76Tr6jNXSZpZFc+kxyqA5lESV9De0i10f+pQ20ztsBe1B7+eYhybS
DWxmaJDmUX3oRYxBNI0epp0shhRIIpkjdAIWOuhuOkDvUYgW0iPGXbBST/NpbehFWkRvsYXs5lAa
zaK1tIkeoSfpEJ1k97ABgzHkp2JaSrcyM0tgOWJL6DkqNR6LeCH0i9BRskH/SVj9grsMtaEz5KFT
BhZqQyYkUCHKWnqK9tOHLIUVi2qKoSKMtZjuor0iBz7OpHsxtwPsTrZXxIR2YzYltIy6aIjdzgZ4
uvGY8VzoDorH/IrgaQ/tpn+kw/Q5rNWyBrFmuCI0hxhZyEVejPQj+mv6OSL3KsovWCxLZ7Ng+R/Z
CfaRWCv+BMs/pdN0gf4/y2Er2CZewbcY3Zc2h16gbMzQAxuz6CZaTT9j2czDbkbfx/gP+CbeJfaL
Dw05hrOh0tBhMlE+dLfQ85jXm/QOvY/1qmU+9h7fJALGvw7dCX/zqQ2z+BE9Q/10nhlZBItmY5id
FbISzOxONsA+4uO5gzeKpWKvcXtoY+g+SkeuLKYW9FxJP6St9CIdoT/Q53SajUPPfPSsYPXsPnY/
+wU/Im4Si8RDBo/hIcMew6uGi8Y446vDbw0PIerSTgH5UBZTK92BWAdRDtMHTLBUNgGWZrDZsLSE
tbK7WC/7O/Y0e5btZ6+xo+xTdpb9hafw7fxBfpD/Ez/Cj4rxwilqxBPidUO64QPDN+bmS+OHXxk+
G4oKuUKFod7QY6HjodP6KqQh4yuoGtm1CnvBj6iX/o5+gpjvozfoXeTdoF5O0jmswTfMhGwaC48y
mINNZLmY3U2skf2A9bAH2G72S/YRO8kucuLRPAPFyafw2XwR38K/4BdFpHCISnG7eFi8Lb42bDS6
UfYYXzCeM500Z1lev/jopRPDNLxi+KHhR0PFyEUTMi8B71wRVSHnZmOVl9N6lFtpA/0AMboDEX8M
mbOXNDpIv6LXEfsjdBw7lPRXlk+xEl/RJRpmHOtpZBaUsO8FWJlqZIuftWBtw+VOtoXdyx5BeZQ9
zp5EfN9ib7N32CD7mJ3HnIjn8Up+PWZUz2/mi1GW8GV8M9/G96G8yd/jx/kf+NfCJuKEIiYKr7hF
3CN6hCr2id+Jdw3ZhkrDTMMqw2uGtzDzmcZZxiXGZcZtxieNTxtfNf7GeNIYMj1gesoUNJ0yR5qn
mOvNDeZ7zX9vPmj+0ByyTEQ++eD9JLr6PMBuNuTzXhbiQcz7Zd4pfssfZHu+pUHGHniwnJbwoDjE
f3JXr/iD+BnfQmSo0cUzsIu9Ti/R68Z3DInGU/QaH0dnsB8+KJr5y3wHT2FTxDTDVsPr2HU2ws+n
+SA3873Q+ByrsYS+x8bSl4Yb6Szif8TYg5jW8hNsD/8ln41MPka7+UHaQbuohZXAu+X0An1Nf8P6
hZ3tR9510VH6goauemvIv1TFK0wpfIOpDCvUz+aFXuOTQp/jrf+IbaXj4mvk/o1sDsunZ+ljrPq7
rIgphmFDKr2FnW8CPYqs/YQCeAd/Y8jEG3Se+kURLTQMYc3zL/16uMbYKX7ILvBKLGeyvnPPlbsx
9uBHsFfJfTSG9iITsIvob/Tn9AbLQBTfMX1AO+l+OiASKUs8w7t5SPzKYKe/pSFxA0b9K+xPaawI
ltbQCszDHvrT8G5YWEmlVMqWsoVUA8lMmhBaA8+fxV7kCS0K7TA2GV30JruBJdIr2L1SEMWHjBHD
p6G5D+/hcZrJtlFgeDkN4FxJYVnMjWw6bdxg7DU+b9xnfNn4huk6uh1v7aNYxT/QVzg17GwZYvEZ
/Rm5XoW3JxfvTyW8mIkzbDVvEoeomo2jduyBOdi3qxCDhVjJDljZQtvxPj2DM+RNOsdsbBG9TMfw
5iTjPV+G8S2wU0ffw6p30LPYHX/IAmhZThPIiTh9zWJYKe/EeHKffQj77AB8+pD+hJ0jpPuVy6ax
GqzeMvqzfJcxwhSqZ304k/fTVJyUNeJ1+iNl4nStwju6G/38yI0YGk9TjR8zTrnDc0KlfIU4xJJw
GsYgqxpwss9g6+FFLOZxiRLZXCoevh7W9mAvqzc+46ls8FSUz5g+rWxqaUlxUaH7uoL8yXm5Luek
nInZWZmOjHS7MmF8Wuq4sSnJSYljEuLjbLEx1uioyAiL2WQ0CM4o1+uo9dvVbL9qyHbMnJkn645m
NDR/q8Gv2tFUe62OavfravZrNT3QbP03mp6wpueKJrPZp9P0vFy712FX36hx2INs4bxG8PfVOJrs
6mmd9+l8r85bwaeno4Pdm9JWY1eZ3+5Vaze09Xj9NTDXFxVZ7ahuiczLpb7IKLBR4NRkR3sfSy5n
OsOTvWV9nCxWOKWOc9R41bGOGumBKrK8zcvV+nmN3prU9PSmvFyVVS9zLFXJUaXGunQVqtaHUU3V
qlkfxr5Czoa22ftyB3q2B2201O+KXu5Y3ryoURXNTXKMOBfGrVGT7ziZcrUK4/HVjXd/W5oqerwp
K+yy2tNzt13dNa/x29J0iZuaYAN9eVatv6cWQ29HEOsW2DEa39rUqLKtGNIuZyJnFZ5fi8MrW/wr
7WqEo8rR1rPSj6UZ16PS/I3p2rhxnv7QEI3z2nsaGh3pakWqo6m5Jq1vDPXM3xgY67GPvVaSl9tn
iwsHti8mdoSJtn6babki0zldXXJ1869ElkmPHLOQEKp9Ge7S8xsdmFOpRC2l1LOsFGp4mhh6qcux
IivUiGp/j61Mtsv+qjHL5rD3nCdkgOP0F9e2NI+0mLJs50myMk+upBrkl3nV5VKdTpki5mqsKXws
1+vFebkbgvwJR7vNDoLwUT1i29xUlo/wp6fLBd4W9NBSVNTueY3hup2WpmrkyXc1qdwvJQOXJYnf
k5Luy5Ir3f0OZPI+kh8oiaol+8pfrC0pwdtWprKk/0DcEpbXLXDUzVvYaPf2+EdiW9dwTS0sL70i
G+HUhOpGkcpHOJ4qdCmSctEVZVlpjFYNWfgz6Um9PGi2ICv1FmavVW3+mWHcFJme/p/sFAydk710
crXbiJtqmeva+rRr6te4F90j4LAhm9c1LOzpibxGVosdqKen1mGv7fH3NAdD3Usddpujpx/XlYk9
7V7/5RUNhg5sS1VrtzdhEm2sDNnKqarPwe6Z1+dh9yxY2Nhvw2fXPQ2NGme82l/V1JcJWWO/ncij
t/IrrbJmlzV8OCHTNW7RRan9HqJuXWrQG/T6siAjvc1yuY3RsiAPt9n0Njx5cu3N6cNeuslG39w7
nA1nGF3zsFOyxdRDX9J0Woe7JMdXTz5OLzLfHQrhdskPUENowCACXq/bEwR1TdapljPJ3S8F2rg0
9yEcATvwIaOggWlJqbqEtKqqEWZKaZgJOPPcg5WRBqKzAG7A1yKOV71XIGey+9wrqDMxTLGMyVZx
MWAbg9HEpUBsgttTaRN/oXoAJ1X00QCA0zpxnroAHOp7tbzr5EBibyAyxm2D/lmyA7oBgnYBM73u
AUj9s4GEJGn+Ey02Tu83qBUUhZmALcVdXzlGfAh/fi3exgesgivh2zjEFfEa6HjQX4pfkVX3c3cg
1ubuxnhPQ/1psZEmQfyMuIPcoM+JTTh/pdrvtZjwOL/XcpzuykjxU3GXrtIh1uP6oYjVYpXmVuwH
xW546hFfBCKipH9faLZE9yHxqVhFY6B1ElrJSuwhsZbyAXImwUCE1d1bGS2CmGYQYVHgI6MndOwR
b2swhPH+XnTjQ1sRR8RmXOkU8bzYoiUqAwfFn3W1C9IKxntKsxRKErDGuAcqI8RTkKriS0T8S320
rwLZpW6qzBbbqQDAEdSPwX0sk0ecAXcGy3QGS3MGS3MGXpxBYpE4Dclp6OSLE9QujlMv4AnwBpjc
qCGC/TqTmePuF38l7kIkbAcRO4bWTYGIGOnZXVp8gq52VyA6xl1xSLxPcwEczh8LJKe41x0UP9an
0htISZUdfqdFRCN0d4bXAh3vkGtwSHSLLXokNusRUF9GlVGs+KHeORSIjnN3YfUbUF0HfD/gKOAs
wAC1BsyhgZYABNTrAzGx7tiDYqHeeZYWU6gcEjMx9Zl6tGZqiRm6z9cHwMw7KOqQJHPFHG25Agfn
aegspXMCpWXugoNijj7hOZriCDdrCWN1plaLCCdPdSAyTg5Xoyu6NEuM3uwaee+EMzAm2a0gGcv0
KRXKF1yUYI1KEP8SvAyFesTdAVs8Uny5cOtuu8kP2AVQAQYspBvqbiykG3d3tz7tKZjTFAoBBBZw
Cp0DcLRfRxWA+wGvAIYARr3VD+BoL8AIfuBeAIfFfNRtwB6AH9AN2AUYAJwDmOmIyMM4edAuAO4G
qIBBgAELkgs/ciGLF3a6ZCFSqIvv8JSxLupiXbxLdBm6jF22rjiLpzgr1+1ZKdFkiXKASvwR7RHd
EaIgwhNRHyFsEfYIHgwNaOayQhBPvKms8APfZ76vfSK+pNfUa+ZHKqNZHA0CzgIEHcHNexBwltk8
d4sj5YPlZ8vFEd+g76xPHDkxeOLsCXEkbzDvbJ7w+FLL3CVL2DrWxe5nBoXlswo2lxmWiHWiS9wv
DIrIFxXIBYM/qj2qO0oURHmi6qOELcoexXujdkWpUQNRR6OMqmnAdNQ0ZDpnMtab/KZ2U7ep17TL
ZFLM+eYKs8dkOFdZzY8jqLuAVQCnbuBenbPpkgHgo3q9V6/7gdv1uge4XuccwAWSAzhg6wPodQP3
AqSerDuAC2Qd4MAW/nu0tQP3Ajj/vSctoyDTk8ltmfZMjm+Uc5nsaOZQJlczBzL5QGUZP6Z7eQxe
HtO9PIaex/Sxj8EuOIAD3r6v670Pvfd1vfehJ7nvavMDt+ucB7he5xzABZLj72uOktjKZP4oLC4B
fgIwCBCUD1wBWKfXFKnBHwX28J2Bibnu7iDfqWVjIwTJCJMJYZKmk8DYce4llbF8J0zuhMmdMCJr
CqBC1kIDfIdWI3V3aDPCpKxwsLIER6V0ZQftBXCaC/yEzuUDV+jcXl0n9kpdBR7SuXbgXVf6LdE5
BfhyX8F3ouwAF8vvQOsdnihOSUk46uPjLPFBfkBbEa8E+T4txwYSCBNNksoELhB7Kzuj45/r+Akd
P6jjm3Qc64lyWP/isP6Tw/pTh7Uyks+mTDSf0/GnOl7picm0nsq0/jLT+nSm9alM60H2MWVAkO4Z
l2H9Y4b1nzOsL2ZYn8+wPpBhXZRhnZdhvSFDmsohO1n5eInZ93Wc5km2Wy/arR/Zrb+1W39ltz5p
tzbZrWV2qLMvcWha2WM6fljHxS8WWZUi6/gi6wGOnYndrMVSxEHO2c1kFZGas1wJigid8HTNlwWS
pvkqQVI133yQcZrvVpAEzfeAUhnBY1kfbiQKj2F9FkmjNedmiKPCxKI5vw9i1JxTlSAb1pwOkG+0
1vEgX2utE0AuaK1FIOcleYn9P2rFl7LC/kVrfRzm2WeUI82yTyib7wENar4KaL8YHp3to3KWhWZ8
FEgv2M80J5xjz2nOHJCfas5MkGfD5GnNqYA8qbVOBnlca30A5Cda60mQnVrOamlvB+Xodh6hbJ12
aL5UiNdrPmmhXfPlg6zTfMUgq7TyN0BWaOUnZddbWB9DZrNWcuqeNmutToiXjExkMeXo4kVUrFu+
XvPJkNRKI5VW5h2ZSA2rlhc7VsX6dCsezVkAtXLNmQ0yIxy56VqrC6RUy0GMWYmW8zgiN2VkgEly
fV5imXBDGnJozj1QUrTWSSATtFYvSKrsCacSRkaNp3LdqTjNKbVsmtOuvMyiqFW3GEnZbOd+5RLs
flMeZDdqyteeoIVpyp9zQPYrX/iWKp/7grjWKp/hFd6zXxmE6olysJ4o5UPnSeV4a4byGyc0PKnK
r52TlcPZG5VgzkEl4Jug9MExtXWpsrdVt/DzbHTTlOdygpyh967WG5RHnC7l4eyg9OFvoXy3HAOG
tjo3KluyNyu3IRU6ffcqHc7xSnvO95WVOXKgZGWFc77Shoncgj4trbcozc4HFH+x7vH3nW8oC4r1
OdS16jOaVa4LZrbOV2rhAQQVUgAPpiEv3eg6ufigjBHlserAG8r3Sl7iOIVZN+BWz2TzIfMm81Jz
g7kK581Ec5Y53TzBPMYSb7FZYizRlkiLxWKyGCzcQhbiY4KhIY9LfmeMMemfGyaDxAadt3GJOemf
IZxZOM0mNUHU8boFVWqJqy5oDs1XS111qrn+5sY+xn7cxOrUgWVUt9SuXljgCLJIfMMZHVVMja+j
uoaqFCir/B58DDU0BllI9tiaKv8x0k+M5W69L1XS2q33NTVR0oaKlIr48riptTXfgfwj2Fvjuvqk
uFzX1MarD9UtaFSfH9+kuiUTGt9Up06S/zzp56v5Sm9NP18lSVNjP2vjq73zZTtrq2mC2jRdjcr5
KqiRTxKo8UVULtXQvuhbaqwPzTV95eVhpbmsTyrhpZmrKy0MK1V/W0lsY9W6UrXYpis9Hh7QCT8w
oEcSqBlXk1Mf0GlcraulSLW+7GxYas2WKn3ubCj0Zbt18byr4pyw+B/C4n+Q4iBjV+XF2WFvcyhb
HyGb50DH9T/4tFT9NzqxwIwNaxvlP738Dm8LwK9u29CWonYvtdv71m4Y+W9Ytn/psjZJm1vUDY6W
GnWto8beN6PxO8SNUjzDUdNHjd6Gxr5GT0uNNsMzw+tormkKzNlcuv6ase69Mlbp5u8wtlkaK5Vj
zVn/HeL1UjxHjrVejrVejjXHM0cfq25+Faurb+yzUFVT9aIwDfCoSLwt/tT0pqokW3u5/upMS0/Z
lHrAQOw5inI1qdGOKtUKkKK8yrxKKcIrLUUx8h+bI6KUTdPSUw+w50ZENjTHOaqoM8W7ogZ/HXg6
O2/Dgxh3dIRjnRIWdLq8uhwKneA69Qea4CV06K0j8k667erjcoV1qcNV3djn83lTVtSk4hIfkPdu
V1MHuVzhAV0uwpiYtX7RT9Iv+lGmpMJ3fX/0nfeJAf2GfxQwpN/wB3C7PwoYwg1/ghgoP1o+VC4G
fEd9Q9A9cfTE0AkxkHc0byhPlIx4IIdqYvDwarnN1XGbbHYxfbb6vFHtdHW45JQvxwA1l2yVUcET
btf7uWDFdaWv6yrTERbepncJt3ZcTWDsq2lExjQjvvrwJVW1j7PDJnNQWDwJZDQcFhRpNhxmNNZi
Mh7m4iVWSREsi91IKS7bhemXps+xfTXdd2k6VYC3XQS6riA9Lj0uC4ilGeiiXQxc9BjpG7IbBkhe
tEMnxXvGdqqgWSxi/8IodsHO7MHQOc/kuISiHVGfRPNZRU1FG6JFfgJLGEzzW43p5r0ZsSZm8owd
X2QyTWR7sz2cyU+wwNjUIkn3x40p4jytKigyAp7pbHpQJAZsk9nkoEjbb89l+bksN8gyNLd7ZlCM
84ydgg8m9LQYBZU7sxz2iMiMuROXTOQTD/LDlEM2luGJS/LAZtKqCRNic9pzjuQIHMBnPYmxkUok
j4ycOvnV/OV1JpbrXTd1+WzbhdNfTQeKn5q//vTiqfkXXKdtXy2eHp881UUVp6fbLi1ef3LxV4ul
3OVajwAV5rsWg1ScPr34ugJavJ65AI7iwuyJEhUXxRe6kxLHmBwZ4EumFBc5MhLHJBcmOpIkMiEb
3SWFUjwxrDKl0J2cbc52ZJgSx0DGJoV+FxFzaA87vvvO/bPKKr2czVuQ99l7JnbkTYOreeOAMil4
1+1b591505K21c6phoiK0snFJUojN2zLqN1uj9vPTA/7y2+oL4uclBC75Hbv6e3lzm2bu1LW9L/U
2blqWkVnXMM/F0zOcDjl709Gy2gZLf83CksbLaNltIyW0TJaRstoGS3/9aL/SIKP/GpiDL6o9R/v
k4mi9X9iMvYJGShD/iQTBVrnWCh0Gct/ewJ9Ev6hBcXLn8aCM8kf3zesWNPSYZ/T8gP7/HVrmteG
NYj1kpH+s4/l2uo5Ohe69qcdYWKaytJGYRRGYRRGYRRG4X8P4HrgGLlT/PuPPMeh06fuPbAkdvp5
y9jwwf/Ux8W1kva/+8Ksb+69tN1GlmLoRlw+9/8V7OwL6A0KZW5kc3RyZWFtDQplbmRvYmoNCjM5
IDAgb2JqDQo8PA0KL0ZpbHRlciAvRmxhdGVEZWNvZGUNCi9MZW5ndGggODM3Mw0KL0xlbmd0aDEg
MTUwMzYNCj4+DQpzdHJlYW0NCnic7Xt7fFNF3vfMnEvOyfUkTdI0aZuk6T1tU5qmpVDIoaQ3AvQC
LRQMtFAEyq1yk0u1uIpU5OblxTuurvs8j/qopSAWrCsPuoiuKKjP+qirKy664lplXRZdoMkzM0lK
8fb42ffz/vE+H3M6kzlz5syZ+V2+v8tJAQQAaMAmwID6ummeIkA/pX/AVfP8ZW2d0fMSGQB4/fy1
qx2TH56AcAe+Du++unPhstKGkzkAoNX4/PzCpeuvjo5X3AlA1pOLFrS1v3rmngcAGHMTmWQR7kgY
K54AgF2Kz9MXLVu9Ljp+dDGeo3Dpivlt0XNPAAD+0rK2dZ3cN8xHePwu3OlY3rZsQWx9h3GV1Lli
1ero+Zh2cr1z5YLO9Qv+K4LH9+L5/sSn8kbuLHeS7WJDzPtAAiDy58ip8Lpwe7iFuRPY8T27wWPg
IDgKXgPxzwA4Qr/Xgj5wGPwOjPzcAO4E/wJeBe+CL4f77gZ7wOOg94pxu2jvI+BR8CTYBw6BF3Bf
D7gN9/4a/PuIcSvAFrAT3Ad+Cd6EKbG+F5ARRldwBqjRSbgK7gBWkAcC4CqwClwPbsbrOgYn475x
uK8e964E68DtuPcgOAa++xkHmkEIdIDlYC8e8R+0Lxf3TgftuJf0RT/XgA3gFvAQ+FfwLF7XBryy
28C93zPfDciJnGA1+Bjf+Qr8P+go3tG/gs28ESgB4E4SqrIhSlsQOQVAuD3ydwCYeegcehjdBp5C
HWCyrG2aXlqSmWFPMGjUHIvyHL1MRqWr0tW2aKujcpFjqyvQGsjPCzbOrAzYnM6W/DwH7g44emGr
o7K3au0iy9ZKMqDX4O5FGZWkdPTKt7bihivgdDrxlYTLV/ojh7eNuLQX4Gctmj6TPJKU1kWOXhZf
pJUN98RWQK4tasW1K4AX8L39VyyxylXVunVrlctRtbV1a1t/ZNM8l0Nybd0bDG7trGx19IL6mb0Q
9x+61dZbta2lV2pdBMfgnZFFVDXO9NucejxLcJor2DBrpqNya2ts3ljP6OjZXgQq9rpgT8NeGfZM
mzXzIBZqR8/0mX0IoomtFS170/G1mQcdAMi0F5Fe0klOHOQEBCFedR8S6HjbQRmATfQqSzvo+fx+
CGifEO+DYH4/ivZJ8T6E+9hon0z7yAeTCk2cPnPkqnEha8cCgbFGUIUbAVDnRe69+JbqDtJzxWcb
6WGuA/OAAiwBHH6GBDxYggHiIhGMUfAgmB45LKf25RSVSH2OPrmvvq+zb1PfL/t6+070fdinPNx3
tg9hlsudTydaSuwBqGu2N6O6prlNaMV0+OD0p6ajhmmJbOM0Mzut0cROqm1kq2pL2eraIrYGl1pf
GVvuL2LH+cex4/1OdqI/ha3wN7ITcJFx8fuK2CJvO+v1FbO+4ulssS+VPVH8YfHZYqY/8sW+/Rk1
Jf2RD/ftl1z4+wtZs1/Uley31rBr9928Dy/r7L59dMQFObJPTC/ZZ6xhb+lJYDuXdq5Duvv/uAfJ
D5iTSuT7zbYS+a5E3NqdaCu5eXOCXXeTbrNuh26nbpf9JvsO+07Pjk2bN/XsvG3X5l1bdvXo5F+I
UolupX0lkq8R1SW6ZdBxDDpegv6jXx5Fjt/Kv0VgHgTzpHlIbvtlG9LNhvlGPZtnzGDdxjI215jA
5hhNrN2YyjodE1mHsZx92VrJWm3VrM1azlqNRawJj0vAyzUYrawel04jlI0TJpbotLl2wEPNC0G7
+kjQrjwctIu4cANBO/tc0M4cDNrRoaAdHgjawTNB+wtHcu2Hn8+1Pyc3Dzjthw467c8ccNqPvPCi
5vnD/6EZeO436oOHnlUfeKZfLQ1sGkDywU0Hke6A/0Ddge4DrO6ABzdX4ObzB14/EDkgKMVSVq1B
GEIYhCBA9Rzsh5HN27en9O7GQt67KaWlXwBBrOywF+5o6RWC02JN4CafVatXrXJ/z6eXqezlKxe1
9fKuwCpyoiUnWqz82speHWnrXAE37DVWLuo14tZ3JlkV/7hXxS5GH0QrsOb7nknWshrX+DpARC0U
gMeqgL+Mz/CIBaR4jr9/nFajCp16pz4DVxCPurCJAxfJN8ANomVDuPocWxQGOA6gZiiAfNgf+VRW
6nSoyQP9EEFPyD0I/IN4HpfeCz//8ks8GoFbIqfYndyXQAVcYIucVgLLVMXqsYaxluLUSlirCqiD
hqAlkKo21YrIWcsodf2RcwfUatSkcwIs3PvJ/LhxTrapVLhlIZfAngxdhj0D2dTkzObk8UA5gYzk
JVHEtZqM5e9Ol85jKgy6Q7FvvDqyvhCUkNOB9JLB6TDAkhJfcWZWZqYrjVfwvMloTjSbvUUl7M6L
4W/C576+AEWo/jr8D1dSUrpr/dw5G9PTkszpzvXtc7rQmfCK8C2wC26F2+HGcPelpxveu/fuD6dO
mTq1btIXO+5/Y9rUxqmYbNCM7Vc593ugAz2yj6vieTWjZWqgoNPb9YhDdh3U6dRauhmtRq3mm7QO
5GdWMJ0Mw6glCTVhIPhQVpENMmayQYYQJIVskkkldzG8RoNrSaPhcU1mYDxxIQh5B93usiJPyOMN
Af9Qkd/rITxy+jCnfUUlpSUlpV69ky2/9C4sCb/i35VR4GPvg4V3M5/0mIxJUyZcOIK5/xDewW3c
WeAAp+SGenurHXEMrzczJn26fiw3WuPT+lP8qWX2IFejqdTWpdSl1trnMiE2xM0Wm/Vzk+bYQslz
U+amdjDt/AL9PNOK1E60Wt9t7U7uTs3Au/l0P1k0IhLlJy2gk3T5gie5UCfreJ1M5UFW493pdKpJ
CQjZJ0HBjgSnWU2IYlYTophZQhAzIU0SucFsJjOZzY49abo0exrChLzHKZ3HlCAVpc2goYySZNCL
z0OjCnEFQ5g0JYQsWCyITLjwmZeAFREP8udkb7skLX5z9uEd99wy+60FyurBFR9D1p2btTi45PR8
xnly1v6WQ+91r75RrnjDNeb955ruqBi/rnbxb6djbbBif2YO9mgU2LN5cZ8sQq4/8g3dOx9vKMgG
1pLWJL5SgURRKaAtEEIjvklUMltYyBo5ju/iVykQU6yUiXwoZcL/QqWs7FQySlHJM3ADBzlBp4a8
QmQ4NUgHZaACzMLu2Wo8D1iuxpeUnJsr4aZwTdwCbiOn4NpV0ichTBxPyJBYhmUlVO4vK8Na7cby
AkNbpKHQ4cOHo1/CYRgisBNyuhgn44LOBAi5OW/ePtR1+8soFQpd4YvhC/DBcBt38tI69N5QBpah
VZGPuSruc+wprpCbOagReaMZ2kSjKcNUYpponC3MVM7UzpZmZ7cybcZOtFbXaUwwm63FBpSbm1nM
K83gmjxdHtTl2fM8ef68FXmcw6Q2Ep6rkwn/1YvcRM8HyRbKAeEpKWTpGZRxrrT0rEzkKzaUlqR7
i8yJJtd3lL7Uy1WVttSM29n8cPjrea1LF82bCzWPrPvydt3Gr7Ze83R15ZSmiVXPLtp5YZl2qSU3
McE2u20uzDjSD9Pa264eU/uXhXNqpwQ/3v3AR9WTqufNw3s+jvm9BvNbBf4hdyeJzfAqzA0xWxwt
ThIXiVvF/xIVOqgUU2ESyoVusQyWiT5VLawVK1VXwQWqlWC9ICHE9MBjGGD34WkEcR9SYR7fpIQC
4pQKBnNZhRilUqdxgEIgA7YeP3a5RtZAgREoVhg5LZERLGmX9hNq4ca7UTDh6AB8/sV+ojC48dl+
Iki48dV+giWkcYCIIrdUTTGUfobcRZjEoVCRx1CG9afcX46/oyJy+PCGIQt7GG6RNgyFLERKrlnp
dEKFHpsEPfRCbk04MrTvzqNH0Ztnhxaiu/aEFVhCvmbEoQBeNo412LWYWhxYcwAxrA9bGYIICRQR
gEKnwKIP6WZgfDNweDOQbgbGNwPjm8GNM3QzpIduBi7lL29mMKTHyk8sAwFFPYHCtZcaj6JPuZMX
/og1Fq+JuxuvScLxx0V5mgBTYD4cA8tSKnU1xpqUWbBZ12JcARejVuUC1fVwjUpPGCUBSWEtRlQt
Sc03ydibRpylmHJM57Q7ZSejN+k0UIMVX04ha9ckk4Vr1GS4xkJWqtFIDkwXvHDZTHpBEiNSdDeC
f4apf43x0jG8/SLMS487hNWcmorBEGEnRkWq9QbCVMJJy2GCitCJuegsIqpCwDAhajUxY6kR4e4O
R8La8Jmj8KEt+2saZj+8oy2/2L22/syxOdtG5btR/VAvd9KV773v2ofeKYW/kuenpSQOvebMz11G
vIu+yCkuB1M5Bbwq21wGl2UcM06czEwWr024NlFI1jAmDAA2ox174XQzgKAldQgIbfTUSaBGAJip
g4DlVk6hA5WUbkoqQmvtOrvdLtsZnVHdH/mDrCIkVFOzgc8/idJPTefB5+cp/dTECSEz4cY5Kkfq
qIeCG0tSR8rRiDYRp3LiaBijwEMo5cOyNYwz2LrovVxOdcOU127ZdqK6ofqoMyvvro4lu/OznEdR
88N/rZ9cNamm8dNHmY2XNq7fVjahYkJF2R3LmK2YVldhVdiOaaUGL8uPVTMLmfUMo4EqxLKI4wS1
KhEmMRYuSUhS5TA5Qo5qLCpjithioVz0KseogijABoTJ4kRlUNUEZ6EmdhY3Q9EiNikXwA60gO3g
OsQFym7Uya4SusSVyi5VgdqIn6ow8hzPMJCRCXlEWmNnUEQYf7BQ8ohnkDAWFPNBEOA3gDU8D1Zq
7Vq/dq62W8vyCzXSFyFsXoDfT4wLtbZYtobwHwyBEIQu8ueF5E+xPXzdH8MvhV97N7z2d7AMFr8M
S2Ep1kcP+9bFPO7kxVz29xdT2Y+wdi7C3mUKuw5kAi9cLLeolawrSWlysW4DYVAerfNp3aJtSL0q
b7G2NWVF/kblBmNnysY8JRKyxxXqZT3S6x1CXTJMTrb4HeyoCQJGV10KTNFn+ehGEeH9cIOIBWnI
1MFAVpCiAjwRJWCIieQnMZG0UCpZYxJ7aX9MNqkvh+WRLow6tyZRJE4PldXbfDqf3ef3MQVEyMm9
BWSIhtxSIJBbCmwqEu+VkmeqqK+rEsg4FbWDKjVt8+RhKjOZmLRxTVVBtbn4sqBinxhzQvrkcsig
L5OGKDBgNwnzapCY0JCeAAKFA2L0MRa4fDGLmukrxsKcXnrZhY66SxQkGD0fs67En055Nqkp27Oh
8a43li24GqY+kp+b3Tlu0oE2ZemJBWufkv0VzzafCTS0r752/iPX6scZEu3H7ut+ID/fIaTI0y2J
UlbG87r0LE/B7UvDKVgYjAmJbU2tbVOwDBzEMrCLN4IE4IAGOacY+XRjTYWOAKrUBU2yY4ZhoaFb
2Jis1op8YoWeVcNUmVeqBGOUlXyTMR5xGG0jI46zcXw5J6soA7Ux7n2+nzIrfjtu/E3OoZzbhd1M
fxrS2kSKISL16EWBDCdtXFsxeHywn8JOf+SjbwHOF3GcOS+rKPTw5E4KQBRu+iNfHqAA1OMcaYwp
t0LSucsspYwjMF52BQYpiBEm3DEwUddWH410dtVNrH7s6rk7KtW9A3V9K45+fOSmOxr/raZ+Ve39
e1Hptg8n19XlYwfMOPTWhGnhE+FPjr1ePXpoU3rycYLciyN/Zv7GXguc4Gl5ss5V50JumKbNNadb
xkCfdozZZ6mFdcqAts48wdICm7SL4QLtBrhKmyBJRr+adTqtfkbUuagb66KOPlDHCP1BnNAfyAWU
vttdiVSqE20ilXdRoASmGiDSwEikJBOx4lBKiZvT4pQadMdaI13DEPUNY/gsgRFeYVRoaXDE/G3O
o3PXv1JTWw/zv249OEXZ/MyMXx58+pGytZ6cGpOyKr+ouqbmD3dAAxxdknVyYs3bJ155J9Vi8uix
bC7FsjkxJptIzii3FiaPdtRZK5JrHDP5RXynJBog0nOWCVoWCqkVnFJv/AGs0USxJk2Oied52UUh
R6BSKo2wgLmUfMoY6Hwh51Os0UXDKkrH26NyGgufabxoswkWMpPQHwnLbjKbQGcTaEAt0JECS+YU
qCQLAplJ2DxCEgfd7hE2MCqZRUUgLorYv4oChysN6QlqUJjQexn9CIKzEwcaehce+0tDZeDptpk9
wYGByeuq9/T27K5/ZE3VVFgM9Ts+mDq5PiMLnr4QQTekWf/wykuvVwNM6Y7IJ2wr2wUs2E87Jmdl
sm5NITtWU546kQ1qgqmzNPXmDk1r4jrNhlQtLLfbdcnjTKyKuJdJFBxVCr8OK6mT4r2TCmISobKG
tqzAERPKc3KA0nCnkzhxfidjh5Q4kLoY0GagZDRQshmofBoo2Qz0ugGRmw2bhz0wTKSo7hIk9nqo
bLqpB0YTFc7LkYkJU84B9ERKDaYY2LKtl14eX1K8s3nln0cp5x5dFv4sfAy6z33092fgHbvv2qdG
toX3jCosnJ13PLsEu60mLKMV4W/+lnvnw303Yd0NAMAY+FRMs5fkhVYqWVbqsgrGMuMajsHuuN8E
VNrxgp7TCAAbfSTqRC2WOXXU0FATQ1VORaVCBamJser0QCtrpFKtmcio1kFm1tJ7tMPopi0gT9IS
CaXWUGsg8+Dzi3IsB0Lm0t6SNFKmioqKhqINHHt4qIny4vh9qIjGedg2xbTX5DQRb9Xl82IDReSM
MSjt7Znrl8Fp4X0D3d1Hn/UvyOXmiAlLtmXuuTSBeX5Pxkv/qRaIxoZb2IlYjlygEHrk/HEJ43OL
8sYUBsRgwuTcirxg4WwY4maZO+BSrsPcxXU69GmcwWnKllNZRdw7JQ3ZRjalUKhkRlMwwaTQ8ZB3
phdRIhviKm6IqzhpyFEJsQLeQvW74Sfot/W7ul1kL/IXITcVPTflittmkcgsFqLbGWQmCwVLC+Wf
heaOLHQkaeN686iR1iQknf4B92AwmjgZVu8MCTgxlvq8w07ut9W99NvqHg6Hz7U82qgsONbeer3L
ldp03zqs/VUTDl3VdmMttkfBG+T7+m66p/HX3eHT4fNJiYcNvoKcrOWBqwMTIY4rd52cXF2XlV14
6feoLS3lxNGBI34s1wex4M7FqGuGXjmBMZlNa0yMpBEqElgthBrhexH2G2psUNy3x14dCZwoC7Dn
JuspG9gRbCD+XKwRjnkIaXH/bj9lC/HRiqkJowIdC0Vus9gtrRYkXaFDwggdsmriPoJmOO2noYM1
cR9BE49ONCT8oeqjoVPg879SZ4E0qAnU9CSOUKAo866AaYo8bhL3+aMuntOlH/bm9HGXwWxi5w4Y
LElzglP+bcrAwMyB+U//BnVN2ZKZmzN57KXfYOfgeG3ju8cJEj+F3YIbufdonvlXcgIMIEyeUsTw
ODrpFqF4OyVoHqVVK0s3xlIqsBRJWEoF1goRjepbuzmSJIsShBsmCKcejnJjwe35eLh7iXISNyLR
cLdHGN5u6HSUAqfdNBLx08wWxCjBkJT1jW+9pR4Y4CwvXMhgQ8S3eRZX12I5YsB1chaCUCBruT3G
/6iXQqkO6JKBtRtCGF8qHF4qVA8nJmL5iBgCQpbcDImzQhs97OWF0mXSReIV0oT6tQMDeClR6VYk
YoRyw2NykElnchLSE3ICjkDmM7mKAxkww56SLCRWZKexKRyUkgU5H9rzC/Pl/Pr8znzuhxefT0Ar
kSw4n1o/aKHbEGJZls+oXwwJTunpfgrpoOTYlr6iIg9JIt5NN0MNHWyTMlTJOvpMHX2mjj5TR5+p
s0qUFuQ5En0OPn8jGjpJmWS0RFFOItpJppfiaoobF6mY40ZEdpJHSXYrfYyVPsZKH2Olj7Fak+NM
SR6O8pPp4OS42CTHuZM8bI+SlWSK5GjYFm3IWvKk5Da7JEubJEbyhM4Na1FUs6Qrz/VlZdLlITFV
C5EkC9a28qEiHFiVhb6lcjhw0n9LA01R8IzqoSJxQGNKbG6o21PHsNHmlPuISj41f+WDWSsHlvQ/
hbpqbs5259WNSxyXOuRDXZM2Z7vdRE3ZUFdtY2tTa9Mfj4E4TmJJMsOcb+Mk90/iZOIInKSJqGFQ
DMcTNx8SDn8LFEkOLJtK42V4pMAYBckfhkcqlVfgYlS3hgHz/xYe/yd0NP0EdKRkx+BIvNRT7DWY
4iqQCC7I1rHaYqnYONYc1AakgDFoFnR+kTX5GaU6SuhY1imWh/oq6hipbUlyjKaX4jHqh1Etir0e
64+8G7dAX8RjqPPxYPWCPC4arCbpkuxJ/qQVSayBpc4IpbiBUtlg4830HRrNYPDUmeCpH8sTc5dE
Zifv2nDN0rcXLJmT32y5IhwYGQ8MUjLS928wBCXgSov6siAai8b8gWvCn/5lMHwGJg7+BVqOPHbX
PY8+dvfux1FB+Mvwi7Ac6vExLvxC+Mt33nzznTfeeZtE/+F2dhemKImw0uSMIlRmKnJMRLWmCkcz
jvyvF7qSlfHIn8ORv6hSG+M0xY3zVIpjkX+MmCfi4nw2ihUkTxPNKcZF+LtUPf+jKQD1T00BDOcc
h3MBMTT6SbmA7yYDfiQbMCy8384GTK2u2Nc+Y3vtwEDw2Y5XTh3ZurPhkWD9qtoHelF5z6mpkxoy
s8N53D/W+JvCr4c/f+VYVdnQlnTrW1E8YVZi02kAA7IRaCSNQ8OoRR1GmYlKHSeSbP4nw+kVOZsS
ExhlY6cRqRWUBApKLwXdrILSS2EV4/QSh01qjLhxeomETHqaEUgnxBKV8SwAJRZu/COaDuhJ+K6y
k/Q/oRGGY4+eqngsiBgJvcxKZW5dyYyHcUDa+XjLqLw8ZpdSnDLu0p/Z0K9nBTkFQdPlkY+Zt9l1
wAunyTN4JNpMKMmWKeamF4nl6RXi5PQ5XMg8zdnsmV60gltqbnW0exYUGTdw3frVjvXZq91bYY9m
s3VL9p3wXpsKaC05bCqzKQ0LNRHLtLTM8dEIQ6bpDhxYjGdEp5bos5sQI4dSLofSLMfmowhhoVGo
RUnbFABxCHD+aerpa+NKoKUZLhpx2YDToqB4Hk+txzUBj6BgboxpwrACfBNXgG/kLKoAO2LZy7m+
bh+noCCioElIhZWy8+Zimm68nHQkNhJLqWcYJYaDYFyF9IZEyhIiuK7LsYWvOIuAMEnbDMcWw5mb
RBIzk4p5e+i9rterlC3vtndty8xcmn2D746NZWNGP7Gk/XhAWfPa/IU73Llzim9w31hdDSvueXGs
682JdfXNFWlpFtGizbpreeWGQk/pKNfLvtq6qZUul1ltUabWTsK8Hh/5DA1xe4AN9MkVas7KuTlG
JSnGa1RKzmZL9DNiXUp3CtKCbSmCRqLSKlEGSdTnkyibJKtSUJAwWUFSXHpCagUNlWO6EBdvxbB4
K5JpUEnnwL1/jRoERSKhvKIn+cpIOSrfHul8EX3v7/F7vTROjqW8fCQ6Ju+7cKR8OcuAhnzXjXq8
r7t7AN4U7hIs5il1Be1mpVJr6P8datwDJ4Sf3xNmZs53Z2fYRCL1e7FFm4F13gxtslHFJyk2KBjE
mUROX8EpofD96azz3+NEfCGnRAPe7/gOKIa6n8WN2nnZOyKs0kbj3qjf8MNRlYDRloqzMOwExlJc
cToLcYQXCGkp7Ap0CiHuNuDG3ymSCFsSv5VFvyL3FSU9Bd7ymNfgixF9xEsgvZedMTD3ycW9Lw5I
VltzY+0TwYGuYP3bJ9B/Dt3UtN6dlz15LFOBaTwOI2g3pjEPtssTMtkcvoQt46vYWp7P4co4mWvg
WjmOt+KRrJVBTDbIYkaDUmYSqGbWwA1IABxaw0CGQwKCDCAYki5KpWqQDDrABsCC7YJOgAyTwCxg
1jAsk0x/WPILBVbREDYlIaKieC+h4be85K0NIDoZfWXDdofLnwv7X4WzIJaEi79iQ5e2MOvxapoB
wEsNATX46iAQMHFjv135KoYm6tgPH87JW6hTxqQweTAX5TAZbCaXLrhVxXAsF4BBbgacybZwM1TL
0Dy2XegQ25VLVOvhdWglu1rYKK5SblClqsn2FVae44EoiUiMv6ZS4ggw/oYKE0DH23kPzwArRbhM
KkA7tJLWr12hZQBPPErq9xBLRV0fArAa6ujQN7L8jZoon4sogsXeZ135OgubEzd0x19pJWASJfAl
4fefDJ8K/+mJ8LsvHoeJ98HUI4RUTOgSIdeDTBspRJ/GYX+G8FoBtskTWL6YD/D1fCvfyfMio+CS
mESuCtYyM8EMuJ4RkYLsmrOyDFsLqlgEGMRySI0W4UAUMQxLeZ0W4/Ukym0ObBd1ImTYBLaSXcCu
YTn2F4J0mvxoAjM6sSzkIVsayenDsRd0CVFeD61++UR44qtwBpzFhi4o4Bts1qUXmXLyu7IHIwWK
Nu4s9W69YLe8rEvTpe9M6Excn7TSxedpXVKaMc/stXjTvbnegoBlQnogN1Aw3TI9fXru9IIl2nap
3bjEPM/SkdKenpjRbYGWvFxLqvqJVB4AwxO85HV4kdfrabTZMzwZKCMjp9Fpqrc5RYbR1YuImg28
8kHPEPm1E6mgh3YNeryDnlA52RIgvqeT5lFxzYxoc1roSkv3FcfeAhTAy28BvIq2MBe+Fx8cvAiv
xsfF1eHa8Cv4qIXPwBJ8PBNe2fzg1D+Fv4GaD1r+fbxU8mjLjgfvuXPaAzUS2jnyRjIRHj8QDtD7
A3BgRlbW+c9OQVSY/HR21eO/fvDJMcX0d6v2//EYi4/nYCo88mMHkvFx6MqDaWDuu3ywU+lxmj3N
dXz34Jcq3IpDwgpRFO9QrlEVq+6hx2mNqDmiXaIbhY9e6V/0bv37hjLDm4Y3E0b9Pz3e/vn4+fj5
+Pn4+fjfegDyFiH6Xxwk905+fm7FBTsBgBld0BCYMbmxLthcWVN91cymqtr6afoxk2bdmmlKMHrS
fS3f8+9F/4s+LGinNUvoczYtEsE1JDXx/QHxwUaDAtAAAmAGmAwaQR0IYi+8EtSAanAVmAmaQBWo
BfVgGtCDMdgjnAVuBZnABBIwpT0gHfhAlIAQGDAPyH/l8eTnws0LVra3LW+LXgFwF+B+8oqFK0/P
grORKzpgfBgcLugE+OfKGTBECmcGt3BmaMbfD/3TZR2w0rIbrPrRcis4zq4Gx76vcLtGlPdAHymK
M+Cqn1LY18Ai9hI4yLrBYvy9lH0RdOA9Bkibk8BBVASeGlGeVRwDB0k/+x7ooPfhwnTQ+5czWWA8
vraXHQDj+G2gmRTS/v+1YJF6MIoLP/IhcoWWG/f2PnVorq7878AWFcTHrg/kkO9+zf1C5N5wi+oO
gYwUqazjz38Dgrh4hw0KZW5kc3RyZWFtDQplbmRvYmoNCjQwIDAgb2JqDQo8PA0KL0ZpbHRlciAv
RmxhdGVEZWNvZGUNCi9MZW5ndGggNjQ1NA0KL0xlbmd0aDEgMTQwOTINCj4+DQpzdHJlYW0NCnic
7TtreFTHdWfmPvbeu7vat7TalXR3tbuS0EpavR8gvNfoARiMBAgsgWUkIUDgGGQeLnZNUJ0abIGD
v6Rp/ciDuP76SJOwrIwjXDvGwW6ctC5gO3br2CVNCXFsFBPHIS2guz1z9wpD4qZtvv7oD+7ZM3Pm
zOvMmTNnzmAZCADYYQw46O5anqgF46s/h8nKtXcMjmbLdSMAZNPau7aHvjb00C+R8TYA99760Q13
fOeVny4E4F8GEO/b8Km712fbuxcDuGpH1g0Ov7rh2xJA4+vIbBxBhmNLjgXAivUQHblj+85s+4Z2
HH/0U1vWDmbLkTEAx9k7BneO2v7I8gG2Z3KENg/esc6Uj43nH92ybXu23PgUqx/dum7004UnHsP2
D6M8z4hFolc4L5zi9/BruW+BEyDz48w7+k59WO/jHgc/zrmSDJBN5C5yH5gfuY1sMIgnySC5nfwB
XP0thiPwPLwF/wa/uMLLEJ44ST5SPyEe2GX0fg3+BU7DR3CJCMRFAiQC/933GHzTpN4gk9RiUArs
p1+B7xIdax+DNmhDad6j93L3c6x+D+yCeoTf4+Ps9AC5lf4BHCRfpW20l75Dv3Z1PZFgMa59K/nc
b/cluUQlCTKbdJJlZIiMkw9oHbkRfga/hGnUhIeo8Axaxxk4RyiRiJfcRB6kN9NLRCebxHHBxX94
zWgbyQJcya1kGxkhI3AB6eWGNv4E081ggwCoV+aNwwu4VzXExg3RNLeYu4f7UFC4NIBwCgKik35E
18Mh2A2fR+iDPlIJA/AZ+CN4BfV/nlyGWYYev4Qtbkc4za/l7+a+S9KwHlbCesxfg1XkYVgLD+L6
bib59O/BCxP0J/BV+GdyK3cjfJ67m3wHV+ggW1CeP8Feb8MEHOBP/T57cP37v/00rWfB7NY5s1ua
mxob6utqa6oTVZUV8fJZZaUlsWikOBxSiwoLgoF8f16uz+txu5yOHLvNqsiSRRR4jhKoICl/W+/h
fEs8GA6H+yrNcuDacoqLOT8Mp8B9TaPgb3Qq+I1y4W+Ui66Ul6TAm+qMtLWzgQ9D59kUeFLEmwI2
C/HcjDOZnTqGN0U6Nqby24YHBrBHe8QZSnWeT5iiGGMftiptkbZ1SmUFHFasSFqRwrajh0nnDcQg
aGfH7MMUJHtlRcodT9FYB8NNKW3fABKRdhwJazwf10xmju2/ugqw2wzlyVIkJbalLMa8oY0pbTAF
+0KHK46N7590wtBA3DYcGR68FTU3iDIeBi7WMdLD9NjBcGAklOJxcCMJIifUMRIajzB1dIwMYBpp
x16fyEe23Na7N3wsmHJj3pFyxVPzscX8e84EufEO/8YQK46P7w2lDi7tvbo2zNK+vj4/CjzeEcEB
cbCOTfNwKf5EZUV2TaYChgc2sTk3DTI5OzaFxvetM2Tdb8hgNO0YwY0Z/O9ajY93DEc6hgeH52VH
b0tpPUYGPat6jQWi6tr7TJbZAGt4o2agvS+cVfaiZb1tTLDIYHswu+1XOAMmBxkdM5UhJsFCHCAV
WhtKwbLeCDZtZsm6Zhhf22wYTxi9ZcWi7o97pYSYMxIa/xWkyEBk6ty1nEGTI8acvwJGdkY6B8bH
OyOhzvGB8cHJzNhQJOSMjB9etGh8tGMAZ+3uxV6TmWf2BVOd+/tSzoERMht1zyygc1lvMhh29c0U
u2eKgCaFhmU1loNawN9CM0MtQ09vOISKWtHbF0Q99TK6B+lszgwJDbcZ99hUG9PRuuYr6mkzyXCY
Wee+SQ2GsJAaW9qbLYdgKJgGLRHH/RhgNcdmanwrWM3YTM2V7gMRnOUpYOGULyWVXPk5nLmejpHZ
KZL7O6rXZetTnrZeLkj7shQNcoxS4njSW1N5caTL4uO4CScjKWc8JfQeC7b2hZwu9ABs95ZHFi1d
1RvqGL9iBVmOuVJmB2jqkcGRcfMoMaP/ZO6i5TMKZxaLR3ofanxsaBMaDf4G9zP3Ex53pjovhIPh
cVfEHWpJ9GWt2nky8j2CjgvdmjNFWo1lEcOn4UwLU1xeM1b+3jNcuyT0Y/MOR8gDSw9r5IHlq3qP
YoQXeqCnN00JbRuY13c4inW9R0N4OxhceoXLSiFWgkXs9KSpZFQFj2oAY0YtbzCM8tpJAgZPmuER
WDtJszynwcOvEncWd1cieh8G1CMXb7+43G5wrvluZRzLh7Afo9F1IAHFXIMVGEHnZDIYg9NnoCdz
jMTTNnvjUSQq0rFZJuENZ4kJ2dmoTZKydCBgMMom7HbGiE10dhp5Wg0ZFbF0sMAkfLkm4XCZhGIz
iOJ0aalJFBVliQlFYcMUT9hsLA9P5OWznEvn5RkNuHQ+m/g7xJcuUk1C8RqEJ419j2ZeILnp5StM
YkmXSXR0mERbm0nMmpUlJqIlbIbcdH6+MUNuOjfXJFwuk5Cz+shP19RkiYmKCtYpP62GzZrCIpMw
BXVP4DDYxJ32Z8d1p5csMYmO+SYRKzEJcyb3jObVtNVqEvYZjtlGTXs8JmEKqhpqJKWEpGtVnFJM
u91GBU2XZfePTJTOYsLQCZQOczIjZTTt95uEw9n4HMkhArhARb0IE3Zjp/kJnJflaVkxWvIziuLT
rXNN4qabssTELX2sbSItWw3lSmk5YBByWmszCaMTI6qqTaK03CSKoyYRmOnl9RmENx2NmkRJaZaY
sHkaHTfmkDpIIq5B5EAlLiD4HnLgy0QljjTfrTKxQFOt/sbMz1T1vfcDavX75GfegPrBOaf6c0S4
oF2geGlo/gtWW+MFElCnzllV5/kD56l2bvTc8+c4dOUTF53eRsy12f/h9jb+9GxAPdsQULW3UODk
P5FTbybVN94MqGM/ID/AbODN0Tfp979Xrn7/ey3N3yfWl9tfpqm3CXZ/+m08PaOvMlK7/1XF0xjd
37N/+/4/3v/k/tT+F/dbtOOk6ahL3Yj4AuLziN9GfA7xWcS/XelSnzkaVI8g/fTRgPotxEnEoyhL
a9KlzkW8AbEdsQ1xXtKn3oioIZ1scKm1dV61rsGrNtR71XrMDzYYkoQbrLjTd86e3Xj6TqLdKXsa
D4ymRunpLUTbgqs9udlolbuZyb7+4fWp9Zy2QXY0fmUdSQ0bVXOGmVM4SEJfSH2BJj9H1hzYfYCG
Hjr2EA3drt1OYYQYv+6RgRFu9yCpXq2t3r16bDXf/EWXyvr/8os27P8S0SbIYdyZlNenHvK61G8i
fgPx616r+jfeHPVriPFylzpaTioqc9RKr139cqhNVb1FKl7Gasjbqj4ViKpfCaxTg4FadXfgQIAG
vMXqdz0LVJ83oXq8IbXarbm73Q+7+VH3mPukm3N7/aoLEbyk2zvgHfVy1TkERHxl4S9BkmQL2U0O
kefJCfIByRDFAWhcCUjCFnzIHcLn+An4ADKgKHKT6qAOjp6gJ7gMzXA848hSucoL5SrlSlSbvUXg
WzjaQqClWyCTOFrKvQgW9cxLeQjmy+cdlmvji1LDy+bd/9BDhak/ZXHHWGHfpIRtMIBJkc/2pSR2
cxkkxM1v23b8bdue4jpSYsfIYEqMtG9jhRxWyGGFnI6UgxUckXaS8naMpLzI3R6Pb9/B+u+IXxnp
Y2obw204rvGx8jZsuIMlcFW73/62bSNYvw2MEeJGQhjfYMRnEOf+XYP8Ph/ebpRddxYQAT2BBQo1
h0h5QKzGO64beYn+V955BRKY1FSHXWFXDBPca7g4JsAllgMSQDKX9M/SKvIg9qg6ClzmnCbL9ib6
Enech8nMac2GpS68SCeSeNEn+qf64+D8aKqmmsQJiXholf7ED14iD04L9BI2ukt/ljsrenGspJbX
whEO/VMz5byUcpQj4JedTeh83j2COS6AeRo2VyJel8AlJRM11XuFqvjeXS+SfkLChDs7fUj/V7pE
9P77X1l62f1+HO/ux4UfgAM6tbjwtCjauBxukkgfYJ1AVBKCBM5pywmRENfNUYdLdVGOczld7pZE
f3/dVEttf6Iu0Q/J6dpkXQJXEWaaCTfUNjY1NjYhxT9+uYzM1v+u44FZ1Q086SR1hOc8v8Rzs7T1
UgIjiKHMv/KvC1NQDLPhD7VWmy0nv9Cm5pdbE7aK/FXWrZat9UqAq5iEQmchLSzkHB5P3tE+B3HQ
5m81cp2oBmUlELe7JAzMFzhkB2qi1dGqttJAbVhmKrG6m+REfLq234VqmTLE7Z9K9k/XJoxlTLlb
aqr7iRfCxSWlJbSh3t3UGK2rzc1zRUpKIsWipbGRlXJzSSM+zrGJwfSKPi9j1tU28q/rb+iX7/uH
+StW9axZTUq+t/DzwWBg582Hvp278M/WdD/UdPNqfUmhGg2HexKly6O0sjjQFivqJJfe108tWriS
OJ97kVTv2LLLI+o/tIcnv55ojs+ac0x/MLpi5YLbCgp8XodSFRn7YlmooIjt2Q7cs2eFU2hxw1ox
M4gvZw0CKHdU4KiEdjEMhPYy26DM5s4zozC0Y5OtqB3JIakS5Q1rcTbxibihmDjqIt7vbmmBZHLa
1fKx6aDhsI18dnqPPkAfnZ7Nz+f/+tIt/CT7Z0PKLIjG+LXGmSnT8slxKojHBckph2RqgZQIeJ+G
CEcS/XW4A5CcSjJbN6zEFaYx/ctkiCF9izx46Ut4amjmIoAwhuuzgAKPaM3Pyydk+rxMSsgsugDm
c33CSrFXuYffYZFlWZEE3oM2ICuixY3KuYfsQE2E2HGYzPxIy0VCrK9WiCIrhOPwvKAiJHYjaz6s
4jibw6bakrYu226b4LARPOOGLiAZb022MNtg5zLev9c5fezYMSOVjpF+6O+PMK1wYTyRnEh+TR4h
v9Z39+sV/eT0I48Ipy4mSLV+kt5A3td9uGOP4Y7txhXJsFwrFBqqqUYH8ABTC2mQOIsEnIZL4JhT
MG5K2YWbZNWsxGGtxoyjgtcyrDgvoP4M6foNE05OuU0BTWXiHu2ePkCT0y/o+7mf8Ef0n+pnppki
sxKI+5C0wX8cBSXzTa01x9kk7MSEskRQmAr5AJ/gk7zGD/CjvIXnLVaZIxZJVqycQL2wLseRo+V0
53ACSvktVJ/gtgzbnRem4v2YuPLQcFqTrUwod14LutTDIm3r6T2iaDmGkzo2wSYyc4Ut1M58lYaJ
wBLzRqqpDmqL8CoUQOG6aJdAWbJVOUQPCQcVcRl3K7/GOsBt4TcpW6yj3G7+HmW31WpVZGtQybdW
WKu5uXyLMteqcV18l7xQsaN++tmG3YlPaReJEKYnNGlxn75f/0VG/4V+EO/nm8hCcoj74fRn6K7L
MeHUdJieZlpbmPkJf044B3Vw4igGtbdqy9gSnmSJS/EpcSHhcwV8gbgv0SAmnXPcLf5GdXaorrwu
3ljbIXY5F7kX+jvVm0Jt5W3xztpVttXO1bk95T3Vn/Ksr/xD1/b49upoATPTKqaIkKw0hQQSEhJF
VM4jeWU1OTwEioqK6wN0VCCCINWDUlSU46thunPKBU01NQ08X+Z7OC+VR/OYYu3Opjw0D3RxpqfD
44a2whIX7smd/f011WjNaNFCcbTUVZfL1xmOOuvV8NdQD+Fa/orjE00fhz+fF+j6v9GntxSPkpzd
oY2h0sbeuYu/segbf0qGiHw/sYyEl3/w6Zol8Ujd0u2L9nU9/mf6nwfn1ZChNetzHK65tc2dTm80
MPcfHz9FuMYq/evzh3K8zmRpS1vQFSpofu7xf9E/NN+b/Fnj7NdoRSJpwDMrOWRVpsJqi5euHmNN
ZEmTd8u033DeZ6bPsLMwXZu9kxmQSX0BfxbxCCnQz1xaxMZFxykFmf2TMs0tcWjQIIscESQowt0U
JzM/1gqQsAIvBsErxiEqtkKduBjaROXh7Ll82rhjc0RDt/397H5Fc29FvZqGzmmyp8lqeFVPk4R5
GnMwTXoDPpethzjuND3J/1B+XeFl6pBB6ZI15QAd4w/IYwqrOi2fVOyyJFoD1McHZJ9STkv4Ektc
ilrLbLNpPT9HrlO66Dz+Znme0ks3Shusd5O7hAP0Pv6v5SeVQjxXJ7U4rkQuZ8tRrNTmQfElWeIt
HlEQJWIRoiQu1JM5Qge5SZDY8WB+Dd2amaGB3LkV+vvwkHAcOjmPB39SUN+rr//gXX29vpf88SsX
ybapf2Jujnv08gbh1OV87qcM2X1Qm/kxfzP/GfQ0lXCv5qXlnvJVwqr8TcKm/O3S1uId5XLJZOaN
IzZnE2ktYJbcZLM3FRR4ytRoIro7eiDKR6OhZBlfKSlJj1IIlYGKLQlHguQ68e5yxNQYjcUsgdzR
KvQ5aNvM90zX1rJ7xbB1ZhRxdIpo5Q2iacFo5HkGHSlGC0eDjzahxTMDj7jwbg/xPryJftG3uaGq
bsXyqoHSaEt1oq/7Cy8N37aGSI88+OANf9FVVP/uXaSYyPqTJPaebPc4b2zsmlP+QFG1P8//8iO7
Hqusiipi//zKCHE4Zr3wd9M8aqIeNfE5fg/aXgw2aJGYvd5+I+3ib7Qvj26j9/ikQDkqIdZqtULx
DSJ/0E/8pnNkuZaPy/X7XRrI+flqQLmz1FFKYtYAN1piXAQYMprHG/fLuAqMRQshcDkhjKkvnGuG
JywSq3MZCvBkzzV9Sf+O/g3SSgoIJfw0EZqrKnfOn3tXTXxhXiw+/4aWuwu5weH128QiUk3yiYcs
0N/Tpz+9ZKOqBoO5ngqXftpV6HC46I+2bL9nI9v1e/GQ/dyIUy0wR/OKGroicZ4gUIFI/FeENRAw
Xno5ck4TIbJULWtyt8yZu/XRFJ5gjB7j2fCRhY3kjP4EuU3RP0u28msP4rMcjXgPJmeMOUqfpoRI
14wp8NWCJnQLM2PiiNnRsiNht+wIlih/H8RhSEuIIbHUF/KV4sFoD4ajYBP8RXy+4JfiARgM51kD
tmBewD84ZkvZTto4W9bp2ptstsoKZ2WiUqscqOSzk/V/NF3rnHK1GOtIokNg3qg/7LoSK7qupcO+
bEQ5E1f6XMKLosORbClbUqUftCDVHF9WysRe+ciaDV+ctW7i1iX3xhMJWrN8azQajoQun6E1y7Yh
WRa8fIZfe+/CZUODt62rrW38ws7pWHad/BO4zlxo0aLU6/HWKx3KqE9w2qV2D58jELtEArDFP+An
TmvAvjkva1IXpphLS2bj4fAnyuzjn9APWh3u9pZ4b60h4Z+v/frTtLJ9b6gkHIqY0vzzP4Jh/+/w
z6L9WyECMc3n1mS+SOMUWxDujCVjxB8UR6M4JzPlmbAwa7pGSq7MLn4caaMp88/qp/T39Sn9BKlB
y/RioPVouFBdUptYHCqKFgcLeurKbwmoIVqDrV7AF7iP+Mlc/QX93eH7y8rDhbNKH9iwYXdJaTQa
jd+d1RW3k98APlh7xCZjDMlnA2UMjNvdgiLIkhGUuYygLM+Rp+ZRmyUgb841dJYNFvH+iRuPiexN
cBRsM84fXf9RyMn8KI2nGc9nH4lco9GmrAlwOwu9i6ua7m5hGvWviJSsq3SVuzi/xRLKnXbya7+a
2+bNC1PKbNiXeY+7SXgSgtCr+azsBEuSnU8qFsHv9yZB9rMbSGMRsNVamCzsKqSiYg9YHKIqhjBW
Bc7J4TXEYTjOAvKEsYI69n5LJLFch0/GfgHdpCvSUGcIGXZdUX6dTxRp/RvH9+wht5Gl+iHqyJnf
XrDaXdQylpt6mdo/Ijfqz3+kb53TG4nM8iu/drhQ3l34vnsU3we56BdiVrFQ3GXhPCH0fNQnyOgd
XO2C4p2xRgUVm2fYBCrX8On4HmF+LRxuyLpv11XyYMD7qP7E6kc2/uXfkgHZ5Wxrja2Lk9vuXdz1
2uv0h9Ov3bK5JBKNqlwBe5Vfxp19C+WwknxtlSRZBF4Q8RKmBC9JDDUlSbaCVQELPh8EUeBFIisc
9xQve3leJmCxPCUSrygSKlglHgjHS4psEQXJKlBeVKrZq5MlGEmcnMAcjejkEcwVBbI+isUOdodd
s1NR5NmT2dB7gkW8biNybmXBRGtei/nq2lvlNzLJ+aL0CakZcmDQ6GWhBtqXl4UaaG5HqOaNGeGH
VooERk5SPs2VMI6QVkqfosOSLAqyNVfIt8aEcuuQcLvViAEAAxqMkNmNb1z5hH9LX//G2/pm8iV9
E3ns1dfI5/WNpE1/jtbQWv04mTv9Zva/CUR+Jyw04G6EZ2aALCePGXD8aqAVV+COq4GTroIXuCkG
6Nt+C4RSE75kwgkDzovD4l+KFxlYliF8zfJzBtKj1+E6XIfrcB2uw3W4DtfhOlyH63AdrsN1uBaM
dz41/xqQ/fsr+2PBAKKIRL6Dq25fsfiWrsbeBe7VhYGmWd5o97Kls//P/0b+/+nHQ7eR8kw/5/2Z
DKaEpVjmMc0HB2qsGtphBSyGW6ALGqEXFoAbVkMhBKAJZqFOozjKMlgKWbURrKUIACL7c5SewZEt
dwyy8cnDIPyPJZOuLZ6H85lrGGSmGbmCtBf+dziWuTyD/JfhLoaCH45/Ag4h7phB+i4c/69QuCdz
6TeR/wt47L9CS+yTUXDBQv4s+++JWZRaoOh/gvz3ofYaPAb1VyPdBPdehXssX4U9ggp7+PNYbyK3
E/YYuBx8WLdrBvk3MtPZ8/M7PrYvXOTNw6lDz6xxtP4KgtmN/OarPzL+f7Nnf33HOxdv13vtIO3B
trJhJ/j9J5MpD3sNCmVuZHN0cmVhbQ0KZW5kb2JqDQo0MSAwIG9iag0KPDwNCi9CYXNlRW5jb2Rp
bmcgL1dpbkFuc2lFbmNvZGluZw0KL0RpZmZlcmVuY2VzIFsgMSAvRCAvZSAvYSAvciAvc3BhY2Ug
L1cgL2kgL24KL2NvbW1hIC9QIC9sIC9zIC9wIC9vIC92IC9kIC90IC9oCi9mIC93IC9nIC9jIC95
IC91IC9tIC9wZXJpb2RdDQovVHlwZSAvRW5jb2RpbmcNCj4+DQplbmRvYmoNCjQyIDAgb2JqDQo8
PA0KL0Jhc2VFbmNvZGluZyAvV2luQW5zaUVuY29kaW5nDQovRGlmZmVyZW5jZXMgWyAxIC9zcGFj
ZV0NCi9UeXBlIC9FbmNvZGluZw0KPj4NCmVuZG9iag0KNDMgMCBvYmoNCjw8DQovRmlsdGVyIC9G
bGF0ZURlY29kZQ0KL0xlbmd0aCAxNTkNCj4+DQpzdHJlYW0NCnicXU8xDoMwDNzzCv8gQBkRC10Y
WlVtPxAcB2XAiUIY+vuSQDp0OEvnu5PPchivI9sI8hEcviiCsawDrW4LSDDRbFnUDWiL8WR54qK8
kMNN+ffHE+wGMge/q4Xks73kTX1k0GlavUIKimcSXVX1nTG9INZ/0hmYTHHWfUZTqTb7i5KiqUM5
CbiFQBxz0VwkFbBMv1+88ykFO8QX+t9THg0KZW5kc3RyZWFtDQplbmRvYmoNCjQ0IDAgb2JqDQo8
PA0KL0Jhc2VFbmNvZGluZyAvV2luQW5zaUVuY29kaW5nDQovRGlmZmVyZW5jZXMgWyAxIC9hZmlp
MDg5NDFdDQovVHlwZSAvRW5jb2RpbmcNCj4+DQplbmRvYmoNCjQ1IDAgb2JqDQo8PA0KL0Jhc2VF
bmNvZGluZyAvV2luQW5zaUVuY29kaW5nDQovRGlmZmVyZW5jZXMgWyAxIC9zcGFjZSAvVSAvSyAv
biAvYSAvdCAvaSAvbwovbCAvaCAvcyAvYiAvZSAvZCAveSAvdSAvciAvYwovZiAvbSAvcCAvcGVy
aW9kIC9XIC9nIC93IC9jb3B5cmlnaHQgL0MgL3R3bwovemVybyAvb25lIC9MIC9BIC9SIC92XQ0K
L1R5cGUgL0VuY29kaW5nDQo+Pg0KZW5kb2JqDQo0NiAwIG9iag0KPDwNCi9CYXNlRW5jb2Rpbmcg
L1dpbkFuc2lFbmNvZGluZw0KL0RpZmZlcmVuY2VzIFsgMSAvc2l4IC9jb21tYSAvc3BhY2UgL00g
L2EgL3IgL2kgL3QKL2wgL1MgL3UgL2UgL3NsYXNoIC94IC9jb2xvbiAvc2V2ZW4gL1QgL0YKL29u
ZSAvQSAvbSAvbyAvbiAvV10NCi9UeXBlIC9FbmNvZGluZw0KPj4NCmVuZG9iag0KNDcgMCBvYmoN
Cjw8DQovTGVuZ3RoIDEzNzYNCj4+DQpzdHJlYW0NCjw/eHBhY2tldCBiZWdpbj0n77u/JyBpZD0n
VzVNME1wQ2VoaUh6cmVTek5UY3prYzlkJz8+Cjw/YWRvYmUteGFwLWZpbHRlcnMgZXNjPSJDUkxG
Ij8+Cjx4OnhtcG1ldGEgeG1sbnM6eD0nYWRvYmU6bnM6bWV0YS8nIHg6eG1wdGs9J1hNUCB0b29s
a2l0IDIuOS4xLTEzLCBmcmFtZXdvcmsgMS42Jz4KPHJkZjpSREYgeG1sbnM6cmRmPSdodHRwOi8v
d3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjJyB4bWxuczppWD0naHR0cDovL25z
LmFkb2JlLmNvbS9pWC8xLjAvJz4KPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9JzY5MzQ0NzJh
LWI5ZTAtMTFlMC0wMDAwLWFlY2UyZjkyOTNjNCcgeG1sbnM6cGRmPSdodHRwOi8vbnMuYWRvYmUu
Y29tL3BkZi8xLjMvJyBwZGY6UHJvZHVjZXI9J0FGUEwgR2hvc3RzY3JpcHQgOC41NCcvPgo8cmRm
OkRlc2NyaXB0aW9uIHJkZjphYm91dD0nNjkzNDQ3MmEtYjllMC0xMWUwLTAwMDAtYWVjZTJmOTI5
M2M0JyB4bWxuczp4YXA9J2h0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8nIHhhcDpNb2RpZnlE
YXRlPScyMDExLTA3LTI2JyB4YXA6Q3JlYXRlRGF0ZT0nMjAxMS0wNy0yNic+PHhhcDpDcmVhdG9y
VG9vbD5BRlBMIEdob3N0c2NyaXB0IDguNTQgUERGIFdyaXRlcjwveGFwOkNyZWF0b3JUb29sPjwv
cmRmOkRlc2NyaXB0aW9uPgo8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0nNjkzNDQ3MmEtYjll
MC0xMWUwLTAwMDAtYWVjZTJmOTI5M2M0JyB4bWxuczp4YXBNTT0naHR0cDovL25zLmFkb2JlLmNv
bS94YXAvMS4wL21tLycgeGFwTU06RG9jdW1lbnRJRD0nNjkzNDQ3MmEtYjllMC0xMWUwLTAwMDAt
YWVjZTJmOTI5M2M0Jy8+CjxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSc2OTM0NDcyYS1iOWUw
LTExZTAtMDAwMC1hZWNlMmY5MjkzYzQnIHhtbG5zOmRjPSdodHRwOi8vcHVybC5vcmcvZGMvZWxl
bWVudHMvMS4xLycgZGM6Zm9ybWF0PSdhcHBsaWNhdGlvbi9wZGYnPjxkYzp0aXRsZT48cmRmOkFs
dD48cmRmOmxpIHhtbDpsYW5nPSd4LWRlZmF1bHQnPk1pY3Jvc29mdCBXb3JkIC0gR292ZXJubWVu
dCBBY2NyZWRpdGVkIExvdHRlcnk8L3JkZjpsaT48L3JkZjpBbHQ+PC9kYzp0aXRsZT48ZGM6Y3Jl
YXRvcj48cmRmOlNlcT48cmRmOmxpPnJhbXppPC9yZGY6bGk+PC9yZGY6U2VxPjwvZGM6Y3JlYXRv
cj48L3JkZjpEZXNjcmlwdGlvbj4KPC9yZGY6UkRGPgo8L3g6eG1wbWV0YT4KICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIAo8P3hwYWNrZXQgZW5kPSd3Jz8+DQplbmRzdHJlYW0NCmVuZG9i
ag0KeHJlZg0KMCA0OA0KMDAwMDAwMDAwMCA2NTUzNSBmDQowMDAwMDAwMDEwIDAwMDAwIG4NCjAw
MDAwMDAwODMgMDAwMDAgbg0KMDAwMDAwMDQ1MyAwMDAwMCBuDQowMDAwMDAwNTM2IDAwMDAwIG4N
CjAwMDAwMDA3MTggMDAwMDAgbg0KMDAwMDAwMDk3MiAwMDAwMCBuDQowMDAwMDExOTM3IDAwMDAw
IG4NCjAwMDAwMTE5NjEgMDAwMDAgbg0KMDAwMDAxMjAxMiAwMDAwMCBuDQowMDAwMDEyNTczIDAw
MDAwIG4NCjAwMDAwMTc0MDIgMDAwMDAgbg0KMDAwMDAxNzk2NCAwMDAwMCBuDQowMDAwMDc5MDQw
IDAwMDAwIG4NCjAwMDAwNzkxMTkgMDAwMDAgbg0KMDAwMDA3OTE5OSAwMDAwMCBuDQowMDAwMDc5
NDczIDAwMDAwIG4NCjAwMDAwNzk3MDAgMDAwMDAgbg0KMDAwMDA3OTg5NiAwMDAwMCBuDQowMDAw
MDgwMTI1IDAwMDAwIG4NCjAwMDAwODA0MzAgMDAwMDAgbg0KMDAwMDA4MDY1NiAwMDAwMCBuDQow
MDAwMDgwNzM0IDAwMDAwIG4NCjAwMDAwODA5MDkgMDAwMDAgbg0KMDAwMDA4MTEzMSAwMDAwMCBu
DQowMDAwMDgxMTgxIDAwMDAwIG4NCjAwMDAwODEyMTggMDAwMDAgbg0KMDAwMDA4MTI3MCAwMDAw
MCBuDQowMDAwMDgxMzg3IDAwMDAwIG4NCjAwMDAwODE1NzIgMDAwMDAgbg0KMDAwMDA4NjAxOCAw
MDAwMCBuDQowMDAwMDg2MDQyIDAwMDAwIG4NCjAwMDAwODYxMjUgMDAwMDAgbg0KMDAwMDA4NjM4
OSAwMDAwMCBuDQowMDAwMDg2NjE2IDAwMDAwIG4NCjAwMDAwODY2NTMgMDAwMDAgbg0KMDAwMDA4
Njc1NyAwMDAwMCBuDQowMDAwMDkyNjM0IDAwMDAwIG4NCjAwMDAwOTQ5OTMgMDAwMDAgbg0KMDAw
MDEwMTQ1OCAwMDAwMCBuDQowMDAwMTA5OTMwIDAwMDAwIG4NCjAwMDAxMTY0ODMgMDAwMDAgbg0K
MDAwMDExNjY2OCAwMDAwMCBuDQowMDAwMTE2NzY5IDAwMDAwIG4NCjAwMDAxMTcwMTAgMDAwMDAg
bg0KMDAwMDExNzExNSAwMDAwMCBuDQowMDAwMTE3MzM1IDAwMDAwIG4NCjAwMDAxMTc1MjUgMDAw
MDAgbg0KdHJhaWxlcg0KPDwNCi9JRCBbIDxDQjJGMDI2QTVCQjFBQzFDMTVDODhFRjVCNEZCMDUx
Nj4gPENCMkYwMjZBNUJCMUFDMUMxNUM4OEVGNUI0RkIwNTE2Pl0NCi9JbmZvIDIgMCBSDQovUm9v
dCAxIDAgUg0KL1NpemUgNDgNCj4+DQpzdGFydHhyZWYNCjExODk2Mg0KJSVFT0Y=
--0-522882420-1314438102=:19139--

From d3e3e3@gmail.com  Mon Aug 29 08:17:20 2011
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A82821F8C2B for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.2
X-Spam-Level: 
X-Spam-Status: No, score=-104.2 tagged_above=-999 required=5 tests=[AWL=-0.601, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3uA4eBuTxrRM for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:17:19 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBEA21F8C2A for <ietf@ietf.org>; Mon, 29 Aug 2011 08:17:19 -0700 (PDT)
Received: by vws12 with SMTP id 12so2476803vws.31 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:18:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=eiCO2Izo6O6mOHYGsIsSIXvF9blJ1NlN8SC0D45FY/4=; b=enXibI+sBwtej+wEiYEjUW/M5AIE8XXHUF/j01YZKcLAz4eq17Ugtl1NiZYXjOE41u l2jbX76FRCxOGs0sVf7fl66f7Cb3ViBw5N7sPBPmA94z9X/X1ZaJZ/SBd3tFg4e6eiOJ frBZjQ1HkyJXRnX2HyAAPIdUSMRyvWxJDk9GI=
Received: by 10.52.26.230 with SMTP id o6mr2857405vdg.430.1314631124125; Mon, 29 Aug 2011 08:18:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.155.42 with HTTP; Mon, 29 Aug 2011 08:18:24 -0700 (PDT)
In-Reply-To: <4E5BA9AD.7050908@gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 29 Aug 2011 11:18:24 -0400
Message-ID: <CAF4+nEE4_cXAGvKxn+JHQ6ADPo9Sy_t0eqSwzWo=sJUrmUdo-g@mail.gmail.com>
Subject: Re: voting system for future venues?
To: henk@uijterwaal.nl
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:17:20 -0000

On Mon, Aug 29, 2011 at 11:01 AM, Henk Uijterwaal
<henk.uijterwaal@gmail.com> wrote:

>>
>>...
>
> Discussions with the hotel starts only 2 years out, so fixing dates 3 yea=
rs
> out won't change a thing. =A0 There is also the clash list, which limits =
the
> weeks when we can have a meeting.
>
> If we want more flexibility in order to find better hotel deals, then we =
have
> to do something like: dates are fixed approximately 1.5 years out, and we=
 do
> not mind having meetings back-to-back with other organizations on the cla=
sh
> list. =A0That means that some folks will have to travel around the globe =
between
> Friday afternoon and Sunday morning in order to make it from one meeting =
to
> another.

IETF, more often that not, meets back-to-back with IEEE 802 Plenary meeting=
s.

> Henk

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

> -------------------------------------------------------------------------=
-----
> Henk Uijterwaal =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Email=
: henk(at)uijterwaal.nl
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0http://www.uijterwaal.nl
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0Phone: +31.6.55861746
> -------------------------------------------------------------------------=
-----

From iljitsch@muada.com  Mon Aug 29 08:19:06 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E23F621F8B89 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:19:06 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1gdKb69mTBa0 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:19:06 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id BD7CF21F8B76 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:18:58 -0700 (PDT)
Received: from dulcinea.it.uc3m.es ([163.117.139.50]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p7TFKEL1035161 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Aug 2011 17:20:14 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4E5BA9AD.7050908@gmail.com>
Date: Mon, 29 Aug 2011 17:19:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <68F70126-516B-48C9-A668-FC25EBE5839A@muada.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com>
To: henk@uijterwaal.nl
X-Mailer: Apple Mail (2.1244.3)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:19:07 -0000

On 29 Aug 2011, at 17:01 , Henk Uijterwaal wrote:

> If we want more flexibility in order to find better hotel deals, then =
we have
> to do something like: dates are fixed approximately 1.5 years out, and =
we do
> not mind having meetings back-to-back with other organizations on the =
clash
> list.  That means that some folks will have to travel around the globe =
between
> Friday afternoon and Sunday morning in order to make it from one =
meeting to
> another.

Is this so bad that $300/night room prices for hundreds of participants =
to avoid this issue is a good deal?

One potential solution could be to select two or three weeks that don't =
clash or only minimally clash and then start the negotiations with a few =
more options, fixing the date a year or so out.=

From aallen@rim.com  Mon Aug 29 08:30:42 2011
Return-Path: <aallen@rim.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C0721F8C49 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.171
X-Spam-Level: 
X-Spam-Status: No, score=-5.171 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jwc61W3DAvJQ for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:30:41 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 3528821F8C40 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:30:41 -0700 (PDT)
X-AuditID: 0a41282f-b7cceae000002964-ec-4e5bb0e0bae1
Received: from XHT101CNC.rim.net (xht101cnc.rim.net [10.65.12.214]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mhs060cnc.rim.net (SBG) with SMTP id A2.2A.10596.0E0BB5E4; Mon, 29 Aug 2011 15:31:45 +0000 (GMT)
Received: from XHT140CNC.rim.net (10.65.12.32) by XHT101CNC.rim.net (10.65.12.214) with Microsoft SMTP Server (TLS) id 8.3.159.2; Mon, 29 Aug 2011 11:32:05 -0400
Received: from XCT104ADS.rim.net (10.67.111.45) by XHT140CNC.rim.net (10.65.12.32) with Microsoft SMTP Server (TLS) id 14.1.289.8; Mon, 29 Aug 2011 11:32:04 -0400
Received: from XMB105ADS.rim.net ([fe80::c47b:e609:558:1b44]) by XCT104ADS.rim.net ([fe80::90f9:3b89:1d94:aa9b%22]) with mapi id 14.01.0289.001; Mon, 29 Aug 2011 10:32:03 -0500
From: Andrew Allen <aallen@rim.com>
To: "iljitsch@muada.com" <iljitsch@muada.com>, "henk@uijterwaal.nl" <henk@uijterwaal.nl>
Subject: Re: voting system for future venues?
Thread-Topic: voting system for future venues?
Thread-Index: AQHMYqKkeZhlzPUvxE+jvPosBWvqIpUtaueAgAO0VICAAA9tAIADEzmAgAAC/wCAAAKagIAABTsA//+vn0Y=
Date: Mon, 29 Aug 2011 15:32:03 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net>
In-Reply-To: <68F70126-516B-48C9-A668-FC25EBE5839A@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.110.251]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLKsWRmVeSWpSXmKPExsXC5chzTffhhmg/gzOH2C0+v25mtni2cT6L xaz2BmYHZo8lS34yeTx+eYzR48TdQ4wBzFENjDaJeXn5JYklqQopqcXJtko+qemJOQoBRZll icmVCi6Zxck5iZm5qUVKCpkptkomSgoFOYnJqbmpeSW2SokFBal5KUp2XAoYwAaoLDNPITUv OT8lMy/dVskz2F/XwsLUUtdQyU4XCST8486YdGAda8FB3orG/+vYGxj/cHUxcnJICJhIfH/5 jB3CFpO4cG89WxcjF4eQQC+TxJ/3k5ghnKWMEksunYRyljFKHP03AcrZwiix6d8lZpB+NgFl ieW/ZzB2MXJwiAhESXxZmQQSZgYKP900hwnEFhbQlVi7YSsLiC0ioCfR0DOBDcJOkti2aivY GSwCqhJty7eB1fAKuEnc3/McrJdTwFai/WkDWJwR6NTvp9YwQcwXl7j1ZD4TxAsCEkv2nGeG sEUlXj7+xwphK0o8adzMAlGvJ3Fj6hQ2CFtbYtnC18wQuwQlTs58AlYjJCAtsePkGsYJjBKz kKyYhaR9FpL2WUjaFzCyrGIUzM0oNjAzSM5L1ivKzNXLSy3ZxAhONxr6Oxj79modYhTgYFTi 4WVfHO0nxJpYVlyZe4hRgoNZSYQ3bRJQiDclsbIqtSg/vqg0J7X4EKMFMFQmMktxJ+cDU2Fe SbyxgQEKR0mcN1jawE9IIB2YxLJTUwtSi2BamTg4pRoYj0ziXb64K/1m2/vujasdZn2+vo1x caykcNKPyZtulYstlywvCPyyzFNh5buwYpVnnct/m6cvPDBDry6s2iTcbMvXLV7My5pWWZwr n/Pw8cecyMclySbPVlRyuwdySGZfym6T6JXe1OUmWvf5cXosg99m7rfcDhWWE4s+zvdOt3I+ wCLxv7BZiaU4I9FQi7moOBEA4XltPFADAAA=
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:30:42 -0000

There likely are no such dates as there are telecommunications standards mee=
tings of one kind or another virtually every week of the year (except Christ=
mas and (western) new year).

Many other standards organisations depend on IETF standards so it is importa=
nt to avoid clashes with those organisations so those stakeholders can parti=
cipate. It is desirable if the meetings are not back to back but that isn't=
 always possible but direct clashes should be avoided especiallly since IETF=
 only meets 3 times a year.

Andrew

----- Original Message -----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Monday, August 29, 2011 10:19 AM=0A=
To: henk@uijterwaal.nl <henk@uijterwaal.nl>
Cc: ietf@ietf.org <ietf@ietf.org>
Subject: Re: voting system for future venues?

On 29 Aug 2011, at 17:01 , Henk Uijterwaal wrote:

> If we want more flexibility in order to find better hotel deals, then we h=
ave
> to do something like: dates are fixed approximately 1.5 years out, and we=
 do
> not mind having meetings back-to-back with other organizations on the clas=
h
> list.  That means that some folks will have to travel around the globe bet=
ween
> Friday afternoon and Sunday morning in order to make it from one meeting t=
o
> another.

Is this so bad that $300/night room prices for hundreds of participants to a=
void this issue is a good deal?

One potential solution could be to select two or three weeks that don't clas=
h or only minimally clash and then start the negotiations with a few more op=
tions, fixing the date a year or so out.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From iljitsch@muada.com  Mon Aug 29 08:38:13 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03AD421F8C1E for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.483
X-Spam-Level: 
X-Spam-Status: No, score=-102.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSrJBVPQqh2g for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:38:12 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 4C19021F8B3A for <ietf@ietf.org>; Mon, 29 Aug 2011 08:38:12 -0700 (PDT)
Received: from dulcinea.it.uc3m.es ([163.117.139.50]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p7TFdQrZ035327 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 29 Aug 2011 17:39:27 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net>
Date: Mon, 29 Aug 2011 17:38:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com>
References: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net>
To: Andrew Allen <aallen@rim.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:38:13 -0000

On 29 Aug 2011, at 17:32 , Andrew Allen wrote:

> There likely are no such dates as there are telecommunications =
standards meetings of one kind or another virtually every week of the =
year (except Christmas and (western) new year).

Then go from "no clash" to "minimal clash". If it turns out that it's =
only possible to select one minimally clashing week in a target period =
then select that week. But randomness suggests that there will be times =
when there are multiple candidates that aren't too different.=

From scott.brim@gmail.com  Mon Aug 29 08:42:52 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C409E21F8C1F for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.56
X-Spam-Level: 
X-Spam-Status: No, score=-103.56 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5XPxnlE7fyic for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:42:52 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 46AC321F8C1D for <ietf@ietf.org>; Mon, 29 Aug 2011 08:42:52 -0700 (PDT)
Received: by iakc1 with SMTP id c1so766916iak.31 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qqr7cc9vd26V0lOWCRRNgIv0+WvTyUU0snPs8bmYZaI=; b=XOMJCno1bha+SKmDSVLvX7Fv+jrquw+VH/v/AGlYk8vKa+jp50lXmaztujo0eVQdgR wvnT4GF89lJcsNXcoIyGvphdzuaGyklosMZMYqrxSYZnGPWgDc66IQBd5oRlMemYlnK5 XI4/2y+8FUjDZN/7Mg23gSckjF641VFFq2E7k=
Received: by 10.231.20.136 with SMTP id f8mr10818209ibb.32.1314632657072; Mon, 29 Aug 2011 08:44:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.36.12 with HTTP; Mon, 29 Aug 2011 08:43:56 -0700 (PDT)
In-Reply-To: <ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com>
References: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net> <ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 29 Aug 2011 11:43:56 -0400
Message-ID: <CAPv4CP-DWqk_iYYbOxPWaCesNFjswsNJcya_L62OHkK3ed1VRQ@mail.gmail.com>
Subject: Re: voting system for future venues?
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:42:52 -0000

Yawn

From agmalis@gmail.com  Mon Aug 29 08:44:34 2011
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E6821F8C67 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrav37HLJa0S for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:44:34 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 06F3221F8C1D for <ietf@ietf.org>; Mon, 29 Aug 2011 08:44:33 -0700 (PDT)
Received: by qwc23 with SMTP id 23so4036759qwc.31 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:45:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=Vy2NQFVxm2Hdkm/f05/R/x+qfz/LpTpSKd5fPM6e+lo=; b=Bt4YFSarcoX7gde1tAI2y4T0l3QDk+F2/TfCnKammjyoHJrPZ4N/qitwuwgNZfNdpY 4ntjNNAgXvxP5NLaw85iHyEqgwV/wWcJGki39xyD4kTtVMfriWvCiboNKtPaFfOgHOP7 f0gafgpMu9xNMaZVdfvMhvcQ3TDh28oRJHVxI=
Received: by 10.229.224.149 with SMTP id io21mr5862740qcb.81.1314632758538; Mon, 29 Aug 2011 08:45:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.221.199 with HTTP; Mon, 29 Aug 2011 08:45:38 -0700 (PDT)
In-Reply-To: <4E5A1761.8030600@uijterwaal.nl>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <1314226999.1973.211.camel@d430> <4E573BB6.5000700@gmail.com> <CAHBDyN4ML7PL65=kQXchvvgmtOEX_hK5LB8BPSxjvOL0G11vmg@mail.gmail.com> <4E5A1761.8030600@uijterwaal.nl>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 29 Aug 2011 11:45:38 -0400
Message-ID: <CAA=duU3jfcX9nhkZC_dYnYWc_mv2DLK11qdfXExYNmk8oy1MwQ@mail.gmail.com>
Subject: Re: Hyatt Taipei cancellation policy?
To: Henk Uijterwaal <henk@uijterwaal.nl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:44:34 -0000

I also like Minneapolis, for what it's worth.

Cheers,
Andy

On Sun, Aug 28, 2011 at 6:24 AM, Henk Uijterwaal <henk@uijterwaal.nl> wrote=
:
> On 26/08/2011 16:48, Mary Barnes wrote:
>
>> [MB] I've not seen a single person advocate a 0:3:0 schedule and it's on=
ly less
>> cheaper for all participants (not just US) because the hotel rates are e=
xtremely
>> reasonable (<$150 as I recall). =A0 =A0It is definitely less expensive f=
or the vast
>> majority of participants than NA cities like Quebec City and San Francis=
co that
>> =A0travel by air. =A0BUT, I think you are missing what we are saying ove=
rall - the
>> major reasons some of us prefer Minneapolis is because it meets what som=
e of us
>> have been saying over and over as far a key factors for meetings:
>> http://www.ietf.org/mail-archive/web/ietf/current/msg68656.html
>> http://www.ietf.org/mail-archive/web/ietf/current/msg68727.html
>
> I like Minneapolis as meeting location too, assuming that the visa troubl=
es we
> had there last time are solved, and I'd be happy to make it the default l=
ocation
> for US meetings.
>
> However, we have said that we want to meet all over the planet. =A0That m=
eans that
> we have to go elsewhere somewhere, even if there is a good and cheaper
> meeting location available elsewhere, but in the wrong region. =A0The sam=
e goes
> for the meeting weeks, if a good hotel option isn't available in a meetin=
g week
> but is available a week or so earlier/later, then under the present rules=
,
> it has to be discarded.
>
> Henk
>
>
> --
> -------------------------------------------------------------------------=
-----
> Henk Uijterwaal =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Email=
: henk(at)uijterwaal.nl
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0http://www.uijterwaal.nl
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0Phone: +31.6.55861746
> -------------------------------------------------------------------------=
-----
>
> There appears to have been a collective retreat from reality that day.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (John Gla=
nfield, on an engineering project)
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From rbarnes@bbn.com  Mon Aug 29 08:45:53 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39AC921F8C0B for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.543
X-Spam-Level: 
X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NfQfji7gmkaY for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:45:52 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 6A02421F8B6F for <ietf@ietf.org>; Mon, 29 Aug 2011 08:45:52 -0700 (PDT)
Received: from ros-dhcp192-1-51-76.bbn.com ([192.1.51.76]:56880) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Qy43K-000KWn-Be; Mon, 29 Aug 2011 11:47:10 -0400
Subject: Re: voting system for future venues?
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: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net>
Date: Mon, 29 Aug 2011 11:47:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DF60AD1-0337-4814-9A81-66CBBE903051@bbn.com>
References: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net>
To: Andrew Allen <aallen@rim.com>
X-Mailer: Apple Mail (2.1082)
Cc: "henk@uijterwaal.nl" <henk@uijterwaal.nl>, "iljitsch@muada.com" <iljitsch@muada.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:45:53 -0000

To add some data to this discussion, there's a table of Internet =
meetings and a chart of overlaps on the PCH website:
<https://prefix.pch.net/applications/internet-governance-meetings/>

The current maximum collision factor is 5 (meetings/day).

--Richard



On Aug 29, 2011, at 11:32 AM, Andrew Allen wrote:

>=20
> There likely are no such dates as there are telecommunications =
standards meetings of one kind or another virtually every week of the =
year (except Christmas and (western) new year).
>=20
> Many other standards organisations depend on IETF standards so it is =
important to avoid clashes with those organisations so those =
stakeholders can participate. It is desirable if the meetings are not =
back to back but that isn't always possible but direct clashes should be =
avoided especiallly since IETF only meets 3 times a year.
>=20
> Andrew
>=20
> ----- Original Message -----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Monday, August 29, 2011 10:19 AM
> To: henk@uijterwaal.nl <henk@uijterwaal.nl>
> Cc: ietf@ietf.org <ietf@ietf.org>
> Subject: Re: voting system for future venues?
>=20
> On 29 Aug 2011, at 17:01 , Henk Uijterwaal wrote:
>=20
>> If we want more flexibility in order to find better hotel deals, then =
we have
>> to do something like: dates are fixed approximately 1.5 years out, =
and we do
>> not mind having meetings back-to-back with other organizations on the =
clash
>> list.  That means that some folks will have to travel around the =
globe between
>> Friday afternoon and Sunday morning in order to make it from one =
meeting to
>> another.
>=20
> Is this so bad that $300/night room prices for hundreds of =
participants to avoid this issue is a good deal?
>=20
> One potential solution could be to select two or three weeks that =
don't clash or only minimally clash and then start the negotiations with =
a few more options, fixing the date a year or so out.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential =
information, privileged material (including material protected by the =
solicitor-client or other applicable privileges), or constitute =
non-public information. Any use of this information by anyone other than =
the intended recipient is prohibited. If you have received this =
transmission in error, please immediately reply to the sender and delete =
this information from your system. Use, dissemination, distribution, or =
reproduction of this transmission by unintended recipients is not =
authorized and may be unlawful.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From dhc@dcrocker.net  Mon Aug 29 08:48:34 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C385021F8C80 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:48:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.398
X-Spam-Level: 
X-Spam-Status: No, score=-6.398 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPiYKsf-S2Jv for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 08:48:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3402721F8C50 for <ietf@ietf.org>; Mon, 29 Aug 2011 08:48:34 -0700 (PDT)
Received: from [192.168.1.156] (adsl-68-122-69-114.dsl.pltn13.pacbell.net [68.122.69.114]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p7TFnrBT008636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 29 Aug 2011 08:49:58 -0700
Message-ID: <4E5BB521.3010800@dcrocker.net>
Date: Mon, 29 Aug 2011 08:49:53 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com>
In-Reply-To: <4E5BA9AD.7050908@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 29 Aug 2011 08:49:59 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 15:48:34 -0000

On 8/29/2011 8:01 AM, Henk Uijterwaal wrote:
> If we want more flexibility in order to find better hotel deals, then we have
> to do something like: dates are fixed approximately 1.5 years out, and we do
> not mind having meetings back-to-back with other organizations on the clash
> list.


As we have been told for many years and experienced directly, hotel schedules 
become crowded 2-3 years ahead of time.  That means we must fix our dates 
farther ahead than we have been doing.  1.5 years essentially guarantees our 
having very limited choice.

This is one of the reasons for the recent move to target having a contract 3 
years ahead of time.  However this year is transitional, so we are still 
suffering from having contract negotiations too close to the event.

As I understand it, the class list also is very much a factor in planning far ahead.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From moore@network-heretics.com  Mon Aug 29 09:02:03 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDF6B21F8BB8 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 09:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.606
X-Spam-Level: 
X-Spam-Status: No, score=-3.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBVLy3-cOIJ4 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 09:02:03 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 446BC21F8BBA for <ietf@ietf.org>; Mon, 29 Aug 2011 09:02:03 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2857620955; Mon, 29 Aug 2011 12:03:28 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 29 Aug 2011 12:03:28 -0400
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=XHKAFW+Lh2J6puiW7S2RATKtgPE=; b=At JqPp7BzpBvxCEE+YHPzdX8k3HXvzuwlJ9btihpmvhi8Gb9wCRlBj4SCjarJVkZJP G/b7A0T4I0zRYBTpo20UmeCfxxl8fS+a9qC+ntbv5xRO/9bwP1VRQ3bN8er4owDF CimAAuTmQReVlinaILp5Vn0+s1ZVwgLwe4lrU3fD8=
X-Sasl-enc: biB0qd4YxOmYRDIoCbdVkkrQvxPgc8N3fAB4PWAB5iZ4 1314633808
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id ED210A00509; Mon, 29 Aug 2011 12:03:27 -0400 (EDT)
Subject: Re: authenticated archives, was https
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E597E0C.7050708@santronics.com>
Date: Mon, 29 Aug 2011 12:03:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <154E7CF4-CAF4-4C1E-B0C4-70EDBFB82D9E@network-heretics.com>
References: <20110827143104.89801.qmail@joyce.lan> <5199131E-EE60-4506-A674-08533630AEF8@network-heretics.com> <4E597E0C.7050708@santronics.com>
To: Hector Santos <hsantos@santronics.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 16:02:04 -0000

On Aug 27, 2011, at 7:30 PM, Hector Santos wrote:

> Keith Moore wrote:
>> On Aug 27, 2011, at 10:31 AM, John Levine wrote:
>>> TLS for session privacy is nice, but I find negligible value in a
>>> little lock icon in my browser that means only that one of the =
several
>>> dozen cert issuers configured into my browser, most of whom I've =
never
>>> heard of, and many of whom aren't even the organization in the cert
>>> name, signed something.
>> +1.  IMO browser vendors have made TLS nearly useless for web =
browsing by including so many default CAs; some with dubious integrity, =
and a few with a demonstrated lack of integrity.
>=20
> Interesting viewpoint.  Are you advocating for a monopoly or oligopoly =
centralization?

no, replacing one flawed model for another won't help.

the root problem is that users are being expected to extend trust to =
whatever set of CAs the browser vendors find "convenient", and browser =
vendors can be influenced/coerced in these choices by various means.

but it's not as if users are in a better position to decide which CAs =
are trustworthy.



From ajs@anvilwalrusden.com  Mon Aug 29 09:32:34 2011
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B92821F8B9F for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 09:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.826
X-Spam-Level: 
X-Spam-Status: No, score=-1.826 tagged_above=-999 required=5 tests=[AWL=-0.716, BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pf5f0q7yHoB2 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 09:32:33 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 8B51F21F8B9D for <ietf@ietf.org>; Mon, 29 Aug 2011 09:32:33 -0700 (PDT)
Received: from shinkuro.com (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 1E5BD1ECB41C for <ietf@ietf.org>; Mon, 29 Aug 2011 16:33:58 +0000 (UTC)
Date: Mon, 29 Aug 2011 12:34:00 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: voting system for future venues?
Message-ID: <20110829163359.GI84494@shinkuro.com>
References: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net> <ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 16:32:34 -0000

On Mon, Aug 29, 2011 at 05:38:57PM +0200, Iljitsch van Beijnum wrote:

> Then go from "no clash" to "minimal clash".

I look forward to the mailing list discussions in which we debate the
relative importance of different clashing events.  It will provide a
welcome change in topic: we can move from "here is how I want to
optimise IETF meetings" to "here are the most important other meetings
to me."

As I understand it (and I think someone already said this upthread),
the point of the early date selection is that the IETF sets its dates
first, and then others have to/may schedule around it.  Given that we
all of us apparently cannot even agree to disagree about the
definition of "secondary" and "primary" airline hubs, what are the
chances we'll be able to pick meeting dates after others have picked
theirs?

The hard truth is that arranging a meeting for over a thousand picky,
cheap geeks from all over the world is a very hard problem.  Simple
answers like voting systems will not result in happy people anyway
(please look up "Kenneth Arrow" before you decide I'm wrong), and so
we have to fall back on trusting the people we have selected, via the
NomCom, to do this job.  For my part, I think they're all either
insane or saints: that is just a thankless task, for which one
inevitably gets coated in rotten fruit.  

People keep demanding more openness, but anyone who has ever negotated
a contract ought to know perfectly well that such negotiations don't
happen in the open; and that the details of failed negotiations end up
secret, too, because neither party wants to give away their positions.
The demands that the IAOC open that up are, in fact, a demand that
prices go _up_, since the other side of the negotiation would be in a
position to understand negotiating strategies.  Every unusual issue
for every IETF venue results in this sort of second-guessing of the
IAOC, and I think it's silly.  (But if you really think you can do
better, I understand there's an IAOC slot up for consideration by the
NomCom this year.)

Indeed, rather than asking how we can optimise the meeting location
for people who live at 1234 Pine Street, Springfield, USA, why don't
we ask why we are having three meetings a year?  I hear there's
something called the Internet.  Do we really need _everybody_ to get
together in one place so often?  Especially given that we have such a
globally dispersed population that we now have to trek all over the
globe for meetings?  Maybe we need to have more interim virtual
meetings, and fewer in-person meetings.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From scott.brim@gmail.com  Mon Aug 29 10:58:05 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AFDF21F8B46 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 10:58:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.562
X-Spam-Level: 
X-Spam-Status: No, score=-103.562 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVLuBXuiYPWh for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 10:58:04 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7F19B21F874B for <ietf@ietf.org>; Mon, 29 Aug 2011 10:58:04 -0700 (PDT)
Received: by ywe9 with SMTP id 9so5771111ywe.31 for <ietf@ietf.org>; Mon, 29 Aug 2011 10:59:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=UC7ztNwqJoYP88dL6YlMRyi8v8IVSJf5pZcwfD4ry/c=; b=o3iyx7SKnTEDA2ZhAhRAZiKQ/GDgZ/4n7R1zVhDGQ9onj4deuOcMuY77f/RoStsY4C yrlCHetkx56/I01BFF89FEkiN3l+4TCibgI2hStjAKw9fWYm6rPtAT0DcJSDlfAjQnay Bsb0pG3wz3PxEwPcC/ggqDdjIjtnBtX04UQQA=
Received: by 10.42.74.202 with SMTP id x10mr5196147icj.295.1314640769070; Mon, 29 Aug 2011 10:59:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.36.12 with HTTP; Mon, 29 Aug 2011 10:59:09 -0700 (PDT)
In-Reply-To: <20110829163359.GI84494@shinkuro.com>
References: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net> <ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com> <20110829163359.GI84494@shinkuro.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 29 Aug 2011 13:59:09 -0400
Message-ID: <CAPv4CP9QbBkUDVcGFQELoxRY-Y5RP9R=vGKM5uahysdctDHDyA@mail.gmail.com>
Subject: Re: voting system for future venues?
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 17:58:05 -0000

On Mon, Aug 29, 2011 at 12:34, Andrew Sullivan <ajs@anvilwalrusden.com> wro=
te:

Nicely said.  On your last point:

> Indeed, rather than asking how we can optimise the meeting location
> for people who live at 1234 Pine Street, Springfield, USA, why don't
> we ask why we are having three meetings a year? =A0I hear there's
> something called the Internet. =A0Do we really need _everybody_ to get
> together in one place so often? =A0Especially given that we have such a
> globally dispersed population that we now have to trek all over the
> globe for meetings? =A0Maybe we need to have more interim virtual
> meetings, and fewer in-person meetings.

WGs can and should apply discipline to make email the primary mode of
interacting, with occasional virtual meetings and even more occasional
physical meetings.  Just because there is a physical meeting doesn't
mean a WG should let issues pile up to be resolved there.

From daedulus@btconnect.com  Mon Aug 29 11:08:57 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 451D621F8C0F for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 11:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.234
X-Spam-Level: 
X-Spam-Status: No, score=-2.234 tagged_above=-999 required=5 tests=[AWL=0.365,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xFpp0efAlJiU for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 11:08:56 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by ietfa.amsl.com (Postfix) with ESMTP id D2B9E21F8C04 for <ietf@ietf.org>; Mon, 29 Aug 2011 11:08:55 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr08.btconnect.com with SMTP id ECH19345; Mon, 29 Aug 2011 19:10:16 +0100 (BST)
Message-ID: <02af01cc666d$ff77a000$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Hector Santos" <hsantos@santronics.com>
References: <017801caf360$a477b900$4001a8c0@gateway.2wire.net>	<4086301E-BDC5-49A9-8CCE-97AB2F442BB4@americafree.tv>	<001d01cc63c0$65b78b60$4001a8c0@gateway.2wire.net>	<6.2.5.6.2.20110826021344.0ab6fbe0@resistor.net>	<005b01cc63cb$b42164a0$4001a8c0@gateway.2wire.net>	<CAF4+nEEpxz4g-rjE7GKCyy93S9mYTT3jGVnvp0wkjTeHpzrXng@mail.gmail.com>	<8F38C2201545EEF1F78C65E8@PST.JCK.COM>	<01O5AUN0VTQY00VHKR@mauve.mrochek.com>	<CADPp2fD4MqLAVpMKk405w18pJcJzoqjecQwvZcp=u+YzGtDZtQ@mail.gmail.com>	<4E57E23A.5070605@santronics.com><CADPp2fC6qOvZig34coQ95Nk_yEgsjKRH=NAyvZAEumEx4HxrBg@mail.gmail.com> <4E57EABD.7090708@santronics.com>
Subject: Re: https
Date: Mon, 29 Aug 2011 19:06:23 +0200
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=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4E5BD607.0066, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.8.29.164814:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_PATH, __CP_URI_IN_BODY, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4E5BD608.0128,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 18:08:57 -0000

---- Original Message -----
From: "Hector Santos" <hsantos@santronics.com>
To: "Adam Novak" <interfect@gmail.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Friday, August 26, 2011 8:49 PM
Subject: Re: https


> I see, so as long as its not revoked, if compromised, you are hosed
> until it expires.
>
> I wonder if OCSP (Online Certificate Status Protocol) can help
> addresses this?

Hector

Back in 2008, some people could not access the IETF website using
TLS because of OCSP; I think that the URI for the OCSP site for
the certificate was unavailable, at least for some parts of the
world.  Another potential vector for failure.

Tom Petch

>                Expired or not, it can still be revoked with dynamic
> checking as long as the browser as OCSP enabled.  So I guess its a
> matter of reporting the theft as soon as it is discovered.
>
>
> Adam Novak wrote:
> > On Fri, Aug 26, 2011 at 1:13 PM, Hector Santos <hsantos@santronics.com>
wrote:
> >> Makes you wonder. Why is the concept of expiration required? ï¿½Did the IETF
> >> expire, die? ï¿½Did its value as an Organization go down and only valid on a
> >> year to year basis?
> >
> > As I understand it, expiration is supposed to solve the problem of
> > someone getting their hands on your old certificates and impersonating
> > you. In order to impersonate you, not only do they have to get into
> > your system, they have to have done it in the last year or so.
> >
> > It also keeps certificates for domains from outliving domain
> > registrations for too long. If you don't have the domain when you go
> > to renew the certificate, the CA shouldn't renew it.
> >
> > I guess it also keeps revocation lists short. You only have to
> > remember that a certain certificate was compromised until it expires,
> > instead of forever.
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
> >
>
> --
> Sincerely
>
> Hector Santos
> http://www.santronics.com
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From melinda.shore@gmail.com  Mon Aug 29 11:19:54 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CADC21F8C69 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 11:19:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.544
X-Spam-Level: 
X-Spam-Status: No, score=-3.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6e8u8x8R+k0 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 11:19:53 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id A17A221F8C5D for <ietf@ietf.org>; Mon, 29 Aug 2011 11:19:53 -0700 (PDT)
Received: by pzk33 with SMTP id 33so19787729pzk.18 for <ietf@ietf.org>; Mon, 29 Aug 2011 11:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=PyKS4kMpEOGU0Untc39a+WUZCtJ9QI59QIGfy4/VTIY=; b=ULA+aZOcHmVs9HiejCaOG7uHSHEfk5zdw0b+Ax5kPKoRKUOgeHr5XpGG6b+jBO6szM i95QFVqPviOm14Hi0r+JGscie+pHCkjyvu0jM2qwTzlxqfoDi529k87GFZ3HEtvfRkM9 6WlLAkyQwkobuFSi+9SDySP95CJLoxOez8kgk=
Received: by 10.142.170.5 with SMTP id s5mr2775367wfe.275.1314642078823; Mon, 29 Aug 2011 11:21:18 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id e8sm19654523pbc.8.2011.08.29.11.21.16 (version=SSLv3 cipher=OTHER); Mon, 29 Aug 2011 11:21:17 -0700 (PDT)
Message-ID: <4E5BD8A1.5090309@gmail.com>
Date: Mon, 29 Aug 2011 10:21:21 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: voting system for future venues?
References: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net>	<ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com>	<20110829163359.GI84494@shinkuro.com> <CAPv4CP9QbBkUDVcGFQELoxRY-Y5RP9R=vGKM5uahysdctDHDyA@mail.gmail.com>
In-Reply-To: <CAPv4CP9QbBkUDVcGFQELoxRY-Y5RP9R=vGKM5uahysdctDHDyA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 18:19:54 -0000

On 08/29/2011 09:59 AM, Scott Brim wrote:
> WGs can and should apply discipline to make email the primary mode of
> interacting, with occasional virtual meetings and even more occasional
> physical meetings.  Just because there is a physical meeting doesn't
> mean a WG should let issues pile up to be resolved there.

Well, that's the theory but it's been my experience that
more stuff is being resolved in meetings in recent years
rather than less stuff (also, more voting and less consensus).
I think that there's some relationship between this and
increasing meeting costs, etc., and that both may be tied
to the increasing "professionalization" (professional
standardizers) of the IETF over the past decade or so.

Melinda

From lixia@cs.ucla.edu  Mon Aug 29 12:17:18 2011
Return-Path: <lixia@cs.ucla.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC7E321F8CF7 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 12:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.379
X-Spam-Level: 
X-Spam-Status: No, score=-102.379 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQ6j79yKNzJx for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 12:17:18 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 5757C21F8CF5 for <ietf@ietf.org>; Mon, 29 Aug 2011 12:17:18 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id A300039E80DA; Mon, 29 Aug 2011 12:18:43 -0700 (PDT)
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 1bu8J6mBOb-f; Mon, 29 Aug 2011 12:18:42 -0700 (PDT)
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 D390739E80CF; Mon, 29 Aug 2011 12:18:42 -0700 (PDT)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <68F70126-516B-48C9-A668-FC25EBE5839A@muada.com>
Date: Mon, 29 Aug 2011 12:18:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F697E596-3686-4783-BB5B-BF12000F348B@cs.ucla.edu>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com> <68F70126-516B-48C9-A668-FC25EBE5839A @muada.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 19:17:19 -0000

top posting to make a small point: for the many IETF meetings I've gone =
to over the years, reserving hotel room took less than 10min in general.

For this Taipei meeting however, because the primary hotel price is way =
above US federal allowance (that's how my employer reimburses me), and =
the only overflow host is about equally pricy, for the first time I have =
to find lodging myself--this has taken me hours and still not settled =
yet (even with a local helper from Taiwan).
Wonder whether this time cost should also be considered.

On Aug 29, 2011, at 8:19 AM, Iljitsch van Beijnum wrote:

> On 29 Aug 2011, at 17:01 , Henk Uijterwaal wrote:
>=20
>> If we want more flexibility in order to find better hotel deals, then =
we have
>> to do something like: dates are fixed approximately 1.5 years out, =
and we do
>> not mind having meetings back-to-back with other organizations on the =
clash
>> list.  That means that some folks will have to travel around the =
globe between
>> Friday afternoon and Sunday morning in order to make it from one =
meeting to
>> another.
>=20
> Is this so bad that $300/night room prices for hundreds of =
participants to avoid this issue is a good deal?
>=20
> One potential solution could be to select two or three weeks that =
don't clash or only minimally clash and then start the negotiations with =
a few more options, fixing the date a year or so out.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From jmpolk@cisco.com  Mon Aug 29 13:02:03 2011
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A080321F8C30 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 13:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.571
X-Spam-Level: 
X-Spam-Status: No, score=-103.571 tagged_above=-999 required=5 tests=[AWL=-0.972, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KMJjgXth8Ki7 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 13:02:02 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8259D21F8C31 for <ietf@ietf.org>; Mon, 29 Aug 2011 13:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1999; q=dns/txt; s=iport; t=1314648208; x=1315857808; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=ar7IF2gyqTGK3jIrTqJDns2MDOWJBL5I5/CWUzbj5yE=; b=Z/w4tySAhG9ckBCZ35LcTseamJwQFW5owOPpYkHGjxd8guyEhDg8U6Mr Q4AuxHyfH0jljVdYH1Deph95RuEjshkooJb6eoeT2sOZm0wVzvEJJ2h6o bTmCE/OUSGJW6WUI4MjvEBWRw0wZtK46xq6IStlqX19u7WTnErvHiVUqF 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAKvvW06rRDoI/2dsb2JhbABCp3x3gUABAQEBAwEBAQ8BJQI0BBcHBBgeEBkOMAYBEiKHVJpfAZ8RhkwEh2ScXQ
X-IronPort-AV: E=Sophos;i="4.68,298,1312156800"; d="scan'208";a="17553655"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-8.cisco.com with ESMTP; 29 Aug 2011 20:03:27 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7TK3QsU008199; Mon, 29 Aug 2011 20:03:27 GMT
Message-Id: <201108292003.p7TK3QsU008199@mtv-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Aug 2011 15:03:21 -0500
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: voting system for future venues?
In-Reply-To: <4E5BD8A1.5090309@gmail.com>
References: <BBF5DDFE515C3946BC18D733B20DAD2302FF72@XMB105ADS.rim.net> <ACACC04A-FEA8-4AE5-A110-70B4E56AA31D@muada.com> <20110829163359.GI84494@shinkuro.com> <CAPv4CP9QbBkUDVcGFQELoxRY-Y5RP9R=vGKM5uahysdctDHDyA@mail.gmail.com> <4E5BD8A1.5090309@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 20:02:03 -0000

At 01:21 PM 8/29/2011, Melinda Shore wrote:
>On 08/29/2011 09:59 AM, Scott Brim wrote:
>>WGs can and should apply discipline to make email the primary mode of
>>interacting, with occasional virtual meetings and even more occasional
>>physical meetings.  Just because there is a physical meeting doesn't
>>mean a WG should let issues pile up to be resolved there.
>
>Well, that's the theory but it's been my experience that
>more stuff is being resolved in meetings in recent years
>rather than less stuff (also, more voting and less consensus).
>I think that there's some relationship between this and
>increasing meeting costs, etc., and that both may be tied
>to the increasing "professionalization" (professional
>standardizers) of the IETF over the past decade or so.

my (not so kind) view of professional standardizers) is that they 
slow things down and take too long to make progress - perhaps because 
they aren't that fast on the uptick/too detached from how products 
are actually built -- is that what you believe is happening in the 
IETF now (and for at least the last 5 or so years)?

James

BTW - I don't believe that is what's happening to the IETF, but 
perhaps I'm slow on the uptick. I think we're getting into way too 
complicated architectures involving way too many lateral WGs and/or 
Areas. We also jump too fast to the newest shiny thing, and don't 
complete our work in a given WG or Area.

Take RTCWEB in the RAI Area, for instance. It's all the rage, cuz 
it's the newest, flashiest, shiniest thing, so everyone in RAI swarms 
to it - but it's not new. It's a rehash of something (or several 
somethings) just built in the RAI Area. It's just packaged a little 
differently, is backed by a HUGE company, and no one wants to get 
left out of the "in" crowd who "was there from the start..."


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


From hartmans@mit.edu  Mon Aug 29 13:25:48 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF3A21F8D13; Mon, 29 Aug 2011 13:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.194
X-Spam-Level: 
X-Spam-Status: No, score=-103.194 tagged_above=-999 required=5 tests=[AWL=-1.548, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYx4LfydXDUk; Mon, 29 Aug 2011 13:25:47 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id BA97021F8D0B; Mon, 29 Aug 2011 13:25:46 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (m890536d0.tmodns.net [208.54.5.137]) (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 34879203CB; Mon, 29 Aug 2011 16:29:14 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6191942B7; Mon, 29 Aug 2011 16:26:50 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Henry B. Hotz" <hotz@jpl.nasa.gov>
Subject: Re: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> <87sjoocgxs.fsf@latte.josefsson.org> <D59A1036-ABCA-43CE-B3D3-1D3334CABE2B@jpl.nasa.gov> <tsl1uw4pb60.fsf@mit.edu> <2A8A3165-D962-4958-92E4-574F9231C265@jpl.nasa.gov>
Date: Mon, 29 Aug 2011 16:26:50 -0400
In-Reply-To: <2A8A3165-D962-4958-92E4-574F9231C265@jpl.nasa.gov> (Henry B. Hotz's message of "Mon, 29 Aug 2011 10:16:58 -0700")
Message-ID: <tslliucq7zp.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: Simon Josefsson <simon@josefsson.org>, "ietf@ietf.org" <ietf@ietf.org>, "gareth.richards@rsa.com" <gareth.richards@rsa.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf-krb-wg@lists.anl.gov" <ietf-krb-wg@lists.anl.gov>, Sam Hartman <hartmans-ietf@mit.edu>, "david.black@emc.com" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 20:25:48 -0000

>>>>> "Henry" == Henry B Hotz <hotz@jpl.nasa.gov> writes:

    Henry> I was thinking that if it's a proprietary OTP, we can still
    Henry> use it even if the algorithm is secret.  If we know we're
    Henry> getting a "clear text" OTP value and we have an (unspecified)
    Henry> method of verifying it against some external infrastructure,
    Henry> that's enough to use otp-preauth.  However I don't think this
    Henry> actually requires a complete registry.  A single
    Henry> undefined/external entry for the existing PSKC registry would
    Henry> be sufficient, wouldn't it?

It's exactly the proprietary OTPs where I think they should specify
their own URI in their own namespace.

From hartmans@mit.edu  Mon Aug 29 13:27:07 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0633E21F8D21; Mon, 29 Aug 2011 13:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.936
X-Spam-Level: 
X-Spam-Status: No, score=-102.936 tagged_above=-999 required=5 tests=[AWL=-1.290, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ri3CMuB+u+6; Mon, 29 Aug 2011 13:27:06 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 7D45421F8D20; Mon, 29 Aug 2011 13:27:06 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (m890536d0.tmodns.net [208.54.5.137]) (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 C6271203C7; Mon, 29 Aug 2011 16:30:42 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2C14042B7; Mon, 29 Aug 2011 16:28:22 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: <gareth.richards@rsa.com>
Subject: Re: Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> <87sjoocgxs.fsf@latte.josefsson.org> <B1371F619AB0A94C9AC73CF2E475485B038C518909@MX11A.corp.emc.com>
Date: Mon, 29 Aug 2011 16:28:22 -0400
In-Reply-To: <B1371F619AB0A94C9AC73CF2E475485B038C518909@MX11A.corp.emc.com> (gareth richards's message of "Fri, 26 Aug 2011 11:58:55 -0400")
Message-ID: <tslhb50q7x5.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: simon@josefsson.org, ietf@ietf.org, david.black@emc.com, ietf-krb-wg@lists.anl.gov, hartmans-ietf@mit.edu, gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 20:27:07 -0000

>>>>>   <gareth.richards@rsa.com> writes:

    > Could we add a URI list to draft-lha-krb-wg-some-numbers-to-iana?

We could do that.  Doing so would be a very inefficient way of moving
the OTP document forward.  I'd recommend that we use an existing
registry.  If we cannot do that, we'll need to do the registry in the
OTP document.

From stpeter@stpeter.im  Mon Aug 29 14:35:35 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ADC321F8C56 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 14:35:35 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BUMi17qGWqxw for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 14:35:34 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A31EF21F8C44 for <ietf@ietf.org>; Mon, 29 Aug 2011 14:35:34 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A51F64174A for <ietf@ietf.org>; Mon, 29 Aug 2011 15:39:32 -0600 (MDT)
Message-ID: <4E5C067A.9080400@stpeter.im>
Date: Mon, 29 Aug 2011 15:36:58 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: 2119bis
X-Enigmail-Version: 1.3.1
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 21:35:35 -0000

After staring at http://www.rfc-editor.org/errata_search.php?eid=499 for
long enough, I finally decided to submit an I-D that is intended to
obsolete RFC 2119. I hope that I've been able to update and clarify the
text in a way that is respectful of the original. Feedback is welcome.

http://www.ietf.org/id/draft-saintandre-2119bis-01.txt

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From narten@us.ibm.com  Mon Aug 29 14:49:05 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1101B21F8C87 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 14:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNQ2VrUued2a for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 14:49:04 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id 8A07A21F8C86 for <ietf@ietf.org>; Mon, 29 Aug 2011 14:49:04 -0700 (PDT)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7TLgVPq002264 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:42:31 -0600
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7TLoLat152632 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:50:21 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7TFoK4K028964 for <ietf@ietf.org>; Mon, 29 Aug 2011 09:50:20 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-76-143-109.mts.ibm.com [9.76.143.109]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7TFoIq2028915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Aug 2011 09:50:19 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7TLoIXh031665; Mon, 29 Aug 2011 17:50:19 -0400
Message-Id: <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: 2119bis
In-reply-to: <4E5C067A.9080400@stpeter.im>
References: <4E5C067A.9080400@stpeter.im>
Comments: In-reply-to Peter Saint-Andre <stpeter@stpeter.im> message dated "Mon, 29 Aug 2011 15:36:58 -0600."
Date: Mon, 29 Aug 2011 17:50:18 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 21:49:05 -0000

It would help me if you explained the diffs and the *reasons* for the
proposed changes.

E.g, the new text says:

   This term means that the feature or behavior is a limited requirement
   of the specification, so that an implementation has a conditional
   obligation to implement the feature or to behave as defined, unless
   there is a strong, explicitly described reason not to do so in
   particular circumstances.  Those who implement the specification or
   deploy conformant technologies need to understand and carefully weigh
   the full implications of violating the requirement before doing so.
   The term "RECOMMENDED" is equivalent to "SHOULD".

The wording "unless there is a strong explicitly described reason not
to do so in particular circumstances" is new wording and my first
reaction is it's not helpful. I.e., "explicitely described by who?"
Explicitely specified in the text? If so, that seems unworkable in
practice.

What problem is this bis document intended to fix?

Thomas

From eburger-l@standardstrack.com  Mon Aug 29 15:07:51 2011
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C10E21F8C3D for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLt6mIGZoBnm for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:07:50 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 879CB21F8C3C for <ietf@ietf.org>; Mon, 29 Aug 2011 15:07:50 -0700 (PDT)
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:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=xRd5kdvS9kXk7bLORMKCuJC10hO96ME3srrUlWPCx4ji6sQ2pnhWdPQgSxP492N4DP+G4srQXEfcKzr1+lFNtTjNYkoZ/c8iuoOgX6bcpc7SL509PuPBrXb8W8VmKJpL;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QyA0B-0008Ro-Fi; Mon, 29 Aug 2011 15:08:19 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>
Date: Mon, 29 Aug 2011 18:08:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>
To: Narten Thomas <narten@us.ibm.com>, Saint-Andre Peter <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 22:07:51 -0000

I would assume in the text of the document.  This paragraph is simply an =
enumeration of Burger's Axiom:
	For every SHOULD, there must be an UNLESS, otherwise the SHOULD =
is a MAY.

On Aug 29, 2011, at 5:50 PM, Thomas Narten wrote:

> It would help me if you explained the diffs and the *reasons* for the
> proposed changes.
>=20
> E.g, the new text says:
>=20
>   This term means that the feature or behavior is a limited =
requirement
>   of the specification, so that an implementation has a conditional
>   obligation to implement the feature or to behave as defined, unless
>   there is a strong, explicitly described reason not to do so in
>   particular circumstances.  Those who implement the specification or
>   deploy conformant technologies need to understand and carefully =
weigh
>   the full implications of violating the requirement before doing so.
>   The term "RECOMMENDED" is equivalent to "SHOULD".
>=20
> The wording "unless there is a strong explicitly described reason not
> to do so in particular circumstances" is new wording and my first
> reaction is it's not helpful. I.e., "explicitely described by who?"
> Explicitely specified in the text? If so, that seems unworkable in
> practice.
>=20
> What problem is this bis document intended to fix?
>=20
> Thomas
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From eburger-l@standardstrack.com  Mon Aug 29 15:11:02 2011
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A023A21F8549 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3NhgakCPEgR for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:11:01 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 90D7521F8538 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:11:01 -0700 (PDT)
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:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=KB5kBgs+Y5fLlWy8hV083M+nMKHuru4qLWMBp+X4XLNQ1sM1P//DV2LqEyc/eQpBlMpGSMZD5R718LNTMISmbSRjYXfhYNPPc2/FYhE//NKSrysN5aNE9TgjTO2gn23W;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1QyA35-0003wD-Gc; Mon, 29 Aug 2011 15:11:19 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <4E5C067A.9080400@stpeter.im>
Date: Mon, 29 Aug 2011 18:11:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <24D227EB-3F6B-4B0C-B9D8-158699959E67@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 22:11:03 -0000

Please make my English language sensibilities and satisfy Burger's =
Second Law of standards documents at the same time, forbidding passive =
voice.  Can we have the following as the boilerplate?  Thanks.

Either:

In this document, [RFCXXXX] describes the following conformance terms: =
"MUST", ...

Or:

[RFCXXXX] describes the following conformance terms used in this =
document: "MUST", ...


Also, from a typographic point of view, why are we quoting single worlds =
that are already in quotes?


On Aug 29, 2011, at 5:36 PM, Peter Saint-Andre wrote:

> After staring at http://www.rfc-editor.org/errata_search.php?eid=3D499 =
for
> long enough, I finally decided to submit an I-D that is intended to
> obsolete RFC 2119. I hope that I've been able to update and clarify =
the
> text in a way that is respectful of the original. Feedback is welcome.
>=20
> http://www.ietf.org/id/draft-saintandre-2119bis-01.txt
>=20
> Peter
>=20
> --=20
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com  Mon Aug 29 15:14:42 2011
Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 108DC21F8551 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.918
X-Spam-Level: 
X-Spam-Status: No, score=-102.918 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77CEgdM4tkZX for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:14:41 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB8521F8538 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:14:41 -0700 (PDT)
Received: by pzk33 with SMTP id 33so20276874pzk.18 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:16:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HFpop/IIbvvtY9FBGxfoOZ/JHSFYHkZL9sVycSNxT+w=; b=STdjvRR437QOrLQEwPgHh35oPHHqWqJHehAOtQR/9/FF1LNZ6xS00ldu2M/nHIcTdA W/pqBEVOenK0lp5ICWlU1uehRi2lELeDBPbRt3w9mspe3/Vdt/YTm5fY4oudM1r4ucZQ zOq8XF3I1ikk6P/4Z4r8C0yS/8jzMH1xfelOA=
Received: by 10.142.125.18 with SMTP id x18mr2765155wfc.412.1314656167098; Mon, 29 Aug 2011 15:16:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.98.5 with HTTP; Mon, 29 Aug 2011 15:15:27 -0700 (PDT)
In-Reply-To: <4E5C067A.9080400@stpeter.im>
References: <4E5C067A.9080400@stpeter.im>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Tue, 30 Aug 2011 00:15:27 +0200
Message-ID: <CAHhFybrSSNa-hmrCJ5gmG0-9CUZpvPhaTHP3sjMUgq4aXLtReA@mail.gmail.com>
Subject: Re: 2119bis
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 22:14:42 -0000

On 29 August 2011 23:36, Peter Saint-Andre wrote:

> staring at http://www.rfc-editor.org/errata_search.php?eid=499 for
> long enough, I finally decided to submit an I-D that is intended to
> obsolete RFC 2119.

There are literally thousands of documents (not only RFCs, also W3C
standards, etc.) with normative references to RFC 2119 (sic!) instead
of BCP 14, and I see no compelling reason to render these references
as "historic".

For starters simply confirm the erratum, I don't see why that caused
you headaches.

IMO it is not necessary (but allowed) to import any BCP 14 terms not
actually used in a document, i.e., I disagree with section 4 in your
draft.

How about trying an "updates 2119" and status BCP, where BCP 14 then
consists of 2119 and 2119bis, and old RFC 2119 references are still
okay "as is".

Readers with difficulties to figure out what RFC 2119 meant might
find the confirmed erratum and the "updated by 2119bis" with better
answers.  Authors could use RFC 2119, 2119bis, or even BCP 14 in
the references of new documents, where "BCP 14" would be new, IIRC
RFC 2119 did not permit this -- fearing precisely what is happening
now, somebody trying to update critical terms.  I think that your
new definitions match precisely what RFC 2119 wanted, but I'm also
almost sure that some old "2119 clients" will disagree.

-Frank

From brian.e.carpenter@gmail.com  Mon Aug 29 15:15:01 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAA6D21F8C54 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:15:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pNsKv4LsjDcU for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:15:01 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id CC0EA21F8538 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:15:00 -0700 (PDT)
Received: by gxk19 with SMTP id 19so6064185gxk.31 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:16:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vAbTegL8sO+lBGXNzs+fBURCDSKLBVbSiWdwYidxOIE=; b=iCOTjsj+DxhJ8dEr4LXkctmbGIdNjOBeMTafYKvAx/gLFQ3KQmQ56JTy+MoO5pqri1 ykMRPkukfQsrqfDa+8rvIol0bbZAgbTyPJuR5TDNpVNicgnvPJbrfi4YQeUmzELIC0kX KaI94lqFxifxCdqzf0Zd0yPM4VAtD0KrXysew=
Received: by 10.143.59.10 with SMTP id m10mr3075614wfk.418.1314656175308; Mon, 29 Aug 2011 15:16:15 -0700 (PDT)
Received: from [202.106.79.19] ([202.106.79.19]) by mx.google.com with ESMTPS id i1sm20547486pbe.1.2011.08.29.15.16.12 (version=SSLv3 cipher=OTHER); Mon, 29 Aug 2011 15:16:14 -0700 (PDT)
Message-ID: <4E5C0FA6.6060805@gmail.com>
Date: Tue, 30 Aug 2011 10:16:06 +1200
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: Eric Burger <eburger-l@standardstrack.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>
In-Reply-To: <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Narten Thomas <narten@us.ibm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 22:15:02 -0000

On 2011-08-30 10:08, Eric Burger wrote:
> I would assume in the text of the document.  This paragraph is simply an enumeration of Burger's Axiom:
> 	For every SHOULD, there must be an UNLESS, otherwise the SHOULD is a MAY.

And there can be cases where even a MUST needs an "unless". These cases can be fixed
by using regular English in the draft.

I'm not sure this needs new legislation. There is one real bug in 2119,
which is that "NOT RECOMMENDED" is not listed in the prescribed boilerplate.

   Brian

From john-ietf@jck.com  Mon Aug 29 15:19:15 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA3C921F8BB3 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBQM7X6cUi+n for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:19:15 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4165121F8A58 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:19:15 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QyAC0-000Enr-1X; Mon, 29 Aug 2011 18:20:32 -0400
Date: Mon, 29 Aug 2011 18:20:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: 2119bis
Message-ID: <AC3F57497C217C5A56C80220@PST.JCK.COM>
In-Reply-To: <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.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 discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 22:19:16 -0000

--On Monday, August 29, 2011 17:50 -0400 Thomas Narten
<narten@us.ibm.com> wrote:

> It would help me if you explained the diffs and the *reasons*
> for the proposed changes.
> 
>...
> The wording "unless there is a strong explicitly described
> reason not to do so in particular circumstances" is new
> wording and my first reaction is it's not helpful. I.e.,
> "explicitely described by who?" Explicitely specified in the
> text? If so, that seems unworkable in practice.
> 
> What problem is this bis document intended to fix?

+1

Note that, although it has often not been understood and there
has been pushback from an occasional AD, we've traditionally
never insisted on use of the 2119 definitions but instead have
permitted individual documents to define their own conformance
norms if they could justify doing so.  I can't tell whether this
document is intended to change that or not.

In addition, if you are going to recommend alternative
terminology for situations in which conformance language is
inappropriate, it would be nice for the community (and for the
RFC Editor) if the terms suggested as examples were literate.
For example, because specifications and protocols are rarely
animate, it is not clear than one can possible "need to" do much
of anything.

   john


From spencer@wonderhamster.org  Mon Aug 29 15:27:56 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90A4F21F8546 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:27:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.217
X-Spam-Level: 
X-Spam-Status: No, score=-101.217 tagged_above=-999 required=5 tests=[AWL=-0.478, BAYES_20=-0.74, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WU-GjcTgTHJR for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 15:27:56 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id EC37C21F8560 for <ietf@ietf.org>; Mon, 29 Aug 2011 15:27:55 -0700 (PDT)
Received: from S73602b ([50.58.7.243]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0Lmrky-1RPnRE3GMW-00hMvC; Mon, 29 Aug 2011 18:29:15 -0400
Message-ID: <6964BE866F744C9382ACAE38DDD26151@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Peter Saint-Andre" <stpeter@stpeter.im>
References: <4E5C067A.9080400@stpeter.im>
Subject: Re: 2119bis
Date: Mon, 29 Aug 2011 17:29:12 -0500
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.6109
X-Provags-ID: V02:K0:SH7oF3HaFiHit8SN8YaNqnJVcwok1PDndGWohiqZaJX Sw3okonAOVu+aMHp8D3/7fYhX2kFbzL9c4PCpGYBLXj25yWren VS2y0rYqKLYs3X2F/5eLR6KOGECatDc+QQ03p/5luRt3rXXCLf SmKHJ0ZA8M9ZMOv6K0l4lJIfUhLpU14UFzh0gA8fWeZ2fNCRzW XS29PcxRNz7TsDf/i3rV4h/TofKPXxVKwWHYryDl5QNEO/lS6i XcD1TaNGNx7lNyIdmexslsZ0+NY998u2nbNT/KRU63tXauF5vB ivAFzwAXU8ZGJUuDMQoj6ApFzOX7e4vwspv7sI9vHf7wHzqYrI edU4nVwct3G+rAwvNvwsljd9GVMIo2yKbZjx8xZth
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 22:27:56 -0000

Peter,

Thank you for submitting this draft. It clarifies some of the most 
consistent sources of cyclic discussion that appear on the IETF discussion 
list.

I have a couple of questions.

The most consistent source of cyclic discussion that I didn't see addressed, 
is the use of RFC 2119 conformance terms in requirements drafts, and various 
other flavors of non-standards-track drafts. The draft itself explicitly 
targets standards-track documents.

My impression is that acceptable practice varies across the IETF, so (at 
least when I was an active Gen-ART reviewer) this came up from time to time 
in cross-area reviews. Is there anything the IESG can say about this, to 
give guidance to the community?

Sections 2.3 and 2.4 leave the requirement to say why one might not 
implement a SHOULD (and SHOULD NOT) as, well, a SHOULD. To ask the 
meta-review question, is there a reason why explaining a SHOULD (and SHOULD 
NOT) is a SHOULD, and not a MUST? :D

It's fine with me if the list of reasons isn't complete (so, "SHOULD" = "do 
X unless you have a good reason; good reasons include Y, and there may be 
other good reasons" would be implicit), but a bare SHOULD (or SHOULD NOT) 
with no explanation doesn't seem helpful. I've been told by some working 
groups "we think doing it is a MUST, but some deployed implementations don't 
do it, so it's a SHOULD". If that's the reason, perhaps writing it down 
would be healthy.

And I'd really like to see discussions of consequences as a MUST, even if 
explaining a SHOULD (or SHOULD NOT) remains a SHOULD.

I hesitate to bring the last one up, but I also see drafts that use the 
formulation "MUST do X unless Y". Would it be helpful to mention this? I 
believe "MUST X unless Y" is the moral equivalent of a SHOULD - perhaps you 
don't have to do anything except say that?

Thanks again for doing the work. Any cyclic discussion we can stop cycling 
on, is a beautiful thing!

Spencer 


From johnl@iecc.com  Mon Aug 29 16:14:40 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA99221F8BE4 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 16:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.132
X-Spam-Level: 
X-Spam-Status: No, score=-111.132 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GnbckZI-NjL5 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 16:14:40 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 1339721F8BAB for <ietf@ietf.org>; Mon, 29 Aug 2011 16:14:39 -0700 (PDT)
Received: (qmail 35650 invoked from network); 29 Aug 2011 23:16:03 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 29 Aug 2011 23:16:03 -0000
Received: (qmail 89717 invoked from network); 29 Aug 2011 23:16:03 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 29 Aug 2011 23:16:03 -0000
Date: 29 Aug 2011 23:15:41 -0000
Message-ID: <20110829231541.66138.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: schedules, was voting system for future venues?
In-Reply-To: <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: iljitsch@muada.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 23:14:41 -0000

>Obviously the date needs to be fixed at some point, but does it really
>have to be six years in advance? (
>http://www.ietf.org/meeting/upcoming.html )

As I understand it, the main reason to schedule so far out is to avoid
collisions with other meetings that attract a large number of the same
people.

If there's a way to have more date flexibility without colliding with
other meetings, I suspect the IAOC would be highly interested to hear
about it.

R's,
John

From mnot@mnot.net  Mon Aug 29 17:06:48 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C14E221F8BA0 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 17:06:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.351
X-Spam-Level: 
X-Spam-Status: No, score=-105.351 tagged_above=-999 required=5 tests=[AWL=-2.752, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gc9Jvfqvnebq for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 17:06:48 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 16ACA21F8B77 for <ietf@ietf.org>; Mon, 29 Aug 2011 17:06:48 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.37.195]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0E42522E247; Mon, 29 Aug 2011 20:08:12 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4E5C067A.9080400@stpeter.im>
Date: Tue, 30 Aug 2011 10:08:12 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net>
References: <4E5C067A.9080400@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1244.3)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 00:06:48 -0000

Thanks for starting this, Peter. A few comments / topics for discussion:

1) I agree that the "SHOULD... UNLESS" pattern ought be documented.


2) I strongly believe that authors should be encouraged to enumerate the =
potential subjects of conformance terms, and to use them in every =
instance.

For example, a requirement like this:

"""The Foo header MUST contain the "bar" directive"""

is ambiguous; it doesn't specify who has to do what. Rather,

"""Senders MUST include the "bar" directive when producing the Foo =
header; recipients that receive a Foo header without a "bar" directive =
MUST ..."""

is unambiguous (assuming that the spec defines the terms "sender" and =
"recipient").


3) It may be worth further cautioning against over-use of MAY; this is =
the most-abused term, IME. Perhaps encouraging people to make =
requirements testable on the wire would help.


4) WRT to the status of the document -- if people really feel that we =
don't need to revise 2119, I'd define this as a superset of 2119 and NOT =
obsolete it; i.e., have documents opt into it. However, I'd hope that we =
can get consensus that it's time to build on what 2119 offers.

Cheers,



On 30/08/2011, at 7:36 AM, Peter Saint-Andre wrote:

> After staring at http://www.rfc-editor.org/errata_search.php?eid=3D499 =
for
> long enough, I finally decided to submit an I-D that is intended to
> obsolete RFC 2119. I hope that I've been able to update and clarify =
the
> text in a way that is respectful of the original. Feedback is welcome.
>=20
> http://www.ietf.org/id/draft-saintandre-2119bis-01.txt
>=20
> Peter
>=20
> --=20
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

--
Mark Nottingham   http://www.mnot.net/




From randy_presuhn@mindspring.com  Mon Aug 29 18:03:33 2011
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2DDD21F8BB3 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:03:33 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPNLShQVHiyB for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:03:33 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC7521F8BAB for <ietf@ietf.org>; Mon, 29 Aug 2011 18:03:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=qKSoJ5TR8eZ4+H3ZfIfoDhXPbnSepL5AHW3kyz4njV5bCy01CiWdZjkQ7uCnT3DD; 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.38.147.127] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QyCl6-0003Jj-Q7 for ietf@ietf.org; Mon, 29 Aug 2011 21:04:57 -0400
Message-ID: <003401cc66b1$d35af5a0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF discussion list" <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im><201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>
Subject: Re: 2119bis
Date: Mon, 29 Aug 2011 18:12:01 -0700
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8887f779e183b2ee28820a9fb884ade3ab6c00b8524ef6e44fc350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.38.147.127
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 01:03:34 -0000

Hi -

> From: "Eric Burger" <eburger-l@standardstrack.com>
> To: "Narten Thomas" <narten@us.ibm.com>; "Saint-Andre Peter" <stpeter@stpeter.im>
> Cc: "IETF discussion list" <ietf@ietf.org>
> Sent: Monday, August 29, 2011 3:08 PM
> Subject: Re: 2119bis
>
> I would assume in the text of the document.  This paragraph is simply an enumeration of Burger's Axiom:
> For every SHOULD, there must be an UNLESS, otherwise the SHOULD is a MAY.

I disagree.  If the "UNLESS" cases can be fully enumerated, then
"SHOULD x UNLESS y" is equivalent to "WHEN NOT y MUST X."
(Both beg the question of whether we would need to spell out that
"WHEN y MUST NOT X" is not necessarily an appropriate inference.)

RFC 2119 SHOULD is appropriate when the "UNLESS" cases are
known (or suspected) to exist, but it is not practical to exhaustively
identify them all.

Let's not gild this lily.

Randy


From moore@network-heretics.com  Mon Aug 29 18:45:50 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D135321F8A36 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.515
X-Spam-Level: 
X-Spam-Status: No, score=-3.515 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id peR6pToQwe+f for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:45:50 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 491E921F8A23 for <ietf@ietf.org>; Mon, 29 Aug 2011 18:45:50 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2BA0820BD8; Mon, 29 Aug 2011 21:47:16 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 29 Aug 2011 21:47:16 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=dte jdNpasH9DSeUhNkryIUG9fhE=; b=TOWfzhesu4od2+erMjiWZAd4gTJ1hgLgj2D hFnLitST0t55ddjKCXiLMCkw2bKmV5utzvsgqc5tqz1YnuBPQ7Sul+ey1JsgyTwp XbKkRuMwPK1haA5W954fny+5yFGfC5mf1UmIVAegb33DHfrRCCJjzPzvZTC0oF/m TWctiJKU=
X-Sasl-enc: gsEDeaydklDCKdYCdKi+Im5eIqx8VKrN7D1WXNj+bbg1 1314668835
Received: from [10.59.1.28] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 999DFAC0176; Mon, 29 Aug 2011 21:47:14 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-36--793300645
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <003401cc66b1$d35af5a0$6801a8c0@oemcomputer>
Date: Mon, 29 Aug 2011 21:47:11 -0400
Message-Id: <5C0D8757-6FF4-4945-83BB-9FCA59C6906A@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im><201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 01:45:50 -0000

--Apple-Mail-36--793300645
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Aug 29, 2011, at 9:12 PM, Randy Presuhn wrote:

> RFC 2119 SHOULD is appropriate when the "UNLESS" cases are
> known (or suspected) to exist, but it is not practical to exhaustively
> identify them all.

+1.


--Apple-Mail-36--793300645
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><div>On Aug 29, 2011, at 9:12 PM, Randy Presuhn wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">RFC 2119 =
SHOULD is appropriate when the "UNLESS" cases are<br>known (or =
suspected) to exist, but it is not practical to exhaustively<br>identify =
them =
all.<br></span></blockquote></div><br><div>+1.</div><div><br></div></body>=
</html>=

--Apple-Mail-36--793300645--

From ned+ietf@mauve.mrochek.com  Mon Aug 29 18:49:19 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AFA121F8ACE for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZBqaI-IbXVt for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:49:18 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id B301A21F8A58 for <ietf@ietf.org>; Mon, 29 Aug 2011 18:49:18 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5FL6UTK8G0103PR@mauve.mrochek.com> for ietf@ietf.org; Mon, 29 Aug 2011 18:49:22 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5C6AOYDC0014O5Z@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 29 Aug 2011 18:49:19 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5FL6TFAY8014O5Z@mauve.mrochek.com>
Date: Mon, 29 Aug 2011 18:47:45 -0700 (PDT)
Subject: Re: 2119bis
In-reply-to: "Your message dated Mon, 29 Aug 2011 18:12:01 -0700" <003401cc66b1$d35af5a0$6801a8c0@oemcomputer>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314668996; i=@mrochek.com; bh=6VqwhA6RH8FEAPa1o0iil62YQm88B6YcZGLpVeqqxik=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=OGzSYGmDSLFPsA/HJ2gam9qlUBfkpKm3wvkMQRZFwQn5pb/MEI0p3Sen8BtqVwJB0 eQzFDEplwhlBnzJnwh7eYikYj2LJ5jndAqA8MR3stH6OAVZ/2WlQYrYJSa93h+Pu9K S82UmMtdmFVgzIFJSmH/Fk304VL0dqH3/5omkbTA=
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 01:49:19 -0000

> Hi -

> > From: "Eric Burger" <eburger-l@standardstrack.com>
> > To: "Narten Thomas" <narten@us.ibm.com>; "Saint-Andre Peter" <stpeter@stpeter.im>
> > Cc: "IETF discussion list" <ietf@ietf.org>
> > Sent: Monday, August 29, 2011 3:08 PM
> > Subject: Re: 2119bis
> >
> > I would assume in the text of the document.  This paragraph is simply an enumeration of Burger's Axiom:
> > For every SHOULD, there must be an UNLESS, otherwise the SHOULD is a MAY.

> I disagree.

I concur with your disagreement. SHOULD should *not* be used when the
list of exceptions is known and practically enumerable.

> If the "UNLESS" cases can be fully enumerated, then
> "SHOULD x UNLESS y" is equivalent to "WHEN NOT y MUST X."
> (Both beg the question of whether we would need to spell out that
> "WHEN y MUST NOT X" is not necessarily an appropriate inference.)

> RFC 2119 SHOULD is appropriate when the "UNLESS" cases are
> known (or suspected) to exist, but it is not practical to exhaustively
> identify them all.

> Let's not gild this lily.

+1

				Ned

From dworley@avaya.com  Mon Aug 29 18:51:37 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 623F421F8B1A for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.969
X-Spam-Level: 
X-Spam-Status: No, score=-102.969 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGxQj2dMgtGt for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 18:51:37 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id D4E8E21F8B0A for <ietf@ietf.org>; Mon, 29 Aug 2011 18:51:36 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAC1BXE7GmAcF/2dsb2JhbABCqAZ3gUABAQEBAgESKDETCwIBCA0IIRAyFwENAQEEEwgah1CcIwKcRYVsYASYS4t0
X-IronPort-AV: E=Sophos;i="4.68,299,1312171200"; d="scan'208";a="204661907"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 29 Aug 2011 21:53:02 -0400
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; 29 Aug 2011 21:48:44 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Mon, 29 Aug 2011 21:53:01 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 29 Aug 2011 21:51:15 -0400
Subject: RE: Routing at the Edges of the Internet
Thread-Topic: Routing at the Edges of the Internet
Thread-Index: AcxkMccWR3AYRPmiRLmAXvQGbo/6cAAAhZcIAAArMbAAoLDXUw==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5868@DC-US1MBEX4.global.avaya.com>
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com><CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com><Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>, <4E5806EC.5050304@dougbarton.us> <CD5674C3CD99574EBA7432465FC13C1B222B1F5864@DC-US1MBEX4.global.avaya.com>, <392CB277BC2EAE4FB83C1206954BA6CEF6AE@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF6AE@newserver.arneill-py.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 01:51:37 -0000

> From: Michel Py [michel@arneill-py.sacramento.ca.us]
>=20
> > I'm no expert in this, but isn't this what ICMP Redirect messages
> > are for?  Aren't routers required to generate them in these cases?
>=20
> Unfortunately, ICMP redirects are often broken. It is a well-known issue
> that the introduction of Windows XP SP2 (a while ago) and the Windows
> Firewall did that.

Someone says, We should have a mechanism to do X!

I reply, We already have a mechanism that does X.

Someone says, Many deployed systems don't implement that mechanism
correctly.

It seems that the answer is to fix the deployed systems, rather than
designing a new mechanism.

Dale

From eburger@standardstrack.com  Mon Aug 29 19:44:16 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E3521F8A62 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 19:44:16 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pv+4LxW+NkR1 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 19:44:15 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3A4CD21F857D for <ietf@ietf.org>; Mon, 29 Aug 2011 19:44:15 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=g/KEFX0CN5WcuQPDDl8beWn+/kgO9GU5vn6zFawi0GskewEStgxHfnK8RhIkUQ5afcEQDBnWyj6KI/wgsg2V6RL1Z0mRnnbc+YwKS3zGW8vaG2d3vXUOOZJ8svgy5N0y;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyEJm-0006nq-C2 for ietf@ietf.org; Mon, 29 Aug 2011 19:44:50 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-4--789843148; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 2119bis
Date: Mon, 29 Aug 2011 22:44:49 -0400
In-Reply-To: <01O5FL6TFAY8014O5Z@mauve.mrochek.com>
To: IETF discussion list <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com>
Message-Id: <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 02:44:16 -0000

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

Yes, and...

I would offer that for most cases, If Y then MUST X or If Z then MUST =
NOT X *are* what people usually mean when they say SHOULD.  In the =
spirit of Say What You Mean, a bare SHOULD at the very least raise an =
ID-nit, suggesting to the author to turn the statement into the if Y =
then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
	SHOULD send a 1 UNLESS you receive a 0
really means
	UNLESS you receive a 0, one MUST send a 1.

My vision of the UNLESS clause is not necessarily a protocol state, but =
an environment state.  These are things that I can see fit the =
SHOULD/UNLESS form:
	SHOULD send a 1 UNLESS you are in a walled garden
	SHOULD flip bit 27 UNLESS you have a disk
	SHOULD NOT explode UNLESS you are a bomb
are all reasonable SHOULD-level statements.

I would offer that ANY construction of SHOULD without an UNLESS is a =
MAY.  Unless of course one considers us the Protocol Nanny's(tm) - if do =
not do a SHOULD, we will send you to bed without your treacle! I.e., =
there IS NO DISTINCTION BETWEEN A BARE SHOULD AND A MAY.

On Aug 29, 2011, at 9:47 PM, ned+ietf@mauve.mrochek.com wrote:

>> Hi -
>=20
>>> From: "Eric Burger" <eburger-l@standardstrack.com>
>>> To: "Narten Thomas" <narten@us.ibm.com>; "Saint-Andre Peter" =
<stpeter@stpeter.im>
>>> Cc: "IETF discussion list" <ietf@ietf.org>
>>> Sent: Monday, August 29, 2011 3:08 PM
>>> Subject: Re: 2119bis
>>>=20
>>> I would assume in the text of the document.  This paragraph is =
simply an enumeration of Burger's Axiom:
>>> For every SHOULD, there must be an UNLESS, otherwise the SHOULD is a =
MAY.
>=20
>> I disagree.
>=20
> I concur with your disagreement. SHOULD should *not* be used when the
> list of exceptions is known and practically enumerable.
>=20
>> If the "UNLESS" cases can be fully enumerated, then
>> "SHOULD x UNLESS y" is equivalent to "WHEN NOT y MUST X."
>> (Both beg the question of whether we would need to spell out that
>> "WHEN y MUST NOT X" is not necessarily an appropriate inference.)
>=20
>> RFC 2119 SHOULD is appropriate when the "UNLESS" cases are
>> known (or suspected) to exist, but it is not practical to =
exhaustively
>> identify them all.
>=20
>> Let's not gild this lily.
>=20
> +1
>=20
> 				Ned
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-4--789843148
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAwMjQ0NDlaMCMGCSqGSIb3DQEJ
BDEWBBRUHzN/aIW+bPbNh+3z2Tl1d/XW0jCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBADpOg9sQB2thmJ/5EaGx/qEff1sDzO1rOAORhqpw98MzJoLN
ZI8mjH1JzQJvlyTueZOjid488MgzpZhfTO5qUN2qSaS9lIqfwAKZz2FLiCgfY7O4ABKS91CD++jz
ao7DWm4y1IheCgUVSEni4oUCF+gQ3G88Zv2SNwJ/efjQ9vqqPQRcz0YhnnjTBBRHFkdXIBd5B+x+
QVspR326WG2SrvJdWS4LvBgaCUHsVZ1/C29QVkFyHZLmRLP04apR30rFsskV9YEd1ptSbvcdWjxm
GspjHEs5hpyiL9Yu5lZ2KN2J8oyQsu1753jW2YnsRwaCc96TRKAAnWmTn83nNlq348QAAAAAAAA=

--Apple-Mail-4--789843148--

From michel@arneill-py.sacramento.ca.us  Mon Aug 29 19:49:21 2011
Return-Path: <michel@arneill-py.sacramento.ca.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 529F321F86DF for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 19:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[AWL=0.163,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsqEexa4-juo for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 19:49:20 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id BC89C21F86DD for <ietf@ietf.org>; Mon, 29 Aug 2011 19:49:20 -0700 (PDT)
Content-class: urn:content-classes:message
Subject: RE: Routing at the Edges of the Internet
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Aug 2011 19:50:45 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF6B6@newserver.arneill-py.local>
X-MimeOLE: Produced By Microsoft Exchange V6.5
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5868@DC-US1MBEX4.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Routing at the Edges of the Internet
Thread-Index: AcxkMccWR3AYRPmiRLmAXvQGbo/6cAAAhZcIAAArMbAAoLDXUwABqKtg
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com><CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com><Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>, <4E5806EC.5050304@dougbarton.us><CD5674C3CD99574EBA7432465FC13C1B222B1F5864@DC-US1MBEX4.global.avaya.com>, <392CB277BC2EAE4FB83C1206954BA6CEF6AE@newserver.arneill-py.local> <CD5674C3CD99574EBA7432465FC13C1B222B1F5868@DC-US1MBEX4.global.avaya.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 02:49:21 -0000

> Worley, Dale R wrote:
> Someone says, Many deployed systems don't
> implement that mechanism correctly.

That's not what I said; the mechanism is deployed correctly, the problem
is that there is another layer on top of it (in that case, the Windows
Firewall, but it's not the only culprit) that prevents the otherwise
working code from working correctly. I forgot to mention it, but the #1
remedy to the problem was to disable the SP2 Windows Firewall.

This problem has become highly visible because of the sheer number of
Windows XP hosts out there. Even as of today, XP still ranks #1 in the
deployed host platform. That being said, I have seen many firewall
policies on the firewall side that blocked it too; the problem is not
only a Microsoft one.

The mechanism (ICMP redirects) is technically fine and socially not.
People have become paranoid and now they firewall everything. It is a
behavioral animal. I'm not saying it's a good idea; the market answer to
crossing firewalls is to encapsulate everything into HTTPS, which is
probably worse. But then again, we have to deal with market pressure
against technically sound solutions, and the market almost always wins.


> It seems that the answer is to fix the deployed
> systems, rather than designing a new mechanism.

It is not the deployed systems we have to fix.
P.I.C.N.I.C.


Michel.


From mnot@mnot.net  Mon Aug 29 19:53:34 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D377D21F89BA for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 19:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.292
X-Spam-Level: 
X-Spam-Status: No, score=-105.292 tagged_above=-999 required=5 tests=[AWL=-2.693, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHa27lE4obYD for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 19:53:33 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7DA21F893C for <ietf@ietf.org>; Mon, 29 Aug 2011 19:53:33 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.37.195]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 08B1B22E1EB; Mon, 29 Aug 2011 22:54:52 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
Date: Tue, 30 Aug 2011 12:54:49 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <806FF78E-17CF-43A3-9F74-80AA876E4A08@mnot.net>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 02:53:34 -0000

On 30/08/2011, at 12:44 PM, Eric Burger wrote:

> Yes, and...
>=20
> I would offer that for most cases, If Y then MUST X or If Z then MUST =
NOT X *are* what people usually mean when they say SHOULD.  In the =
spirit of Say What You Mean, a bare SHOULD at the very least raise an =
ID-nit, suggesting to the author to turn the statement into the if Y =
then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
> 	SHOULD send a 1 UNLESS you receive a 0
> really means
> 	UNLESS you receive a 0, one MUST send a 1.
>=20
> My vision of the UNLESS clause is not necessarily a protocol state, =
but an environment state.  These are things that I can see fit the =
SHOULD/UNLESS form:
> 	SHOULD send a 1 UNLESS you are in a walled garden
> 	SHOULD flip bit 27 UNLESS you have a disk
> 	SHOULD NOT explode UNLESS you are a bomb
> are all reasonable SHOULD-level statements.

If this is the intent, I'd say it should (ahem) really be MUST... =
UNLESS. SHOULD... UNLESS will lead to people misreading it.


> Unless of course one considers us the Protocol Nanny's(tm) - if do not =
do a SHOULD, we will send you to bed without your treacle! I.e., there =
IS NO DISTINCTION BETWEEN A BARE SHOULD AND A MAY.

+1


>=20
> On Aug 29, 2011, at 9:47 PM, ned+ietf@mauve.mrochek.com wrote:
>=20
>>> Hi -
>>=20
>>>> From: "Eric Burger" <eburger-l@standardstrack.com>
>>>> To: "Narten Thomas" <narten@us.ibm.com>; "Saint-Andre Peter" =
<stpeter@stpeter.im>
>>>> Cc: "IETF discussion list" <ietf@ietf.org>
>>>> Sent: Monday, August 29, 2011 3:08 PM
>>>> Subject: Re: 2119bis
>>>>=20
>>>> I would assume in the text of the document.  This paragraph is =
simply an enumeration of Burger's Axiom:
>>>> For every SHOULD, there must be an UNLESS, otherwise the SHOULD is =
a MAY.
>>=20
>>> I disagree.
>>=20
>> I concur with your disagreement. SHOULD should *not* be used when the
>> list of exceptions is known and practically enumerable.
>>=20
>>> If the "UNLESS" cases can be fully enumerated, then
>>> "SHOULD x UNLESS y" is equivalent to "WHEN NOT y MUST X."
>>> (Both beg the question of whether we would need to spell out that
>>> "WHEN y MUST NOT X" is not necessarily an appropriate inference.)
>>=20
>>> RFC 2119 SHOULD is appropriate when the "UNLESS" cases are
>>> known (or suspected) to exist, but it is not practical to =
exhaustively
>>> identify them all.
>>=20
>>> Let's not gild this lily.
>>=20
>> +1
>>=20
>> 				Ned
>> _______________________________________________
>> 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

--
Mark Nottingham   http://www.mnot.net/




From moore@network-heretics.com  Mon Aug 29 20:12:19 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E90E421F8569 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 20:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.521
X-Spam-Level: 
X-Spam-Status: No, score=-3.521 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14drs9-To05G for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 20:12:19 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id E401621F8568 for <ietf@ietf.org>; Mon, 29 Aug 2011 20:12:18 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 6F49020365; Mon, 29 Aug 2011 23:11:29 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Mon, 29 Aug 2011 23:11:29 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=vLS zDTZLUeDnEF1+ZY7+WmrIsDc=; b=cSaNeykjdk8FsU2ktSIIw8eUZRhOIStNsFF 554agew7D8E013vCETVMWlz0pKJPW5yP/CWuAMcmEVZBsc0HLAxJbWwykg4PNANj X+cmnaYqG3D4dpJmgvW+dFljj8Suu7VOjQGBiieb4hAVn0aeJNzLQOch91id7Mza XNufqTQY=
X-Sasl-enc: HySwiljvKgS7BvWX5eK6dYwk3ooS56NwTUVpswTWZ0sG 1314673889
Received: from [10.59.1.28] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id EB0A4AC018A; Mon, 29 Aug 2011 23:11:28 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-37--788248665
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
Date: Mon, 29 Aug 2011 23:11:23 -0400
Message-Id: <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 03:12:20 -0000

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

On Aug 29, 2011, at 10:44 PM, Eric Burger wrote:

> I would offer that ANY construction of SHOULD without an UNLESS is a =
MAY.


The essential beauty of SHOULD is that it gets specification writers and =
working groups out of the all-too-common rathole of trying to anticipate =
and nail down every exceptional case.

Keith


--Apple-Mail-37--788248665
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><div>On Aug 29, 2011, at 10:44 PM, Eric Burger wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I would offer =
that ANY construction of SHOULD without an UNLESS is a =
MAY.</span></blockquote></div><div><br></div><div>The essential beauty =
of SHOULD is that it gets specification writers and working groups out =
of the all-too-common rathole of trying to anticipate and nail down =
every exceptional =
case.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-37--788248665--

From sant9442@gmail.com  Mon Aug 29 20:28:50 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46CE521F8876 for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 20:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hWI5WCMj-Ron for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 20:28:49 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 984FA21F8834 for <ietf@ietf.org>; Mon, 29 Aug 2011 20:28:49 -0700 (PDT)
Received: by yie12 with SMTP id 12so4782133yie.31 for <ietf@ietf.org>; Mon, 29 Aug 2011 20:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=FF7QB7T9TvRhZgjUQxvZDBNRckTF1P5nFEYQCllexoc=; b=aoRW0mmVfJJaSwQnHJQc8SB1oWYaOx0BbyrM5txrLhvvVPfOumwbg5XxTIUunbsmaZ aO33ipjCjHQcTPnDKzPzIFjsMDLeNSdvXIcgdy2QyPXeIqCEJZTDA5XagCCDwTAkhpsw uku7YLgr2F3K/INIT7Di9yszucxO15Lki8X24=
MIME-Version: 1.0
Received: by 10.236.153.98 with SMTP id e62mr30361540yhk.40.1314674506230; Mon, 29 Aug 2011 20:21:46 -0700 (PDT)
Received: by 10.147.35.10 with HTTP; Mon, 29 Aug 2011 20:21:46 -0700 (PDT)
In-Reply-To: <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
Date: Mon, 29 Aug 2011 23:21:46 -0400
Message-ID: <CAEa=Q_XK-DZxyU0D3VFBaBRB3i9dn=RVDrduriY=o-kyXh=WTw@mail.gmail.com>
Subject: Re: 2119bis
From: HLS <sant9442@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 03:28:50 -0000

+1

I believe the issue is the subtle differences between:

    SHOULD for something new, i.e. no dependency
    SHOULD for something old, i.e. an enhancement or new dependency
the engineer is trying to push hard.

As much as we want to isolate protocols, in practice,  we are
integrating many protocols and in theory, it should all work. I
believe it has for the most part.  But increasingly a protocol upgrade
or new protocol here requires a "MUST USAGE" dependency of another
otherwise optional protocol there.  I believe that is what we are
seeing with this new interpretation.

New protocol X works better if existing optional (and much older)
protocol Y is applied as a SHOULD. It would like to say MUST but it
can't because Y is already optional and not required.   This new
interpretation will make software implementing X non-compliant if it
also doesn't support Y.

---
HLS
On Mon, Aug 29, 2011 at 10:44 PM, Eric Burger
<eburger@standardstrack.com> wrote:
> Yes, and...
>
> I would offer that for most cases, If Y then MUST X or If Z then MUST NOT=
 X *are* what people usually mean when they say SHOULD. =C2=A0In the spirit=
 of Say What You Mean, a bare SHOULD at the very least raise an ID-nit, sug=
gesting to the author to turn the statement into the if Y then MUST X or if=
 Z then MUST NOT X form. =C2=A0Being pedantic and pedagogic:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0SHOULD send a 1 UNLESS you receive a 0
> really means
> =C2=A0 =C2=A0 =C2=A0 =C2=A0UNLESS you receive a 0, one MUST send a 1.
>
> My vision of the UNLESS clause is not necessarily a protocol state, but a=
n environment state. =C2=A0These are things that I can see fit the SHOULD/U=
NLESS form:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0SHOULD send a 1 UNLESS you are in a walled gar=
den
> =C2=A0 =C2=A0 =C2=A0 =C2=A0SHOULD flip bit 27 UNLESS you have a disk
> =C2=A0 =C2=A0 =C2=A0 =C2=A0SHOULD NOT explode UNLESS you are a bomb
> are all reasonable SHOULD-level statements.
>
> I would offer that ANY construction of SHOULD without an UNLESS is a MAY.=
 =C2=A0Unless of course one considers us the Protocol Nanny's(tm) - if do n=
ot do a SHOULD, we will send you to bed without your treacle! I.e., there I=
S NO DISTINCTION BETWEEN A BARE SHOULD AND A MAY.
>
> On Aug 29, 2011, at 9:47 PM, ned+ietf@mauve.mrochek.com wrote:
>
>>> Hi -
>>
>>>> From: "Eric Burger" <eburger-l@standardstrack.com>
>>>> To: "Narten Thomas" <narten@us.ibm.com>; "Saint-Andre Peter" <stpeter@=
stpeter.im>
>>>> Cc: "IETF discussion list" <ietf@ietf.org>
>>>> Sent: Monday, August 29, 2011 3:08 PM
>>>> Subject: Re: 2119bis
>>>>
>>>> I would assume in the text of the document. =C2=A0This paragraph is si=
mply an enumeration of Burger's Axiom:
>>>> For every SHOULD, there must be an UNLESS, otherwise the SHOULD is a M=
AY.
>>
>>> I disagree.
>>
>> I concur with your disagreement. SHOULD should *not* be used when the
>> list of exceptions is known and practically enumerable.
>>
>>> If the "UNLESS" cases can be fully enumerated, then
>>> "SHOULD x UNLESS y" is equivalent to "WHEN NOT y MUST X."
>>> (Both beg the question of whether we would need to spell out that
>>> "WHEN y MUST NOT X" is not necessarily an appropriate inference.)
>>
>>> RFC 2119 SHOULD is appropriate when the "UNLESS" cases are
>>> known (or suspected) to exist, but it is not practical to exhaustively
>>> identify them all.
>>
>>> Let's not gild this lily.
>>
>> +1
>>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ned
>> _______________________________________________
>> 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
hls

From sant9442@gmail.com  Mon Aug 29 20:40:11 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 848C121F8ABE for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 20:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FdY33vHGD9mm for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 20:40:11 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA1C21F8AB9 for <ietf@ietf.org>; Mon, 29 Aug 2011 20:40:10 -0700 (PDT)
Received: by gxk19 with SMTP id 19so6237733gxk.31 for <ietf@ietf.org>; Mon, 29 Aug 2011 20:40:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8xTMYDEcuF0iQo5Avt8sefgl0BKarq2wF8oXAe8EJeQ=; b=FQnmJz8RqiZScHO05S0DNTpwjLb+w5rX8XduITaFN7VBsMKFL9MF+yv9PGZQfs2Wwn psRIU7/PG3bDe++20y/uB/46fR9ybAJwZcHtgbaBt7Q9m+VGVhIv6VpHIZsLbGGGE0ko /ehJZ4BMqQJ84cKEHcyaFBvxDYtfUXRun3thg=
MIME-Version: 1.0
Received: by 10.147.16.28 with SMTP id t28mr4613528yai.37.1314675649702; Mon, 29 Aug 2011 20:40:49 -0700 (PDT)
Received: by 10.147.35.10 with HTTP; Mon, 29 Aug 2011 20:40:49 -0700 (PDT)
In-Reply-To: <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>
Date: Mon, 29 Aug 2011 23:40:49 -0400
Message-ID: <CAEa=Q_U5LZSm00BdKh_CzzreRKywyF44a-uBmeaxvh5QuK==2Q@mail.gmail.com>
Subject: Re: 2119bis
From: HLS <sant9442@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 03:40:11 -0000

On Mon, Aug 29, 2011 at 11:11 PM, Keith Moore
<moore@network-heretics.com> wrote:
> On Aug 29, 2011, at 10:44 PM, Eric Burger wrote:
>
>> I would offer that ANY construction of SHOULD without an UNLESS is a MAY.
>
> The essential beauty of SHOULD is that it gets specification writers and
> working groups out of the all-too-common rathole of trying to anticipate and
> nail down every exceptional case.
> Keith

+1,  and thats the problem with this new interpretation and its
unwritten form has already been used in a WG to label a group
participants as 2119 illiterates and any software that has implemented
a SHOULD as already non-compliant.

-- 
hls

From msk@cloudmark.com  Mon Aug 29 21:32:55 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A126021F863E for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 21:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.043
X-Spam-Level: 
X-Spam-Status: No, score=-103.043 tagged_above=-999 required=5 tests=[AWL=-0.444, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KOfzsHWun18E for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 21:32:55 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDDB21F8634 for <ietf@ietf.org>; Mon, 29 Aug 2011 21:32:55 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Mon, 29 Aug 2011 21:34:21 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Mon, 29 Aug 2011 21:34:20 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxmqPH9GKyL/QJwR4uvBXbFOkAIYgAJI02g
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net>
In-Reply-To: <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 04:32:55 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of M=
ark Nottingham
> Sent: Monday, August 29, 2011 5:08 PM
> To: Peter Saint-Andre
> Cc: IETF discussion list
> Subject: Re: 2119bis
>=20
> Thanks for starting this, Peter. A few comments / topics for
> discussion:
>=20
> 1) I agree that the "SHOULD... UNLESS" pattern ought be documented.

I had never thought of this before.  I kind of like the idea, especially si=
nce SHOULD has always meant "MUST unless you really know what you're doing"=
 but that last bit, though strong, is still pretty subjective.  Having a to=
ol to make it more explicit is a nice idea.

> 2) I strongly believe that authors should be encouraged to enumerate
> the potential subjects of conformance terms, and to use them in every
> instance.
>=20
> For example, a requirement like this:
>=20
> """The Foo header MUST contain the "bar" directive"""
>=20
> is ambiguous; it doesn't specify who has to do what. Rather,
>=20
> """Senders MUST include the "bar" directive when producing the Foo
> header; recipients that receive a Foo header without a "bar" directive
> MUST ..."""
>=20
> is unambiguous (assuming that the spec defines the terms "sender" and
> "recipient").

...or at least say at the bottom of such a collection that fields/messages/=
pages/whatever that don't conform MUST be (default treatment here).

> 4) WRT to the status of the document -- if people really feel that we
> don't need to revise 2119, I'd define this as a superset of 2119 and
> NOT obsolete it; i.e., have documents opt into it. However, I'd hope
> that we can get consensus that it's time to build on what 2119 offers.

I don't see a big deal with rendering RFC2119 obsolete.  Or perhaps more ac=
curately, I don't like the argument that we can't just because lots of outs=
ide SDOs reference it, or any similarly useful BCP we use could become set-=
in-stone as soon as others decide they like it.  We have a mechanism for ch=
ecking whether a given RFC has been replaced or not; we all have to learn t=
o use it, so I think others should as well.

From henk.uijterwaal@gmail.com  Tue Aug 30 00:21:38 2011
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A6A21F8B1F for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 00:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.425
X-Spam-Level: 
X-Spam-Status: No, score=-3.425 tagged_above=-999 required=5 tests=[AWL=0.174,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DxRTde7f20Nj for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 00:21:37 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 134DF21F8B1C for <ietf@ietf.org>; Tue, 30 Aug 2011 00:21:33 -0700 (PDT)
Received: by ewy19 with SMTP id 19so2823869ewy.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 00:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=1eLowHa49JK8/MVt0+42ArkQ+hZsdQN22xP51HOg+cQ=; b=naQk/9ZwaR0zeDRKLVNJh+aH9CxpqtQgMAhbfUwxS51KPKbDCYfd5N/xYt6Xhqtobk wK6R3DPyK92/FHiXe8TofeUZIP8Xe2aHh8JcFgwE112xSBelpOn3TWjONlcRqYxoEJ3E wPqnmeYnzngwhHN9qoOefuQA9zCrivrpB0YwM=
Received: by 10.213.113.212 with SMTP id b20mr856631ebq.71.1314688979505; Tue, 30 Aug 2011 00:22:59 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl [82.95.178.49]) by mx.google.com with ESMTPS id v2sm3282359eej.34.2011.08.30.00.22.58 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 00:22:58 -0700 (PDT)
Message-ID: <4E5C8FD1.4010306@gmail.com>
Date: Tue, 30 Aug 2011 09:22:57 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: voting system for future venues?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com> <4E5BB521.3010800@dcrocker.net>
In-Reply-To: <4E5BB521.3010800@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 07:21:38 -0000

Dave,

> On 8/29/2011 8:01 AM, Henk Uijterwaal wrote:
>> If we want more flexibility in order to find better hotel deals, then we have
>> to do something like: dates are fixed approximately 1.5 years out, and we do
>> not mind having meetings back-to-back with other organizations on the clash
>> list.

> As we have been told for many years and experienced directly, hotel schedules
> become crowded 2-3 years ahead of time.  That means we must fix our dates
> farther ahead than we have been doing.  1.5 years essentially guarantees our
> having very limited choice.

Yes, I agree.  My point was the change that was proposed.  Currently the
algorithm is something like:

 T-6 years:    Announce date of meeting
 T-3 years:    Start finding a hotel
 T-2 years:    Select hotel
 T-1.5 years:  Announce venue to community.

Obvious advantage of this model is that all other organizations know when we
will meet and clashes are minimal.  Also, people who asked for early
announcements of meeting dates, get what they want.

If we change to a model where we are more flexible in order to find the best
hotel deal, this becomes something like:

 T-6 years   Announce that we have meeting in say March/July/November
 T-3 years   Start finding a hotel for that month.
 T-2 years   Select hotel and set exact meeting dates.
 T-1.5 years Announce to community.

That is a 4.5 year difference in when the exact date is announced.  This
increase the risk that there is a clash with another meeting and people
cannot plan much in advance.

The question is what we, as a community, want: dates known early or
flexibility to select the best venue at a late stage.

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From Martin.Thomson@commscope.com  Tue Aug 30 00:22:16 2011
Return-Path: <Martin.Thomson@commscope.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1948D21F8B2B for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 00:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level: 
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N5xtiHchYMdF for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 00:22:14 -0700 (PDT)
Received: from cdcsmgw02.commscope.com (fw.commscope.com [198.135.207.129]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACF921F8B3B for <ietf@ietf.org>; Tue, 30 Aug 2011 00:21:55 -0700 (PDT)
X-AuditID: 0a0404e9-b7cd4ae000004b3f-2e-4e5c8fe9aa56
Received: from ACDCE7HC2.commscope.com ( [10.86.20.103]) by cdcsmgw02.commscope.com (Symantec Brightmail Gateway) with SMTP id 82.2E.19263.9EF8C5E4; Tue, 30 Aug 2011 02:23:22 -0500 (CDT)
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.3.159.2; Tue, 30 Aug 2011 02:23:21 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Tue, 30 Aug 2011 15:23:17 +0800
From: "Thomson, Martin" <Martin.Thomson@commscope.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, IETF discussion list <ietf@ietf.org>
Date: Tue, 30 Aug 2011 15:23:35 +0800
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: Acxmk9PTqhoOPEFrSOmiurnysGThOAAT+g4Q
Message-ID: <8B0A9FCBB9832F43971E38010638454F040F1C12B5@SISPE7MB1.commscope.com>
References: <4E5C067A.9080400@stpeter.im>
In-Reply-To: <4E5C067A.9080400@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 07:22:16 -0000

On 2011-08-30 at 07:36:58, Peter Saint-Andre wrote:
> for long enough, I finally decided to submit an I-D that is intended=20
> to obsolete RFC 2119.=20

<bike-shed>
IS THERE ANY CHANCE OF AGREEING THAT SHOUTING IS BAD?  (i.e., Burger's firs=
t anti-law.)  As opposed to mandating that requirements ought to be shouted=
.  Lowercase "must" can be as effective as uppercase as long as it is consi=
stently applied.
</bike-shed>

On a more serious note, many documents lean too heavily on conformance term=
s.

A gentle reminder that conformance terms ought to be sparingly used might n=
ot go astray here.  It's just like the F-bomb, it's a F-ing big deal if use=
d infrequently enough.  People are more likely to pay attention when it's r=
are.

--Martin

From sant9442@gmail.com  Tue Aug 30 00:58:46 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 840E321F8B9A for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 00:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0oulbQaOxwIF for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 00:58:46 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0595421F8B98 for <ietf@ietf.org>; Tue, 30 Aug 2011 00:58:45 -0700 (PDT)
Received: by gxk19 with SMTP id 19so6356972gxk.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 01:00:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8I0DBkA9ICLFGQZwhO5uaLvFNHRQsbwTIvEOFHMDznc=; b=cF15meF340cJBFdQm0hfFVMMXL4mYa1Gpet2DHCt3vcJmgeefRuOhQpXH81k2rcJon 67BOYQLlS1cut+SFc1diC8+/IpcnH9cZkKv7zT3ZEjkGDfEPfeNLy3veQtUdZPOXAS25 n1LxH4eATmK2/Ml6HRSd4MET6shgLpMoKObC4=
MIME-Version: 1.0
Received: by 10.147.16.28 with SMTP id t28mr4799218yai.37.1314691212558; Tue, 30 Aug 2011 01:00:12 -0700 (PDT)
Received: by 10.147.35.10 with HTTP; Tue, 30 Aug 2011 01:00:12 -0700 (PDT)
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net> <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com>
Date: Tue, 30 Aug 2011 04:00:12 -0400
Message-ID: <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com>
Subject: Re: 2119bis
From: HLS <sant9442@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 07:58:46 -0000

On 8/30/11, Murray S. Kucherawy <msk@cloudmark.com> wrote:

>> Mark Nottingham:
>> 1) I agree that the "SHOULD... UNLESS" pattern ought be documented.

> I had never thought of this before.  I kind of like the idea, especially since SHOULD
> has always meant "MUST unless you really know what you're doing"

Such an odd reading.  Does it mean you MUST because you could not
handle it otherwise?

It takes two to tango.  One side reasons can be different than the
other. If a software breaks down because it read SHOULD as a MUST and
expected the other end will also view is a MUST, then it didn't know
what it was doing.  Things break down. Implementors on either side
can't depend on it and need to function in lieu of it. There is always
the possibility one decided "Nahhhh, not needed, not worth the cost.
Its not required." etc, and no one should die because of that
decision.

I think it MUST be noted that a Minimum Implementation for a protocol
is all anyone can expect. If a SHOULD item is among the listed minimum
requirements, it MUST be removed from the list or changed to a MUST.

Maybe the term Minimum Implementation (is part of, is not part of) can
be incorporated into each of the key word text.

-- 
hls

From lear@cisco.com  Tue Aug 30 01:04:50 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E66E321F8BB2 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 01:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.606
X-Spam-Level: 
X-Spam-Status: No, score=-110.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b1KRzUSFt7L8 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 01:04:50 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEC421F8BAE for <ietf@ietf.org>; Tue, 30 Aug 2011 01:04:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=1000; q=dns/txt; s=iport; t=1314691577; x=1315901177; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=DRKxnQEZdiXsgry5h9Dt+7HimgaPjE/xErBz/Y7iH4Q=; b=mmDAAFSwtPH2qsAjrybYQfSCm/16giFdPKg/IoOEv/c3ewegX3oh6mYf TiqtsCR+F0NRiYb3Vn0FbyWZz4pBqbW524bYnPXqHVeUjoVnBy88Kp82k HlaaFdOfbp5YHMy+5qsM7qtm2GbX0cyqeMT+nbirmIVwInexD56me7Ut5 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAKKYXE6Q/khR/2dsb2JhbAAoGoRMo0N3gUABAQEBAgESARBVAQULCxgCAgUWCwICCQMCAQIBRQYNAQcBAR6HUAQjlwEBjTaSGIEshBCBEQSTJJEHaQ
X-IronPort-AV: E=Sophos;i="4.68,301,1312156800"; d="scan'208";a="52516134"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 30 Aug 2011 08:06:13 +0000
Received: from dhcp-10-55-87-154.cisco.com (dhcp-10-55-87-154.cisco.com [10.55.87.154]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7U85nW9004484; Tue, 30 Aug 2011 10:05:49 +0200
Message-ID: <4E5C99BE.4040105@cisco.com>
Date: Tue, 30 Aug 2011 10:05:18 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im> <CAHhFybrSSNa-hmrCJ5gmG0-9CUZpvPhaTHP3sjMUgq4aXLtReA@mail.gmail.com>
In-Reply-To: <CAHhFybrSSNa-hmrCJ5gmG0-9CUZpvPhaTHP3sjMUgq4aXLtReA@mail.gmail.com>
X-Enigmail-Version: 1.3.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 08:04:51 -0000

Frank,


On 8/30/11 12:15 AM, Frank Ellermann wrote:
> On 29 August 2011 23:36, Peter Saint-Andre wrote:
>
>> staring at http://www.rfc-editor.org/errata_search.php?eid=499 for
>> long enough, I finally decided to submit an I-D that is intended to
>> obsolete RFC 2119.
> There are literally thousands of documents (not only RFCs, also W3C
> standards, etc.) with normative references to RFC 2119 (sic!) instead
> of BCP 14, and I see no compelling reason to render these references
> as "historic".

On the basis of this logic we wouldn't be able to supercede any of our
key RFCs.

> [...]

> How about trying an "updates 2119" and status BCP, where BCP 14 then
> consists of 2119 and 2119bis, and old RFC 2119 references are still
> okay "as is".

What ends up happening, then, is that we need Internet lawyers to
traipse through references.  I challenge you or anyone else here to list
all the process RFCs that update RFC 2026.  Let's not repeat that fiasco
with 2119.



From evnikita2@gmail.com  Tue Aug 30 02:12:05 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0ACB21F8BC4 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 02:12:05 -0700 (PDT)
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.134,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTY5IyspKHWw for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 02:12:05 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id C679921F8BBF for <ietf@ietf.org>; Tue, 30 Aug 2011 02:12:04 -0700 (PDT)
Received: by bkar4 with SMTP id r4so5867775bka.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 02:13:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Monc0CnzfRn2nWNfbYUajbFXveeIIAGsD+Hn3pdDe4I=; b=Vp1cBvs3PoFfqmbJHTV7i16K9HMxxYM/UisDgnoboxyBnZAHc6TQtfRPsKk/6dbMhP CV6RIpDwXfmrpLVNBJe65jdDF9M5YU4kcHHDm+7bFkZ28QwVX6fPyNn4f/I4+plQYaKw Oj6MjeYvOe5ZyHqBkBn7r2bbK/Nc8JtefBjeM=
Received: by 10.204.152.139 with SMTP id g11mr2823700bkw.3.1314695611034; Tue, 30 Aug 2011 02:13:31 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id o20sm794684bku.43.2011.08.30.02.13.29 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 02:13:30 -0700 (PDT)
Message-ID: <4E5CA9DA.2030205@gmail.com>
Date: Tue, 30 Aug 2011 12:14:02 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im> <CAHhFybrSSNa-hmrCJ5gmG0-9CUZpvPhaTHP3sjMUgq4aXLtReA@mail.gmail.com>
In-Reply-To: <CAHhFybrSSNa-hmrCJ5gmG0-9CUZpvPhaTHP3sjMUgq4aXLtReA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 09:12:06 -0000

Frank,

2119bis is going to replace RFC 2119, and "Obsoletes: 2119" header is 
fine here.  "Updates:" header means that some changes are made, and 
these specific changes are clearly indicated; 2119bis imports all the 
content of 2119 plus adding own changes, and is a significant update of 
2119, so "Updates: 2119" is inappropriate (sorry for pun).

I would rather object to making RFC 2119 Historic; I remember RFC 2026 
discusses such case (probably Section 6.3, which is also applicable to 
BCPs).  So, the following change is necessary:

Abstract and Introduction (similar text).  OLD: "If approved, this 
document obsoletes RFC 2119 and changes its status to Historic."; NEW: 
"This document obsoletes RFC 2119."

Mykyta Yevstifeyev

30.08.2011 1:15, Frank Ellermann wrote:
> On 29 August 2011 23:36, Peter Saint-Andre wrote:
>
>> staring at http://www.rfc-editor.org/errata_search.php?eid=499 for
>> long enough, I finally decided to submit an I-D that is intended to
>> obsolete RFC 2119.
> There are literally thousands of documents (not only RFCs, also W3C
> standards, etc.) with normative references to RFC 2119 (sic!) instead
> of BCP 14, and I see no compelling reason to render these references
> as "historic".
>
> For starters simply confirm the erratum, I don't see why that caused
> you headaches.
>
> IMO it is not necessary (but allowed) to import any BCP 14 terms not
> actually used in a document, i.e., I disagree with section 4 in your
> draft.
>
> How about trying an "updates 2119" and status BCP, where BCP 14 then
> consists of 2119 and 2119bis, and old RFC 2119 references are still
> okay "as is".
>
> Readers with difficulties to figure out what RFC 2119 meant might
> find the confirmed erratum and the "updated by 2119bis" with better
> answers.  Authors could use RFC 2119, 2119bis, or even BCP 14 in
> the references of new documents, where "BCP 14" would be new, IIRC
> RFC 2119 did not permit this -- fearing precisely what is happening
> now, somebody trying to update critical terms.  I think that your
> new definitions match precisely what RFC 2119 wanted, but I'm also
> almost sure that some old "2119 clients" will disagree.
>
> -Frank
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From evnikita2@gmail.com  Tue Aug 30 02:27:14 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2EAA21F8B7E for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 02:27:14 -0700 (PDT)
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.133,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iu6Bd6N-7tyu for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 02:27:13 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8549521F8B75 for <ietf@ietf.org>; Tue, 30 Aug 2011 02:27:13 -0700 (PDT)
Received: by bkar4 with SMTP id r4so5885065bka.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 02:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=l/a5FQ/Yjylbx2DhtfAIXgttJIC2A/28pKtMYd90DFQ=; b=xTnWumbKbjU+c+Ig335j47i2lNtiJmtQIHhdyMDUjJqrk8yfvuJufmak4laNnYvcf7 FiuuooKn3JYxLDxis7SE+Po3PavGQhLail6PxxNwmQWNDfv6Wzl9eEeZuHJ/t/K+dUNo y2j8VVjOVzhqjgjKCvdlWgENy8vetHiRlSWao=
Received: by 10.204.149.15 with SMTP id r15mr2648771bkv.279.1314696519650; Tue, 30 Aug 2011 02:28:39 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id 14sm1450216bkd.25.2011.08.30.02.28.38 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 02:28:39 -0700 (PDT)
Message-ID: <4E5CAD66.50708@gmail.com>
Date: Tue, 30 Aug 2011 12:29:10 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net>
In-Reply-To: <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 09:27:15 -0000

30.08.2011 3:08, Mark Nottingham wrote:
> Thanks for starting this, Peter. A few comments / topics for discussion:
>
> 1) I agree that the "SHOULD... UNLESS" pattern ought be documented.

I think 2119bis should discuss use of the keywords in conditional 
clauses, how to interpret something like "<a> MUST be set to <b> if <c> 
is <d>", or "<a> SHOULD be <b> if <c> and SHOULD be <d> if <e>" etc.  
Defining the "<keyword> ... IF"/"<keyword> ... UNLESS" constructions for 
all of them?

>
>
> 2) I strongly believe that authors should be encouraged to enumerate the potential subjects of conformance terms, and to use them in every instance.
>
> For example, a requirement like this:
>
> """The Foo header MUST contain the "bar" directive"""
>
> is ambiguous; it doesn't specify who has to do what. Rather,
>
> """Senders MUST include the "bar" directive when producing the Foo header; recipients that receive a Foo header without a "bar" directive MUST ..."""
>
> is unambiguous (assuming that the spec defines the terms "sender" and "recipient").

+1.

>
>
> 3) It may be worth further cautioning against over-use of MAY; this is the most-abused term, IME. Perhaps encouraging people to make requirements testable on the wire would help.

My personal observation is that MAY is often used in sense of "can", 
i.e. to designate possibility rather than optionality.  So 2119bis 
should be clear that MAY is used for describing discretionary 
actions/behavior, and those authors who wish to denote "possible action" 
should use "can", which shouldn't be included in the repertoire as being 
irrelevant to conformance.

>
>
> 4) WRT to the status of the document -- if people really feel that we don't need to revise 2119, I'd define this as a superset of 2119 and NOT obsolete it; i.e., have documents opt into it. However, I'd hope that we can get consensus that it's time to build on what 2119 offers.

See my previous message.

Mykyta Yevstifeyev

>
> Cheers,
>
>
>
> On 30/08/2011, at 7:36 AM, Peter Saint-Andre wrote:
>
>> After staring at http://www.rfc-editor.org/errata_search.php?eid=499 for
>> long enough, I finally decided to submit an I-D that is intended to
>> obsolete RFC 2119. I hope that I've been able to update and clarify the
>> text in a way that is respectful of the original. Feedback is welcome.
>>
>> http://www.ietf.org/id/draft-saintandre-2119bis-01.txt
>>
>> Peter
>>
>> -- 
>> Peter Saint-Andre
>> https://stpeter.im/
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From iljitsch@muada.com  Tue Aug 30 03:03:41 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94C1321F8B9E for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 03:03:41 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTupc-YYLZ3a for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 03:03:41 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id DD70421F8AEA for <ietf@ietf.org>; Tue, 30 Aug 2011 03:03:40 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:21b:63ff:fe95:7d9b] ([IPv6:2001:720:410:100f:21b:63ff:fe95:7d9b]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p7UA4rng041549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 30 Aug 2011 12:04:54 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: voting system for future venues?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4E5C8FD1.4010306@gmail.com>
Date: Tue, 30 Aug 2011 12:04:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1AECBC82-4F01-4722-B0A3-E6132F01DC99@muada.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com> <4E5BB521.3010800@dcrocker.net> <4E5! C8FD1.4010306@gmail.com>
To: henk@uijterwaal.nl
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 10:03:41 -0000

On 30 aug 2011, at 9:22, Henk Uijterwaal wrote:

> That is a 4.5 year difference in when the exact date is announced.  =
This
> increase the risk that there is a clash with another meeting and =
people
> cannot plan much in advance.

Come on, the idea that people need to know the date of a meeting more =
than 1.5 years out or they won't be able to plan their attendance is =
ridiculous. I don't even know which country I'll be living in 1.5 years =
from now.

You also only look at the situation where the dates are completely open =
until after the venue negotiations are complete. I don't think we need =
to go that far, we could start by selecting two weeks long in advance =
and then choosing between those as the negotiations happen. This could =
be especially useful for a meeting in a region where more contraints =
than usual are expected.

> The question is what we, as a community, want: dates known early or
> flexibility to select the best venue at a late stage.

I can only speak for myself, but $300/night is a big problem for me. I =
have no problem staying in non-official hotels, but obviously that only =
works when those are available and have more reasonable prices.

Then again, I don't need to go to _every_ IETF meeting (I think I'm at =
12 meetings in 9 years now) so I'm ok having a mix of cheaper and more =
expensive meetings.=

From vesely@tana.it  Tue Aug 30 04:08:43 2011
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA6021F8C32 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 04:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.629
X-Spam-Level: 
X-Spam-Status: No, score=-4.629 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k3zrZgUNOqyi for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 04:08:42 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id E74EC21F8C31 for <ietf@ietf.org>; Tue, 30 Aug 2011 04:08:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1314702605; bh=ECwhnot0HT5JGCmh/EXgWh/1D6C811C3I1MKb3vqvXs=; l=841; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=eJi3XTduBOcDkGTO07CpN65xw7kuCSyIbSGKzUAOQ4UoymSh3R09XAenxW4jt1dG5 W383ltfL+TljTmiG9eLDwoEQmManvzDaOKrdNC6JY35Qj4bYQGwvmuowhNbBhvJIoo ZErl3ybEtDKV1UhLvzTED69loE6CLFoSlRzf+tK0=
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, 30 Aug 2011 13:10:05 +0200 id 00000000005DC039.000000004E5CC50D.00005534
Message-ID: <4E5CC50D.2080303@tana.it>
Date: Tue, 30 Aug 2011 13:10:05 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Routing at the Edges of the Internet
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com><CD5674C3CD99574EBA7432465FC13C1B222B1F5861@DC-US1MBEX4.global.avaya.com><Pine.LNX.4.64.1108260902450.21086@egate.xpasc.com>, <4E5806EC.5050304@dougbarton.us><CD5674C3CD99574EBA7432465FC13C1B222B1F5864@DC-US1MBEX4.global.avaya.com>, <392CB277BC2EAE4FB83C1206954BA6CEF6AE@newserver.arneill-py.local>	<CD5674C3CD99574EBA7432465FC13C1B222B1F5868@DC-US1MBEX4.global.avaya.com> <392CB277BC2EAE4FB83C1206954BA6CEF6B6@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF6B6@newserver.arneill-py.local>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 11:08:43 -0000

On 30/Aug/11 04:50, Michel Py wrote:
> 
> The mechanism (ICMP redirects) is technically fine and socially not.
> People have become paranoid and now they firewall everything. It is a
> behavioral animal. I'm not saying it's a good idea; the market answer to
> crossing firewalls is to encapsulate everything into HTTPS, which is
> probably worse. But then again, we have to deal with market pressure
> against technically sound solutions, and the market almost always wins.

That brings us back to the problem that "free routing" is apparently
insecure.  OTOH, there are large expectations from RIRs and network
providers, about security and policy routing, especially on port 25.
On closer inspection, though, those chaps don't seem to be eager to
play net-cops.

Should we go for secure routing, now that we have secure DNS?


From brian.e.carpenter@gmail.com  Tue Aug 30 05:10:14 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4FD21F8C33 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 05:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9fji0AuHGjnY for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 05:10:13 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id A8DF121F8C31 for <ietf@ietf.org>; Tue, 30 Aug 2011 05:10:13 -0700 (PDT)
Received: by gyf3 with SMTP id 3so6540322gyf.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 05:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=azWTN/hCo2u1SidzcMYeGa1X+GlyunvI7GVzfgATSmE=; b=s6FHrET/G20r8TohcQS5o6lHuprCPhhka3xmenfzbpHM9gNTKeUqcQ15nYzzwqK7ji mLzyneHSn8vs7MUbebDX62MDUy/TCe4VV+9yybzu2hUX60FYKshZY3YTZcysc4vJFXfg tMfq99ady9pD2Ogfh6pmmK5iZ8dbGVnotQRrs=
Received: by 10.142.202.19 with SMTP id z19mr3007553wff.68.1314706267163; Tue, 30 Aug 2011 05:11:07 -0700 (PDT)
Received: from [202.106.79.19] ([202.106.79.19]) by mx.google.com with ESMTPS id z12sm2746208wfn.11.2011.08.30.05.11.04 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 05:11:06 -0700 (PDT)
Message-ID: <4E5CD350.4050108@gmail.com>
Date: Wed, 31 Aug 2011 00:10:56 +1200
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: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Scheduling years in advance [Re: voting system for future venues?]
References: <20110822191708.652C721F8C19@ietfa.amsl.com>	<66998320DD3FCC5628E32634@PST.JCK.COM>	<F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org>	<CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com>	<E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com>	<4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu>	<4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu>	<1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net>	<15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com>	<4E55E827.4060802@gmail.com>	<13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com>	<CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com>	<FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com>	<458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com>	<4E5BA9AD.7050908@gmail.com> <4E5BB521.3010800@dcrocker.net> <4E5!	C8FD1.4010306@gmail.com> <1AECBC82-4F01-4722-B0A3-E6132F01DC99@muada.com>
In-Reply-To: <1AECBC82-4F01-4722-B0A3-E6132F01DC99@muada.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: henk@uijterwaal.nl, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 12:10:14 -0000

On 2011-08-30 22:04, Iljitsch van Beijnum wrote:
> On 30 aug 2011, at 9:22, Henk Uijterwaal wrote:
> 
>> That is a 4.5 year difference in when the exact date is announced.  This
>> increase the risk that there is a clash with another meeting and people
>> cannot plan much in advance.
> 
> Come on, the idea that people need to know the date of a meeting more than 1.5 years out or they won't be able to plan their attendance is ridiculous. I don't even know which country I'll be living in 1.5 years from now.

That isn't the point. It's to avoid clashes with IEEE, ITU-T, W3C and numerous
others standards bodies that have overlapping participants. There were constant
problems in the past, until we went to the current advance scheduling.

    Brian

From narten@us.ibm.com  Tue Aug 30 05:32:21 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1290521F8B82 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 05:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94RYImzz7vtY for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 05:32:20 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id 9786D21F8B7A for <ietf@ietf.org>; Tue, 30 Aug 2011 05:32:20 -0700 (PDT)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e36.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7UCR5Ya029748 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:27:05 -0600
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7UCXWus095414 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:33:35 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7UCXWPe015311 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:33:32 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-48-40-225.mts.ibm.com [9.48.40.225]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7UCXUKt015277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Aug 2011 06:33:31 -0600
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7UCXT3o010788; Tue, 30 Aug 2011 08:33:30 -0400
Message-Id: <201108301233.p7UCXT3o010788@cichlid.raleigh.ibm.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Scheduling years in advance [Re: voting system for future venues?]
In-reply-to: <4E5CD350.4050108@gmail.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com> <4E5BB521.3010800@dcrocker.net> <4E5! C8FD1.4010306@gmail.com> <1AECBC82-4F01-4722-B0A3-E6132F01DC99@muada.com> <4E5CD350.4050108@gmail! .com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Wed, 31 Aug 2011 00:10:56 +1200."
Date: Tue, 30 Aug 2011 08:33:29 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 12:32:21 -0000

> That isn't the point. It's to avoid clashes with IEEE, ITU-T, W3C
> and numerous others standards bodies that have overlapping
> participants. There were constant problems in the past, until we
> went to the current advance scheduling.

Understood.

But I wonder of we've forgotten the original motivation for this rule
and it has become an unchangable slogan (e.g., "four legs good, two
legs bad")

If, in fact, a date we've chosen turns out to be problematic in terms
of getting a good site, the IAOC should consider (emphasis on
*consider*) whether an alternate date would be better. Of course, such
a change in date should not be done lightly. And it should not be done
with out checking with the specific organizations we try to avoid
clashes with, etc. But to say the dates are fixed and immovable no
matter what seems unhelpful.

At the plenary, I recall it being said that for one of the upcoming
asian meetings, the exact dates were problematical, and alternate
dates would have had better options/rates. When I suggested privately
to the IAOC that they should *consider* changing the date, I got (what
to me) felt like one big knee jerk "we can't change the dates,
period."

Thomas

From marshall.eubanks@gmail.com  Tue Aug 30 05:41:54 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A57221F8B83 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 05:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.173
X-Spam-Level: 
X-Spam-Status: No, score=-103.173 tagged_above=-999 required=5 tests=[AWL=0.425, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSaELUsfKAG0 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 05:41:53 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5841621F8B7E for <ietf@ietf.org>; Tue, 30 Aug 2011 05:41:53 -0700 (PDT)
Received: by gyf3 with SMTP id 3so6569518gyf.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 05:43:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kun5S5EZhEdnOhEBqAXYWyU/sYfeedHzFBMqykEiWEA=; b=G7BoESNNnC0t5JICxXJ96No4sERbUAyaz9yzHbh0khvjR8spkpz713VOQDCkOlQOef fV3KvG1VgRDhJ0UFM3zyoCH/9xhUpzUWNGEwZSbYgfKlanNyvKxakQmGqwKDiSAIoRMJ /sT9Tw0NMn5f41zOxHN2S3Lxlus1upKLHUl9Q=
MIME-Version: 1.0
Received: by 10.150.150.41 with SMTP id x41mr5765723ybd.255.1314708199732; Tue, 30 Aug 2011 05:43:19 -0700 (PDT)
Received: by 10.150.185.9 with HTTP; Tue, 30 Aug 2011 05:43:19 -0700 (PDT)
In-Reply-To: <201108301233.p7UCXT3o010788@cichlid.raleigh.ibm.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <66998320DD3FCC5628E32634@PST.JCK.COM> <F74DDD2D-163A-4CBF-99A5-E452CBB7C17F@isoc.org> <CE8FC485-DA54-491B-B57E-96DA2FE835FC@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0D55796B@PRVPEXVS04.corp.twcable.com> <E9A8F486-2327-4F48-B21A-6155CF334F21@network-heretics.com> <4E554C78.9000504@gmail.com> <tslr54a8v7s.fsf@mit.edu> <4E555B06.6000108@dcrocker.net> <tslmxey8sia.fsf@mit.edu> <1314218041.1973.204.camel@d430> <4E55655C.6030502@bbiw.net> <15F4BD95-8858-4E47-896A-703A472412B1@network-heretics.com> <4E55E827.4060802@gmail.com> <13C2D038-C4C7-4ADE-9E5E-EAB39B94EE3D@cisco.com> <CAJNg7VKBJyR8drxgZvM7om66p8r0x++dL=uGkS-K=bJQ+Oe4wQ@mail.gmail.com> <FF9C30FD-0C3E-4175-9383-6049A8AC7987@muada.com> <458AD1BF-0EFA-4209-890C-92200B839EC4@network-heretics.com> <4E5BA9AD.7050908@gmail.com> <4E5BB521.3010800@dcrocker.net> <1AECBC82-4F01-4722-B0A3-E6132F01DC99@muada.com> <4E5CD350.4050108@gmail.com> <201108301233.p7UCXT3o010788@cichlid.raleigh.ibm.com>
Date: Tue, 30 Aug 2011 08:43:19 -0400
Message-ID: <CAJNg7VJ5uEk6_GgUD5sUrczY=Vxma5oTKdAyWRh-hesUxV7DmQ@mail.gmail.com>
Subject: Re: Scheduling years in advance [Re: voting system for future venues?]
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: multipart/alternative; boundary=000e0cd70c923a775004abb85b77
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 12:41:54 -0000

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

On Tue, Aug 30, 2011 at 8:33 AM, Thomas Narten <narten@us.ibm.com> wrote:

> > That isn't the point. It's to avoid clashes with IEEE, ITU-T, W3C
> > and numerous others standards bodies that have overlapping
> > participants. There were constant problems in the past, until we
> > went to the current advance scheduling.
>
> Understood.
>
> But I wonder of we've forgotten the original motivation for this rule
> and it has become an unchangable slogan (e.g., "four legs good, two
> legs bad")
>
> If, in fact, a date we've chosen turns out to be problematic in terms
> of getting a good site, the IAOC should consider (emphasis on
> *consider*) whether an alternate date would be better. Of course, such
> a change in date should not be done lightly. And it should not be done
> with out checking with the specific organizations we try to avoid
> clashes with, etc. But to say the dates are fixed and immovable no
> matter what seems unhelpful.
>
> At the plenary, I recall it being said that for one of the upcoming
> asian meetings, the exact dates were problematical, and alternate
> dates would have had better options/rates. When I suggested privately
> to the IAOC that they should *consider* changing the date, I got (what
> to me) felt like one big knee jerk "we can't change the dates,
> period."
>
>
As we move the meeting scheduling window from 1.5 years out to 3 years, I
think that that is
one of the things we should consider when necessary. Of course, hopefully
that same move will make it less necessary.

Regards
Marshall





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

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

<br><br><div class=3D"gmail_quote">On Tue, Aug 30, 2011 at 8:33 AM, Thomas =
Narten <span dir=3D"ltr">&lt;<a href=3D"mailto:narten@us.ibm.com">narten@us=
.ibm.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">&gt; That isn&#39;t the point. It&#39;s to avoid clashes =
with IEEE, ITU-T, W3C<br>
&gt; and numerous others standards bodies that have overlapping<br>
&gt; participants. There were constant problems in the past, until we<br>
&gt; went to the current advance scheduling.<br>
<br>
</div>Understood.<br>
<br>
But I wonder of we&#39;ve forgotten the original motivation for this rule<b=
r>
and it has become an unchangable slogan (e.g., &quot;four legs good, two<br=
>
legs bad&quot;)<br>
<br>
If, in fact, a date we&#39;ve chosen turns out to be problematic in terms<b=
r>
of getting a good site, the IAOC should consider (emphasis on<br>
*consider*) whether an alternate date would be better. Of course, such<br>
a change in date should not be done lightly. And it should not be done<br>
with out checking with the specific organizations we try to avoid<br>
clashes with, etc. But to say the dates are fixed and immovable no<br>
matter what seems unhelpful.<br>
<br>
At the plenary, I recall it being said that for one of the upcoming<br>
asian meetings, the exact dates were problematical, and alternate<br>
dates would have had better options/rates. When I suggested privately<br>
to the IAOC that they should *consider* changing the date, I got (what<br>
to me) felt like one big knee jerk &quot;we can&#39;t change the dates,<br>
period.&quot;<br>
<font color=3D"#888888"><br></font></blockquote><div><br></div><div>As we m=
ove the meeting scheduling window from 1.5 years out to 3 years, I think th=
at that is</div><div>one of the things we should consider when necessary. O=
f course, hopefully that same move will make it less necessary.=A0</div>
<div><br></div><div>Regards</div><div>Marshall</div><div><br></div><div><br=
></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;"><font c=
olor=3D"#888888">
Thomas<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>

--000e0cd70c923a775004abb85b77--

From marshall.eubanks@gmail.com  Tue Aug 30 06:23:37 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90DAC21F8B50 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.404
X-Spam-Level: 
X-Spam-Status: No, score=-101.404 tagged_above=-999 required=5 tests=[AWL=2.194, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OioOl6hFhJsD for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:23:36 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id B333621F871E for <ietf@ietf.org>; Tue, 30 Aug 2011 06:23:21 -0700 (PDT)
Received: by gwb20 with SMTP id 20so6539371gwb.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:24:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rR3hGSMEaYAXsAzbIZI7TNQIkHdiCwhqYu0NtzosxOs=; b=IJviOUIP8lKQ8AMyYGrNmj3kJEejaCStnJbFHnY/7zFKw8G42/FQ+7JwgFzWY2ikT/ LSTJodTIfCdyc0p4Z0Rdu7QgsMexfn5IeomCCDVcdwd1D5zE2GxO2mNY6kkEAO2w/P1X vl24n5+/+wq9dPwk2XUQZLLfFDeO+kdUo0L/Y=
MIME-Version: 1.0
Received: by 10.150.177.16 with SMTP id z16mr6687768ybe.27.1314710687179; Tue, 30 Aug 2011 06:24:47 -0700 (PDT)
Received: by 10.150.185.9 with HTTP; Tue, 30 Aug 2011 06:24:47 -0700 (PDT)
In-Reply-To: <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
Date: Tue, 30 Aug 2011 09:24:47 -0400
Message-ID: <CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com>
Subject: Re: 2119bis
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/alternative; boundary=000e0cd6a95a7de61d04abb8ef88
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:23:37 -0000

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

Dear Eric;

I support adding the SHOULD ... UNLESS formalism (although maybe it should
be MUST... UNLESS). It would be useful as there will be times where the
UNLESS can be specified and has been given due consideration at the time of
writing. That, however, will not always be the case. (More inline).

On Mon, Aug 29, 2011 at 10:44 PM, Eric Burger <eburger@standardstrack.com>wrote:

> Yes, and...
>
> I would offer that for most cases, If Y then MUST X or If Z then MUST NOT X
> *are* what people usually mean when they say SHOULD.  In the spirit of Say
> What You Mean, a bare SHOULD at the very least raise an ID-nit, suggesting
> to the author to turn the statement into the if Y then MUST X or if Z then
> MUST NOT X form.  Being pedantic and pedagogic:
>        SHOULD send a 1 UNLESS you receive a 0
> really means
>        UNLESS you receive a 0, one MUST send a 1.
>
> My vision of the UNLESS clause is not necessarily a protocol state, but an
> environment state.  These are things that I can see fit the SHOULD/UNLESS
> form:
>        SHOULD send a 1 UNLESS you are in a walled garden
>        SHOULD flip bit 27 UNLESS you have a disk
>        SHOULD NOT explode UNLESS you are a bomb
> are all reasonable SHOULD-level statements.
>

But how about

SHOULD do FOO UNLESS you have given serious consideration as to the
consequences of not doing FOO.

Isn't that really the original intention of SHOULD ?  Do we gain anything if
that is added every time it is used?


> I would offer that ANY construction of SHOULD without an UNLESS is a MAY.


How about this as a counterexample.

In London, you MAY use the tube for transport. Given the weather, you SHOULD
carry an umbrella.

This SHOULD and  MAY convey different things, in a way that I would argue is
useful, and enumerating a list of UNLESSes is not going to be exhaustive.


> Unless of course one considers us the Protocol Nanny's(tm) - if do not do a
> SHOULD, we will send you to bed without your treacle!


Now, now, now. This is the IETF. We use cookies for motivation.

Regards
Marshall


> I.e., there IS NO DISTINCTION BETWEEN A BARE SHOULD AND A MAY.
>
> On Aug 29, 2011, at 9:47 PM, ned+ietf@mauve.mrochek.com wrote:
>
> >> Hi -
> >
> >>> From: "Eric Burger" <eburger-l@standardstrack.com>
> >>> To: "Narten Thomas" <narten@us.ibm.com>; "Saint-Andre Peter" <
> stpeter@stpeter.im>
> >>> Cc: "IETF discussion list" <ietf@ietf.org>
> >>> Sent: Monday, August 29, 2011 3:08 PM
> >>> Subject: Re: 2119bis
> >>>
> >>> I would assume in the text of the document.  This paragraph is simply
> an enumeration of Burger's Axiom:
> >>> For every SHOULD, there must be an UNLESS, otherwise the SHOULD is a
> MAY.
> >
> >> I disagree.
> >
> > I concur with your disagreement. SHOULD should *not* be used when the
> > list of exceptions is known and practically enumerable.
> >
> >> If the "UNLESS" cases can be fully enumerated, then
> >> "SHOULD x UNLESS y" is equivalent to "WHEN NOT y MUST X."
> >> (Both beg the question of whether we would need to spell out that
> >> "WHEN y MUST NOT X" is not necessarily an appropriate inference.)
> >
> >> RFC 2119 SHOULD is appropriate when the "UNLESS" cases are
> >> known (or suspected) to exist, but it is not practical to exhaustively
> >> identify them all.
> >
> >> Let's not gild this lily.
> >
> > +1
> >
> >                               Ned
> > _______________________________________________
> > 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
>
>

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

Dear Eric;<div><br></div><div>I support adding the SHOULD ... UNLESS formal=
ism (although maybe it should be MUST... UNLESS). It would be useful as the=
re will be times where the UNLESS can be specified and has been given due c=
onsideration at the time of writing. That, however, will not always be the =
case. (More inline).<br>
<br><div class=3D"gmail_quote">On Mon, Aug 29, 2011 at 10:44 PM, Eric Burge=
r <span dir=3D"ltr">&lt;<a href=3D"mailto:eburger@standardstrack.com">eburg=
er@standardstrack.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x;">
Yes, and...<br>
<br>
I would offer that for most cases, If Y then MUST X or If Z then MUST NOT X=
 *are* what people usually mean when they say SHOULD. =A0In the spirit of S=
ay What You Mean, a bare SHOULD at the very least raise an ID-nit, suggesti=
ng to the author to turn the statement into the if Y then MUST X or if Z th=
en MUST NOT X form. =A0Being pedantic and pedagogic:<br>

 =A0 =A0 =A0 =A0SHOULD send a 1 UNLESS you receive a 0<br>
really means<br>
 =A0 =A0 =A0 =A0UNLESS you receive a 0, one MUST send a 1.<br>
<br>
My vision of the UNLESS clause is not necessarily a protocol state, but an =
environment state. =A0These are things that I can see fit the SHOULD/UNLESS=
 form:<br>
 =A0 =A0 =A0 =A0SHOULD send a 1 UNLESS you are in a walled garden<br>
 =A0 =A0 =A0 =A0SHOULD flip bit 27 UNLESS you have a disk<br>
 =A0 =A0 =A0 =A0SHOULD NOT explode UNLESS you are a bomb<br>
are all reasonable SHOULD-level statements.<br></blockquote><div><br></div>=
<div>But how about=A0</div><div><br></div><div>SHOULD do FOO UNLESS you hav=
e given serious consideration as to the consequences of not doing FOO.</div=
>
<div><br></div><div>Isn&#39;t that really the original intention of SHOULD =
? =A0Do we gain anything if that is added every time it is used?</div><div>=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex;">

<br>
I would offer that ANY construction of SHOULD without an UNLESS is a MAY. =
=A0</blockquote><div><br></div><div>How about this as a counterexample.=A0<=
/div><div><br></div><div>In London, you MAY use the tube for transport. Giv=
en the weather, you SHOULD carry an umbrella.</div>
<div><br></div><div>This SHOULD and =A0MAY convey different things, in a wa=
y that I would argue is useful, and enumerating a list of UNLESSes is not g=
oing to be exhaustive.=A0</div><div>=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;=
">
Unless of course one considers us the Protocol Nanny&#39;s(tm) - if do not =
do a SHOULD, we will send you to bed without your treacle!</blockquote><div=
><br></div><div>Now, now, now. This is the IETF. We use cookies for motivat=
ion.=A0</div>
<div><br></div><div>Regards</div><div>Marshall</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;"> I.e., there IS NO DISTINCTION BETWEEN A BARE SHOULD=
 AND A MAY.<br>

<div><div></div><div class=3D"h5"><br>
On Aug 29, 2011, at 9:47 PM, <a href=3D"mailto:ned%2Bietf@mauve.mrochek.com=
">ned+ietf@mauve.mrochek.com</a> wrote:<br>
<br>
&gt;&gt; Hi -<br>
&gt;<br>
&gt;&gt;&gt; From: &quot;Eric Burger&quot; &lt;<a href=3D"mailto:eburger-l@=
standardstrack.com">eburger-l@standardstrack.com</a>&gt;<br>
&gt;&gt;&gt; To: &quot;Narten Thomas&quot; &lt;<a href=3D"mailto:narten@us.=
ibm.com">narten@us.ibm.com</a>&gt;; &quot;Saint-Andre Peter&quot; &lt;<a hr=
ef=3D"mailto:stpeter@stpeter.im">stpeter@stpeter.im</a>&gt;<br>
&gt;&gt;&gt; Cc: &quot;IETF discussion list&quot; &lt;<a href=3D"mailto:iet=
f@ietf.org">ietf@ietf.org</a>&gt;<br>
&gt;&gt;&gt; Sent: Monday, August 29, 2011 3:08 PM<br>
&gt;&gt;&gt; Subject: Re: 2119bis<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I would assume in the text of the document. =A0This paragraph =
is simply an enumeration of Burger&#39;s Axiom:<br>
&gt;&gt;&gt; For every SHOULD, there must be an UNLESS, otherwise the SHOUL=
D is a MAY.<br>
&gt;<br>
&gt;&gt; I disagree.<br>
&gt;<br>
&gt; I concur with your disagreement. SHOULD should *not* be used when the<=
br>
&gt; list of exceptions is known and practically enumerable.<br>
&gt;<br>
&gt;&gt; If the &quot;UNLESS&quot; cases can be fully enumerated, then<br>
&gt;&gt; &quot;SHOULD x UNLESS y&quot; is equivalent to &quot;WHEN NOT y MU=
ST X.&quot;<br>
&gt;&gt; (Both beg the question of whether we would need to spell out that<=
br>
&gt;&gt; &quot;WHEN y MUST NOT X&quot; is not necessarily an appropriate in=
ference.)<br>
&gt;<br>
&gt;&gt; RFC 2119 SHOULD is appropriate when the &quot;UNLESS&quot; cases a=
re<br>
&gt;&gt; known (or suspected) to exist, but it is not practical to exhausti=
vely<br>
&gt;&gt; identify them all.<br>
&gt;<br>
&gt;&gt; Let&#39;s not gild this lily.<br>
&gt;<br>
&gt; +1<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ned<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>
</div></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></div>

--000e0cd6a95a7de61d04abb8ef88--

From Chris.Dearlove@baesystems.com  Tue Aug 30 06:25:24 2011
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 504E221F8BD8 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MSydRmB8ncxS for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:25:23 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id C0AC321F85F2 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:25:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.68,302,1312153200"; d="scan'208";a="154639289"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 30 Aug 2011 14:26:49 +0100
Received: from glkms1103.GREENLNK.NET (glkms1103.greenlnk.net [10.108.36.194]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id p7UDQmdu017239; Tue, 30 Aug 2011 14:26:49 +0100
Received: from GLKMS2100.GREENLNK.NET ([10.15.184.93]) by glkms1103.GREENLNK.NET with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 30 Aug 2011 14:26: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: 7bit
Subject: RE: Routing at the Edges of the Internet
Date: Tue, 30 Aug 2011 14:26:47 +0100
Message-ID: <ABE739C5ADAC9A41ACCC72DF366B719D0496C447@GLKMS2100.GREENLNK.NET>
In-Reply-To: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Routing at the Edges of the Internet
Thread-Index: Acxjk52echQzEzzZTQyWWfF32FyUxwDgrLAg
References: <CADPp2fB9Y0Zcqi3p7Oxnog2t66rSe2HY_qQOK62e+t5Hp6fJFg@mail.gmail.com>
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "Adam Novak" <interfect@gmail.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 30 Aug 2011 13:26:48.0771 (UTC) FILETIME=[78A2C130:01CC6718]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:25:24 -0000

You could start by looking at MANET work, both in the WG of that
name and work outside the IETF under that name and as ad hoc
networks (the mobile in MANET can be misleading, D for dynamic
might be mor to the point) and mesh networks. There are real
networks (such as the Freifunk network in Germany) that do some
of what you are talking about, and use protocols based on IETF
work. (Freifunk uses OLSR - RFC 3626 - and intends, as I
understand, to use OLSRv2, once we manage to finish it.)

Note: I'm an author of OLSRv2, but have no connection to
Freifunk.

There are more issues, some of which you touch on, such as
with regard to addressing issues (the MANET WG is about
routing). The AUTOCONF WG was intended to address these but
that has not been a great success. Nor am I claiming MANET
has produced all the answers to all the routing-related
problems. Part of what's missing is rationale and explanatory
material explaining how you can do more than might be obvious
with what does exist. (There are RFCs 2501 and 5889, but
there is more material known to people working in these areas
than those capture.)

-- 
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
Adam Novak
Sent: 26 August 2011 02:58
To: ietf@ietf.org
Subject: Routing at the Edges of the Internet


                    *** WARNING ***

  This message has originated outside your organisation,
  either from an external partner or the Global Internet. 
      Keep this in mind if you answer this message.
 

I trust that some of you have seen this article from a while back:

<http://moblog.wiredwings.com/archives/20110315/How-We-Killed-The-Intern
et-And-Nobody-Noticed.html>

An informative except:

"When I open my laptop, I see over ten different wifi access points.
Say I wanted to send data to my friend in the flat next to mine. It is
idiotic that nowadays, I would use the bottleneck subscriber line to
my upstream ISP and my crippled upload speed and push it all the way
across their infrastructure to my neighbors ISP and back to the Wifi
router in reach of mine. The Internet is not meant to be used that
way. Instead, all these wifi networks should be configured to talk to
each other."

I also trust that you are aware of what happened to the Internet in
Egypt (and elsewhere) this spring, where Internet connectivity was
disrupted by shutting down major ISP networks.

I would like to bring the attention of the IETF to what I see as a
fundamental problem with the current architecture of the Internet:

The Internet is not a network.

As part of the development of the Internet, fault-tolerant routing
protocols have been developed that allow a connecdestined fortion to
be maintained, even if the link that was carrying goes down, by
routing packets around the problem. Similarly, packets can be
load-balanced over multiple links for increased bandwidth. However,
the benefits of these technologies are not available to end users. If
I have a smartphone with both a 3G and a Wi-Fi connection, downloads
cannot currently be load-balanced across them. The two interfaces are
on two different networks, which are almost certainly part of two
different autonomous systems. Packets must be addressed to one of the
two interfaces, not the device, and packets addressed to one interface
have no way to be routed to the other. Similar problems arise when a
laptop has both a wired and a wireless connection. Wired networks also
suffer from related difficulties: If I have Verizon and my friend has
Comcast, and we string an Ethernet cable between our houses, packets
for me will still all come down my connection, and packets for my
friend will still all come down theirs.

The Internet, as it currently appears to end-users, has a logical tree
topology: computers connect to your home router, which connects to
your ISP, which connects to the rest of the Internet. Cell phones
connect to the tower, which connects through a backhaul link to the
rest of the Internet. Almost all of the devices involved have multiple
physical interfaces and full IP routing implementations, but only the
default route is ever used. This results in a brittle Internet: the
failure of one ISP router can disconnect a large number of end-users
from the Internet, as well as interrupting communication between those
users, even when those users are, physically, only a few feet from
each other.

My question is this: what IETF work would be needed to add more
routing to the edges of the Internet? If each home or mobile device
was essentially it's own autonomous system, what would this do to
routing table size? To ASN space utilization? How can individuals
interconnect home networks when RIRs do not assign address and AS
number resources to individuals? How might individuals interconnect
home networks without manual routing configuration? Under what
circumstances could an ISP trust a client's claim to have a route to
another client or to another ISP? How might packets sent to a device's
address on one network be routed to that device's address on another
network, while packets to immediately adjacent addresses take the
normal path?
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


********************************************************************
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 eburger@standardstrack.com  Tue Aug 30 06:46:31 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 901B421F8B25 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N4zFZ300sud0 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:46:31 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id E95E921F8B22 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:46:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=T5jv68bTwPxTuF+4d+dNmCM0gHlgxdGHX9fsJFC2tnwefRiYLSnJmyCTaPMBBJv/QVvHmUex6QHf4wXFZg7he0CBGd7QEevX6jTQmJUbBlweBrQ0Jyf4muC9qT3pUNxN;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyOfP-0001Dt-V4 for ietf@ietf.org; Tue, 30 Aug 2011 06:47:54 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-14--750060501; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 2119bis
Date: Tue, 30 Aug 2011 09:47:52 -0400
In-Reply-To: <4E5CAD66.50708@gmail.com>
To: IETF list discussion <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net> <4E5CAD66.50708@gmail.com>
Message-Id: <0CD74772-7300-4A85-AA2F-CCC4574D47A1@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:46:31 -0000

--Apple-Mail-14--750060501
Content-Type: multipart/alternative;
	boundary=Apple-Mail-13--750060546


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

+1, too.

This goes along with my strong desire to eliminate passive voice, unless =
the goal is to have the actor be obfuscated (as an example).

On Aug 30, 2011, at 5:29 AM, Mykyta Yevstifeyev wrote:

>> 2) I strongly believe that authors should be encouraged to enumerate =
the potential subjects of conformance terms, and to use them in every =
instance.
>>=20
>> For example, a requirement like this:
>>=20
>> """The Foo header MUST contain the "bar" directive"""
>>=20
>> is ambiguous; it doesn't specify who has to do what. Rather,
>>=20
>> """Senders MUST include the "bar" directive when producing the Foo =
header; recipients that receive a Foo header without a "bar" directive =
MUST ..."""
>>=20
>> is unambiguous (assuming that the spec defines the terms "sender" and =
"recipient").
>=20
> +1.


--Apple-Mail-13--750060546
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1, =
too.<div><br></div><div>This goes along with my strong desire to =
eliminate passive voice, unless the goal is to have the actor be =
obfuscated (as an example).</div><div><br><div><div>On Aug 30, 2011, at =
5:29 AM, Mykyta Yevstifeyev wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
"><div><blockquote type=3D"cite">2) I strongly believe that authors =
should be encouraged to enumerate the potential subjects of conformance =
terms, and to use them in every instance.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">For example, a =
requirement like this:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">"""The Foo =
header MUST contain the "bar" directive"""<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is ambiguous; =
it doesn't specify who has to do what. =
Rather,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">"""Senders MUST =
include the "bar" directive when producing the Foo header; recipients =
that receive a Foo header without a "bar" directive MUST =
..."""<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">is unambiguous =
(assuming that the spec defines the terms "sender" and =
"recipient").<br></blockquote><br>+1.<br></div></span></blockquote></div><=
br></div></body></html>=

--Apple-Mail-13--750060546--

--Apple-Mail-14--750060501
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxMzQ3NTJaMCMGCSqGSIb3DQEJ
BDEWBBR1dWomqc2LQ1lwwDS7gWIxz77RpTCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAAEnrM6sKyVnoh9aoK689UYFG99bsXkL2AJtiXctzW81gsnu
4AGcrm/U/531x2rB2Dv0QgJ92HKy/tHVE/NWzUl50kCQXYgsqd+TZT9fzluJwvlUof5jLlzVQ+zH
nvShBCrHCihi/m65x1NnKOdBjRknFnuB2VX83ACPakAfGI7KTNIdYzxU9cd9OdqypSqLkvV2BeYK
EvTNt6tPOHQLHN4wrUcu0KbCi3AwSjf5+Sconq1RLmEhryVf6iuaVKkJKttgPPwOAltH+AH7qmcc
hDi5C/AYv61LBn9/Zuk+MBUb5pCryuxi6MSem/dit3UQp7gHWjHTkcvrcHvej0ym9vgAAAAAAAA=

--Apple-Mail-14--750060501--

From eburger@standardstrack.com  Tue Aug 30 06:47:58 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5C821F8B68 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.506
X-Spam-Level: 
X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W7w-eYyp-e0H for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:47:57 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9778121F8B56 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:47:57 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=nAy2ybTRG9Qs5sBBQTeETSNXgxem1YHYqaGMGR6R1Zq0O2G9dQ0qql/hZ+wFVvAAeS3iAd48u036ds8xsk5RLU2D1lK5SjM2uz8amReWgM8ApXIor+h+BXyvMSkkLXsz;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyOgu-0003dw-6Z; Tue, 30 Aug 2011 06:49:24 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-16--749968795; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com>
Date: Tue, 30 Aug 2011 09:49:23 -0400
Message-Id: <9B8715F5-A028-422E-8A54-689E47267F92@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:47:58 -0000

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

On Aug 30, 2011, at 9:24 AM, Marshall Eubanks wrote:
> Dear Eric;
>=20
> I support adding the SHOULD ... UNLESS formalism (although maybe it =
should be MUST... UNLESS). It would be useful as there will be times =
where the UNLESS can be specified and has been given due consideration =
at the time of writing. That, however, will not always be the case. =
(More inline).
[snip]
> But how about=20
>=20
> SHOULD do FOO UNLESS you have given serious consideration as to the =
consequences of not doing FOO.
>=20
> Isn't that really the original intention of SHOULD ?  Do we gain =
anything if that is added every time it is used?

Looking at this from a protocol perspective, SHOULD now equals MAY.  =
There is no objective way of deciding when to do FOO or not.

[snip]=

--Apple-Mail-16--749968795
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxMzQ5MjRaMCMGCSqGSIb3DQEJ
BDEWBBQJTS7EmFsNgH9EALYatO+SHmGbVzCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAEMOZU81+x/YZudjWxHpPlZXy6ffc8SMkZBbBXRkPmJmZIgf
Pwpxb4JGLBmZIaCwlOs7mf81L6qNldJHFUXT9GSwuxs8zlbH8yx9+vMEKlxYDGcgNmINUS+sutxF
C3W3szJB6VeSezJgPlp7gtvZVegnTSOxNjrE6/nQ9kWgA8wX6Gq1kNjPlVzXLbUnSERtm4NNytim
9Ogh0lAiCptjvCRCSjGoyrwTIkSOzodIqUVqVYG/vc8zkG/bc1bjHUizDJ4Mxg0r1ECluM3jc+Uq
J+EAEeJusZXzndwt/scbJ1hJMcsxGWG8oswjesKroEXp621lLBcrwTyrvCVgC8FR0lQAAAAAAAA=

--Apple-Mail-16--749968795--

From eburger@standardstrack.com  Tue Aug 30 06:49:48 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC87721F851A for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:49:48 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SiKXFUwCm7r3 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:49:48 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 247A721F8B2D for <ietf@ietf.org>; Tue, 30 Aug 2011 06:49:48 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=LYcXoXzxOnDFOsQ1ud6TT5qULP87+6EunC52cvwZOYwxef8/0brdWJuVKtmjXMV5XWCZUBDAWFCeQgRSido7lokpsitbHm26eXEzSa7IJrCVJXso8YBhyib4HuOCnbcn;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyOig-0005HX-Lm; Tue, 30 Aug 2011 06:51:14 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-18--749857667; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>
Date: Tue, 30 Aug 2011 09:51:14 -0400
Message-Id: <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:49:48 -0000

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

I would offer that working groups that say to do something that may or =
may not hold in foreseen or unforeseen circumstances is most likely =
working on a protocol that is way too complex and is begging for =
interoperability problems.  What ever happened to building simple, =
point-solution protocols that followed the hour-glass and end-to-end =
principles, and then building your complex protocols out of them?

On Aug 29, 2011, at 11:11 PM, Keith Moore wrote:

> On Aug 29, 2011, at 10:44 PM, Eric Burger wrote:
>=20
>> I would offer that ANY construction of SHOULD without an UNLESS is a =
MAY.
>=20
> The essential beauty of SHOULD is that it gets specification writers =
and working groups out of the all-too-common rathole of trying to =
anticipate and nail down every exceptional case.
>=20
> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-18--749857667
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxMzUxMTVaMCMGCSqGSIb3DQEJ
BDEWBBR29q13ddE+QfZG6FT5zPIOwj9qoDCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAAnO5db3FBR/HyHaAuMKfrHy5ZqRvX7fVuLjBsw2kw8aj8yl
r5LWBnXRxlEwK4FoCKUBpIJxLP7EWfhc+EDlCaW/2dHrozfYONsCcjS5M4slnAfNt+nsC/falNV7
ySLAMw1Flh4a/8U11thkK1VeEXtnXPlptFnD5Fyvw9gpecWaC8vxl96wKd+vCWIBYHQt9SGgcNRo
57PtoR04vSDQS+7Iuum1BpFIHvF7USNlaaciXmLG3Q6vKAM76uTmVYF3ZWRHESvDCEk+OPmgeqWO
Kl1y4zTLsFFZJ1K/e9ghQMlrhd0TogytYcLshAxF0UJ5/Ei+KnmgDUZ+YRhM/nHATxQAAAAAAAA=

--Apple-Mail-18--749857667--

From moore@network-heretics.com  Tue Aug 30 06:52:59 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B847221F8B28 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.605
X-Spam-Level: 
X-Spam-Status: No, score=-3.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RxAKIOZRssbE for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:52:59 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 1360A21F8B2B for <ietf@ietf.org>; Tue, 30 Aug 2011 06:52:58 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id DEE0820CD8; Tue, 30 Aug 2011 09:54:25 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 30 Aug 2011 09:54:25 -0400
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=/B72Zy1a9nMzW2Kygq03OFdftPs=; b=VH 5ugxVpd35ZJ4WDqyAO9S/wCuSeL7nlSkBXASfzGZUZlEmQHGO6bh3SoX0dYAHJMy ZA8edoaN9Yt9n9G8aKdc+KysMdKvDa4wa+zR7PNZTHfowU6GaqBbdIehGTKwVeBE yOG4ofCFKts0xkSOeyI/WjQX8iwHWQCnUMaA3O0FM=
X-Sasl-enc: IWRDjIsr1UY5VLJX7/+T3FdW9jNpWX5xbQW4au+0S7je 1314712465
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id A88B341D5D4; Tue, 30 Aug 2011 09:54:25 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com>
Date: Tue, 30 Aug 2011 09:54:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com> <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:52:59 -0000

I think you're overgeneralizing.  My experience is that judicious use of =
SHOULD seems to make both protocols and protocol specifications simpler; =
trying to nail everything down makes them more complex.

Keith

On Aug 30, 2011, at 9:51 AM, Eric Burger wrote:

> I would offer that working groups that say to do something that may or =
may not hold in foreseen or unforeseen circumstances is most likely =
working on a protocol that is way too complex and is begging for =
interoperability problems.  What ever happened to building simple, =
point-solution protocols that followed the hour-glass and end-to-end =
principles, and then building your complex protocols out of them?
>=20
> On Aug 29, 2011, at 11:11 PM, Keith Moore wrote:
>=20
>> On Aug 29, 2011, at 10:44 PM, Eric Burger wrote:
>>=20
>>> I would offer that ANY construction of SHOULD without an UNLESS is a =
MAY.
>>=20
>> The essential beauty of SHOULD is that it gets specification writers =
and working groups out of the all-too-common rathole of trying to =
anticipate and nail down every exceptional case.
>>=20
>> Keith
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20


From moore@network-heretics.com  Tue Aug 30 06:54:45 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC3C21F8C00 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.604
X-Spam-Level: 
X-Spam-Status: No, score=-3.604 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJUxli1QzCLx for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:54:42 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id ACA9021F8BF6 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:54:39 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2D49D209DB; Tue, 30 Aug 2011 09:56:07 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 30 Aug 2011 09:56:07 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Jlb C5Pd4xEoQ6KCu/ZUUE8Kxjqo=; b=ormsX/sPhGl3CQ27fyrCEsMuzL1qx0LY5Q8 qycU2Btb7UcNpzkqCdj5ErWhpOjSr/1GsXuHR0mD4386HiW0Ua7HVPn7pfRjoupz JzJ4zsZtAJ8KrV2ZTS9S2SAqWE9yu5ECCgkWmfOgwQKI9iglk7sDNTkl1oUGRV4H jRR8biI0=
X-Sasl-enc: M9om8yGsxFim/kEcUyCKVzfTPivHLYEO2u+IZProZETf 1314712567
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id EBCAB41E9E4; Tue, 30 Aug 2011 09:56:06 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-40--749566518
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com>
Date: Tue, 30 Aug 2011 09:56:06 -0400
Message-Id: <ABF8FB5A-AAA7-419D-BBFA-FF11DA263837@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:54:45 -0000

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

On Aug 30, 2011, at 9:24 AM, Marshall Eubanks wrote:

> I support adding the SHOULD ... UNLESS formalism (although maybe it =
should be MUST... UNLESS). It would be useful as there will be times =
where the UNLESS can be specified and has been given due consideration =
at the time of writing. That, however, will not always be the case. =
(More inline).

How would SHOULD...UNLESS or MUST...UNLESS differ from using the current =
2119 definitions and just writing SHOULD...unless or MUST ... unless?

Personally I think 2119 is just fine and doesn't need to be updated.

Keith


--Apple-Mail-40--749566518
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><div>On Aug 30, 2011, at 9:24 AM, Marshall Eubanks =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I support =
adding the SHOULD ... UNLESS formalism (although maybe it should be =
MUST... UNLESS). It would be useful as there will be times where the =
UNLESS can be specified and has been given due consideration at the time =
of writing. That, however, will not always be the case. (More =
inline).</span></blockquote></div><br><div>How would SHOULD...UNLESS or =
MUST...UNLESS differ from using the current 2119 definitions and just =
writing SHOULD...unless or MUST ... =
unless?</div><div><br></div><div>Personally I think 2119 is just fine =
and doesn't need to be =
updated.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-40--749566518--

From eburger@standardstrack.com  Tue Aug 30 06:54:52 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11EA621F8C37 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:54:52 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FoUXmIokUCaH for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:54:51 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0E421F8C35 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:54:51 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=w1uw8i1NahuHJYMvo4blbWWdSlYgozuJKd1vAUmPsRDTiKhIK4MPzovL6gcS4h/0dNdQVaLHuPJ3aMthee55geW4V4zEfG52DGgwASHvZimZ6yV3A/EpFAkIUML+U3yl;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyOnZ-0002re-9k for ietf@ietf.org; Tue, 30 Aug 2011 06:56:18 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-19--749557775; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 2119bis
Date: Tue, 30 Aug 2011 09:56:14 -0400
In-Reply-To: <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com>
To: IETF discussion list <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net> <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com> <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com>
Message-Id: <5FD474FD-CC22-4222-89F9-B47B7ECE0638@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:54:52 -0000

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

This sentiment mostly makes sense.

If an endpoint expects SHOULD/MAY items implemented as MUSTs on the =
remote end, then one should slap the endpoint developer silly.  Read the =
RFC!  If it says SHOULD/MAY, then your implementation MUST be able to =
handle the feature present *and* absent.

Note that every SHOULD/MAY in a specification introduces cyclomatic =
complexity.  Every SHOULD/MAY results in at least one "if" statement, to =
test the presence or absence of the feature in the remote end.  =
Protocols will be much simpler to implement. Moreover, given the results =
in the software engineering literature that indicate latent defects =
appear super-linearly with cyclomatic complexity, protocols without (or =
a minimum) of SHOULD/MAY features will have fewer defects in the field.

Remember, we are working on Internet protocols, where a one-in-a-million =
corner case happens many times per day.

On Aug 30, 2011, at 4:00 AM, HLS wrote:

> On 8/30/11, Murray S. Kucherawy <msk@cloudmark.com> wrote:
>=20
>>> Mark Nottingham:
>>> 1) I agree that the "SHOULD... UNLESS" pattern ought be documented.
>=20
>> I had never thought of this before.  I kind of like the idea, =
especially since SHOULD
>> has always meant "MUST unless you really know what you're doing"
>=20
> Such an odd reading.  Does it mean you MUST because you could not
> handle it otherwise?
>=20
> It takes two to tango.  One side reasons can be different than the
> other. If a software breaks down because it read SHOULD as a MUST and
> expected the other end will also view is a MUST, then it didn't know
> what it was doing.  Things break down. Implementors on either side
> can't depend on it and need to function in lieu of it. There is always
> the possibility one decided "Nahhhh, not needed, not worth the cost.
> Its not required." etc, and no one should die because of that
> decision.
>=20
> I think it MUST be noted that a Minimum Implementation for a protocol
> is all anyone can expect. If a SHOULD item is among the listed minimum
> requirements, it MUST be removed from the list or changed to a MUST.
>=20
> Maybe the term Minimum Implementation (is part of, is not part of) can
> be incorporated into each of the key word text.
>=20
> --=20
> hls
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-19--749557775
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxMzU2MTVaMCMGCSqGSIb3DQEJ
BDEWBBQzX1ajvS+WNva2BQgudi6wIGrQezCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAGWTSXJc74nxY9GBvxjDjGpVRDRrNNXJkOdzPaoB50OqYVZa
jeS+ejp/ExbA8ol2GYMObBmX/EyNquUjjMarn6e0NSCnl5xU4JNc3PvSTn6TCXqzIv5vRoF6uvf4
HXaA03sTyjOgI+6WiUkx/NR3hktCUcI4LPeQiDtm5MF/pQkliwCvy9nl2zOas9Hk9LfWg8ckX2Rh
uR7fNNSQ9LWeBzCTJVcEWuvhibRKYiXgsQp8vlqeYYcDEriTV1CycqbNEyBC6SySG+j1bGTPubEE
5B73K6k1HyLjZM+bCMBw0c3YqWQWF8bEZQNeepthrht44I+xHm56pxbNY1+02hb26QMAAAAAAAA=

--Apple-Mail-19--749557775--

From moore@network-heretics.com  Tue Aug 30 06:57:31 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB22721F8C53 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.604
X-Spam-Level: 
X-Spam-Status: No, score=-3.604 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzpUOUHn1nZB for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 06:57:31 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 53DF821F8C48 for <ietf@ietf.org>; Tue, 30 Aug 2011 06:57:31 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 4A70B20D35; Tue, 30 Aug 2011 09:58:58 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 30 Aug 2011 09:58:58 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=bny LwrAK4+2h48qGfN32RzVldso=; b=eGJr0x1gyh34kWgwFlW9Oi8Oxy/bk9fkLDD T3o/8PXMOFoQm7PPmSW78SsNH15F0pDwc46iBbTXF0bDZOFWnbJSff8Zdgb/8Fql 2/WcGX4QCyNw8DMA+MXd4JceJRv9HzHTyZmGaJ5mphGJtkNhw+wOiPPPblskwSHs XQen8klo=
X-Sasl-enc: 8WXMMNpiazog1Ny3S1exjkWOwmrdlZte5U5SBRQ4hOWr 1314712738
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 18C31B2030D; Tue, 30 Aug 2011 09:58:58 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-41--749395431
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <5FD474FD-CC22-4222-89F9-B47B7ECE0638@standardstrack.com>
Date: Tue, 30 Aug 2011 09:58:57 -0400
Message-Id: <998C3E75-53BB-45CB-9999-07676F95ABE9@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net> <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com> <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com> <5FD474FD-CC22-4222-89F9-B47B7ECE0638@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:57:31 -0000

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

On Aug 30, 2011, at 9:56 AM, Eric Burger wrote:

>  Every SHOULD/MAY results in at least one "if" statement, to test the =
presence or absence of the feature in the remote end.=20

false.=20


--Apple-Mail-41--749395431
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><div>On Aug 30, 2011, at 9:56 AM, Eric Burger wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">&nbsp;Every =
SHOULD/MAY results in at least one "if" statement, to test the presence =
or absence of the feature in the remote end.<span =
class=3D"Apple-converted-space">&nbsp;</span></span></blockquote></div><br=
><div>false.&nbsp;</div><div><br></div></body></html>=

--Apple-Mail-41--749395431--

From eburger@standardstrack.com  Tue Aug 30 07:12:18 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 944EE21F8C35 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:12:18 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iL8ssMvfsdi9 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:12:17 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id B9BB921F8C0B for <ietf@ietf.org>; Tue, 30 Aug 2011 07:12:17 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=W839V8OLJmk5Eh6/Bb3pT8m91TwSpdS770kDptBS6aK10NlEy8imY7XIxHtsiR//wXoYYs7gPaR6b7CACLTHxeIEn8wE2bijOwcnvKJXsDwohaLqq63qW1whXdh9sEmn;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyP4R-0006iy-26; Tue, 30 Aug 2011 07:13:44 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-23--748510800; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <998C3E75-53BB-45CB-9999-07676F95ABE9@network-heretics.com>
Date: Tue, 30 Aug 2011 10:13:41 -0400
Message-Id: <D2521E89-6075-4D72-BE80-80CB1C7437B4@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net> <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com> <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com> <5FD474FD-CC22-4222-89F9-B47B7ECE0638@standardstrack.com> <998C3E75-53BB-45CB-9999-07676F95ABE9@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 14:12:18 -0000

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

Strictly speaking, you are correct, in that if one interprets SHOULD/MAY =
as 'not bother', one does not need to check, unless the presence of the =
remote end doing the feature results in your barfing.  However, if one =
interprets SHOULD/MAY as 'bother', then one most likely needs to check =
on the capabilities of the far end or handle the varying data elements =
or protocol states that will or will not happen.

On Aug 30, 2011, at 9:58 AM, Keith Moore wrote:

> On Aug 30, 2011, at 9:56 AM, Eric Burger wrote:
>=20
>>  Every SHOULD/MAY results in at least one "if" statement, to test the =
presence or absence of the feature in the remote end.=20
>=20
> false.=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-23--748510800
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxNDEzNDJaMCMGCSqGSIb3DQEJ
BDEWBBRGzflNSktFlC82ExlXdAHsZqqEajCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAH8btgDeQZzgacalpWSBrPVzIMMuyLYQBUVSzwbrS8cYKLJ3
rcC3FO46yhtcWnFV1qir2kmlkEyZZcFcd7MWhFSMoQ3aZl3cq9i834UCWDi17pNDKidZsTeXm6Wk
f+jVMcSEEUMP2QFNstTpBwaKy5dGzgmnIXaMB02y4EwVboUENixtY908Krb04ucQbU5GMMnK9Xnu
qiPZKp7mI/oG+28l46yHmVUTVyYvQuifbrYBe08sYLRGHwk/SeSkjODiDLxyrwEeAHO+Jyy3GTc+
XHKWVnGzeKerfvjp+zsl7fx3eO+U4PjVlqqcYGLz7QYD7GhMeoWJgO0+CIUUbeJqSggAAAAAAAA=

--Apple-Mail-23--748510800--

From petithug@acm.org  Tue Aug 30 07:12:49 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7CCE21F8C7D for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fRt1yG+3YKvF for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:12:49 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id E96C021F8B7E for <ietf@ietf.org>; Tue, 30 Aug 2011 07:12:48 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 3EEA7202C8; Tue, 30 Aug 2011 16:09:37 +0200 (CEST)
Message-ID: <4E5CF034.6040308@acm.org>
Date: Tue, 30 Aug 2011 07:14:12 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com>
In-Reply-To: <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 14:12:50 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/30/2011 06:54 AM, Keith Moore wrote:
> I think you're overgeneralizing.  My experience is that judicious use of
> SHOULD seems to make both protocols and protocol specifications simpler;
> trying to nail everything down makes them more complex.

But using SHOULD does not make the implementation less complex, it simply
decreases the complexity for the *author* and increases the probability that two
independent implementations will have interoperability problems.

As an implementer, I would ban all SHOULD/SHOULD NOT/RECOMMENDED/NOT RECOMMENDED.

> 
> Keith
> 
> On Aug 30, 2011, at 9:51 AM, Eric Burger wrote:
> 
>> I would offer that working groups that say to do something that may or may
>> not hold in foreseen or unforeseen circumstances is most likely working on
>> a protocol that is way too complex and is begging for interoperability
>> problems.  What ever happened to building simple, point-solution protocols
>> that followed the hour-glass and end-to-end principles, and then building
>> your complex protocols out of them?
>> 
>> On Aug 29, 2011, at 11:11 PM, Keith Moore wrote:
>> 
>>> On Aug 29, 2011, at 10:44 PM, Eric Burger wrote:
>>> 
>>>> I would offer that ANY construction of SHOULD without an UNLESS is a
>>>> MAY.
>>> 
>>> The essential beauty of SHOULD is that it gets specification writers and
>>> working groups out of the all-too-common rathole of trying to anticipate
>>> and nail down every exceptional case.
>>> 

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5c8DMACgkQ9RoMZyVa61dv/ACfRCGdkyioOtkcLOR5P5AT7EGE
y/gAn2LtqRUztE/HJEpTAMuY2eoVrRjp
=VFmG
-----END PGP SIGNATURE-----

From sant9442@gmail.com  Tue Aug 30 07:21:43 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F05B821F8B56 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNM1wEcvBuZ6 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:21:43 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id F381221F8B4C for <ietf@ietf.org>; Tue, 30 Aug 2011 07:21:42 -0700 (PDT)
Received: by gwb20 with SMTP id 20so6596643gwb.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 07:23:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=852W5c0OhToQUept9dj/l7U1mFHp93uGbAZ6XZSHuYM=; b=EZCcYnReU2kC/FhN/g310gjzJm8QZnrwYHoHN71TKroZOip5wN8Bg/g9c1F4zJUdjl X/PKetS20wKZTt4XwZj/v2RSi3uwGmCbLr9joX0noMPxAKfkG8PuADOJI8rwtFlhYWNp NiHuBhhEV+XPzmK8F/vVYUjw04UCiHzuHSo60=
MIME-Version: 1.0
Received: by 10.236.184.134 with SMTP id s6mr13664714yhm.6.1314714190358; Tue, 30 Aug 2011 07:23:10 -0700 (PDT)
Received: by 10.147.136.20 with HTTP; Tue, 30 Aug 2011 07:23:10 -0700 (PDT)
In-Reply-To: <ABF8FB5A-AAA7-419D-BBFA-FF11DA263837@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com> <ABF8FB5A-AAA7-419D-BBFA-FF11DA263837@network-heretics.com>
Date: Tue, 30 Aug 2011 10:23:10 -0400
Message-ID: <CAEa=Q_WrXgq5QBPy0FEwrrDJ7ekCqD4FY1zES--k7cSk0iZ_kA@mail.gmail.com>
Subject: Re: 2119bis
From: HLS <sant9442@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 14:21:44 -0000

On 8/30/11, Keith Moore <moore@network-heretics.com> wrote:
> On Aug 30, 2011, at 9:24 AM, Marshall Eubanks wrote:
>
> Personally I think 2119 is just fine and doesn't need to be updated.
>
> Keith

+1

-- 
hls

From moore@network-heretics.com  Tue Aug 30 07:30:32 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95CBC21F8CA7 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.604
X-Spam-Level: 
X-Spam-Status: No, score=-3.604 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzbnlUKKGQF1 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:30:31 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id BFF0F21F8CA6 for <ietf@ietf.org>; Tue, 30 Aug 2011 07:30:31 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id A38592054F; Tue, 30 Aug 2011 10:31:58 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Tue, 30 Aug 2011 10:31:58 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=cP+ 9qvQezevVpmm0VipD8liEK7g=; b=TOAo+HimmI7+Gf3G9gMgesvM3rZmsyTH59P UD/DGNOKrq0mGmeNgBilu8bbzZAm9AwLZ75c9nv+D13NOLJYapNLRtX6rpIeQvR9 97iVBJtuh+/1Cfx6FIQL6o9FcIUiXtMS/GWgk57EPAKV9zjeThIntvy/0EHl3pPV KA6/XAuo=
X-Sasl-enc: DQwXrGjzfGhz2Wca7XhonqNh28t3pDB1PZhfXZm3RmUU 1314714718
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 72681AC025B; Tue, 30 Aug 2011 10:31:58 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-43--747415300
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <D2521E89-6075-4D72-BE80-80CB1C7437B4@standardstrack.com>
Date: Tue, 30 Aug 2011 10:31:57 -0400
Message-Id: <FD7E11EA-1B06-4129-95C5-F516DE8D783C@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net> <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com> <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com> <5FD474FD-CC22-4222-89F9-B47B7ECE0638@standardstrack.com> <998C3E75-53BB-45CB-9999-07676F95ABE9@network-heretics.com> <D2521E89-6075-4D72-BE80-80CB1C7437B4@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 14:30:32 -0000

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


On Aug 30, 2011, at 10:13 AM, Eric Burger wrote:
>=20
> On Aug 30, 2011, at 9:58 AM, Keith Moore wrote:
>=20
>> On Aug 30, 2011, at 9:56 AM, Eric Burger wrote:
>>=20
>>> Every SHOULD/MAY results in at least one "if" statement, to test the =
presence or absence of the feature in the remote end.=20
>>=20
>> false.=20

> Strictly speaking, you are correct, in that if one interprets =
SHOULD/MAY as 'not bother', one does not need to check, unless the =
presence of the remote end doing the feature results in your barfing.  =
However, if one interprets SHOULD/MAY as 'bother', then one most likely =
needs to check on the capabilities of the far end or handle the varying =
data elements or protocol states that will or will not happen.

SHOULD/MAY is used for many other cases than whether to implement a =
protocol feature that changes how the protocol works as viewed by its =
peer.

Keith


--Apple-Mail-43--747415300
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 Aug 30, 2011, at 10:13 AM, Eric Burger =
wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font>On Aug 30, 2011, =
at 9:58 AM, Keith Moore wrote:<br><br><blockquote type=3D"cite">On Aug =
30, 2011, at 9:56 AM, Eric Burger wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"> Every SHOULD/MAY results in at least one "if" statement, =
to test the presence or absence of the feature in the remote end. =
<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">false.&nbsp;</blockquote></div></blockquote><br><div><blockq=
uote type=3D"cite">Strictly speaking, you are correct, in that if one =
interprets SHOULD/MAY as 'not bother', one does not need to check, =
unless the presence of the remote end doing the feature results in your =
barfing. &nbsp;However, if one interprets SHOULD/MAY as 'bother', then =
one most likely needs to check on the capabilities of the far end or =
handle the varying data elements or protocol states that will or will =
not happen.<br></blockquote><div><br></div><div>SHOULD/MAY is used for =
many other cases than whether to implement a protocol feature that =
changes how the protocol works as viewed by its =
peer.</div><div><br></div><div>Keith</div><div><br></div></div></div></bod=
y></html>=

--Apple-Mail-43--747415300--

From moore@network-heretics.com  Tue Aug 30 07:33:53 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D90ED21F8C43 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.604
X-Spam-Level: 
X-Spam-Status: No, score=-3.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81lbCcMX86uy for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:33:53 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 0995221F8C04 for <ietf@ietf.org>; Tue, 30 Aug 2011 07:33:53 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8F29120E19; Tue, 30 Aug 2011 10:35:20 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 30 Aug 2011 10:35:20 -0400
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=5xjr5zt1sJ1F4GQ3AxUVUKZA9fM=; b=qj PHqoF6K8GaVOCi03cBWFKE1eBHHgVIidpdL+IC8c3xtioZt8shfa9ocy0KWQ4a4n Ly+3d/pzfQT0qZuYkPNFJz62JslPekGHG3MrgLJ4sxkeMgXJ5P07yp/OVDWdNPns 84YE2MVlxD35LbwClAPCPhzxRsJYrIm5pI0k7ArzY=
X-Sasl-enc: OPFclKIxaMOCQ7rsTDea6iHD2rI+85OSuXS6GqT6Ue7i 1314714920
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 663E0AC01F4; Tue, 30 Aug 2011 10:35:20 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5CF034.6040308@acm.org>
Date: Tue, 30 Aug 2011 10:35:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 14:33:54 -0000

On Aug 30, 2011, at 10:14 AM, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 08/30/2011 06:54 AM, Keith Moore wrote:
>> I think you're overgeneralizing.  My experience is that judicious use =
of
>> SHOULD seems to make both protocols and protocol specifications =
simpler;
>> trying to nail everything down makes them more complex.
>=20
> But using SHOULD does not make the implementation less complex, it =
simply
> decreases the complexity for the *author* and increases the =
probability that two
> independent implementations will have interoperability problems.

To the extent that SHOULD is causing interoperability problems, it may =
be that some authors are misusing SHOULD.  But it's not an inherent =
problem with SHOULD.

> As an implementer, I would ban all SHOULD/SHOULD NOT/RECOMMENDED/NOT =
RECOMMENDED.

I'm an implementor also, and I've found SHOULD to be very helpful. =20

Keith


From petithug@acm.org  Tue Aug 30 07:52:38 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C354121F8C0F for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:52:38 -0700 (PDT)
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.030, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sTRbgbUS0Uc for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:52:38 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 137AF21F8C07 for <ietf@ietf.org>; Tue, 30 Aug 2011 07:52:38 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 6CDCC202C8; Tue, 30 Aug 2011 16:49:26 +0200 (CEST)
Message-ID: <4E5CF98A.5090204@acm.org>
Date: Tue, 30 Aug 2011 07:54:02 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com>
In-Reply-To: <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 14:52:38 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/30/2011 07:35 AM, Keith Moore wrote:
> On Aug 30, 2011, at 10:14 AM, Marc Petit-Huguenin wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 08/30/2011 06:54 AM, Keith Moore wrote:
>>> I think you're overgeneralizing.  My experience is that judicious use of
>>> SHOULD seems to make both protocols and protocol specifications simpler;
>>> trying to nail everything down makes them more complex.
>>
>> But using SHOULD does not make the implementation less complex, it simply
>> decreases the complexity for the *author* and increases the probability that two
>> independent implementations will have interoperability problems.
> 
> To the extent that SHOULD is causing interoperability problems, it may be that some authors are misusing SHOULD.  But it's not an inherent problem with SHOULD.
> 
>> As an implementer, I would ban all SHOULD/SHOULD NOT/RECOMMENDED/NOT RECOMMENDED.
> 
> I'm an implementor also, and I've found SHOULD to be very helpful.  

Yes, it is very helpful in convincing one's PHB that one does not have to
implement something, or in convincing another company to reactivate a feature
during interop tests because one did not bother to implement it.

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5c+YgACgkQ9RoMZyVa61fVhACeKsjqPX1ckD572A+wpb2AKQA/
3qUAoJz3M9ORMxmCGksApSlxu5sEQbdk
=r9Bf
-----END PGP SIGNATURE-----

From moore@network-heretics.com  Tue Aug 30 07:57:05 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D534E21F8B4C for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.604
X-Spam-Level: 
X-Spam-Status: No, score=-3.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lgTFN-7QKlzO for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 07:57:05 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 3014221F8B47 for <ietf@ietf.org>; Tue, 30 Aug 2011 07:57:05 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id C16B520E70; Tue, 30 Aug 2011 10:58:32 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 30 Aug 2011 10:58:32 -0400
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=uR+21giPdUrBtg4npuHG/XYwzAg=; b=h7 iU84zETi5TB19IvPAS29Dye2ikCN9PdSNwqUQGuBxNgt1dxpriisEO/kVdJu1kEF n2ZUFO5QqCqrSokJoa7Qkpnvx0t57XCv9EG3ellZYR7Dcohuh6l//och/PyhfHsR E4CtkAliwyyxXGdLgvYH6xebmfCvwKtTPvyKzghZc=
X-Sasl-enc: VdOFgp616L/iOE7sdXP/NsXRc02mauKgNHUxsNiYNV9V 1314716312
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 8EBA2AC02A4; Tue, 30 Aug 2011 10:58:32 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5CF98A.5090204@acm.org>
Date: Tue, 30 Aug 2011 10:58:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 14:57:06 -0000

On Aug 30, 2011, at 10:54 AM, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 08/30/2011 07:35 AM, Keith Moore wrote:
>> On Aug 30, 2011, at 10:14 AM, Marc Petit-Huguenin wrote:
>>=20
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>=20
>>> On 08/30/2011 06:54 AM, Keith Moore wrote:
>>>> I think you're overgeneralizing.  My experience is that judicious =
use of
>>>> SHOULD seems to make both protocols and protocol specifications =
simpler;
>>>> trying to nail everything down makes them more complex.
>>>=20
>>> But using SHOULD does not make the implementation less complex, it =
simply
>>> decreases the complexity for the *author* and increases the =
probability that two
>>> independent implementations will have interoperability problems.
>>=20
>> To the extent that SHOULD is causing interoperability problems, it =
may be that some authors are misusing SHOULD.  But it's not an inherent =
problem with SHOULD.
>>=20
>>> As an implementer, I would ban all SHOULD/SHOULD NOT/RECOMMENDED/NOT =
RECOMMENDED.
>>=20
>> I'm an implementor also, and I've found SHOULD to be very helpful. =20=

>=20
> Yes, it is very helpful in convincing one's PHB that one does not have =
to
> implement something, or in convincing another company to reactivate a =
feature
> during interop tests because one did not bother to implement it.


Rather than vaguely attacking SHOULD, maybe it would be more =
illuminating to cite specific examples?

Keith


From evnikita2@gmail.com  Tue Aug 30 08:17:13 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A55B21F8C7B for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:17:13 -0700 (PDT)
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.133,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ndu9aWS8u4zk for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:17:12 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 00C1B21F8B84 for <ietf@ietf.org>; Tue, 30 Aug 2011 08:17:11 -0700 (PDT)
Received: by fxe6 with SMTP id 6so5927006fxe.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 08:18:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=m88OvLZeunGJDcuZb5LlGxAuvfUUzEg1ws4q3Nwzoz0=; b=eHpMMR5CT5HcsdQNQYyt4RhoEdNSfaGB7D4FWV99Xsi8Oe+wh8BGjBzX7mCVYoxssE ddN0VsdjHCZo04NSNp2RtvpJK4E2u8RjVN1f59DaHKwO63ODlPXKC29r2/k1TJV5zjtB iVolOG8aDeTRiIzs3tZN51gEB8CteaIw6ZYYc=
Received: by 10.223.71.155 with SMTP id h27mr975720faj.126.1314717516111; Tue, 30 Aug 2011 08:18:36 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id p3sm4652909faa.33.2011.08.30.08.18.34 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 08:18:35 -0700 (PDT)
Message-ID: <4E5CFF6A.30004@gmail.com>
Date: Tue, 30 Aug 2011 18:19:06 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Limitations in RFC Errata mechanism
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 15:17:13 -0000

Hello all,

I've observed several problems with submission mechanism for RFC 
Errata.  Here they are:

First, we have only two types of errata - Technical or Editorial.  In 
presence of 
<http://www.ietf.org/iesg/statement/rfc-metadata-errata.html>, "IESG 
Statement on IESG Processing of RFC Errata concerning RFC Metadata", I 
think the third type is necessary - Metadata.

Second, the "Section" field at 
<http://www.rfc-editor.org/errata_report.php> implies that only 
numerical sections will contain something an erratum can be reported 
against (overlooking the GLOBAL option).  However, Appendices, Abstract, 
Index, Author Info, different Notes exist, that aren't covered here.

Third, Original text and Corrected text fields imply that only 
before-and-after errata may be submitted.  However, there might be 
errata like Erratum # 6 
(http://www.rfc-editor.org/errata_search.php?eid=6), with an only Report 
text field.  I understand this feature was present in previous versions 
of errata mechanism but removed from the current.

So, taking this into consideration, some specific proposals:

1) Additional Metedata erratum type.  The fields which will be required 
to be filled in are: (a) metadata type: document source, RFC number, 
subseries*, obsoletes header*, updates header*, obsoleted-by header*, 
updated-by header*, category, (b) current value, and (c) correct value.  
Values marked under * in (a) may be available in the case when such 
metainfo is present in the RFC.

2) Replace the "Section" field with the drop-down list containing the 
following options: Section, Appendix, Abstract, Table of Contents, Note, 
Author information, Index.  In the case of the first two an additional 
field for number is available; in the case with Note - type of Note (RFC 
Editor, IESG etc.).

3) Allow user to choose whether they will enter old_text-new_text 
erratum or single_text erratum.

Also, several issues not related to submission mechanism.

1) Specific mailing lists devoted to discussion of errata against RFCs 
from different areas.  I've proposed this on rfc-interest list; see 
rationale at 
<http://www.rfc-editor.org/pipermail/rfc-interest/2011-August/002672.html>.;

2) Users might want to submit comments which could be displayable at 
erratum's page, similar to the mechanim employed by some IETF WGs in 
issue trackers.  This also includes ability to add myself to cc list.

3) Verified technical errata may be incorporated in the references.  Eg. 
4 technical errata were reported against RFC 793 and verified; so the 
reference may be:

> Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981.  Ammended by RFC Errata Reports 573, 1562, 1564, 1572.

So, further discussion is welcome...

Mykyta Yevstifeyev


From petithug@acm.org  Tue Aug 30 08:37:33 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B57A21F8CC3 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ze5hTOEIQXyH for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:37:32 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5CE21F8CA2 for <ietf@ietf.org>; Tue, 30 Aug 2011 08:37:32 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 63387202C8; Tue, 30 Aug 2011 17:34:21 +0200 (CEST)
Message-ID: <4E5D0410.1080000@acm.org>
Date: Tue, 30 Aug 2011 08:38:56 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com>
In-Reply-To: <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 15:37:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/30/2011 07:58 AM, Keith Moore wrote:
> On Aug 30, 2011, at 10:54 AM, Marc Petit-Huguenin wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 08/30/2011 07:35 AM, Keith Moore wrote:
>>> On Aug 30, 2011, at 10:14 AM, Marc Petit-Huguenin wrote:
>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> On 08/30/2011 06:54 AM, Keith Moore wrote:
>>>>> I think you're overgeneralizing.  My experience is that judicious use of
>>>>> SHOULD seems to make both protocols and protocol specifications simpler;
>>>>> trying to nail everything down makes them more complex.
>>>>
>>>> But using SHOULD does not make the implementation less complex, it simply
>>>> decreases the complexity for the *author* and increases the probability that two
>>>> independent implementations will have interoperability problems.
>>>
>>> To the extent that SHOULD is causing interoperability problems, it may be that some authors are misusing SHOULD.  But it's not an inherent problem with SHOULD.
>>>
>>>> As an implementer, I would ban all SHOULD/SHOULD NOT/RECOMMENDED/NOT RECOMMENDED.
>>>
>>> I'm an implementor also, and I've found SHOULD to be very helpful.  
>>
>> Yes, it is very helpful in convincing one's PHB that one does not have to
>> implement something, or in convincing another company to reactivate a feature
>> during interop tests because one did not bother to implement it.
> 
> 
> Rather than vaguely attacking SHOULD, maybe it would be more illuminating to cite specific examples?

It is difficult because of a mix of NDAs, employment confidentiality agreements
and desire to not single out individuals.  I'll send you an example in a private
email.

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5dBA0ACgkQ9RoMZyVa61cu4gCfTBpCbDMdZry14MxAA32zhFe8
oMwAn3dTiHuqO90Kb9SmC0etND8YT9px
=Nht0
-----END PGP SIGNATURE-----

From moore@network-heretics.com  Tue Aug 30 08:43:26 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2110F21F8ABC for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.603
X-Spam-Level: 
X-Spam-Status: No, score=-3.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q5DpY6iQ89IL for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:43:25 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 603B221F8834 for <ietf@ietf.org>; Tue, 30 Aug 2011 08:43:25 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 135ED20A83; Tue, 30 Aug 2011 11:44:53 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 30 Aug 2011 11:44:53 -0400
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=O07RjlDqHLnczpIBjtrRf3fik3w=; b=hU exXNzPNM6qbmKyANuUhclWOL3P4eriKzg9dDyMTB6ns1bPIE9XJSdr9SJ+gzTjan +vnGFfkb71Qbc3rdOeNJCRVRIpznYDGqY2NdrSfUdFYhEsgvjKOyUV6xhutgFtey LYNcSsncrDqcWQ4OEP/xv1CIlgDvSKjTOsI2SuHig=
X-Sasl-enc: Aqqc3E60+GDkTt0FciFbrmGQwBYJ9qp92Y+TAhyvSYY5 1314719092
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id CF4EDAC02FC; Tue, 30 Aug 2011 11:44:52 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5D0410.1080000@acm.org>
Date: Tue, 30 Aug 2011 11:44:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 15:43:26 -0000

On Aug 30, 2011, at 11:38 AM, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 08/30/2011 07:58 AM, Keith Moore wrote:
>> On Aug 30, 2011, at 10:54 AM, Marc Petit-Huguenin wrote:
>>=20
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>=20
>>> On 08/30/2011 07:35 AM, Keith Moore wrote:
>>>> On Aug 30, 2011, at 10:14 AM, Marc Petit-Huguenin wrote:
>>>>=20
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>=20
>>>>> On 08/30/2011 06:54 AM, Keith Moore wrote:
>>>>>> I think you're overgeneralizing.  My experience is that judicious =
use of
>>>>>> SHOULD seems to make both protocols and protocol specifications =
simpler;
>>>>>> trying to nail everything down makes them more complex.
>>>>>=20
>>>>> But using SHOULD does not make the implementation less complex, it =
simply
>>>>> decreases the complexity for the *author* and increases the =
probability that two
>>>>> independent implementations will have interoperability problems.
>>>>=20
>>>> To the extent that SHOULD is causing interoperability problems, it =
may be that some authors are misusing SHOULD.  But it's not an inherent =
problem with SHOULD.
>>>>=20
>>>>> As an implementer, I would ban all SHOULD/SHOULD =
NOT/RECOMMENDED/NOT RECOMMENDED.
>>>>=20
>>>> I'm an implementor also, and I've found SHOULD to be very helpful. =20=

>>>=20
>>> Yes, it is very helpful in convincing one's PHB that one does not =
have to
>>> implement something, or in convincing another company to reactivate =
a feature
>>> during interop tests because one did not bother to implement it.
>>=20
>>=20
>> Rather than vaguely attacking SHOULD, maybe it would be more =
illuminating to cite specific examples?
>=20
> It is difficult because of a mix of NDAs, employment confidentiality =
agreements
> and desire to not single out individuals.  I'll send you an example in =
a private
> email.

I look forward to seeing it.

But in general I get the impression that people are attacking SHOULD =
because of specific problems rather than general problems.  Since I find =
SHOULD very useful, to me it makes more sense to try to outline cases =
where SHOULD is problematic, and provide advice for those cases, than to =
try to get rid of it or change what it means.

e.g. For the specific case of optional features that must be negotiated, =
I don't think that SHOULD is the problem.  Rather I think that optional =
features are too common.  That's not to say that optional features and =
feature negotiation are never useful, particularly when extending a =
protocol that is already well-established in the field.  But if making =
features optional is seen by WGs as a way to avoid making hard decisions =
about what is required to interoperate, that really is a problem.  It =
just doesn't have anything to do with SHOULD.

Keith


From eburger@standardstrack.com  Tue Aug 30 08:45:29 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 854C821F8C80 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:45:29 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhjjHeNhxEo0 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:45:29 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id E839A21F8C78 for <ietf@ietf.org>; Tue, 30 Aug 2011 08:45:28 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=YBvspGYbu3+O3sfcs6Lq3CriSHLDlGVw0CJlqnV1hjOh3gkoKzgzNZfB0k3nuxb/3RmXrmEs8fhS9JIiBmBrOn21vozvWCOo2/klTir+nEoGZ+j2abJVoSXDi15SFAhD;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyQWd-0002bz-H5; Tue, 30 Aug 2011 08:46:55 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-30--742916637; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com>
Date: Tue, 30 Aug 2011 11:46:55 -0400
Message-Id: <4C4E3D71-F57D-4AFF-AAD7-73746A35B969@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 15:45:29 -0000

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

I think you have hit the root cause on the head.

I would also offer that by removing the crutch, or raising the bar to =
using the crutch, will help alleviate the root cause.

On Aug 30, 2011, at 11:44 AM, Keith Moore wrote:

> e.g. For the specific case of optional features that must be =
negotiated, I don't think that SHOULD is the problem.  Rather I think =
that optional features are too common.  That's not to say that optional =
features and feature negotiation are never useful, particularly when =
extending a protocol that is already well-established in the field.  But =
if making features optional is seen by WGs as a way to avoid making hard =
decisions about what is required to interoperate, that really is a =
problem.  It just doesn't have anything to do with SHOULD.


--Apple-Mail-30--742916637
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxNTQ2NTZaMCMGCSqGSIb3DQEJ
BDEWBBSfvrzEQNpbO9fneBPtVDmDGHj5WTCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAAsNHPwKWNn+1fiYKMqU+xNOyluwEdRHeHTjWYFj9O+COwoB
5WwWNTFWovORQDRl3QSO5j5mpaPy5FQG9lCVw9YJ9QLaHW3lV9Yw47wFwKl+O329LMn27TRpYGEj
PqN3eu13YcM90PeUtUhWafPZrtfEJtbz7SN+byWvw9WqOkTe7TBksAnriJFFyzDPwaqZp8PVoW7E
ePbAu33PKTVKOLsy0Bu3AGtB3xq/mVtdrgnxnRKwgduN6LLUQY3PTi0KPj4K6OIF2fgNUlA4/hN1
qZFiHxxbS033jxXef3Lf+gnXoVY/0AN4t9dWUFchVNLv9OnS2Opi6j0PDP7JmBnCLv8AAAAAAAA=

--Apple-Mail-30--742916637--

From moore@network-heretics.com  Tue Aug 30 08:57:08 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2985C21F8D01 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.603
X-Spam-Level: 
X-Spam-Status: No, score=-3.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NxRwG5vlCzgM for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 08:57:07 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 53BA121F8D00 for <ietf@ietf.org>; Tue, 30 Aug 2011 08:57:07 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 0C6D1209E1; Tue, 30 Aug 2011 11:58:35 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 30 Aug 2011 11:58:35 -0400
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=RaqaciSPiTdJryYaYFe2OsChvf8=; b=rP kLcn3RqxcG54oCPDuLKBCfnaXAJBU8gGvGq6y6PquN8CVTXruK43b7CeaVVad8rU DA4tMcv/zBMMB7l8rj0DgziOMPYNG1+aYPAVQlry415HioAjG00WegmAwsDzuuuC JoEBPpDgRJ5O0tUK5Y4Re8UjxQpaEGIvFdGht+dNg=
X-Sasl-enc: 1tSkaMZZxVR/DR28IjI/UcC2ZUUaMzsClo3i4/rCLwHl 1314719914
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id B25CEAC030B; Tue, 30 Aug 2011 11:58:34 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4C4E3D71-F57D-4AFF-AAD7-73746A35B969@standardstrack.com>
Date: Tue, 30 Aug 2011 11:58:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D410DE5F-4924-41BF-99A4-366D3614EDF9@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4C4E3D71-F57D-4AFF-AAD7-73746A35B969@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 15:57:08 -0000

e.g.=20

"SHOULD", "SHOULD NOT", "RECOMMENDED", and "NOT RECOMMENDED"  are =
appropriate when valid exceptions to a general requirement are known to =
exist or appear to exist, and it is infeasible or impractical to =
enumerate all of them.    However, they should not be interpreted as =
permitting implementors to fail to implement the general requirement =
when such failure would result in interoperability failure.=20


On Aug 30, 2011, at 11:46 AM, Eric Burger wrote:

> I think you have hit the root cause on the head.
>=20
> I would also offer that by removing the crutch, or raising the bar to =
using the crutch, will help alleviate the root cause.
>=20
> On Aug 30, 2011, at 11:44 AM, Keith Moore wrote:
>=20
>> e.g. For the specific case of optional features that must be =
negotiated, I don't think that SHOULD is the problem.  Rather I think =
that optional features are too common.  That's not to say that optional =
features and feature negotiation are never useful, particularly when =
extending a protocol that is already well-established in the field.  But =
if making features optional is seen by WGs as a way to avoid making hard =
decisions about what is required to interoperate, that really is a =
problem.  It just doesn't have anything to do with SHOULD.
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From petithug@acm.org  Tue Aug 30 09:05:12 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C14421F8D24 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kzI96fV6wZLJ for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:05:11 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 98B1F21F8D23 for <ietf@ietf.org>; Tue, 30 Aug 2011 09:05:11 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 6E603202C8; Tue, 30 Aug 2011 18:02:01 +0200 (CEST)
Message-ID: <4E5D0A8D.2040501@acm.org>
Date: Tue, 30 Aug 2011 09:06:37 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com>
In-Reply-To: <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 16:05:12 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/30/2011 08:44 AM, Keith Moore wrote:
> 
> On Aug 30, 2011, at 11:38 AM, Marc Petit-Huguenin wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On 08/30/2011 07:58 AM, Keith Moore wrote:
>>> On Aug 30, 2011, at 10:54 AM, Marc Petit-Huguenin wrote:
>>> 
>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>> 
>>>> On 08/30/2011 07:35 AM, Keith Moore wrote:
>>>>> On Aug 30, 2011, at 10:14 AM, Marc Petit-Huguenin wrote:
>>>>> 
>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>>> 
>>>>>> On 08/30/2011 06:54 AM, Keith Moore wrote:
>>>>>>> I think you're overgeneralizing.  My experience is that judicious
>>>>>>> use of SHOULD seems to make both protocols and protocol
>>>>>>> specifications simpler; trying to nail everything down makes them
>>>>>>> more complex.
>>>>>> 
>>>>>> But using SHOULD does not make the implementation less complex, it
>>>>>> simply decreases the complexity for the *author* and increases the
>>>>>> probability that two independent implementations will have
>>>>>> interoperability problems.
>>>>> 
>>>>> To the extent that SHOULD is causing interoperability problems, it
>>>>> may be that some authors are misusing SHOULD.  But it's not an
>>>>> inherent problem with SHOULD.
>>>>> 
>>>>>> As an implementer, I would ban all SHOULD/SHOULD
>>>>>> NOT/RECOMMENDED/NOT RECOMMENDED.
>>>>> 
>>>>> I'm an implementor also, and I've found SHOULD to be very helpful.
>>>> 
>>>> Yes, it is very helpful in convincing one's PHB that one does not have
>>>> to implement something, or in convincing another company to reactivate
>>>> a feature during interop tests because one did not bother to implement
>>>> it.
>>> 
>>> 
>>> Rather than vaguely attacking SHOULD, maybe it would be more illuminating
>>> to cite specific examples?
>> 
>> It is difficult because of a mix of NDAs, employment confidentiality
>> agreements and desire to not single out individuals.  I'll send you an
>> example in a private email.
> 
> I look forward to seeing it.
> 
> But in general I get the impression that people are attacking SHOULD because
> of specific problems rather than general problems.  Since I find SHOULD very
> useful, to me it makes more sense to try to outline cases where SHOULD is
> problematic, and provide advice for those cases, than to try to get rid of it
> or change what it means.

The meaning of SHOULD is clear for the authors (it "mean[s] that there may exist
valid reasons in particular circumstances to ignore a particular item, but the
full implications must be understood and carefully weighed before choosing a
different course."), the problem is that some implementers use a different
meaning (I do not have to implement this if it is inconvenient or difficult for
me to implement), vendors another one (SHOULD gave us the right to not implement
it).  I even read somewhere, perhaps on this list, about a vendor that rejected
any bug report against a SHOULD.  Conditional MUST, in my opinion, does not have
this problem.

> 
> e.g. For the specific case of optional features that must be negotiated, I
> don't think that SHOULD is the problem.  Rather I think that optional
> features are too common.  That's not to say that optional features and
> feature negotiation are never useful, particularly when extending a protocol
> that is already well-established in the field.  But if making features
> optional is seen by WGs as a way to avoid making hard decisions about what is
> required to interoperate, that really is a problem.  It just doesn't have
> anything to do with SHOULD.

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5dCosACgkQ9RoMZyVa61e8iwCfZccbWf20L0VaDtBFH6ekmhm5
l30AoJmTDscY/dAGwjfU3toAnydGZHft
=pbTY
-----END PGP SIGNATURE-----

From McQuilWP@pobox.com  Tue Aug 30 09:06:25 2011
Return-Path: <McQuilWP@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F41E21F8C93 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWNppF7N-kvo for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:06:24 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 74BB321F8C97 for <ietf@ietf.org>; Tue, 30 Aug 2011 09:06:24 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id BB7933335; Tue, 30 Aug 2011 12:07:49 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=26JIOhf2CSp/ Q3CLsvxbD7nWyjw=; b=BGTXknCMABWCzE9zbHdZn70YFbc7OJqQX+IRZ2XFUtT7 r7oYo0mRlFoeA4WnKKTUNEMo9mwpW6bhN0EmcNdtmVMJx+kEpclYxP+RONkHhlW3 m2rFqbQZlRVFS1Vg9GhjyAn5uhQuEBQYUBq8wZG2UQZDj9Gyy/YogftlUFZI/MU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=WtwLI0 bM2xF7JFPxNJmAIME/txkxdjm5HwbzKfMf1Wd5dg5qeoTPXrC6et+hz+Yf2JGnx6 +C8C96WjNw7pdyZ8sjwIwA5BdBrfqks7hj6YQwEIwxlYx5AHOKNv0S9EE8t0Y+Sa IITn5HhmS9ATDucPIyKe20bIMJRLG7LF0nli4=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id B34683334; Tue, 30 Aug 2011 12:07:49 -0400 (EDT)
Received: from BQ07NB (unknown [70.181.252.118]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id 34DC73332; Tue, 30 Aug 2011 12:07:49 -0400 (EDT)
Date: Tue, 30 Aug 2011 09:07:47 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <1156236919.20110830090747@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: 2119bis
In-Reply-To: <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com> <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 3517B882-D322-11E0-9D97-9DB42E706CDE-02871704!b-pb-sasl-quonix.pobox.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 16:06:25 -0000

On Tue, 2011-08-30, Keith Moore wrote:


> But in general I get the impression that people are attacking
> SHOULD because of specific problems rather than general
> problems.  Since I find SHOULD very useful, to me it makes more
> sense to try to outline cases where SHOULD is problematic, and
> provide advice for those cases, than to try to get rid of it or change what it means.

> e.g. For the specific case of optional features that must be
> negotiated, I don't think that SHOULD is the problem.  Rather I
> think that optional features are too common.  That's not to say
> that optional features and feature negotiation are never
> useful, particularly when extending a protocol that is already
> well-established in the field.  But if making features optional
> is seen by WGs as a way to avoid making hard decisions about
> what is required to interoperate, that really is a problem.  It
> just doesn't have anything to do with SHOULD.

How about recommending SHOULD ... BECAUSE to encourage the author
to justify the SHOULD. I suspect that this would reduce the
number of SHOULDs, that would be better as MAYs, due to the
author's personal preference.

My impression is that the 2119 limitation on MUST and SHOULD for
only necessary protocol features is sometimes forgotten.

-- 
Bill McQuillan <McQuilWP@pobox.com>


From moore@network-heretics.com  Tue Aug 30 09:10:44 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DBC421F8D44 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.603
X-Spam-Level: 
X-Spam-Status: No, score=-3.603 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66i2ipSjojxW for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:10:43 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 83D8321F8D43 for <ietf@ietf.org>; Tue, 30 Aug 2011 09:10:43 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id C931620DD9; Tue, 30 Aug 2011 12:11:47 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 30 Aug 2011 12:11:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=cXi Fo+4744jtPNdO0CzKYtHn8Ic=; b=pUXb/h9OD/PmGWJOl3s3W5hc7v1nyM78DV+ lEpApSDiPsBtpxo4+01iHeNbSXSY1J79gPVf2Z+ec9uB2SefGrB8XROKLofFXeZ+ 1OZT/HpC7G0xGtO+C6FfxarVjQYoXtmKhLEA6/76Xm4A6woXv6ZEvtNSc6rL/Dhe UbEBXGk8=
X-Sasl-enc: p58v18K7GpJxt02Y2SLa8T6Z/hFfhyZB6EkMdPgtfe5p 1314720707
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 6D4FDAC02F6; Tue, 30 Aug 2011 12:11:47 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-53--741425933
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5D0A8D.2040501@acm.org>
Date: Tue, 30 Aug 2011 12:11:46 -0400
Message-Id: <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 16:10:44 -0000

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

On Aug 30, 2011, at 12:06 PM, Marc Petit-Huguenin wrote:

> The meaning of SHOULD is clear for the authors (it "mean[s] that there =
may exist
> valid reasons in particular circumstances to ignore a particular item, =
but the
> full implications must be understood and carefully weighed before =
choosing a
> different course."), the problem is that some implementers use a =
different
> meaning (I do not have to implement this if it is inconvenient or =
difficult for
> me to implement), vendors another one (SHOULD gave us the right to not =
implement
> it).  I even read somewhere, perhaps on this list, about a vendor that =
rejected
> any bug report against a SHOULD.  Conditional MUST, in my opinion, =
does not have
> this problem.

But conditional MUST has other problems, namely that you have to =
enumerate the exceptions for the MUST, and that's not always practical.

Implementors who think that SHOULD gives them a free pass to avoid =
implementing something that's needed to interoperate are misreading =
2119.  But document editors should avoid using SHOULD for cases where =
failure to implement the requirement will result in interoperability =
failure.

I could see maybe posting an erratum or a brief update to 2119, but I =
think that reopening that document in general is a Very bad Idea.  And =
for existing documents that misuse SHOULD, the appropriate thing to do =
is to update those documents or post errata to those documents, rather =
than try to retroactively change the meaning of the keywords in those =
documents.

Keith


--Apple-Mail-53--741425933
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><div>On Aug 30, 2011, at 12:06 PM, Marc Petit-Huguenin =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">The meaning =
of SHOULD is clear for the authors (it "mean[s] that there may =
exist<br>valid reasons in particular circumstances to ignore a =
particular item, but the<br>full implications must be understood and =
carefully weighed before choosing a<br>different course."), the problem =
is that some implementers use a different<br>meaning (I do not have to =
implement this if it is inconvenient or difficult for<br>me to =
implement), vendors another one (SHOULD gave us the right to not =
implement<br>it). &nbsp;I even read somewhere, perhaps on this list, =
about a vendor that rejected<br>any bug report against a SHOULD. =
&nbsp;Conditional MUST, in my opinion, does not have<br>this =
problem.<br></span></blockquote></div><br><div>But conditional MUST has =
other problems, namely that you have to enumerate the exceptions for the =
MUST, and that's not always =
practical.</div><div><br></div><div>Implementors who think that SHOULD =
gives them a free pass to avoid implementing something that's needed to =
interoperate are misreading 2119. &nbsp;But document editors should =
avoid using SHOULD for cases where failure to implement the requirement =
will result in interoperability failure.</div><div><br></div><div>I =
could see maybe posting an erratum or a brief update to 2119, but I =
think that reopening that document in general is a Very bad Idea. =
&nbsp;And for existing documents that misuse SHOULD, the appropriate =
thing to do is to update those documents or post errata to those =
documents, rather than try to retroactively change the meaning of the =
keywords in those =
documents.</div><div><br></div><div>Keith</div><div><br></div></body></htm=
l>=

--Apple-Mail-53--741425933--

From sustrik@250bpm.com  Tue Aug 30 09:17:40 2011
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D819B21F8D71 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.292
X-Spam-Level: 
X-Spam-Status: No, score=-0.292 tagged_above=-999 required=5 tests=[AWL=0.402,  BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qGgtWcXaD8Z6 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:17:40 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 45F4E21F8D6F for <ietf@ietf.org>; Tue, 30 Aug 2011 09:17:39 -0700 (PDT)
Received: from [10.9.1.2] (chello089173046084.chello.sk [89.173.46.84]) by mail.moloch.sk (Postfix) with ESMTPSA id 5B1CA18385BF; Tue, 30 Aug 2011 18:19:06 +0200 (CEST)
Message-ID: <4E5D0DD7.2090008@250bpm.com>
Date: Tue, 30 Aug 2011 18:20:39 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: Bill McQuillan <McQuilWP@pobox.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com>	<91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com>	<4E5CF034.6040308@acm.org>	<2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com>	<4E5CF98A.5090204@acm.org>	<54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com>	<4E5D0410.1080000@acm.org>	<4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <1156236919.20110830090747@pobox.com>
In-Reply-To: <1156236919.20110830090747@pobox.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 16:17:41 -0000

On 08/30/2011 06:07 PM, Bill McQuillan wrote:

> How about recommending SHOULD ... BECAUSE to encourage the author
> to justify the SHOULD.

+1

Although saying something like this should do: "If there's a SHOULD 
clause in the document, the document MUST provide background and 
rationale for making the behaviour optional.

For an implementor it's often pretty hard to decide whether to implement 
functionality marked as SHOULD given that he has zero context and no 
idea whether the reason he has for not implementing the feature is at 
all in line with RFC authors' intentions.

Martin

From petithug@acm.org  Tue Aug 30 09:17:59 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AD1A21F8D80 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybEyHtMIO8l1 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:17:58 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 5145C21F8D7F for <ietf@ietf.org>; Tue, 30 Aug 2011 09:17:58 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 4684F202C8; Tue, 30 Aug 2011 18:14:47 +0200 (CEST)
Message-ID: <4E5D0D8B.3060000@acm.org>
Date: Tue, 30 Aug 2011 09:19:23 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
In-Reply-To: <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 16:17:59 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/30/2011 09:11 AM, Keith Moore wrote:
> On Aug 30, 2011, at 12:06 PM, Marc Petit-Huguenin wrote:
> 
>> The meaning of SHOULD is clear for the authors (it "mean[s] that there may exist
>> valid reasons in particular circumstances to ignore a particular item, but the
>> full implications must be understood and carefully weighed before choosing a
>> different course."), the problem is that some implementers use a different
>> meaning (I do not have to implement this if it is inconvenient or difficult for
>> me to implement), vendors another one (SHOULD gave us the right to not implement
>> it).  I even read somewhere, perhaps on this list, about a vendor that rejected
>> any bug report against a SHOULD.  Conditional MUST, in my opinion, does not have
>> this problem.
> 
> But conditional MUST has other problems, namely that you have to enumerate the
> exceptions for the MUST, and that's not always practical.
> 
> Implementors who think that SHOULD gives them a free pass to avoid implementing
> something that's needed to interoperate are misreading 2119.  But document
> editors should avoid using SHOULD for cases where failure to implement the
> requirement will result in interoperability failure.
> 
> I could see maybe posting an erratum or a brief update to 2119, but I think that
> reopening that document in general is a Very bad Idea.  And for existing
> documents that misuse SHOULD, the appropriate thing to do is to update those
> documents or post errata to those documents, rather than try to retroactively
> change the meaning of the keywords in those documents.

I like your definition a previous email, so perhaps an alternative solution to
updating 2119 is for authors who really care about this subject is to integrate
it in the Terminology section, something like this:

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   "SHOULD", "SHOULD NOT", "RECOMMENDED", and "NOT RECOMMENDED" are
   appropriate when valid exceptions to a general requirement are known
   to exist or appear to exist, and it is infeasible or impractical to
   enumerate all of them.  However, they should not be interpreted as
   permitting implementors to fail to implement the general requirement
   when such failure would result in interoperability failure.


- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5dDYkACgkQ9RoMZyVa61fA6gCfYTawSM53Uy7okAgidhSyQZzH
8JUAn3AwH0wz96A9K2EfyALIsVkjAFJP
=L35E
-----END PGP SIGNATURE-----

From moore@network-heretics.com  Tue Aug 30 09:22:11 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAE3A21F8D1D for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.603
X-Spam-Level: 
X-Spam-Status: No, score=-3.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JEIklT7cUEoN for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:22:10 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id BE31121F8C22 for <ietf@ietf.org>; Tue, 30 Aug 2011 09:22:10 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 81C3520EB4; Tue, 30 Aug 2011 12:23:38 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 30 Aug 2011 12:23:38 -0400
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=Dpul06xyM+oHUhioIoEiRapWpEQ=; b=Ac D4kw4M9KYft/fcdLe8+lHnrv4O1TP3vNyoOQNKUFfYzrOmOkPlpBv5gipum1U6x5 bul0fiQXo1pMEb4mMlrJB0nyM79SdRwVFuscU3l6ZxyAukwYyDsHGRQI9MyEfd7e jzWjplgpKSmbK2BvPw5+BNw3nhmkL2cClFQV+t8fU=
X-Sasl-enc: HKarrIKYk11fRN9iFhhU43nsitav1XRg/JSmzwKmBMd1 1314721418
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 4CBC3AC0317; Tue, 30 Aug 2011 12:23:38 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3 (Normal)
In-Reply-To: <1156236919.20110830090747@pobox.com>
Date: Tue, 30 Aug 2011 12:23:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DBC2BC4-9ACF-4673-B4F4-700E83A6EF4B@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com> <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <1156236919.20110830090747@pobox.com>
To: Bill McQuillan <McQuilWP@pobox.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 16:22:11 -0000

On Aug 30, 2011, at 12:07 PM, Bill McQuillan wrote:

> On Tue, 2011-08-30, Keith Moore wrote:
>=20
>> But in general I get the impression that people are attacking
>> SHOULD because of specific problems rather than general
>> problems.  Since I find SHOULD very useful, to me it makes more
>> sense to try to outline cases where SHOULD is problematic, and
>> provide advice for those cases, than to try to get rid of it or =
change what it means.
>=20
>> e.g. For the specific case of optional features that must be
>> negotiated, I don't think that SHOULD is the problem.  Rather I
>> think that optional features are too common.  That's not to say
>> that optional features and feature negotiation are never
>> useful, particularly when extending a protocol that is already
>> well-established in the field.  But if making features optional
>> is seen by WGs as a way to avoid making hard decisions about
>> what is required to interoperate, that really is a problem.  It
>> just doesn't have anything to do with SHOULD.
>=20
> How about recommending SHOULD ... BECAUSE to encourage the author
> to justify the SHOULD. I suspect that this would reduce the
> number of SHOULDs, that would be better as MAYs, due to the
> author's personal preference.

I think 1122 and 1123 did this very well.  State the general requirement =
briefly in terms of MUST or SHOULD or whatever, then follow that by an =
explanation written in normal language.

What I see far too often these days is an attempt to write both =
complicated requirements and the explanations in terms of 2119 =
conditional keywords.   This makes the requirements difficult for an =
implementor to understand and perhaps more ambiguous than was intended.  =
 =20

> My impression is that the 2119 limitation on MUST and SHOULD for
> only necessary protocol features is sometimes forgotten.

This is actually one case where I think 2119 misstated things.   The =
problem is that it's not just protocol features (as viewed on the wire) =
that matter in practice.  SHOULD and its friends are really useful for =
cases where you can't precisely nail down what should happen on every =
particular platform on which the protocol might be implemented, but it's =
quite reasonable to state the intent.

Keith


From eburger@standardstrack.com  Tue Aug 30 09:45:23 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 643BC21F8D9D for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Pfb0NXKpwbS for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 09:45:22 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 22DE321F8D8D for <ietf@ietf.org>; Tue, 30 Aug 2011 09:45:08 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=V7zX/ev6IyUtiaeGPUoS/2fxdvmXrEoFOXhjoodcPK9M4GCUQamPFTs0kB+p5ZTJ/124Or+AhTRiS4CpxIMP4kwfYA6/kbxbZGRhZ3uk3q8GqWO3+YVEG3ZdX4jFVHs9;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyRSM-0004Ih-N0; Tue, 30 Aug 2011 09:46:35 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-34--739337066; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
Date: Tue, 30 Aug 2011 12:46:35 -0400
Message-Id: <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 16:45:23 -0000

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

Can you give an example of where a dangling SHOULD makes sense?  Most =
often I see something like:
	SHOULD implement security
meaning
	SHOULD implement security, unless you do not feel like it or are =
in an authoritarian regime that bans security


On Aug 30, 2011, at 12:11 PM, Keith Moore wrote:

> On Aug 30, 2011, at 12:06 PM, Marc Petit-Huguenin wrote:
>=20
>> The meaning of SHOULD is clear for the authors (it "mean[s] that =
there may exist
>> valid reasons in particular circumstances to ignore a particular =
item, but the
>> full implications must be understood and carefully weighed before =
choosing a
>> different course."), the problem is that some implementers use a =
different
>> meaning (I do not have to implement this if it is inconvenient or =
difficult for
>> me to implement), vendors another one (SHOULD gave us the right to =
not implement
>> it).  I even read somewhere, perhaps on this list, about a vendor =
that rejected
>> any bug report against a SHOULD.  Conditional MUST, in my opinion, =
does not have
>> this problem.
>=20
> But conditional MUST has other problems, namely that you have to =
enumerate the exceptions for the MUST, and that's not always practical.
>=20
> Implementors who think that SHOULD gives them a free pass to avoid =
implementing something that's needed to interoperate are misreading =
2119.  But document editors should avoid using SHOULD for cases where =
failure to implement the requirement will result in interoperability =
failure.
>=20
> I could see maybe posting an erratum or a brief update to 2119, but I =
think that reopening that document in general is a Very bad Idea.  And =
for existing documents that misuse SHOULD, the appropriate thing to do =
is to update those documents or post errata to those documents, rather =
than try to retroactively change the meaning of the keywords in those =
documents.
>=20
> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-34--739337066
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxNjQ2MzVaMCMGCSqGSIb3DQEJ
BDEWBBQGaBkpZ9prTDEwoCqmMQCQw0MBxjCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAC09MjIu8SMeBXesq696K/2uKBIvSa9IxX7ZyTd8PuJed2zn
ZsJybKZTZXyq8K5kuEDuS6yXWuhMVOeJNGIcWYCghzHyYT9zZd4vwQYltTx284ef6CEbDg0chS/p
YlcnZY1nIynW9LAzRneRGx5zp8B54tQqRdlCRrwPE1xyfhy6pzEjvNS+7m2ROqKzXseVRTz+ytIU
PuqLrEI2h+Iqax791vqHXJpufQUFg4TSE/Pz800ix1UusgkeRN0yAUbFk4JAJMoIHWRSfaN+JnjH
J5ha5Q40IqSsDsVxtAyyPAdawqg6+mSmFRVXPaVdaYhy777gVBxGqP2E9sjo96kzUJYAAAAAAAA=

--Apple-Mail-34--739337066--

From spencer@wonderhamster.org  Tue Aug 30 10:10:28 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D578521F8CF4 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.121
X-Spam-Level: 
X-Spam-Status: No, score=-102.121 tagged_above=-999 required=5 tests=[AWL=0.477, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id voL3otDb296S for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:10:28 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id DE89821F8DC6 for <ietf@ietf.org>; Tue, 30 Aug 2011 10:10:27 -0700 (PDT)
Received: from S73602b ([50.58.7.243]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MDz31-1Qzpy32nAV-00H4Jh; Tue, 30 Aug 2011 13:11:49 -0400
Message-ID: <3DC2C232DD4B4C19A55477444CAFB3F9@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Keith Moore" <moore@network-heretics.com>, "Marc Petit-Huguenin" <petithug@acm.org>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com><91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com><4E5CF034.6040308@acm.org><2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com><4E5CF98A.5090204@acm.org><54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com><4E5D0410.1080000@acm.org><4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com><4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
Subject: Re: 2119bis
Date: Tue, 30 Aug 2011 12:11:43 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_289F_01CC670D.FB80CDA0"
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.6109
X-Provags-ID: V02:K0:H0Dnae3zitKiYIzubEtg9nw5XrrW6wXLPcX/gvyJhkN o97Hka3Zmy7Olq6gDZrq3LDyHw5xkgHM8S/FawKhhlVx9DX3hY HoZcY5DrUY7lygSUWQM38gYElfGCLm5s0S7X5jK226plVtwqjv dnYttwmD0f/eHnIwYSGqTaJQpGgHnwrYZGKa1qR0GOfY4s35dx /vaNnFSokSFaalWf6G3EWHcdVvXqYRwqM8BIh+6r77NRrr1Bod MEW5jQFf5Rak1sKS5uJ5NvpUY8X3iSybYzRxh0HA+LR0iQDrM9 36972ERuKJwP5XZlzMXf0+EJyUZu0qZ0zJ6edj26NEfGynsiPd fhUMwHGkvxCadhl1o0WPgw2kDFPeLs/cCLjvpXMV8
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 17:10:28 -0000

This is a multi-part message in MIME format.

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

Umm, wait. I'm confused.

The boilerplate in existing documents points to 2119, right? and the =
updated boilerplate would point to this spec, if approved, right? so =
we're not retroactively changing the meaning of anything, right?

What am I missing?

Spencer
  ----- Original Message -----=20
  From: Keith Moore=20
  To: Marc Petit-Huguenin=20
  Cc: IETF discussion list ; Eric Burger=20
  Sent: Tuesday, August 30, 2011 11:11 AM
  Subject: Re: 2119bis


  I could see maybe posting an erratum or a brief update to 2119, but I =
think that reopening that document in general is a Very bad Idea.  And =
for existing documents that misuse SHOULD, the appropriate thing to do =
is to update those documents or post errata to those documents, rather =
than try to retroactively change the meaning of the keywords in those =
documents.


  Keith




-------------------------------------------------------------------------=
-----


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

------=_NextPart_000_289F_01CC670D.FB80CDA0
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.19088">
<STYLE></STYLE>
</HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space"=20
bgColor=3D#ffffff>
<DIV><FONT size=3D2>Umm, wait. I'm confused.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>The boilerplate in existing documents points to =
2119, right?=20
and the updated boilerplate would point to this spec, if approved, =
right? so=20
we're not retroactively changing the meaning of anything, =
right?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>What am I missing?</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=3Dmoore@network-heretics.com=20
  href=3D"mailto:moore@network-heretics.com">Keith Moore</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dpetithug@acm.org =

  href=3D"mailto:petithug@acm.org">Marc Petit-Huguenin</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A title=3Dietf@ietf.org=20
  href=3D"mailto:ietf@ietf.org">IETF discussion list</A> ; <A=20
  title=3Deburger@standardstrack.com =
href=3D"mailto:eburger@standardstrack.com">Eric=20
  Burger</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, August 30, 2011 =
11:11=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: 2119bis</DIV>
  <DIV><BR></DIV>
  <DIV>
  <DIV>I could see maybe posting an erratum or a brief update to 2119, =
but I=20
  think that reopening that document in general is a Very bad Idea. =
&nbsp;And=20
  for existing documents that misuse SHOULD, the appropriate thing to do =
is to=20
  update those documents or post errata to those documents, rather than =
try to=20
  retroactively change the meaning of the keywords in those=20
  documents.</DIV></DIV>
  <DIV><BR></DIV>
  <DIV>Keith</DIV>
  <DIV><BR></DIV>
  <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_289F_01CC670D.FB80CDA0--


From sant9442@gmail.com  Tue Aug 30 10:29:14 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61A6621F8D48 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JnqGjY9w6tlo for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:29:13 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id A3CDB21F8D41 for <ietf@ietf.org>; Tue, 30 Aug 2011 10:29:13 -0700 (PDT)
Received: by yie12 with SMTP id 12so5383392yie.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 10:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=EtMY+QAqqDvZvAg1nvYSK0Zh8mNQuONEtrMMckLLVhc=; b=ftygF3GXFT8DtUP5179n90truM5rrC533+9rpaWfCBD3lHvNMBu3sS3AXwlHByRXGx P/BcQJgZooIQbpUy8LIEeYTtG66Jz8d28jOKXdmqMWNaBbA51j3tJL9DYAEU+a9dkr72 eJX4GAnegGQpHn03uJyEbOGuW7lGvrpNrmqkY=
MIME-Version: 1.0
Received: by 10.236.184.134 with SMTP id s6mr15185679yhm.6.1314725441239; Tue, 30 Aug 2011 10:30:41 -0700 (PDT)
Received: by 10.147.136.20 with HTTP; Tue, 30 Aug 2011 10:30:41 -0700 (PDT)
In-Reply-To: <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com> <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com>
Date: Tue, 30 Aug 2011 13:30:41 -0400
Message-ID: <CAEa=Q_WEx+RMbROpDOQmLzePK3fhA3MtumuWra5kFMpcmp7QOg@mail.gmail.com>
Subject: Re: 2119bis
From: HLS <sant9442@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 17:29:14 -0000

In the perfect written technical specification, if you pulled out all
the SHOULDs, the protocol still survives.  But if a required
functionality breaks down, then it wasn't well written.

On 8/30/11, Eric Burger <eburger@standardstrack.com> wrote:
> Can you give an example of where a dangling SHOULD makes sense?  Most often
> I see something like:
> 	SHOULD implement security
> meaning
> 	SHOULD implement security, unless you do not feel like it or are in an
> authoritarian regime that bans security
>
>
> On Aug 30, 2011, at 12:11 PM, Keith Moore wrote:
>
>> On Aug 30, 2011, at 12:06 PM, Marc Petit-Huguenin wrote:
>>
>>> The meaning of SHOULD is clear for the authors (it "mean[s] that there
>>> may exist
>>> valid reasons in particular circumstances to ignore a particular item,
>>> but the
>>> full implications must be understood and carefully weighed before
>>> choosing a
>>> different course."), the problem is that some implementers use a
>>> different
>>> meaning (I do not have to implement this if it is inconvenient or
>>> difficult for
>>> me to implement), vendors another one (SHOULD gave us the right to not
>>> implement
>>> it).  I even read somewhere, perhaps on this list, about a vendor that
>>> rejected
>>> any bug report against a SHOULD.  Conditional MUST, in my opinion, does
>>> not have
>>> this problem.
>>
>> But conditional MUST has other problems, namely that you have to enumerate
>> the exceptions for the MUST, and that's not always practical.
>>
>> Implementors who think that SHOULD gives them a free pass to avoid
>> implementing something that's needed to interoperate are misreading 2119.
>> But document editors should avoid using SHOULD for cases where failure to
>> implement the requirement will result in interoperability failure.
>>
>> I could see maybe posting an erratum or a brief update to 2119, but I
>> think that reopening that document in general is a Very bad Idea.  And for
>> existing documents that misuse SHOULD, the appropriate thing to do is to
>> update those documents or post errata to those documents, rather than try
>> to retroactively change the meaning of the keywords in those documents.
>>
>> Keith
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>
>


-- 
hls

From moore@network-heretics.com  Tue Aug 30 10:49:16 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7388021F8D70 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.602
X-Spam-Level: 
X-Spam-Status: No, score=-3.602 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVnjX0t549kc for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:49:15 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 91B0021F8D5C for <ietf@ietf.org>; Tue, 30 Aug 2011 10:49:15 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8186220E84; Tue, 30 Aug 2011 13:50:43 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 30 Aug 2011 13:50:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=KJk MNpRSuNcu1rAL9dLFhEPUv94=; b=Iq6Lpyi4j4OjjSobqo2WIjFVHVumj9WUDTc Gn58bISkDtFMh1Tyuq4H8+UwNQgNWZy3hhVP8OzFEgt2wFhL5VTOiPsYnXCi+p8i MPqCxu/fRAQl0vO9TMnQ08nTiq7fx5Ew/uosPoNcR6e3fSyIGoAyTg35+AOHRlzg YbwV30yE=
X-Sasl-enc: tX7CS77zsQQFKCrHA77n2etqLAmxu41UiVAV3Zt1mdNs 1314726643
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 43515B20303; Tue, 30 Aug 2011 13:50:43 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-54--735489954
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com>
Date: Tue, 30 Aug 2011 13:50:42 -0400
Message-Id: <2844326D-A102-4296-8DAC-EE668293DC10@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 17:49:16 -0000

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

On Aug 30, 2011, at 12:46 PM, Eric Burger wrote:

> Can you give an example of where a dangling SHOULD makes sense?  Most =
often I see something like:
> 	SHOULD implement security
> meaning
> 	SHOULD implement security, unless you do not feel like it or are =
in an authoritarian regime that bans security

That wording doesn't make any sense.  Security implementation should =
almost always be a MUST, regardless of what any particular government =
might say.  We shouldn't relax the security requirements of our =
protocols because of brain-damaged governments (and I include my own =
country's government in that list).  =20

In cases like this it's sometimes important to distinguish between =
implementation and use.  "MUST implement, SHOULD use" is a common =
compromise.

Note also that MUST doesn't mean "you have to do this".   It means "if =
you don't do this, you don't comply with the specification".

I don't think the example above is a typical use of SHOULD, though it =
might be too common.

Keith


--Apple-Mail-54--735489954
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><div>On Aug 30, 2011, at 12:46 PM, Eric Burger wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Can you give =
an example of where a dangling SHOULD makes sense? &nbsp;Most often I =
see something like:<br><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>SHOULD implement =
security<br>meaning<br><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>SHOULD implement security, unless =
you do not feel like it or are in an authoritarian regime that bans =
security</span></blockquote></div><br><div>That wording doesn't make any =
sense. &nbsp;Security implementation should almost always be a MUST, =
regardless of what any particular government might say. &nbsp;We =
shouldn't relax the security requirements of our protocols because of =
brain-damaged governments (and I include my own country's government in =
that list). &nbsp; &nbsp;</div><div><br></div><div>In cases like this =
it's sometimes important to distinguish between implementation and use. =
&nbsp;"MUST implement, SHOULD use" is a common =
compromise.</div><div><br></div><div>Note also that MUST doesn't mean =
"you have to do this". &nbsp; It means "if you don't do this, you don't =
comply with the specification".</div><div><br></div><div>I don't think =
the example above is a typical use of SHOULD, though it might be too =
common.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-54--735489954--

From moore@network-heretics.com  Tue Aug 30 10:51:29 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A33421F8CBF for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.602
X-Spam-Level: 
X-Spam-Status: No, score=-3.602 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYvEzgyqpaRJ for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 10:51:28 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 738B221F8CBC for <ietf@ietf.org>; Tue, 30 Aug 2011 10:51:28 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 606032072B; Tue, 30 Aug 2011 13:52:56 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 30 Aug 2011 13:52:56 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=ydx gaBPDde7LwqqqkXt+q3XY4FE=; b=NHdGz89RCEXHEcKBaAeizzDseZkMB+cg3pB FHoytdAsLhDC6RmthtQmFkFdPOY9/5f26e8joNNUmVjTS+dejMWpPBUO2xCK5PxF 6TXZzRNi5HMCKLdTyLGuNIUjI8gwEP/19uNYoTtUuGy4Z6uv5cUgUEZUUZWMvqlJ GnpNdeXk=
X-Sasl-enc: Jt/BxPnYDEVtkF/For8UHtU+ytReT3CcXzHW07kYkoOH 1314726776
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 1E7D4B202B1; Tue, 30 Aug 2011 13:52:56 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-55--735357009
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <3DC2C232DD4B4C19A55477444CAFB3F9@china.huawei.com>
Date: Tue, 30 Aug 2011 13:52:55 -0400
Message-Id: <C84BD513-97C8-48D3-9A35-E82DA8944CD8@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com><91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com><4E5CF034.6040308@acm.org><2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com><4E5CF98A.5090204@acm.org><54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com><4E5D0410.1080000@acm.org><4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com><4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <3DC2C232DD4B4C19A55477444CAFB3F9@china.huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 17:51:29 -0000

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

On Aug 30, 2011, at 1:11 PM, Spencer Dawkins wrote:

> Umm, wait. I'm confused.
> =20
> The boilerplate in existing documents points to 2119, right? and the =
updated boilerplate would point to this spec, if approved, right? so =
we're not retroactively changing the meaning of anything, right?
> =20
> What am I missing?

If 2119 were to be updated, that's how it should work.   If we're going =
to retroactively clarify the meanings of the keywords, that should =
probably be done on a per-document basis.  (here's what we really meant =
when we said SHOULD in RFC XXXX...)

I think it's very premature to assume that 2119 will be updated.

Keith


--Apple-Mail-55--735357009
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><div>On Aug 30, 2011, at 1:11 PM, Spencer Dawkins wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
bgcolor=3D"#ffffff" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><font size=3D"2">Umm,=
 wait. I'm confused.</font></div><div><font =
size=3D"2"></font>&nbsp;</div><div><font size=3D"2">The boilerplate in =
existing documents points to 2119, right? and the updated boilerplate =
would point to this spec, if approved, right? so we're not retroactively =
changing the meaning of anything, right?</font></div><div><font =
size=3D"2"></font>&nbsp;</div><div><font size=3D"2">What am I =
missing?</font></div></div></span></blockquote><br></div><div>If 2119 =
were to be updated, that's how it should work. &nbsp; If we're going to =
retroactively clarify the meanings of the keywords, that should probably =
be done on a per-document basis. &nbsp;(here's what we really meant when =
we said SHOULD in RFC XXXX...)</div><div><br></div><div>I think it's =
very premature to assume that 2119 will be =
updated.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-55--735357009--

From msk@cloudmark.com  Tue Aug 30 11:00:41 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2851521F8E04 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.041
X-Spam-Level: 
X-Spam-Status: No, score=-103.041 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dh80Vuv0tLzV for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:00:40 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 11C4821F8E05 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:00:38 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Tue, 30 Aug 2011 11:02:05 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Tue, 30 Aug 2011 11:02:04 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: Acxm6uEPbVrAmxCiT2O5IbK6UdtS+gAU+htg
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF997@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net> <F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com> <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com>
In-Reply-To: <CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:00:41 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of H=
LS
> Sent: Tuesday, August 30, 2011 1:00 AM
> To: IETF discussion list
> Subject: Re: 2119bis
>=20
> > I had never thought of this before.  I kind of like the idea, especiall=
y since SHOULD
> > has always meant "MUST unless you really know what you're doing"
>=20
> Such an odd reading.  Does it mean you MUST because you could not
> handle it otherwise?

I'm sorry if you think it's odd, but it's correct.  Read RFC2119 again:

3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

From eburger@standardstrack.com  Tue Aug 30 11:01:44 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B0C21F8D0D for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:01:44 -0700 (PDT)
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.084, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPhEzkjTFmR0 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:01:43 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9CD21F8CBD for <ietf@ietf.org>; Tue, 30 Aug 2011 11:01:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=eflOL+BumJHD8NcCM5GfxSja24ISnR//8/kcossmC77MafWx21Nrgq0ixkxCYOH7jbBMO1b5jt1HrUnslxifegSMVCnkVMA8GccJgQpZULR3AXaE+lz9XXLTKxZjl2tn;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QySeG-00064A-HU for ietf@ietf.org; Tue, 30 Aug 2011 11:02:56 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-42--734754949; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 2119bis
Date: Tue, 30 Aug 2011 14:02:57 -0400
In-Reply-To: <2844326D-A102-4296-8DAC-EE668293DC10@network-heretics.com>
To: IETF discussion list <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com> <2844326D-A102-4296-8DAC-EE668293DC10@network-heretics.com>
Message-Id: <E8A2F0DB-0E46-41E7-AE78-F6E1704DB0E1@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:01:44 -0000

--Apple-Mail-42--734754949
Content-Type: multipart/alternative;
	boundary=Apple-Mail-41--734754994


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

Note the language
> "MUST implement, SHOULD use" is a common compromise.
                                          ^^^^^^^^^^^

This is my heartache.  Why is it a compromise?  Most use of SHOULD I run =
into in WG's is either this precise one:
	I don't want to make this a MUST use, because I will have =
deployments *THAT ARE NOT FOR THE INTERNET* but I want to market them as =
if they were.
Example: instant messaging systems for enterprises where tapping is a =
legal requirement, not something to be avoided.
Example: instant messaging systems deployed where governments want to do =
warrantless, undetectable tapping

I would offer neither of these examples are Internet examples, and we =
should get some iron underpants on and say so.

Internet protocols need Internet protections.

SHOULD should neither be a crutch for making a proprietary protocol look =
like an Internet protocol nor for making two proprietary protocols look =
like a single, Internet protocol.

On Aug 30, 2011, at 1:50 PM, Keith Moore wrote:

> On Aug 30, 2011, at 12:46 PM, Eric Burger wrote:
>=20
>> Can you give an example of where a dangling SHOULD makes sense?  Most =
often I see something like:
>> 	SHOULD implement security
>> meaning
>> 	SHOULD implement security, unless you do not feel like it or are =
in an authoritarian regime that bans security
>=20
> That wording doesn't make any sense.  Security implementation should =
almost always be a MUST, regardless of what any particular government =
might say.  We shouldn't relax the security requirements of our =
protocols because of brain-damaged governments (and I include my own =
country's government in that list).   =20
>=20
> In cases like this it's sometimes important to distinguish between =
implementation and use.  "MUST implement, SHOULD use" is a common =
compromise.
>=20
> Note also that MUST doesn't mean "you have to do this".   It means "if =
you don't do this, you don't comply with the specification".
>=20
> I don't think the example above is a typical use of SHOULD, though it =
might be too common.
>=20
> Keith
>=20


--Apple-Mail-41--734754994
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; "><font =
class=3D"Apple-style-span" face=3D"Monaco">Note the =
language</font><div><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><font class=3D"Apple-style-span" =
face=3D"Monaco">"MUST implement, SHOULD use" is a common =
compromise.</font></div></div></blockquote><font =
class=3D"Apple-style-span" face=3D"Monaco">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
^^^^^^^^^^^</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">This is my heartache. &nbsp;Why is it a compromise? =
&nbsp;Most use of SHOULD I run into in WG's is either this precise =
one:</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>I don't want to make this a MUST use, because I will have =
deployments *THAT ARE NOT FOR THE INTERNET* but I want to market them as =
if they were.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">Example: instant messaging systems for enterprises where =
tapping is a legal requirement, not something to be =
avoided.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">Example: instant messaging systems deployed where =
governments want to do warrantless, undetectable =
tapping</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">I would offer neither of these examples are Internet =
examples, and we should get some iron underpants on and say =
so.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">Internet protocols need Internet =
protections.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">SHOULD should neither be a crutch for making a =
proprietary protocol look like an Internet protocol nor for making two =
proprietary protocols look like a single, Internet =
protocol.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font><div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">On Aug 30, 2011, at 1:50 PM, Keith Moore =
wrote:</font></div><font class=3D"Apple-style-span" face=3D"Monaco"><br =
class=3D"Apple-interchange-newline"></font><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><font =
class=3D"Apple-style-span" face=3D"Monaco">On Aug 30, 2011, at 12:46 PM, =
Eric Burger wrote:</font></div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br class=3D"Apple-interchange-newline"></font><blockquote=
 type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-variant: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><font class=3D"Apple-style-span" =
face=3D"Monaco">Can you give an example of where a dangling SHOULD makes =
sense? &nbsp;Most often I see something like:<br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>SHOULD =
implement security<br>meaning<br><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>SHOULD implement security, unless =
you do not feel like it or are in an authoritarian regime that bans =
security</font></span></blockquote></div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font><div><font class=3D"Apple-style-span" =
face=3D"Monaco">That wording doesn't make any sense. &nbsp;Security =
implementation should almost always be a MUST, regardless of what any =
particular government might say. &nbsp;We shouldn't relax the security =
requirements of our protocols because of brain-damaged governments (and =
I include my own country's government in that list). &nbsp; =
&nbsp;</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">In cases like this it's sometimes important to =
distinguish between implementation and use. &nbsp;"MUST implement, =
SHOULD use" is a common compromise.</font></div><div><font =
class=3D"Apple-style-span" face=3D"Monaco"><br></font></div><div><font =
class=3D"Apple-style-span" face=3D"Monaco">Note also that MUST doesn't =
mean "you have to do this". &nbsp; It means "if you don't do this, you =
don't comply with the specification".</font></div><div><font =
class=3D"Apple-style-span" face=3D"Monaco"><br></font></div><div><font =
class=3D"Apple-style-span" face=3D"Monaco">I don't think the example =
above is a typical use of SHOULD, though it might be too =
common.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">Keith</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div></div></blockquote></div><br></div></body=
></html>=

--Apple-Mail-41--734754994--

--Apple-Mail-42--734754949
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxODAyNThaMCMGCSqGSIb3DQEJ
BDEWBBQwJPP4sPTQ69wlwCDbCFoec8UqwzCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAC77AOXNWprT1ATNd5vxzg75vmCIDQw9xwlYV7Hxud1BdZ3E
QZR3W5JhfRY6Ng07C+PBGuSK2N1qs1mV/Pe+duXAKMfzSNPAr+3gcruKYPZqR/R0pZo2PTiOrZMz
AiyUWO4quUNmYyiJ2MhTNMx6BCG85FVqKsl0QRPYzG4p27f7SR2yWgTH3ChYcr1nsDpeGYqqqjGi
Tapc7u7Kodnn/HOj7L/yacNXK26QMq0Ir8MqE9Z9ignLjDZk8beHi9Cle3X54cXD4Y9jqy7kOOXC
gunjgOb7yNkUaCgGdEKCLlVGLiTS+lI39V5g34V5jSyBxic2SgCBEQx41zAPMLGb4V8AAAAAAAA=

--Apple-Mail-42--734754949--

From msk@cloudmark.com  Tue Aug 30 11:02:39 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 312F821F8D0D for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.538
X-Spam-Level: 
X-Spam-Status: No, score=-103.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8rnLoBiw636 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:02:38 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id BB63621F8B35 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:02:38 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Tue, 30 Aug 2011 11:04:06 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Tue, 30 Aug 2011 11:04:06 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxnIg/+iGSYswiiR325BdY4+cOYbQAHRR2Q
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF998@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com> <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com>
In-Reply-To: <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:02:39 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of K=
eith Moore
> Sent: Tuesday, August 30, 2011 7:35 AM
> To: Marc Petit-Huguenin
> Cc: IETF discussion list; Eric Burger
> Subject: Re: 2119bis
>=20
> To the extent that SHOULD is causing interoperability problems, it may
> be that some authors are misusing SHOULD.  But it's not an inherent
> problem with SHOULD.
>=20
> [...]
>=20
> I'm an implementor also, and I've found SHOULD to be very helpful.

+1 to both points.

From petithug@acm.org  Tue Aug 30 11:12:23 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C489821F8DAB for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KnXUL6Souphr for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:12:22 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 16A7A21F8CB3 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:12:21 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 99673202C8; Tue, 30 Aug 2011 20:09:10 +0200 (CEST)
Message-ID: <4E5D285A.6000804@acm.org>
Date: Tue, 30 Aug 2011 11:13:46 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
In-Reply-To: <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:12:23 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/30/2011 09:11 AM, Keith Moore wrote:
> On Aug 30, 2011, at 12:06 PM, Marc Petit-Huguenin wrote:
> 
>> The meaning of SHOULD is clear for the authors (it "mean[s] that there may exist
>> valid reasons in particular circumstances to ignore a particular item, but the
>> full implications must be understood and carefully weighed before choosing a
>> different course."), the problem is that some implementers use a different
>> meaning (I do not have to implement this if it is inconvenient or difficult for
>> me to implement), vendors another one (SHOULD gave us the right to not implement
>> it).  I even read somewhere, perhaps on this list, about a vendor that rejected
>> any bug report against a SHOULD.  Conditional MUST, in my opinion, does not have
>> this problem.
> 
> But conditional MUST has other problems, namely that you have to enumerate the
> exceptions for the MUST, and that's not always practical.
> 

No, you just have to list the known cases.  Here's an example of a SHOULD that
creates a lot of problems.  This is from RFC 1889 (RFC 3550 has a slightly
better statement, but the damage was done by the time it was published):

"Functions 1-3 [i.e. RTCP feedback, RTCP CNAME and RTCP rate limit] are
mandatory when RTP is used in the IP multicast environment, and are recommended
for all environments."

If I remember correctly the reason was that it is not always possible for the
receiver to send back the RR packets, for example on satellite links.

But VoIP implementations more or less all decided to not implement RTCP using
this statement (feedback is very important even on unicast RTP for congestion
control).

A conditional MUST could have been written this way:

"Functions 1-3 are mandatory for all environments that permit a channel back to
the sender."

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5dKFgACgkQ9RoMZyVa61d7ZACgn3U/lqN14YWy3TPGArqtN7AO
yrwAmwcccGVHNOm0AsbeUIdj/0MxFG1p
=91cE
-----END PGP SIGNATURE-----

From msk@cloudmark.com  Tue Aug 30 11:13:05 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D1C721F8E1F for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.534
X-Spam-Level: 
X-Spam-Status: No, score=-103.534 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4LaNILEhc4R for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:13:04 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id BDEFB21F8E1B for <ietf@ietf.org>; Tue, 30 Aug 2011 11:13:04 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Tue, 30 Aug 2011 11:14:32 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Tue, 30 Aug 2011 11:14:31 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxnPx3cZYp/wQ7rS1yvasPR8fwhaAAARhSw
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF99A@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com> <093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com> <2844326D-A102-4296-8DAC-EE668293DC10@network-heretics.com> <E8A2F0DB-0E46-41E7-AE78-F6E1704DB0E1@standardstrack.com>
In-Reply-To: <E8A2F0DB-0E46-41E7-AE78-F6E1704DB0E1@standardstrack.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_F5833273385BB34F99288B3648C4F06F13512DF99AEXCHC2corpclo_"
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:13:05 -0000

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

It seems to me RFC2119bis might benefit from some consensus text on what pr=
oper use of each is, beyond defining their respective meanings.  From the d=
iscussion, this is obviously true for SHOULD at least.  The discussion arou=
nd use of MAY in RFC2119 is fairly thorough, so maybe SHOULD needs to be si=
milarly expanded.  And I suspect some distillation of this discussion might=
 provide some ideal text.

-MSK

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Eri=
c Burger
Sent: Tuesday, August 30, 2011 11:03 AM
To: IETF discussion list
Subject: Re: 2119bis

Note the language
"MUST implement, SHOULD use" is a common compromise.
                                          ^^^^^^^^^^^

This is my heartache.  Why is it a compromise?  Most use of SHOULD I run in=
to in WG's is either this precise one:
    I don't want to make this a MUST use, because I will have deployments *=
THAT ARE NOT FOR THE INTERNET* but I want to market them as if they were.
Example: instant messaging systems for enterprises where tapping is a legal=
 requirement, not something to be avoided.
Example: instant messaging systems deployed where governments want to do wa=
rrantless, undetectable tapping

I would offer neither of these examples are Internet examples, and we shoul=
d get some iron underpants on and say so.

Internet protocols need Internet protections.

SHOULD should neither be a crutch for making a proprietary protocol look li=
ke an Internet protocol nor for making two proprietary protocols look like =
a single, Internet protocol.

On Aug 30, 2011, at 1:50 PM, Keith Moore wrote:


On Aug 30, 2011, at 12:46 PM, Eric Burger wrote:


Can you give an example of where a dangling SHOULD makes sense?  Most often=
 I see something like:
    SHOULD implement security
meaning
    SHOULD implement security, unless you do not feel like it or are in an =
authoritarian regime that bans security

That wording doesn't make any sense.  Security implementation should almost=
 always be a MUST, regardless of what any particular government might say. =
 We shouldn't relax the security requirements of our protocols because of b=
rain-damaged governments (and I include my own country's government in that=
 list).

In cases like this it's sometimes important to distinguish between implemen=
tation and use.  "MUST implement, SHOULD use" is a common compromise.

Note also that MUST doesn't mean "you have to do this".   It means "if you =
don't do this, you don't comply with the specification".

I don't think the example above is a typical use of SHOULD, though it might=
 be too common.

Keith



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Monaco;
	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","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-tab-span
	{mso-style-name:apple-tab-span;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: space;-webkit=
-line-break: after-white-space'><div class=3DWordSection1><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'>It seems to me RFC2119bis might benefit from some consensus text=
 on what proper use of each is, beyond defining their respective meanings.&=
nbsp; From the discussion, this is obviously true for SHOULD at least.&nbsp=
; The discussion around use of MAY in RFC2119 is fairly thorough, so maybe =
SHOULD needs to be similarly expanded.&nbsp; And I suspect some distillatio=
n of this discussion might provide some ideal text.<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>-MSK<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize: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;paddin=
g:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4D=
F 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ietf-bounces@ie=
tf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>Eric Burger<br><b=
>Sent:</b> Tuesday, August 30, 2011 11:03 AM<br><b>To:</b> IETF discussion =
list<br><b>Subject:</b> Re: 2119bis<o:p></o:p></span></p></div></div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'fon=
t-family:"Monaco","serif"'>Note the language</span><o:p></o:p></p><div><blo=
ckquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=
=3DMsoNormal><span style=3D'font-family:"Monaco","serif"'>&quot;MUST implem=
ent, SHOULD use&quot; is a common compromise.</span><o:p></o:p></p></div></=
div></blockquote><p class=3DMsoNormal><span style=3D'font-family:"Monaco","=
serif"'>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; ^^^^^^^^^^^</span><o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-family:=
"Monaco","serif"'>This is my heartache. &nbsp;Why is it a compromise? &nbsp=
;Most use of SHOULD I run into in WG's is either this precise one:</span><o=
:p></o:p></p></div><div><p class=3DMsoNormal><span class=3Dapple-tab-span><=
span style=3D'font-family:"Monaco","serif"'>&nbsp;&nbsp;&nbsp; </span></spa=
n><span style=3D'font-family:"Monaco","serif"'>I don't want to make this a =
MUST use, because I will have deployments *THAT ARE NOT FOR THE INTERNET* b=
ut I want to market them as if they were.</span><o:p></o:p></p></div><div><=
p class=3DMsoNormal><span style=3D'font-family:"Monaco","serif"'>Example: i=
nstant messaging systems for enterprises where tapping is a legal requireme=
nt, not something to be avoided.</span><o:p></o:p></p></div><div><p class=
=3DMsoNormal><span style=3D'font-family:"Monaco","serif"'>Example: instant =
messaging systems deployed where governments want to do warrantless, undete=
ctable tapping</span><o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-family:"M=
onaco","serif"'>I would offer neither of these examples are Internet exampl=
es, and we should get some iron underpants on and say so.</span><o:p></o:p>=
</p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p clas=
s=3DMsoNormal><span style=3D'font-family:"Monaco","serif"'>Internet protoco=
ls need Internet protections.</span><o:p></o:p></p></div><div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><span style=3D=
'font-family:"Monaco","serif"'>SHOULD should neither be a crutch for making=
 a proprietary protocol look like an Internet protocol nor for making two p=
roprietary protocols look like a single, Internet protocol.</span><o:p></o:=
p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p cla=
ss=3DMsoNormal><span style=3D'font-family:"Monaco","serif"'>On Aug 30, 2011=
, at 1:50 PM, Keith Moore wrote:</span><o:p></o:p></p></div><p class=3DMsoN=
ormal><span style=3D'font-family:"Monaco","serif"'><br><br></span><o:p></o:=
p></p><div><div><div><p class=3DMsoNormal><span style=3D'font-family:"Monac=
o","serif"'>On Aug 30, 2011, at 12:46 PM, Eric Burger wrote:</span><o:p></o=
:p></p></div><p class=3DMsoNormal><span style=3D'font-family:"Monaco","seri=
f"'><br><br></span><o:p></o:p></p><p class=3DMsoNormal><span class=3Dapple-=
style-span><span style=3D'font-family:"Monaco","serif"'>Can you give an exa=
mple of where a dangling SHOULD makes sense? &nbsp;Most often I see somethi=
ng like:</span></span><span style=3D'font-family:"Monaco","serif"'><br><spa=
n class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp; </span><span class=3Dapple-styl=
e-span>SHOULD implement security</span><br><span class=3Dapple-style-span>m=
eaning</span><br><span class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp; </span><sp=
an class=3Dapple-style-span>SHOULD implement security, unless you do not fe=
el like it or are in an authoritarian regime that bans security</span></spa=
n><o:p></o:p></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p cl=
ass=3DMsoNormal><span style=3D'font-family:"Monaco","serif"'>That wording d=
oesn't make any sense. &nbsp;Security implementation should almost always b=
e a MUST, regardless of what any particular government might say. &nbsp;We =
shouldn't relax the security requirements of our protocols because of brain=
-damaged governments (and I include my own country's government in that lis=
t). &nbsp; &nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><span style=3D'font-family=
:"Monaco","serif"'>In cases like this it's sometimes important to distingui=
sh between implementation and use. &nbsp;&quot;MUST implement, SHOULD use&q=
uot; is a common compromise.</span><o:p></o:p></p></div><div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><span style=3D'=
font-family:"Monaco","serif"'>Note also that MUST doesn't mean &quot;you ha=
ve to do this&quot;. &nbsp; It means &quot;if you don't do this, you don't =
comply with the specification&quot;.</span><o:p></o:p></p></div><div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><span s=
tyle=3D'font-family:"Monaco","serif"'>I don't think the example above is a =
typical use of SHOULD, though it might be too common.</span><o:p></o:p></p>=
</div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3D=
MsoNormal><span style=3D'font-family:"Monaco","serif"'>Keith</span><o:p></o=
:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></d=
iv><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></htm=
l>=

--_000_F5833273385BB34F99288B3648C4F06F13512DF99AEXCHC2corpclo_--

From moore@network-heretics.com  Tue Aug 30 11:18:10 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD6D21F8E17 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.602
X-Spam-Level: 
X-Spam-Status: No, score=-3.602 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5TyJRA0VPz0Y for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:18:10 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id D55CC21F8E07 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:18:09 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id C479820DB7; Tue, 30 Aug 2011 14:19:37 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 30 Aug 2011 14:19:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=x9j Bn3GD7kWj7n8i0hhURtLYTqA=; b=eEnL2J/d6A4w6O0HqJmSOublfaeYIfnF2Ps m7d/eT5w0kjvqvqEJG8g4/D57YU3pApMO0sxgQh/whF7rUhDCzXuJA3Pb8sT7+sE HRfXnu7NYVX5IkSbIv1w2jtF2osaEubwQPT8EQyofpKkU81XrX/mdZx6XS1NdfQY PHTjS6Es=
X-Sasl-enc: 35x/LBa1i2OJKQrf/VfZtD7ZPWyQC5eDtACcoHu3vIV5 1314728377
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F967B20382; Tue, 30 Aug 2011 14:19:37 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-57--733755155
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <E8A2F0DB-0E46-41E7-AE78-F6E1704DB0E1@standardstrack.com>
Date: Tue, 30 Aug 2011 14:19:37 -0400
Message-Id: <F63C4B15-7744-4498-9060-E3706289A8E8@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com> <2844326D-A102-4296-8DAC-EE668293DC10@network-heretics.com> <E8A2F0DB-0E46-41E7-AE78-F6E1704DB0E1@standardstra ck.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:18:10 -0000

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


On Aug 30, 2011, at 2:02 PM, Eric Burger wrote:

> Note the language
>> "MUST implement, SHOULD use" is a common compromise.
>                                           ^^^^^^^^^^^
>=20
> This is my heartache.  Why is it a compromise?  Most use of SHOULD I =
run into in WG's is either this precise one:
> 	I don't want to make this a MUST use, because I will have =
deployments *THAT ARE NOT FOR THE INTERNET* but I want to market them as =
if they were.
> Example: instant messaging systems for enterprises where tapping is a =
legal requirement, not something to be avoided.
> Example: instant messaging systems deployed where governments want to =
do warrantless, undetectable tapping
>=20
> I would offer neither of these examples are Internet examples, and we =
should get some iron underpants on and say so.

Mumble.  I fundamentally don't buy the argument that things that are =
used on both local networks and the Internet should not be subject to =
Internet-strength security.  =20

And even where recording is a legal requirement, that's NOT an argument =
for sending traffic in cleartext or with weak encryption.  That might be =
an argument for some kind of backdoor - e.g. a trusted proxy or key =
escrow or whatever, but it's not an argument for making the traffic =
available for those without a legal need to see it.

> SHOULD should neither be a crutch for making a proprietary protocol =
look like an Internet protocol nor for making two proprietary protocols =
look like a single, Internet protocol.

agree.

Keith


--Apple-Mail-57--733755155
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 Aug 30, 2011, at 2:02 PM, Eric Burger wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><font class=3D"Apple-style-span" =
face=3D"Monaco">Note the language</font><div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><font =
class=3D"Apple-style-span" face=3D"Monaco">"MUST implement, SHOULD use" =
is a common compromise.</font></div></div></blockquote><font =
class=3D"Apple-style-span" face=3D"Monaco">&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
^^^^^^^^^^^</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">This is my heartache. &nbsp;Why is it a compromise? =
&nbsp;Most use of SHOULD I run into in WG's is either this precise =
one:</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>I don't want to make this a MUST use, because I will have =
deployments *THAT ARE NOT FOR THE INTERNET* but I want to market them as =
if they were.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">Example: instant messaging systems for enterprises where =
tapping is a legal requirement, not something to be =
avoided.</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">Example: instant messaging systems deployed where =
governments want to do warrantless, undetectable =
tapping</font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco"><br></font></div><div><font class=3D"Apple-style-span" =
face=3D"Monaco">I would offer neither of these examples are Internet =
examples, and we should get some iron underpants on and say =
so.</font></div></div></blockquote><div><br></div>Mumble. &nbsp;I =
fundamentally don't buy the argument that things that are used on both =
local networks and the Internet should not be subject to =
Internet-strength security. &nbsp;&nbsp;</div><div><br></div><div>And =
even where recording is a legal requirement, that's NOT an argument for =
sending traffic in cleartext or with weak encryption. &nbsp;That might =
be an argument for some kind of backdoor - e.g. a trusted proxy or key =
escrow or whatever, but it's not an argument for making the traffic =
available for those without a legal need to see =
it.</div><div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><font class=3D"Apple-style-span" =
face=3D"Monaco">SHOULD should neither be a crutch for making a =
proprietary protocol look like an Internet protocol nor for making two =
proprietary protocols look like a single, Internet =
protocol.</font></div></div></blockquote></div><br><div>agree.</div><div><=
br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-57--733755155--

From eburger@standardstrack.com  Tue Aug 30 11:24:54 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1BAD21F8E01 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tu8r2l1TofZf for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:24:53 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 8C6F421F8D62 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:24:49 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=RxKrAcIZ0VuZ2TKw8LXMilSPI/NYOnQz+p728N5mQHhjSLhl2KSI4QvpOXKmisbhakd0uYMhSWbADBz0VVmKanEgHI53CsfrIdv+uT52YOcxJwwMp+qYPsCE6ebEL2kd;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyT0q-00008n-36 for ietf@ietf.org; Tue, 30 Aug 2011 11:26:16 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-46--733352541; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 2119bis
Date: Tue, 30 Aug 2011 14:26:19 -0400
In-Reply-To: <F63C4B15-7744-4498-9060-E3706289A8E8@network-heretics.com>
To: IETF discussion list <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com> <2844326D-A102-4296-8DAC-EE668293DC10@network-heretics.com> <E8A2F0DB-0E46-41E7-AE78-F6E1704DB0E1@standardstra ck.com> <F63C4B15-7744-4498-9060-E3706289A8E8@network-heretics.com>
Message-Id: <AAA1DDCA-2CB5-4163-B04B-87081C778E9A@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:24:54 -0000

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

We violently agree.  However, the most cited reason I get for watering =
down security requirements are what I mentioned below.

On Aug 30, 2011, at 2:19 PM, Keith Moore wrote:

>=20
> On Aug 30, 2011, at 2:02 PM, Eric Burger wrote:
>=20
>> Note the language
>>> "MUST implement, SHOULD use" is a common compromise.
>>                                           ^^^^^^^^^^^
>>=20
>> This is my heartache.  Why is it a compromise?  Most use of SHOULD I =
run into in WG's is either this precise one:
>> 	I don't want to make this a MUST use, because I will have =
deployments *THAT ARE NOT FOR THE INTERNET* but I want to market them as =
if they were.
>> Example: instant messaging systems for enterprises where tapping is a =
legal requirement, not something to be avoided.
>> Example: instant messaging systems deployed where governments want to =
do warrantless, undetectable tapping
>>=20
>> I would offer neither of these examples are Internet examples, and we =
should get some iron underpants on and say so.
>=20
> Mumble.  I fundamentally don't buy the argument that things that are =
used on both local networks and the Internet should not be subject to =
Internet-strength security.  =20
>=20
> And even where recording is a legal requirement, that's NOT an =
argument for sending traffic in cleartext or with weak encryption.  That =
might be an argument for some kind of backdoor - e.g. a trusted proxy or =
key escrow or whatever, but it's not an argument for making the traffic =
available for those without a legal need to see it.
>=20
>> SHOULD should neither be a crutch for making a proprietary protocol =
look like an Internet protocol nor for making two proprietary protocols =
look like a single, Internet protocol.
>=20
> agree.
>=20
> Keith
>=20


--Apple-Mail-46--733352541
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxODI2MjBaMCMGCSqGSIb3DQEJ
BDEWBBS8HetQOlrsGq5+I31B1ey4dxCo6jCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBADHHsYwZ1w+p5ySXv4FKGPPmOoXNgO9pkoKulAzbjRZ3h2Y+
K29lvyfjuI3VOWfktMF86+YltOhEE75pofETBiQbcT17/70zl8hEcy85MSBWGAD9XmNxqIe7qbA3
togzxncam9BslVWjbU3tBPXMi0rZC3g6uw/ty3sUNIEnSN7940NZYpLt+CfoWvlUdwQHiUVpz6D1
M7csUWeQ5sfD5H3rgAy1Ol9jNOzgI/Shxa9yTr7gh5CiRmIhDGPI7bevmyBuKU0ePZqQ+7gdacLc
PhVO4YbAlL7lhUFvfexIHmYCxs1fsYmfyzep3srLzSl7cqr5FN5YLSgm15n1yQurIWAAAAAAAAA=

--Apple-Mail-46--733352541--

From wes@mti-systems.com  Tue Aug 30 11:36:47 2011
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4F6221F8D4E for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fK8tFDzcgNyM for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:36:34 -0700 (PDT)
Received: from omr2.networksolutionsemail.com (omr2.networksolutionsemail.com [205.178.146.52]) by ietfa.amsl.com (Postfix) with ESMTP id 45ABF21F8D07 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:36:34 -0700 (PDT)
Received: from cm-omr8 (mail.networksolutionsemail.com [205.178.146.50]) by omr2.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p7UIbrLj010142 for <ietf@ietf.org>; Tue, 30 Aug 2011 14:37:56 -0400
Authentication-Results: cm-omr8 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [107.49.30.60] ([107.49.30.60:45789] helo=[68.245.171.115]) by cm-omr8 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 96/D1-11933-FFD2D5E4; Tue, 30 Aug 2011 14:37:53 -0400
Message-ID: <4E5D2DFE.1000201@mti-systems.com>
Date: Tue, 30 Aug 2011 14:37:50 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org, Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Limitations in RFC Errata mechanism
References: <4E5CFF6A.30004@gmail.com>
In-Reply-To: <4E5CFF6A.30004@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:36:47 -0000

On 8/30/2011 11:19 AM, Mykyta Yevstifeyev wrote:
> Hello all,
>
> I've observed several problems with submission mechanism for RFC Errata.
> Here they are:
>
> First, we have only two types of errata - Technical or Editorial. In
> presence of
> <http://www.ietf.org/iesg/statement/rfc-metadata-errata.html>, "IESG
> Statement on IESG Processing of RFC Errata concerning RFC Metadata", I
> think the third type is necessary - Metadata.
>


I agree with this part of the proposal, at least.


-- 
Wes Eddy
MTI Systems

From sant9442@gmail.com  Tue Aug 30 11:45:50 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC9BB21F8DDE for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.307
X-Spam-Level: 
X-Spam-Status: No, score=-2.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dQ5Y2FJBUr5V for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:45:50 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4F38D21F8CEA for <ietf@ietf.org>; Tue, 30 Aug 2011 11:45:50 -0700 (PDT)
Received: by ywe9 with SMTP id 9so6828222ywe.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=V1fRuoUWBObmY8b0gYq7rmDkRHcestSSM4nQxk8vYr4=; b=coyLUwc+AkDFNcNQRPQCrIh+FS2o17PSUVfRctdpg2zgwBMyTn/eBF4nqy67+7KoED mLXtRVISduXemhh6ktjU40wke5xRmWEJ2efgrIKDSHqTWA+xCw1t9mvNieLQdBNtVsWn ThfZHNTnSOaGAa6rY16XU5sRb1Dj/fnTp01lY=
Received: by 10.236.189.104 with SMTP id b68mr17219612yhn.13.1314730037127; Tue, 30 Aug 2011 11:47:17 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id f48sm6474419yhh.42.2011.08.30.11.47.16 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Aug 2011 11:47:16 -0700 (PDT)
Sender: HLS <sant9442@gmail.com>
Message-ID: <4E5D3053.70002@winserver.com>
Date: Tue, 30 Aug 2011 14:47:47 -0400
From: hector <gmail.sant9442@winserver.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<2F028B83-789E-4366-B1D9-22BF096B7DD4@mnot.net>	<F5833273385BB34F99288B3648C4F06F13512DF97D@EXCH-C2.corp.cloudmark.com>	<CAEa=Q_W+XntUc+UXouzTQ7u7MpFaBOdsD3sp0ATHbrWmjKm9nQ@mail.gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF997@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF997@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:45:50 -0000

Its not correct if its doesn't state it how you interpreted it. A
recommendation is not a MUST or a mandate, and using a SHOULD as if
its required feature is pretty much guaranteed to cause problems when
this MUST expectation is not met.  Sounds like we are trying to remove
the idea that implementators really don't have "valid" reasons to
ignore it.

IMV, the problem here is that we can't generalized how protocol
recommendations are implemented across the board equally and its not
correct to be begin using this as a mandate for forcing deployment of
what may be deemed unnecessary, controversial and automatically begin
classifying existing minimum requirements implementators as
non-compliant.


Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of HLS
>> Sent: Tuesday, August 30, 2011 1:00 AM
>> To: IETF discussion list
>> Subject: Re: 2119bis
>>
>>> I had never thought of this before.  I kind of like the idea, especially since SHOULD
>>> has always meant "MUST unless you really know what you're doing"
>> Such an odd reading.  Does it mean you MUST because you could not
>> handle it otherwise?
> 
> I'm sorry if you think it's odd, but it's correct.  Read RFC2119 again:
> 
> 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
>    may exist valid reasons in particular circumstances to ignore a
>    particular item, but the full implications must be understood and
>    carefully weighed before choosing a different course.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From adam@nostrum.com  Tue Aug 30 11:48:21 2011
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C607B21F8DF6 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.305
X-Spam-Level: 
X-Spam-Status: No, score=-102.305 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W060IMC2FtM7 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:48:21 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 38C8C21F8D3F for <ietf@ietf.org>; Tue, 30 Aug 2011 11:48:21 -0700 (PDT)
Received: from dn3-110.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 p7UInmvL059073 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 30 Aug 2011 13:49:48 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4E5D30CC.4000009@nostrum.com>
Date: Tue, 30 Aug 2011 13:49:48 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
In-Reply-To: <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:48:21 -0000

On 8/29/11 9:44 PM, Eric Burger wrote:
> Yes, and...
>
> I would offer that for most cases, If Y then MUST X or If Z then MUST NOT X *are* what people usually mean when they say SHOULD.  In the spirit of Say What You Mean, a bare SHOULD at the very least raise an ID-nit, suggesting to the author to turn the statement into the if Y then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
> 	SHOULD send a 1 UNLESS you receive a 0
> really means
> 	UNLESS you receive a 0, one MUST send a 1.
>
> My vision of the UNLESS clause is not necessarily a protocol state, but an environment state.  These are things that I can see fit the SHOULD/UNLESS form:
> 	SHOULD send a 1 UNLESS you are in a walled garden
> 	SHOULD flip bit 27 UNLESS you have a disk
> 	SHOULD NOT explode UNLESS you are a bomb
> are all reasonable SHOULD-level statements.
>
> I would offer that ANY construction of SHOULD without an UNLESS is a MAY.


Eric. Put down the axe and step away from the whetstone. Here, I'll give 
you some text from RFC 3265 to mull.


    deactivated: The subscription has been terminated, but the subscriber
       SHOULD retry immediately with a new subscription.  One primary use
       of such a status code is to allow migration of subscriptions
       between nodes.


Let's examine this use of "SHOULD." If the subscriber doesn't 
re-subscribe, is it an interop issue? No.

Is it in the interest of the implementation to re-subscribe? Yes. At 
least, under most circumstances. Otherwise, they won't get the state 
change notifications they want.

Are there cases in which it makes sense for the subscriber _not_ to 
re-subscribe? Yes, I'm sure there are. It's conceivable that the client 
happens to be shutting down but hasn't gotten around to terminating this 
particular subscription yet. But any such exceptions are highly 
implementation-dependent. Listing them would be useless noise to the 
reader, and senseless text creation for the author.

Does "SHOULD" get abused by some authors in some documents? Of course it 
does. But your crusade to throw out a useful tool just because it has 
been misused on occasion is an extreme over-reaction. I like this tool. 
I use this tool. If you see people misusing it, slap them.

But don't ban the tool.

/a

From eburger@standardstrack.com  Tue Aug 30 11:56:48 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD50621F8D62 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.517
X-Spam-Level: 
X-Spam-Status: No, score=-102.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bogIXjjcAjFJ for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 11:56:48 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id CBF5521F8CD6 for <ietf@ietf.org>; Tue, 30 Aug 2011 11:56:16 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=EauR/n96buInt2kirPMjfHUPlO9/gXw42LyHq0srCkwycbCkS3eINqgK9zvjqmjJewx4qU3F6BH7Q4+7SNoJbtg3a65IHHEeeeMpW3fKaqWJP7lYAuYNmAe6e2IE94lS;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyTVH-0001iR-1K; Tue, 30 Aug 2011 11:57:43 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-56--731469161; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4E5D30CC.4000009@nostrum.com>
Date: Tue, 30 Aug 2011 14:57:43 -0400
Message-Id: <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 18:56:48 -0000

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

What is the difference in this case between SHOULD or MAY?

On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:

> On 8/29/11 9:44 PM, Eric Burger wrote:
>> Yes, and...
>>=20
>> I would offer that for most cases, If Y then MUST X or If Z then MUST =
NOT X *are* what people usually mean when they say SHOULD.  In the =
spirit of Say What You Mean, a bare SHOULD at the very least raise an =
ID-nit, suggesting to the author to turn the statement into the if Y =
then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
>> 	SHOULD send a 1 UNLESS you receive a 0
>> really means
>> 	UNLESS you receive a 0, one MUST send a 1.
>>=20
>> My vision of the UNLESS clause is not necessarily a protocol state, =
but an environment state.  These are things that I can see fit the =
SHOULD/UNLESS form:
>> 	SHOULD send a 1 UNLESS you are in a walled garden
>> 	SHOULD flip bit 27 UNLESS you have a disk
>> 	SHOULD NOT explode UNLESS you are a bomb
>> are all reasonable SHOULD-level statements.
>>=20
>> I would offer that ANY construction of SHOULD without an UNLESS is a =
MAY.
>=20
>=20
> Eric. Put down the axe and step away from the whetstone. Here, I'll =
give you some text from RFC 3265 to mull.
>=20
>=20
>   deactivated: The subscription has been terminated, but the =
subscriber
>      SHOULD retry immediately with a new subscription.  One primary =
use
>      of such a status code is to allow migration of subscriptions
>      between nodes.
>=20
>=20
> Let's examine this use of "SHOULD." If the subscriber doesn't =
re-subscribe, is it an interop issue? No.
>=20
> Is it in the interest of the implementation to re-subscribe? Yes. At =
least, under most circumstances. Otherwise, they won't get the state =
change notifications they want.
>=20
> Are there cases in which it makes sense for the subscriber _not_ to =
re-subscribe? Yes, I'm sure there are. It's conceivable that the client =
happens to be shutting down but hasn't gotten around to terminating this =
particular subscription yet. But any such exceptions are highly =
implementation-dependent. Listing them would be useless noise to the =
reader, and senseless text creation for the author.
>=20
> Does "SHOULD" get abused by some authors in some documents? Of course =
it does. But your crusade to throw out a useful tool just because it has =
been misused on occasion is an extreme over-reaction. I like this tool. =
I use this tool. If you see people misusing it, slap them.
>=20
> But don't ban the tool.
>=20
> /a


--Apple-Mail-56--731469161
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzAxODU3NDNaMCMGCSqGSIb3DQEJ
BDEWBBQcUNLqgUAqPyj+ndvFU5n/lbEYJzCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAA871t2H1MfuhKUQueTdEIAFA0IOTybAmqXvazhfydAV5C8F
pBJzB9HafwrauMGJEcrGp70Xh3T4acD7Hm928iqXX+a5SEiWiMwi2EQzSGGrGoKOCnkBqarIi36F
9hURcOuRTBq3RO65kn7f1hBxmo6IKRStsYQmqMXlRIiv5qXv1iV19AuM9P/KwQsvWqlWqFW7C67c
flGnNx9mpPezX9e0cBqrwF1IexbIaJmplmKvE2I+IX11tAFo17UOz8/81p603uB8Dl+QmOg5RBwY
BDalSiHLVVH5mArLjwKmR9NilThBrJ2AO20kHFv4iDYi1dKbI+bbHS+Host9FCp+E4AAAAAAAAA=

--Apple-Mail-56--731469161--

From adam@nostrum.com  Tue Aug 30 12:06:50 2011
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A678E21F8D33 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.316
X-Spam-Level: 
X-Spam-Status: No, score=-102.316 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0Ua6PByQWgd for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:06:49 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id AA7A221F8D22 for <ietf@ietf.org>; Tue, 30 Aug 2011 12:06:49 -0700 (PDT)
Received: from dn3-110.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 p7UJ8Fg1060728 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 30 Aug 2011 14:08:16 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4E5D351F.8050000@nostrum.com>
Date: Tue, 30 Aug 2011 14:08:15 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "Thomson, Martin" <Martin.Thomson@commscope.com>
Subject: Re: 2119bis -- Tying our hands?
References: <4E5C067A.9080400@stpeter.im> <8B0A9FCBB9832F43971E38010638454F040F1C12B5@SISPE7MB1.commscope.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F040F1C12B5@SISPE7MB1.commscope.com>
Content-Type: multipart/alternative; boundary="------------070109050208080505050102"
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 19:06:50 -0000

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

On 8/30/11 2:23 AM, Thomson, Martin wrote:
> On 2011-08-30 at 07:36:58, Peter Saint-Andre wrote:
>> for long enough, I finally decided to submit an I-D that is intended
>> to obsolete RFC 2119.
> <bike-shed>
> IS THERE ANY CHANCE OF AGREEING THAT SHOUTING IS BAD?  (i.e., Burger's first anti-law.)  As opposed to mandating that requirements ought to be shouted.  Lowercase "must" can be as effective as uppercase as long as it is consistently applied.
> </bike-shed>

You paint that as tongue-in-cheek, but Peter's draft does go down the 
rat-hole of picking out a color scheme for this particular bike shed, 
when doing so is really unwarranted. In addition to the SHOULD & co 
brouhaha, I have serious heartburn over this passage:

    When it is not appropriate to use the conformance terms, authors can
    use a variety of alternative words and phrases, such as: "need to" or
    "mandatory" instead of "MUST"; "ought to" or "strongly encouraged"
    instead of "SHOULD"; and "might" or "discretionary" instead of "MAY".
    To prevent confusion, authors ought to use these alternative words
    and phrases instead of the lowercase versions of the conformance
    terms, and to use the conformance terms only in their uppercase
    versions.



There is no reason to tie authors' hands by restricting them from using 
perfectly good English words just because they happen to be the same 
symbols used by RFC 2119. If we're going down this path, let's scrap 
using MUST/SHOULD/MAY/etc, and formalize our conformance terms with 
symbols that aren't English words.

Because the current suggestion -- which turns RFC writing into the game 
"Taboo" [1], but with incredibly common English words [2] as the 
forbidden list -- is ridiculous on its face.

/a

[1] http://en.wikipedia.org/wiki/Taboo_%28game%29
[2] According to Project Gutenberg, "must" and "may" are among the 100 
words most frequently used in written literature. See 
http://en.wiktionary.org/wiki/Wiktionary:Frequency_lists#Project_Gutenberg

--------------070109050208080505050102
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 8/30/11 2:23 AM, Thomson, Martin wrote:
    <blockquote
cite="mid:8B0A9FCBB9832F43971E38010638454F040F1C12B5@SISPE7MB1.commscope.com"
      type="cite">
      <pre wrap="">On 2011-08-30 at 07:36:58, Peter Saint-Andre wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">for long enough, I finally decided to submit an I-D that is intended 
to obsolete RFC 2119. 
</pre>
      </blockquote>
      <pre wrap="">
&lt;bike-shed&gt;
IS THERE ANY CHANCE OF AGREEING THAT SHOUTING IS BAD?  (i.e., Burger's first anti-law.)  As opposed to mandating that requirements ought to be shouted.  Lowercase "must" can be as effective as uppercase as long as it is consistently applied.
&lt;/bike-shed&gt;</pre>
    </blockquote>
    <br>
    You paint that as tongue-in-cheek, but Peter's draft does go down
    the rat-hole of picking out a color scheme for this particular bike
    shed, when doing so is really unwarranted. In addition to the SHOULD
    &amp; co brouhaha, I have serious heartburn over this passage:<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre class="newpage">   When it is not appropriate to use the conformance terms, authors can
   use a variety of alternative words and phrases, such as: "need to" or
   "mandatory" instead of "MUST"; "ought to" or "strongly encouraged"
   instead of "SHOULD"; and "might" or "discretionary" instead of "MAY".
   To prevent confusion, authors ought to use these alternative words
   and phrases instead of the lowercase versions of the conformance
   terms, and to use the conformance terms only in their uppercase
   versions.</pre>
    <br>
    <br>
    There is no reason to tie authors' hands by restricting them from
    using perfectly good English words just because they happen to be
    the same symbols used by RFC 2119. If we're going down this path,
    let's scrap using MUST/SHOULD/MAY/etc, and formalize our conformance
    terms with symbols that aren't English words.<br>
    <br>
    Because the current suggestion -- which turns RFC writing into the
    game "Taboo" [1], but with incredibly common English words [2] as
    the forbidden list -- is ridiculous on its face.<br>
    <br>
    /a<br>
    <br>
    [1] <a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Taboo_%28game%29">http://en.wikipedia.org/wiki/Taboo_%28game%29</a><br>
    [2] According to Project Gutenberg, "must" and "may" are among the
    100 words most frequently used in written literature. See
<a class="moz-txt-link-freetext" href="http://en.wiktionary.org/wiki/Wiktionary:Frequency_lists#Project_Gutenberg">http://en.wiktionary.org/wiki/Wiktionary:Frequency_lists#Project_Gutenberg</a><br>
  </body>
</html>

--------------070109050208080505050102--

From sant9442@gmail.com  Tue Aug 30 12:06:59 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2341821F8E10 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.953
X-Spam-Level: 
X-Spam-Status: No, score=-2.953 tagged_above=-999 required=5 tests=[AWL=0.646,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anVRT8xwoYFd for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:06:58 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6E77021F8E0D for <ietf@ietf.org>; Tue, 30 Aug 2011 12:06:58 -0700 (PDT)
Received: by gwb20 with SMTP id 20so6869780gwb.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 12:08:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=87QKhVBlyQxPw6oboW+s2a4jdjw64eIweqB9WbgikFY=; b=AlgAughYuUQ1D59dYX8GPGtUNyvbTvuL1RaTUjQ4x2/swzm2f81L8yX6CW4+cxkQeF ayxyznzUFLQ7cZe1G2x02UlP6bC16dJnH1tWK8eGCG5ry3Lksty2woIaJ9tNbU+TQDgi rQl5b4FBKqPN7ThyRQsHtUAIQy1bMS6JKhAOc=
Received: by 10.151.112.1 with SMTP id p1mr6355431ybm.262.1314731303176; Tue, 30 Aug 2011 12:08:23 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id c63sm5642035yhe.32.2011.08.30.12.08.22 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Aug 2011 12:08:22 -0700 (PDT)
Sender: HLS <sant9442@gmail.com>
Message-ID: <4E5D3546.3020109@winserver.com>
Date: Tue, 30 Aug 2011 15:08:54 -0400
From: hector <gmail.sant9442@winserver.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>
In-Reply-To: <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 19:06:59 -0000

When I approach a protocol to implement, the first thing I typically 
do is extract and develop the basic wiring of the protocol, the 
minimum requirements.  Make sure the basic framework is correct 100%, 
then I look for the SHOULDs and also MAYS which are the easiest to 
add.  I look at the SHOULD by order of importance and also complexity. 
  How much "CANDY" is it?  It is a security feature?  What are the 
other implementation requirements, tools, APIs, etc.  Generally I want 
to get security out the way.  Its like SMTP AUTH - its not required 
but anyone cleaning up and rewriting an SMTP spec today, might include 
the AUTH extension as a SHOULD. And implementators are keen to the 
importance of it.  But nothing won't break down if you don't, less 
functionality but the basic structure is still there.

Its the same approach used for all the protocols we support. Start 
with the basics and then add on  as necessary.

Eric Burger wrote:
> What is the difference in this case between SHOULD or MAY?
> 
> On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:
> 
>> On 8/29/11 9:44 PM, Eric Burger wrote:
>>> Yes, and...
>>>
>>> I would offer that for most cases, If Y then MUST X or If Z then MUST NOT X *are* what people usually mean when they say SHOULD.  In the spirit of Say What You Mean, a bare SHOULD at the very least raise an ID-nit, suggesting to the author to turn the statement into the if Y then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
>>> 	SHOULD send a 1 UNLESS you receive a 0
>>> really means
>>> 	UNLESS you receive a 0, one MUST send a 1.
>>>
>>> My vision of the UNLESS clause is not necessarily a protocol state, but an environment state.  These are things that I can see fit the SHOULD/UNLESS form:
>>> 	SHOULD send a 1 UNLESS you are in a walled garden
>>> 	SHOULD flip bit 27 UNLESS you have a disk
>>> 	SHOULD NOT explode UNLESS you are a bomb
>>> are all reasonable SHOULD-level statements.
>>>
>>> I would offer that ANY construction of SHOULD without an UNLESS is a MAY.
>>
>> Eric. Put down the axe and step away from the whetstone. Here, I'll give you some text from RFC 3265 to mull.
>>
>>
>>   deactivated: The subscription has been terminated, but the subscriber
>>      SHOULD retry immediately with a new subscription.  One primary use
>>      of such a status code is to allow migration of subscriptions
>>      between nodes.
>>
>>
>> Let's examine this use of "SHOULD." If the subscriber doesn't re-subscribe, is it an interop issue? No.
>>
>> Is it in the interest of the implementation to re-subscribe? Yes. At least, under most circumstances. Otherwise, they won't get the state change notifications they want.
>>
>> Are there cases in which it makes sense for the subscriber _not_ to re-subscribe? Yes, I'm sure there are. It's conceivable that the client happens to be shutting down but hasn't gotten around to terminating this particular subscription yet. But any such exceptions are highly implementation-dependent. Listing them would be useless noise to the reader, and senseless text creation for the author.
>>
>> Does "SHOULD" get abused by some authors in some documents? Of course it does. But your crusade to throw out a useful tool just because it has been misused on occasion is an extreme over-reaction. I like this tool. I use this tool. If you see people misusing it, slap them.
>>
>> But don't ban the tool.
>>
>> /a
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From msk@cloudmark.com  Tue Aug 30 12:08:20 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FBBB21F8E91 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.032
X-Spam-Level: 
X-Spam-Status: No, score=-103.032 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90hz0iIM4pmd for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:08:19 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id C84C221F8E90 for <ietf@ietf.org>; Tue, 30 Aug 2011 12:08:19 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Tue, 30 Aug 2011 12:09:47 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF Discussion <ietf@ietf.org>
Date: Tue, 30 Aug 2011 12:09:47 -0700
Subject: RE: Limitations in RFC Errata mechanism
Thread-Topic: Limitations in RFC Errata mechanism
Thread-Index: AcxnKB/k6y+lDIJ3Q5GpJr45WmJ3KgAHvFiQ
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9A2@EXCH-C2.corp.cloudmark.com>
References: <4E5CFF6A.30004@gmail.com>
In-Reply-To: <4E5CFF6A.30004@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 19:08:20 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of M=
ykyta Yevstifeyev
> Sent: Tuesday, August 30, 2011 8:19 AM
> To: IETF Discussion
> Subject: Limitations in RFC Errata mechanism
>=20
> First, we have only two types of errata - Technical or Editorial.  In pre=
sence of
> <http://www.ietf.org/iesg/statement/rfc-metadata-errata.html>, "IESG
> Statement on IESG Processing of RFC Errata concerning RFC Metadata", I
> think the third type is necessary - Metadata.

I think given the current mechanism I would just submit such things under "=
Editorial".

> Second, the "Section" field at
> <http://www.rfc-editor.org/errata_report.php> implies that only
> numerical sections will contain something an erratum can be reported
> against (overlooking the GLOBAL option).  However, Appendices, Abstract,
> Index, Author Info, different Notes exist, that aren't covered here.

I was able to type "Appendix A" just now into that section without difficul=
ty.  The preview page shows "Section Appendix A says:", but that hardly see=
ms a difficulty.

> Third, Original text and Corrected text fields imply that only
> before-and-after errata may be submitted.  However, there might be
> errata like Erratum # 6
> (http://www.rfc-editor.org/errata_search.php?eid=3D6), with an only Repor=
t
> text field.  I understand this feature was present in previous versions
> of errata mechanism but removed from the current.

I don't understand the problem here.  That report seems pretty clear to me.

> Also, several issues not related to submission mechanism.
>=20
> 1) Specific mailing lists devoted to discussion of errata against RFCs
> from different areas.  I've proposed this on rfc-interest list; see ratio=
nale at
> <http://www.rfc-editor.org/pipermail/rfc-interest/2011-
> August/002672.html>.;

Typically a working group discusses an erratum when it is raised, and then =
it sits in limbo until a document update occurs.  Isn't the right place for=
 discussion about a particular one the mailing list of that working group o=
r, if it's disbanded, the main IETF list?

> 3) Verified technical errata may be incorporated in the references. Eg.
> 4 technical errata were reported against RFC 793 and verified; so the
> reference may be:
>=20
> Postel, J., "Transmission Control Protocol", STD 7, RFC 793,
> September 1981.  Ammended by RFC Errata Reports 573, 1562, 1564, 1572.

I don't think verified errata have any force or effect until the document i=
s actually updated, so this really just becomes clutter in the references. =
 Moreover, if I'm implementing some RFC that references another which itsel=
f has errata, I will want to know about all of them, not the ones that were=
 present and verified at the time of publication.

-MSK

From adam@nostrum.com  Tue Aug 30 12:13:35 2011
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 396B021F8EB6 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.328
X-Spam-Level: 
X-Spam-Status: No, score=-102.328 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XkhxqAuET5Dd for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:13:34 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7E13721F8EB2 for <ietf@ietf.org>; Tue, 30 Aug 2011 12:13:34 -0700 (PDT)
Received: from dn3-110.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 p7UJF2Ye061333 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 30 Aug 2011 14:15:02 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4E5D36B4.7000805@nostrum.com>
Date: Tue, 30 Aug 2011 14:15:00 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>
In-Reply-To: <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 19:13:35 -0000

In this case, unless the implementation has a good reason, failing to 
re-subscribe will result in behavior that the user perceives as broken. 
I don't think that's really "MAY" territory.

/a


On 8/30/11 1:57 PM, Eric Burger wrote:
> What is the difference in this case between SHOULD or MAY?
>
> On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:
>
>> On 8/29/11 9:44 PM, Eric Burger wrote:
>>> Yes, and...
>>>
>>> I would offer that for most cases, If Y then MUST X or If Z then MUST NOT X *are* what people usually mean when they say SHOULD.  In the spirit of Say What You Mean, a bare SHOULD at the very least raise an ID-nit, suggesting to the author to turn the statement into the if Y then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
>>> 	SHOULD send a 1 UNLESS you receive a 0
>>> really means
>>> 	UNLESS you receive a 0, one MUST send a 1.
>>>
>>> My vision of the UNLESS clause is not necessarily a protocol state, but an environment state.  These are things that I can see fit the SHOULD/UNLESS form:
>>> 	SHOULD send a 1 UNLESS you are in a walled garden
>>> 	SHOULD flip bit 27 UNLESS you have a disk
>>> 	SHOULD NOT explode UNLESS you are a bomb
>>> are all reasonable SHOULD-level statements.
>>>
>>> I would offer that ANY construction of SHOULD without an UNLESS is a MAY.
>>
>> Eric. Put down the axe and step away from the whetstone. Here, I'll give you some text from RFC 3265 to mull.
>>
>>
>>    deactivated: The subscription has been terminated, but the subscriber
>>       SHOULD retry immediately with a new subscription.  One primary use
>>       of such a status code is to allow migration of subscriptions
>>       between nodes.
>>
>>
>> Let's examine this use of "SHOULD." If the subscriber doesn't re-subscribe, is it an interop issue? No.
>>
>> Is it in the interest of the implementation to re-subscribe? Yes. At least, under most circumstances. Otherwise, they won't get the state change notifications they want.
>>
>> Are there cases in which it makes sense for the subscriber _not_ to re-subscribe? Yes, I'm sure there are. It's conceivable that the client happens to be shutting down but hasn't gotten around to terminating this particular subscription yet. But any such exceptions are highly implementation-dependent. Listing them would be useless noise to the reader, and senseless text creation for the author.
>>
>> Does "SHOULD" get abused by some authors in some documents? Of course it does. But your crusade to throw out a useful tool just because it has been misused on occasion is an extreme over-reaction. I like this tool. I use this tool. If you see people misusing it, slap them.
>>
>> But don't ban the tool.
>>
>> /a


From moore@network-heretics.com  Tue Aug 30 12:17:27 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD2121F8EE5 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.602
X-Spam-Level: 
X-Spam-Status: No, score=-3.602 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zXJJ1jvDRb2G for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:17:26 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id D150321F8EE0 for <ietf@ietf.org>; Tue, 30 Aug 2011 12:17:25 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id E8590209C1; Tue, 30 Aug 2011 15:18:53 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 30 Aug 2011 15:18:53 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=/0O 7Kxe0FnukNq5UKeH8NRswlbI=; b=kI0Mjct9EGRtU2TrYOWdwdYVE1ROzJbzqce ZwUApJ1QQiVwI3kgJtNjjAxMPlkHnYWjh7Ju21+DOIB1VIweIyYz+tIB1GdEqjo+ ZgOeRmOBCeV4T1tF5NKePtvlrGyDR6wzVmcH1beG5O+6d6cwN5f1eTQKoYZUVre8 BRwrHP+c=
X-Sasl-enc: YpJA8wO5WZmOOCL2AYxCp+WmIDlUofng4gm4JKVkzOAE 1314731933
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id ABDB896009D; Tue, 30 Aug 2011 15:18:53 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-62--730199412
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5D30CC.4000009@nostrum.com>
Date: Tue, 30 Aug 2011 15:18:53 -0400
Message-Id: <370F6928-4703-4142-A3C0-9F815404A971@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 19:17:27 -0000

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

On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:

> Does "SHOULD" get abused by some authors in some documents? Of course =
it does. But your crusade to throw out a useful tool just because it has =
been misused on occasion is an extreme over-reaction. I like this tool. =
I use this tool. If you see people misusing it, slap them.
>=20
> But don't ban the tool.

+1


--Apple-Mail-62--730199412
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><div>On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Does "SHOULD" =
get abused by some authors in some documents? Of course it does. But =
your crusade to throw out a useful tool just because it has been misused =
on occasion is an extreme over-reaction. I like this tool. I use this =
tool. If you see people misusing it, slap them.<br><br>But don't ban the =
tool.<br></span></blockquote></div><br><div>+1</div><div><br></div></body>=
</html>=

--Apple-Mail-62--730199412--

From petithug@acm.org  Tue Aug 30 12:58:37 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 720FA21F8E94 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IgSAw0Yce3qD for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:58:36 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id CEEA121F8E90 for <ietf@ietf.org>; Tue, 30 Aug 2011 12:58:36 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 9078D202C8; Tue, 30 Aug 2011 21:55:25 +0200 (CEST)
Message-ID: <4E5D4142.1040501@acm.org>
Date: Tue, 30 Aug 2011 13:00:02 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com> <370F6928-4703-4142-A3C0-9F815404A971@network-heretics.com>
In-Reply-To: <370F6928-4703-4142-A3C0-9F815404A971@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 19:58:37 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/30/2011 12:18 PM, Keith Moore wrote:
> On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:
> 
>> Does "SHOULD" get abused by some authors in some documents? Of course it does.
>> But your crusade to throw out a useful tool just because it has been misused
>> on occasion is an extreme over-reaction. I like this tool. I use this tool. If
>> you see people misusing it, slap them.
>>
>> But don't ban the tool.
> 
> +1
> 

I am wondering if having an Implementers Directorate, tasked to do reviews from
an implementation point of view, could not help discovering when a SHOULD can
create interoperability problems.  I would certainly volunteer in such group.


- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5dQT4ACgkQ9RoMZyVa61eU3gCglqmaf07bpE1RJU9oN3YotGgS
T+oAoKeRCXuB2Ea+Bzy+nw+A7er0kURv
=bHul
-----END PGP SIGNATURE-----

From dean.willis@softarmor.com  Tue Aug 30 12:58:40 2011
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D5B21F8F29 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.391
X-Spam-Level: 
X-Spam-Status: No, score=-103.391 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ui6XYlgbJEPh for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 12:58:40 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC5221F8F22 for <ietf@ietf.org>; Tue, 30 Aug 2011 12:58:39 -0700 (PDT)
Received: by ywe9 with SMTP id 9so6897898ywe.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 13:00:08 -0700 (PDT)
Received: by 10.101.181.10 with SMTP id i10mr1248908anp.116.1314734408041; Tue, 30 Aug 2011 13:00:08 -0700 (PDT)
Received: from dwillis-mb1.local (cpe-66-25-15-110.tx.res.rr.com [66.25.15.110]) by mx.google.com with ESMTPS id g3sm2987380ank.2.2011.08.30.13.00.06 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 13:00:07 -0700 (PDT)
Message-ID: <4E5D4144.1010700@softarmor.com>
Date: Tue, 30 Aug 2011 15:00:04 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Hyatt Taipei cancellation policy?
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM>
In-Reply-To: <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 19:58:40 -0000

On 8/23/11 9:24 AM, John C Klensin wrote:
>
> So I'm opposed to a USD 200 (or any other number) firm limit on
> hotel rates.  At the same time, I continue to wish that the IAOC
> would be more open with the community about how these decisions
> are made and, in particular, how the tradeoffs between
> sponsorship (and hence lower costs to the IETF for meeting
> infrastructure and arrangements) and meetings costs to attendees
> are made... open enough that the community could give
> substantive guidance on the subject, guidance that I assume the
> IAOC would follow if it were coherent and plausible.
>

Quite right. There's more than just the hotel rates.

My budget is about $2500 US per IETF meeting. That has to cover airfare, 
the IETF meeting fee, the hotel, meals, service charges, ground 
transport, mobile phone roaming, incidentals, etc.

$300 a night counting taxes and surcharge is just ABSOLUTELY OUT OF THE 
FREAKING QUESTION. Having the "backup" hotel a 10 minute taxi ride away 
is out of the question -- I can't afford taxis. If I can't walk, I can't go.

So guess what? I told the wife last night that I wasn't planning to go 
to the Taiwan meeting. I wanted to go, but I just don't see how it can 
happen. Maybe I'll win the lottery between now and then...

I'm disappointed. I'm hurt. I'm angry. And the trend has just been 
getting worse and worse with every venue. I want the IAOC's heads on a 
platter (preferably an inexpensive, disposable platter, like maybe the 
lid off an old pizza box) for signing us up to this venue. And I want a 
travel budget no larger than mine for the people we send to future meetings.

If we can't find a reasonably inexpensive place to have a meeting, DON'T 
HAVE THE MEETING!


--
Dean Willis

From jari.arkko@piuha.net  Tue Aug 30 13:16:50 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAFCC21F8F21 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 13:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7cUOxSvakaE for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 13:16:50 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id ECE7C21F8CC2 for <ietf@ietf.org>; Tue, 30 Aug 2011 13:16:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3BAA22CEFF; Tue, 30 Aug 2011 23:17:53 +0300 (EEST)
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 xt7by5e1zYmG; Tue, 30 Aug 2011 23:17:52 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 8CDCD2CE66; Tue, 30 Aug 2011 23:17:52 +0300 (EEST)
Message-ID: <4E5D4570.9080108@piuha.net>
Date: Tue, 30 Aug 2011 23:17:52 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12
MIME-Version: 1.0
To: ietf@ietf.org, Russ Housley <housley@vigilsec.com>
Subject: Conclusion of the last call on draft-housley-two-maturity-levels
References: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>
In-Reply-To: <20110728121904.2D22AD7A76F@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 20:16:50 -0000

I have reviewed the discussion from the last call on this document.

My conclusion as the sponsoring AD is that we have consensus to move forward. There was clearly a constituency who believed this is a good (albeit small) step forward. A number of other people did not care so much; did not believe there was either harm or benefit. I also saw a couple of opposing opinions, though some of them were more about a desire to do something else than specific objections about this proposal. I will be recommending that the IESG approve the draft.

There were a number of smaller details raised in the discussion. But I did not see an overwhelming consensus on any specific issue to make changes. But I will ask Russ to take a look at the issue raised by Scott, whether he wants to add an informative reference to RFC 5657.

Another issue that I wanted to highlight is the question of what kinds of discusses are desirable/acceptable for documents that move from PS to IS. It is outside the scope of Russ' document, but generated nevertheless some interest. The IESG has discussed this matter and drafted some suggested guidelines. Look for a different thread on this list, under "Discuss criteria for documents that advance on the standards track". Feedback on the guidelines would be appreciated.

Jari


From jari.arkko@piuha.net  Tue Aug 30 13:17:40 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22AA721F8F51 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 13:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.478
X-Spam-Level: 
X-Spam-Status: No, score=-102.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1MJyy4j0sMCJ for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 13:17:39 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF1721F8F4F for <ietf@ietf.org>; Tue, 30 Aug 2011 13:17:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 825542CEFF for <ietf@ietf.org>; Tue, 30 Aug 2011 23:18:59 +0300 (EEST)
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 aYqBvqBn3oT1 for <ietf@ietf.org>; Tue, 30 Aug 2011 23:18:57 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id C72A02CE66 for <ietf@ietf.org>; Tue, 30 Aug 2011 23:18:57 +0300 (EEST)
Message-ID: <4E5D45B1.50107@piuha.net>
Date: Tue, 30 Aug 2011 23:18:57 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Discuss criteria for documents that advance on the standards track
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 20:17:40 -0000

During the discussion of the two maturity levels change, a question was brought up about DISCUSSes appropriate for documents that advance on the standards track. We discussed this in the IESG and I drafted some suggested guidelines. Feedback on these suggestions would be welcome. The intent is to publish an IESG statement to complement the already existing general-purpose DISCUSS criteria IESG statement (http://www.ietf.org/iesg/statement/discuss-criteria.html).

Here are the suggested guidelines for documents that advance to IS:

http://www.arkko.com/ietf/iesg/discuss-criteria-advancing.txt

Comments appreciated. Please send comments either on this list or to the IESG (iesg@ietf.org) in time before our next telechat (Thursday, September 8, 2011).

Jari


From hotz@jpl.nasa.gov  Mon Aug 29 10:15:46 2011
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 064C621F8997; Mon, 29 Aug 2011 10:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTaXqZoAxpXm; Mon, 29 Aug 2011 10:15:45 -0700 (PDT)
Received: from mail.jpl.nasa.gov (sentrion3.jpl.nasa.gov [128.149.139.109]) by ietfa.amsl.com (Postfix) with ESMTP id 7401221F87D6; Mon, 29 Aug 2011 10:15:45 -0700 (PDT)
Received: from laphotz.jpl.nasa.gov (laphotz.jpl.nasa.gov [128.149.133.44]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id p7THGxYD015439 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Mon, 29 Aug 2011 10:17:05 -0700
Subject: Re: [Ietf-krb-wg] Gen-ART review of draft-ietf-krb-wg-otp-preauth-18
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <tsl1uw4pb60.fsf@mit.edu>
Date: Mon, 29 Aug 2011 10:16:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A8A3165-D962-4958-92E4-574F9231C265@jpl.nasa.gov>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E0589672C6A@MX14A.corp.emc.com> <tslliui6ycj.fsf@mit.edu> <7C4DFCE962635144B8FAE8CA11D0BF1E0589672CE3@MX14A.corp.emc.com> <B1371F619AB0A94C9AC73CF2E475485B038C5188E1@MX11A.corp.emc.com> <87sjoocgxs.fsf@latte.josefsson.org> <D59A1036-ABCA-43CE-B3D3-1D3334CABE2B@jpl.nasa.gov> <tsl1uw4pb60.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1084)
X-Source-IP: laphotz.jpl.nasa.gov [128.149.133.44]
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Tue, 30 Aug 2011 13:46:05 -0700
Cc: Simon Josefsson <simon@josefsson.org>, "ietf@ietf.org" <ietf@ietf.org>, "gareth.richards@rsa.com" <gareth.richards@rsa.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf-krb-wg@lists.anl.gov" <ietf-krb-wg@lists.anl.gov>, "david.black@emc.com" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2011 17:15:46 -0000

I was thinking that if it's a proprietary OTP, we can still use it even =
if the algorithm is secret.  If we know we're getting a "clear text" OTP =
value and we have an (unspecified) method of verifying it against some =
external infrastructure, that's enough to use otp-preauth.

However I don't think this actually requires a complete registry.  A =
single undefined/external entry for the existing PSKC registry would be =
sufficient, wouldn't it?

On Aug 29, 2011, at 7:03 AM, Sam Hartman wrote:

> What information required by the PSC registry do we not need?
> The only thing I see is the XML information, but it looks like that
> could be blank.

------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu




From hsantos@santronics.com  Mon Aug 29 17:54:12 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8312821F8C7D for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 17:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level: 
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[AWL=-0.289, BAYES_00=-2.599, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xuK0f0WvDDge for <ietf@ietfa.amsl.com>; Mon, 29 Aug 2011 17:54:11 -0700 (PDT)
Received: from secure.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3BC21F8C77 for <ietf@ietf.org>; Mon, 29 Aug 2011 17:54:09 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4389; t=1314665726; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=gAONvxc YGQa9Gr8qiV/lzXvjrmQ=; b=qVtR8NF7FQpogPxTrqOBwQnkH2idcsPhTryJGUJ /Cbht0//j9DMo1tQBSuvuKEJ3nizVrsZYZnOreA99lqInUR1XFV5RjTVKn8WAPSm luEevtIfM4/lAIQQiGMHO+ouOTOP85NrzKooapJY61stl2aLtl9KDnHHREqmLCDR QsvA=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 29 Aug 2011 20:55:26 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3121125455.45324.5636; Mon, 29 Aug 2011 20:54:26 -0400
Message-ID: <4E5C34DD.2010905@santronics.com>
Date: Mon, 29 Aug 2011 20:54:53 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>
In-Reply-To: <4E5C067A.9080400@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 30 Aug 2011 13:46:05 -0700
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 00:54:12 -0000

Thanks for doing this Peter.  I only have one input regarding SHOULD.

Recently an AD entered an WG during LC, apologized for not being 
involved more and specifically called out the 4-5 people who had 
rejected a SHOULD text injection proposal as not understanding 
RFC2119. He also added that software which does not implement a SHOULD 
is broken already.  In fact, his interpretation is ironically very 
close to what you have for SHOULD in this I-D.  So I wonder if this 
I-D SHOULD text is the same AD view and a result of what happen in the 
WG.  This is not a disrespect of AD, but I vocalized my exception to 
the AD description when:

    A) There was no RFC2119 material text or copy that even came close
       to AD interpretation, and

    B) RFC2119 states SHOULD is the same as the adjective "RECOMMENDED."

As far I am concern, a recommendation is not a mandate nor obligation. 
  The text is very vague and the original RFC2119 is simpler to 
understand and IMO, closer to practical realities faced for 
implementators.

Of course, none of this is cut and dry and I understand the intent of 
the text is to encourage implementators to update their software, 
especially for enhanced protocol and/or new integrated ideas where one 
protocol requires the help of another protocol, a situation where 
ideally one would like something to be written as a MUST but for 
legacy reasons a fallback is available, thus written as a SHOULD.  The 
dilemma begin that unless it is more described with some level of 
obligation, people don't upgrade as fast or as wide as one would like.

My concerns are when a protocol SHOULD is read as an obligation, then 
two things can and has happen:

    - Any software that is not currently supportive of a SHOULD or 
even aware
      of it, is instantly classified as broken software. This was one 
of the
      concerns  in the WG when the AD issued the same description as 
you have
      here.  When the feature was not already support and especially not
      required, or worst viewed as a temporary short term solution, a 
SHOULD
      defined as an Obligation is not going to go smoothly by all
      responsible implementators.

    - A feature that was a highly controversial decision and was added as
      a SHOULD with a rough consensus with lack compromise, an obligation
      interpretation will cause implementators to not follow it nor 
support
      something else that requires an additional SHOULD. It could even 
be a
      cost reason, an expensive design change that is require to 
accommodate
      a SHOULD not believed to be worth the effort.

I think rephrasing is necessary.  I think what is important, no matter 
which way the text wants it convey SHOULD as an important obligated 
feature to support, no protocol error can occur due to lack of support 
on either end or disabled by operators.

So if anything, I believe removing the final sentence would be more 
correct because its no longer a recommendation but an obligation. 
This is not a suggestion, but to highlight it it can probably be said 
in two sentences to convey the point:

      A SHOULD is a MUST with a fallback. Implementators are not
      considered NON-COMPLIANT if a SHOULD is not implemented as long
      as the fallback is already possible.

Thanks

Peter Saint-Andre wrote:
> After staring at http://www.rfc-editor.org/errata_search.php?eid=499 for
> long enough, I finally decided to submit an I-D that is intended to
> obsolete RFC 2119. I hope that I've been able to update and clarify the
> text in a way that is respectful of the original. Feedback is welcome.
> 
> http://www.ietf.org/id/draft-saintandre-2119bis-01.txt
> 
> Peter
> 

-- 
Sincerely

Hector Santos
http://www.santronics.com

I addition, even if it was added by a piece of software, it does not
mean the operator MUST enabled it or that the software prevent him 
from turning it off.  I venture most implementations will not provide 
an MUST turn off switch but will provide a SHOULD turn off switch.

I also stated more importantly that even if it was a mandate for a 
server, since it must be ready for clients that do not support it and 
there is no operational repercussions for its lack of usage, thus by 
this consideration, there is no mandate or obligation by either side 
to support it.  In my view, if one end expects a feature, then its a 
MUST.  But if its able to fall back, then its a SHOULD.




From stbryant@cisco.com  Tue Aug 30 05:12:23 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B590F21F886F; Tue, 30 Aug 2011 05:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.536
X-Spam-Level: 
X-Spam-Status: No, score=-110.536 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zs3sVAMARYdp; Tue, 30 Aug 2011 05:12:23 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id A6DBF21F88B6; Tue, 30 Aug 2011 05:12:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=6177; q=dns/txt; s=iport; t=1314706429; x=1315916029; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=OtYsUzWPDxGRQGlA9Lk6/Ma6pr5AMyMkIn1EaymvlUw=; b=iGyebGz6yq+NLkg5QCUbbDGwhXurQk4cFCmizpbHJp+i7GuE35g4wIt6 ili15A1hYPDW61KPaD7tghZH4gN9ln9M95c56hr4jgNMBw2Hh2HkBwdDn E9P5CYVehxeg1NNxESl/zKQGB0a+VD2ajn3yzmZSh6TfQn+rzdnNXXPup 8=;
X-IronPort-AV: E=Sophos;i="4.68,302,1312156800";  d="scan'208,217";a="113203816"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 30 Aug 2011 12:13:37 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7UCDbuu009669; Tue, 30 Aug 2011 12:13:37 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p7UC4lu1011120; Tue, 30 Aug 2011 13:04:47 +0100 (BST)
Message-ID: <4E5CD1DF.90702@cisco.com>
Date: Tue, 30 Aug 2011 13:04:47 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Luca Martini <lmartini@cisco.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>, <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net> <4E4EC4D2.3070603@cisco.com>
In-Reply-To: <4E4EC4D2.3070603@cisco.com>
Content-Type: multipart/alternative; boundary="------------020208080607020801080801"
X-Mailman-Approved-At: Tue, 30 Aug 2011 13:46:05 -0700
Cc: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "ietf@ietf.org" <ietf@ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, "mpls@ietf.org" <mpls@ietf.org>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 12:12:23 -0000

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


Reviewing this discussion there are three components.

1) The update of RFC5586 to allow PW to use the GAL.
2) The PW OAM application that is to use the GAL.
3) The label stack structure when  teh GAL is used with a PW

This draft is only concerned with point 1 above. Points
2 and 3 need to be resolved in any PWE3 draft that describes
the use of the GAL.

To that end the text in draft-ietf-pwe3-mpls-tp-gal-in-pw-01

========
  -Section 4.2  <http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2>. (GAL Applicability and Usage) in [RFC5586  <http://tools.ietf.org/html/rfc5586>], the
       original text:

           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
           LSPs, Concatenated Segments of LSPs, and with Sections, and
           MUST NOT be used with PWs. It MUST always be at the bottom of
           the label stack (i.e., S bit set to 1). However, in other MPLS
           environments, this document places no restrictions on where
           the GAL may appear within the label stack or its use with PWs.

       is replaced by:

           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
           LSPs, Concatenated Segments of LSPs, and with Sections, and
           MAY be used with PWs. It MUST always be at the bottom of the
           label stack (i.e., S bit set to 1). However, in other MPLS
           environments, this document places no restrictions on where
           the GAL may appear within the label stack.

=====

should be replaced by

=====

  -Section 4.2  <http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2>. (GAL Applicability and Usage) in [RFC5586  <http://tools.ietf.org/html/rfc5586>], the
       original text:

           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
           LSPs, Concatenated Segments of LSPs, and with Sections, and
           MUST NOT be used with PWs. It MUST always be at the bottom of
           the label stack (i.e., S bit set to 1). However, in other MPLS
           environments, this document places no restrictions on where
           the GAL may appear within the label stack or its use with PWs.

       is replaced by:

           In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
           LSPs, Concatenated Segments of LSPs, and with Sections, and
           MAY be used with PWs. The presence of a GAL indicates that
           an ACH immediately follows the MPLS label stack.

======

- Stewart

--------------020208080607020801080801
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    Reviewing this discussion there are three components.<br>
    <br>
    1) The update of RFC5586 to allow PW to use the GAL.<br>
    2) The PW OAM application that is to use the GAL. <br>
    3) The label stack structure when&nbsp; teh GAL is used with a PW<br>
    <br>
    This draft is only concerned with point 1 above. Points<br>
    2 and 3 need to be resolved in any PWE3 draft that describes<br>
    the use of the GAL.<br>
    <br>
    To that end the text in draft-ietf-pwe3-mpls-tp-gal-in-pw-01<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre class="newpage">========
&nbsp;-  <a href="http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2">Section 4.2</a>. (GAL Applicability and Usage) in [<a href="http://tools.ietf.org/html/rfc5586" title="&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>], the
      original text:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MUST NOT be used with PWs. It MUST always be at the bottom of
          the label stack (i.e., S bit set to 1). However, in other MPLS
          environments, this document places no restrictions on where
          the GAL may appear within the label stack or its use with PWs.

      is replaced by:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MAY be used with PWs. It MUST always be at the bottom of the
          label stack (i.e., S bit set to 1). However, in other MPLS
          environments, this document places no restrictions on where
          the GAL may appear within the label stack.</pre>
    =====<br>
    <br>
    should be replaced by<br>
    <br>
    =====<br>
    <br>
    <pre class="newpage">&nbsp;-  <a href="http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2">Section 4.2</a>. (GAL Applicability and Usage) in [<a href="http://tools.ietf.org/html/rfc5586" title="&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>], the
      original text:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MUST NOT be used with PWs. It MUST always be at the bottom of
          the label stack (i.e., S bit set to 1). However, in other MPLS
          environments, this document places no restrictions on where
          the GAL may appear within the label stack or its use with PWs.

      is replaced by:

          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on
          LSPs, Concatenated Segments of LSPs, and with Sections, and
          MAY be used with PWs. The presence of a GAL indicates that
          an ACH immediately follows the MPLS label stack.  </pre>
    ======<br>
    <br>
    - Stewart<br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
  </body>
</html>

--------------020208080607020801080801--

From Alexander.Vainshtein@ecitele.com  Tue Aug 30 05:20:40 2011
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC36421F8B82; Tue, 30 Aug 2011 05:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.036
X-Spam-Level: 
X-Spam-Status: No, score=-4.036 tagged_above=-999 required=5 tests=[AWL=1.166,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DAHbBAyjvDsO; Tue, 30 Aug 2011 05:20:38 -0700 (PDT)
Received: from mail27.messagelabs.com (mail27.messagelabs.com [193.109.254.147]) by ietfa.amsl.com (Postfix) with SMTP id BF33121F8B73; Tue, 30 Aug 2011 05:20:37 -0700 (PDT)
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1314706897!40762545!3
X-Originating-IP: [147.234.242.234]
X-StarScan-Version: 6.3.6; banners=-,-,-
Received: (qmail 10878 invoked from network); 30 Aug 2011 12:21:48 -0000
Received: from ilptbmg01-out.ecitele.com (HELO ilptbmg01-out.ecitele.com) (147.234.242.234) by server-4.tower-27.messagelabs.com with SMTP; 30 Aug 2011 12:21:48 -0000
X-AuditID: 93eaf2e7-b7be0ae000003a75-e1-4e5cd5e075ca
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01-out.ecitele.com (Symantec Messaging Gateway) with SMTP id 75.63.14965.0E5DC5E4; Tue, 30 Aug 2011 15:21:52 +0300 (IDT)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Tue, 30 Aug 2011 15:22:01 +0300
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Date: Tue, 30 Aug 2011 15:22:00 +0300
Subject: RE: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Topic: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
Thread-Index: AcxnDkCbya80tx8hTnaiki2IohjPNgAAGCAA
Message-ID: <A3C5DF08D38B6049839A6F553B331C760111EFB651BF@ILPTMAIL02.ecitele.com>
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>,  <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>,  <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net> <4E4EC4D2.3070603@cisco.com> <4E5CD1DF.90702@cisco.com>
In-Reply-To: <4E5CD1DF.90702@cisco.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_A3C5DF08D38B6049839A6F553B331C760111EFB651BFILPTMAIL02e_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLsWRmVeSWpSXmKPExsUy+dWnL7oPrsb4GSx5pWsx489EZotnG+ez WMy562zx/M5fdotbS1eyWrSvPcti0fdpC4vFuadzGB04PKb83sjqsWTJTyaP601X2T2+XP7M FsAS1cBok5iXl1+SWJKqkJJanGyrFFCUWZaYXKmkkJliq2SopFCQk5icmpuaV2KrlFhQkJqX omTHpYABbIDKMvMUUvOS81My89JtlTyD/XUtLEwtdQ2V7NSUDY2tuUIyMosVUnVzEzNzFHJT i4sT01MVgCIJW5gz/jx5x1bQ0sBYcb/XqIFxQkEXIyeHhICJxMKlV5ggbDGJC/fWs3UxcnEI CexnlDh06CgLhDONUeLp8w5mkCo2AVuJTavvsoHYIgK6ErM33GAEKWIWaGCRuDh/LliCRUBV 4mYjSIKTQ1ggQOLCsmZWiIZAidbTj4DiHEC2kcSJRy4gYV6g8ItVm8FKhAR6WSS+XQ4HsTkF 1CVmX34Edh0j0HXfT60Bs5kFxCVuPZkPdbWAxJI955khbFGJl4//sULUi0rcaV/PCFGfL7Fj cSMbxC5BiZMzn7BA1EtKHFxxg2UCo9gsJGNnIWmZhaQFIq4jsWD3JzYIW1ti2cLXzDD2mQOP mZDFFzCyr2IUzcwpKEnKTTcw1EtNzixJzUnVS87P3cQISWPPdzD+mq9yiFGAg1GJh/fEt2g/ IdbEsuLK3EOMkhxMSqK8Nldi/IT4kvJTKjMSizPii0pzUosPMUpwMCuJ8K5YBZTjTUmsrEot yodJuQIDfyKzFHdyPjA155XEGxsY4OYoifM+TX7jKySQDkya2ampBalFMHNkODiUJHgNgTlA SLAoNT21Ii0zpwQhzcTBCXIGD9AZuiA1vMUFibnFmekQ+VOMilLivPYgCQGQREZpHlwvKHfV /////xWjONDTwrx6IFU8wLwH1/0KaDAT0OBLhtEgg4HZBi4l1cAoMPmyUJfbilrGMqf8RbIX Smb/nqCcvd5irndE9cJfQoteCm+uK1JRLTwpzR1q95WxN+agnlvel/rumd0fn3nevZTmUDBd rH6Bs7L1Brb8xz9+tniEOtlN4+k3mbjuwSnr9fHTozsC52iGrDLwPTmzzsRwp/aaZoZfmTLH LVaxHj5y0uWI0RElluKMREMt5qLiRAAaqfI+OAQAAA==
X-Mailman-Approved-At: Tue, 30 Aug 2011 13:46:05 -0700
Cc: IETF Discussion <ietf@ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, "mpls@ietf.org" <mpls@ietf.org>, Luca Martini <lmartini@cisco.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 12:20:41 -0000

--_000_A3C5DF08D38B6049839A6F553B331C760111EFB651BFILPTMAIL02e_
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable

Stewart,
I believe that your item #1 is presumably addressed by draft-ietf-pwe3-gal-i=
n-pw (with the changes you've proposed), draft-nadeau-pwe3-vccv-2 is an atte=
mpt to address your item #2, and your item #3 is not yet addressed.  Is this=
 understanding correct?

I also think that one of the items in the discussion was the restriction on=
 ECMP in MPLS to skip reserved labels. I am not sure if it has been properly=
 addressed anywhere, so should not it constitute item #4?

Regards,
     Sasha

From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Tuesday, August 30, 2011 3:05 PM
To: Luca Martini; IETF Discussion
Cc: John E Drake; mpls@ietf.org; Alexander Vainshtein; ietf@ietf.org; Vladim=
ir Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rotem=
 Cohen; pwe3-chairs@tools.ietf.org; iesg@ietf.org
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-=
pw


Reviewing this discussion there are three components.

1) The update of RFC5586 to allow PW to use the GAL.
2) The PW OAM application that is to use the GAL.
3) The label stack structure when  teh GAL is used with a PW

This draft is only concerned with point 1 above. Points
2 and 3 need to be resolved in any PWE3 draft that describes
the use of the GAL.

To that end the text in draft-ietf-pwe3-mpls-tp-gal-in-pw-01

=3D=3D=3D=3D=3D=3D=3D=3D

 -  Section 4.2<http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw=
-01#section-4.2>. (GAL Applicability and Usage) in [RFC5586<http://tools.iet=
f.org/html/rfc5586>], the

      original text:



          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on

          LSPs, Concatenated Segments of LSPs, and with Sections, and

          MUST NOT be used with PWs. It MUST always be at the bottom of

          the label stack (i.e., S bit set to 1). However, in other MPLS

          environments, this document places no restrictions on where

          the GAL may appear within the label stack or its use with PWs.



      is replaced by:



          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on

          LSPs, Concatenated Segments of LSPs, and with Sections, and

          MAY be used with PWs. It MUST always be at the bottom of the

          label stack (i.e., S bit set to 1). However, in other MPLS

          environments, this document places no restrictions on where

          the GAL may appear within the label stack.
=3D=3D=3D=3D=3D

should be replaced by

=3D=3D=3D=3D=3D

 -  Section 4.2<http://tools.ietf.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw=
-01#section-4.2>. (GAL Applicability and Usage) in [RFC5586<http://tools.iet=
f.org/html/rfc5586>], the

      original text:



          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on

          LSPs, Concatenated Segments of LSPs, and with Sections, and

          MUST NOT be used with PWs. It MUST always be at the bottom of

          the label stack (i.e., S bit set to 1). However, in other MPLS

          environments, this document places no restrictions on where

          the GAL may appear within the label stack or its use with PWs.



      is replaced by:



          In MPLS-TP, the GAL MUST be used with packets on a G-ACh on

          LSPs, Concatenated Segments of LSPs, and with Sections, and

          MAY be used with PWs. The presence of a GAL indicates that

          an ACH immediately follows the MPLS label stack.
=3D=3D=3D=3D=3D=3D

- Stewart


This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.


--_000_A3C5DF08D38B6049839A6F553B331C760111EFB651BFILPTMAIL02e_
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-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xm=
lns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-micr=
osoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office:acc=
ess" 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:offic=
e:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" xmlns=
:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc=3D"u=
rn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-microsoft-com:o=
ffice: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.micro=
soft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/mee=
tings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" xmln=
s:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=3D"http://schemas=
.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schemas.microsoft.c=
om/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"ht=
tp://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www.w3.org/2001/XML=
Schema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/ale=
rts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns:sp=3D"http://sche=
mas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schemas.microsoft.com/sha=
repoint/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://s=
chemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D"http://schemas.micros=
oft.com/data/udc/parttopart" xmlns:wf=3D"http://schemas.microsoft.com/sharep=
oint/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-signa=
ture" xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2=
006" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrel=
s=3D"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spw=
p=3D"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t=3D"http://sch=
emas.microsoft.com/exchange/services/2006/types" xmlns:ex12m=3D"http://schem=
as.microsoft.com/exchange/services/2006/messages" xmlns:pptsl=3D"http://sche=
mas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl=3D"http://micros=
oft.com/webservices/SharePointPortalServer/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=3DContent-Type content=3D"text/html; cha=
rset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 (filter=
ed 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:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
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 bgcolor=3Dwhite 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:#1F4=
97D'>Stewart,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I believe that=
 your item #1 is presumably addressed by draft-ietf-pwe3-gal-in-pw (with the=
 changes you&#8217;ve proposed), draft-nadeau-pwe3-vccv-2 is an attempt to a=
ddress your item #2, and your item #3 is not yet addressed. &nbsp;Is this un=
derstanding correct?<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-serif";color:#1F497D'>I also think that one of t=
he items in the discussion was the restriction on ECMP in MPLS to skip reser=
ved labels. I am not sure if it has been properly addressed anywhere, so sho=
uld not it constitute item #4?<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Sasha<o=
:p></o:p></span></p></div><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;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;padding:0cm 0cm=
 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;pa=
dding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> Stewart Bryant [mailto:stbryant@cisco.com] <br><b>Sent:</b> Tuesday, A=
ugust 30, 2011 3:05 PM<br><b>To:</b> Luca Martini; IETF Discussion<br><b>Cc:=
</b> John E Drake; mpls@ietf.org; Alexander Vainshtein; ietf@ietf.org; Vladi=
mir Kleiner; Idan Kaspit; Mishael Wexler; pwe3; Oren Gal; John Shirron; Rote=
m Cohen; pwe3-chairs@tools.ietf.org; iesg@ietf.org<br><b>Subject:</b> Re: [m=
pls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw<o:p></o:p></=
span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMs=
oNormal style=3D'margin-bottom:12.0pt'><br>Reviewing this discussion there a=
re three components.<br><br>1) The update of RFC5586 to allow PW to use the=
 GAL.<br>2) The PW OAM application that is to use the GAL. <br>3) The label=
 stack structure when&nbsp; teh GAL is used with a PW<br><br>This draft is o=
nly concerned with point 1 above. Points<br>2 and 3 need to be resolved in a=
ny PWE3 draft that describes<br>the use of the GAL.<br><br>To that end the t=
ext in draft-ietf-pwe3-mpls-tp-gal-in-pw-01<o:p></o:p></p><pre>=3D=3D=3D=3D=
=3D=3D=3D=3D<o:p></o:p></pre><pre>&nbsp;-&nbsp; <a href=3D"http://tools.ietf=
.org/html/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2">Section 4.2</a>.=
 (GAL Applicability and Usage) in [<a href=3D"http://tools.ietf.org/html/rfc=
5586" title=3D"&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>], th=
e<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; original text:<o:p></o=
:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; In MPLS-TP, the GAL MUST be used with packets on a G-AC=
h on<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; LSPs, Concatenated Segments of LSPs, and with Sections, and<o:p></o:p><=
/pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MUST NOT be=
 used with PWs. It MUST always be at the bottom of<o:p></o:p></pre><pre>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the label stack (i.e., S=
 bit set to 1). However, in other MPLS<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; environments, this document places no=
 restrictions on where<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; the GAL may appear within the label stack or its use=
 with PWs.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; is replaced by:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><=
pre> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;In MPLS-TP, the G=
AL MUST be used with packets on a G-ACh on<o:p></o:p></pre><pre>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LSPs, Concatenated Segments of LS=
Ps, and with Sections, and<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; MAY be used with PWs. It MUST always be at the bo=
ttom of the<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; label stack (i.e., S bit set to 1). However, in other MPLS<o:p><=
/o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; envir=
onments, this document places no restrictions on where<o:p></o:p></pre><pre>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the GAL may appear wi=
thin the label stack.<o:p></o:p></pre><p class=3DMsoNormal style=3D'margin-b=
ottom:12.0pt'>=3D=3D=3D=3D=3D<br><br>should be replaced by<br><br>=3D=3D=3D=
=3D=3D<o:p></o:p></p><pre>&nbsp;-&nbsp; <a href=3D"http://tools.ietf.org/htm=
l/draft-ietf-pwe3-mpls-tp-gal-in-pw-01#section-4.2">Section 4.2</a>. (GAL Ap=
plicability and Usage) in [<a href=3D"http://tools.ietf.org/html/rfc5586" ti=
tle=3D"&quot;MPLS Generic Associated Channel&quot;">RFC5586</a>], the<o:p></=
o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; original text:<o:p></o:p></pre=
><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; In MPLS-TP, the GAL MUST be used with packets on a G-ACh on<o:p=
></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LSP=
s, Concatenated Segments of LSPs, and with Sections, and<o:p></o:p></pre><pr=
e>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MUST NOT be used wi=
th PWs. It MUST always be at the bottom of<o:p></o:p></pre><pre>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the label stack (i.e., S bit set=
 to 1). However, in other MPLS<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; environments, this document places no restric=
tions on where<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; the GAL may appear within the label stack or its use with PWs=
.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; is replaced by:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In MPLS-TP, the GAL MUST b=
e used with packets on a G-ACh on<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LSPs, Concatenated Segments of LSPs, and w=
ith Sections, and<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; MAY be used with PWs. The presence of a GAL indicates that=
<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 an ACH immediately follows the MPLS label stack.&nbsp; <o:p></o:p></pre><p=
 class=3DMsoNormal>=3D=3D=3D=3D=3D=3D<br><br>- Stewart<o:p></o:p></p></div><=
/div><p>
This e-mail message is intended for the recipient only and contains informat=
ion which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If yo=
u have received this transmission in error, please inform us by e-mail, phon=
e or fax, and then delete the original and all copies thereof.
</p>
</body></html>
--_000_A3C5DF08D38B6049839A6F553B331C760111EFB651BFILPTMAIL02e_--

From stbryant@cisco.com  Tue Aug 30 06:12:01 2011
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C30D21F8B25; Tue, 30 Aug 2011 06:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.538
X-Spam-Level: 
X-Spam-Status: No, score=-110.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGQc083XeGY1; Tue, 30 Aug 2011 06:12:00 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id AEE7121F8B21; Tue, 30 Aug 2011 06:11:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=904; q=dns/txt; s=iport; t=1314710008; x=1315919608; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=zMuYBXQ4OFsHFdfZkiCCKVVAd9Dj0Gc1bRjtRrx/57k=; b=hzt5rTb1cFXsd0v/gtjZFiJEa23Zdw2F7mV7xBV5pghs8wZtBihk+o5Q gStmGQZiR8zLGRL5hQi0WcpPFGWbVcr5m2oSeRwdRWZpfaVUBruINmc2t kXKWowHlxKOIkvoMiP1NUHGQltEYkkmfVcUJ7K/dffl+VLkCtmRz48coh w=;
X-IronPort-AV: E=Sophos;i="4.68,302,1312156800"; d="scan'208";a="113214001"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 30 Aug 2011 13:13:25 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p7UDDMUC011810; Tue, 30 Aug 2011 13:13:25 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id p7UDDKJ7014717; Tue, 30 Aug 2011 14:13:20 +0100 (BST)
Message-ID: <4E5CE1F0.6040701@cisco.com>
Date: Tue, 30 Aug 2011 14:13:20 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Subject: Re: [mpls] [PWE3] IETF Last Call comment on draft-ietf-pwe3-gal-in-pw
References: <A3C5DF08D38B6049839A6F553B331C760111EFA07C5F@ILPTMAIL02.ecitele.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD443@ILPTMAIL02.ecitele.com>, <CAGEmCZxh7N-E-vFhYkYG_RVUOQVG00qxc5pEbOuRBC0fqjBprg@mail.gmail.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD445@ILPTMAIL02.ecitele.com>, <4E4C0F3F.8010700@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EF7BD447@ILPTMAIL02.ecitele.com> <5E893DB832F57341992548CDBB333163A0ACD4831F@EMBX01-HQ.jnpr.net> <4E4EC4D2.3070603@cisco.com> <4E5CD1DF.90702@cisco.com> <A3C5DF08D38B6049839A6F553B331C760111EFB651BF@ILPTMAIL02.ecitele.com>
In-Reply-To: <A3C5DF08D38B6049839A6F553B331C760111EFB651BF@ILPTMAIL02.ecitele.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 30 Aug 2011 13:46:05 -0700
Cc: IETF Discussion <ietf@ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Vladimir Kleiner <Vladimir.Kleiner@ecitele.com>, "mpls@ietf.org" <mpls@ietf.org>, Luca Martini <lmartini@cisco.com>, Idan Kaspit <Idan.Kaspit@ecitele.com>, Mishael Wexler <Mishael.Wexler@ecitele.com>, pwe3 <pwe3@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Oren Gal <Oren.Gal@ecitele.com>, John Shirron <John.Shirron@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 13:12:01 -0000

Sasha



On 30/08/2011 13:22, Alexander Vainshtein wrote:
>
> Stewart,
>
> I believe that your item #1 is presumably addressed by 
> draft-ietf-pwe3-gal-in-pw (with the changes you’ve proposed), 
> draft-nadeau-pwe3-vccv-2 is an attempt to address your item #2, and 
> your item #3 is not yet addressed. Is this understanding correct?
>
Yes
>
> I also think that one of the items in the discussion was the 
> restriction on ECMP in MPLS to skip reserved labels. I am not sure if 
> it has been properly addressed anywhere, so should not it constitute 
> item #4?
>
Yes-ish, here I am concerned about the practical ability to do that 
given the extent of deployed LSRs that do not do that.

My point here was to note the scope of this draft (which is is IESG review).

Other drafts need to make their own case for what they want to do and 
how they propose to do it.

Stewart




From moore@network-heretics.com  Tue Aug 30 14:15:52 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 825B821F8F24; Tue, 30 Aug 2011 14:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.602
X-Spam-Level: 
X-Spam-Status: No, score=-3.602 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcUT2Q0vBLH2; Tue, 30 Aug 2011 14:15:51 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5A99821F8ED1; Tue, 30 Aug 2011 14:15:51 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 9744D20BD7; Tue, 30 Aug 2011 17:17:19 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 30 Aug 2011 17:17:19 -0400
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=bxFUdczIwENQz2gTu/iNKM87Qz8=; b=uW qS3LHaw2phxR1QLkfyDWTJPnFmwML772gG4rx57SOFJHMabH6LeHfl4hX//mBFGJ jkqmCd6PLHviPrr2+/+t2LxOdBknl0ByuvqzbqH4t+JtPRMdLYu5m21qqwVXGk2e 6kH4VRaqG8hABDlTcdJGBCkeRTxyaScaNSNjUkRRY=
X-Sasl-enc: u+Him1zbBA/m6KapR1hjwaWfWaxJYRL3Bz5tceNeeo3L 1314739039
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 5E63B9603A1; Tue, 30 Aug 2011 17:17:19 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5D45B1.50107@piuha.net>
Date: Tue, 30 Aug 2011 17:17:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com>
References: <4E5D45B1.50107@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 21:15:52 -0000

There's something inherently wrong with trying to establish criteria for =
voting DISCUSS. =20

My understanding was always that DISCUSS was supposed to be an =
indication that, at a minimum, the AD needs to understand the situation =
better before casting a yea or nay vote.   The resolution of a DISCUSS =
might end up being a yes vote, a no objection vote, a request for =
clarification of the document.  It should also be possible for an AD to =
say "now that I've understood better, I can't support this going =
forward"   (for which ABSTAIN is not an appropriate label).

It should never be wrong for an AD to vote DISCUSS, though it's =
reasonable to limit the amount of time during which a DISCUSS can stand =
for a particular document.

It should also never be wrong for an AD to vote NO if the AD has =
initially voted DISCUSS, made a sincere effort to understand the issues, =
believes that he does so, and can state 2026 or other documented =
criteria for why the document is not suitable for approval.

So my recommendations are:=20

1. Fix the broken IESG voting system before you try to establish more =
decision criteria.  I'm serious.  The system you have now is just too =
broken, and has been broken for a long time.  It places too much =
pressure on ADs to cave in when a WG produces flawed output that isn't =
easily fixed.  It is weighed too heavily in favor of approving a =
document - such that one AD can vote YES, another vote DISCUSS, no other =
ADs read the document and all vote NO OBJECTION, and the AD that votes =
DISCUSS will be expected to change that vote to ABSTAIN because nobody =
else felt like reading it.   And the idea that an AD should ever, ever, =
be compelled to change his vote to an ABSTAIN is completely =
unacceptable.  And the "votes" of ADs who haven't read the document =
should not count AT ALL.

Here is a stab at better voting criteria:

- The possible votes are: Yes, No, No Objection, Discuss, Abstain, =
Recuse
- Yes means "I've read it, I believe it meets applicable criteria (2026 =
or whatever else is applicable), that there's community-wide consensus =
to support the document, and that all issues raised by reviewers =
(including directorate, last call comments, etc.) have been adequately =
addressed."
- No means "I've read it, but one or more of the above criteria have =
failed to have been met."  The criteria must be documented.
- No Objection means "I've read it, and I think there are issues with =
it, but I don't think those issues are sufficient to block the =
document".   The criteria should be documented, but the AD isn't =
compelled to do so.
- Discuss means "I have read the document and see at least one potential =
issue which needs to be discussed."  Discuss should always be raised =
before voting No.  However, Discuss votes should time out and be =
replaced by Abstain (if not explicitly changed by the AD) after say 45 =
days.  (however, nothing should ever stop an AD from changing his vote =
to No.)  Note that the ADs, WG chairs, authors, etc. should attempt to =
resolve the issue offline (not during the telechat or other IESG =
meeting) but the discussion should be archived.
- Abstain means "I did not read this", and/or "I don't consider myself =
competent to review this"
- Recuse means "I have a conflict of interest with stating a position on =
this document"

All Discuss votes must be changed (whether explicitly by the AD or by =
automatic timeout) before a ballot is finished.
If there are two or more No votes, all ADs without a conflict of =
interest are expected to read the document, and the vote is taken again.
In order to approve a document or standards action, there must be twice =
as many Yes + No Objection votes as No votes.

2. Don't overconstrain the use of DISCUSS.  In particular, don't ever =
create a situation where a reviewer can't cite a problem with a =
document, regardless of whether that problem has previously been =
enumerated.    It's fine to have guidelines for the benefit of new ADs =
but they should be nonbinding.  You need to have other ways of dealing =
with the occasional stubborn AD who votes DISCUSS or whatever without a =
defensible reason.

This applies to all IESG voting actions, not just moving from PS->DS/IS.

3. I take serious issue with the statement in the draft that IESG =
reviews are "reviews of last resort" and the implication that WG reviews =
are sufficient.  In numerous situations this has not been the case.  I'm =
all for having IESG place greater reliance on directorates (especially =
if this is formalized to some degree), so as to lessen IESG's workload =
to to get individual ADs out of the hot seat.   But for IESG to presume =
by default that the WG has done due diligence is for IESG to shirk its =
responsibility.

4. When evaluating PS->DS/IS actions, IESG should avoid repeating the PS =
review.  Instead it should look at what has changed between PS and =
DS/IS, and what has been learned as a result of implementation and =
deployment experience.   The changes have to be minimal and "safe".    =
No new features can be added, and there needs to be reason to have =
confidence (ideally backed by analysis and implementation experience) =
that any changes made will not impair interoperability between both PS =
and DS/IS versions of the protocol.

Design flaws discovered since approval as PS are also fair game, and =
flaws for which the implications are better understood than at PS time =
should also be fair game.   However it's not fair to revisit an issue =
that was raised at PS approval time, unless new information or =
understanding makes that issue of worse consequence than understood at =
that time.  (e.g. say an issue was raised at PS time and it was decided =
it was too minor to hold up the document, but since then practical DoS =
attacks had been identified that exploited that problem...then it's fair =
to raise the issue.  It's always fair to raise an issue about something =
that actually causes problems.)

What's also not fair game is to "raise the bar" - to expect the document =
at DS to meet more stringent criteria than it was required to meet at =
the time of PS approval.  IESG needs strong justification (e.g. =
community consensus) to raise the bar in this way for standards that are =
actually deployed.  This includes but isn't limited to security issues.
(Though it might be reasonable to make an exception to this if more than =
N years had lapsed since PS approval.)

But IESG should not presume that there are no serious technical issues.  =
 It shouldn't presume one way or the other.  And it shouldn't discourage =
ADs from raising DISCUSSes about technical issues at all.

Keith

On Aug 30, 2011, at 4:18 PM, Jari Arkko wrote:

> During the discussion of the two maturity levels change, a question =
was brought up about DISCUSSes appropriate for documents that advance on =
the standards track. We discussed this in the IESG and I drafted some =
suggested guidelines. Feedback on these suggestions would be welcome. =
The intent is to publish an IESG statement to complement the already =
existing general-purpose DISCUSS criteria IESG statement =
(http://www.ietf.org/iesg/statement/discuss-criteria.html).
>=20
> Here are the suggested guidelines for documents that advance to IS:
>=20
> http://www.arkko.com/ietf/iesg/discuss-criteria-advancing.txt
>=20
> Comments appreciated. Please send comments either on this list or to =
the IESG (iesg@ietf.org) in time before our next telechat (Thursday, =
September 8, 2011).
>=20
> Jari
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From ole@cisco.com  Tue Aug 30 14:29:15 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5565221F8D41 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 14:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHZW7aPJpZlX for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 14:29:14 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 68CBD21F8D3A for <ietf@ietf.org>; Tue, 30 Aug 2011 14:29:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=2608; q=dns/txt; s=iport; t=1314739843; x=1315949443; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=ZwlMWzEfcO4jW8XJif14mGreBZ2Ak0xr0AejJcKun1w=; b=U3sF2BXk4G7k9FOkLnjNrqKdijzisXgV4JAy6b47zk9HFp2vQ2IbotOq +W905I8AJZGMC1jAJHu7enDkyAY73RuZLE+emObphb0MMJAGOjg9/saZW nfKmSi3JKuWzF31l2albxeQh9sHhV5LOlQR2V7JMkNdS38xLn19ZRbFm+ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEpVXU6rRDoH/2dsb2JhbAA/A6hAd4FAAQEBAQIBAQEBDwECASQ0CwULCxguJzAGExQKBIdQBJkwAYMlDwGbZoNCgwsEh2aVOIcr
X-IronPort-AV: E=Sophos;i="4.68,304,1312156800"; d="scan'208";a="17945280"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-6.cisco.com with ESMTP; 30 Aug 2011 21:30:42 +0000
Received: from sjc-vpn6-1246.cisco.com (sjc-vpn6-1246.cisco.com [10.21.124.222]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7ULUfgi009239; Tue, 30 Aug 2011 21:30:41 GMT
Date: Tue, 30 Aug 2011 14:30:41 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Hyatt Taipei cancellation policy?
In-Reply-To: <4E5D4144.1010700@softarmor.com>
Message-ID: <alpine.OSX.2.01.1108301422160.95146@sjc-vpn6-1246.cisco.com>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM> <4E5D4144.1010700@softarmor.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 21:29:15 -0000

Dean,

Before you give up completely I would check out:

http://wikitravel.org/en/Taipei

Taxis are not expensive, the Metro even less so, and there are at 
least some budget hotels nearby. I expect the local hosts to provide
more information soon -- they already have some info on the website.

I agree about the Hyatt hotel price.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Tue, 30 Aug 2011, Dean Willis wrote:

> On 8/23/11 9:24 AM, John C Klensin wrote:
> >
> > So I'm opposed to a USD 200 (or any other number) firm limit on
> > hotel rates.  At the same time, I continue to wish that the IAOC
> > would be more open with the community about how these decisions
> > are made and, in particular, how the tradeoffs between
> > sponsorship (and hence lower costs to the IETF for meeting
> > infrastructure and arrangements) and meetings costs to attendees
> > are made... open enough that the community could give
> > substantive guidance on the subject, guidance that I assume the
> > IAOC would follow if it were coherent and plausible.
> >
> 
> Quite right. There's more than just the hotel rates.
> 
> My budget is about $2500 US per IETF meeting. That has to cover airfare, the
> IETF meeting fee, the hotel, meals, service charges, ground transport, mobile
> phone roaming, incidentals, etc.
> 
> $300 a night counting taxes and surcharge is just ABSOLUTELY OUT OF THE
> FREAKING QUESTION. Having the "backup" hotel a 10 minute taxi ride away is out
> of the question -- I can't afford taxis. If I can't walk, I can't go.
> 
> So guess what? I told the wife last night that I wasn't planning to go to the
> Taiwan meeting. I wanted to go, but I just don't see how it can happen. Maybe
> I'll win the lottery between now and then...
> 
> I'm disappointed. I'm hurt. I'm angry. And the trend has just been getting
> worse and worse with every venue. I want the IAOC's heads on a platter
> (preferably an inexpensive, disposable platter, like maybe the lid off an old
> pizza box) for signing us up to this venue. And I want a travel budget no
> larger than mine for the people we send to future meetings.
> 
> If we can't find a reasonably inexpensive place to have a meeting, DON'T HAVE
> THE MEETING!
> 
> 
> --
> Dean Willis
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From fred@cisco.com  Tue Aug 30 14:50:07 2011
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3221C21F8EC2; Tue, 30 Aug 2011 14:50:07 -0700 (PDT)
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.511, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nEgYHOZDOtfh; Tue, 30 Aug 2011 14:50:06 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 79AFB21F8EC1; Tue, 30 Aug 2011 14:50:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2688; q=dns/txt; s=iport; t=1314741095; x=1315950695; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=uf7jukaA/yOCFj9r/xU18qz6PIUY4SoizxmjjfZIh80=; b=VBKnODb44gKrX1vxP+ZLZIXYQo+H35xqGL0aLbVBgj3eck7sgQ06VANz +vtA18eQnpB5URJydQmadKrCwWWKjVz+rxW9Zp9WpciMcZ3FLXMeU48CQ bLQ14vvS4GGYcQuRP1UJp70xgEH8WNHffRoVDnaLDDh5ssrHg4vY8cXtO c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOFaXU6rRDoG/2dsb2JhbABCqEB3gUABAQEBAgESASc5BgULCxguVwY1h1CZGwGfGYVtYASHZos+hQ6MFw
X-IronPort-AV: E=Sophos;i="4.68,304,1312156800"; d="scan'208";a="17958163"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by rcdn-iport-1.cisco.com with ESMTP; 30 Aug 2011 21:51:34 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p7ULpX4r015230; Tue, 30 Aug 2011 21:51:33 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Tue, 30 Aug 2011 14:51:33 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Tue, 30 Aug 2011 14:51:33 -0700
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com>
Date: Tue, 30 Aug 2011 14:51:01 -0700
Message-Id: <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 21:50:07 -0000

On Aug 30, 2011, at 2:17 PM, Keith Moore wrote:
> My understanding was always that DISCUSS was supposed to be an =
indication that, at a minimum, the AD needs to understand the situation =
better before casting a yea or nay vote.   The resolution of a DISCUSS =
might end up being a yes vote, a no objection vote, a request for =
clarification of the document.  It should also be possible for an AD to =
say "now that I've understood better, I can't support this going =
forward"   (for which ABSTAIN is not an appropriate label).
>=20
> It should never be wrong for an AD to vote DISCUSS, though it's =
reasonable to limit the amount of time during which a DISCUSS can stand =
for a particular document.
>=20
> It should also never be wrong for an AD to vote NO if the AD has =
initially voted DISCUSS, made a sincere effort to understand the issues, =
believes that he does so, and can state 2026 or other documented =
criteria for why the document is not suitable for approval.

I agree in part. My problem is that even some ADs tell me that ADs =
sometimes behave as if they haven't done their job if they haven't =
produced a "discuss". A few months ago, I got a "discuss" on a document =
that in essence said "what should I be writing a 'discuss' about?". I =
have no problem with valid concerns, and many of the concerns raised are =
valid. It should be possible for a working group to produce a quality =
document and have the IESG simply approve it, however. I'm not sure it =
is.

> Discuss votes should time out and be replaced by Abstain (if not =
explicitly changed by the AD) after say 45 days. =20

There I disagree. If the AD raised a valid issue, the ball is in the =
author/wg's court to address it. They can game this rule by not =
responding until after 45 days.

Personally, I would rather see the document returned to the author/wg if =
review results in a request for major changes. In my working group, we =
recently had one draft completely rewritten in the response to =
"discuss"es, and I pulled it back for the WG to decide whether it still =
had consensus around the resulting draft. I would say the same about a =
"discuss" that is not adequately responded to in 45 days; the IESG =
should clean it off their plate.

> What's also not fair game is to "raise the bar" - to expect the =
document at DS to meet more stringent criteria than it was required to =
meet at the time of PS approval.

Hmmm, the "demonstrated interoperability" requirement of DS/IS is in =
fact a raising of the bar,and one that has served us well. We don't =
(although IMHO we should) require even an implementation to go to PS.=20=

From moore@network-heretics.com  Tue Aug 30 15:24:21 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98FF521F8F5E; Tue, 30 Aug 2011 15:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level: 
X-Spam-Status: No, score=-3.301 tagged_above=-999 required=5 tests=[AWL=-0.303, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 931jOagmMDVt; Tue, 30 Aug 2011 15:24:20 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 4A71C21F8F5B; Tue, 30 Aug 2011 15:24:20 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id BA71120DDB; Tue, 30 Aug 2011 18:25:48 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 30 Aug 2011 18:25:48 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Llr ec2DwiFzrVc9Ta+xm7i/bBNc=; b=O7q8j7ABjLDFuFjilT1Hm4GIskWWhXof1Bo u2MFHet9bpdML/SR1IET/c8mDPoc3+tdPnZq4UgzRuOX1aVqv4NAiENX08A2+kWX 6DBDg5+ySxqSdEjLA3XdupJwtX4+acsk20bJwMIMPvihG19onZBnlc6AVwYqD/Xl EtcRXNX4=
X-Sasl-enc: k2/ZUoVfQCQLxS43v7f1SMiypRCYjN5YLHu0Mmzkj042 1314743148
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 55D2796034D; Tue, 30 Aug 2011 18:25:48 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-66--718984401
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>
Date: Tue, 30 Aug 2011 18:25:48 -0400
Message-Id: <2660CD8D-EAD7-4F98-84BD-59BE6D667031@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 22:24:21 -0000

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

On Aug 30, 2011, at 5:51 PM, Fred Baker wrote:

>=20
> On Aug 30, 2011, at 2:17 PM, Keith Moore wrote:
>> My understanding was always that DISCUSS was supposed to be an =
indication that, at a minimum, the AD needs to understand the situation =
better before casting a yea or nay vote.   The resolution of a DISCUSS =
might end up being a yes vote, a no objection vote, a request for =
clarification of the document.  It should also be possible for an AD to =
say "now that I've understood better, I can't support this going =
forward"   (for which ABSTAIN is not an appropriate label).
>>=20
>> It should never be wrong for an AD to vote DISCUSS, though it's =
reasonable to limit the amount of time during which a DISCUSS can stand =
for a particular document.
>>=20
>> It should also never be wrong for an AD to vote NO if the AD has =
initially voted DISCUSS, made a sincere effort to understand the issues, =
believes that he does so, and can state 2026 or other documented =
criteria for why the document is not suitable for approval.
>=20
> I agree in part. My problem is that even some ADs tell me that ADs =
sometimes behave as if they haven't done their job if they haven't =
produced a "discuss". A few months ago, I got a "discuss" on a document =
that in essence said "what should I be writing a 'discuss' about?". I =
have no problem with valid concerns, and many of the concerns raised are =
valid. It should be possible for a working group to produce a quality =
document and have the IESG simply approve it, however. I'm not sure it =
is.

The first time I reviewed a document as an AD, I realized I was working =
very hard to find something wrong.  And I did - I found a bona fide (and =
uncontroversial) technical flaw - actually an incorrect value for a =
constant.  But after that I got over needing to find things that were =
wrong.   I found plenty of issues without trying to do anything more =
than read and understand the documents - and had quite enough work to do =
just reading and understanding them and writing up those issues without =
making more work for myself.  (Especially when other ADs would often =
demand that I not only identify the issues but also specify the fixes - =
something I always regarded as out-of-scope for an AD and even =
potentially "tampering" with WG output.)

So I don't disagree that ADs sometime believe that they need to vote =
Discuss or they're not doing their jobs.  Though I have a hard time =
believing that the drafts coming out of WGs these days are so good that =
ADs have to work hard to find things that are wrong with many of them.   =
If they're trying to find a reason to Discuss every document, well I =
guess that is a problem.   But overall, it seems like there are far more =
incentives to avoid finding reasons to object to a document, than there =
are to find them.

>> Discuss votes should time out and be replaced by Abstain (if not =
explicitly changed by the AD) after say 45 days. =20
>=20
> There I disagree. If the AD raised a valid issue, the ball is in the =
author/wg's court to address it. They can game this rule by not =
responding until after 45 days.

I don't think I stated that rule very well.   If the author/wg fail to =
address the issue within 45 days, the AD should of course be able to =
change the vote to No.  The point is that the Discuss should inherently =
be a temporary state, a time during which the AD doesn't vote No (yet) =
but lets the author/WG know that he has issues with a document.  And the =
idea is to encourage those parties enough time to understand each other =
and work out their differences before bringing the issue to a firm vote. =
 But I don't think that the WG should be able to game the rule to force =
the AD's objection to go away, nor should the AD be able to =
singlehandedly block a document.

> Personally, I would rather see the document returned to the author/wg =
if review results in a request for major changes. In my working group, =
we recently had one draft completely rewritten in the response to =
"discuss"es, and I pulled it back for the WG to decide whether it still =
had consensus around the resulting draft. I would say the same about a =
"discuss" that is not adequately responded to in 45 days; the IESG =
should clean it off their plate.

IMO, any time a document is significantly revised, IESG should consider =
it a separate item, requiring a new Last Call, writeup, ballot, etc.

>> What's also not fair game is to "raise the bar" - to expect the =
document at DS to meet more stringent criteria than it was required to =
meet at the time of PS approval.
>=20
> Hmmm, the "demonstrated interoperability" requirement of DS/IS is in =
fact a raising of the bar,and one that has served us well. We don't =
(although IMHO we should) require even an implementation to go to PS.

I should have been more specific.  By "raising the bar" I was thinking =
about things like design decisions, and document quality.   If feature =
FOO was judged to be of adequate design at PS, it's not fair to say it's =
not adequate on DS review unless there's some new information that =
demonstrates that it doesn't work well.  Or if the wording of a document =
was okay with IESG at PS, it's not fair for an AD to nitpick that =
wording at DS review time unless there's some reason to believe that the =
wording caused problems. For those cases the AD can always file an =
erratum.

Keith


--Apple-Mail-66--718984401
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><div>On Aug 30, 2011, at 5:51 PM, Fred Baker wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><br>On =
Aug 30, 2011, at 2:17 PM, Keith Moore wrote:<br><blockquote =
type=3D"cite">My understanding was always that DISCUSS was supposed to =
be an indication that, at a minimum, the AD needs to understand the =
situation better before casting a yea or nay vote. &nbsp;&nbsp;The =
resolution of a DISCUSS might end up being a yes vote, a no objection =
vote, a request for clarification of the document. &nbsp;It should also =
be possible for an AD to say "now that I've understood better, I can't =
support this going forward" &nbsp;&nbsp;(for which ABSTAIN is not an =
appropriate label).<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">It should never =
be wrong for an AD to vote DISCUSS, though it's reasonable to limit the =
amount of time during which a DISCUSS can stand for a particular =
document.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">It should also =
never be wrong for an AD to vote NO if the AD has initially voted =
DISCUSS, made a sincere effort to understand the issues, believes that =
he does so, and can state 2026 or other documented criteria for why the =
document is not suitable for approval.<br></blockquote><br>I agree in =
part. My problem is that even some ADs tell me that ADs sometimes behave =
as if they haven't done their job if they haven't produced a "discuss". =
A few months ago, I got a "discuss" on a document that in essence said =
"what should I be writing a 'discuss' about?". I have no problem with =
valid concerns, and many of the concerns raised are valid. It should be =
possible for a working group to produce a quality document and have the =
IESG simply approve it, however. I'm not sure it =
is.<br></div></blockquote><div><br></div>The first time I reviewed a =
document as an AD, I realized I was working very hard to find something =
wrong. &nbsp;And I did - I found a bona fide (and uncontroversial) =
technical flaw - actually an incorrect value for a constant. &nbsp;But =
after that I got over needing to find things that were wrong. &nbsp; I =
found plenty of issues without trying to do anything more than read and =
understand the documents - and had quite enough work to do just reading =
and understanding them and writing up those issues without making more =
work for myself. &nbsp;(Especially when other ADs would often demand =
that I not only identify the issues but also specify the fixes - =
something I always regarded as out-of-scope for an AD and even =
potentially "tampering" with WG output.)</div><div><br></div><div>So I =
don't disagree that ADs sometime believe that they need to vote Discuss =
or they're not doing their jobs. &nbsp;Though I have a hard time =
believing that the drafts coming out of WGs these days are so good that =
ADs have to work hard to find things that are wrong with many of them. =
&nbsp; If they're trying to find a reason to Discuss <i>every</i> =
document, well I guess that is a problem. &nbsp; But overall, it seems =
like there are far more incentives to avoid finding reasons to object to =
a document, than there are to find =
them.</div><div><br></div><div><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">Discuss votes should time out and be replaced by Abstain =
(if not explicitly changed by the AD) after say 45 days. =
&nbsp;<br></blockquote><br>There I disagree. If the AD raised a valid =
issue, the ball is in the author/wg's court to address it. They can game =
this rule by not responding until after 45 =
days.<br></div></blockquote><div><br></div>I don't think I stated that =
rule very well. &nbsp; If the author/wg fail to address the issue within =
45 days, the AD should of course be able to change the vote to No. =
&nbsp;The point is that the Discuss should inherently be a temporary =
state, a time during which the AD doesn't vote No (yet) but lets the =
author/WG know that he has issues with a document. &nbsp;And the idea is =
to encourage those parties enough time to understand each other and work =
out their differences before bringing the issue to a firm vote. =
&nbsp;But I don't think that the WG should be able to game the rule to =
force the AD's objection to go away, nor should the AD be able to =
singlehandedly block a document.</div><div><br><blockquote =
type=3D"cite"><div>Personally, I would rather see the document returned =
to the author/wg if review results in a request for major changes. In my =
working group, we recently had one draft completely rewritten in the =
response to "discuss"es, and I pulled it back for the WG to decide =
whether it still had consensus around the resulting draft. I would say =
the same about a "discuss" that is not adequately responded to in 45 =
days; the IESG should clean it off their =
plate.<br></div></blockquote><div><br></div><div>IMO, any time a =
document is significantly revised, IESG should consider it a separate =
item, requiring a new Last Call, writeup, ballot, =
etc.</div><br><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">What's also not fair game is to "raise the bar" - to =
expect the document at DS to meet more stringent criteria than it was =
required to meet at the time of PS approval.<br></blockquote><br>Hmmm, =
the "demonstrated interoperability" requirement of DS/IS is in fact a =
raising of the bar,and one that has served us well. We don't (although =
IMHO we should) require even an implementation to go to PS. =
</div></blockquote></div><br><div>I should have been more specific. =
&nbsp;By "raising the bar" I was thinking about things like design =
decisions, and document quality. &nbsp; If feature FOO was judged to be =
of adequate design at PS, it's not fair to say it's not adequate on DS =
review unless there's some new information that demonstrates that it =
doesn't work well. &nbsp;Or if the wording of a document was okay with =
IESG at PS, it's not fair for an AD to nitpick that wording at DS review =
time unless there's some reason to believe that the wording caused =
problems. For those cases the AD can always file an =
erratum.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-66--718984401--

From ned+ietf@mauve.mrochek.com  Tue Aug 30 15:38:57 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 422D521F8A95 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 15:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJ7Xumjfspjw for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 15:38:56 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB3621F8A6C for <ietf@ietf.org>; Tue, 30 Aug 2011 15:38:56 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5GSU9UT68010I0O@mauve.mrochek.com> for ietf@ietf.org; Tue, 30 Aug 2011 15:39:06 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O5FCUOO1PS00RCTX@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 30 Aug 2011 15:39:02 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O5GSU8EM7O00RCTX@mauve.mrochek.com>
Date: Tue, 30 Aug 2011 15:38:06 -0700 (PDT)
Subject: Re: 2119bis
In-reply-to: "Your message dated Tue, 30 Aug 2011 09:56:06 -0400" <ABF8FB5A-AAA7-419D-BBFA-FF11DA263837@network-heretics.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com> <ABF8FB5A-AAA7-419D-BBFA-FF11DA263837@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1314743977; i=@mrochek.com; bh=VD3Q6LrB0SjD51f4EmCCcUWxpv3DmJZrO0IikXcNGZI=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=XLRA4xE41krbW2vq4nYcH5US4stgznu0YFmLxgcFVlUXqo7nPl5+6toUYA6gBfRBo sLXGt4Y91fKvTPR6oCFMmsAnreW1KCFSfuZJS/FaRIdl9plvYjQVJsidgDX8AVpzkk ROqecfcGWI3Xx+sp+U+v8qE0iQ4IMxrBE38BuN58=
Cc: Eric Burger <eburger@standardstrack.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 22:38:57 -0000

> On Aug 30, 2011, at 9:24 AM, Marshall Eubanks wrote:

> > I support adding the SHOULD ... UNLESS formalism (although maybe it should be MUST... UNLESS). It would be useful as there will be times where the UNLESS can be specified and has been given due consideration at the time of writing. That, however, will not always be the case. (More inline).

> How would SHOULD...UNLESS or MUST...UNLESS differ from using the current 2119 definitions and just writing SHOULD...unless or MUST ... unless?

> Personally I think 2119 is just fine and doesn't need to be updated.

+1. I'm still not seeing sufficient justification to open this particular can
of worms at this juncture.

				Ned

From brian.e.carpenter@gmail.com  Tue Aug 30 17:12:28 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 131DA21F8D90; Tue, 30 Aug 2011 17:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V89T08482Cdx; Tue, 30 Aug 2011 17:12:27 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id B19E521F8D8C; Tue, 30 Aug 2011 17:12:26 -0700 (PDT)
Received: by pzk33 with SMTP id 33so523955pzk.18 for <multiple recipients>; Tue, 30 Aug 2011 17:13:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AMsWktgTXarxgT9YHfhNi92bYkGbB3AP9LxBhGofkRQ=; b=LM3pRjy+0XKpAkjLvq/CuXsYRMwpfLiXQBrAkhWQRrNCm96kroIdPW298g+3pQ2hGY Evv1DhYFus7CDUm52xCTzMZBtrCNnp/C+3kFZ04ZitSXFAwC2s+a8dV3+qgRRmrXah6w cUqbeEfTGE4U5wW6G0hYokmYVy4XiZWv115cc=
Received: by 10.143.99.21 with SMTP id b21mr1049454wfm.431.1314749635246; Tue, 30 Aug 2011 17:13:55 -0700 (PDT)
Received: from [202.106.79.19] ([202.106.79.19]) by mx.google.com with ESMTPS id w18sm4564594wfg.21.2011.08.30.17.13.52 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 17:13:54 -0700 (PDT)
Message-ID: <4E5D7CB9.9060903@gmail.com>
Date: Wed, 31 Aug 2011 12:13:45 +1200
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: Fred Baker <fred@cisco.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
References: <4E5D45B1.50107@piuha.net>	<DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>
In-Reply-To: <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 00:12:28 -0000

On 2011-08-31 09:51, Fred Baker wrote:

...
> If the AD raised a valid issue, the ball is in the author/wg's court to address it. They can game this rule by not responding until after 45 days.

Not if the draft has been updated and the AD doesn't either cancel the DISCUSS within
a reasonable time*, or explain why the update is insufficient. This happens, probably
as often as authors failing to address an issue within a reasonable time. Whichever
party is responsible for the delay should be subject to a timeout, surely.

That said, I disagree with Keith. The current DISCUSS criteria were written
for a very specific reason - to get rid of the type of DISCUSS listed in the
"non-criteria". There was a lot of analysis done of documents that were stuck
in the IESG for months in the 2004/2005 timeframe, and the non-criteria describe
the problem cases - DISCUSSes that were not actionable or simply expressed the
fact that the AD didn't like the WG's informed consensus.

Of course nothing's perfect and I'm sure the criteria could be improved. But
not having them was much worse.

* for example, is "IESG Evaluation::AD Followup (for 32 days)" a reasonable
  delay for a Discussing AD to review an updated draft [hint, hint]?

     Brian

From brian.e.carpenter@gmail.com  Tue Aug 30 17:39:20 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9114921F8CFC for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 17:39:20 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W43AhsaZC5VK for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 17:39:19 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id A91C621F8CF7 for <ietf@ietf.org>; Tue, 30 Aug 2011 17:39:19 -0700 (PDT)
Received: by pzk33 with SMTP id 33so569937pzk.18 for <ietf@ietf.org>; Tue, 30 Aug 2011 17:40:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aj6UJ/xZ5DOgRBCFZh19v/+juFhrqlUu2XTpJAfeiGU=; b=w0yXk8Vkzs/jfTv9HHUtfFsn5H5czDbub/KFqGwKD3SfiEd3S2oyZMpfyQPVVAA9X7 N8XwPs6Ip/PYJjXmyas2c53qhfqWoEtUokm+AZeka2P73sPpqryEkJuybA+yPEWtkAjP Lg3CvEixKDegy8zlY3k8wDDIaCtIj7VJmzeT8=
Received: by 10.68.28.7 with SMTP id x7mr50223pbg.526.1314751248429; Tue, 30 Aug 2011 17:40:48 -0700 (PDT)
Received: from [202.106.79.19] ([202.106.79.19]) by mx.google.com with ESMTPS id t6sm12125290pbg.4.2011.08.30.17.40.45 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 17:40:47 -0700 (PDT)
Message-ID: <4E5D8091.40802@gmail.com>
Date: Wed, 31 Aug 2011 12:30:09 +1200
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: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Discuss criteria for documents that advance on the standards track
References: <4E5D45B1.50107@piuha.net>
In-Reply-To: <4E5D45B1.50107@piuha.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 00:39:20 -0000

On 2011-08-31 08:18, Jari Arkko wrote:
...
> Here are the suggested guidelines for documents that advance to IS:
> 
> http://www.arkko.com/ietf/iesg/discuss-criteria-advancing.txt
> 
> Comments appreciated.

To answer Jari's original request: +1 to these new guidelines.

Not worth nit-picking until we have some experience.

   Brian


From brian.e.carpenter@gmail.com  Tue Aug 30 17:39:26 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDEF21F8D20 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 17:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FlJOMrkcQGAl for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 17:39:26 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3E421F8D1F for <ietf@ietf.org>; Tue, 30 Aug 2011 17:39:26 -0700 (PDT)
Received: by mail-pz0-f45.google.com with SMTP id 33so569937pzk.18 for <ietf@ietf.org>; Tue, 30 Aug 2011 17:40:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=91sNqUbM1phv0yxrM/n0pLMsuU22yNqVtBcRnTTHwlM=; b=hj5B8MFa6eF1JV8K7N75irg9ckjQQyGtDrN2UzCfA6Afg0BetSPC7cet6ZI2VCAcWn 6y2R6ig5hlIm72I25VTsL7uInBeCv/3jxIXQnG/Psv4kqvqY8lcYwh1AgneUIwhLvHx6 N7nJ9J4KHHD79Fvp1YmV6hUacjSwRqnDhEGZ0=
Received: by 10.68.16.196 with SMTP id i4mr63035pbd.512.1314751255301; Tue, 30 Aug 2011 17:40:55 -0700 (PDT)
Received: from [202.106.79.19] ([202.106.79.19]) by mx.google.com with ESMTPS id e6sm5291704wfh.2.2011.08.30.17.40.51 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 17:40:54 -0700 (PDT)
Message-ID: <4E5D80D0.7060608@gmail.com>
Date: Wed, 31 Aug 2011 12:31:12 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<CAJNg7V+P0_QvaOLmhLVhRd7T5NMteoCG_ZSo1ZHiUzcXg8AMRw@mail.gmail.com>	<ABF8FB5A-AAA7-419D-BBFA-FF11DA263837@network-heretics.com> <01O5GSU8EM7O00RCTX@mauve.mrochek.com>
In-Reply-To: <01O5GSU8EM7O00RCTX@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, Eric Burger <eburger@standardstrack.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 00:39:26 -0000

On 2011-08-31 10:38, ned+ietf@mauve.mrochek.com wrote:
>> On Aug 30, 2011, at 9:24 AM, Marshall Eubanks wrote:
> 
>>> I support adding the SHOULD ... UNLESS formalism (although maybe it should be MUST... UNLESS). It would be useful as there will be times where the UNLESS can be specified and has been given due consideration at the time of writing. That, however, will not always be the case. (More inline).
> 
>> How would SHOULD...UNLESS or MUST...UNLESS differ from using the current 2119 definitions and just writing SHOULD...unless or MUST ... unless?
> 
>> Personally I think 2119 is just fine and doesn't need to be updated.
> 
> +1. I'm still not seeing sufficient justification to open this particular can
> of worms at this juncture.

+ another 1.

    Brian


From barryleiba.mailing.lists@gmail.com  Tue Aug 30 19:25:01 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0D4521F8D77 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 19:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.026
X-Spam-Level: 
X-Spam-Status: No, score=-103.026 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q139ZHJEycb1 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 19:25:01 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1164121F8D6D for <ietf@ietf.org>; Tue, 30 Aug 2011 19:25:01 -0700 (PDT)
Received: by gxk19 with SMTP id 19so234875gxk.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 19:26:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=y5JW/nzE7uARQun2VWkqoW7EKRVuTAa4WJCtVfwr1i8=; b=ANyfqrngt6oNwjJ6TzFLZ8vgNy5PoHF4/0UF9+xYgPTexkrbLWe8XngnnilDlaHXX+ qVNdvrbR+r7X5qQQhywXerwKxjgRvNek0KIZYn8fnrxevORHZyk5v7uSmsBd39hC7AVo AHDfI/86T/kzbs/UbhQypYxapTBt3DLi5vjc0=
MIME-Version: 1.0
Received: by 10.147.53.37 with SMTP id f37mr5875343yak.25.1314757589709; Tue, 30 Aug 2011 19:26:29 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.146.83.8 with HTTP; Tue, 30 Aug 2011 19:26:29 -0700 (PDT)
In-Reply-To: <4E5C34DD.2010905@santronics.com>
References: <4E5C067A.9080400@stpeter.im> <4E5C34DD.2010905@santronics.com>
Date: Tue, 30 Aug 2011 22:26:29 -0400
X-Google-Sender-Auth: AWBuJ0vL4l_WL0WhuwVtDIe9hAo
Message-ID: <CAC4RtVCw=0vkYeBDgRudKYsNqL5WY1_uH+Q_X+kGZq-TM6duug@mail.gmail.com>
Subject: Re: 2119bis
From: Barry Leiba <barryleiba@computer.org>
To: Hector Santos <hsantos@santronics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 02:25:01 -0000

Just responding to a small part, here:

> =A0 B) RFC2119 states SHOULD is the same as the adjective "RECOMMENDED."
>
> As far I am concern, a recommendation is not a mandate nor obligation.

The problem we have with using what look like English words for these
things is that people have expectations about what those words mean.
Notwithstanding that, these words, in this context, are technical
terms, not English words.  One can't look them up in a dictionary, nor
use one's own sense, as a speaker of English, to determine what they
mean.  One must only use what RFC 2119 says.

It says this:

   3. SHOULD This word, or the adjective "RECOMMENDED", mean
   that there may exist valid reasons in particular circumstances to ignore
   a particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

That's not the same as many people's understanding of the English
meaning of the words "should" and "recommended", which are similar in
appearance to the technical terms defined in RFC 2119.

Of course, then we run into interpretations of the definitions of the
terms, and exactly what that sentence in item 3 in RFC 2119 *means*,
but I'm not getting into that here.  This may be where you, I, Peter,
and/or the AD in question differ.

But don't make the mistake of thinking that, in the context of RFC
2119, one can use one's own English sense of what the meanings of
these terms are.

Barry

From rbarnes@bbn.com  Tue Aug 30 20:19:07 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8DC521F8C49 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 20:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.604
X-Spam-Level: 
X-Spam-Status: No, score=-106.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXewWTEX77dR for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 20:19:06 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 14A3521F8C1A for <ietf@ietf.org>; Tue, 30 Aug 2011 20:18:57 -0700 (PDT)
Received: from [128.89.253.18] (port=55746 helo=col-rbarnes-l1-2.local) by smtp.bbn.com with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1QybLj-000Lgg-NS; Tue, 30 Aug 2011 23:20:24 -0400
Message-ID: <4E5DA875.1070304@bbn.com>
Date: Tue, 30 Aug 2011 23:20:21 -0400
From: Richard Barnes <rbarnes@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5CF034.6040308@acm.org> <2B9BA4D2-C1CC-4CEF-B7F7-8ED5E5D3B299@network-heretics.com> <4E5CF98A.5090204@acm.org> <54FC3B88-123D-4A59-BE69-46FB87A3CFB1@network-heretics.com> <4E5D0410.1080000@acm.org> <4E4504EF-B57E-4FE4-9B7F-8CE2CD73154C@network-heretics.com> <4E5D0A8D.2040501@acm.org> <FEB38139-8FC6-4545-B9A8-F4D84FD6AE76@network-heretics.com> <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com>
In-Reply-To: <245A0FA3-6739-4B79-8B2C-E40CE74781BF@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 03:19:07 -0000

Friendly reminder from BCP 61: Security is a "MUST implement"
<http://tools.ietf.org/html/bcp61#section-7>


On 8/30/11 12:46 PM, Eric Burger wrote:
> Can you give an example of where a dangling SHOULD makes sense?  Most often I see something like:
> 	SHOULD implement security
> meaning
> 	SHOULD implement security, unless you do not feel like it or are in an authoritarian regime that bans security
>
>
> On Aug 30, 2011, at 12:11 PM, Keith Moore wrote:
>
>> On Aug 30, 2011, at 12:06 PM, Marc Petit-Huguenin wrote:
>>
>>> The meaning of SHOULD is clear for the authors (it "mean[s] that there may exist
>>> valid reasons in particular circumstances to ignore a particular item, but the
>>> full implications must be understood and carefully weighed before choosing a
>>> different course."), the problem is that some implementers use a different
>>> meaning (I do not have to implement this if it is inconvenient or difficult for
>>> me to implement), vendors another one (SHOULD gave us the right to not implement
>>> it).  I even read somewhere, perhaps on this list, about a vendor that rejected
>>> any bug report against a SHOULD.  Conditional MUST, in my opinion, does not have
>>> this problem.
>>
>> But conditional MUST has other problems, namely that you have to enumerate the exceptions for the MUST, and that's not always practical.
>>
>> Implementors who think that SHOULD gives them a free pass to avoid implementing something that's needed to interoperate are misreading 2119.  But document editors should avoid using SHOULD for cases where failure to implement the requirement will result in interoperability failure.
>>
>> I could see maybe posting an erratum or a brief update to 2119, but I think that reopening that document in general is a Very bad Idea.  And for existing documents that misuse SHOULD, the appropriate thing to do is to update those documents or post errata to those documents, rather than try to retroactively change the meaning of the keywords in those documents.
>>
>> Keith
>>
>> _______________________________________________
>> 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 dean.willis@softarmor.com  Tue Aug 30 20:29:08 2011
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF7C421F8C69 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 20:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.418
X-Spam-Level: 
X-Spam-Status: No, score=-103.418 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrMHqm-KIejm for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 20:29:08 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 211F521F8C5E for <ietf@ietf.org>; Tue, 30 Aug 2011 20:29:08 -0700 (PDT)
Received: by yie12 with SMTP id 12so307670yie.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 20:30:37 -0700 (PDT)
Received: by 10.90.213.9 with SMTP id l9mr1941agg.182.1314761436996; Tue, 30 Aug 2011 20:30:36 -0700 (PDT)
Received: from dwillis-mb1.local (cpe-66-25-15-110.tx.res.rr.com [66.25.15.110]) by mx.google.com with ESMTPS id s15sm6773163ank.19.2011.08.30.20.30.36 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 20:30:36 -0700 (PDT)
Message-ID: <4E5DAADB.3060902@softarmor.com>
Date: Tue, 30 Aug 2011 22:30:35 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 2119bis -- Tying our hands?
References: <4E5C067A.9080400@stpeter.im> <8B0A9FCBB9832F43971E38010638454F040F1C12B5@SISPE7MB1.commscope.com> <4E5D351F.8050000@nostrum.com>
In-Reply-To: <4E5D351F.8050000@nostrum.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 03:29:08 -0000

On 8/30/11 2:08 PM, Adam Roach wrote:
> Because the current suggestion -- which turns RFC writing into the game
> "Taboo" [1], but with incredibly common English words [2] as the
> forbidden list -- is ridiculous on its face.

Don't use requirements language unless you absolutely have to. 
Otherwise, explain things in clear prose, describing what happens in 
normal and error cases, and the logic used in distinguishing them.

If you absolutely require RFC 2119 requirements language to make 
something clear, I suggest the following symbology:


âœ”: MUST
â˜‚: SHOULD
â™¥: MAY
âœ–: MUST NOT
â™ : SHOULD NOT
â˜¹: MAY NOT

And the fact that the above is garbled for some large percentage of 
readers explains why we use 7-bit ASCII in drafts, so let's just stop 
that argument now, ok?

--
Dean

From Martin.Thomson@commscope.com  Tue Aug 30 20:46:20 2011
Return-Path: <Martin.Thomson@commscope.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 515FD21F8B37 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 20:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level: 
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a572Y2M-Gxpr for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 20:46:19 -0700 (PDT)
Received: from cdcsmgw01.commscope.com (fw.commscope.com [198.135.207.129]) by ietfa.amsl.com (Postfix) with ESMTP id B475F21F8B32 for <ietf@ietf.org>; Tue, 30 Aug 2011 20:46:19 -0700 (PDT)
X-AuditID: 0a0404e8-b7b6dae00000237b-2b-4e5daee1010e
Received: from ACDCE7HC2.commscope.com ( [10.86.20.103]) by cdcsmgw01.commscope.com (Symantec Brightmail Gateway) with SMTP id D4.9C.09083.1EEAD5E4; Tue, 30 Aug 2011 22:47:45 -0500 (CDT)
Received: from CDCE10HC1.commscope.com (10.86.28.21) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.3.159.2; Tue, 30 Aug 2011 22:47:44 -0500
Received: from SISPE7HC1.commscope.com (10.97.4.12) by CDCE10HC1.commscope.com (10.86.28.21) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 30 Aug 2011 22:47:44 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Wed, 31 Aug 2011 11:47:43 +0800
From: "Thomson, Martin" <Martin.Thomson@commscope.com>
To: Adam Roach <adam@nostrum.com>
Date: Wed, 31 Aug 2011 11:47:42 +0800
Subject: RE: 2119bis -- Tying our hands?
Thread-Topic: 2119bis -- Tying our hands?
Thread-Index: AcxnSC7JyV+wotVZSVWRiuI4oANmhgAQ4uDA
Message-ID: <8B0A9FCBB9832F43971E38010638454F040F1C13BA@SISPE7MB1.commscope.com>
References: <4E5C067A.9080400@stpeter.im> <8B0A9FCBB9832F43971E38010638454F040F1C12B5@SISPE7MB1.commscope.com> <4E5D351F.8050000@nostrum.com>
In-Reply-To: <4E5D351F.8050000@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
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.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 03:46:20 -0000

My first reaction was that the entire topic is a bike shed.  The goal is cl=
ear and understandable specifications and 2119 is just a tool we use to mak=
e the process of producing and reading specifications more efficient.

What I'm getting from this is that there are a significant number of drafts=
 being submitted to the IESG for publication that are not sufficiently prec=
ise in their use of language.

Deciding to revise 2119 seems - at first blush - an interesting reaction to=
 this problem.  But it's become evident that we don't share a common unders=
tanding of the language, nor are we consistent in its application.

Formalizing usage patterns (c.f. server MUST/client MAY, MUST...UNLESS...) =
does help, if only because you've made it easier to do the right thing in m=
ore cases.  If the problem is that authors and editors don't have the tools=
 they need, then maybe a revision is the right approach.

However, I'd still like to see more RFCs that describe something without re=
sorting to using these crude implements.

On 2011-08-31 at 05:08:15, Adam Roach wrote:
> There is no reason to tie authors' hands by restricting them from=20
> using perfectly good English words just because they happen to be the=20
> same symbols used by RFC 2119. If we're going down this path, let's=20
> scrap using MUST/SHOULD/MAY/etc, and formalize our conformance terms=20
> with symbols that aren't English words.




From evnikita2@gmail.com  Tue Aug 30 21:03:21 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABE721F8C4D for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 21:03:21 -0700 (PDT)
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.130,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0KJfJ0pdEMag for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 21:03:20 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id B6AB521F8C4B for <ietf@ietf.org>; Tue, 30 Aug 2011 21:03:19 -0700 (PDT)
Received: by bkar4 with SMTP id r4so415391bka.31 for <ietf@ietf.org>; Tue, 30 Aug 2011 21:04:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bGrEBq1wI9VT43IAVsfSbxHYqwaDThN8dTamQwxZC+o=; b=Nus3ehjAi7uHnJb6lU+Pgpy9zJGwhlBSD+RNCPkKuQ1+KvzOzyUdR17O/gbkRH7+zt a45G8KmLSzwFj5MKuEo+I6p0GnmWPmahJAHbDUMgEq0HHswcCG5VDlQMx/IBdX4gsKBL UU8zd6yoTbK8zzQTxLv6GgcuiE8QWIxOVt3x8=
Received: by 10.204.135.141 with SMTP id n13mr573914bkt.290.1314763488238; Tue, 30 Aug 2011 21:04:48 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id s10sm193862bka.31.2011.08.30.21.04.47 (version=SSLv3 cipher=OTHER); Tue, 30 Aug 2011 21:04:47 -0700 (PDT)
Message-ID: <4E5DB2FF.9050402@gmail.com>
Date: Wed, 31 Aug 2011 07:05:19 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Limitations in RFC Errata mechanism
References: <4E5CFF6A.30004@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9A2@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF9A2@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 04:03:21 -0000

30.08.2011 22:09, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mykyta Yevstifeyev
>> Sent: Tuesday, August 30, 2011 8:19 AM
>> To: IETF Discussion
>> Subject: Limitations in RFC Errata mechanism
>>
>> First, we have only two types of errata - Technical or Editorial.  In presence of
>> <http://www.ietf.org/iesg/statement/rfc-metadata-errata.html>, "IESG
>> Statement on IESG Processing of RFC Errata concerning RFC Metadata", I
>> think the third type is necessary - Metadata.
> I think given the current mechanism I would just submit such things under "Editorial".

This is an option; but doing so makes work of RFC Editor when 
incorporating metadata errata harder.  If we have such thing as Metadata 
erratum type, and if such erratum gets verified, RFC Editor will be 
capable of noticing and acting quickly (I doubt RFC Editor pays much 
attention to Editorial errata when submitted/verified).

>
>> Second, the "Section" field at
>> <http://www.rfc-editor.org/errata_report.php>  implies that only
>> numerical sections will contain something an erratum can be reported
>> against (overlooking the GLOBAL option).  However, Appendices, Abstract,
>> Index, Author Info, different Notes exist, that aren't covered here.
> I was able to type "Appendix A" just now into that section without difficulty.  The preview page shows "Section Appendix A says:", but that hardly seems a difficulty.

This limitation makes submitters find the way to put what they want in 
this field whose entity, I think, should be limited to digits and ".".  
This issue is probably of aesthetic importance.

>
>> Third, Original text and Corrected text fields imply that only
>> before-and-after errata may be submitted.  However, there might be
>> errata like Erratum # 6
>> (http://www.rfc-editor.org/errata_search.php?eid=6), with an only Report
>> text field.  I understand this feature was present in previous versions
>> of errata mechanism but removed from the current.
> I don't understand the problem here.  That report seems pretty clear to me.

There used to be a "Text Report" option for submitting errata.  This 
implied filling in the only field, not "Current Text" and "Corrected 
Text".  Now it is unavailable, and this makes submitters write smth like 
this:

"Scope: GLOBAL"; "Current text: N/A"; "Corrected text: <what they want 
to say>"

and this results in a report saying that

"Throughout the document, when it says N/A, it should say <what 
submitter wanted to say>".

If the one-field errata existed, this would be:

"Scope: <not filled in>"; "Report Text: <what they want to say>"

and the erratum will look like:

"[For this document] the following erratum was reported: <what submitter 
wanted to say>".

(The scope-indicating field when submitting such errata should be made 
optional, BTW.)

>
>> Also, several issues not related to submission mechanism.
>>
>> 1) Specific mailing lists devoted to discussion of errata against RFCs
>> from different areas.  I've proposed this on rfc-interest list; see rationale at
>> <http://www.rfc-editor.org/pipermail/rfc-interest/2011-
>> August/002672.html>.;
> Typically a working group discusses an erratum when it is raised, and then it sits in limbo until a document update occurs.  Isn't the right place for discussion about a particular one the mailing list of that working group or, if it's disbanded, the main IETF list?

Well, there are AD-sponsored Individual Submissions, which have no 
associated WG, and IAB, IRTF and Independent docs which IETF community 
might have a limited interest in.  If we had the lists where errata for:

1. IETF Stream:
a. Apps Area;
b. Int Area;
c. Gen Area;
d. Ops Area;
e. RAI Area;
f. Rtg area;
g. Sec Area;
h. Tsv-Area
i. Legacy (published bu concluded areas);
j. Individual Submissions;
2. IAB Stream;
3. IRTF Stream;
4. Independent Submissions

folks who don't have ability or willing to join corresponding groups' 
lists will be capable of joining these lists.

Discussing errata on IETF Discussion list will increase our traffic and 
will soon bore many people who aren't particularly interested in a 
variety of topics errata are submitted on.

>
>> 3) Verified technical errata may be incorporated in the references. Eg.
>> 4 technical errata were reported against RFC 793 and verified; so the
>> reference may be:
>>
>> Postel, J., "Transmission Control Protocol", STD 7, RFC 793,
>> September 1981.  Ammended by RFC Errata Reports 573, 1562, 1564, 1572.
> I don't think verified errata have any force or effect until the document is actually updated, so this really just becomes clutter in the references.  Moreover, if I'm implementing some RFC that references another which itself has errata, I will want to know about all of them, not the ones that were present and verified at the time of publication.

Well, a reasonable argument.  At Appendix A of 
draft-rfc-editor-errata-process-02 
(http://tools.ietf.org/html/draft-rfc-editor-errata-process-02#appendix-A) 
I found a proposal from Brian Carpenter to point to errata list in the 
RFC itself, probably in Status of this Memo section.  So this may be a 
solution.

Mykyta

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


From msk@cloudmark.com  Tue Aug 30 22:08:04 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 780D821F8C30 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 22:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.028
X-Spam-Level: 
X-Spam-Status: No, score=-103.028 tagged_above=-999 required=5 tests=[AWL=-0.429, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F4NtApNmtrmB for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 22:08:03 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id ED45621F8C29 for <ietf@ietf.org>; Tue, 30 Aug 2011 22:08:03 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Tue, 30 Aug 2011 22:09:32 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 30 Aug 2011 22:09:32 -0700
Subject: RE: Limitations in RFC Errata mechanism
Thread-Topic: Limitations in RFC Errata mechanism
Thread-Index: AcxnkybO1UAx3PDXT7qe5tYy7TpyUgACDUfQ
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9B5@EXCH-C2.corp.cloudmark.com>
References: <4E5CFF6A.30004@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9A2@EXCH-C2.corp.cloudmark.com> <4E5DB2FF.9050402@gmail.com>
In-Reply-To: <4E5DB2FF.9050402@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 05:08:04 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of M=
ykyta Yevstifeyev
> Sent: Tuesday, August 30, 2011 9:05 PM
> To: ietf@ietf.org
> Subject: Re: Limitations in RFC Errata mechanism
>=20
> > I think given the current mechanism I would just submit such things
> > under "Editorial".
>=20
> This is an option; but doing so makes work of RFC Editor when
> incorporating metadata errata harder.  If we have such thing as Metadata
> erratum type, and if such erratum gets verified, RFC Editor will be
> capable of noticing and acting quickly (I doubt RFC Editor pays much
> attention to Editorial errata when submitted/verified).

I'm sure the RFC Editor appreciates people in the IETF trying to make their=
 work easier, but since so far they haven't complained about this in partic=
ular, I'm not sure it's something that actually needs fixing.

> > I was able to type "Appendix A" just now into that section without
> > difficulty.  The preview page shows "Section Appendix A says:", but
> > that hardly seems a difficulty.
>=20
> This limitation makes submitters find the way to put what they want in
> this field whose entity, I think, should be limited to digits and ".".
> This issue is probably of aesthetic importance.

As a submitter, I didn't find typing "Appendix A" into that box and decodin=
g the output to be at all inconvenient.  It may not be perfect, but it's no=
t terribly broken either.

> > Typically a working group discusses an erratum when it is raised, and
> > then it sits in limbo until a document update occurs.  Isn't the right
> > place for discussion about a particular one the mailing list of that
> > working group or, if it's disbanded, the main IETF list?
>=20
> Well, there are AD-sponsored Individual Submissions, which have no
> associated WG, and IAB, IRTF and Independent docs which IETF community
> might have a limited interest in.  If we had the lists where errata
> for:
> [...]

I still don't see this as evidence that we need to have a forum specificall=
y for discussing errata.  I would have to subscribe to that list just in ca=
se there's ever any erratum opened for an RFC that interests me, and deal w=
ith the (possibly huge) amount of traffic that is not of interest.  It seem=
s to me that ietf@ietf.org is just fine for this purpose, and most of us al=
ready are on that one.

I also haven't seen any demand prior to this for a special forum where erra=
ta are discussed, separate from the list(s) we already have.

> Discussing errata on IETF Discussion list will increase our traffic and
> will soon bore many people who aren't particularly interested in a
> variety of topics errata are submitted on.

As far as I can tell, that's where this happens now, and I don't see it bei=
ng much of a burden.

I could be wrong, but I don't see much evidence that any of this stuff is b=
roken enough to warrant a bunch of form changes, new mailing lists, or othe=
r new infrastructure.  If it ain't broke, don't fix it.

-MSK

From john-ietf@jck.com  Tue Aug 30 23:30:26 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C38021F8B86; Tue, 30 Aug 2011 23:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=-0.290, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DeokRm9SszLv; Tue, 30 Aug 2011 23:30:25 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA9A21F8B73; Tue, 30 Aug 2011 23:30:25 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QyeL0-00015p-WD; Wed, 31 Aug 2011 02:31:51 -0400
Date: Wed, 31 Aug 2011 02:31:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Fred Baker <fred@cisco.com>, Keith Moore <moore@network-heretics.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
Message-ID: <65AB1B585CF6B912684ECB00@PST.JCK.COM>
In-Reply-To: <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@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
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 06:30:26 -0000

--On Tuesday, August 30, 2011 14:51 -0700 Fred Baker
<fred@cisco.com> wrote:

>> What's also not fair game is to "raise the bar" - to expect
>> the document at DS to meet more stringent criteria than it
>> was required to meet at the time of PS approval.
> 
> Hmmm, the "demonstrated interoperability" requirement of DS/IS
> is in fact a raising of the bar,and one that has served us
> well. We don't (although IMHO we should) require even an
> implementation to go to PS. 

I know it is controversial, but there is at least one other area
in which we should be raising the bar for DS/IS by dropping the
bar for Proposed.  If we really want to get PS specs out quickly
while the percentage of people who easily write very high
quality technical English in the IETF continues to go down, we
need to stop the behavior of various IESG members simulating
technical editors or translators to "fix" PS text (or insisting
that the author or WG do so, which, IMO, is less bad but still
often a problem).  Doing that will get documents out faster,
perhaps even a lot faster in some cases, but will inevitably
result in PS documents that need significant editorial work
before being approved at DS.  

I think that would actually be a good thing.  I think that
stuffing explicit placeholders to the effect of "this needs to
be rewritten to be completely clear to folks who haven't
participated in the WG" into PS documents would be a fine idea
-- it would get those documents finished and out while making
their preliminary nature very clear.   But it implies a higher
editorial quality standard --a higher bar-- for DS/IS than for
PS.

    john




From jari.arkko@piuha.net  Tue Aug 30 23:34:39 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D828821F8C36; Tue, 30 Aug 2011 23:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1d1p1lincQQR; Tue, 30 Aug 2011 23:34:39 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id D4D9521F8C32; Tue, 30 Aug 2011 23:34:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E4A9B2D223; Wed, 31 Aug 2011 09:36:07 +0300 (EEST)
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 WfcCa+c+s0Hi; Wed, 31 Aug 2011 09:36:06 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 973322CE66; Wed, 31 Aug 2011 09:36:06 +0300 (EEST)
Message-ID: <4E5DD655.1000809@piuha.net>
Date: Wed, 31 Aug 2011 09:36:05 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com>
In-Reply-To: <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 06:34:40 -0000

Keith, thank you for the feedback. Some responses inline:

> 1. Fix the broken IESG voting system before you try to establish more decision criteria.

I do agree with your general thinking here. The way that you describe the different positions is what I personally try to achieve in my IESG reviews.

But I think you are overemphasizing the role of the vote designations. Again, I try to do this already, though maybe not always succeeding. In general, if the Area Directors are not doing their job of stopping bad stuff and moving good stuff along, they don't need a new voting system, they need to grow a spine.

Elaborating a bit more about this:

We have plenty of cases where a DISCUSS has been left standing, and today that acts as your "NO" vote. (Obviously, in many cases this was an error, or lack of effort. I'm quilty of this for sure, even right now I have a queue of DISCUSSes and their proposed resolutions that I need to go check.) But I think a DISCUSS should stand, if there is a serious issue and it is not rectified.

There are corner cases where a single AD has an opinion that is not shared by the rest of the community. For those cases we have an override procedure. This has been never been invoked, but that's probably because it gets pretty ugly way before that -- there are often heated discussions between ADs about discusses.

We have the ABSTAIN vote, which some ADs use to vote "NO", often together with other ADs who feel the same. There's never been a case where this would have blocked a document from proceeding, as we've never collected the necessary 1/3 number of ADs to vote ABSTAIN for any single document. My conclusion is that ABSTAIN stands for NO-OBJECTION in practical terms. I don't recommend its use...

> 2. Don't overconstrain the use of DISCUSS.  In particular, don't ever create a situation where a reviewer can't cite a problem with a document, regardless of whether that problem has previously been enumerated.

I agree, and that's why the guidelines I posted are just that -- guidelines. They are not binding rules, they leave room for a judgment call.

> 3. I take serious issue with the statement in the draft that IESG reviews are "reviews of last resort" and the implication that WG reviews are sufficient.  In numerous situations this has not been the case.

Of course. But I don't see a conflict between a "review of last resort" and having the last resort find issues. I wish we'd find less issues, but at least I still view the IESG as the final check, that should catch issues if others have not. Its not a "last resort" in the sense that it would not be invoked; we do review all documents very carefully. Its a last resort only in the sense that there is an expectation that previous stages should have produced a quality result without issues.

Jari


From eburger@standardstrack.com  Wed Aug 31 00:12:30 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB9DC21F8C1D for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.22
X-Spam-Level: 
X-Spam-Status: No, score=-102.22 tagged_above=-999 required=5 tests=[AWL=-0.221, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q0C7OTecuCHd for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:12:30 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 485E121F8C06 for <ietf@ietf.org>; Wed, 31 Aug 2011 00:12:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=wO3D1PLToQuoWXYhov7e/CA5F5KviG+n8tio3gjemfzC8BMccRyjORTENoewwnQx2b+QdjjixMufe4cI8j70ZjjxkhTMf8Sp8pT3KdeYD32JiW7rPQjUBBSXhpG8b9nR;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Qyezn-0002NF-Da for ietf@ietf.org; Wed, 31 Aug 2011 00:13:59 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-78--687296716; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: Discuss criteria for documents that advance on the standards track
Date: Wed, 31 Aug 2011 03:13:55 -0400
In-Reply-To: <65AB1B585CF6B912684ECB00@PST.JCK.COM>
To: IETF Discussion <ietf@ietf.org>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM>
Message-Id: <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 07:12:31 -0000

--Apple-Mail-78--687296716
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Would having professional editors make a difference here?

On Aug 31, 2011, at 2:31 AM, John C Klensin wrote:

> 
> 
> --On Tuesday, August 30, 2011 14:51 -0700 Fred Baker
> <fred@cisco.com> wrote:
> 
>>> What's also not fair game is to "raise the bar" - to expect
>>> the document at DS to meet more stringent criteria than it
>>> was required to meet at the time of PS approval.
>> 
>> Hmmm, the "demonstrated interoperability" requirement of DS/IS
>> is in fact a raising of the bar,and one that has served us
>> well. We don't (although IMHO we should) require even an
>> implementation to go to PS. 
> 
> I know it is controversial, but there is at least one other area
> in which we should be raising the bar for DS/IS by dropping the
> bar for Proposed.  If we really want to get PS specs out quickly
> while the percentage of people who easily write very high
> quality technical English in the IETF continues to go down, we
> need to stop the behavior of various IESG members simulating
> technical editors or translators to "fix" PS text (or insisting
> that the author or WG do so, which, IMO, is less bad but still
> often a problem).  Doing that will get documents out faster,
> perhaps even a lot faster in some cases, but will inevitably
> result in PS documents that need significant editorial work
> before being approved at DS.  
> 
> I think that would actually be a good thing.  I think that
> stuffing explicit placeholders to the effect of "this needs to
> be rewritten to be completely clear to folks who haven't
> participated in the WG" into PS documents would be a fine idea
> -- it would get those documents finished and out while making
> their preliminary nature very clear.   But it implies a higher
> editorial quality standard --a higher bar-- for DS/IS than for
> PS.
> 
>    john
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-78--687296716
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzEwNzEzNTZaMCMGCSqGSIb3DQEJ
BDEWBBTMovML/iMMq4ZEnwWAadLKSZJcGTCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAC2Nrr5Pi75bUY4m4avUJ1wy2oeZAM4V/a4fJI9G5mGlkpZS
8SPZR05KOAREqtaWUrizewr9Nt2OreuZASyksOAGFosXl+o4GYyBoGlybJP1VwAv9Un3XIECQ2Y+
DKSgrWI20Zz1bOaDJZaaCQqLyIRjf5AdVd34OSa7zapiLwvviQ1ij8hHyeu3BGnxbRQGiFoh+wd9
Tjd1Lisa3o0NXWinaWRLuEIMC+zuFlmrg6CcQ2WhEEd6BmzPk7hQDkAtJeBZjwD2Ohugs5+QioZf
dC40gDeNQb3+nBlS5GIE8hKAO8UQ0c4ySLinS9Cg+c4AXP+fTXDWfD7wHvRqE48dCUoAAAAAAAA=

--Apple-Mail-78--687296716--

From eburger@standardstrack.com  Wed Aug 31 00:35:18 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0C7321F8B63 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-txDVjhKYk0 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:35:18 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0E19C21F8B0E for <ietf@ietf.org>; Wed, 31 Aug 2011 00:35:18 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=NPfUL8o2GazupQS3KUbdFKB6XtuZD+Swe37ChDb1imikETbgGrAJmx3DzGgaDtn2/q/MhwSsI/g+pdAOY7Nh6Gei1OO/jWMX27c5Bw92lMMsnd1s8200Il05vro9Ngol;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyfLq-0006YW-N7; Wed, 31 Aug 2011 00:36:47 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-85--685929244; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4E5D3546.3020109@winserver.com>
Date: Wed, 31 Aug 2011 03:36:43 -0400
Message-Id: <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D3546.3020109@winserver.com>
To: hector <gmail.sant9442@winserver.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 07:35:19 -0000

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

My interpretation of what you wrote is that in your mind there is =
absolutely no difference between a SHOULD and a MAY.  They are both =
optional, and you implement whatever you have time to implement, with =
SHOULD's prioritized higher than MAY's.

Even if that is not what you mean, it is what many implementors do.

I would offer this highlights the problem with today's SHOULD.  Some =
think SHOULD means something is OK to implement, but life does not end =
if you do not do it. Others think SHOULD means something HAS to be =
implemented, unless the environment indicates the protocol will not work =
in some corner case.


On Aug 30, 2011, at 3:08 PM, hector wrote:

> When I approach a protocol to implement, the first thing I typically =
do is extract and develop the basic wiring of the protocol, the minimum =
requirements.  Make sure the basic framework is correct 100%, then I =
look for the SHOULDs and also MAYS which are the easiest to add.  I look =
at the SHOULD by order of importance and also complexity.  How much =
"CANDY" is it?  It is a security feature?  What are the other =
implementation requirements, tools, APIs, etc.  Generally I want to get =
security out the way.  Its like SMTP AUTH - its not required but anyone =
cleaning up and rewriting an SMTP spec today, might include the AUTH =
extension as a SHOULD. And implementators are keen to the importance of =
it.  But nothing won't break down if you don't, less functionality but =
the basic structure is still there.
>=20
> Its the same approach used for all the protocols we support. Start =
with the basics and then add on  as necessary.
>=20
> Eric Burger wrote:
>> What is the difference in this case between SHOULD or MAY?
>> On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:
>>> On 8/29/11 9:44 PM, Eric Burger wrote:
>>>> Yes, and...
>>>>=20
>>>> I would offer that for most cases, If Y then MUST X or If Z then =
MUST NOT X *are* what people usually mean when they say SHOULD.  In the =
spirit of Say What You Mean, a bare SHOULD at the very least raise an =
ID-nit, suggesting to the author to turn the statement into the if Y =
then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
>>>> 	SHOULD send a 1 UNLESS you receive a 0
>>>> really means
>>>> 	UNLESS you receive a 0, one MUST send a 1.
>>>>=20
>>>> My vision of the UNLESS clause is not necessarily a protocol state, =
but an environment state.  These are things that I can see fit the =
SHOULD/UNLESS form:
>>>> 	SHOULD send a 1 UNLESS you are in a walled garden
>>>> 	SHOULD flip bit 27 UNLESS you have a disk
>>>> 	SHOULD NOT explode UNLESS you are a bomb
>>>> are all reasonable SHOULD-level statements.
>>>>=20
>>>> I would offer that ANY construction of SHOULD without an UNLESS is =
a MAY.
>>>=20
>>> Eric. Put down the axe and step away from the whetstone. Here, I'll =
give you some text from RFC 3265 to mull.
>>>=20
>>>=20
>>>  deactivated: The subscription has been terminated, but the =
subscriber
>>>     SHOULD retry immediately with a new subscription.  One primary =
use
>>>     of such a status code is to allow migration of subscriptions
>>>     between nodes.
>>>=20
>>>=20
>>> Let's examine this use of "SHOULD." If the subscriber doesn't =
re-subscribe, is it an interop issue? No.
>>>=20
>>> Is it in the interest of the implementation to re-subscribe? Yes. At =
least, under most circumstances. Otherwise, they won't get the state =
change notifications they want.
>>>=20
>>> Are there cases in which it makes sense for the subscriber _not_ to =
re-subscribe? Yes, I'm sure there are. It's conceivable that the client =
happens to be shutting down but hasn't gotten around to terminating this =
particular subscription yet. But any such exceptions are highly =
implementation-dependent. Listing them would be useless noise to the =
reader, and senseless text creation for the author.
>>>=20
>>> Does "SHOULD" get abused by some authors in some documents? Of =
course it does. But your crusade to throw out a useful tool just because =
it has been misused on occasion is an extreme over-reaction. I like this =
tool. I use this tool. If you see people misusing it, slap them.
>>>=20
>>> But don't ban the tool.
>>>=20
>>> /a
>> =
------------------------------------------------------------------------
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-85--685929244
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzEwNzM2NDNaMCMGCSqGSIb3DQEJ
BDEWBBQVurR9fTB0bTmd0Nv9L6YP2CNj2DCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAKJzVigmCAybu/CWqDJ5L4NR5YydgS5yvJgdJ+cgf4NvuWor
/4UjFUz2oGwbT+snU4FhAV7KLG7XhZ4+aqjzmwYg3+fbJE2fxA122OAVSrvI7R4Btgdt1wafQ0Mq
BtV1JPyyeTFkCj6y94TwgNlZr4lX/SfalP6zfc9458R1ceFxoYreWYlyc06ZiBslMBcDLlyF1OQA
zwyy6BCdjYhf5DKUXHrcOGVxebsqURAH6SOt+JOKu35OYLxR4jhWZFbcOoKNAv1fw3e67nrb4bt6
aj0GGSorgL6MfspK5vVqgPuezdi6yPxMvoZUuIvGycXSvtRQEDmwmBpFFzoWP1Gd040AAAAAAAA=

--Apple-Mail-85--685929244--

From eburger@standardstrack.com  Wed Aug 31 00:40:43 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 160E521F8C59 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Jyh5MgiGcae for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:40:42 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9694321F8C57 for <ietf@ietf.org>; Wed, 31 Aug 2011 00:40:37 -0700 (PDT)
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:X-Source:X-Source-Args:X-Source-Dir; b=B5nwvSYOCqFQ37qktGAgt0TxGe0nmggsjFMnWOjb/spKebPlPFIhHiiIhuwfVAU/nEWEVHCmg4jIFh+hfpRt5k9w0NAHdWRMu3zWiSvrHHJ0PgqY/rcwww33lmBG/MvK;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyfR0-0001zA-4F; Wed, 31 Aug 2011 00:42:07 -0700
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-86--685611979; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4E5D36B4.7000805@nostrum.com>
Date: Wed, 31 Aug 2011 03:42:00 -0400
Message-Id: <DC6D2BD8-972B-4D16-8FA1-67FC326691A9@standardstrack.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D36B4.7000805@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 07:40:43 -0000

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

Interesting example.  I like it.  I agree that when to retry is not at =
all a protocol issue.  That probably is why we are in fuzzy land, and =
this highlights why SHOULD is bad.  The availability of SHOULD drew the =
author of the mentioned RFC to mix a user interface / user experience =
issue with a protocol issue.

Saying a client SHOULD retry immediately, to migrate subscriptions, is =
an implementation detail and has absolutely NOTHING to do with the =
protocol.

It would be OK to have a NOTE in the protocol RFC discussing that =
"deactivated" is an opportunity to migrate the subscription.  It would =
be OK to have an Informational implementor's guide that notes that it =
would be good for clients to leverage the "deactivated" state to quickly =
migrate a subscription.  However, there is NOTHING in the protocol to =
say SHOULD.

On Aug 30, 2011, at 3:15 PM, Adam Roach wrote:

> In this case, unless the implementation has a good reason, failing to =
re-subscribe will result in behavior that the user perceives as broken. =
I don't think that's really "MAY" territory.
>=20
> /a
>=20
>=20
> On 8/30/11 1:57 PM, Eric Burger wrote:
>> What is the difference in this case between SHOULD or MAY?
>>=20
>> On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:
>>=20
>>> On 8/29/11 9:44 PM, Eric Burger wrote:
>>>> Yes, and...
>>>>=20
>>>> I would offer that for most cases, If Y then MUST X or If Z then =
MUST NOT X *are* what people usually mean when they say SHOULD.  In the =
spirit of Say What You Mean, a bare SHOULD at the very least raise an =
ID-nit, suggesting to the author to turn the statement into the if Y =
then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
>>>> 	SHOULD send a 1 UNLESS you receive a 0
>>>> really means
>>>> 	UNLESS you receive a 0, one MUST send a 1.
>>>>=20
>>>> My vision of the UNLESS clause is not necessarily a protocol state, =
but an environment state.  These are things that I can see fit the =
SHOULD/UNLESS form:
>>>> 	SHOULD send a 1 UNLESS you are in a walled garden
>>>> 	SHOULD flip bit 27 UNLESS you have a disk
>>>> 	SHOULD NOT explode UNLESS you are a bomb
>>>> are all reasonable SHOULD-level statements.
>>>>=20
>>>> I would offer that ANY construction of SHOULD without an UNLESS is =
a MAY.
>>>=20
>>> Eric. Put down the axe and step away from the whetstone. Here, I'll =
give you some text from RFC 3265 to mull.
>>>=20
>>>=20
>>>   deactivated: The subscription has been terminated, but the =
subscriber
>>>      SHOULD retry immediately with a new subscription.  One primary =
use
>>>      of such a status code is to allow migration of subscriptions
>>>      between nodes.
>>>=20
>>>=20
>>> Let's examine this use of "SHOULD." If the subscriber doesn't =
re-subscribe, is it an interop issue? No.
>>>=20
>>> Is it in the interest of the implementation to re-subscribe? Yes. At =
least, under most circumstances. Otherwise, they won't get the state =
change notifications they want.
>>>=20
>>> Are there cases in which it makes sense for the subscriber _not_ to =
re-subscribe? Yes, I'm sure there are. It's conceivable that the client =
happens to be shutting down but hasn't gotten around to terminating this =
particular subscription yet. But any such exceptions are highly =
implementation-dependent. Listing them would be useless noise to the =
reader, and senseless text creation for the author.
>>>=20
>>> Does "SHOULD" get abused by some authors in some documents? Of =
course it does. But your crusade to throw out a useful tool just because =
it has been misused on occasion is an extreme over-reaction. I like this =
tool. I use this tool. If you see people misusing it, slap them.
>>>=20
>>> But don't ban the tool.
>>>=20
>>> /a
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-86--685611979
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA4MzEwNzQyMDFaMCMGCSqGSIb3DQEJ
BDEWBBSJJweGslB75KUhQq3WytAhY21wYDCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAImgLOqwtboUc7+vBGAzum1dRSfR1FIaO8NXEQaAgF3yTMNH
M8T1yP9eNoLiZTqrocT08x8W1bUcRyX7+hItI20Qmxqvga7hvyDAV8IWy1J9m47simHQoPk8m/0D
xmq+S4slYzxCM5Phq7056dVJtue4FqNfOLyAeAY5IDa/I555gmqok6kDaY3Djtl42rAdbCO9icXn
XNq0zcu+QbeqkPthxkwQ8i341HXThhjM5ox0lCSzG6Clm764mxYSo8FEE1VlmnImlYUY+L+49IlO
UfAxxyUvHWIK30I+JAhIjE/sDIafb0l4WbbY0FAkwKRJLnmpFLtnAS09yUckU4+CmkMAAAAAAAA=

--Apple-Mail-86--685611979--

From julian.reschke@gmx.de  Wed Aug 31 00:41:17 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79CCC21F8828 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.122
X-Spam-Level: 
X-Spam-Status: No, score=-104.122 tagged_above=-999 required=5 tests=[AWL=-1.523, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bmUyugPtiNNH for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:41:17 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 7320C21F87E2 for <ietf@ietf.org>; Wed, 31 Aug 2011 00:41:16 -0700 (PDT)
Received: (qmail invoked by alias); 31 Aug 2011 07:42:43 -0000
Received: from p508FA8FA.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.168.250] by mail.gmx.net (mp057) with SMTP; 31 Aug 2011 09:42:43 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/t59lvrjDty1i3uvB3ME0vPlwYqSRfxmApp2OXKQ bApHed4QIRoOZH
Message-ID: <4E5DE5E8.9070808@gmx.de>
Date: Wed, 31 Aug 2011 09:42:32 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Limitations in RFC Errata mechanism
References: <4E5CFF6A.30004@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9A2@EXCH-C2.corp.cloudmark.com> <4E5DB2FF.9050402@gmail.com>
In-Reply-To: <4E5DB2FF.9050402@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 07:41:17 -0000

On 2011-08-31 06:05, Mykyta Yevstifeyev wrote:
> ...
> Well, a reasonable argument. At Appendix A of
> draft-rfc-editor-errata-process-02
> (http://tools.ietf.org/html/draft-rfc-editor-errata-process-02#appendix-A)
> I found a proposal from Brian Carpenter to point to errata list in the
> RFC itself, probably in Status of this Memo section. So this may be a
> solution.
> ...

"Status of this Memo" already has a link to 
http://www.rfc-editor.org/info/rfcNNNN.

Best regards, Julian

From evnikita2@gmail.com  Wed Aug 31 00:55:04 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA9821F8BA7 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level: 
X-Spam-Status: No, score=-3.471 tagged_above=-999 required=5 tests=[AWL=0.128,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id taX6IZHSKpet for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:55:03 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4B47E21F8B9D for <ietf@ietf.org>; Wed, 31 Aug 2011 00:55:03 -0700 (PDT)
Received: by bkar4 with SMTP id r4so666975bka.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 00:56:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=TVxzv6IqehAMfRgnk2FopVA/8N00uBAenIOSCdJOK6I=; b=GptZJaIb5ym3bnC/o304xanNXjhGgRKuoxWjR2XqSsDLOtySndWt7whuV30XRtSgIw hF9IuiwbJf85Zg6uHyvk3pjx6JKNQDgf20c8XXnygjk/qdD8YdfmLSbu37V34Jsfn6Zx 3j9gNungYkis/IRhxe5k1AbTLebHbJLBv6E70=
Received: by 10.204.133.3 with SMTP id d3mr63058bkt.314.1314777391968; Wed, 31 Aug 2011 00:56:31 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id f9sm252038bkt.3.2011.08.31.00.56.30 (version=SSLv3 cipher=OTHER); Wed, 31 Aug 2011 00:56:31 -0700 (PDT)
Message-ID: <4E5DE94E.3070807@gmail.com>
Date: Wed, 31 Aug 2011 10:57:02 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Limitations in RFC Errata mechanism
References: <4E5CFF6A.30004@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9A2@EXCH-C2.corp.cloudmark.com> <4E5DB2FF.9050402@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9B5@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF9B5@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 07:55:04 -0000

31.08.2011 8:09, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mykyta Yevstifeyev
>> Sent: Tuesday, August 30, 2011 9:05 PM
>> To: ietf@ietf.org
>> Subject: Re: Limitations in RFC Errata mechanism
>>
>>> I think given the current mechanism I would just submit such things
>>> under "Editorial".
>> This is an option; but doing so makes work of RFC Editor when
>> incorporating metadata errata harder.  If we have such thing as Metadata
>> erratum type, and if such erratum gets verified, RFC Editor will be
>> capable of noticing and acting quickly (I doubt RFC Editor pays much
>> attention to Editorial errata when submitted/verified).
> I'm sure the RFC Editor appreciates people in the IETF trying to make their work easier, but since so far they haven't complained about this in particular, I'm not sure it's something that actually needs fixing.

Usually, when metadata erratum is reported, and some AD verifies it, 
this AD is to report this change to RFC Editor manually, despite the 
fact the verification notification is cc'ed to 
rfc-editor@rfc-editor.org; also note that processing such errata may 
take additional time because the whole IESG may be necessary to be 
consulted, and so on.  At least one step of this process may be 
simplified simply.

>
>>> I was able to type "Appendix A" just now into that section without
>>> difficulty.  The preview page shows "Section Appendix A says:", but
>>> that hardly seems a difficulty.
>> This limitation makes submitters find the way to put what they want in
>> this field whose entity, I think, should be limited to digits and ".".
>> This issue is probably of aesthetic importance.
> As a submitter, I didn't find typing "Appendix A" into that box and decoding the output to be at all inconvenient.  It may not be perfect, but it's not terribly broken either.

So this, as already mentioned, is an aesthetic question.  However, 
"Section TOC" or "Section Appendix A" don't look nice.

>
>>> Typically a working group discusses an erratum when it is raised, and
>>> then it sits in limbo until a document update occurs.  Isn't the right
>>> place for discussion about a particular one the mailing list of that
>>> working group or, if it's disbanded, the main IETF list?
>> Well, there are AD-sponsored Individual Submissions, which have no
>> associated WG, and IAB, IRTF and Independent docs which IETF community
>> might have a limited interest in.  If we had the lists where errata
>> for:
>> [...]
> I still don't see this as evidence that we need to have a forum specifically for discussing errata.  I would have to subscribe to that list just in case there's ever any erratum opened for an RFC that interests me, and deal with the (possibly huge) amount of traffic that is not of interest.  It seems to me that ietf@ietf.org is just fine for this purpose, and most of us already are on that one.

I didn't see, for instance, any errata report against apps-related RFCs 
coming to apps-discuss list.  This would only happen if such RFC was 
produced is appsawg WG.  I didn't notice errata reports on genarea RFCs 
coming on IETF Discussion list, which would be logical.  There may be 
more examples.

Else, errata system should be configured to copy all notifications to 
specific area lists, which exists in all areas, which it currently isn't.

>
> I also haven't seen any demand prior to this for a special forum where errata are discussed, separate from the list(s) we already have.
>
>> Discussing errata on IETF Discussion list will increase our traffic and
>> will soon bore many people who aren't particularly interested in a
>> variety of topics errata are submitted on.
> As far as I can tell, that's where this happens now, and I don't see it being much of a burden.

Have we ever seen any errata coming on IETF Discussion?

Mykyta Yevstifeyev

>
> I could be wrong, but I don't see much evidence that any of this stuff is broken enough to warrant a bunch of form changes, new mailing lists, or other new infrastructure.  If it ain't broke, don't fix it.
>
> -MSK
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From evnikita2@gmail.com  Wed Aug 31 00:56:31 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0738421F8B3C for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.472
X-Spam-Level: 
X-Spam-Status: No, score=-3.472 tagged_above=-999 required=5 tests=[AWL=0.127,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 516ficMRCpu9 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 00:56:30 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3669221F8B2E for <ietf@ietf.org>; Wed, 31 Aug 2011 00:56:30 -0700 (PDT)
Received: by bkar4 with SMTP id r4so668594bka.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 00:57:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9/Yvxt57yBZWug5fB526hWYgu3ou0PwoBHjHNQuPPes=; b=lkL4o6EBSJ9G5yIaWZL59Ykd5QRXVS8QZKYvy4uMkMWC2AWigVItStf9JrfyCosVCR fxJwp+CLlGVHo3o3zO6Fc2b2KN8c7rpht8PoYSreds8VfaFS8dJBsrbKNi7vSWHr8WT3 S7VsLGoAajuV6HUfopCoRWVY6/HFyxN1z6fvo=
Received: by 10.204.129.194 with SMTP id p2mr73948bks.233.1314777477852; Wed, 31 Aug 2011 00:57:57 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id j17sm251285bks.13.2011.08.31.00.57.56 (version=SSLv3 cipher=OTHER); Wed, 31 Aug 2011 00:57:57 -0700 (PDT)
Message-ID: <4E5DE9A5.3000809@gmail.com>
Date: Wed, 31 Aug 2011 10:58:29 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Limitations in RFC Errata mechanism
References: <4E5CFF6A.30004@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9A2@EXCH-C2.corp.cloudmark.com> <4E5DB2FF.9050402@gmail.com> <4E5DE5E8.9070808@gmx.de>
In-Reply-To: <4E5DE5E8.9070808@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 07:56:31 -0000

31.08.2011 10:42, Julian Reschke wrote:
> On 2011-08-31 06:05, Mykyta Yevstifeyev wrote:
>> ...
>> Well, a reasonable argument. At Appendix A of
>> draft-rfc-editor-errata-process-02
>> (http://tools.ietf.org/html/draft-rfc-editor-errata-process-02#appendix-A) 
>>
>> I found a proposal from Brian Carpenter to point to errata list in the
>> RFC itself, probably in Status of this Memo section. So this may be a
>> solution.
>> ...
>
> "Status of this Memo" already has a link to 
> http://www.rfc-editor.org/info/rfcNNNN.

Yes, this slipped my mind.  Thanks.

Mykyta

>
> Best regards, Julian
>


From jari.arkko@piuha.net  Wed Aug 31 01:32:35 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA30B21F8B4E for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 01:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DdFT0fThRYF for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 01:32:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 39CD121F8B43 for <ietf@ietf.org>; Wed, 31 Aug 2011 01:32:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7FBD82D223; Wed, 31 Aug 2011 11:34:04 +0300 (EEST)
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 Ujcx4Mcem4wz; Wed, 31 Aug 2011 11:34:04 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id F3DC12CE66; Wed, 31 Aug 2011 11:34:03 +0300 (EEST)
Message-ID: <4E5DF1FB.2020306@piuha.net>
Date: Wed, 31 Aug 2011 11:34:03 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>, John C Klensin <klensin@jck.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
References: <4E5D45B1.50107@piuha.net>	<DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com>	<E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>	<65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com>
In-Reply-To: <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 08:32:36 -0000

Eric, John,

> Would having professional editors make a difference here?

>> I know it is controversial, but there is at least one other area
>> in which we should be raising the bar for DS/IS by dropping the
>> bar for Proposed.  If we really want to get PS specs out quickly
>> while the percentage of people who easily write very high
>> quality technical English in the IETF continues to go down, we
>> need to stop the behavior of various IESG members simulating
>> technical editors or translators to "fix" PS text (or insisting
>> that the author or WG do so, which, IMO, is less bad but still
>> often a problem).

I think the existing Discuss criteria already says very clearly that editorial comments cannot be blocking DISCUSSes.

I see a lot of language feedback from IESG and directorate reviews, but its rare to have them appear in the DISCUSSes. If they do, its inappropriate, you should push back. And I'm sure you will :-)

Besides, we pay the RFC Editor a large amount of money every year to do the editing. Documents need to be clear enough to be understood, but the RFC editor can handle most of the editorial problems.

(That being said, I've seen documents that were sent back because they really were not understandable. Obviously there is some bar under which you should not go, or the document cannot advance at all. This happens more in WG stages than in the IESG. But if you can't communicate your idea clearly then I think it should be up to you to hire co-workers/editors to  help clarify your idea... not the IETF's problem, IMHO.)

Jari


From mnot@mnot.net  Wed Aug 31 04:29:06 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63EF021F8ACA for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 04:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.316
X-Spam-Level: 
X-Spam-Status: No, score=-105.316 tagged_above=-999 required=5 tests=[AWL=-2.717, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsM6ylOqq1uS for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 04:29:05 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 90F6721F8AC9 for <ietf@ietf.org>; Wed, 31 Aug 2011 04:29:05 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.37.195]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 3867322E1EB; Wed, 31 Aug 2011 07:30:27 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <DC6D2BD8-972B-4D16-8FA1-67FC326691A9@standardstrack.com>
Date: Wed, 31 Aug 2011 21:30:24 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <97E27FC7-8201-4E89-9490-ECA087F1D177@mnot.net>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D36B4.7000805@nostrum.com> <DC6D2BD8-972B-4D16-8FA1-67FC326691A9@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 11:29:06 -0000

Exactly. I'm working my way through RFC2616bis, trying to distinguish =
between SHOULDs that actually have implications for interoperability and =
SHOULDs that are just there because the english word 'should' happened =
to make sense at the time. It's a huge pain.


On 31/08/2011, at 5:42 PM, Eric Burger wrote:

> Interesting example.  I like it.  I agree that when to retry is not at =
all a protocol issue.  That probably is why we are in fuzzy land, and =
this highlights why SHOULD is bad.  The availability of SHOULD drew the =
author of the mentioned RFC to mix a user interface / user experience =
issue with a protocol issue.
>=20
> Saying a client SHOULD retry immediately, to migrate subscriptions, is =
an implementation detail and has absolutely NOTHING to do with the =
protocol.
>=20
> It would be OK to have a NOTE in the protocol RFC discussing that =
"deactivated" is an opportunity to migrate the subscription.  It would =
be OK to have an Informational implementor's guide that notes that it =
would be good for clients to leverage the "deactivated" state to quickly =
migrate a subscription.  However, there is NOTHING in the protocol to =
say SHOULD.
>=20
> On Aug 30, 2011, at 3:15 PM, Adam Roach wrote:
>=20
>> In this case, unless the implementation has a good reason, failing to =
re-subscribe will result in behavior that the user perceives as broken. =
I don't think that's really "MAY" territory.
>>=20
>> /a
>>=20
>>=20
>> On 8/30/11 1:57 PM, Eric Burger wrote:
>>> What is the difference in this case between SHOULD or MAY?
>>>=20
>>> On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:
>>>=20
>>>> On 8/29/11 9:44 PM, Eric Burger wrote:
>>>>> Yes, and...
>>>>>=20
>>>>> I would offer that for most cases, If Y then MUST X or If Z then =
MUST NOT X *are* what people usually mean when they say SHOULD.  In the =
spirit of Say What You Mean, a bare SHOULD at the very least raise an =
ID-nit, suggesting to the author to turn the statement into the if Y =
then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
>>>>> 	SHOULD send a 1 UNLESS you receive a 0
>>>>> really means
>>>>> 	UNLESS you receive a 0, one MUST send a 1.
>>>>>=20
>>>>> My vision of the UNLESS clause is not necessarily a protocol =
state, but an environment state.  These are things that I can see fit =
the SHOULD/UNLESS form:
>>>>> 	SHOULD send a 1 UNLESS you are in a walled garden
>>>>> 	SHOULD flip bit 27 UNLESS you have a disk
>>>>> 	SHOULD NOT explode UNLESS you are a bomb
>>>>> are all reasonable SHOULD-level statements.
>>>>>=20
>>>>> I would offer that ANY construction of SHOULD without an UNLESS is =
a MAY.
>>>>=20
>>>> Eric. Put down the axe and step away from the whetstone. Here, I'll =
give you some text from RFC 3265 to mull.
>>>>=20
>>>>=20
>>>>  deactivated: The subscription has been terminated, but the =
subscriber
>>>>     SHOULD retry immediately with a new subscription.  One primary =
use
>>>>     of such a status code is to allow migration of subscriptions
>>>>     between nodes.
>>>>=20
>>>>=20
>>>> Let's examine this use of "SHOULD." If the subscriber doesn't =
re-subscribe, is it an interop issue? No.
>>>>=20
>>>> Is it in the interest of the implementation to re-subscribe? Yes. =
At least, under most circumstances. Otherwise, they won't get the state =
change notifications they want.
>>>>=20
>>>> Are there cases in which it makes sense for the subscriber _not_ to =
re-subscribe? Yes, I'm sure there are. It's conceivable that the client =
happens to be shutting down but hasn't gotten around to terminating this =
particular subscription yet. But any such exceptions are highly =
implementation-dependent. Listing them would be useless noise to the =
reader, and senseless text creation for the author.
>>>>=20
>>>> Does "SHOULD" get abused by some authors in some documents? Of =
course it does. But your crusade to throw out a useful tool just because =
it has been misused on occasion is an extreme over-reaction. I like this =
tool. I use this tool. If you see people misusing it, slap them.
>>>>=20
>>>> But don't ban the tool.
>>>>=20
>>>> /a
>>=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

--
Mark Nottingham   http://www.mnot.net/




From moore@network-heretics.com  Wed Aug 31 04:35:08 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 928B221F8B10; Wed, 31 Aug 2011 04:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.237
X-Spam-Level: 
X-Spam-Status: No, score=-2.237 tagged_above=-999 required=5 tests=[AWL=-1.219, BAYES_00=-2.599, FRT_PROFILE2=1.981, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgJpfY05aH+4; Wed, 31 Aug 2011 04:35:08 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id F26BA21F8B11; Wed, 31 Aug 2011 04:35:04 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8768E24687; Wed, 31 Aug 2011 07:36:34 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 31 Aug 2011 07:36:34 -0400
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=sp6ETSWIMrPb/wlzaFkTerNk4p4=; b=Zu D5i/Dau1uu6YncMib79Dm3nHlsZtGayhxNSqiuR7zL0g2npWQxYmVS0d0owRNGZ5 XZO2G2imq/WntXcf/BXb47v2UXDCOvIiRTVAID0E+T8FDBFnn9/ma6lUnp0Q+Gz9 QS3aYbJvcXqMbpksxNUNLi7jiKG4AvD/zYY3C+pMs=
X-Sasl-enc: Vv/2Q9KPGyZtX1mNmLhl0Dk31wvExNMeTwCG5FdXx5yb 1314790594
Received: from [10.59.1.20] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 0B8BE6A02CC; Wed, 31 Aug 2011 07:36:34 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <65AB1B585CF6B912684ECB00@PST.JCK.COM>
Date: Wed, 31 Aug 2011 07:36:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F11676D-450A-480E-B129-8E22130309FB@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: The IESG <iesg@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 11:35:08 -0000

On Aug 31, 2011, at 2:31 AM, John C Klensin wrote:

> --On Tuesday, August 30, 2011 14:51 -0700 Fred Baker
> <fred@cisco.com> wrote:
>=20
>>> What's also not fair game is to "raise the bar" - to expect
>>> the document at DS to meet more stringent criteria than it
>>> was required to meet at the time of PS approval.
>>=20
>> Hmmm, the "demonstrated interoperability" requirement of DS/IS
>> is in fact a raising of the bar,and one that has served us
>> well. We don't (although IMHO we should) require even an
>> implementation to go to PS.=20
>=20
> I know it is controversial, but there is at least one other area
> in which we should be raising the bar for DS/IS by dropping the
> bar for Proposed.  If we really want to get PS specs out quickly
> while the percentage of people who easily write very high
> quality technical English in the IETF continues to go down, we
> need to stop the behavior of various IESG members simulating
> technical editors or translators to "fix" PS text (or insisting
> that the author or WG do so, which, IMO, is less bad but still
> often a problem).  Doing that will get documents out faster,
> perhaps even a lot faster in some cases, but will inevitably
> result in PS documents that need significant editorial work
> before being approved at DS. =20

Given that people commonly implement and deploy Proposed Standards in =
products, sometimes even prior to their approval as Proposed Standards, =
I think this is a very bad idea.  I think it's likely to create =
interoperability problems between PS and DS versions of products, and =
sometimes between implementations of the same PS version.  For better or =
worse, the widespread desire to implement at PS (recommendations in 2026 =
notwithstanding) pretty much forces IETF to try to produce high quality =
prose at PS.

I agree that IESG should not generally be acting as technical editors, =
so maybe IETF needs to find some way to provide technical editors who =
are proficient in technical English before documents are reviewed by =
IESG.  Documents written by native English speakers would also benefit.  =
 Maybe the GEN-ART review could be expanded, or maybe the RFC Editor =
could assume some role here (awkward though that might be at first).

Keith




From moore@network-heretics.com  Wed Aug 31 04:49:51 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A31C21F877B; Wed, 31 Aug 2011 04:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.446
X-Spam-Level: 
X-Spam-Status: No, score=-3.446 tagged_above=-999 required=5 tests=[AWL=0.153,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2I1+RcsvyOV; Wed, 31 Aug 2011 04:49:50 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB9621F874F; Wed, 31 Aug 2011 04:49:50 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id ACA5120161; Wed, 31 Aug 2011 07:51:19 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 07:51:19 -0400
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=MhIH1sBZ9ig9nOv6vzDqVXRCqpo=; b=QW 0gogSxS3VEXYAh17gV1pD/WWQy6ZKy2O7DI86w9FvqGxyCQlwGcGy2Q4kEpbbzr9 eV7wNHcJ1x3LCcuoukaonjGr8uSNJVoDHQFZWdJ1wes/X8dzgf1J2XjYVSs+kgsY wx2EQ6eAoV5tfAJiGpUW+7vTCeUadNXEmbZHstk5M=
X-Sasl-enc: FwgDk015lv0sE/SY1M3+Hmtpul1hWRw6F3m+w19KGZuC 1314791479
Received: from [10.59.1.20] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 185956A0284; Wed, 31 Aug 2011 07:51:18 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5DD655.1000809@piuha.net>
Date: Wed, 31 Aug 2011 07:51:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <06D5CA5A-040D-40A6-BF19-80BAEFBA28CF@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <4E5DD655.1000809@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 11:49:51 -0000

On Aug 31, 2011, at 2:36 AM, Jari Arkko wrote:

> Keith, thank you for the feedback. Some responses inline:
>=20
>> 1. Fix the broken IESG voting system before you try to establish more =
decision criteria.
>=20
> I do agree with your general thinking here. The way that you describe =
the different positions is what I personally try to achieve in my IESG =
reviews.
>=20
> But I think you are overemphasizing the role of the vote designations. =
Again, I try to do this already, though maybe not always succeeding. In =
general, if the Area Directors are not doing their job of stopping bad =
stuff and moving good stuff along, they don't need a new voting system, =
they need to grow a spine.
>=20
> Elaborating a bit more about this:
>=20
> We have plenty of cases where a DISCUSS has been left standing, and =
today that acts as your "NO" vote. (Obviously, in many cases this was an =
error, or lack of effort. I'm quilty of this for sure, even right now I =
have a queue of DISCUSSes and their proposed resolutions that I need to =
go check.) But I think a DISCUSS should stand, if there is a serious =
issue and it is not rectified.
>=20
> There are corner cases where a single AD has an opinion that is not =
shared by the rest of the community. For those cases we have an override =
procedure. This has been never been invoked, but that's probably because =
it gets pretty ugly way before that -- there are often heated =
discussions between ADs about discusses.
>=20
> We have the ABSTAIN vote, which some ADs use to vote "NO", often =
together with other ADs who feel the same. There's never been a case =
where this would have blocked a document from proceeding, as we've never =
collected the necessary 1/3 number of ADs to vote ABSTAIN for any single =
document. My conclusion is that ABSTAIN stands for NO-OBJECTION in =
practical terms. I don't recommend its use...

The biggest problem with the current voting system (other than =
misleading labels, which do cause real problems of their own) is the =
presumption that the document should go forward no matter how few IESG =
members read the document.   So No Objection votes from ADs who didn't =
read the document count as Yes votes, but there's also a presumption in =
the rules (as well as pressure from other ADs who want to get documents =
off the agenda) to clear Discuss votes in favor of moving a document =
forward whether or not the identified issues have been adequately =
addressed.

(One thing that I didn't mention that also needs to be fixed if it's =
still the case is the presumption that the responsible AD votes Yes for =
the document.  I don't know what the tools do now, but this Yes vote =
used to be automatically filled-in.)

>> 2. Don't overconstrain the use of DISCUSS.  In particular, don't ever =
create a situation where a reviewer can't cite a problem with a =
document, regardless of whether that problem has previously been =
enumerated.
>=20
> I agree, and that's why the guidelines I posted are just that -- =
guidelines. They are not binding rules, they leave room for a judgment =
call.
>=20
>> 3. I take serious issue with the statement in the draft that IESG =
reviews are "reviews of last resort" and the implication that WG reviews =
are sufficient.  In numerous situations this has not been the case.
>=20
> Of course. But I don't see a conflict between a "review of last =
resort" and having the last resort find issues. I wish we'd find less =
issues, but at least I still view the IESG as the final check, that =
should catch issues if others have not. Its not a "last resort" in the =
sense that it would not be invoked; we do review all documents very =
carefully. Its a last resort only in the sense that there is an =
expectation that previous stages should have produced a quality result =
without issues.

That is not a valid expectation, in either theory or practice.  That's =
my point.  Arguably when a poor quality document gets to IESG, it's a =
failure on the part of the WG to do due diligence.  But the problem is =
actually deeper than that - it's partially structural (in that IETF =
partitions almost all work into narrowly focused WGs who don't represent =
a sufficiently broad spectrum of interests), and partially due to a =
failure to consistently apply good engineering principles across all of =
IETF.  =20

IESG's assuming that the WG has produced a quality result basically =
works to mask the other problems with IETF's way of doing work.   But =
even if WGs generally did produce high quality results without issues =
(which I don't think is the case now), IESG review should still not =
presume that they do.   There will always be some failures at the WG =
level, and the IESG's job is to try to catch those.

Keith


From moore@network-heretics.com  Wed Aug 31 05:00:34 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D871621F8ACC for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 05:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XuJ2yEcVJnNC for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 05:00:34 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 2356A21F8ABE for <ietf@ietf.org>; Wed, 31 Aug 2011 05:00:33 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id A4787204E9; Wed, 31 Aug 2011 08:02:03 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 08:02:03 -0400
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=inBIyRhCeohtmnjNAdlrzd1YEh4=; b=Pm NtIcVf5CUsawDYrmKHWrv2ygIjM99rvTRKyhqortJqQb2UpHYWMlMy4bpHAuxDZY UO+9AdOB5hps47CxOiQKNpvOgCFweeMsSbsy7GHKNShdjBEKva4ClxkULuRbSuN5 pKxj740ZHRbCJN+0LjDnV/XdUxJhXNDW5u6oOtTRI=
X-Sasl-enc: zFVJDHVECS9EQjY48yr7Ho/6lI9zEIQ1SG7r0qBh71jk 1314792123
Received: from [10.59.1.20] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 1CA766A0284; Wed, 31 Aug 2011 08:02:03 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5DF1FB.2020306@piuha.net>
Date: Wed, 31 Aug 2011 08:02:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.com>
References: <4E5D45B1.50107@piuha.net>	<DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com>	<E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com>	<65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <klensin@jck.com>, IETF Discussion <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 12:00:34 -0000

On Aug 31, 2011, at 4:34 AM, Jari Arkko wrote:

> Eric, John,
>=20
>> Would having professional editors make a difference here?
>=20
>>> I know it is controversial, but there is at least one other area
>>> in which we should be raising the bar for DS/IS by dropping the
>>> bar for Proposed.  If we really want to get PS specs out quickly
>>> while the percentage of people who easily write very high
>>> quality technical English in the IETF continues to go down, we
>>> need to stop the behavior of various IESG members simulating
>>> technical editors or translators to "fix" PS text (or insisting
>>> that the author or WG do so, which, IMO, is less bad but still
>>> often a problem).
>=20
> I think the existing Discuss criteria already says very clearly that =
editorial comments cannot be blocking DISCUSSes.

So nobody has the job of making sure that the documents are well-written =
in clear English?

> Besides, we pay the RFC Editor a large amount of money every year to =
do the editing. Documents need to be clear enough to be understood, but =
the RFC editor can handle most of the editorial problems.

If the document is edited for clarity after final review, that's really =
a botch in the process.  It means that the review doesn't apply to the =
version of the document being published.   Of course the RFC Editor's =
resources shouldn't be used for documents that aren't otherwise deemed =
worthy of publication, and you'd like to avoid the RFC Editor having to =
do multiple reviews, so I admit that this is tricky to solve.

> (That being said, I've seen documents that were sent back because they =
really were not understandable. Obviously there is some bar under which =
you should not go, or the document cannot advance at all. This happens =
more in WG stages than in the IESG. But if you can't communicate your =
idea clearly then I think it should be up to you to hire =
co-workers/editors to  help clarify your idea... not the IETF's problem, =
IMHO.)

If writing clear specifications isn't the IETF's problem, I'm not sure =
what is.

Keith


From sant9442@gmail.com  Wed Aug 31 05:28:37 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238F421F8AF1 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 05:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1lMR2-jItSl for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 05:28:36 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3402D21F8888 for <ietf@ietf.org>; Wed, 31 Aug 2011 05:28:36 -0700 (PDT)
Received: by yie12 with SMTP id 12so640830yie.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 05:30:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=dBfibzw1vPVJQiTmd7774Y5o2fbdzY0lhJne+eGtR04=; b=p6fkBzim0/h0JMLI5I20XhA+dD/a4Tyg/2y5jRvoLbJQqgly+m6q30RgjBcj8vMBbk ZFVnmpfjUzHLPEuLr1+uJ8iojeCGHSfIyTosU9XD3NCJdIMDxW1WqwkXPAANDwxooqtH uqxz5BztAqh5XTXmLjVkDAX70NbTttz8etcl0=
Received: by 10.236.139.138 with SMTP id c10mr1647568yhj.62.1314793806162; Wed, 31 Aug 2011 05:30:06 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id f4sm1064402yhn.41.2011.08.31.05.29.57 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 05:30:02 -0700 (PDT)
Message-ID: <4E5E2976.90102@gmail.com>
Date: Wed, 31 Aug 2011 08:30:46 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>
In-Reply-To: <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 12:28:37 -0000

Yes, but there is another factor that appears to be presumed in the 
discussions that might will help explains the critical difference:

     Even if SHOULD is interpreted as a MUST IMPLEMENT,
     there is no MUST USE guarantee by protocol consumers.

An implementator might decide a particular SHOULD has an absolute no 
consumer value, it might even be harmful, and it might be a low 
adoption currently, that might be enough to ignore it.

On the hand, if he says "Oh, lets add it anyway," he must still 
present it as OPTION to the consumer for them to decide.

In my view, SHOULD are user protocol options to set.  Odds are good a 
SHOULD would be enabled out of the box.  Some might be disabled out of 
the box.   If its not an user option, then that means it must be 
enabled with no way to turn off.  If so, then logic tells me that this 
SHOULD should of been a MUST to be begin right. No?

--
HLS


Eric Burger wrote:
> My interpretation of what you wrote is that in your mind there is absolutely no difference between a SHOULD and a MAY.  They are both optional, and you implement whatever you have time to implement, with SHOULD's prioritized higher than MAY's.
> 
> Even if that is not what you mean, it is what many implementors do.
> 
> I would offer this highlights the problem with today's SHOULD.  Some think SHOULD means something is OK to implement, but life does not end if you do not do it. Others think SHOULD means something HAS to be implemented, unless the environment indicates the protocol will not work in some corner case.
> 
> 
> On Aug 30, 2011, at 3:08 PM, hector wrote:
> 
>> When I approach a protocol to implement, the first thing I typically do is extract and develop the basic wiring of the protocol, the minimum requirements.  Make sure the basic framework is correct 100%, then I look for the SHOULDs and also MAYS which are the easiest to add.  I look at the SHOULD by order of importance and also complexity.  How much "CANDY" is it?  It is a security feature?  What are the other implementation requirements, tools, APIs, etc.  Generally I want to get security out the way.  Its like SMTP AUTH - its not required but anyone cleaning up and rewriting an SMTP spec today, might include the AUTH extension as a SHOULD. And implementators are keen to the importance of it.  But nothing won't break down if you don't, less functionality but the basic structure is still there.
>>
>> Its the same approach used for all the protocols we support. Start with the basics and then add on  as necessary.
>>
>> Eric Burger wrote:
>>> What is the difference in this case between SHOULD or MAY?
>>> On Aug 30, 2011, at 2:49 PM, Adam Roach wrote:
>>>> On 8/29/11 9:44 PM, Eric Burger wrote:
>>>>> Yes, and...
>>>>>
>>>>> I would offer that for most cases, If Y then MUST X or If Z then MUST NOT X *are* what people usually mean when they say SHOULD.  In the spirit of Say What You Mean, a bare SHOULD at the very least raise an ID-nit, suggesting to the author to turn the statement into the if Y then MUST X or if Z then MUST NOT X form.  Being pedantic and pedagogic:
>>>>> 	SHOULD send a 1 UNLESS you receive a 0
>>>>> really means
>>>>> 	UNLESS you receive a 0, one MUST send a 1.
>>>>>
>>>>> My vision of the UNLESS clause is not necessarily a protocol state, but an environment state.  These are things that I can see fit the SHOULD/UNLESS form:
>>>>> 	SHOULD send a 1 UNLESS you are in a walled garden
>>>>> 	SHOULD flip bit 27 UNLESS you have a disk
>>>>> 	SHOULD NOT explode UNLESS you are a bomb
>>>>> are all reasonable SHOULD-level statements.
>>>>>
>>>>> I would offer that ANY construction of SHOULD without an UNLESS is a MAY.
>>>> Eric. Put down the axe and step away from the whetstone. Here, I'll give you some text from RFC 3265 to mull.
>>>>
>>>>
>>>>  deactivated: The subscription has been terminated, but the subscriber
>>>>     SHOULD retry immediately with a new subscription.  One primary use
>>>>     of such a status code is to allow migration of subscriptions
>>>>     between nodes.
>>>>
>>>>
>>>> Let's examine this use of "SHOULD." If the subscriber doesn't re-subscribe, is it an interop issue? No.
>>>>
>>>> Is it in the interest of the implementation to re-subscribe? Yes. At least, under most circumstances. Otherwise, they won't get the state change notifications they want.
>>>>
>>>> Are there cases in which it makes sense for the subscriber _not_ to re-subscribe? Yes, I'm sure there are. It's conceivable that the client happens to be shutting down but hasn't gotten around to terminating this particular subscription yet. But any such exceptions are highly implementation-dependent. Listing them would be useless noise to the reader, and senseless text creation for the author.
>>>>
>>>> Does "SHOULD" get abused by some authors in some documents? Of course it does. But your crusade to throw out a useful tool just because it has been misused on occasion is an extreme over-reaction. I like this tool. I use this tool. If you see people misusing it, slap them.
>>>>
>>>> But don't ban the tool.
>>>>
>>>> /a
>>> ------------------------------------------------------------------------
>>> _______________________________________________
>>> 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 moore@network-heretics.com  Wed Aug 31 05:36:35 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 904C021F8ADC for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 05:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.464
X-Spam-Level: 
X-Spam-Status: No, score=-3.464 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xHD0MLM5+h4 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 05:36:35 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id DEC1D21F8ABE for <ietf@ietf.org>; Wed, 31 Aug 2011 05:36:32 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 634B721963; Wed, 31 Aug 2011 08:38:02 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 08:38:02 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=RyJ Re66wslH4ITmx0HkOW7tqRm0=; b=CyfUn/JQ2Wbtd7ox+qEXA4Asp3SKZQykyMH 1rdmMOW4EkgY14QpT0mObrpIP0rRXe11iVpnj3PYmWTwpUTMezFAszqpV3WAjp7s nVxoaqQEg4AxcD8CjwRo1R1nJx4hIF3l2dnw/Ma7FPeqH2Olv/8AM3VsU0Vef4kl bUmHMkos=
X-Sasl-enc: I8mOXqD3LEmzKkvt4Zr0I5w86TwWadomN0U7GHL/0hAJ 1314794282
Received: from [10.59.1.20] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id E96B84400AA; Wed, 31 Aug 2011 08:38:01 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-67--667851558
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5E2976.90102@gmail.com>
Date: Wed, 31 Aug 2011 08:38:01 -0400
Message-Id: <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com>
To: Hector <sant9442@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 12:36:35 -0000

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

On Aug 31, 2011, at 8:30 AM, Hector wrote:

> In my view, SHOULD are user protocol options to set. =20

In my view, SHOULD should rarely be used for optional protocol features, =
because optional protocol features should themselves be rare.  And the =
primary purpose of SHOULD is not to permit optional protocol features.

Keith


--Apple-Mail-67--667851558
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><div>On Aug 31, 2011, at 8:30 AM, Hector =
wrote:</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-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">In my view, =
SHOULD are user protocol options to set. =
&nbsp;</span></blockquote><br></div><div>In my view, SHOULD should =
rarely be used for optional protocol features, because optional protocol =
features should themselves be rare. &nbsp;And the primary purpose of =
SHOULD is not to permit optional protocol =
features.</div><div><br></div><div>Keith</div><div><br></div></body></html=
>=

--Apple-Mail-67--667851558--

From sant9442@gmail.com  Wed Aug 31 06:11:03 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E56B21F854C for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PlV9CExuL4KZ for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:11:02 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 67A2E21F8AEC for <ietf@ietf.org>; Wed, 31 Aug 2011 06:11:02 -0700 (PDT)
Received: by gyf3 with SMTP id 3so648909gyf.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 06:12:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=lKVAHYK3iYeTNCD2zPb3zzZBlHl0oFJGQ1w3mCh00ko=; b=sfKUYDA9eh+xneBuYvq/VWiQWQ3//fdazuhehZLeLYmrmUXmL21hPtKkr6DP/VsGEc MVImZa6dSr8ytCjkmkH9e6Ej5sDlvcOLZk26XMyS04b+Cq9u/4c3igYchymMDpFgrlNw CdSF+ZLhg95Y7vE4KfZsL8kTp5xiajoOMABvc=
Received: by 10.101.9.4 with SMTP id m4mr275458ani.150.1314796324624; Wed, 31 Aug 2011 06:12:04 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id g17sm7221240ank.36.2011.08.31.06.12.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 06:12:03 -0700 (PDT)
Message-ID: <4E5E3353.4010503@gmail.com>
Date: Wed, 31 Aug 2011 09:12:51 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>
In-Reply-To: <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 13:11:04 -0000

Keith Moore wrote:
> On Aug 31, 2011, at 8:30 AM, Hector wrote:
> 
>> In my view, SHOULD are user protocol options to set.  
> 
> In my view, SHOULD should rarely be used for optional protocol features, 
> because optional protocol features should themselves be rare.  And the primary 
> purpose of SHOULD is not to permit optional protocol features.

If SHOULD is read as a MUST IMPLEMENT, and that also implies MUST USE 
with no provision to disable then its should of been a MUST in the 
first place.

When presented to consumers, we do this for the most part:

o MUST items

No options, to way to turn off. No GUI, Nada.  Under rare 
circumstances, usually due to protocol conflicts, i.e. a MUST really 
should of been a SHOULD and it might have been a SHOULD in protocol 
STD, but made into a MUST in protocol RFC update and that now causes 
problems, hence undocumented switches are provided for support.

o SHOULD items

Here we have three forms of the options:

    [X] Extended Feature A    -  higher sweet benefit! default ON
    [_] Extended Feature B    -  Nice, but high overhead, default OFF
    [_] Extended Feature C    -  It was default ON, but operator said 
NAHHHHH!

MAY options are similar but heres you have learn more about the 
consumer needs to decide what protocol overhead is added and/or 
initial ON/OFF position.

Many Implementators makes decides on the basic of this SHOULD value 
offers. Its a big waste of them, it won't be implemented.  But when 
its get more adoption, maybe.  And we can't impose Bloat Ware options 
that prove to be bad or not desired, so you have to present these 
SHOULDS as options.

I sense a bad direction with what is basically "ALL or Nothing" 
protocol implementation, including with there little adoption, complex 
to support and simply not required. This might be enough to raise the 
barrier on adoption for some protocols that insist on on a "All or 
Nothing" conformance mandate.

Why even bother with SHOULD, and use have MUST and MAY?

--
HLS

From moore@network-heretics.com  Wed Aug 31 06:24:44 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE91E21F8B1F for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.472
X-Spam-Level: 
X-Spam-Status: No, score=-3.472 tagged_above=-999 required=5 tests=[AWL=0.127,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlAkKufC42Ks for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:24:44 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id EB90721F8AFC for <ietf@ietf.org>; Wed, 31 Aug 2011 06:24:43 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id A9D032365D; Wed, 31 Aug 2011 09:26:13 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 31 Aug 2011 09:26:13 -0400
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=olADYcbuuKD1BpYQE9mtmBJd9mo=; b=Ha G9/uxfrXJC6cccwHqllex/tRt9ot5gz9rhn7Zdjfghi0F0H/qkGRA4V9s+zUy+Wo Zpemtzw5yXklfOlpd5zpv1Zc69IfDLIKFx+gkXf7DTrGXkg70JC/wfKLsnAiwYj+ XoGPjyFro2/uklIL3Wyy1g/p9K/a1jDqTwdGcN/+w=
X-Sasl-enc: +3MPB5boI8CuB1A6kRBCevTqKQ91H6SZ4z2qalNEESls 1314797173
Received: from [10.59.1.20] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 382A5A8178F; Wed, 31 Aug 2011 09:26:13 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5E3353.4010503@gmail.com>
Date: Wed, 31 Aug 2011 09:26:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com> <4E5E3353.4010503@gmail.com>
To: Hector <sant9442@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 13:24:44 -0000

On Aug 31, 2011, at 9:12 AM, Hector wrote:

> Keith Moore wrote:
>> On Aug 31, 2011, at 8:30 AM, Hector wrote:
>>> In my view, SHOULD are user protocol options to set. =20
>> In my view, SHOULD should rarely be used for optional protocol =
features, because optional protocol features should themselves be rare.  =
And the primary purpose of SHOULD is not to permit optional protocol =
features.
>=20
> If SHOULD is read as a MUST IMPLEMENT, and that also implies MUST USE =
with no provision to disable then its should of been a MUST in the first =
place.

Just because a feature is optional does not mean that it's a protocol =
feature... i.e. it doesn't mean that it affects how the implementation =
interacts with peers. =20

SHOULD is IMO most often useful not when specifying how a protocol acts =
"on the wire", but when specifying how a protocol needs to be =
implemented on a particular platform, where the precise semantics, API =
details, etc. naturally differ from one platform to another.

> Why even bother with SHOULD, and use have MUST and MAY?

To get people out of the rathole of trying to specify exactly how =
everything must work in excruciating detail, in a world where there is =
inherently going to be some necessary variation.

Keith


From sob@harvard.edu  Wed Aug 31 06:27:30 2011
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 478A421F8B23 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dD5j9SvsEfjf for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:27:29 -0700 (PDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by ietfa.amsl.com (Postfix) with ESMTP id A900F21F8B12 for <ietf@ietf.org>; Wed, 31 Aug 2011 06:27:29 -0700 (PDT)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id D47F3EAC648; Wed, 31 Aug 2011 09:28:55 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: 2119bis
Message-Id: <20110831132855.D47F3EAC648@newdev.eecs.harvard.edu>
Date: Wed, 31 Aug 2011 09:28:55 -0400 (EDT)
From: sob@harvard.edu (Scott O. Bradner)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 13:27:30 -0000

I've been traveling so have not had a chance to do anything but watch
the discussion on a RFC 2119 update.

a few thoughts

1/ I am far from convinced that there is a need to update RFC 2119
      there is a bug in the boilerplate (as has been mentioned) 
      and some people seem to have a hard time understanding what 
      (to me) seem like clear descriptions of (for example) MUST & 
      SHOULD - but the issues do not seem serious enough to warrant
      replacing what is, basically, a simple dictionary & usage 
      constraint

2/ it seems like a very Bad Idea to move 2119 to historic- we move
     RFCs to historic when no one uses them or when they are a Bad
     Idea in light of updated technology - I do not think that makes 
     much sense in this case - in addition it makes the status of RFCs
     that have a normative reference to a historic document a bit
     funky - if an update is actually needed there is no reason that
     I can come up with that it could not just be that -- an update

3/ I doubt that I'll ever catch up with Postel as the most referenced
     RFC author so that is not a consideration (for me)

I wrote RFC 2119 (most using text from RFC 1122) because people were
using MUST without saying what they meant, an update, if people think
that one is actually needed, will serve that purpose as well as 2119 has.  

When I posted the original ID it was pointed out that I should also
address when such terms should be used (i.e. try to limit the use to
where it actually made sense protocol-wise) - I tried to do that but
that part may not have been as successful as it might have been - any
update might try to be clearer in this area that RFC 2119 is.

Scott



From sant9442@gmail.com  Wed Aug 31 06:55:08 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1748721F8B9F for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.276
X-Spam-Level: 
X-Spam-Status: No, score=-3.276 tagged_above=-999 required=5 tests=[AWL=0.323,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oqiVoWmSjRrn for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 06:55:07 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6D36521F8B9D for <ietf@ietf.org>; Wed, 31 Aug 2011 06:55:07 -0700 (PDT)
Received: by gwb20 with SMTP id 20so91332gwb.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 06:56:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=RdXvIUVtMOR4XPESCUF6jy5zRluhJORIui8Cp+KNbPc=; b=jRpN1KNSWbevBFS5IGPsSoBhWRq7dd5xq3nBD6ahIZQ5dqujUKjtsv+i4zaztZnRl1 U79FuGy0RQVeOS+GoX3Z8e9cHBkLyDJbQ+K4utObkT27GV0P69CDjUYntNKDnQrdcK9C AEaE8hmakUdO6Jol1R8YH7V7SxERwq3N4+Qf0=
Received: by 10.236.187.104 with SMTP id x68mr2117152yhm.130.1314798997245; Wed, 31 Aug 2011 06:56:37 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id p63sm5179584yhl.81.2011.08.31.06.56.34 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 06:56:36 -0700 (PDT)
Sender: HLS <sant9442@gmail.com>
Message-ID: <4E5E3DC3.7080201@winserver.com>
Date: Wed, 31 Aug 2011 09:57:23 -0400
From: hector <gmail.sant9442@winserver.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com> <4E5E3353.4010503@gmail.com> <2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com>
In-Reply-To: <2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 13:55:08 -0000

Keith Moore wrote:
> On Aug 31, 2011, at 9:12 AM, Hector wrote:
> 
>> If SHOULD is read as a MUST IMPLEMENT, and that also 
>> implies MUST USE with no provision to disable then its should of 
>> been a MUST in the first place.
> 
> Just because a feature is optional does not mean that it's a 
> protocol feature... i.e. it doesn't mean that it affects how the 
> implementation interacts with peers.  

Thats the problem with trying generalize SHOULD as single 
interpretation for all SHOULDs when it is so highly subjective many times.

I think you are speaking of long term operations where an SHOULD is so 
widely adopted, it inherently because a MUST have in all new 
implementations.  So that vain, sure, eventually the better options 
naturally become part of the protocol to the extent the options might 
be even remove to simplify things.  We also have the opposite where a 
SHOULD is implemented but no one users it so eventually, it may be 
remove as an option.

> SHOULD is IMO most often useful not when specifying how a protocol 
> acts "on the wire", but when specifying how a protocol needs to be 
> implemented on a particular platform, where the precise semantics, 
> API details, etc. naturally differ from one platform to another.

Yeah, but its also very very useful to offering what parts of a 
protocol are on and off and let operators decide what they want. 
Don't we already do this?

> 
>> Why even bother with SHOULD, and just use MUST and MAY?
> 
> To get people out of the rathole of trying to specify exactly how 
> everything must work in excruciating detail, in a world where there is 
> inherently going to be some necessary variation.

I agree, it is the easy way out.  But wouldn't it still be a rathole 
if SHOULD was still a MUST-IMPLEMENT concept which is why a MUST made 
it an rathole in the first place?  Too many people didn't like, not 
want it nor wish to waste time on a unproven concept. So you make it a 
SHOULD or a MAY.

With a MUST-IMPLEMENT view of SHOULD, then SHOULD really isn't 
compromise if you have to implement and even more so if no one is 
allowed to turn it off.

-1 on RFC2119bis :)



From msk@cloudmark.com  Wed Aug 31 07:01:52 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 028DA21F8B48 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.021
X-Spam-Level: 
X-Spam-Status: No, score=-103.021 tagged_above=-999 required=5 tests=[AWL=-0.422, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xn+4mf3geO6t for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:01:51 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 79E6E21F886D for <ietf@ietf.org>; Wed, 31 Aug 2011 07:01:51 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Wed, 31 Aug 2011 07:03:21 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Wed, 31 Aug 2011 07:03:20 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxnsMRScZo43kLhShOXU3dvxjO3QgANcN3w
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9C2@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>
In-Reply-To: <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 14:01:52 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of E=
ric Burger
> Sent: Wednesday, August 31, 2011 12:37 AM
> To: hector
> Cc: IETF discussion list
> Subject: Re: 2119bis
>=20
> I would offer this highlights the problem with today's SHOULD.  Some
> think SHOULD means something is OK to implement, but life does not end
> if you do not do it. Others think SHOULD means something HAS to be
> implemented, unless the environment indicates the protocol will not
> work in some corner case.

On the other hand, given the current SHOULD definition in RFC2119, I'm at a=
 loss to understand how one could reasonably come to other than the second =
interpretation you give here.  It's fairly explicit to me.

From john-ietf@jck.com  Wed Aug 31 07:14:36 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A608421F8BA8 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-0vB4MokNQ5 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:14:36 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 895A821F8BA2 for <ietf@ietf.org>; Wed, 31 Aug 2011 07:14:35 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qyla6-0008aG-4I; Wed, 31 Aug 2011 10:15:54 -0400
Date: Wed, 31 Aug 2011 10:15:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, Eric Burger <eburger@standardstrack.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
Message-ID: <FF995068A37D4EF5ABECFF2C@PST.JCK.COM>
In-Reply-To: <4E5DF1FB.2020306@piuha.net>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.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
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 14:14:36 -0000

--On Wednesday, August 31, 2011 11:34 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

> Eric, John,
> 
>> Would having professional editors make a difference here?
> 
>>> I know it is controversial, but there is at least one other
>...

> I think the existing Discuss criteria already says very
> clearly that editorial comments cannot be blocking DISCUSSes.

This issue drifts quickly from DISCUSS criteria into how we
review, approve, and edit documents, but I think they are
completely intertwined... so please forgive the apparent
digression.

> I see a lot of language feedback from IESG and directorate
> reviews, but its rare to have them appear in the DISCUSSes. If
> they do, its inappropriate, you should push back. And I'm sure
> you will :-)

Yes, but... First of all, a long list of "editorial comments"
from one or more ADs can do fully as good a job of slowing a
document down as a DISCUSS or two.  And anyone smart enough to
be on the IESG is more than capable of disguising what is really
an editorial comment as a substantive issue that gets a DISCUSS.
Part of the problem is that there are a whole series of judgment
calls tangled up with this topic.  For example:

* If an AD says "this particular paragraph is really important
to the specification and, after several readings, I can't tell
what is actually means or whether a particular implementation
would be conforming", that is a problem, certainly worthy of a
"DISCUSS" (or, given Keith's typology, "NO until it is fixed".
On the other hand, "this particular paragraph is important and
it is much harder  to understand than it should be, even though
the intent is clear" is an editorial comment that should be
non-blocking.  I think we all know that the boundary between
those two can be very thin and even a matter for debate.

* I can't speak for others, but I'm often tired with a document
for which I've got responsibility by the time I get it past the
small revisions and nit-picking or WG LC and pre-IETF-LC
comments from ADs.  Faced with what I consider an inappropriate
editorial comment or even an inappropriate DISCUSS, I have a
choice between pushing back (thereby guaranteeing that I will
have to deal with the document for additional weeks or months)
or just making the requested changes and getting the document
off my plate.  I'm probably more stubborn about editorial
matters than most people, but even I usually just give in.

> Besides, we pay the RFC Editor a large amount of money every
> year to do the editing. Documents need to be clear enough to
> be understood, but the RFC editor can handle most of the
> editorial problems.

Yes, and I've been saying that, along with variations on "let
them do their job" for years.  But it introduces another set of
issues.  I don't think I'm giving away a secret by saying that
they believe that their contracts and the way their performance
is measured focus on pages of published output per month.  They
also believe that the IESG has told them things that amount to
"minimal editing" or "copy editing only" on many occasions.
Unless we can change things to shift from measuring what is easy
to include a focus on quality improvements, the RFC Editor ends
up in an impossible situation.

>From a standardization perspective, it also isn't desirable to
make lots of editorial changes post-approval.  AUTH48 is a
rather dangerous process because it is easy to make mistakes
there that no one catches or, again, for an exhausted author to
make "it is easier to let this go than to fight about it"
decisions.  One could, in principle, send all such documents
back to a producing WG for final, pre-publication review but, in
my experience, most of the people in most WGs get more exhausted
by the document end-game than most authors (and most other
participants want to reopen long-dead issues by questioning the
language used to describe them).

This is precisely why many SDOs use a two-stage vote in which
the first vote approves the general concepts and technical
content, the document then gets edited into final form by
profession staff, and then the first and only actual approval
vote occurs (possibly by a different body with a different
mission).  That wouldn't work well in the IETF... and not only
because we have a more-than-one-step standards process.   I
think we could adopt a process in which a WG, or an AD, could
look at a document before IETF LC and say "this is going to need
a lot of editorial work before approval but the technical
content looks ok, so let's hand it off to the RFC Editor now and
get it cleaned up before a final WG review and IETF LC".  But
that has a lot of procedural and budgetary implications and I
don't know if we are ready to deal with them.

> (That being said, I've seen documents that were sent back
> because they really were not understandable. Obviously there
> is some bar under which you should not go, or the document
> cannot advance at all. This happens more in WG stages than in
> the IESG. But if you can't communicate your idea clearly then
> I think it should be up to you to hire co-workers/editors to
> help clarify your idea... not the IETF's problem, IMHO.)

Agreed.  See above.

best,
   john



From moore@network-heretics.com  Wed Aug 31 07:34:27 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71DEC21F8ACE for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.592
X-Spam-Level: 
X-Spam-Status: No, score=-3.592 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39DkElBADI9k for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:34:26 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id B888621F8AC3 for <ietf@ietf.org>; Wed, 31 Aug 2011 07:34:26 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1188723F2C; Wed, 31 Aug 2011 10:35:57 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 31 Aug 2011 10:35:57 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=GcW ITB2CC7bmIrE7/8HpfxDfiVI=; b=XQPsU3KyIhuuLBd34MH3Bn9Hie1CYivvDyg udWuX51r5SqLYCRSN3+ZfgR4yXeNPIBMjF6umzLc5bfI9pntwz7GYAEvuGc2zzZS dlir8BHCkZQfis7TkjNPZx8m1bLHNzI6xTgoTFBkLJbrJESzjT948igCXJN1DAL2 Two2FvGI=
X-Sasl-enc: Bq1x+hugdepSmPL01kY882lvF7bYaCYkiS6gsZ/a0zSp 1314801356
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id C9AF2B215B0; Wed, 31 Aug 2011 10:35:56 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-70--660777967
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF9C2@EXCH-C2.corp.cloudmark.com>
Date: Wed, 31 Aug 2011 10:35:54 -0400
Message-Id: <A215DC38-852B-4BFF-8843-B26E0F28CAAA@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <F5833273385BB34F99288B3648C4F06F13512DF9C2@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 14:34:27 -0000

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

On Aug 31, 2011, at 10:03 AM, Murray S. Kucherawy wrote:

> On the other hand, given the current SHOULD definition in RFC2119, I'm =
at a loss to understand how one could reasonably come to other than the =
second interpretation you give here.  It's fairly explicit to me.

The simplest explanation is that people don't bother to read 2119.


--Apple-Mail-70--660777967
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><div>On Aug 31, 2011, at 10:03 AM, Murray S. Kucherawy =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On the other =
hand, given the current SHOULD definition in RFC2119, I'm at a loss to =
understand how one could reasonably come to other than the second =
interpretation you give here. &nbsp;It's fairly explicit to =
me.<br></span></blockquote></div><br><div>The simplest explanation is =
that people don't bother to read =
2119.</div><div><br></div></body></html>=

--Apple-Mail-70--660777967--

From john-ietf@jck.com  Wed Aug 31 07:41:17 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40BDB21F85B8 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u94gyKdLYApY for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:41:16 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2AAA121F85A3 for <ietf@ietf.org>; Wed, 31 Aug 2011 07:41:16 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qym03-00091H-Jr; Wed, 31 Aug 2011 10:42:44 -0400
Date: Wed, 31 Aug 2011 10:42:42 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Discuss criteria for documents that advance on the standards track
Message-ID: <36352F5671DE5E04F6504860@PST.JCK.COM>
In-Reply-To: <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.net> <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.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 Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 14:41:17 -0000

--On Wednesday, August 31, 2011 08:02 -0400 Keith Moore
<moore@network-heretics.com> wrote:

>> I think the existing Discuss criteria already says very
>> clearly that editorial comments cannot be blocking DISCUSSes.
> 
> So nobody has the job of making sure that the documents are
> well-written in clear English?

Keith, I don't think either Jari or I were saying anything
remotely close to that.

Think about it this way, moving away from the language in 2026
and back to the much-earlier assumptions on which that language,
and the multiple-stage standards process, were based.  With the
understanding that these are oversimplifications, we can have
three types of documents:

	(1) Complete spec, so complete and so clear that someone
	with reasonable familiarity with the technology but no
	contact with the authors, anyone who participated the
	relevant WG, or the WG mailing list can produce an
	implementation that will interoperate with other
	implementations --both those produced with the same
	level of knowledge and those produced by, or in
	coordination with, the authors.
	
	(2) Specs that are good and clear enough to act as aids
	to memory and documentation about agreement so that
	someone who participated in the WG and who can ask
	questions of a WG mailing list and/or the authors can
	produce an interoperable implementation.
	
	(3) A spec that just outlines an idea for others to try
	out.

Because I want to avoid losing the distinction, I would point
out that only the first is really suitable for use in a
procurement spec (although people often accept the second and
sometimes the third).   

>From a standardization standpoint, we should consider the third
as potentially appropriate for Experimental, especially if  the
purpose of the experiment is to help understand what the details
should be.  We've been trying to hold everything (even, in many
cases, experimental documents) up until we get to that first
criterion, but, if one looks at long-term history and reads
between the lines, only DS and above actually require
documentation at that level.  We ought to, IMO, be permitting
publication of PS documents at the second level as long as there
are no _obvious_ ambiguities that cannot be figured out (the
same way) by people of good will acting in good faith and with
help from WG lists and as long as there are no other "known
[technical] defects".

I suggest that we have called that second category "Proposed
Standard" and then interpreted that term in ways that have
caused us harm.  It is closer to what ISO has called a "Type II
Technical Report" (known in internal jargon as a "pre-standard"
or "sub-standard") and what IEEE calls (or used to call) a
"Draft Standard for Trial Use" -- a document that represents
consensus about the idea and about publication, including
publication as a standard when it is mature enough, and good
enough to form a basis for experimentation and serious
evaluation, but not expected to meet criterion (1) above.

>From that particular narrow perspective, if one wants PS
documents published quickly rather than killing them and the
standards process through delays and nit-picking that are almost
irrelevant to the technical content of the specification, then
we either need to make some really major changes in how we do
things or we need to be willing to publish things that,
explicitly or implicitly contain notes like "the following
paragraph is horribly written and barely intelligible and will
need to be fixed up for DS but, right now, everyone involved
knows what it means".  Insisting that all PS documents be
"well-written in clear English" may actually be our enemy.

That doesn't mean they shouldn't be.  And it would be perfectly
reasonable for some WGs and authors to decide the situation is
"do the work now (and accept the added delay) or do it later, so
better now".  But we should not be trying to force every PS
document to meet such a standard... at least if we want to get
them out quickly and have them treated as interim steps rather
than final products. 

>> Besides, we pay the RFC Editor a large amount of money every
>> year to do the editing. Documents need to be clear enough to
>> be understood, but the RFC editor can handle most of the
>> editorial problems.
> 
> If the document is edited for clarity after final review,
> that's really a botch in the process.  It means that the
> review doesn't apply to the version of the document being
> published.   Of course the RFC Editor's resources shouldn't be
> used for documents that aren't otherwise deemed worthy of
> publication, and you'd like to avoid the RFC Editor having to
> do multiple reviews, so I admit that this is tricky to solve.

Yes.  See my previous note.

>> (That being said, I've seen documents that were sent back
>> because they really were not understandable. Obviously there
>> is some bar under which you should not go, or the document
>> cannot advance at all. This happens more in WG stages than in
>> the IESG. But if you can't communicate your idea clearly then
>> I think it should be up to you to hire co-workers/editors to
>> help clarify your idea... not the IETF's problem, IMHO.)
> 
> If writing clear specifications isn't the IETF's problem, I'm
> not sure what is.

Well, see previous note.  But also remember that people evaluate
where to get work done based on what it "costs".  And SDOs like
ISO (and ISO/IEC JTC1) and ITU-T bundle professional editing,
pre-approval-review, into the system for "free".

      john



From moore@network-heretics.com  Wed Aug 31 07:48:16 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67ED921F8BA0 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.592
X-Spam-Level: 
X-Spam-Status: No, score=-3.592 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tsU6kMvD2BIK for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 07:48:15 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id A2AC121F8BA2 for <ietf@ietf.org>; Wed, 31 Aug 2011 07:48:15 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 0B25C24C36; Wed, 31 Aug 2011 10:49:46 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 10:49:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=9PZ bv0O3oSLGIyDp9LD2+/9NDyI=; b=hifpEpt3t0uScZlasLReKWqlqd3FLoMC2If swFocoIiMWHHg1S6v889yUxdmtqVCD9C3puPviaRXsjbpueg2BL7ignaN8sl9An4 6Tx1tGlEu2cfALYjpvKIsUb/NzeASmVIcJo1M6lspU2RSv2SksstJAGj08HuWySG v4BUxUSA=
X-Sasl-enc: Iv6MTFKsg7UxGbK2NFA527M14GvzKiXmSu51afT1hEta 1314802185
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id C50FEB215C3; Wed, 31 Aug 2011 10:49:45 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-72--659948173
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5E3DC3.7080201@winserver.com>
Date: Wed, 31 Aug 2011 10:49:44 -0400
Message-Id: <BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com> <4E5E3353.4010503@gmail.com> <2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com> <4E5E3DC3.7080201@winserver.com>
To: hector <gmail.sant9442@winserver.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 14:48:16 -0000

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

On Aug 31, 2011, at 9:57 AM, hector wrote:

>> SHOULD is IMO most often useful not when specifying how a protocol =
acts "on the wire", but when specifying how a protocol needs to be =
implemented on a particular platform, where the precise semantics, API =
details, etc. naturally differ from one platform to another.
>=20
> Yeah, but its also very very useful to offering what parts of a =
protocol are on and off and let operators decide what they want. Don't =
we already do this?

yes, it is done to some degree.  but that's not, in general, a desirable =
practice. (though there are cases where it can be justified).

Keith



--Apple-Mail-72--659948173
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><div>On Aug 31, 2011, at 9:57 AM, hector =
wrote:</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-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><blockquote =
type=3D"cite">SHOULD is IMO most often useful not when specifying how a =
protocol acts "on the wire", but when specifying how a protocol needs to =
be implemented on a particular platform, where the precise semantics, =
API details, etc. naturally differ from one platform to =
another.<br></blockquote><br>Yeah, but its also very very useful to =
offering what parts of a protocol are on and off and let operators =
decide what they want. Don't we already do =
this?</span></blockquote></div><br><div>yes, it is done to some degree. =
&nbsp;but that's not, in general, a desirable practice. (though there =
are cases where it can be =
justified).</div><div><br></div><div>Keith</div><div><br></div><div><br></=
div></body></html>=

--Apple-Mail-72--659948173--

From john@jlc.net  Wed Aug 31 08:05:20 2011
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E21C621F8BEC; Wed, 31 Aug 2011 08:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.34
X-Spam-Level: 
X-Spam-Status: No, score=-106.34 tagged_above=-999 required=5 tests=[AWL=0.259, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33XpvzdYAfKq; Wed, 31 Aug 2011 08:05:20 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id E61D521F8BFB; Wed, 31 Aug 2011 08:05:19 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 7EBB033C2C; Wed, 31 Aug 2011 11:06:49 -0400 (EDT)
Date: Wed, 31 Aug 2011 11:06:49 -0400
From: John Leslie <john@jlc.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
Message-ID: <20110831150649.GF8140@verdi>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <4E5DD655.1000809@piuha.net> <06D5CA5A-040D-40A6-BF19-80BAEFBA28CF@network-heretics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <06D5CA5A-040D-40A6-BF19-80BAEFBA28CF@network-heretics.com>
User-Agent: Mutt/1.4.1i
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:05:21 -0000

Keith Moore <moore@network-heretics.com> wrote:
> 
> The biggest problem with the current voting system (other than
> misleading labels, which do cause real problems of their own) is the
> presumption that the document should go forward no matter how few
> IESG members read the document.

   Keith makes a good point here; but I wouldn't agree to any rule
that a particular number must "read" a document. Some ADs quite
properly defer actual reading to review teams.

> So No Objection votes from ADs who didn't read the document count as
> Yes votes,

   No, they don't. (But I can't ask folks posting to this thread to
actually _understand_ the difference.)

   Roughly, the rule says "enough" ADs must enter a "position" before
a document can be approved. Basically, "No-Objection" says the AD is
"somewhat" familiar with the document and actively consents to approving
it.

   These "positions" are _NOT_ "votes".

> but there's also a presumption in the rules (as well as pressure from
> other ADs who want to get documents off the agenda) to clear Discuss
> votes in favor of moving a document forward whether or not the
> identified issues have been adequately addressed.

   This is somewhat true, but the "pressure" is highly variable. The
agendas _are_ too crowded (IMHO); but in most cases sufficient progress
will have been made before the telechat that only a few seconds are
needed to agree to "AD-followup" status.

   When there is no progress between telechats (most often due to
unresponsive authors/editors), there _is_ some pressure to reduce
what a DISCUSS asks for. It might help for non-IESG folk to chime in
on whether this is good or bad...

   (There _are_ cases where the responsible AD puts quite a bit of
pressure on the DISCUSS-holder: that's really an internal issue which
I don't believe this list should be discussing.)

> (One thing that I didn't mention that also needs to be fixed if
> it's still the case is the presumption that the responsible AD
> votes Yes for the document. I don't know what the tools do now,
> but this Yes vote used to be automatically filled-in.)

   We're seeing a number of cases where the responsible AD holds a
DISCUSS at the time of the telechat -- generally because LastCall
hadn't ended yet when the document was placed on the agenda.

   IMHO, there's nothing there that needs "fixing".

> Arguably when a poor quality document gets to IESG, it's a failure
> on the part of the WG to do due diligence.

   IMHO, there _are_ poor-quality documents that get on the IESG agenda.
I'm not sure it helps to allocate blame...

   But there is a huge variance between WGs on diligence. I am alarmed
by the sheer number of COMMENTS saying in essence, "This document is
not specific enough to guide an implementor to an interoperable
implementation." To me, that's really-close to DISCUSS territory...

   However, we really don't have a process for improving situations
like that -- other than for it to be a DISCUSS and for authors to
actually be responsive (which would probably require repeating at
least one LastCall). :^(

   In the absence of such a process, I really can't blame ADs for
reducing such issues from DISCUSS to COMMENT, and entering ABSTAIN
if they think the issue is serious.

> But the problem is actually deeper than that - it's partially
> structural (in that IETF partitions almost all work into narrowly
> focused WGs who don't represent a sufficiently broad spectrum of
> interests), and partially due to a failure to consistently apply
> good engineering principles across all of IETF.   

   +1

   This problem, of course, is endemic in organizations that depend
on volunteers. And I really don't have suggestions on how to ensure
sufficient wide-area review, though review teams certainly help.

   I wonder if there's some room for process-improvement by formalizing
some role for review teams...

> IESG's assuming that the WG has produced a quality result basically
> works to mask the other problems with IETF's way of doing work.

   I don't agree that's what IESG members "assume" -- they IMHO instead
presume that documenting ideas (even not-fully-baked ideas) is a
mostly-unmitigated good-thing.

> But even if WGs generally did produce high quality results without
> issues (which I don't think is the case now), IESG review should
> still not presume that they do.   There will always be some failures
> at the WG level, and the IESG's job is to try to catch those.

   I don't think we have universal agreement on that as a goal.

   Of course, neither do we have universal agreement that anyone else
has the job to "catch these". Some of us quite plainly believe it
shouldn't be anyone's job to "catch these": that ideas should be
published and we should see whether "rough consensus" emerges later.

   (All of which brings us to the actual question: when advancing a
maturity-level, what constitutes sufficient "consensus"? Arguably,
folks will expect a higher maturity level to indicate that the
"standard" is ready to be handed to an implementor, and merely by
following it, sufficient interoperability is ensured. Alas, we
really don't have a process to address that expectation...)

--
John Leslie <john@jlc.net>

From moore@network-heretics.com  Wed Aug 31 08:06:39 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4410A21F8663 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Level: 
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LoM1Y7RGzz8t for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:06:38 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD8F21F85DA for <ietf@ietf.org>; Wed, 31 Aug 2011 08:06:38 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id AA3F1246DA; Wed, 31 Aug 2011 11:08:08 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 11:08:08 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=HbU UAGsSQ3Xh/iRQ3RWeQT861E8=; b=bXuE2LbPYVHNlPJ1H1INbK9wHcsEyS5QyzP bBUUBxqo2xy8jIqOc/Lgnz9TueFsp3QkWyb5OzXC7K6nhvJs4Y9E7MJMI7J2pT0V z5ta2H3LnG60wd3wv8DI7kw0Iix78AavF6jeVYsLpSD8YXxIU0rMvbKqOGP6WLq7 xkYZyM18=
X-Sasl-enc: x5cMsY3clGcC9Gi5cXNUPmKH3baYyH4MrqQ6F11N8TQb 1314803288
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 6857EB215B9; Wed, 31 Aug 2011 11:08:08 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-73--658845560
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <36352F5671DE5E04F6504860@PST.JCK.COM>
Date: Wed, 31 Aug 2011 11:08:07 -0400
Message-Id: <A9A04168-FBDC-44BC-9B35-6EBBB781CEBC@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.net> <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.com> <36352F5671DE5E04F6504860@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:06:39 -0000

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

On Aug 31, 2011, at 10:42 AM, John C Klensin wrote:

> We ought to, IMO, be permitting
> publication of PS documents at the second level as long as there
> are no _obvious_ ambiguities that cannot be figured out (the
> same way) by people of good will acting in good faith and with
> help from WG lists and as long as there are no other "known
> [technical] defects".

That would be fine with me if we could somehow effectively discourage =
deployment of proposed standards in products.  But that's a lost cause, =
IMO.

Keith


--Apple-Mail-73--658845560
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><div>On Aug 31, 2011, at 10:42 AM, John C Klensin wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">We ought to, =
IMO, be permitting<br>publication of PS documents at the second level as =
long as there<br>are no _obvious_ ambiguities that cannot be figured out =
(the<br>same way) by people of good will acting in good faith and =
with<br>help from WG lists and as long as there are no other =
"known<br>[technical] defects".</span></blockquote><br></div>That would =
be fine with me if we could somehow effectively discourage deployment of =
proposed standards in products. &nbsp;But that's a lost cause, =
IMO.<div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-73--658845560--

From tony@att.com  Wed Aug 31 08:09:05 2011
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF72521F8C2A for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:09:05 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EfyxkVQzaV4L for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:09:04 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by ietfa.amsl.com (Postfix) with ESMTP id C34B321F8BEC for <ietf@ietf.org>; Wed, 31 Aug 2011 08:09:04 -0700 (PDT)
X-Env-Sender: tony@att.com
X-Msg-Ref: server-3.tower-120.messagelabs.com!1314803433!35769366!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17240 invoked from network); 31 Aug 2011 15:10:34 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-3.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Aug 2011 15:10:34 -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 p7VFAwIg003245 for <ietf@ietf.org>; Wed, 31 Aug 2011 11:10:59 -0400
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 p7VFAuQg003196 for <ietf@ietf.org>; Wed, 31 Aug 2011 11:10:56 -0400
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 p7VFATLI014485 for <ietf@ietf.org>; Wed, 31 Aug 2011 11:10:29 -0400
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 p7VFALBp014194 for <ietf@ietf.org>; Wed, 31 Aug 2011 11:10:22 -0400
Received: from [135.70.0.246] (vpn-135-70-0-246.vpn.west.att.com[135.70.0.246]) by maillennium.att.com (mailgw1) with ESMTP id <20110831151020gw100e4lnke> (Authid: tony); Wed, 31 Aug 2011 15:10:20 +0000
X-Originating-IP: [135.70.0.246]
Message-ID: <4E5E4ED4.5080702@att.com>
Date: Wed, 31 Aug 2011 11:10:12 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: "Scott O. Bradner" <sob@harvard.edu>
Subject: non-2119
References: <20110831132855.D47F3EAC648@newdev.eecs.harvard.edu>
In-Reply-To: <20110831132855.D47F3EAC648@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:09:06 -0000

While 2119 is being discussed, I thought I'd mention a small I-D that 
Dave Crocker and I wrote on terminology that might be used in places 
where 2119 ought not apply. It's

     Non-Normative Synonyms in RFCs
     http://tools.ietf.org/html/draft-hansen-nonkeywords-non2119-01

Thoughts on this draft would be appreciated as well.

     Tony Hansen
     tony@att.com

On 8/31/2011 9:28 AM, Scott O. Bradner wrote:
> I've been traveling so have not had a chance to do anything but watch
> the discussion on a RFC 2119 update.
>
> a few thoughts
>
> 1/ I am far from convinced that there is a need to update RFC 2119
>        there is a bug in the boilerplate (as has been mentioned)
>        and some people seem to have a hard time understanding what
>        (to me) seem like clear descriptions of (for example) MUST&
>        SHOULD - but the issues do not seem serious enough to warrant
>        replacing what is, basically, a simple dictionary&  usage
>        constraint
>
> 2/ it seems like a very Bad Idea to move 2119 to historic- we move
>       RFCs to historic when no one uses them or when they are a Bad
>       Idea in light of updated technology - I do not think that makes
>       much sense in this case - in addition it makes the status of RFCs
>       that have a normative reference to a historic document a bit
>       funky - if an update is actually needed there is no reason that
>       I can come up with that it could not just be that -- an update
>
> 3/ I doubt that I'll ever catch up with Postel as the most referenced
>       RFC author so that is not a consideration (for me)
>
> I wrote RFC 2119 (most using text from RFC 1122) because people were
> using MUST without saying what they meant, an update, if people think
> that one is actually needed, will serve that purpose as well as 2119 has.
>
> When I posted the original ID it was pointed out that I should also
> address when such terms should be used (i.e. try to limit the use to
> where it actually made sense protocol-wise) - I tried to do that but
> that part may not have been as successful as it might have been - any
> update might try to be clearer in this area that RFC 2119 is.
>
> Scott
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From spencer@wonderhamster.org  Wed Aug 31 08:22:21 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06D121F8B85 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:22:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.164
X-Spam-Level: 
X-Spam-Status: No, score=-102.164 tagged_above=-999 required=5 tests=[AWL=0.435, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnyjwSZJVoHU for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:22:20 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id AD9B721F8B83 for <ietf@ietf.org>; Wed, 31 Aug 2011 08:22:20 -0700 (PDT)
Received: from S73602b ([50.58.7.243]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MGRtA-1R3CV80ntQ-00DVSy; Wed, 31 Aug 2011 11:23:48 -0400
Message-ID: <EF3771F6968F4FBBADF419F0E8EFD2C6@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Jari Arkko" <jari.arkko@piuha.net>, "IETF Discussion" <ietf@ietf.org>
References: <4E5D45B1.50107@piuha.net>
Subject: Re: Discuss criteria for documents that advance on the standards track
Date: Wed, 31 Aug 2011 10:23:46 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
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.6109
X-Provags-ID: V02:K0:jcMREEQ2qG3LiXWYb38QfJvgOhFU0+oPbtc9i8ZMPez DiO+XKm+AwGiwQ4jQfMcAUWL6KGzl7sPCUobAUg9Xp6BGpXrSv BwovvAnPLm7cWOuaXTkIHlgwpTBad0o5/yk9hwIf1hEMugcaSe OKduDLko7BHvtQf+egfs1hAf+m+w6l8qxbPnh5I0udprQe11n/ btewtRsDTAagIqWAqy/4HEbHLboxkzpZsQ2ZRecI/TpNXPfPQO V3jgwIRtkNqGBfnXW2vXoxXMXIkWIo/ltm0gRartgBCXJfKeuz vZl3P35rSzwTcZTMCDo5gfaWwDLPAFS7M9ErSF15jY0GCQAxXp uylJjkT+/Gq+Q5ZSCKYGnXLssECx87SZNgOsEeqAV
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:22:21 -0000

Dear Jari,

> During the discussion of the two maturity levels change, a question was 
> brought up about DISCUSSes appropriate for documents that advance on the 
> standards track. We discussed this in the IESG and I drafted some 
> suggested guidelines. Feedback on these suggestions would be welcome. The 
> intent is to publish an IESG statement to complement the already existing 
> general-purpose DISCUSS criteria IESG statement 
> (http://www.ietf.org/iesg/statement/discuss-criteria.html).
>
> Here are the suggested guidelines for documents that advance to IS:
>
> http://www.arkko.com/ietf/iesg/discuss-criteria-advancing.txt
>
> Comments appreciated. Please send comments either on this list or to the 
> IESG (iesg@ietf.org) in time before our next telechat (Thursday, September 
> 8, 2011).
>
> Jari

As with 2119bis, thank you guys for putting this together.

The text in http://www.arkko.com/ietf/iesg/discuss-criteria-advancing.txt
says

   IESG reviews should be considered as a review of "last resort".  Most
   documents reviewed by the IESG are produced and reviewed in the
   context of IETF working groups.  In those cases, the IESG cannot
   overrule working group consensus without good reason; informed
   community consensus should prevail.

I might have thought that the point for documents advancing on the standards
track is that they already have *IETF* consensus (especially if they are
being advanced without text changes), so the IESG cannot overrule *IETF*
consensus without good reason ... which seems like a higher bar (one can 
more easily assume the existence of a rogue working group producing a rogue 
Internet-Draft, than a rogue IETF that is still sane enough to NomCom-select 
non-rogue ADs who will push back on rogue standards-track documents 
advancing :-)

So perhaps s/informed working group consensus/informed IETF consensus/?

I note that this isn't quite tying the IESG's hands (I'm reading this 
descriptive text as the moral equivalent of "MUST NOT overrule IETF 
consensus without good reason", which leaves one hand free).

Spencer


From moore@network-heretics.com  Wed Aug 31 08:28:10 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87DFB21F8B51; Wed, 31 Aug 2011 08:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Level: 
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OkkO9BNzLjOp; Wed, 31 Aug 2011 08:28:09 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB5D21F8AF9; Wed, 31 Aug 2011 08:28:09 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id E7FD124A9A; Wed, 31 Aug 2011 11:29:39 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 11:29:39 -0400
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=9x2ZGpA4TrKWaS5RHSIq5kVYJNk=; b=f4 YSQoLaPMh+4N4MEUG2uXknLr2cqM3IafuG/BD4RSpkVFNg6p5odWhb+ITi6InEwr 7U8x8fxX6AQCpasIrcHSGQDQAzlt9yUi8rAyqYG0hZaOo+/HZvli8P/5fp/e3s25 MWQsfX4HUDhbPdZVrcXDordiQ9md/acSKGJh0dvGA=
X-Sasl-enc: tPEnp6l49PzWV/8MVy/M6jx39EbBuS0B+PPOUgl2b85V 1314804579
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id A890DB215D4; Wed, 31 Aug 2011 11:29:39 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110831150649.GF8140@verdi>
Date: Wed, 31 Aug 2011 11:29:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <37F59D17-F5A6-43CA-B191-0F9DBD11497B@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <4E5DD655.1000809@piuha.net> <06D5CA5A-040D-40A6-BF19-80BAEFBA28CF@network-heretics.com> <20110831150649.GF8140@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:28:10 -0000

On Aug 31, 2011, at 11:06 AM, John Leslie wrote:

> Keith Moore <moore@network-heretics.com> wrote:
>>=20
>> The biggest problem with the current voting system (other than
>> misleading labels, which do cause real problems of their own) is the
>> presumption that the document should go forward no matter how few
>> IESG members read the document.
>=20
>   Keith makes a good point here; but I wouldn't agree to any rule
> that a particular number must "read" a document. Some ADs quite
> properly defer actual reading to review teams.

I disagree that that is "quite properly".  I believe that the AD's name =
goes on the vote, so an AD whose vote is actually counted as =
contributing toward yes or no has some responsibility to read the =
document.  Having said that, I'll readily admit that I read some =
documents more thoroughly than others when I was an AD.

>> So No Objection votes from ADs who didn't read the document count as
>> Yes votes,
>=20
>   No, they don't. (But I can't ask folks posting to this thread to
> actually _understand_ the difference.)

In practice, they do, because the difference between Yes and NoObj under =
current voting rules is never significant.

>   Roughly, the rule says "enough" ADs must enter a "position" before
> a document can be approved. Basically, "No-Objection" says the AD is
> "somewhat" familiar with the document and actively consents to =
approving
> it.
>=20
>   These "positions" are _NOT_ "votes".

Call them what you will, they're still explicitly enumerated.

>> but there's also a presumption in the rules (as well as pressure from
>> other ADs who want to get documents off the agenda) to clear Discuss
>> votes in favor of moving a document forward whether or not the
>> identified issues have been adequately addressed.
>=20
>   This is somewhat true, but the "pressure" is highly variable. The
> agendas _are_ too crowded (IMHO); but in most cases sufficient =
progress
> will have been made before the telechat that only a few seconds are
> needed to agree to "AD-followup" status.

That, of course, is how things should work.   Most drafts should not be =
controversial.   It's what happens when things are controversial that =
I'm concerned about.

>> (One thing that I didn't mention that also needs to be fixed if
>> it's still the case is the presumption that the responsible AD
>> votes Yes for the document. I don't know what the tools do now,
>> but this Yes vote used to be automatically filled-in.)
>=20
>   We're seeing a number of cases where the responsible AD holds a
> DISCUSS at the time of the telechat -- generally because LastCall
> hadn't ended yet when the document was placed on the agenda.
>=20
>   IMHO, there's nothing there that needs "fixing".

Maybe that's been fixed since I was on IESG.  If so I'm glad to hear it.

>> Arguably when a poor quality document gets to IESG, it's a failure
>> on the part of the WG to do due diligence.
>=20
>   IMHO, there _are_ poor-quality documents that get on the IESG =
agenda.
> I'm not sure it helps to allocate blame...
>=20
>   But there is a huge variance between WGs on diligence. I am alarmed
> by the sheer number of COMMENTS saying in essence, "This document is
> not specific enough to guide an implementor to an interoperable
> implementation." To me, that's really-close to DISCUSS territory...

To me, it's more than adequate grounds to reject a document.   It should =
be considered a duty to vote DISCUSS on such documents.

>   However, we really don't have a process for improving situations
> like that -- other than for it to be a DISCUSS and for authors to
> actually be responsive (which would probably require repeating at
> least one LastCall). :^(
>=20
>   In the absence of such a process, I really can't blame ADs for
> reducing such issues from DISCUSS to COMMENT, and entering ABSTAIN
> if they think the issue is serious.

And again, the idea that an AD should be compelled to label such an =
objection as an abstention, is harmful.

>> But the problem is actually deeper than that - it's partially
>> structural (in that IETF partitions almost all work into narrowly
>> focused WGs who don't represent a sufficiently broad spectrum of
>> interests), and partially due to a failure to consistently apply
>> good engineering principles across all of IETF.  =20
>=20
>   +1
>=20
>   This problem, of course, is endemic in organizations that depend
> on volunteers. And I really don't have suggestions on how to ensure
> sufficient wide-area review, though review teams certainly help.
>=20
>   I wonder if there's some room for process-improvement by formalizing
> some role for review teams...

perhaps.

>> IESG's assuming that the WG has produced a quality result basically
>> works to mask the other problems with IETF's way of doing work.
>=20
>   I don't agree that's what IESG members "assume" -- they IMHO instead
> presume that documenting ideas (even not-fully-baked ideas) is a
> mostly-unmitigated good-thing.

I don't think it's what individual IESG members assume; I think it's =
what the voting guidelines and other aspects of IESG's process assume.  =
And that process has been around without many changes since before I was =
on IESG, which is to say for 15 years or more.  It's not a valid =
assumption, and it hasn't been a valid assumption since the IETF grew to =
more than a few hundred active participants.  (When I first started =
working with IETF circa 1990, cross-area review was much less of an =
issue because the affected community was so much smaller, the protocols =
were much less complex, and the installed base was so small that it was =
relatively easy to fix mistakes.)

>> But even if WGs generally did produce high quality results without
>> issues (which I don't think is the case now), IESG review should
>> still not presume that they do.   There will always be some failures
>> at the WG level, and the IESG's job is to try to catch those.
>=20
>   I don't think we have universal agreement on that as a goal.

Perhaps not, but I want to explicitly state that some form of =
area-independent review, independent of the WG, is an appropriate and =
necessary goal.  There are other ways to achieve that goal than having =
IESG do the review.  But the idea that nobody should do the review and =
the WG's output should always be considered adequate is ridiculous.

Keith


From moore@network-heretics.com  Wed Aug 31 08:33:39 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A56C921F8BD3 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Level: 
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQVERKk0yZyK for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:33:39 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id C677C21F8B4C for <ietf@ietf.org>; Wed, 31 Aug 2011 08:33:38 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2C0AC233C6; Wed, 31 Aug 2011 11:35:09 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 31 Aug 2011 11:35:09 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=51T hEcjqk1qy7Aj/RrQ6uA2/TY0=; b=dAq/n0Xj9FeQqVJalSZuxgdFdgLpq1Hi/L7 THO5vE50P94vx7MuQ1GZSpBrZ9A7iKjTO2BcRyadL3fz9cXpF7zS7HG4gKfgNrUr NncVOBC8O4R87cI9tSkJwGrWVJCQ+sGBIFEOU6EHV3V620sfEQfwrvnRPMzEgopK HJgbaBog=
X-Sasl-enc: JlfD3EZjBLBNP5WIO295K8zbNWBZIDKzA/lcPFaL8K+H 1314804909
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id EBC6BB20310; Wed, 31 Aug 2011 11:35:08 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-75--657225614
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <EF3771F6968F4FBBADF419F0E8EFD2C6@china.huawei.com>
Date: Wed, 31 Aug 2011 11:35:06 -0400
Message-Id: <18C49016-D75F-4707-8EC4-0937EAE6C591@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <EF3771F6968F4FBBADF419F0E8EFD2C6@china.huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:33:39 -0000

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

thanks Spencer for pointing this part out.

On Aug 31, 2011, at 11:23 AM, Spencer Dawkins wrote:

>  IESG reviews should be considered as a review of "last resort".  Most
>  documents reviewed by the IESG are produced and reviewed in the
>  context of IETF working groups.  In those cases, the IESG cannot
>  overrule working group consensus without good reason; informed
>  community consensus should prevail.

The idea that WG consensus should prevail is simply incorrect.  It =
biases IESG in an inappropriate way.

There are a number of very good reasons for overriding WG consensus, =
e.g.

- there is no evidence of broad community consensus or a clear lack of =
broad community consensus
- the document does not meet the criteria specified in 2026 (or other =
document when applicable)
- the document is ambiguous in such a way that it is likely to degrade =
interoperability

The WG DOES NOT represent the entire community.    Far too often, WGs =
are deliberately chartered in such a way as to marginalize parts of the =
community

Keith


--Apple-Mail-75--657225614
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; =
">thanks Spencer for pointing this part out.<div><br><div><div>On Aug =
31, 2011, at 11:23 AM, Spencer Dawkins wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">&nbsp;IESG =
reviews should be considered as a review of "last resort". =
&nbsp;Most<br>&nbsp;documents reviewed by the IESG are produced and =
reviewed in the<br>&nbsp;context of IETF working groups. &nbsp;In those =
cases, the IESG cannot<br>&nbsp;overrule working group consensus without =
good reason; informed<br>&nbsp;community consensus should =
prevail.<br></span></blockquote></div><br></div><div>The idea that WG =
consensus should prevail is simply incorrect. &nbsp;It biases IESG in an =
inappropriate way.</div><div><br></div><div>There are a number of very =
good reasons for overriding WG consensus, =
e.g.</div><div><br></div><div>- there is no evidence of broad community =
consensus or a clear lack of broad community consensus</div><div>- the =
document does not meet the criteria specified in 2026 (or other document =
when applicable)</div><div>- the document is ambiguous in such a way =
that it is likely to degrade =
interoperability</div><div><br></div><div>The WG DOES NOT represent the =
entire community. &nbsp; &nbsp;Far too often, WGs are deliberately =
chartered in such a way as to marginalize parts of the =
community</div><div><div><br></div></div><div>Keith</div><div><br></div></=
body></html>=

--Apple-Mail-75--657225614--

From john-ietf@jck.com  Wed Aug 31 08:34:54 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB9421F8C0C for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SlItoksjLTfA for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:34:54 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id B6FD921F8C06 for <ietf@ietf.org>; Wed, 31 Aug 2011 08:34:53 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qympx-0009s7-A2; Wed, 31 Aug 2011 11:36:21 -0400
Date: Wed, 31 Aug 2011 11:36:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
Message-ID: <D254EA76DCADA61E7C3BDEA2@PST.JCK.COM>
In-Reply-To: <A9A04168-FBDC-44BC-9B35-6EBBB781CEBC@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.net> <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.com> <36352F5671DE5E04F6504860@PST.JCK.COM> <A9A04168-FBDC-44BC-9B35-6EBBB781CEBC@network-heretics.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 Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:34:54 -0000

--On Wednesday, August 31, 2011 11:08 -0400 Keith Moore
<moore@network-heretics.com> wrote:

> On Aug 31, 2011, at 10:42 AM, John C Klensin wrote:
> 
>> We ought to, IMO, be permitting
>> publication of PS documents at the second level as long as
>> there are no _obvious_ ambiguities that cannot be figured out
>> (the same way) by people of good will acting in good faith
>> and with help from WG lists and as long as there are no other
>> "known [technical] defects".
> 
> That would be fine with me if we could somehow effectively
> discourage deployment of proposed standards in products.  But
> that's a lost cause, IMO.

Keith,

IMO, there are two possibilities here.  At this point, sadly,
both involve a chicken-and-egg problem.  Such is life.

(1) We proceed as if Proposed Standards are what 2026 (and the
earlier culture) claims they are and work on ways to reinforce
that notion in the community.  If that is our goal, than getting
documents out sooner and having them look a bit rough as well as
being a bit rough is A Good Thing and reinforces the "deploying
at PS, much less at I-D, is taking a big risk".  The idea isn't
foreign to the industry: to take a handy example, we saw
products identified as 801.11-draft-N floating around for years.
Every vendor who shipped one (and their more sophisticated
customers) knew that there could be serious incompatibilities
between their approximations to the drafts and the real 802.11n.

(2) We accept, and effectively encourage, deployment of proposed
standards in products, either because it is a lost cause or
because we think it is a good idea.  As part of that, we move
further down the path of ensuring that PS documents are complete
and polished (my group (1)) and of guaranteeing that there will
be no significant changes in the future (either in going to DS
or in grade).    If that is really our position, then we better
stop grumbling about how long it takes to get PS documents out
(and the partially-consequential deployment of technologies from
I-Ds), accept the fact that the SDOs who used to be very
concerned about how much faster the IETF was than they were have
now won and become faster than us (in large measure because we
have slowed down so much).  And we should stop wasting time
trying to figure out how many maturity levels we need or what
those criteria should be because the answer is "one level is
what we get and pretending anything else, e.g., by trying to
fine-tune procedures, is an embarrassing public act of
self-delusion" (stronger language occurs to me but would
probably get the message killed by spam filters).

Remember that, while ignoring procedures and category
definitions that we don't follow is not desirable, "fixing" them
to reflect a model that doesn't (and won't) exist either is a
public demonstration that we are disconnected from reality.  I'd
much rather leave that distinction to some other SDOs than join
them.  YMMD.

    john






From jari.arkko@piuha.net  Wed Aug 31 08:42:31 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 261D321F8C26 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:42:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fzIsW-rBnLl2 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:42:30 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 3E18321F8C1E for <ietf@ietf.org>; Wed, 31 Aug 2011 08:42:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5D9912D223; Wed, 31 Aug 2011 18:44:00 +0300 (EEST)
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 qkrFJbG4r+Qn; Wed, 31 Aug 2011 18:43:59 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id AC0DE2CE66; Wed, 31 Aug 2011 18:43:59 +0300 (EEST)
Message-ID: <4E5E56BF.6050909@piuha.net>
Date: Wed, 31 Aug 2011 18:43:59 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <806FF78E-17CF-43A3-9F74-80AA876E4A08@mnot.net>
In-Reply-To: <806FF78E-17CF-43A3-9F74-80AA876E4A08@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:42:31 -0000

> Unless of course one considers us the Protocol Nanny's(tm) - if do not do a SHOULD, we will send you to bed without your treacle! I.e., there IS NO DISTINCTION BETWEEN A BARE SHOULD AND A MAY.
>

Of course there is. Its the distinction between -

Qualified SHOULD) Here lie dragons. Take the recommended route, unless you know how to fight them.

Unqualified SHOULD) Here lie some dangers. Check with someone who knows, or take the recommended route.

MAY) Here's an area. You could go there.

Of course, the first and last pieces of text are preferred. But sometimes no one was brave enough to explore the area, so we don't actually know what dangers there are, they cannot be listed.

Jari


From moore@network-heretics.com  Wed Aug 31 08:45:33 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A44121F8C44 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.594
X-Spam-Level: 
X-Spam-Status: No, score=-3.594 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqvcZ62emZxy for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:45:32 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD6821F8C4F for <ietf@ietf.org>; Wed, 31 Aug 2011 08:45:32 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8E10723E81; Wed, 31 Aug 2011 11:47:02 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 31 Aug 2011 11:47:02 -0400
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=vNCsfa9nu7Q8GX/FZ9egDtDLwEU=; b=Zp hZi4lOXVeyLasvJM/Q9SpFmn7bCqen6S5o8jkrYlJoaJ21GME9d4J16y0g7WxJtc SmUmu4hZ7uiIc61lpQ+LI4ntkv/jzL00nMwWVJd4pfoyjkvpHt1hvZF9w/6cPVtH +iZ4HmVkgIlOdQIGKeJMtgjHtgvhVP4caZPxNvGJY=
X-Sasl-enc: x6364cMEkmLm3c1WyenzE3VueiqpAcPkIFNLrcFdyfRV 1314805622
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 52D61B215C0; Wed, 31 Aug 2011 11:47:02 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <D254EA76DCADA61E7C3BDEA2@PST.JCK.COM>
Date: Wed, 31 Aug 2011 11:47:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA800973-B00E-4624-BB16-FE1203D164E3@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.net> <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.com> <36352F5671DE5E04F6504860@PST.JCK.COM> <A9A04168-FBDC-44BC-9B35-6EBBB781CEBC@network-heretics.com> <D254EA76DCADA61E7C3BDEA2@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:45:33 -0000

On Aug 31, 2011, at 11:36 AM, John C Klensin wrote:

>>> We ought to, IMO, be permitting
>>> publication of PS documents at the second level as long as
>>> there are no _obvious_ ambiguities that cannot be figured out
>>> (the same way) by people of good will acting in good faith
>>> and with help from WG lists and as long as there are no other
>>> "known [technical] defects".
>>=20
>> That would be fine with me if we could somehow effectively
>> discourage deployment of proposed standards in products.  But
>> that's a lost cause, IMO.
>=20
> Keith,
>=20
> IMO, there are two possibilities here.  At this point, sadly,
> both involve a chicken-and-egg problem.  Such is life.
>=20
> (1) We proceed as if Proposed Standards are what 2026 (and the
> earlier culture) claims they are and work on ways to reinforce
> that notion in the community. [...]

> (2) We accept, and effectively encourage, deployment of proposed
> standards in products, either because it is a lost cause or
> because we think it is a good idea.  [...]

Agree with your description of the two possibilities, but I think the =
decision of possibility 2 has long since been forced on us by market =
expectation and habit.

We could fix it, perhaps, by drastically changing how we label our =
products (dropping the whole notion of "Proposed Standard", refusing to =
publish your category 2 documents as RFCs, etc.).   But we can't =
significantly change market perception of what "RFC" and "Proposed =
Standard" mean. =20

(which, BTW, is why I think that moving to a two-step process, while =
probably Mostly Harmless, won't do a bit of good in the overall scheme =
of things)

> Remember that, while ignoring procedures and category
> definitions that we don't follow is not desirable, "fixing" them
> to reflect a model that doesn't (and won't) exist either is a
> public demonstration that we are disconnected from reality.  I'd
> much rather leave that distinction to some other SDOs than join
> them.  YMMD.

And my assertion is that the model inherent in your possibility #1 above =
doesn't exist and won't exist absent from drastic change.   Insisting on =
high quality for proposed standards is recognizing current market =
reality. =20

And I'm not one of those people who believes that market perceptions are =
inherently unchangeable.  But expecting the market to change how it =
interprets our documents without us bothering to significantly change =
how we present them to the public - THAT would indeed be a serious =
disconnect from reality.

Keith


From jari.arkko@piuha.net  Wed Aug 31 08:46:49 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99E8821F8B59 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O3eXANMulz4I for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:46:49 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id CDA6421F8B4F for <ietf@ietf.org>; Wed, 31 Aug 2011 08:46:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F24D22D223; Wed, 31 Aug 2011 18:48:18 +0300 (EEST)
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 jlp06vzXJ2Ay; Wed, 31 Aug 2011 18:48:18 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 488FE2CE66; Wed, 31 Aug 2011 18:48:18 +0300 (EEST)
Message-ID: <4E5E57C1.3040503@piuha.net>
Date: Wed, 31 Aug 2011 18:48:17 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>,  Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com>
In-Reply-To: <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:46:49 -0000

Keith, Peter,

> I think you're overgeneralizing. My experience is that judicious use of SHOULD seems to make both protocols and protocol specifications simpler; trying to nail everything down makes them more complex.

I agree.

In any case, Peter, I think its fine to add the NOT RECOMMENDED word to the boilerplate. Publish a spec on that, have it Update 2119, and then new RFCs would refer to that (say, 7119) instead of 2119 and everyone would be happy.

But I'm not quite sure why there are other changes in the text. Maybe I need to be educated better. On quick read I got more questions from it than what I get from 2119...

Jari


From spencer@wonderhamster.org  Wed Aug 31 08:49:41 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23FC521F8C58 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.182
X-Spam-Level: 
X-Spam-Status: No, score=-102.182 tagged_above=-999 required=5 tests=[AWL=0.416, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id alHFsM8AldLf for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:49:40 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1EB21F8C4C for <ietf@ietf.org>; Wed, 31 Aug 2011 08:49:40 -0700 (PDT)
Received: from S73602b ([50.58.7.243]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MBVTq-1R5yrW2ZqI-00ApaA; Wed, 31 Aug 2011 11:51:08 -0400
Message-ID: <196934B4BA2F455086D224381B3E219C@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Keith Moore" <moore@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <EF3771F6968F4FBBADF419F0E8EFD2C6@china.huawei.com> <18C49016-D75F-4707-8EC4-0937EAE6C591@network-heretics.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
Date: Wed, 31 Aug 2011 10:51:04 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_2C54_01CC67CB.E15F8F60"
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.6109
X-Provags-ID: V02:K0:236TO/eaZc0wH8SA6gD5hNipC6xHndghg1u4Z8lfKJL Z05BnS7vCP9qAASLXcG0L4iyEJEWF5GKtEj3i4fQvso6qHvTjd X+HkWzI/D0Wlyqh/BWWFJt2GIYM4lK55RET7pu90nPL6B2Jpzg fJsSiqv2LUdQf2LEZvHmk5uFCgyW6mSCvcqgVFvB1YgKuxtsuR 8rkIs5lSRalyFgeKBMmm/sk7FX7csOmCwjv9hldzJ8CWbF8wmC mkdq1SQDWl6QfEG0XeFCe/zlcBPeTpf3PZUKzC+NptIdLxuHGR Em0zXO5FunTZuxe1mK9ADCYC6vboKdtkZadhfkS4SNiYIY+UhI +/vq+fyoC57Hz/T2Eq0VeSnrgGJHi6IcBX/lpIqiI
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:49:41 -0000

This is a multi-part message in MIME format.

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

Keith,

Yes, to what you are saying, but I was pointing out that the text we're =
discussing isn't intended to apply to moving what a working group has =
consensus for onto the standards track, it's intended to apply to what =
the *IETF* already has consensus for, that's already on the standards =
track, further along the standards track.

I think there's a higher bar, especially when a document is advancing =
unchanged, because I don't think there's any meaningful distinction =
between a widely deployed PS that could be improved, and advancing it to =
be a widely deployed IS that could be improved. I don't see the =
value-add from DISCUSSing the advancement, because the same document is =
sitting there as a proposed standard, and widely deployed.

If ADs look at a document proposed for advancement and see real and =
meaningful opportunities to improve the specification, I think it makes =
just as much sense to advance the document, as is, and start looking for =
people who will produce an improved version, as to slow down the =
document for DISCUSSion in the hope you end up with an improved =
document, that can then advance. Finding those people, and chartering =
that work, falls well within the "S" in IESG, AFAICT.

Thanks,

Spencer
  ----- Original Message -----=20
  From: Keith Moore=20
  To: Spencer Dawkins=20
  Cc: Jari Arkko ; IETF Discussion=20
  Sent: Wednesday, August 31, 2011 10:35 AM
  Subject: Re: Discuss criteria for documents that advance on the =
standards track


  thanks Spencer for pointing this part out.


  On Aug 31, 2011, at 11:23 AM, Spencer Dawkins wrote:


     IESG reviews should be considered as a review of "last resort".  =
Most
     documents reviewed by the IESG are produced and reviewed in the
     context of IETF working groups.  In those cases, the IESG cannot
     overrule working group consensus without good reason; informed
     community consensus should prevail.



  The idea that WG consensus should prevail is simply incorrect.  It =
biases IESG in an inappropriate way.


  There are a number of very good reasons for overriding WG consensus, =
e.g.


  - there is no evidence of broad community consensus or a clear lack of =
broad community consensus
  - the document does not meet the criteria specified in 2026 (or other =
document when applicable)
  - the document is ambiguous in such a way that it is likely to degrade =
interoperability


  The WG DOES NOT represent the entire community.    Far too often, WGs =
are deliberately chartered in such a way as to marginalize parts of the =
community


  Keith


------=_NextPart_000_2C54_01CC67CB.E15F8F60
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.19088">
<STYLE></STYLE>
</HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space"=20
bgColor=3D#ffffff>
<DIV><FONT size=3D2>Keith,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Yes, to what you are saying,&nbsp;but I was pointing =
out that=20
the text we're discussing isn't intended to apply to moving what a =
working group=20
has consensus for onto the standards track, it's intended to apply to =
what the=20
*IETF* already has consensus for, that's already on the standards track, =
further=20
along the standards track.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I think there's a higher bar, especially when a =
document is=20
advancing unchanged, because I don't think there's any meaningful =
distinction=20
between a widely deployed PS that could be improved, and advancing it to =
be a=20
widely deployed IS that could be improved. I don't see the value-add =
from=20
DISCUSSing the advancement, because the same document is sitting there =
as a=20
proposed standard, and widely deployed.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>If ADs look at a document proposed for advancement =
and see=20
real and meaningful opportunities to improve the specification, I think =
it makes=20
just as much sense to advance the document, as is, and start looking for =
people=20
who will produce an improved version, as to slow down the document for=20
DISCUSSion in the hope you end up with an improved document, that can =
then=20
advance. Finding those people, and chartering that work, falls well =
within the=20
"S" in IESG, AFAICT.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks,</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"=20
dir=3Dltr>
  <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=3Dmoore@network-heretics.com=20
  href=3D"mailto:moore@network-heretics.com">Keith Moore</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dspencer@wonderhamster.org=20
  href=3D"mailto:spencer@wonderhamster.org">Spencer Dawkins</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Djari.arkko@piuha.net=20
  href=3D"mailto:jari.arkko@piuha.net">Jari Arkko</A> ; <A =
title=3Dietf@ietf.org=20
  href=3D"mailto:ietf@ietf.org">IETF Discussion</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, August 31, =
2011 10:35=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: Discuss criteria =
for=20
  documents that advance on the standards track</DIV>
  <DIV><BR></DIV>thanks Spencer for pointing this part out.
  <DIV><BR>
  <DIV>
  <DIV>On Aug 31, 2011, at 11:23 AM, Spencer Dawkins wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <BLOCKQUOTE type=3D"cite"><SPAN=20
    style=3D"WIDOWS: 2; TEXT-TRANSFORM: none; TEXT-INDENT: 0px; =
BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: normal; =
ORPHANS: 2; LETTER-SPACING: normal; 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"=20
    class=3DApple-style-span>&nbsp;IESG reviews should be considered as =
a review=20
    of "last resort". &nbsp;Most<BR>&nbsp;documents reviewed by the IESG =
are=20
    produced and reviewed in the<BR>&nbsp;context of IETF working =
groups.=20
    &nbsp;In those cases, the IESG cannot<BR>&nbsp;overrule working =
group=20
    consensus without good reason; informed<BR>&nbsp;community consensus =
should=20
    prevail.<BR></SPAN></BLOCKQUOTE></DIV><BR></DIV>
  <DIV>The idea that WG consensus should prevail is simply incorrect. =
&nbsp;It=20
  biases IESG in an inappropriate way.</DIV>
  <DIV><BR></DIV>
  <DIV>There are a number of very good reasons for overriding WG =
consensus,=20
  e.g.</DIV>
  <DIV><BR></DIV>
  <DIV>- there is no evidence of broad community consensus or a clear =
lack of=20
  broad community consensus</DIV>
  <DIV>- the document does not meet the criteria specified in 2026 (or =
other=20
  document when applicable)</DIV>
  <DIV>- the document is ambiguous in such a way that it is likely to =
degrade=20
  interoperability</DIV>
  <DIV><BR></DIV>
  <DIV>The WG DOES NOT represent the entire community. &nbsp; &nbsp;Far =
too=20
  often, WGs are deliberately chartered in such a way as to marginalize =
parts of=20
  the community</DIV>
  <DIV>
  <DIV><BR></DIV></DIV>
  <DIV>Keith</DIV>
  <DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_2C54_01CC67CB.E15F8F60--


From stpeter@stpeter.im  Wed Aug 31 08:49:54 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB1A321F8C76 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HuxSgOZJWelK for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:49:54 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 42FAE21F8C72 for <ietf@ietf.org>; Wed, 31 Aug 2011 08:49:54 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9546B40E87; Wed, 31 Aug 2011 09:54:01 -0600 (MDT)
Message-ID: <4E5E587A.9040704@stpeter.im>
Date: Wed, 31 Aug 2011 09:51:22 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5E57C1.3040503@piuha.net>
In-Reply-To: <4E5E57C1.3040503@piuha.net>
X-Enigmail-Version: 1.3.1
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:49:55 -0000

On 8/31/11 9:48 AM, Jari Arkko wrote:
> Keith, Peter,
> 
>> I think you're overgeneralizing. My experience is that judicious use
>> of SHOULD seems to make both protocols and protocol specifications
>> simpler; trying to nail everything down makes them more complex.
> 
> I agree.
> 
> In any case, Peter, I think its fine to add the NOT RECOMMENDED word to
> the boilerplate. Publish a spec on that, have it Update 2119, and then
> new RFCs would refer to that (say, 7119) instead of 2119 

Yes, that is one path.

> and everyone
> would be happy.

I'm not sure that everyone would be happy, because I do think that some
clarifications and additional guidelines might be helpful. But those,
too, could go in a separate (likely Informational) document that would
not necessarily update (and certainly not obsolete) 2119.

> But I'm not quite sure why there are other changes in the text. Maybe I
> need to be educated better. On quick read I got more questions from it
> than what I get from 2119...

Thus the desirability of writing a separate document.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From moore@network-heretics.com  Wed Aug 31 08:50:57 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 735BF21F8C8B for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Level: 
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+NJX-JxCVD2 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:50:56 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id B72C621F8C72 for <ietf@ietf.org>; Wed, 31 Aug 2011 08:50:56 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3BA95210A8; Wed, 31 Aug 2011 11:52:27 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 11:52:27 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=6un AIyhuVNBeVxosS1VJG95SUJo=; b=WUz3p6+BZ+VwrmzpOepScxtLDCzSRi2IcMI Dn3aHiKHPGv6tCm9Gd3LndsEZk/j9Xz48llIjdpqsPMpNxA/wzVpnqNjONUFOvyD T9GnV+uHFMnN5vCmL4B8fBXJFiu//7eDJZ2MSSQVzCih/1Ci2AKGpzjIsq34qv4Z cDRX57sA=
X-Sasl-enc: PxcfPf5QuDNUaS8ZxSIsof8djRo82v+Wh4CvrvT8aJB3 1314805947
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 03AC8B215C0; Wed, 31 Aug 2011 11:52:27 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-76--656188748
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5E57C1.3040503@piuha.net>
Date: Wed, 31 Aug 2011 11:52:23 -0400
Message-Id: <70AD2744-55E0-4E54-B182-F96306C0B9F2@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5E57C1.3040503@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:50:57 -0000

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

or maybe just file an erratum.  I think it's fairly obvious that any =
document that actually uses NOT RECOMMENDED should define what it means, =
if it expects those words to have any meaning other than the ordinary =
English meaning of those words (with or without capitalization). =20

I've seen documents that didn't quote the 2119 boilerplate verbatim =
because they didn't use all of the terms defined in 2119.   I didn't see =
any problem with that.

On Aug 31, 2011, at 11:48 AM, Jari Arkko wrote:

> In any case, Peter, I think its fine to add the NOT RECOMMENDED word =
to the boilerplate. Publish a spec on that, have it Update 2119, and =
then new RFCs would refer to that (say, 7119) instead of 2119 and =
everyone would be happy.


--Apple-Mail-76--656188748
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; ">or =
maybe just file an erratum. &nbsp;I think it's fairly obvious that any =
document that actually uses NOT RECOMMENDED should define what it means, =
if it expects those words to have any meaning other than the ordinary =
English meaning of those words (with or without capitalization). =
&nbsp;<div><br></div><div>I've seen documents that didn't quote the 2119 =
boilerplate verbatim because they didn't use all of the terms defined in =
2119. &nbsp; I didn't see any problem with that.<div><br><div><div>On =
Aug 31, 2011, at 11:48 AM, Jari Arkko wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">In any case, =
Peter, I think its fine to add the NOT RECOMMENDED word to the =
boilerplate. Publish a spec on that, have it Update 2119, and then new =
RFCs would refer to that (say, 7119) instead of 2119 and everyone would =
be happy.<br></span></blockquote></div><br></div></div></body></html>=

--Apple-Mail-76--656188748--

From stpeter@stpeter.im  Wed Aug 31 08:52:32 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D478021F8C96 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11+-56J62z+o for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:52:32 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6802C21F8BCB for <ietf@ietf.org>; Wed, 31 Aug 2011 08:52:32 -0700 (PDT)
Received: from leavealone.cisco.com (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B804B417B6; Wed, 31 Aug 2011 09:56:39 -0600 (MDT)
Message-ID: <4E5E5919.80305@stpeter.im>
Date: Wed, 31 Aug 2011 09:54:01 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5E57C1.3040503@piuha.net> <70AD2744-55E0-4E54-B182-F96306C0B9F2@network-heretics.com>
In-Reply-To: <70AD2744-55E0-4E54-B182-F96306C0B9F2@network-heretics.com>
X-Enigmail-Version: 1.3.1
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:52:32 -0000

On 8/31/11 9:52 AM, Keith Moore wrote:
> or maybe just file an erratum.

There is an erratum on file:

http://www.rfc-editor.org/errata_search.php?eid=499

I started down this road in part while working to clear out errata...

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From sant9442@gmail.com  Wed Aug 31 08:53:31 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96E6221F8C88 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.953
X-Spam-Level: 
X-Spam-Status: No, score=-2.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7HmvIKKHpZAt for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 08:53:31 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id F337621F8BCB for <ietf@ietf.org>; Wed, 31 Aug 2011 08:53:30 -0700 (PDT)
Received: by gwb20 with SMTP id 20so218559gwb.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 08:54:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=WubqlV2q6z7TolsOJFY/dh06TPz+e/Ijzv6rAj3fjpc=; b=t6ZHP0V/0PT2RWFWieoYn7oGb/L4VmrDafS/cx4hfZjXWKF9i34+8u9o2BI2qJ73cl QQo8xGm841MHttETHu14TQRQn57g2C/UjT19xyV/vpzm+rzas6wOm918EYGfMymYkj2O a9LTJUPo4jIw3XKze9WnjuLuUaVmo+QwOeJr8=
Received: by 10.236.191.103 with SMTP id f67mr3057511yhn.93.1314806099384; Wed, 31 Aug 2011 08:54:59 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id q25sm2937320yhm.6.2011.08.31.08.54.57 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 08:54:58 -0700 (PDT)
Message-ID: <4E5E5982.9030809@gmail.com>
Date: Wed, 31 Aug 2011 11:55:46 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com>	<BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>	<4E5E2976.90102@gmail.com>	<B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>	<4E5E3353.4010503@gmail.com>	<2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com>	<4E5E3DC3.7080201@winserver.com> <BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com>
In-Reply-To: <BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 15:53:31 -0000

Keith Moore wrote:
> On Aug 31, 2011, at 9:57 AM, hector wrote:

>> Yeah, but its also very very useful to offering what parts of a protocol are 
>> on and off and let operators decide what they want. Don't we already do this?

> yes, it is done to some degree.  

Every protocol I have implemented such as PPP, RADIUS, SMTP, TELNET, 
FTP, POP3 among the augmented protocols all have some levels of 
"Features" presented as SHOULDs and MAYs and those seem necessary 
where exposed in some form of configuration options. They might be 
tweaked for optimal out of the box performance, so you might not need 
them.  Just look at SMTP extensions, EHLO features.  There are SHOULD 
for 5 mins timeouts and 5321 states that its good idea to make this 
configurable.  Came in handy the other day! :) or even DKIM. Protocol 
options made available, but fined tune so the operators just can start 
using it.  But not all will use the setting you prepare for them.

> but that's not, in general, a desirable practice. (though there are 
> cases where it can be justified).

While I agree long time engineering & fine tuning, options become 
stable, deprecated or obsolete and  short of an finely tuned embedded 
system, turnkey system, even smart phone/devices, and not really even 
then, I hardly seen any protocol with options not implement with some 
level of exposure deemed necessary.

> The simplest explanation is that people don't bother to read 2119.

How can you make a claim like this with a straight face or I guess 
fingers? That invites useless conflicts like "get a dictionary" for 
the word Recommended,  or just plain old accepting the simple idea 
that after determining all full implications above and beyond what was 
necessary is a valid reason to IGNORE the recommendation.

--
HLS


From moore@network-heretics.com  Wed Aug 31 09:01:19 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 076D821F86B6 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.594
X-Spam-Level: 
X-Spam-Status: No, score=-3.594 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnRIIFlLkVBF for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:01:18 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 588E921F86AF for <ietf@ietf.org>; Wed, 31 Aug 2011 09:01:18 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 292C621464; Wed, 31 Aug 2011 12:02:46 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 31 Aug 2011 12:02:46 -0400
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=vYjEQ/3AUWzRBXDWlUUJ1QhL2lk=; b=ZG 04oozAfsYusHkEUmbmj9puctpuzBenhaz7B1Sl4bxs3dkGyakZinyBBUQPjGorAI 2p9y09zeIFeFyBGOXx57rglevr73IF3QriWhmxyOaRJoCcbJC9WcfDgP1ib+uZyj YvCWkMY5DIdrh0jHwLU4PCm00IyJp+BZq8IYKQtqg=
X-Sasl-enc: 8PgCdjoN6VAqew2iR0m+mrGf53lvI/AEWHhgMsr/elbi 1314806565
Received: from [10.164.210.44] (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id DABCFB215E1; Wed, 31 Aug 2011 12:02:45 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5E5982.9030809@gmail.com>
Date: Wed, 31 Aug 2011 12:02:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com>	<BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>	<4E5E2976.90102@gmail.com>	<B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>	<4E5E3353.4010503@gmail.com>	<2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com>	<4E5E3DC3.7080201@winserver.com> <BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com> <4E5E5982.9030809@gmail.com>
To: Hector <sant9442@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 16:01:19 -0000

On Aug 31, 2011, at 11:55 AM, Hector wrote:

> Keith Moore wrote:
>> On Aug 31, 2011, at 9:57 AM, hector wrote:
>=20
>>> Yeah, but its also very very useful to offering what parts of a =
protocol are on and off and let operators decide what they want. Don't =
we already do this?
>=20
>> yes, it is done to some degree. =20
>=20
> Every protocol I have implemented such as PPP, RADIUS, SMTP, TELNET, =
FTP, POP3 among the augmented protocols all have some levels of =
"Features" presented as SHOULDs and MAYs and those seem necessary where =
exposed in some form of configuration options. They might be tweaked for =
optimal out of the box performance, so you might not need them.  Just =
look at SMTP extensions, EHLO features.  There are SHOULD for 5 mins =
timeouts and 5321 states that its good idea to make this configurable.  =
Came in handy the other day! :) or even DKIM. Protocol options made =
available, but fined tune so the operators just can start using it.  But =
not all will use the setting you prepare for them.

Old protocols that were extended after they were widely deployed are one =
of the exceptional cases where SHOULD / SHOULD NOT / etc. make sense to =
describe protocol features.   They can't always be MUSTs or MUST NOTs =
because of the need to maintain backward compatibility with old =
implementations.

Things like timeout intervals are often labeled as SHOULDs because they =
aren't precisely determined, they're educated guesses.  So implementors =
and perhaps operators should have some leeway to tweak them in light of =
experience.

>> The simplest explanation is that people don't bother to read 2119.
>=20
> How can you make a claim like this with a straight face or I guess =
fingers?

Because of long experience that indicates that implementors often fail =
to read base specifications thoroughly, much less the referenced =
specifications.

Keith


From john-ietf@jck.com  Wed Aug 31 09:17:54 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0DB221F8CD8 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08pWIgp7mNaX for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:17:54 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id C88AC21F8B4F for <ietf@ietf.org>; Wed, 31 Aug 2011 09:17:53 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QynVZ-000AU9-LF; Wed, 31 Aug 2011 12:19:22 -0400
Date: Wed, 31 Aug 2011 12:19:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Discuss criteria for documents that advance on the standards track
Message-ID: <4460DBAE246554491FD94FE1@PST.JCK.COM>
In-Reply-To: <AA800973-B00E-4624-BB16-FE1203D164E3@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.net> <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.com> <36352F5671DE5E04F6504860@PST.JCK.COM> <A9A04168-FBDC-44BC-9B35-6EBBB781CEBC@network-heretics.com> <D254EA76DCADA61E7C3BDEA2@PST.JCK.COM> <AA800973-B00E-4624-BB16-FE1203D164E3@network-heretics.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 Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 16:17:55 -0000

--On Wednesday, August 31, 2011 11:47 -0400 Keith Moore
<moore@network-heretics.com> wrote:

>...
>> IMO, there are two possibilities here.  At this point, sadly,
>> both involve a chicken-and-egg problem.  Such is life.
>> 
>> (1) We proceed as if Proposed Standards are what 2026 (and the
>> earlier culture) claims they are and work on ways to reinforce
>> that notion in the community. [...]
> 
>> (2) We accept, and effectively encourage, deployment of
>> proposed standards in products, either because it is a lost
>> cause or because we think it is a good idea.  [...]
> 
> Agree with your description of the two possibilities, but I
> think the decision of possibility 2 has long since been forced
> on us by market expectation and habit.
> 
> We could fix it, perhaps, by drastically changing how we label
> our products (dropping the whole notion of "Proposed
> Standard", refusing to publish your category 2 documents as
> RFCs, etc.).   But we can't significantly change market
> perception of what "RFC" and "Proposed Standard" mean.  

Whether we agree on how best to manage a perception change and
what it takes, I agree that there is no single magic bullet,
much less a painless one.   I would turn your comment around
slightly and say that a change in names is likely to have little
or no effect on perceptions unless we actually change what we
do.   As I said in and earlier note, there is something of a
chicken-and-egg problem here.
 
> while probably Mostly Harmless, won't do a bit of good in the
> overall scheme of things)

For reasons I've explained in previous notes, I don't think
procedural changes, especially from "not followed and doesn't
work but ancient" or "contemporary and [still] doesn't work or
reflect reality, are harmless ("mostly" or otherwise).

>> Remember that, while ignoring procedures and category
>> definitions that we don't follow is not desirable, "fixing"
>> them to reflect a model that doesn't (and won't) exist either
>> is a public demonstration that we are disconnected from
>> reality.  I'd much rather leave that distinction to some
>> other SDOs than join them.  YMMD.
> 
> And my assertion is that the model inherent in your
> possibility #1 above doesn't exist and won't exist absent from
> drastic change.   Insisting on high quality for proposed
> standards is recognizing current market reality.

If you are right, then fussing around with how many maturity
levels we have, what criteria we claim we are using, and even
how we name things, are dangerous as well as a waste of time and
resources.  That is where we are maybe in violent agreement --
we either ought to be identifying real problems and fixing them
or just staying with what we have until we have the knowledge
and will needed to make real changes.  In that regard, I applaud
one aspect of Jari's note, which is that it affects and IETF
administrative procedure and not a fundamental (and unnecessary)
procedural change.

By contrast, suppose draft-housley-two-maturity-levels were just
shelved for a while and replaced by an announcement by an AD or
two (ideally from areas that have really low advancement rates
even as compared to the already-low IETF average) that they
intended to

	(i) accept a public assertion of interoperability as an
	implementation report, issue an IETF LC for DS to see if
	anyone with real experience with the protocol objects
	loudly, and then move to advance the document, and 
	
	(ii) that they would construe the passage of the
	relevant number of month and public claims of deployment
	as sufficient incentive to issue an IETF LC for
	advancement to IS.

If the rest of the IESG were willing to go along with that, we'd
have a real experiment without permanent changes to the official
procedures.  People who saw a problem advancing a particular
protocol or document could object and it would presumably work
only for PS documents that were of high quality.  If it worked
out, we would have a basis for coming back and evaluating
whether there really was enough of a difference between DS and
IS to be worth the trouble and whether the practical differences
between that sort of implementation report and today's
interpretation of what is required was.  And then we could take
...two-maturity-levels back up with some confidence about both
utility and potential harm.

And, if you are right and this is all hopeless without really
major changes, then that experiment might give us the
information needed to finally come to grips with that and either
make the major change or accept the status quo and stop spending
energy trying to turn the knobs a degree or two.

> And I'm not one of those people who believes that market
> perceptions are inherently unchangeable.  But expecting the
> market to change how it interprets our documents without us
> bothering to significantly change how we present them to the
> public - THAT would indeed be a serious disconnect from
> reality.

I actually agree.

    john


From moore@network-heretics.com  Wed Aug 31 09:23:40 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDCED21F8D04 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Level: 
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4P4zR15cG1vw for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:23:40 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 175E421F8D03 for <ietf@ietf.org>; Wed, 31 Aug 2011 09:23:40 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 9B91322B01; Wed, 31 Aug 2011 12:25:10 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Wed, 31 Aug 2011 12:25:10 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=2Ym DUvhOJqzK/hS2cxIJjsWMCog=; b=cfBPK8SlWItMh2HDLBynz9HwAnoTVBeP0+5 4Nn4xDBXLm25YZkPsMoWQLecTMgg9ZXQljBgnddliqjvR2tkjsL2UPKoJgY8pzwH UbyzoyUE8iu2hMDzaTxcHydFF+eHOzzecc8wkmwZNLNN5KFaddt5kziz8y3pvgnu Qry5/Vmc=
X-Sasl-enc: jEm1xcm1yI+C1Z9/MhI4cTP4MV7FRFipYp0c8OEBr7dl 1314807910
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 551D3B215F6; Wed, 31 Aug 2011 12:25:10 -0400 (EDT)
Subject: Re: Discuss criteria for documents that advance on the standards track
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-78--654223749
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4460DBAE246554491FD94FE1@PST.JCK.COM>
Date: Wed, 31 Aug 2011 12:25:08 -0400
Message-Id: <99A6ED33-BD6B-4B6B-B229-CEE09A1A05C4@network-heretics.com>
References: <4E5D45B1.50107@piuha.net> <DB2BC72F-6022-4216-B228-E6500FA98524@network-heretics.com> <E9BE6BFC-ABA4-402C-AF77-EB0497E949CC@cisco.com> <65AB1B585CF6B912684ECB00@PST.JCK.COM> <C8899A19-74B4-4ECA-BD04-A28057958E43@standardstrack.com> <4E5DF1FB.2020306@piuha.net> <F7EFBF3F-C423-4096-8A9F-100ECE5CCE9B@network-heretics.com> <36352F5671DE5E04F6504860@PST.JCK.COM> <A9A04168-FBDC-44BC-9B35-6EBBB781CEBC@network-heretics.com> <D254EA76DCADA61E7C3BDEA2@PST.JCK.COM> <AA800973-B00E-4624-BB16-FE1203D164E3@network-heretics.com> <4460DBAE246554491FD94FE1@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 16:23:41 -0000

--Apple-Mail-78--654223749
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Aug 31, 2011, at 12:19 PM, John C Klensin wrote:

> we either ought to be identifying real problems and fixing them
> or just staying with what we have until we have the knowledge
> and will needed to make real changes.

That would certainly be my preference.

Keith


--Apple-Mail-78--654223749
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><div>On Aug 31, 2011, at 12:19 PM, John C Klensin wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">we either =
ought to be identifying real problems and fixing them<br>or just staying =
with what we have until we have the knowledge<br>and will needed to make =
real changes.</span></blockquote></div><br><div>That would certainly be =
my =
preference.</div><div><br></div><div>Keith</div><div><br></div></body></ht=
ml>=

--Apple-Mail-78--654223749--

From evnikita2@gmail.com  Wed Aug 31 09:25:29 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F32421F8D1E for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level: 
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HHGlAEWfD2nD for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:25:28 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6D14421F8D19 for <ietf@ietf.org>; Wed, 31 Aug 2011 09:25:28 -0700 (PDT)
Received: by bkar4 with SMTP id r4so1217432bka.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 09:26:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2eLKUykCG1d7+TdC8m4jOFCMnkfOzI0VLtpH56FMYuE=; b=M7TZQ6c7rCjsBqAvo7oSjNnEYi1qKZw4faP5P5dLcb2/KAvvevkr5a9DllmMI441u8 DN7JT0xcFqMaTAH/Sc6jeHzSqbW7fafsWMU0nCd1igb5bxNjxolSWcx0FbhEVY55CsCl FOwxDJCrX++uuOGzhAvzY0chh/XuplrvFzd6g=
Received: by 10.204.143.77 with SMTP id t13mr373910bku.120.1314808018385; Wed, 31 Aug 2011 09:26:58 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id m18sm437147bkt.18.2011.08.31.09.26.57 (version=SSLv3 cipher=OTHER); Wed, 31 Aug 2011 09:26:57 -0700 (PDT)
Message-ID: <4E5E60F1.9010209@gmail.com>
Date: Wed, 31 Aug 2011 19:27:29 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: non-2119
References: <20110831132855.D47F3EAC648@newdev.eecs.harvard.edu> <4E5E4ED4.5080702@att.com>
In-Reply-To: <4E5E4ED4.5080702@att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 16:25:29 -0000

Isn't it already incorporated in Section 3 of 2119bis:

>     When it is not appropriate to use the conformance terms, authors can
>     use a variety of alternative words and phrases, such as: "need to" or
>     "mandatory" instead of "MUST"; "ought to" or "strongly encouraged"
>     instead of "SHOULD"; and "might" or "discretionary" instead of "MAY".
>     To prevent confusion, authors ought to use these alternative words
>     and phrases instead of the lowercase versions of the conformance
>     terms, and to use the conformance terms only in their uppercase
>     versions.

Mykyta

31.08.2011 18:10, Tony Hansen wrote:
> While 2119 is being discussed, I thought I'd mention a small I-D that 
> Dave Crocker and I wrote on terminology that might be used in places 
> where 2119 ought not apply. It's
>
>     Non-Normative Synonyms in RFCs
>     http://tools.ietf.org/html/draft-hansen-nonkeywords-non2119-01
>
> Thoughts on this draft would be appreciated as well.
>
>     Tony Hansen
>     tony@att.com
>
> On 8/31/2011 9:28 AM, Scott O. Bradner wrote:
>> I've been traveling so have not had a chance to do anything but watch
>> the discussion on a RFC 2119 update.
>>
>> a few thoughts
>>
>> 1/ I am far from convinced that there is a need to update RFC 2119
>>        there is a bug in the boilerplate (as has been mentioned)
>>        and some people seem to have a hard time understanding what
>>        (to me) seem like clear descriptions of (for example) MUST&
>>        SHOULD - but the issues do not seem serious enough to warrant
>>        replacing what is, basically, a simple dictionary&  usage
>>        constraint
>>
>> 2/ it seems like a very Bad Idea to move 2119 to historic- we move
>>       RFCs to historic when no one uses them or when they are a Bad
>>       Idea in light of updated technology - I do not think that makes
>>       much sense in this case - in addition it makes the status of RFCs
>>       that have a normative reference to a historic document a bit
>>       funky - if an update is actually needed there is no reason that
>>       I can come up with that it could not just be that -- an update
>>
>> 3/ I doubt that I'll ever catch up with Postel as the most referenced
>>       RFC author so that is not a consideration (for me)
>>
>> I wrote RFC 2119 (most using text from RFC 1122) because people were
>> using MUST without saying what they meant, an update, if people think
>> that one is actually needed, will serve that purpose as well as 2119 
>> has.
>>
>> When I posted the original ID it was pointed out that I should also
>> address when such terms should be used (i.e. try to limit the use to
>> where it actually made sense protocol-wise) - I tried to do that but
>> that part may not have been as successful as it might have been - any
>> update might try to be clearer in this area that RFC 2119 is.
>>
>> 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 hsantos@santronics.com  Tue Aug 30 21:07:26 2011
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E7721F8C51 for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 21:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.944
X-Spam-Level: 
X-Spam-Status: No, score=-1.944 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, J_CHICKENPOX_46=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pdW+oBHyJ+uZ for <ietf@ietfa.amsl.com>; Tue, 30 Aug 2011 21:07:25 -0700 (PDT)
Received: from mail.winserver.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5122E21F8C50 for <ietf@ietf.org>; Tue, 30 Aug 2011 21:07:24 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2921; t=1314763726; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=VVOmfDw u7acFfgITUPXT0XTYR48=; b=QgsdYt5kOs02kbWxbpxPimODN1FcHOQr+eO0geT e2sIIlvov4CCBlUmaGyxrIcnYPq2X7CEt/a83roTIFcosvTZ/a/3PtqhpYG/socN NoL5iKPGhPbxERU1aypyR5NzgG+3PGv5BVtjVMTgQIPPSdFJnh1OHQb7HSDdjkMO jtS4=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 31 Aug 2011 00:08:46 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3219147934.47382.2852; Wed, 31 Aug 2011 00:08:10 -0400
Message-ID: <4E5DB3CD.4070109@santronics.com>
Date: Wed, 31 Aug 2011 00:08:45 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: 2119bis - SHOULD Classifications
References: <4E5C067A.9080400@stpeter.im>	<4E5C34DD.2010905@santronics.com> <CAC4RtVCw=0vkYeBDgRudKYsNqL5WY1_uH+Q_X+kGZq-TM6duug@mail.gmail.com>
In-Reply-To: <CAC4RtVCw=0vkYeBDgRudKYsNqL5WY1_uH+Q_X+kGZq-TM6duug@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Wed, 31 Aug 2011 09:30:47 -0700
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 04:07:26 -0000

Barry Leiba wrote:
> Just responding to a small part, here:
> 
>> ï¿½ B) RFC2119 states SHOULD is the same as the adjective "RECOMMENDED."
>>
>> As far I am concern, a recommendation is not a mandate nor obligation.
>
> ..
> 
> But don't make the mistake of thinking that, in the context of RFC
> 2119, one can use one's own English sense of what the meanings of
> these terms are.

Agree, that is why the final part of my email I suggested the 
consideration to remove the last sentence of the text be removed;  The 
term "RECOMMENDED" is equivalent to "SHOULD".

Personally, it benefit us if we state SHOULD under different 
classifications. I'm just winging it, but perhaps:

      NEW ITEM
      IMPROVEMENT
      SECURITY (VERY IMPORTANT)

A context of which the SHOULD offers has a lot of weight in the 
decision making process.

Example:

  If the SHOULD is related to security,
  then all efforts MUST be to made to support it.

  If the SHOULD item is an improvement not related to security,
  then all efforts SHOULD be to made to support it.

  If the SHOULD item is a new item not related to security,
  then all efforts MAY be to made to support it.

Of course, there is the interesting nature of recursion here and the 
last two can possibly be folded, but I think stating SHOULD compliance 
classified under new, improvement and the level of importance context 
will help rather than trying to state it as a generalize, ambiguous 
rule of thumb - "A MUST BUT OPTIONAL IFF YOU KNOW WHAT YOU ARE DOING."

The basic idea is that when is something is NEW there is lesser 
obligation to support it until its becomes widely adopted. If its 
really an important feature, like security, then it ought to be stated 
with a heavy obligatory emphasis.

Also, we may consider other general guidelines text like:

     New protocol enhancements with SHOULD key words MUST NOT be used 
a non-compliance
     measurement tool of existing compliant implementations. i.e. 
current implementator
     are not "broken" because they are not currently supporting a SHOULD.

     A new protocol that has a OPTIONAL dependency on an existing 
optional protocol
     MUST NOT use MUST|SHOULD as an enforcement tool for make 
implementator to
     support the optional protocol.

The last one I had trouble writing it, but I think you get the gist of it.

Overall, I believe the "system" has worked - we got this far because 
we gave implementators the benefit of the doubt that valid reasons to 
ignore was done responsibly and the protocols still worked.

The problem, in my view, has been an agenda of enforcing protocol 
behavior from a "Throw the book" non-compliance mindset, worst when 
dealing with integrated of optional protocols, yet not equally 
applied. e.g., "I don't wish to honor that other protocol SHOULD but 
you MUST follow my protocol SHOULD."

-- 
Sincerely

Hector Santos
http://www.santronics.com




From mcr@sandelman.ca  Wed Aug 31 09:49:14 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0630E21F8D82 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.591
X-Spam-Level: 
X-Spam-Status: No, score=-1.591 tagged_above=-999 required=5 tests=[AWL=0.363,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCh0135AS6-d for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 09:49:13 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 3549621F8D74 for <ietf@ietf.org>; Wed, 31 Aug 2011 09:49:06 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 7FBB8A0067 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:49:54 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 91CA598C76 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:51:03 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
In-Reply-To: <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Wed, 31 Aug 2011 12:51:03 -0400
Message-ID: <31453.1314809463@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 16:49:14 -0000

>>>>> "Keith" == Keith Moore <moore@network-heretics.com> writes:
    >> In my view, SHOULD are user protocol options to set.

    Keith> In my view, SHOULD should rarely be used for optional
    Keith> protocol features, because optional protocol features should
    Keith> themselves be rare.  And the primary purpose of SHOULD is not
    Keith> to permit optional protocol features.

Let me give an example of where I think SHOULD is useful:
    a TLS end-point SHOULD verify the received certificate against
    a trusted anchor.

Removing this requirement in SMTP-TLS has meant that we now have
opportunistically encrypted email transmission.  It makes sense for the
TLS library to have this option.   

In a web browser, the same SHOULD is much more controversial.

Some TLS libraries have this as a MUST, and there is all sorts of
trouble for people implementing other protocols or authentication
mechanisms over TLS.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From jari.arkko@piuha.net  Wed Aug 31 10:16:02 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFA6821F8E0D for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kO05ysyidcjC for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:16:02 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id CCABB21F8E0F for <ietf@ietf.org>; Wed, 31 Aug 2011 10:16:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2645F2D223; Wed, 31 Aug 2011 20:17:30 +0300 (EEST)
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 2Umz9mMypoJc; Wed, 31 Aug 2011 20:17:29 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 72EC52CE66; Wed, 31 Aug 2011 20:17:29 +0300 (EEST)
Message-ID: <4E5E6CA9.4060506@piuha.net>
Date: Wed, 31 Aug 2011 20:17:29 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<81FDA04B-013E-4B91-8C60-460E50D23B36@network-heretics.com>	<093D5F51-B800-4DFC-A8BE-37F0230BA742@standardstrack.com> <91F87138-50D7-4C44-B682-759CD74E8303@network-heretics.com> <4E5E57C1.3040503@piuha.net> <70AD2744-55E0-4E54-B182-F96306C0B9F2@network-heretics.com> <4E5E5919.80305@stpeter.im>
In-Reply-To: <4E5E5919.80305@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 17:16:03 -0000

I think we should update our RFCs when there's a generally accepted errata. I mean, I know about errata. I browse IETF docs through tools.ietf.org and they show me the errata links. But... shame on me... I don't click through those links often enough. I suspect I'd miss a few even if I was implementing something. Its far better if the entire document is up to date. I suspect this holds for other at least some other people, too.

Jari

On 31.08.2011 18:54, Peter Saint-Andre wrote:
> On 8/31/11 9:52 AM, Keith Moore wrote:
>> or maybe just file an erratum.
>


From msk@cloudmark.com  Wed Aug 31 10:32:56 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB01521F8E05 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.519
X-Spam-Level: 
X-Spam-Status: No, score=-104.519 tagged_above=-999 required=5 tests=[AWL=1.080, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b0ZgfHKR5an0 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:32:56 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 367FA21F8E00 for <ietf@ietf.org>; Wed, 31 Aug 2011 10:32:56 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Wed, 31 Aug 2011 10:34:27 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Wed, 31 Aug 2011 10:34:26 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: Acxn93RjKSDIEQoMSreeP7WmBWWZdQACm/4Q
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com> <4E5E3353.4010503@gmail.com> <2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com> <4E5E3DC3.7080201@winserver.com> <BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com> <4E5E5982.9030809@gmail.com> <478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com>
In-Reply-To: <478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 17:32:56 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of K=
eith Moore
> Sent: Wednesday, August 31, 2011 9:03 AM
> To: Hector
> Cc: IETF discussion list
> Subject: Re: 2119bis
>=20
> Because of long experience that indicates that implementors often fail
> to read base specifications thoroughly, much less the referenced
> specifications.

I absolutely agree, and also with your earlier point that a lot of people a=
pparently either don't bother to read RFC2119 at all, or (in my experience)=
 read it selectively.

If there is an RFC2119bis, I would like to see it illustrate the cases wher=
e a MUST would be preferred over a SHOULD, and vice-versa, such that the im=
plications to both the spec author and the reader are clarified.  It alread=
y seems to start down that road, which is fine.  But I don't think there's =
anything wrong with the definitions as we have them; I think they've served=
 us well for the last fourteen years.

I don't agree at all with the interpretation of SHOULD as an optional proto=
col feature in all cases.  RFC2119 makes it clear what SHOULD and RECOMMEND=
ED mean beyond the dictionary definition.  They are not an invitation to di=
sregard those requirements merely because they are hard to implement or wou=
ld confuse end users if exposed.  It seems clear to me that SHOULD is the s=
ame as "MUST... UNLESS", and the "unless" part has to be carefully consider=
ed in terms of how interoperability will be affected, not how your source c=
ode or user interface will become more complicated.

It's certainly the case that there are some documents that got use of SHOUL=
D wrong, but that doesn't mean RFC2119 is broken.

From sant9442@gmail.com  Wed Aug 31 10:54:44 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5814221F8E59 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.738
X-Spam-Level: 
X-Spam-Status: No, score=-2.738 tagged_above=-999 required=5 tests=[AWL=-0.431, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yntwC7HhSaX for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:54:44 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id E11D621F8E58 for <ietf@ietf.org>; Wed, 31 Aug 2011 10:54:43 -0700 (PDT)
Received: by gyf3 with SMTP id 3so942914gyf.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 10:56:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ARhEKMI6EFl3inNbsdj2fmXX0BoIBFhifEnOsbKHjnI=; b=gYGqq2Afbf1hlSTDEfUF0ID68tvQR0IQf1/XFpTKHlLKb5lfrL1hAOFeyvyYGoSPvu OhGuUULGal51DkI7fcdvVv71AJe8YA9n9meGgC+DTnEGABc9OB0wsPNm7sUDYzhLeQuk 5bCEELbctpHRLcrkDOzk/uNcls+4zRpaKGdyY=
Received: by 10.236.178.10 with SMTP id e10mr3997986yhm.31.1314813374571; Wed, 31 Aug 2011 10:56:14 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id j45sm181083yhe.36.2011.08.31.10.56.13 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 10:56:14 -0700 (PDT)
Message-ID: <4E5E75EE.8050002@gmail.com>
Date: Wed, 31 Aug 2011 13:57:02 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com>	<BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com>	<4E5E2976.90102@gmail.com>	<B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com>	<4E5E3353.4010503@gmail.com>	<2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com>	<4E5E3DC3.7080201@winserver.com>	<BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com>	<4E5E5982.9030809@gmail.com>	<478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com> <F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 17:54:44 -0000

Murray S. Kucherawy wrote:
>> -----Original Message-----

> But I don't think there's anything wrong with the definitions as we have them; 
> I think they've served us well for the last fourteen years.

Correct and by far, most deployments have use SHOULD = OPTION with an 
documented right to IGNORE - so be it written so be it followed.  The 
"MUST-IMPLEMENT seems to be an exception and not the rule and even 
then is inconsistency in application seem to be very selective.

Maybe Tony's I-D can help reinforce this concept of a Recommendation:

    SHOULD, RECOMMENDED:  The words "ought", "encouraged" and "suggest
          strongly" can be used to connote something that is strongly
          urged.

and I hope these terms still don't means "MUST-IMPLEMENT" and worst a 
"MUST-USE" by the operator.

From msk@cloudmark.com  Wed Aug 31 10:58:50 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E130921F8E78 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.525
X-Spam-Level: 
X-Spam-Status: No, score=-103.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4oe4lU3uxg1S for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 10:58:50 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 21E8721F8E7E for <ietf@ietf.org>; Wed, 31 Aug 2011 10:58:50 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Wed, 31 Aug 2011 11:00:21 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Wed, 31 Aug 2011 11:00:20 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxoB0vtpfpC1RonTayq0SEYZ+2ivQAABy3Q
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com> <4E5E3353.4010503@gmail.com> <2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com> <4E5E3DC3.7080201@winserver.com> <BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com> <4E5E5982.9030809@gmail.com> <478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com> <F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com> <4E5E75EE.8050002@gmail.com>
In-Reply-To: <4E5E75EE.8050002@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 17:58:51 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of H=
ector
> Sent: Wednesday, August 31, 2011 10:57 AM
> Cc: IETF discussion list
> Subject: Re: 2119bis
>=20
> > But I don't think there's anything wrong with the definitions as we hav=
e them;
> > I think they've served us well for the last fourteen years.
>=20
> Correct and by far, most deployments have use SHOULD =3D OPTION with an
> documented right to IGNORE - so be it written so be it followed.

This sentence is self-contradictory.  "SHOULD" is, by definition, not "OPTI=
ONAL".

From christer.holmberg@ericsson.com  Wed Aug 31 11:04:13 2011
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5AB21F8E8A for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 11:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level: 
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 84d3xomh9f0s for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 11:04:12 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 221EE21F8E6C for <ietf@ietf.org>; Wed, 31 Aug 2011 11:04:11 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-06-4e5e77f64cac
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 24.6D.20773.6F77E5E4; Wed, 31 Aug 2011 20:05:42 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.250]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Wed, 31 Aug 2011 20:05:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ole Jacobsen <ole@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Date: Wed, 31 Aug 2011 20:05:41 +0200
Subject: RE: Hyatt Taipei cancellation policy?
Thread-Topic: Hyatt Taipei cancellation policy?
Thread-Index: AcxnXBxx3iGVjZXPT5arTM5RBBT9NgATJ5DA
Message-ID: <96F825286CEAFC40B37C080D4284A44F1947E33E6A@ESESSCMS0356.eemea.ericsson.se>
References: <20110822191708.652C721F8C19@ietfa.amsl.com> <801FB726-F672-4F7F-8D9C-7ED37DB08672@cs.ucla.edu> <FE5EB7C9-C395-4B98-A0D4-8B2320F78C04@isoc.org> <66998320DD3FCC5628E32634@PST.JCK.COM> <BD20F48A-E30F-49BB-86BB-90CEB20A67F2@lucidvision.com> <BF38F8D23E8D794ED9DBD7B5@PST.JCK.COM> <4E5D4144.1010700@softarmor.com> <alpine.OSX.2.01.1108301422160.95146@sjc-vpn6-1246.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1108301422160.95146@sjc-vpn6-1246.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 18:04:13 -0000

Hi,

Also note that, according to Google maps, it is possible to take a bus from=
 the overflow hotel to the meeting. It requires a 400 meters walk from the =
hotel to the bus stop, but that should be managble even for an IETF attende=
e...=20

The total travel (walking+bus) is 13 minutes.

Regards,

Christer


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
> Behalf Of Ole Jacobsen
> Sent: 31. elokuuta 2011 0:31
> To: Dean Willis
> Cc: ietf@ietf.org
> Subject: Re: Hyatt Taipei cancellation policy?
>=20
>=20
> Dean,
>=20
> Before you give up completely I would check out:
>=20
> http://wikitravel.org/en/Taipei
>=20
> Taxis are not expensive, the Metro even less so, and there=20
> are at least some budget hotels nearby. I expect the local=20
> hosts to provide more information soon -- they already have=20
> some info on the website.
>=20
> I agree about the Hyatt hotel price.
>=20
> Ole
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20
> On Tue, 30 Aug 2011, Dean Willis wrote:
>=20
> > On 8/23/11 9:24 AM, John C Klensin wrote:
> > >
> > > So I'm opposed to a USD 200 (or any other number) firm limit on=20
> > > hotel rates.  At the same time, I continue to wish that the IAOC=20
> > > would be more open with the community about how these=20
> decisions are=20
> > > made and, in particular, how the tradeoffs between=20
> sponsorship (and=20
> > > hence lower costs to the IETF for meeting infrastructure and=20
> > > arrangements) and meetings costs to attendees are made... open=20
> > > enough that the community could give substantive guidance on the=20
> > > subject, guidance that I assume the IAOC would follow if it were=20
> > > coherent and plausible.
> > >
> >=20
> > Quite right. There's more than just the hotel rates.
> >=20
> > My budget is about $2500 US per IETF meeting. That has to cover=20
> > airfare, the IETF meeting fee, the hotel, meals, service charges,=20
> > ground transport, mobile phone roaming, incidentals, etc.
> >=20
> > $300 a night counting taxes and surcharge is just ABSOLUTELY OUT OF=20
> > THE FREAKING QUESTION. Having the "backup" hotel a 10=20
> minute taxi ride=20
> > away is out of the question -- I can't afford taxis. If I=20
> can't walk, I can't go.
> >=20
> > So guess what? I told the wife last night that I wasn't=20
> planning to go=20
> > to the Taiwan meeting. I wanted to go, but I just don't see=20
> how it can=20
> > happen. Maybe I'll win the lottery between now and then...
> >=20
> > I'm disappointed. I'm hurt. I'm angry. And the trend has just been=20
> > getting worse and worse with every venue. I want the IAOC's=20
> heads on a=20
> > platter (preferably an inexpensive, disposable platter,=20
> like maybe the=20
> > lid off an old pizza box) for signing us up to this venue.=20
> And I want=20
> > a travel budget no larger than mine for the people we send=20
> to future meetings.
> >=20
> > If we can't find a reasonably inexpensive place to have a meeting,=20
> > DON'T HAVE THE MEETING!
> >=20
> >=20
> > --
> > Dean Willis
> > _______________________________________________
> > 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 randy_presuhn@mindspring.com  Wed Aug 31 11:29:22 2011
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4851C21F8DC2 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 11:29:22 -0700 (PDT)
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.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rmzeqiWT4H2u for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 11:29:21 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id AC6FB21F8DBE for <ietf@ietf.org>; Wed, 31 Aug 2011 11:29:21 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=ZWft3U3kk73mDYLE4+b6o297HUOsQoTUnPdgWMFU5/L2uxBOg2RqPxqmh9mYZzec; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.30.227.232] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QypYo-0008Kg-74 for ietf@ietf.org; Wed, 31 Aug 2011 14:30:50 -0400
Message-ID: <004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF discussion list" <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im><201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com><41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com><003401cc66b1$d35af5a0$6801a8c0@oemcomputer><01O5FL6TFAY8014O5Z@mauve.mrochek.com><5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>
Subject: Re: 2119bis
Date: Wed, 31 Aug 2011 11:30:52 -0700
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8887f779e183b2ee288456cce770269f086caef6ab1197a3e35350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.227.232
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 18:29:22 -0000

Hi -

> From: "Murray S. Kucherawy" <msk@cloudmark.com>
> To: "IETF discussion list" <ietf@ietf.org>
> Sent: Wednesday, August 31, 2011 11:00 AM
> Subject: RE: 2119bis
>
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Hector
> > Sent: Wednesday, August 31, 2011 10:57 AM
> > Cc: IETF discussion list
> > Subject: Re: 2119bis
> > 
> > > But I don't think there's anything wrong with the definitions as we have them;
> > > I think they've served us well for the last fourteen years.
> > 
> > Correct and by far, most deployments have use SHOULD = OPTION with an
> > documented right to IGNORE - so be it written so be it followed.
> 
> This sentence is self-contradictory.  "SHOULD" is, by definition, not "OPTIONAL".

I disagree with the claim that there is a contradiction there, but I also think
"IGNORE" is incorrect.

The only difference between "SHOULD" and "MAY" is that the implementor /
deployer needs a good excuse to not implement / employ a "SHOULD."
That's not the same as "IGNORE".

However, looking at an implementation from a conformance testing perspective,
these are indistinguishable.  If the conditions under which the feature may
be omitted are well-defined, then an "if not x MUST y" structure would be
much more appropriate, and this can be easily handled with the existing
keywords.

Randy


From msk@cloudmark.com  Wed Aug 31 11:37:53 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9952D21F8DFC for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 11:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.523
X-Spam-Level: 
X-Spam-Status: No, score=-103.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-Ak1jmlc+7Q for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 11:37:53 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 31CA721F8DF6 for <ietf@ietf.org>; Wed, 31 Aug 2011 11:37:53 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Wed, 31 Aug 2011 11:39:20 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Wed, 31 Aug 2011 11:39:19 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxoDCYPUZucCggwT0WLTw1D9uxVfQAANKUQ
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im><201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com><41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com><003401cc66b1$d35af5a0$6801a8c0@oemcomputer><01O5FL6TFAY8014O5Z@mauve.mrochek.com><5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com> <004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>
In-Reply-To: <004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 18:37:53 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of R=
andy Presuhn
> Sent: Wednesday, August 31, 2011 11:31 AM
> To: IETF discussion list
> Subject: Re: 2119bis
>=20
> > This sentence is self-contradictory.  "SHOULD" is, by definition, not "=
OPTIONAL".
>=20
> I disagree with the claim that there is a contradiction there, but I also=
 think
> "IGNORE" is incorrect.

What was said is "SHOULD =3D OPTION", but RFC2119 says "OPTIONAL" is the sa=
me as "MAY".  That's the contradiction.

> The only difference between "SHOULD" and "MAY" is that the implementor /
> deployer needs a good excuse to not implement / employ a "SHOULD."
> That's not the same as "IGNORE".

But that's a big difference.  I think some people are being cavalier about =
the "good excuse" part, and that's where I have a problem.  RFC2119 is not =
unclear on this point.


From sant9442@gmail.com  Wed Aug 31 12:05:11 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB6C21F8EE6 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.63
X-Spam-Level: 
X-Spam-Status: No, score=-2.63 tagged_above=-999 required=5 tests=[AWL=-0.323,  BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46gMnSx8C9Gr for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:05:10 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id C128E21F8EBD for <ietf@ietf.org>; Wed, 31 Aug 2011 12:05:10 -0700 (PDT)
Received: by ywe9 with SMTP id 9so1041516ywe.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:06:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=MNqf2QZ2IraTeN/dFWtODaxha87MDrnfOWOxXP5OkPA=; b=YlKqcEtLRcXdc9YATwiX7C5he1+6MUUIXpdHFjIVJ3eHf2mAUFTBTR5fJn9PkF0xnu 6E+SMuZ42QlJEeiH+O4oM+hGEsYrTMrs0pxoKb57vPizscGH6aWdn/2WbLiDbMGXubR5 sREtWnT1wgz3BhGaR2tZZBe0OLEifH45DkOEA=
Received: by 10.236.178.10 with SMTP id e10mr4448165yhm.31.1314817601307; Wed, 31 Aug 2011 12:06:41 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id f4sm1122004yhn.69.2011.08.31.12.06.40 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 12:06:40 -0700 (PDT)
Message-ID: <4E5E8670.6090308@gmail.com>
Date: Wed, 31 Aug 2011 15:07:28 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><003401cc66b1$d35af5a0$6801a8c0@oemcomputer><01O5FL6TFAY8014O5Z@mauve.mrochek.com><5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark. com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:05:11 -0000

Murray S. Kucherawy wrote:

>> The only difference between "SHOULD" and "MAY" is that the implementor /
>> deployer needs a good excuse to not implement / employ a "SHOULD."
>> That's not the same as "IGNORE".
> 
> But that's a big difference.  I think some people are being cavalier 
> about the "good excuse" part, and that's where I have a problem.  
> RFC2119 is not unclear on this point.

Correct again, it is not unclear.  It says it very clear.  I don't 
know why you wish to ignore Tony's I-D reinforcing this concept and 
optional implementation:

    SHOULD, RECOMMENDED:  The words "ought", "encouraged" and "suggest
          strongly" can be used to connote something that is strongly
          urged.

There is no possibility to interpret SHOULD as nothing else as an 
optional implementation and thus can be ignored. Of course, the 
presumptions are:

      - Faith in your engineering peers,
      - Due Diligence decision to decide to ignore it, and
      - understanding if it was implemented, it could be ignored by 
consumers.

If that is not enough, we have a huge deployment history where SHOULDs 
was ignored and implemented as an option for operators, and we have 
history where a SHOULD was changed to a MUST and it caused problems. 
If your interpretation was correct, this change would not have been 
necessary.

IMV, the evidence is quite clear that SHOULD has no MUST-IMPLEMENT 
concept and never had.  If people read it that way, it probably did 
not cause a problem. So no big deal.  But if they expected others to 
MUST-IMPLEMENT a SHOULD and broke down because of that expectation, 
then I suggest they didn't read RFC2119 correctly.


From christer.holmberg@ericsson.com  Wed Aug 31 12:10:32 2011
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D367321F8E86 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level: 
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyVgU+VEJruf for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:10:31 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 225A721F8E3A for <ietf@ietf.org>; Wed, 31 Aug 2011 12:10:29 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-88-4e5e87808e0b
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id C1.31.20773.0878E5E4; Wed, 31 Aug 2011 21:12:00 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.250]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 31 Aug 2011 21:11:59 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Hector <sant9442@gmail.com>
Date: Wed, 31 Aug 2011 21:09:58 +0200
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxoESeZAOljERTPR9qclpXVgiZSXwAAGvtG
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852233C3B7BC@ESESSCMS0356.eemea.ericsson.se>
References: <4E5C067A.9080400@stpeter.im><003401cc66b1$d35af5a0$6801a8c0@oemcomputer><01O5FL6TFAY8014O5Z@mauve.mrochek.com><5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com> <004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark. com>,<4E5E8670.6090308@gmail.com>
In-Reply-To: <4E5E8670.6090308@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:10:33 -0000

Hi,

Sometimes the drafts says that something SHOULD be done, but the justificat=
ion is unclear to the reader, so it can be difficult to interpret the meani=
ng correctly.

So, I think it would cause less confusion if drafts made a better job of de=
scribing WHY something is a SHOULD, or MUST.

Something like SHOULD....BECAUSE :)

Regards,

Christer

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Hector [sa=
nt9442@gmail.com]
Sent: Wednesday, August 31, 2011 10:07 PM
Cc: IETF discussion list
Subject: Re: 2119bis

Murray S. Kucherawy wrote:

>> The only difference between "SHOULD" and "MAY" is that the implementor /
>> deployer needs a good excuse to not implement / employ a "SHOULD."
>> That's not the same as "IGNORE".
>
> But that's a big difference.  I think some people are being cavalier
> about the "good excuse" part, and that's where I have a problem.
> RFC2119 is not unclear on this point.

Correct again, it is not unclear.  It says it very clear.  I don't
know why you wish to ignore Tony's I-D reinforcing this concept and
optional implementation:

    SHOULD, RECOMMENDED:  The words "ought", "encouraged" and "suggest
          strongly" can be used to connote something that is strongly
          urged.

There is no possibility to interpret SHOULD as nothing else as an
optional implementation and thus can be ignored. Of course, the
presumptions are:

      - Faith in your engineering peers,
      - Due Diligence decision to decide to ignore it, and
      - understanding if it was implemented, it could be ignored by
consumers.

If that is not enough, we have a huge deployment history where SHOULDs
was ignored and implemented as an option for operators, and we have
history where a SHOULD was changed to a MUST and it caused problems.
If your interpretation was correct, this change would not have been
necessary.

IMV, the evidence is quite clear that SHOULD has no MUST-IMPLEMENT
concept and never had.  If people read it that way, it probably did
not cause a problem. So no big deal.  But if they expected others to
MUST-IMPLEMENT a SHOULD and broke down because of that expectation,
then I suggest they didn't read RFC2119 correctly.

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

From sant9442@gmail.com  Wed Aug 31 12:11:17 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE1B21F8E9B for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.211
X-Spam-Level: 
X-Spam-Status: No, score=-3.211 tagged_above=-999 required=5 tests=[AWL=0.388,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msaD0dKRX+QY for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:11:16 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id E614421F84D6 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:11:13 -0700 (PDT)
Received: by gyf3 with SMTP id 3so1019516gyf.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:12:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Pqr17/+NsSWW7pRftRaKz9FZLVr572NTL/bfK0rhO5E=; b=nNXue6cqFQ9GR+4fW9g4rEOWeW+PX3DnL0hy2k49KmN2d2XRNuwVeK5cPmraZ3CJDw 5zoo5H+p0SMVoUC6JaU/O2W35+OdQhqgkK+DGNAcA7lHe2CZ0IWna3vsT46UYd2jWjPP oMfOGK2fHihlBx848bdPW+Oxn5cub3qqpisdw=
Received: by 10.236.176.226 with SMTP id b62mr4269270yhm.78.1314817934443; Wed, 31 Aug 2011 12:12:14 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id z29sm776931yhn.16.2011.08.31.12.12.09 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 12:12:14 -0700 (PDT)
Message-ID: <4E5E87B9.3010902@gmail.com>
Date: Wed, 31 Aug 2011 15:12:57 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com><003401cc66b1$d35af5a0$6801a8c0@oemcomputer><01O5FL6TFAY8014O5Z@mauve.mrochek.com><5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com> <004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>
In-Reply-To: <004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:11:17 -0000

Randy Presuhn wrote:

>> Murray stated:
>> This sentence is self-contradictory.  "SHOULD" is, by definition, not "OPTIONAL".
> 
> I disagree with the claim that there is a contradiction there, but I also think
> "IGNORE" is incorrect.

That's a good point because if a good-faith decision was made to not 
implement a SHOULD, then there was no intent to ignore, there was no 
negligence and there is technical or protocol liability in that decision.

--
HLS

From moore@network-heretics.com  Wed Aug 31 12:12:44 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 969B321F8EFA for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.594
X-Spam-Level: 
X-Spam-Status: No, score=-3.594 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyflH760Xc7y for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:12:43 -0700 (PDT)
Received: from out5.smtp.messagingengine.com (out5.smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9EF21F8E9B for <ietf@ietf.org>; Wed, 31 Aug 2011 12:12:43 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3921221A8C; Wed, 31 Aug 2011 15:14:14 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 31 Aug 2011 15:14:14 -0400
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=EQYZ0+RtUywP5+yMz7ky+qEr4WI=; b=sM x8rYGD4aT1R+AjiwrnqMmMmnMFZ2wOkk/FOaNSFi97e4spgpY75iE5kekfswj89U URDz3eKUDRn1l676qtHYpFQg1QdlyDZurzAnc74XVFOHo79QIAcj2YcnwtRG+olM hSOtQxDGT1p9pkFc4mnkGe5/k01k8NNgfiPu5Obow=
X-Sasl-enc: RzO9OBxFIuxJ3t7Drqs1yukaftA23vVsXl+D1FpsdCcq 1314818054
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id 0A0CF960639; Wed, 31 Aug 2011 15:14:14 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5E8670.6090308@gmail.com>
Date: Wed, 31 Aug 2011 15:14:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im><003401cc66b1$d35af5a0$6801a8c0@oemcomputer><01O5FL6TFAY8014O5Z@mauve.mrochek.com><5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark. com> <4E5E8670.6090308@gmail.com>
To: Hector <sant9442@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:12:44 -0000

On Aug 31, 2011, at 3:07 PM, Hector wrote:

> Murray S. Kucherawy wrote:
>=20
>>> The only difference between "SHOULD" and "MAY" is that the =
implementor /
>>> deployer needs a good excuse to not implement / employ a "SHOULD."
>>> That's not the same as "IGNORE".
>> But that's a big difference.  I think some people are being cavalier =
about the "good excuse" part, and that's where I have a problem.  =
RFC2119 is not unclear on this point.
>=20
> Correct again, it is not unclear.  It says it very clear.  I don't =
know why you wish to ignore Tony's I-D reinforcing this concept and =
optional implementation:
>=20
>   SHOULD, RECOMMENDED:  The words "ought", "encouraged" and "suggest
>         strongly" can be used to connote something that is strongly
>         urged.
>=20

When the text in 2119 is already clearly written, but people fail to =
read it, I don't understand why adding more text in yet another document =
is likely to improve understanding.   Adding additional text and =
documents inherently increases the burden on readers.

Keith


From melinda.shore@gmail.com  Wed Aug 31 12:26:25 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F12AC21F8E00 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHDRgLWR6raH for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:26:24 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7977A21F8D84 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:26:24 -0700 (PDT)
Received: by pzk33 with SMTP id 33so3029331pzk.18 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:27:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=LMB7Up422o1N3u6lrojUlPQlmCjYfG5iphJACsZT1w4=; b=nLUT9FsNE73p5iyqcJFLB4ayRJkRHpfiwYkucLxJFMEKR015fYmElVwts+MxbxbWeh mAA1nMFp8/+bF+fmbL8XHwFjkoGz6iB/dU10Mco7ChLKJxD8FW+OPNxJuOmjD07mg+l+ k4Rzp03Ys8dqI7AGPJYQW2uySiY9Ui0yc6j7Y=
Received: by 10.68.51.234 with SMTP id n10mr671379pbo.374.1314818875359; Wed, 31 Aug 2011 12:27:55 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id m1sm30933753pbf.3.2011.08.31.12.27.53 (version=SSLv3 cipher=OTHER); Wed, 31 Aug 2011 12:27:54 -0700 (PDT)
Message-ID: <4E5E8B3F.9000904@gmail.com>
Date: Wed, 31 Aug 2011 11:27:59 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>	<F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark.	com> <4E5E8670.6090308@gmail.com> <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
In-Reply-To: <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:26:25 -0000

On 08/31/2011 11:14 AM, Keith Moore wrote:
> When the text in 2119 is already clearly written, but people fail to read it,
 > I don't understand why adding more text in yet another document is
 > likely to improve understanding.   Adding additional text and
 > documents inherently increases the burden on readers.

This seems pretty clear to me, and perhaps it's been the only clear 
thing in this discussion so far.  2119 was published in 1997 and aside
from a typo (that does not seem to have caused confusion, for whatever
that's worth) there haven't been a lot of complaints.  Thumbs up on
correcting typos, and both thumbs down on using the process of
correcting a typo to reopen a "SHOULD/MAY" rathole, or even a "NOT
RECOMMENDED" rathole.  I'd rather let the typo stand.  I don't think
the putative benefits of revising 2119 justify the effort.

Melinda

From sant9442@gmail.com  Wed Aug 31 12:41:55 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E5F21F8F79 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.276
X-Spam-Level: 
X-Spam-Status: No, score=-3.276 tagged_above=-999 required=5 tests=[AWL=0.323,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hvwtwuwx-Cvh for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:41:54 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id E667421F8F77 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:41:53 -0700 (PDT)
Received: by yie12 with SMTP id 12so1083198yie.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:43:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/odC4+5QFOMTB46mqsYvxklCqy+tAjK0Y5CHChsOGbE=; b=qBgtDBWMTIlvvERiABnGYWEZXJm/lpS/cBwD/ULAawIkAxsYyoWupvTY0m35h+bNnZ +e6HF6Zgf3AdkwPtkmjaDSQ15cZ/CLrYx3auw2KBrYqc9QMMJKn8J/6mWZn0oZtux3XW XezEaCRDebs0ObG/UW5U4H6VJMmfn8tMukOQk=
Received: by 10.151.92.12 with SMTP id u12mr666505ybl.189.1314819804712; Wed, 31 Aug 2011 12:43:24 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id f5sm539610ybf.1.2011.08.31.12.43.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 12:43:24 -0700 (PDT)
Message-ID: <4E5E8F0C.3060602@gmail.com>
Date: Wed, 31 Aug 2011 15:44:12 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark. com> <4E5E8670.6090308@gmail.com> <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
In-Reply-To: <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:41:55 -0000

Keith Moore wrote:

>> Correct again, it is not unclear.  It says it very clear.  I don't know 
>> why you wish to ignore Tony's I-D reinforcing this concept and 
>> optional implementation:
>>
>>   SHOULD, RECOMMENDED:  The words "ought", "encouraged" and "suggest
>>         strongly" can be used to connote something that is strongly
>>         urged.
>>
> 
> When the text in 2119 is already clearly written, but people fail to read 
> it, I don't understand why adding more text in yet another document is 
> likely to improve understanding.   Adding additional text and documents 
> inherently increases the burden on readers.

I'm having a hard time understanding why you continue to work on the 
basis that people "fail to read" essentially implying stupidity in the 
process.  The Point being that if Tony's I-D has it as it was  shown 
above, then it would be incorrect too in its understanding of RFC2119 
because non-normative words are clearly concepts related to a 
non-required mandate.

I suggest we have a huge history of protocol deployment where SHOULDs 
are ignored and SHOULDs implemented as an option, but in addition, the 
idea of the possibility that isn't presented as an option to operators 
was solely an implementator decision to enforce it and not make an 
optional feature for the operator to play with.  It is really up to 
the author to describe what the intent is for a particular SHOULD 
because its not an universal idea that SHOULD is always implemented.

Anyway, I think that's it for me on this. :)

--
HLS

From johnl@iecc.com  Wed Aug 31 12:43:43 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED5A21F8FAB for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.144
X-Spam-Level: 
X-Spam-Status: No, score=-111.144 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXGt9QL+f5wg for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:43:43 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CA65721F8FA7 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:43:42 -0700 (PDT)
Received: (qmail 59164 invoked from network); 31 Aug 2011 19:45:12 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 31 Aug 2011 19:45:12 -0000
Received: (qmail 51586 invoked from network); 31 Aug 2011 19:45:12 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 31 Aug 2011 19:45:12 -0000
Date: 31 Aug 2011 19:44:50 -0000
Message-ID: <20110831194450.1875.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: you can't force people to write well, was 2119bis
In-Reply-To: <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: moore@network-heretics.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:43:43 -0000

>When the text in 2119 is already clearly written, but people fail to
>read it, I don't understand why adding more text in yet another
>document is likely to improve understanding.  Adding additional text
>and documents inherently increases the burden on readers.

Having done my share of writing, and also having hired people to write
for me, I entirely agree.  You can't force people to write well by
adding ever more detailed and nitpicky rules.

If the problem is that RFCs aren't clear, or that they use words in
misleading ways, the burden should be on the WGs that produce the
drafts to fix them so that they say what they're trying to say better.

R's,
John

From moore@network-heretics.com  Wed Aug 31 12:49:05 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D44421F8FBC for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.594
X-Spam-Level: 
X-Spam-Status: No, score=-3.594 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hpxBTtWNBz2b for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:49:04 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2C28221F8F86 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:49:04 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id EE5D721DC2; Wed, 31 Aug 2011 15:50:34 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 31 Aug 2011 15:50:34 -0400
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=9+WBLVCdYGFE33AHxjvF7I66NCw=; b=WU ABjwz2L3NKCm067XPxP6AftSIoYnogJlm2YvfT9jWYd7Q3ukDV7/COHUVIzDLKqx fuO9XxbjpIIKrFkjJsSHylmaLnRggHnHhjvipdvd7DeV2+5SDfF9sFw+jtVqB5ds DHk8ONLbbRh6HcF2UfDp9gvGzO5gPL1UL+kToKRbc=
X-Sasl-enc: OZxnBt4DfZeXuXQ8s5k9QkTy0979CrVIwsPdVYTE31ob 1314820234
Received: from takiba.hq.corp.pbs.org (unknown [149.48.225.2]) by mail.messagingengine.com (Postfix) with ESMTPA id BBDD4960184; Wed, 31 Aug 2011 15:50:34 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E5E8F0C.3060602@gmail.com>
Date: Wed, 31 Aug 2011 15:50:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BF3216A-567F-4B99-A6A1-BE545D57C3E5@network-heretics.com>
References: <4E5C067A.9080400@stpeter.im><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark. com> <4E5E8670.6090308@gmail.com> <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com> <4E5E8F0C.3060602@gmail.com>
To: Hector <sant9442@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:49:05 -0000

On Aug 31, 2011, at 3:44 PM, Hector wrote:

> I'm having a hard time understanding why you continue to work on the =
basis that people "fail to read" essentially implying stupidity in the =
process.

I work on the basis of "fail to read" because I've seen countless =
examples of it.   And stupidity is not the same thing as lack of =
diligence.

>  The Point being that if Tony's I-D has it as it was  shown above, =
then it would be incorrect too in its understanding of RFC2119 because =
non-normative words are clearly concepts related to a non-required =
mandate.

As far as I'm concerned, Tony's I-D is a nonstarter, and therefore =
irrelevant.

Keith


From msk@cloudmark.com  Wed Aug 31 12:58:49 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B1B21F8FBB for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.524
X-Spam-Level: 
X-Spam-Status: No, score=-103.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NyPtDS0Z7xCK for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 12:58:49 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 19D7B21F8FB5 for <ietf@ietf.org>; Wed, 31 Aug 2011 12:58:49 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Wed, 31 Aug 2011 13:00:20 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF discussion list <ietf@ietf.org>
Date: Wed, 31 Aug 2011 13:00:18 -0700
Subject: RE: 2119bis
Thread-Topic: 2119bis
Thread-Index: AcxoF0RvLKK0g8RjTu6YjzUPydpYDAAAGzsA
Message-ID: <F5833273385BB34F99288B3648C4F06F13512DF9F1@EXCH-C2.corp.cloudmark.com>
References: <4E5C067A.9080400@stpeter.im><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com> <F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com> <004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark.	com> <4E5E8670.6090308@gmail.com> <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com> <4E5E8F0C.3060602@gmail.com> <1BF3216A-567F-4B99-A6A1-BE545D57C3E5@network-heretics.com>
In-Reply-To: <1BF3216A-567F-4B99-A6A1-BE545D57C3E5@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 19:58:49 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of K=
eith Moore
> Sent: Wednesday, August 31, 2011 12:51 PM
> To: Hector
> Cc: IETF discussion list
> Subject: Re: 2119bis
>=20
> On Aug 31, 2011, at 3:44 PM, Hector wrote:
>=20
> > I'm having a hard time understanding why you continue to work on the
> > basis that people "fail to read" essentially implying stupidity in the
> > process.
>=20
> I work on the basis of "fail to read" because I've seen countless
> examples of it.   And stupidity is not the same thing as lack of
> diligence.

Ditto.  And I also see a lot of creative interpretation.  There's little we=
 can do to thwart any of those problems; some people read what they want to=
 read and do so in a vacuum.

> As far as I'm concerned, Tony's I-D is a nonstarter, and therefore
> irrelevant.

I certainly agree that it's irrelevant to this discussion, plus it's only a=
n I-D at this point anyway.  We're talking about a published BCP here.

From tony@att.com  Wed Aug 31 13:08:22 2011
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF9D21F8D7C for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 13:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.258
X-Spam-Level: 
X-Spam-Status: No, score=-106.258 tagged_above=-999 required=5 tests=[AWL=0.340, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KCLXlDDE3O18 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 13:08:22 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 2366521F8D65 for <ietf@ietf.org>; Wed, 31 Aug 2011 13:08:22 -0700 (PDT)
X-Env-Sender: tony@att.com
X-Msg-Ref: server-10.tower-119.messagelabs.com!1314821391!27060298!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23063 invoked from network); 31 Aug 2011 20:09:51 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-10.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Aug 2011 20:09:51 -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 p7VKAHGc007497 for <ietf@ietf.org>; Wed, 31 Aug 2011 16:10:17 -0400
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 p7VKADs4007350 for <ietf@ietf.org>; Wed, 31 Aug 2011 16:10:13 -0400
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 p7VK9jEV003031 for <ietf@ietf.org>; Wed, 31 Aug 2011 16:09:46 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p7VK9hlK003007 for <ietf@ietf.org>; Wed, 31 Aug 2011 16:09:43 -0400
Received: from [135.70.29.151] (vpn-135-70-29-151.vpn.west.att.com[135.70.29.151]) by maillennium.att.com (mailgw1) with ESMTP id <20110831200941gw100e4loje> (Authid: tony); Wed, 31 Aug 2011 20:09:42 +0000
X-Originating-IP: [135.70.29.151]
Message-ID: <4E5E94FB.3050802@att.com>
Date: Wed, 31 Aug 2011 16:09:31 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark. com> <4E5E8670.6090308@gmail.com> <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
In-Reply-To: <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>
Content-Type: multipart/alternative; boundary="------------090206010901000505020907"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 20:08:23 -0000

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

On 8/31/2011 3:14 PM, Keith Moore wrote:
> On Aug 31, 2011, at 3:07 PM, Hector wrote:
>
>> RFC2119 is not unclear on this point.
>> Correct again, it is not unclear.  It says it very clear.  I don't know why you wish to ignore Tony's I-D reinforcing this concept and optional implementation:
>>
>>    SHOULD, RECOMMENDED:  The words "ought", "encouraged" and "suggest
>>          strongly" can be used to connote something that is strongly
>>          urged.
>>
> When the text in 2119 is already clearly written, but people fail to read it, I don't understand why adding more text in yet another document is likely to improve understanding.   Adding additional text and documents inherently increases the burden on readers.

context check. The purview of the non2119-nonkeywords doc is to suggest 
wording to use when *NOT* in the 2119 context.

Perhaps the paragraph in the non2119-nonkeywords docs should read:

     *instead* of "SHOULD" or "RECOMMENDED":  The words "ought", 
"encouraged" and "suggest
         strongly" can be used to connote something that is strongly
         urged.

     Tony

--------------090206010901000505020907
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <link href="chrome://translator/skin/floatingPanel.css"
      type="text/css" rel="stylesheet">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 8/31/2011 3:14 PM, Keith Moore wrote:
    <blockquote
      cite="mid:7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com"
      type="cite">
      <pre wrap="">
On Aug 31, 2011, at 3:07 PM, Hector wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">RFC2119 is not unclear on this point.
</pre>
        <pre wrap="">
Correct again, it is not unclear.  It says it very clear.  I don't know why you wish to ignore Tony's I-D reinforcing this concept and optional implementation:

  SHOULD, RECOMMENDED:  The words "ought", "encouraged" and "suggest
        strongly" can be used to connote something that is strongly
        urged.

</pre>
      </blockquote>
      <pre wrap="">
When the text in 2119 is already clearly written, but people fail to read it, I don't understand why adding more text in yet another document is likely to improve understanding.   Adding additional text and documents inherently increases the burden on readers.
</pre>
    </blockquote>
    <br>
    context check. The purview of the non2119-nonkeywords doc is to
    suggest wording to use when *NOT* in the 2119 context.<br>
    <br>
    Perhaps the paragraph in the non2119-nonkeywords docs should read:<br>
    <br>
    &nbsp;&nbsp;&nbsp; *instead* of "SHOULD" or "RECOMMENDED":&nbsp; The words "ought",
    "encouraged" and "suggest<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; strongly" can be used to connote something that is strongly<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; urged.<br>
    <br>
    &nbsp;&nbsp;&nbsp; Tony<br>
    <div style="bottom: auto; left: 197px; right: auto; top: 271px;
      display: none;" class="translator-theme-default"
      id="translator-floating-panel">
      <div title="Click to translate"
        id="translator-floating-panel-button"></div>
    </div>
  </body>
</html>

--------------090206010901000505020907--

From melinda.shore@gmail.com  Wed Aug 31 13:15:06 2011
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5879821F8F43 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 13:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.553
X-Spam-Level: 
X-Spam-Status: No, score=-3.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ntn+vHIgLnK for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 13:15:04 -0700 (PDT)
Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1626C21F8F3B for <ietf@ietf.org>; Wed, 31 Aug 2011 13:15:04 -0700 (PDT)
Received: by pzk33 with SMTP id 33so3125614pzk.18 for <ietf@ietf.org>; Wed, 31 Aug 2011 13:16:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=60Q1D6rD1BWc37yWd1wvq4BLRXb4ZZgjq/Zn/XAqISY=; b=CpZrjuE2CcVa/2CHavFm49IButYokHO1ieOIuMq1AlxncFkoXnld0UBcizYfpjDyn9 3PY5vw6rRZLxEniqKyQsxynB0v8L3v0w5JxPd3iYYv8FY5x9UERXX3dv1R9jj5lXEZV7 7iDgHjhutp91IMgdCe6fhwf6+NiSeX7Fwupt0=
Received: by 10.68.66.165 with SMTP id g5mr1047532pbt.327.1314821793450; Wed, 31 Aug 2011 13:16:33 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id p7sm2993548pbe.0.2011.08.31.13.16.29 (version=SSLv3 cipher=OTHER); Wed, 31 Aug 2011 13:16:30 -0700 (PDT)
Message-ID: <4E5E96A3.60401@gmail.com>
Date: Wed, 31 Aug 2011 12:16:35 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><4E5D30CC.4000009@nostrum.com><2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>	<F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark.	com> <4E5E8670.6090308@gmail.com>	<7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com> <4E5E94FB.3050802@att.com>
In-Reply-To: <4E5E94FB.3050802@att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 20:15:07 -0000

On 08/31/2011 12:09 PM, Tony Hansen wrote:
> context check. The purview of the non2119-nonkeywords doc is to suggest
> wording to use when *NOT* in the 2119 context.

Personally, I'm okay with an ambiguous, informal "may."  I'm
even okay with an ambiguous, informal "must."  I'm less okay
with the IETF publishing a thesaurus.

Melinda


From sant9442@gmail.com  Wed Aug 31 13:18:22 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D27221F8CF1 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 13:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[AWL=-0.369, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gg6h2Uo2ogp1 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 13:18:21 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id BA94021F8CED for <ietf@ietf.org>; Wed, 31 Aug 2011 13:18:21 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1082721gxk.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 13:19:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=aOuGm45NC0o9w2xIAsqWjW0VKzh5Uw+O3KuawTcP138=; b=N9ExAyQD0+2DNvz5/5w4DRam/9d0lwfCqmyd57CTz3qJVSr5oZFzTyna+9+/436G2o 883ckbQNzBvS5oapF7L+a0/w6XcB6Nx6yDQFWHncKn+9GF4TxvSATlspW1QkfzFhb1lJ 1NyRaQH/2vvMslGwfGKzwqSS8ECZFjchuCZ4M=
Received: by 10.236.37.230 with SMTP id y66mr4990964yha.10.1314821992582; Wed, 31 Aug 2011 13:19:52 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id e21sm119265yhn.77.2011.08.31.13.19.51 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 13:19:52 -0700 (PDT)
Message-ID: <4E5E9797.5020509@gmail.com>
Date: Wed, 31 Aug 2011 16:20:39 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><4E5D3546.3020109@winserver.com><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer> <F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark. com> <4E5E8670.6090308@gmail.com> <7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com> <4E5E8F0C.3060602@gmail.com> <1BF3216A-567F-4B99-A6A1-BE545D57C3E5@network-heretics.com>
In-Reply-To: <1BF3216A-567F-4B99-A6A1-BE545D57C3E5@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 20:18:22 -0000

Keith Moore wrote:

>> The Point being that if Tony's I-D has it as it was  shown above, 
>> then it would be incorrect too in its understanding of RFC2119 
>> because the non-normative words are clearly concepts related to a 
>> non-required mandate.
> 
> As far as I'm concerned, Tony's I-D is a nonstarter, and therefore irrelevant.

Oh the irony in the "Failure to Read" labeling category, the art of 
selective synergism, :) if only to acknowledge the rich IETF-MAN-YEARS 
behind the production of this I-D and its obvious relationship to 
RFC2119 and any future consideration for a RFC2119BIS. :)

Thanks

From mnot@mnot.net  Wed Aug 31 14:56:08 2011
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3AB021F8F37 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 14:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.263
X-Spam-Level: 
X-Spam-Status: No, score=-105.263 tagged_above=-999 required=5 tests=[AWL=-2.664, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BAxBisxPAfXZ for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 14:56:08 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1170121F8F24 for <ietf@ietf.org>; Wed, 31 Aug 2011 14:56:07 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.37.195]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6345822E256; Wed, 31 Aug 2011 17:57:31 -0400 (EDT)
Subject: Re: 2119bis
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4E5E56BF.6050909@piuha.net>
Date: Thu, 1 Sep 2011 07:57:28 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <15EA8757-9E65-41C2-8C8F-7B4FB3AB25F5@mnot.net>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <806FF78E-17CF-43A3-9F74-80AA876E4A08@mnot.net> <4E5E56BF.6050909@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1244.3)
Cc: IETF discussion list <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 21:56:08 -0000

If the author is disciplined enough to use them in that manner, sure.

I haven't come across many.


On 01/09/2011, at 1:43 AM, Jari Arkko wrote:

>=20
>> Unless of course one considers us the Protocol Nanny's(tm) - if do =
not do a SHOULD, we will send you to bed without your treacle! I.e., =
there IS NO DISTINCTION BETWEEN A BARE SHOULD AND A MAY.
>>=20
>=20
> Of course there is. Its the distinction between -
>=20
> Qualified SHOULD) Here lie dragons. Take the recommended route, unless =
you know how to fight them.
>=20
> Unqualified SHOULD) Here lie some dangers. Check with someone who =
knows, or take the recommended route.
>=20
> MAY) Here's an area. You could go there.
>=20
> Of course, the first and last pieces of text are preferred. But =
sometimes no one was brave enough to explore the area, so we don't =
actually know what dangers there are, they cannot be listed.
>=20
> Jari
>=20

--
Mark Nottingham   http://www.mnot.net/




From eburger@standardstrack.com  Wed Aug 31 17:35:42 2011
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78B8F21F8CDF for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 17:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.335
X-Spam-Level: 
X-Spam-Status: No, score=-102.335 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bcFKykioQ38u for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 17:35:41 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id D01FE21F8CDE for <ietf@ietf.org>; Wed, 31 Aug 2011 17:35:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=FHmx2s6Yfmb0Sdt9UrkHnPdsBe01LSQHFHFNL1io5pcjLBinUVt29e0aEMt6Y7aZ3GU9JQ/PL18AvT9pu1y16mOcEFwVw6hEebsjabCuEsUVi98FyjEpH6z+7z5oJNMq;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.141]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QyvHL-0004Zt-6V for ietf@ietf.org; Wed, 31 Aug 2011 17:37:11 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-32--624703531; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: 2119bis
Date: Wed, 31 Aug 2011 20:37:08 -0400
In-Reply-To: <4E5E3DC3.7080201@winserver.com>
To: IETF discussion list <ietf@ietf.org>
References: <4E5C067A.9080400@stpeter.im>	<201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com>	<41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com>	<003401cc66b1$d35af5a0$6801a8c0@oemcomputer>	<01O5FL6TFAY8014O5Z@mauve.mrochek.com>	<5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com>	<4E5D30CC.4000009@nostrum.com>	<2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com>	<4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5E2976.90102@gmail.com> <B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com> <4E5E3353.4010503@gmail.com> <2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com> <4E5E3DC3.7080201@winserver.com>
Message-Id: <54F02272-BE28-4BFB-AE24-CAA345AE25FA@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.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
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2011 00:35:42 -0000

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

This highlights an interesting issue as an RFC goes from PS to IS.  I =
would offer that most SHOULDs in a document will, if there are real =
implementations out there, migrate to MUST or MUST NOT.

On Aug 31, 2011, at 9:57 AM, hector wrote:

> I think you are speaking of long term operations where an SHOULD is so =
widely adopted, it inherently because a MUST have in all new =
implementations.  So that vain, sure, eventually the better options =
naturally become part of the protocol to the extent the options might be =
even remove to simplify things.  We also have the opposite where a =
SHOULD is implemented but no one users it so eventually, it may be =
remove as an option.


--Apple-Mail-32--624703531
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
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA5MDEwMDM3MDlaMCMGCSqGSIb3DQEJ
BDEWBBT5hTCcRrv1XAiDhnQ+M4zcrn2hjjCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBACSdvqGZt5dq8hAnFMKwDFbzeToY07CQWayZ7+Oi/6LRUtf+
oPt/RD8C+cuSas4NhjAuwy7aWgUpgrN1G5bBXKrinF1DZZD78TxHEIUmXJfCXbM5vz85BK76f8Nz
K2yCU+OlhgC7S8c8CTbSzkjCu8f3NFSDj49EmeQ32+DWkCDw4ZzMKhY9Iow3JlJyguC6WJmN6/sw
QUr7Am1YlNkqECXGzbzYysiO8J9wJhyWARvjE+GNL3xmccVPjU0sqHbynmpPekT+2hKDGqZEo28g
gcomSIbdz14CmsRJrUJ+8Nfo1V6j9G5xVAeEQqPzM539rgdVIPgsTthz6KFyJUmjNCwAAAAAAAA=

--Apple-Mail-32--624703531--

From sant9442@gmail.com  Wed Aug 31 23:56:39 2011
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD51121F8834 for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 23:56:39 -0700 (PDT)
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.677,  BAYES_00=-2.599, GB_I_LETTER=-2, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C0gu+DhUA2wf for <ietf@ietfa.amsl.com>; Wed, 31 Aug 2011 23:56:38 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id A98C421F87F9 for <ietf@ietf.org>; Wed, 31 Aug 2011 23:56:38 -0700 (PDT)
Received: by gwb20 with SMTP id 20so843842gwb.31 for <ietf@ietf.org>; Wed, 31 Aug 2011 23:58:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=8hVmfzXD5lWB4DvZ2hU781gzRP3w+AiEJ4yrE2E/F0A=; b=TBNuYfcvDXs9huNkPgGT/JkT10RkgXheWCd6L3S+8JuUKsjXO66HnJPKt3DM2ydvjr 7915Q67oTDMIchEGSWIrYzVEqdU7Ew37AkTPKXE4smBkcCqCmLixead2ZR5CmQq7FF0T OA/iV31NMcIpUSaQ8t/t33YvAnSm2QizZ4PAM=
Received: by 10.90.168.7 with SMTP id q7mr1068284age.30.1314860290505; Wed, 31 Aug 2011 23:58:10 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id s13sm336660anm.32.2011.08.31.23.58.09 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 23:58:09 -0700 (PDT)
Message-ID: <4E5F2D31.90006@gmail.com>
Date: Thu, 01 Sep 2011 02:58:57 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: 2119bis
References: <4E5C067A.9080400@stpeter.im><BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com><4E5E2976.90102@gmail.com><B8C3D5C9-5053-4A35-8EB6-098E1CF8874B@network-heretics.com><4E5E3353.4010503@gmail.com><2292D626-A55E-40D3-A68B-4FCA6526F156@network-heretics.com><4E5E3DC3.7080201@winserver.com><BE1DAF7C-16FE-479E-B9F4-DD1E030A55BF@network-heretics.com><4E5E5982.9030809@gmail.com><478B8813-3C9F-4F42-9872-A2512DAEA8C0@network-heretics.com><F5833273385BB34F99288B3648C4F06F13512DF9D9@EXCH-C2.corp.cloudmark.com><4E5E75EE.8050002@gmail.com>	<F5833273385BB34F99288B3648C4F06F13512DF9DF@EXCH-C2.corp.cloudmark.com>	<004901cc680c$1dcd6cc0$6801a8c0@oemcomputer>	<F5833273385BB34F99288B3648C4F06F13512DF9EB@EXCH-C2.corp.cloudmark.	com>	<4E5E8670.6090308@gmail.com>	<7A7AF436-E39B-494D-B5CC-C1FC749D0BD6@network-heretics.com>	<4E5E8F0C.3060602@gmail.com>	<1BF3216A-567F-4B99-A6A1-BE545D57C3E5@network-heretics.com> <F5833273385BB34F99288B3648C4F06F13512DF9F1@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F13512DF9F1@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2011 06:56:40 -0000

Murray S. Kucherawy wrote:

> Ditto.  And I also see a lot of creative interpretation.  There's little we 
> can do to thwart any of those problems; some people read what they want to 
> read and do so in a vacuum.

+1.

I couldn't agree with you more Murray!

When you consider that its not very hard to find mainstream software, 
or even the one they are using to post mail in the list using well 
established IETF protocols that follows RFC2119 to the letter, it 
makes you wonder if there really a problem with RFC2119. I mean, I 
don't see it myself. It reads pretty clear to me, especially section 6 
with that precise non-ambiguous sentence.

    6. Guidance in the use of these Imperatives

    Imperatives of the type defined in this memo must be used with care
    and sparingly.  In particular, they MUST only be used where it is
    actually required for interoperation or to limit behavior which has
    potential for causing harm (e.g., limiting retransmisssions)  For
    example, they must not be used to try to impose a particular method
    on implementors where the method is not required for
    interoperability.

That last sentence is so clear. Maybe the error is not using an 
uppercase MUST NOT and NOT REQUIRED in that last sentence.  Maybe 
software people need logic statements like:

      If X doesn't need Y, then MUST NOT use SHOULD to impose Y.

Honestly, this is like in the DKIM WG where DKIM tried to impose the 
SMTP extension 8BITMIME on SMTP servers with a SHOULD keyword.  DKIM 
tried to make that a MUST but the DKIM WG rejected it, I guess because 
too many SMTP servers did not support 8BITMIME and it wasn't really 
required. I think one person had a problem or something like that and 
because of them, DKIM wanted to force 8BITMIME on SMTP Servers. So 
instead the DKIM WG was yelled at for being RFC2119 illiterates 
because DKIM didn't need a MUST anyway a SHOULD was enough to mandate 
8BITMIME and any SMTP server that didn't support 8BITMIME was broken 
already. So the question here is:

      Does DKIM need 8BITMIME in order to work correctly?

DKIM seems to be working fine without it.

I will say that I don't agree that there isn't much anyone can do to 
thwart these problems.  You really can by just sticking to engineering 
conviction and point out which misinterpretations of RFC2119 can cause 
some serious problems, like with SMTP!

STD10 (RFC821) has a SHOULD NOT drop connection before QUIT is 
negotiated, and it was changed in RFC2821 to a MUST NOT.  I guess 
RFC2119, released during DRUMS, was misread to help provide the 
rational that a SHOULD NOT is really not an option so why not make it 
a MUST NOT? After all there is really no valid reason for not a client 
not to seen a QUIT and all those clients that don't are broken!

But look at that Current Standard STD10 SHOULD to Proposed Standard 
MUST did!  Receivers now are forced to wait for the client to hangup 
for upto 5 minutes and this allowed smart clients to leverage this 
delay to hold the remote host connection to wait for more mail to 
send.  Is that a problem?  Well, maybe not, but those smart clients 
seem to think so warning client operators to:

      - Use it Wisely,
      - Seek Remote Host permission to consume computer resources
      - Do no hold the server too long
      - Its considered Anti-Social, and
      - even foretold that is abuse remote hosts, they might begin
        to drop you and block you!

Even with all those warnings from the smart clients leveraging the 
delays, its ignored and increasingly happening and that server 
defensive prediction is starting to come true - by selectively 
ignoring the one RFC2821 MUST NOT drop connection mandate and 
selective using STD10 SHOULD NOT which RFC2119 says is an option, you 
don't need to follow it.

Its frustrating I must admit when people read RFC2119 with creative 
interpretations to do things it doesn't what you to do!


--
HLS
