RE: Education and Information Sharing ... was Re: Transparency in Specifications and PRISM-class attacks

"Moriarty, Kathleen" <kathleen.moriarty@emc.com> Fri, 20 September 2013 17:24 UTC

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 BFBE621F9AED for <ietf@ietfa.amsl.com>; Fri, 20 Sep 2013 10:24: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=[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 EWRmVHPwijkW for <ietf@ietfa.amsl.com>; Fri, 20 Sep 2013 10:24:53 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 8356321F9BB6 for <ietf@ietf.org>; Fri, 20 Sep 2013 10:24:53 -0700 (PDT)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r8KHOfeC008733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Sep 2013 13:24:42 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com r8KHOfeC008733
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1379697883; bh=YLucelITpqzgD+h1wJH6zMwBNwE=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=HNg6hMtxiUjVz/pIb158VkFktaK5UnnBQULrlyZqPjspyhmx8/oavPEM3z6ATBkxZ oeNp0Dlk1XSzFQxCJr6bsCmciW6kpgdvIiBzlx+Maq3r4y3vjvuGB8kOVGbmTlmhgH 4sdS3JYpYZxhCMnq0BIxm4h+IgvqdPRuNLlOmnu4=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com r8KHOfeC008733
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd56.lss.emc.com (RSA Interceptor); Fri, 20 Sep 2013 13:24:34 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r8KHOXgX003840 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 20 Sep 2013 13:24:33 -0400
Received: from mxhub39.corp.emc.com (128.222.70.106) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.297.1; Fri, 20 Sep 2013 13:24:33 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub39.corp.emc.com ([128.222.70.106]) with mapi; Fri, 20 Sep 2013 13:24:33 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Date: Fri, 20 Sep 2013 13:24:32 -0400
Subject: RE: Education and Information Sharing ... was Re: Transparency in Specifications and PRISM-class attacks
Thread-Topic: Education and Information Sharing ... was Re: Transparency in Specifications and PRISM-class attacks
Thread-Index: Ac62JW1iWhRtl2VCROOG6pQCL2XfxwAAH+TA
Message-ID: <F5063677821E3B4F81ACFB7905573F24049E7A6E75@MX15A.corp.emc.com>
References: <CAMm+LwiYy1xVGFvcKNbmLEEWcnHns70CS6aH9zV4B0Xqg-OWOw@mail.gmail.com> <523C216A.8030305@alvestrand.no> <523C339F.9080205@gmx.net> <F5063677821E3B4F81ACFB7905573F24049E7A6E05@MX15A.corp.emc.com> <523C8350.7010002@gmx.net>
In-Reply-To: <523C8350.7010002@gmx.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-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-EMM-GWVC: 1
X-EMM-McAfeeVC: 1
X-RSA-Classifications: DLM_1, public
Cc: "harald@alvestrand.no" <harald@alvestrand.no>, "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, 20 Sep 2013 17:24:58 -0000

Hi Hannes,

I would also like to reach developers that may not be familiar with the IETF and find themselves assigned with developing protocols we designed.  I'll see if I (or my co-chair) can get something together in short order.  ENISA was reviewing materials and asked for this type of information.  For our work, they are an important group that have not been attending meetings, but do follow the work.  

Thanks,
Kathleen

-----Original Message-----
From: Hannes Tschofenig [mailto:hannes.tschofenig@gmx.net] 
Sent: Friday, September 20, 2013 1:18 PM
To: Moriarty, Kathleen
Cc: Hannes Tschofenig; harald@alvestrand.no; ietf@ietf.org
Subject: Education and Information Sharing ... was Re: Transparency in Specifications and PRISM-class attacks

Hi Kathleen,

you are responding to the question about the target audience* and I saw your video. That's an interesting idea to reach out to those who are not yet involved in an IETF group.

Of course, our working group pages and the Wikis are not necessarily are great way to communicate with people other than our main target audience.

There is indeed something we could improve and I had in fact given a presentation about this topic to the IAB at the retreat this year. Here are the slides:
http://www.tschofenig.priv.at/IAB_Work_Style.pdf

Ciao
Hannes

PS: I got the impression from Harald's response that he was actually thinking about a different audience. Of course, the audience determines the content.

On 20.09.2013 17:28, Moriarty, Kathleen wrote:
> From my experience, some people not as familiar with the IETF have 
> trouble understanding how to fit RFCs together.  That leads to a 
> readability problem in itself.  Some also don't realize that you can 
> reference part of one RFC and not the whole thing rather than 
> reinventing the wheel or documenting something again.
>
> For MILE, we had several requests to pull together descriptions on how 
> the drafts&  RFCs fit together.  We did a short video, but need to get 
> a wiki or something together to assist.  In light of the current 
> thread, I think it is important to include in that the current set of 
> security protections in case they are not adequate and it gets 
> someone's attention who is interested to help improve things (even 
> just through critiques).  We will try to get this together in a wiki 
> soon.  If it helps readability, maybe to would be good for others to 
> consider?
>
> Thanks, Kathleen
>
> -----Original Message----- From: ietf-bounces@ietf.org 
> [mailto:ietf-bounces@ietf.org] On Behalf Of Hannes Tschofenig Sent:
> Friday, September 20, 2013 7:38 AM To: harald@alvestrand.no Cc:
> ietf@ietf.org Subject: Re: Transparency in Specifications and 
> PRISM-class attacks
>
> On 20.09.2013 13:20, Harald Alvestrand wrote:
>> To my mind, the first thing to focus on is making our specs readable, 
>> so that it's possible to understand that they have not been 
>> compromised.
>
> Three questions for you Harald:
>
> 1) When you say that our documents have to be "readable" then you have 
> to say readable by whom? Of course, most of our documents are tailored 
> to those who implement rather than to, let's say, someone who has 
> little understanding of Internet technology in general.
>
> 2) Are there documents you find non-readable?
>
> 3) Do you have any reasons to believe that there are documents that 
> have been compromised?
>
>