
From nobody Wed Apr 16 11:40:00 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62791A021D for <irtf-discuss@ietfa.amsl.com>; Wed, 16 Apr 2014 11:39:58 -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=-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 VRH23zUtfAIP for <irtf-discuss@ietfa.amsl.com>; Wed, 16 Apr 2014 11:39:53 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 456641A020A for <irtf-discuss@irtf.org>; Wed, 16 Apr 2014 11:39:53 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id j17so12550969oag.26 for <irtf-discuss@irtf.org>; Wed, 16 Apr 2014 11:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=NVRn5Z1kzd1YytQfeLU3KYlbbRpAytKnOrJNNGZeg6A=; b=GZiWKuIZgND/ILqDEr6eAruJxO3YiQ7KFdOxj+dAad8CMDN86TZWiXaFhfvwoViTXk /EhRpDZZxocp5WlLNBu4OZH1It28GeukVIIZuirUriCdsqeB2jiDpfaEQGx9Ju6Gq011 y0GnkTRjv/IID+N8LUkuG0XWnHVxrqFR8BpxLFhCsVSaB9Hm5jSG7WhJvWDppHoL84eW DAoZWlnoVVuMWaV3I9EUnGuhFtTltbQpD5fqXTwB3dzv7DgO0dJbGW2Uqa2Z7A0V5v0J EZnAUPLEcyw8MeVye6xR4d+rptJcwr/8dkis4n9BNNojV4NiHGMBlSgwllXBm9LHTLxo yWNw==
X-Received: by 10.60.229.228 with SMTP id st4mr7923607oec.16.1397673589900; Wed, 16 Apr 2014 11:39:49 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id ii8sm41303336obb.11.2014.04.16.11.39.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 11:39:49 -0700 (PDT)
Message-ID: <534ECE74.4080705@gmail.com>
Date: Wed, 16 Apr 2014 13:39:48 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IRTF Discuss <irtf-discuss@irtf.org>
References: <20140416183211.14488.3655.idtracker@ietfa.amsl.com>
In-Reply-To: <20140416183211.14488.3655.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140416183211.14488.3655.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------040305020608000105040605"
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/G36T2UTwAqaG8j4w766uS5W7LhM
Subject: [irtf-discuss] Request for feedback on "An IRTF Primer for IETF Participants"
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 18:39:59 -0000

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

Lars and I have been talking for an embarrassingly long time about a 
draft to help IETF folk who are proposing work in the IRTF, and that's 
finally happened.

Please comment (either on this list or privately is fine) about whether 
the document seems helpful based on your experience, and whether there 
are other things we should include.

Thanks,

Spencer, as an editor

-------- Original Message --------
Subject: 	[irsg] New Version Notification - draft-dawkins-irtf-newrg-01.txt
Date: 	Wed, 16 Apr 2014 11:32:11 -0700
From: 	internet-drafts@ietf.org
To: 	irtf@irtf.org, IRSG <irsg@irtf.org>



A new version (-01) has been submitted for draft-dawkins-irtf-newrg:
http://www.ietf.org/internet-drafts/draft-dawkins-irtf-newrg-01.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-dawkins-irtf-newrg/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-dawkins-irtf-newrg-01

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.




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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Lars and I have been talking for an embarrassingly long time about a
    draft to help IETF folk who are proposing work in the IRTF, and
    that's finally happened.<br>
    <br>
    Please comment (either on this list or privately is fine) about
    whether the document seems helpful based on your experience, and
    whether there are other things we should include.<br>
    <br>
    Thanks,<br>
    <br>
    Spencer, as an editor<br>
    <div class="moz-forward-container"><br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>[irsg] New Version Notification -
              draft-dawkins-irtf-newrg-01.txt</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Wed, 16 Apr 2014 11:32:11 -0700</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:irtf@irtf.org">irtf@irtf.org</a>, IRSG <a class="moz-txt-link-rfc2396E" href="mailto:irsg@irtf.org">&lt;irsg@irtf.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>A new version (-01) has been submitted for draft-dawkins-irtf-newrg:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-dawkins-irtf-newrg-01.txt">http://www.ietf.org/internet-drafts/draft-dawkins-irtf-newrg-01.txt</a>


The IETF datatracker page for this Internet-Draft is:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-dawkins-irtf-newrg/">https://datatracker.ietf.org/doc/draft-dawkins-irtf-newrg/</a>

