Guidance for Authentication, Authorization, and Accounting (AAA) Key Management
RFC 4962

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

Lars Eggert No Objection

(Jari Arkko; former steering group member) (was Discuss) Yes

Yes (2007-02-12)
No email
send info
My Discuss has been cleared based on the new version -07 that Russ Housley prepared.

(Sam Hartman; former steering group member) (was Discuss, Yes) Yes

Yes ()
No email
send info

(Bill Fenner; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Brian Carpenter; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Chris Newman; former steering group member) No Objection

No Objection (2007-04-26)
No email
send info
Minor comments:

Section 2, last paragraph:
OLD:
   however, other parties may receive keys that is derived from this
                                                ^^
NEW:
   however, other parties may receive keys that are derived from this

Section 3,
>      Cryptographic algorithm independent

Although this section implies hash function agility is required, it might be clearer to make that explicit.

(Cullen Jennings; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Dan Romascanu; former steering group member) No Objection

No Objection (2007-01-11 for -)
No email
send info
(contributed by AAA doctor David Nelson who reviewed the document and is confortable with its content). 

The following text in Section 2 seems to be duplicated, and should probably show up only once: 

   However, due to ad hoc development of AAA-
   based key management, AAA-based key distribution schemes have poorly
   understood security properties, even when well-studied cryptographic
   algorithms are employed.  More academic research is needed to fully
   understand the security properties of AAA-based key management in the
   diverse protocol environments where it is being employed today.  In
   the absence of research results, pragmatic guidance based on sound
   security engineering principles is needed.

(David Kessens; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Jon Peterson; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Lisa Dusseault; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Mark Townsley; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Ted Hardie; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Russ Housley; former steering group member) Recuse

Recuse ( for -)
No email
send info