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
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
Precedence: list

I read the Google doc again this morning. I like the idea of a short introd=
uction to each topic and then moving on to specific situations (use cases a=
nd 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 spec=
ific scenario (signed email) could be enlightening, considering the differe=
nces 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 d=
iscussion.

Mike Boyle