Diff from previous version:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-dawkins-irtf-newrg-01">http://www.ietf.org/rfcdiff?url2=draft-dawkins-irtf-newrg-01</a>

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.

</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------040305020608000105040605--


From nobody Thu Apr 17 01:59:17 2014
Return-Path: <aaronyiding@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFBDE1A02EA for <irtf-discuss@ietfa.amsl.com>; Thu, 17 Apr 2014 01:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.423
X-Spam-Level: *
X-Spam-Status: No, score=1.423 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 Gbjm6R4QWUm8 for <irtf-discuss@ietfa.amsl.com>; Thu, 17 Apr 2014 01:59:10 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5611A0027 for <irtf-discuss@irtf.org>; Thu, 17 Apr 2014 01:59:10 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id i7so153229oag.23 for <irtf-discuss@irtf.org>; Thu, 17 Apr 2014 01:59:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=xvkuxSHXzikSKgYqxO+yDH6JJoiiLRAHDiOtjf/5rSY=; b=VCfl20YlTGPjNMZPA9PLKXJa3sH7VcJWmJtxxp7lXhvqK6Ug9KPuAcmBRDRfZZ0264 RDIvX6bo1MVJ1DRqnpp300IKTq8tB9D6iY5j+KdHOY3l0I/2ZJE6/zYdAIDw9fpCLvxV fi/lbNY+oS4GMKqdxYtuajUQGsv4c8ehQyiJOtwo9qOSyLfSeQ9WD6/XnZu5nxkHb6uA +ORH+Ez1bqUsF0zsg21epErfYwMifjBTyetlKs9RyzToe0ix+moFmn6e2BnXTdy4uoH0 By9dc/mpXDpys5BWfDjvKMVfFVJusBjnBaHpEfNierhfpRPic4yF+gdk7wuRWZheIp1W bZgg==
MIME-Version: 1.0
X-Received: by 10.60.135.106 with SMTP id pr10mr10967404oeb.15.1397725146721;  Thu, 17 Apr 2014 01:59:06 -0700 (PDT)
Sender: aaronyiding@gmail.com
Received: by 10.182.8.42 with HTTP; Thu, 17 Apr 2014 01:59:06 -0700 (PDT)
Date: Thu, 17 Apr 2014 11:59:06 +0300
X-Google-Sender-Auth: darjmAH6vsQ20r19HbM_dkzJfW0
Message-ID: <CANqPRgyAQ2tmrSV8DhorbYTNVGH9qGL8jhBFWJrjG2p+prozFw@mail.gmail.com>
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: ietf@ietf.org, irtf-discuss@irtf.org, diversity@ietf.org
Content-Type: multipart/alternative; boundary=047d7b41791ddd30df04f7393ed3
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/XFN9nPbuaQ3FJuMvONjXHfnZC44
Subject: [irtf-discuss] IETFer's work received ACM Computing Review
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 08:59:15 -0000

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

picked up by the Computing Review, by a couple of ietfers (e.g., Jouni
Korhonen, J=C3=B6rg Ott, Jon Crowcroft)

http://www.computingreviews.com/Browse/Browse_titles2.cfm?journal_id=3D6052

Bridging the gap between Internet standardization and networking research

---------------------------------------
ACM Computing Review
"
Bridging the gap between the network research community and Internet
standards is an important topic. Most network research has not been turned
into an Internet standard, while some research comes a long way in order to
become an Internet standard. Very few studies investigate this issue
because it extends beyond purely technical concerns.

The authors have an advantage in investigating this issue since they have
tightly collaborated on projects with academic researchers and industrial
professionals. They thoroughly present their observations and share their
experiences in this paper. The challenges for this gap are defined in two
parts: technical challenges and nontechnical challenges. A good point is
that the authors share the nontechnical challenges that might be ignored by
researchers and industrial professionals. The authors, aware of the gap,
also find two major opportunities that can extend research works to
standardization contributions, which is encouraging to networking
researchers.

