[Ghost] Proposed Structure for Organizing Standards Information

"Boyle, Vincent M" <vmboyle@nsa.gov> Tue, 11 August 2015 18:05 UTC

Return-Path: <vmboyle@nsa.gov>
X-Original-To: ghost@ietfa.amsl.com
Delivered-To: ghost@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 76DF41ACE67 for <ghost@ietfa.amsl.com>; Tue, 11 Aug 2015 11:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Vo8yvWLD_Qga for <ghost@ietfa.amsl.com>; Tue, 11 Aug 2015 11:05:26 -0700 (PDT)
Received: from emvm-gh1-uea09.nsa.gov (emvm-gh1-uea09.nsa.gov []) by ietfa.amsl.com (Postfix) with ESMTP id 423F11ACE61 for <ghost@ietf.org>; Tue, 11 Aug 2015 11:05:26 -0700 (PDT)
X-TM-IMSS-Message-ID: <0ab6feb200041d0d@nsa.gov>
Received: from MSHT-GH1-UEA02.corp.nsa.gov (msht-gh1-uea02.corp.nsa.gov []) by nsa.gov ([]) with ESMTP (TREND IMSS SMTP Service 7.1; TLSv1/SSLv3 AES128-SHA (128/128)) id 0ab6feb200041d0d ; Tue, 11 Aug 2015 14:10:40 -0400
Received: from MSMR-GH1-UEA04.corp.nsa.gov ( by MSHT-GH1-UEA02.corp.nsa.gov ( with Microsoft SMTP Server (TLS) id 14.2.347.0; Tue, 11 Aug 2015 14:05:24 -0400
Received: from MSMR-GH1-UEA02.corp.nsa.gov ([]) by MSMR-GH1-UEA04.corp.nsa.gov ([]) with mapi id 14.02.0347.000; Tue, 11 Aug 2015 14:05:24 -0400
From: "Boyle, Vincent M" <vmboyle@nsa.gov>
To: "'ghost@ietf.org'" <ghost@ietf.org>
Thread-Topic: Proposed Structure for Organizing Standards Information
Thread-Index: AdDUXcxXhzNIWmXZT0+Nzz8oLTVF3g==
Date: Tue, 11 Aug 2015 18:05:23 +0000
Message-ID: <E18BF42C3D667642ABC0EF4B6064EB67D1D69191@MSMR-GH1-UEA02.corp.nsa.gov>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ghost/E8AX-VsuvU5QiGWW2N0747cFLF4>
Subject: [Ghost] Proposed Structure for Organizing Standards Information
X-BeenThere: ghost@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for GatHering and reOrganizing STandards information \(GHOST\) team" <ghost.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ghost>, <mailto:ghost-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ghost/>
List-Post: <mailto:ghost@ietf.org>
List-Help: <mailto:ghost-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ghost>, <mailto:ghost-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2015 18:05:29 -0000

I read the Google doc again this morning. I like the idea of a short introduction to each topic and then moving on to specific situations (use cases and device types; maybe deployment scenarios as well, such as how big is the set of things that have to authenticate to each other, or how will keys be provisioned). In general, I like the idea of quickly getting to specifics and providing pointers to appropriate standards.

I'm wondering if we need to work through the Authentication example a bit. Maybe create a part of the matrix (no attempt to be complete) and then see how we would handle things from there. I think even concentrating on a specific scenario (signed email) could be enlightening, considering the differences when you're all part of an enterprise vs. a community with no central authority.

 If it would help, I'd be happy to join a phone call to discuss. Otherwise, maybe somebody more adept than me could create a small example to foster discussion.

Mike Boyle