Re: [sidr] WGLC for draft-ietf-sidr-algorithm-agility-03

Brian Dickson <brian.peter.dickson@gmail.com> Wed, 09 November 2011 20:07 UTC

Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F95F1F0C4A for <sidr@ietfa.amsl.com>; Wed, 9 Nov 2011 12:07:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.567
X-Spam-Level:
X-Spam-Status: No, score=-3.567 tagged_above=-999 required=5 tests=[AWL=0.032, 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 tEfTK3nKQqZO for <sidr@ietfa.amsl.com>; Wed, 9 Nov 2011 12:07:27 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id E51391F0C41 for <sidr@ietf.org>; Wed, 9 Nov 2011 12:07:26 -0800 (PST)
Received: by faas12 with SMTP id s12so2454543faa.31 for <sidr@ietf.org>; Wed, 09 Nov 2011 12:07:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cssFrTj0EKdN54JJeN7Lm+k5hRLL53yx4bCJVsF/PNU=; b=NQurJ+TQykt/l5ilUdf85qB9Hfl7d6byQhLH9TeW3no7XChhPHSjldou8PLfDLD+yG FYbB6YaT/Jdd3LqeKgMxBJefYNTt6NiST4VYMMYLMBEvuG+uhEpb3v75F6k0TX3JEQoY A1OKAFA3H5cYGj8LXnhGt63RRfJDS+iCEw2Gg=
MIME-Version: 1.0
Received: by 10.223.94.143 with SMTP id z15mr6853937fam.32.1320869246067; Wed, 09 Nov 2011 12:07:26 -0800 (PST)
Received: by 10.223.54.15 with HTTP; Wed, 9 Nov 2011 12:07:25 -0800 (PST)
In-Reply-To: <p06240805cae063a02041@128.89.89.6>
References: <Pine.WNT.4.64.1110201037470.4820@SMURPHY-LT.columbia.ads.sparta.com> <24B20D14B2CD29478C8D5D6E9CBB29F6025FEE@Hermes.columbia.ads.sparta.com> <CAH1iCipuaB=niUZY2WQdMX8REDVTWGjhosxTyq1AekkUiLZ=FQ@mail.gmail.com> <p06240805cae063a02041@128.89.89.6>
Date: Wed, 09 Nov 2011 15:07:25 -0500
Message-ID: <CAH1iCipm-DGtwuYm0471J2890zAng0CH-sj1dnuq1wi2QEvsFQ@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] WGLC for draft-ietf-sidr-algorithm-agility-03
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2011 20:07:27 -0000

On Wed, Nov 9, 2011 at 1:42 PM, Stephen Kent <kent@bbn.com> wrote:
> At 1:27 AM -0500 11/8/11, Brian Dickson wrote:
>
> ...
>
> I do not support adoption of this document in its current form.
>
> The main reasons have to do with fundamental aspects which at a high
>
> level have been addressed by my colleagues,
>
> so, this is a Verisign critique, provided by you, Eric, and Danny?

Respectfully, Stephen, I would ask that you not infer anything along
these lines.
The IETF is very clear on participation being an individual activity,
regardless of
$day_job.

In addition to this _not_ being the case, I _personally_ consider this both
highly inappropriate at a professional level, and bordering on _ad_hominem_,
something that really has no place in WG mailing-list discussions.

I would ask that you seriously consider whether an apology for your comment
is appropriate.

As for "colleague", I meant within the WG, as in "collegial". If I had meant to
say "co-worker", I would have said "co-worker".

Any similarity between our concerns is entirely due to similarity in operational
experiences in a variety of venues, at a variety of $day_jobs.

I'll address the content-oriented portion of your email in a separate message.

Brian
- not using any email-address that would suggest affiliation -