Based on their past experiences, the authors share two concrete case
studies: mobile traffic offloading and Internet protocol version 6 (IPv6)
transition technologies. The mobile traffic offloading case shows
substantial scientific results, but it also shows an under-performing
standardization effort. This case proves that the proposal, which does not
fit in an existing mindset, is usually a failure. On the other hand, the
case of IPv6 transition technologies shows good results in both academia
and industry, because the research proposal has extensibility and minimum
impact on the existing infrastructure. The authors then share their lessons
and suggestions to bridge the gap. These are honest and useful to both
academia and industry. Readers will see the potential for comprehensive
collaboration between networking research and Internet standardization.
"

----------------------
ACM SIGCOMM CCR chief editor:

"Its focus is to identify ways to bridge the gap between the networking
community and the Internet standardization bodies. The authors, from
Broadcom, Nokia, University of Cambridge, Aalto University and University
of Helsinki, are describing the differences and similarities between how
the two communities operate. They further provide interesting data on the
participation of academic and industrial researchers in standardization
bodies. They discuss ways to minimize the friction that may exist as a
particular technology is making the leap from the scientific community into
the industry."


Two cents,
Aaron

-----------
http://www.cl.cam.ac.uk/~ad707/

--047d7b41791ddd30df04f7393ed3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">picked up by the Computing Review, by a couple of ietfers =
(e.g., Jouni Korhonen, J=C3=B6rg Ott, Jon Crowcroft)<br>
<br>
<a href=3D"http://www.computingreviews.com/Browse/Browse_titles2.cfm?journa=
l_id=3D6052">http://www.computingreviews.com/Browse/Browse_titles2.cfm?jour=
nal_id=3D6052</a><br>
<br>
Bridging the gap between Internet standardization and networking research<b=
r>
<br>
---------------------------------------<br>
ACM Computing Review<br>
&quot;<br>
Bridging the gap between the network research community and Internet=20
standards is an important topic. Most network research has not been=20
turned into an Internet standard, while some research comes a long way=20
in order to become an Internet standard. Very few studies investigate=20
this issue because it extends beyond purely technical concerns.<br>
<br>
The
 authors have an advantage in investigating this issue since they have=20
tightly collaborated on projects with academic researchers and=20
industrial professionals. They thoroughly present their observations and
 share their experiences in this paper. The challenges for this gap are=20
defined in two parts: technical challenges and nontechnical challenges. A
 good point is that the authors share the nontechnical challenges that=20
might be ignored by researchers and industrial professionals. The=20
authors, aware of the gap, also find two major opportunities that can=20
extend research works to standardization contributions, which is=20
encouraging to networking researchers.<br>
<br>
Based on their past=20
experiences, the authors share two concrete case studies: mobile traffic
 offloading and Internet protocol version 6 (IPv6) transition=20
technologies. The mobile traffic offloading case shows substantial=20
scientific results, but it also shows an under-performing=20
standardization effort. This case proves that the proposal, which does=20
not fit in an existing mindset, is usually a failure. On the other hand,
 the case of IPv6 transition technologies shows good results in both=20
academia and industry, because the research proposal has extensibility=20
and minimum impact on the existing infrastructure. The authors then=20
share their lessons and suggestions to bridge the gap. These are honest=20
and useful to both academia and industry. Readers will see the potential
 for comprehensive collaboration between networking research and=20
Internet standardization.<br>
&quot;<br>
<br>
----------------------<br>
ACM SIGCOMM CCR chief editor: <br>
<br>
&quot;Its focus is to identify ways to bridge the gap between the networkin=
g=20
community and the Internet standardization bodies. The authors, from=20
Broadcom, Nokia, University of Cambridge, Aalto University and=20
University of Helsinki, are describing the differences and similarities=20
between how the two communities operate. They further provide=20
interesting data on the participation of academic and industrial=20
researchers in standardization bodies. They discuss ways to minimize the
 friction that may exist as a particular technology is making the leap=20
from the scientific community into the industry.&quot;<br>
<br>
<br>
Two cents,<br>
Aaron=C2=A0<br><div dir=3D"ltr"><br>-----------<br><a href=3D"http://www.cl=
.cam.ac.uk/%7Ead707/" target=3D"_blank">http://www.cl.cam.ac.uk/~ad707/</a>=
</div>
</div>

--047d7b41791ddd30df04f7393ed3--


