Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)
RFC 4279

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

(Sam Hartman) (was Discuss) Yes

(Russ Housley) Yes

(Allison Mankin) Yes

Comment (2005-05-26 for -)
No email
send info
Glad to see this, it has been needed.  It might be useful to state that examples of identities form
a very partial list and that URIs and user@... (anything that can be expressed as a UTF-8 string),
can be an identity.  The requirements for inputting the identity allow many applications to use
this.  An RFC Editor note could easily add this, if you feel the clarification would help.

(Brian Carpenter) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ted Hardie) No Objection

Comment (2005-06-03 for -)
No email
send info
The document says:

   IANA does not currently have a registry for TLS-related numbers, so
   there are no IANA actions associated with this document.

Note that IANA does have a TLS-related compression registry:

http://www.iana.org/assignments/comp-meth-ids

(Scott Hollenbeck) No Objection

(David Kessens) (was Discuss, No Objection) No Objection

(Jon Peterson) No Objection

(Mark Townsley) No Objection

(Bert Wijnen) No Objection

Comment (2005-05-25 for -)
No email
send info
sect 5.1 has as first bullet:

   o  IPv4 addresses are sent as dotted-decimal strings (e.g.,
      "192.0.1.2"), not as 32-bit integers in network byte order.

Probably better to adhere to RFC3330 and use 192.0.2.1 or some
other address in the 192.0.2.0/24 range.

(Alex Zinin) No Objection