Skip to main content

Generic Security Service API Version 2: Java Bindings Update
draft-ietf-kitten-rfc2853bis-05

Yes

(Tim Polk)

No Objection

(Adrian Farrel)
(Alexey Melnikov)
(Cullen Jennings)
(Dan Romascanu)
(Jari Arkko)
(Lars Eggert)
(Lisa Dusseault)
(Ralph Droms)
(Robert Sparks)
(Ron Bonica)
(Ross Callon)

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

Tim Polk Former IESG member
Yes
Yes () Unknown

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

                            
Alexey Melnikov Former IESG member
No Objection
No Objection () Unknown

                            
Cullen Jennings Former IESG member
No Objection
No Objection () Unknown

                            
Dan Romascanu Former IESG member
(was Discuss) No Objection
No Objection () Unknown

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

                            
Lars Eggert Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Lisa Dusseault Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
No Objection
No Objection () Unknown

                            
Robert Sparks Former IESG member
No Objection
No Objection () Unknown

                            
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection (2009-06-02) Unknown
  Please consider the places where "service@host" is used in examples.
  It would be better to use the domain names in RFC 2606 in examples.


  The Gen-ART Review by Gonzalo Camarillo on 2-Jun-2009 included a few
  comments that shoule be considered:

  In general, Abstracts should not contain references. While referencing
  RFC 2853 to explain that this document obsoletes it is probably OK, I
  would remove the rest of the references from the Abstract.

  The naming of the references is not consistent. Some of them are named
  [RFCxxxx] but not all of them.

  In Section 4, a ':' to introduce the definition of each optional
  service would probably make the text clearer (e.g., Mutual
  Authentication: in addition...)

  The word "Section" should be capitalized when referring to a specific
  section (e.g., in Section 8).

  The ID nits tool makes a few observations about boilerplates. The
  authors should make sure that the boilerplates in the draft are okay.