From nobody Thu Apr 24 08:53:14 2014
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0C351A02CC; Thu, 24 Apr 2014 08:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.174
X-Spam-Level: 
X-Spam-Status: No, score=-7.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-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 zb1fgSCyuDhX; Thu, 24 Apr 2014 08:53:03 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 479821A0275; Thu, 24 Apr 2014 08:53:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.97,919,1389772800";  d="asc'?scan'208";a="160208690"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx12-out.netapp.com with ESMTP; 24 Apr 2014 08:52:55 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.246]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Thu, 24 Apr 2014 08:52:55 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: [Cfrg] CFRG Spring 2014 Interim Meeting on ECC: request for input
Thread-Index: AQHPVK366dNRiERB9Uyx6nA6sDk+iQ==
Date: Thu, 24 Apr 2014 15:52:54 +0000
Message-ID: <8E87CCDF-1797-4779-A770-F4AE05CF3E60@netapp.com>
References: <53467CEA.8070008@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.122.105.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_956C3310-FA97-44FF-9BDE-584E0C638E7E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/nlIyZFTG9ojSG867FMe2HW9FT9A
Subject: [irtf-discuss] Fwd: [Cfrg] CFRG Spring 2014 Interim Meeting on ECC: request for input
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 15:53:07 -0000

--Apple-Mail=_956C3310-FA97-44FF-9BDE-584E0C638E7E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

If you are interested in attending, you should also subscribe to the =
CFRG list at http://www.irtf.org/mailman/listinfo/cfrg for logistics and =
discussion.

Begin forwarded message:

