Skip to main content

Telechat Review of draft-turner-est-extensions-08

Request Review of draft-turner-est-extensions
Requested revision No specific revision (document currently at 11)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2017-07-04
Requested 2017-05-22
Authors Sean Turner
I-D last updated 2017-07-10
Completed reviews Genart Telechat review of -08 by Vijay K. Gurbani (diff)
Secdir Telechat review of -08 by Scott G. Kelly (diff)
Opsdir Telechat review of -08 by Qin Wu (diff)
Assignment Reviewer Vijay K. Gurbani
State Completed
Request Telechat review on draft-turner-est-extensions by General Area Review Team (Gen-ART) Assigned
Reviewed revision 08 (document currently at 11)
Result Ready w/nits
Completed 2017-07-10
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at


Document: draft-turner-est-extensions-??
Reviewer: Vijay Gurbani
Review Date: 2017-07-10
IETF LC End Date: 2017-07-11
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with nits.

Major issues: 0

Minor issues: 1

Nits/editorial comments: 2

- S2, I understand that a PAL may be represented as a XML file or a JSON
 object, but I note that the underlying semantic content of the resource,
 irrespective of representation as shown in Sections 2.1.2 and 2.1.3 is
 different.  I suspect that is by design, but could not figure out why the
 XML and JSON resource would have different semantic content.

- S1, top of page 5: What is TA?  The expansion is not defined before being
 used here for the first time; I suspect it is "Trust Anchor", but may help
 to expand it here rather than in S7.

- S1.1, "air gap" --- I understand what it means from rfc4949, but someone
 not familiar (or too lazy to look up rfc4949 or simply much too younger than
 us) may assume that "air gap" refers to "wifi".  Admittedly in 2007 when
 rfc4949 was written, 802.11{g,e,n} were just released [1], and only three
 years before, in 2004, Economist predicted that the worldwide market for WiFi
 devices in 2006 will be 50 million (!) [2].

 I don't know that we can do much here, but it was with some chuckle that
 the term "air gap" lead me to the statistics I mention above.