Procedures for Maintaining the Time Zone Database
RFC 6557

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

(David Harrington; former steering group member) (was Discuss) Yes

Yes ()
No email
send info

(Pete Resnick; former steering group member) Yes

Yes (2011-05-10 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I don't particularly see the point of the 2119 language in the document. It doesn't add anything for me. I wouldn't mind seeing it go. Otherwise, I think the procedures defined here are spot on.

(Peter Saint-Andre; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Ralph Droms; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Robert Sparks; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Ron Bonica; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Russ Housley; former steering group member) (was Discuss) Yes

Yes ()
No email
send info

(Sean Turner; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Stephen Farrell; former steering group member) Yes

Yes (2011-05-10 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I like that the IETF & IANA are helping here. 

Bunch of near-nits below.

(1) Maybe add pointers to the current and new TZ lists and archives?
It looks like this document also has consensus or at least no objections 
on the current list btw - I took a quick peek:-)

(2) s/a well known key/well known public keys/ - there's an unfortunate 
trend these days to use sign for MACs as well and I'm not sure you 
want to say that the code and DB SHOULD use the same signing key

(3) Maybe add "key" to the terminology saying its sometimes a DB 
key and sometimes (once?) a signing key and if you can't tell which, 
then you should start reading RFCs somewhere else:-)

(4) "timezone policy policy" might be worth adding to the terminology 
section since it could otherwise be seen as a typo

(5) s/signature of an identity/signature verifiable by a public key/

(6) I guess the TZ Coordinator won't want to be "filled" except maybe 
with beer - I guess adding the word "role" there will fix that.

(7) s/maintain a cryptographic identity/securely maintain a cryptographic 
private key/

(Adrian Farrel; former steering group member) (was Discuss) No Objection

No Objection (2011-05-12)
No email
send info
Abstract                                

s/semantic meanings/semantics/

(Dan Romascanu; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Gonzalo Camarillo; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Stewart Bryant; former steering group member) No Objection

No Objection (2011-05-11 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Just a couple of minor points:

NIH is used in the introduction but not defined.

"the TZ mailing list" is not defined

(Wesley Eddy; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info