> From: David McGrew <mcgrew@cisco.com>
> Subject: [Cfrg] CFRG Spring 2014 Interim Meeting on ECC: request for =
input
> Date: April 10, 2014 at 13:13:46 GMT+2
> To: "cfrg@irtf.org" <cfrg@irtf.org>, "Igoe, Kevin M." =
<kmigoe@nsa.gov>, Stephen Farrell <Stephen.Farrell@cs.tcd.ie>, =
"kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, Sean Turner =
<turners@ieca.com>, Joseph Salowey <jsalowey@cisco.com>, Eric Rescorla =
<ekr@rtfm.com>
>=20
> There is broad interest in the use of new elliptic curve cryptography =
mechanisms, and the Transport Layer Security (TLS) Working Group in =
particular has asked CFRG for input on what mechanisms are suitable for =
use in that protocol.   At the IETF89 meeting of the CFRG, it was =
decided to hold an interim meeting via teleconference, in order to allow =
more time for presentations and discussions on elliptic cryptography, =
and to also be more inclusive of CFRG members that do not typically =
attend IETF meetings. Presentations are invited on elliptic curve =
cryptography mechanisms (including both curves and algorithms), their =
security, their performance, and criteria for their selection and use in =
IETF standards.   Preference will be given to presentations that cover =
published documents, if time is limited.
>=20
> If you are interested in attending, please complete the doodle poll at =
http://doodle.com/cqg7eu9m3xugwrps and vote on the time and day for the =
meeting.   We are targeting  April 28 through May 2. Duration is to be =
determined by number of presenters, but the target will be two to three =
hours.
>=20
> If you are interested in presenting, respond to this email with a =
description of your presentation that includes a title, a short summary =
of the contents, and a duration.
>=20
> The meeting will use Webex (http://www.webex.com/), and participants =
should verify that they can use that software as needed to view or =
present slides.
>=20
> David and Kevin
>=20
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> http://www.irtf.org/mailman/listinfo/cfrg


--Apple-Mail=_956C3310-FA97-44FF-9BDE-584E0C638E7E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBU1kzWNZcnpRveo1xAQK+FwP9FbbbdiXNkGzCOJSiuGwau2FGhEB8pqxN
LKRYzP1NVXlQLkpLDLViSlCu3dcYmaF1CXt+KTCFx7vXvkv07D2rGo75G2ettMNT
2Kpru1juKFWhezi81ulrYSZr5X/d7LnKyxqwHKrs0QVJqQVZLxnSjz3Vua0G0sCI
HLCSJDpIKDA=
=6vrz
-----END PGP SIGNATURE-----

--Apple-Mail=_956C3310-FA97-44FF-9BDE-584E0C638E7E--


From nobody Fri Apr 25 09:03:46 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F20991A0658 for <irtf-discuss@ietfa.amsl.com>; Fri, 25 Apr 2014 09:03:41 -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=-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 xKTQZXzpcPcy for <irtf-discuss@ietfa.amsl.com>; Fri, 25 Apr 2014 09:03:39 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id E96971A0652 for <irtf-discuss@irtf.org>; Fri, 25 Apr 2014 09:03:36 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id i11so4407031oag.37 for <irtf-discuss@irtf.org>; Fri, 25 Apr 2014 09:03:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=LWMRTJsL5eEgs88wxObtOb23MJt0gC6JaPzccTX0Wxc=; b=nZ2ZssnwNL/do1tS1tTr4zCRCb5hZYq1WnKnx4W9ynm7/nmzHT1kjoMRetC1P+w2AY fQnaWM4ZCXPSoMDzZwEQO7zQ/Edme2QBjXWUY+hPgBw/cVwQDkd/Y/T/HVbvupwy9IKB T9wJuVtqzPdT+v/iamt0fTP43nYOyAaILYkpsWJaglIIpNDaMQd601CbXxlLGc7eIO68 Z/8hwyXsO/LJ+VHLxNOKaP/0YCGoY0E7unyecd7DbPBtjOVV+WozV1D5DFM6lXcKAULh cJvlda1F6bvW5NAusJbYqlnOTXrrcKeGgzjtWu+VkhvQ2Cn6p6XWVlGhuAr1VEMFVfl8 wwgA==
X-Received: by 10.182.219.167 with SMTP id pp7mr1017623obc.85.1398441810337; Fri, 25 Apr 2014 09:03:30 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id dh8sm33304406oeb.10.2014.04.25.09.03.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Apr 2014 09:03:29 -0700 (PDT)
Message-ID: <535A8750.3010703@gmail.com>
Date: Fri, 25 Apr 2014 11:03:28 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IRTF Discuss <irtf-discuss@irtf.org>
References: <20140416183211.14488.3655.idtracker@ietfa.amsl.com> <534ECE74.4080705@gmail.com>
In-Reply-To: <534ECE74.4080705@gmail.com>
Content-Type: multipart/alternative; boundary="------------060908030205070805000807"
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/nUOC2Z0FACC-9jVdSS02HtxcVoc
Subject: Re: [irtf-discuss] Request for feedback on "An IRTF Primer for IETF Participants"
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 16:03:42 -0000

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

Just following up ... any thoughts on this draft?

Thanks,

Spencer

On 04/16/2014 01:39 PM, Spencer Dawkins wrote:
> Lars and I have been talking for an embarrassingly long time about a 
> draft to help IETF folk who are proposing work in the IRTF, and that's 
> finally happened.
>
> Please comment (either on this list or privately is fine) about 
> whether the document seems helpful based on your experience, and 
> whether there are other things we should include.
>
> Thanks,
>
> Spencer, as an editor
>
> -------- Original Message --------
> Subject: 	[irsg] New Version Notification - 
> draft-dawkins-irtf-newrg-01.txt
> Date: 	Wed, 16 Apr 2014 11:32:11 -0700
> From: 	internet-drafts@ietf.org
> To: 	irtf@irtf.org, IRSG <irsg@irtf.org>
>
>
>
> A new version (-01) has been submitted for draft-dawkins-irtf-newrg:
> http://www.ietf.org/internet-drafts/draft-dawkins-irtf-newrg-01.txt
>
>
> The IETF datatracker page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-dawkins-irtf-newrg/
>
> Diff from previous version:
> http://www.ietf.org/rfcdiff?url2=draft-dawkins-irtf-newrg-01
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> IETF Secretariat.
>
>
>


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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Just following up ... any thoughts on this draft?<br>
    <br>
    Thanks,<br>
    <br>
    Spencer<br>
    <br>
    <div class="moz-cite-prefix">On 04/16/2014 01:39 PM, Spencer Dawkins
      wrote:<br>
    </div>
    <blockquote cite="mid:534ECE74.4080705@gmail.com" type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      Lars and I have been talking for an embarrassingly long time about
      a draft to help IETF folk who are proposing work in the IRTF, and
      that's finally happened.<br>
      <br>
      Please comment (either on this list or privately is fine) about
      whether the document seems helpful based on your experience, and
      whether there are other things we should include.<br>
      <br>
      Thanks,<br>
      <br>
      Spencer, as an editor<br>
      <div class="moz-forward-container"><br>
        -------- Original Message --------
        <table class="moz-email-headers-table" border="0"
          cellpadding="0" cellspacing="0">
          <tbody>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:

              </th>
              <td>[irsg] New Version Notification -
                draft-dawkins-irtf-newrg-01.txt</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date:
              </th>
              <td>Wed, 16 Apr 2014 11:32:11 -0700</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From:
              </th>
              <td><a moz-do-not-send="true"
                  class="moz-txt-link-abbreviated"
                  href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
              <td><a moz-do-not-send="true"
                  class="moz-txt-link-abbreviated"
                  href="mailto:irtf@irtf.org">irtf@irtf.org</a>, IRSG <a
                  moz-do-not-send="true" class="moz-txt-link-rfc2396E"
                  href="mailto:irsg@irtf.org">&lt;irsg@irtf.org&gt;</a></td>
            </tr>
          </tbody>
        </table>
        <br>
        <br>
        <pre>A new version (-01) has been submitted for draft-dawkins-irtf-newrg:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-dawkins-irtf-newrg-01.txt">http://www.ietf.org/internet-drafts/draft-dawkins-irtf-newrg-01.txt</a>


The IETF datatracker page for this Internet-Draft is:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-dawkins-irtf-newrg/">https://datatracker.ietf.org/doc/draft-dawkins-irtf-newrg/</a>

Diff from previous version:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-dawkins-irtf-newrg-01">http://www.ietf.org/rfcdiff?url2=draft-dawkins-irtf-newrg-01</a>

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.

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

--------------060908030205070805000807--


From nobody Sat Apr 26 05:26:21 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89F31A04C5 for <irtf-discuss@ietfa.amsl.com>; Sat, 26 Apr 2014 05:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 Uxe_lXlmje9j for <irtf-discuss@ietfa.amsl.com>; Sat, 26 Apr 2014 05:26:17 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id ADE791A048F for <irtf-discuss@irtf.org>; Sat, 26 Apr 2014 05:26:17 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id vb8so5483405obc.29 for <irtf-discuss@irtf.org>; Sat, 26 Apr 2014 05:26:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=QNbH6FNKOoB3mp0MZIsHZAyi1Y5FloQM4/vKqsIdpTM=; b=cBPWn/YSvoNcNXTsJX5UnBUMAIZUhxz0tQ7CX595Ro6mekYmbA34fzNsNFrylFv7m7 SdxU58Tdk9LigbnYCvL2gBAOIDKbw7dz27a1OHxKdjBuou7mSZRpZStyM9fN8/Y0p8mq URNRj5sCgPDOoROyzqTcIVjYp82545Bn9wGMnDPPN770RwGQD4k3dIXFdXeTPnNvjO/J awd1w85RNwQQT5D8eZ2m7N9O6IHNiE7I+rFphCvtZlRDBALD4bNV6OBA+uHl2Z3l2fOC 5ZTUPneGba5J019oxQ0cck8mh7tyUIqFbDohGeZ+PF3ynHo27/1x0jh2Bg9wGym0otDL MMNg==
X-Received: by 10.182.230.135 with SMTP id sy7mr12238357obc.24.1398515170723;  Sat, 26 Apr 2014 05:26:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.183.8.7 with HTTP; Sat, 26 Apr 2014 05:25:49 -0700 (PDT)
In-Reply-To: <535A8750.3010703@gmail.com>
References: <20140416183211.14488.3655.idtracker@ietfa.amsl.com> <534ECE74.4080705@gmail.com> <535A8750.3010703@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 26 Apr 2014 08:25:49 -0400
Message-ID: <CAPv4CP9GGSF_sRro4ba+L0_04bbnLNbXn04iCST1SmT-+ahDrg@mail.gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/CgbvLvfV_sOVP5RtISVlPnZ_oaI
Cc: IRTF Discuss <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] Request for feedback on "An IRTF Primer for IETF Participants"
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 12:26:20 -0000

