Skip to main content

Procedures for Maintaining the Time Zone Database
draft-lear-iana-timezone-database-05

Yes

(David Harrington)
(Peter Saint-Andre)
(Ralph Droms)
(Robert Sparks)
(Ron Bonica)
(Russ Housley)
(Sean Turner)

No Objection

(Dan Romascanu)
(Gonzalo Camarillo)
(Jari Arkko)
(Wesley Eddy)

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

David Harrington Former IESG member
(was Discuss) Yes
Yes () Unknown

                            
Pete Resnick Former IESG member
Yes
Yes (2011-05-10) Unknown
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 IESG member
Yes
Yes () Unknown

                            
Ralph Droms Former IESG member
Yes
Yes () Unknown

                            
Robert Sparks Former IESG member
Yes
Yes () Unknown

                            
Ron Bonica Former IESG member
Yes
Yes () Unknown

                            
Russ Housley Former IESG member
(was Discuss) Yes
Yes () Unknown

                            
Sean Turner Former IESG member
Yes
Yes () Unknown

                            
Stephen Farrell Former IESG member
Yes
Yes (2011-05-10) Unknown
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 IESG member
(was Discuss) No Objection
No Objection (2011-05-12) Unknown
Abstract                                

s/semantic meanings/semantics/
Dan Romascanu Former IESG member
No Objection
No Objection () Unknown

                            
Gonzalo Camarillo Former IESG member
No Objection
No Objection () Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection () Unknown

                            
Stewart Bryant Former IESG member
No Objection
No Objection (2011-05-11) Unknown
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 IESG member
No Objection
No Objection () Unknown