Re: [therightkey] Ramping up

Phillip Hallam-Baker <hallam@gmail.com> Mon, 17 February 2014 20:08 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0494B1A025C for <therightkey@ietfa.amsl.com>; Mon, 17 Feb 2014 12:08:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVF6bxyf81pY for <therightkey@ietfa.amsl.com>; Mon, 17 Feb 2014 12:08:12 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id B55721A0536 for <therightkey@ietf.org>; Mon, 17 Feb 2014 12:08:11 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id mc6so11426359lab.21 for <therightkey@ietf.org>; Mon, 17 Feb 2014 12:08:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3D+tAAnm9UHfArBHU+V1TQvQu/SNpzzRgn4/1cPEBDI=; b=KPOaCojmIfYGrFVgqpmt5YoBavof6fdPN0GHDbqVVCa1IRzBPgk+Q1CD+nuv1i33n4 DdPCNreg8PwFv9HVprVaZ1J1DUU3pX/8UC9gNo1sP1Uog4CdvE8/b+n+f045KCY4QVZV bIR8CylA3eV0tVax0TWQTpVmH7ExTQrGmXHNY/LfKavjh5AP+ukKbQ6/buBhjSMAeiZO Vugu5edcukXwFnPHCBfbF0+5i4l5gHjVNgQ3ApkGs5MbMhV6hnbmLBaCDd0efym/KRzU 8MUzto3fdUg3HA4etd2e9jBna/RyPDTBqdiAQY594rRGleE5IIOZC21RnwrH1XjhMJVy 5I0g==
MIME-Version: 1.0
X-Received: by 10.112.39.167 with SMTP id q7mr22216lbk.82.1392667688433; Mon, 17 Feb 2014 12:08:08 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 17 Feb 2014 12:08:08 -0800 (PST)
In-Reply-To: <53025C8F.5020803@gmail.com>
References: <53025C8F.5020803@gmail.com>
Date: Mon, 17 Feb 2014 15:08:08 -0500
Message-ID: <CAMm+Lwh04TKrPy1Kp-=SZCOLxOJmf0OQpAOJS2gnq4254O12Vw@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary="001a1134d7aedc00cd04f29fb651"
Archived-At: http://mailarchive.ietf.org/arch/msg/therightkey/CGigslBAoEPZvMEFT0GV3-fgT9E
Cc: "therightkey@ietf.org" <therightkey@ietf.org>
Subject: Re: [therightkey] Ramping up
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>, <mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey/>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>, <mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 20:08:15 -0000

The fact that designers have been forced to go through the process of
generating a description is often very useful.

What I have been doing is to make the presentation of what and why into
podcasts that are up on YouTube.

I think UNIX would have come out very differently if the designers had been
required to work with a technical writer and explain what was going on. Lot
of needless obfustication would have been easier to fix than to explain.

Which is of course why there is a resistance to doing such exercises.


On Mon, Feb 17, 2014 at 2:01 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> 1) I've asked Ben and his co-authors to resubmit
>    draft-laurie-rfc6962-bis as draft-ietf-trans-rfc6962-bis
>
> 2) We need to nail down milestones.  In particular we need
>    to have a reasonable ballpark estimate of when we'll get
>    the bis draft into working group last call.  I'd like more
>    feedback from the authors and working group participants
>    on what they and you feel needs to be done to wrap up
>    the draft.  Does late 2014 seem reasonable for working
>    group last call?
>
> 3) Another question is whether or not there are sections
>    of 6962bis which ought to be moved to separate documents,
>    such as client behavior.
>
> 4) London planning: I am generally not a fan of burning up
>    meeting time on PowerPoint-driven presentations - they're
>    sometimes unavoidable but IETF meetings are working meetings
>    and I'd rather use the time productively, for face to face
>    discussion of things which are difficult to work out on
>    the mailing list or which would benefit from more interactivity
>    than we can get with email.  We don't have a huge amount of
>    spare time in London but we can squeeze in some people in
>    if they've got something that needs attention or that would
>    help move the document along
>
> 5) the corollary to 4 is that I do try to get as much done on
>    the mailing list as possible.  One thing that's been useful
>    in some circumstances in the past has been an issue tracker.
>    We do have a working group wiki page with an issue tracker,
>    and I'd like to get a sense of whether the working group in
>    general and the authors more specifically would find it
>    helpful in progressing the document.
>
> 6) Are there other process issues you'd like to see addressed?
>
> Once I hear from Ben et al. I'll get a draft agenda for London
> posted.
>
> Thanks,
>
> Melinda
>
> _______________________________________________
> therightkey mailing list
> therightkey@ietf.org
> https://www.ietf.org/mailman/listinfo/therightkey
>



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