Spencer (and Lars),

Section 2 is "the IRTF is not the IETF", and talks about what an RG
does NOT need to do, and MAY do. I suggest you add a section 3 which
gathers up the threads started in Section 2 and describes briefly what
IS expected in a request to start an RG - just to give a feeling of
what the flow would be like.

I did wonder how much of what's listed is essential, invariant versus
how the current IRTF chair likes to do things. That's Lars's call.
Perhaps the next IRTF chair can produce a revision.

Finally,

      "I work in research and engineering.  When we finish a project, if
      it works, it was engineering.  If it doesn't work, it was
      research." - anon

Well, I remember Dave Clark saying (to Noel maybe?), "If it has to
work when you're done, it's not research, it's engineering."

Scott


From nobody Sat Apr 26 10:31:37 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D18CF1A0654 for <irtf-discuss@ietfa.amsl.com>; Sat, 26 Apr 2014 10:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 ul8PaQpmdq1K for <irtf-discuss@ietfa.amsl.com>; Sat, 26 Apr 2014 10:31:34 -0700 (PDT)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 558F71A0639 for <irtf-discuss@irtf.org>; Sat, 26 Apr 2014 10:31:34 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id j17so5589855oag.14 for <irtf-discuss@irtf.org>; Sat, 26 Apr 2014 10:31:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=fJU7ILp/PmCYHCBminEK85vlWYSk9LyHGrkWJAgb+DE=; b=ABBEGni1UE6VQF1TFl+n0qZimyAAcDYOpkVWEYs/oj4Ats0SL/PVnFCCR0Z3TgQFR2 +wdmAJj8MkWtX+zQUcYLrTCYpvp7wpgkNK01+34aMyzVUto6qgcsmM0hH65cFBcxG8dR oUf0XS0WIdzVe4lN/QhNYOZf9hXtTi2chBNadCmVR8GEIvbLJvhJp6R55uH5c6zuvvQQ McnTMJbkiIl9HBal9JLUdc9uaSLCEJbhQ1ZkCJuhNSqDPcVC1kgqq+r5R2NDkTW0Yr/A qyUkz7EDsT0ozqaujzV6swxpfpkFsXsdKDBV3tyYdojYZ7rqQz6GvEqTMhWKhQwP986R cBFA==
X-Received: by 10.182.28.195 with SMTP id d3mr13273142obh.19.1398533487370; Sat, 26 Apr 2014 10:31:27 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id dg2sm23859634obb.17.2014.04.26.10.31.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 26 Apr 2014 10:31:26 -0700 (PDT)
Message-ID: <535BED6C.2090302@gmail.com>
Date: Sat, 26 Apr 2014 12:31:24 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
References: <20140416183211.14488.3655.idtracker@ietfa.amsl.com> <534ECE74.4080705@gmail.com> <535A8750.3010703@gmail.com> <CAPv4CP9GGSF_sRro4ba+L0_04bbnLNbXn04iCST1SmT-+ahDrg@mail.gmail.com>
In-Reply-To: <CAPv4CP9GGSF_sRro4ba+L0_04bbnLNbXn04iCST1SmT-+ahDrg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/s4lgbayZg2l-ArZwm8LaQq3XrIU
Cc: IRTF Discuss <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] Request for feedback on "An IRTF Primer for IETF Participants"
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 17:31:36 -0000

