Skip to main content

PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)
draft-ietf-nea-pb-tnc-06

Yes

(Tim Polk)

No Objection

(Adrian Farrel)
(Lars Eggert)
(Magnus Westerlund)
(Pasi Eronen)
(Ross Callon)
(Russ Housley)

Note: This ballot was opened for revision 06 and is now closed.

Tim Polk Former IESG member
Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
No Objection
No Objection () Unknown

                            
Alexey Melnikov Former IESG member
(was Discuss) No Objection
No Objection (2009-10-25) Unknown
After talking to Tim about the issue I downgraded this to a comment:
Should the expert review be required for Vendor specific registrations?
Lars Eggert Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Magnus Westerlund Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Pasi Eronen Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
(was Discuss) No Objection
No Objection (2009-07-15) Unknown
Is there a reason that the Field Types defined in the PA-TNC document
are not defined and used in this document?  I guess the only two types
that are used in this doc are Integer and String (perhaps OctetArray,
which is used in the definition of string>).

And, my curiosity is piqued by the choices of 16-bit versus 32-bit
integers in various places, as well as the placement of various
"Reserved" fields to the left or the right of some data fields.

Section 4.6: The list of PB-Access-Recommendation codes cannot be
extended; therefore this document does not request IANA to establish a
registry.  I think the list of PB-Assessment-Result codes also cannot
be extended.  Should there be a similar note about not establishing a
registry? 

Nit: The citations to the reference entries for RFC 5209 and the
PA-TNC specification are not attached to the first mentions of those
docs; I assume the RFC Editor catches those editorial issues.
Robert Sparks Former IESG member
(was Discuss) No Objection
No Objection (2009-10-26) Unknown
I still find the mechanics of establishing and maintaining subscriptions very underspecified, but yield to the strong opinions of those closer to this work that such specification (and interoperability between these elements) is not needed.
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
(was Discuss) No Objection
No Objection (2009-08-10) Unknown