Hi, Scott,

Thanks for the comments! I knew I wasn't finished.


On 04/26/2014 07:25 AM, Scott Brim wrote:
> Spencer (and Lars),
>
> Section 2 is "the IRTF is not the IETF", and talks about what an RG
> does NOT need to do, and MAY do. I suggest you add a section 3 which
> gathers up the threads started in Section 2 and describes briefly what
> IS expected in a request to start an RG - just to give a feeling of
> what the flow would be like.

Lars has moved close enough to "act like an RG and we'll see if you are 
one" that I'm not sure how much more I can say about an expected flow. 
I'll think that over, and at a minimum, pull that quote out into a 
section 3 and explain it with pointers.

> I did wonder how much of what's listed is essential, invariant versus
> how the current IRTF chair likes to do things. That's Lars's call.
> Perhaps the next IRTF chair can produce a revision.

I wasn't working closely with IRTF RGs before Aaron Falk was IRTF chair, 
so my sample size is "2", but even based on that small sample, I agree 
with the observation that this doc is going to be "the Lars Edition". 
That's definitely worth pointing out.

> Finally,
>
>        "I work in research and engineering.  When we finish a project, if
>        it works, it was engineering.  If it doesn't work, it was
>        research." - anon
>
> Well, I remember Dave Clark saying (to Noel maybe?), "If it has to
> work when you're done, it's not research, it's engineering."

That's a better quote than the one I had for the point I'm making. I'll 
make the substitution. If you have any context (like roughly a year), 
I'd add that, too.

Thanks again,

Spencer

