The SEED Cipher Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)
draft-ietf-avt-seed-srtp-14
Yes
(Cullen Jennings)
No Objection
(Adrian Farrel)
(Lars Eggert)
(Lisa Dusseault)
(Pasi Eronen)
(Ralph Droms)
(Robert Sparks)
(Ron Bonica)
(Ross Callon)
(Tim Polk)
Note: This ballot was opened for revision 14 and is now closed.
Cullen Jennings Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
()
Unknown
Alexey Melnikov Former IESG member
(was Discuss)
No Objection
No Objection
(2009-06-12)
Unknown
In Section 5: OLD: An RTP implementation that supports SEED, it MUST implement the modes listed in Section 5. NEW: An RTP implementation that supports SEED MUST implement the modes listed in Section 5 of this document.
Jari Arkko Former IESG member
No Objection
No Objection
(2009-06-04)
Unknown
IANA considerations have to be fixed, as other ADs have already noted.
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Unknown
Magnus Westerlund Former IESG member
No Objection
No Objection
(2009-06-01)
Unknown
I would like to support Alexey's Discuss regarding IANA registration. It seems to me to be an unnecessary complexity to define the algorithm in one place and not register the necessary identifiers with the key-management. Sure SRTP has several keying mechanisms. However, this question should be well thought through as there may be issues down the road in publishing this as informational status. From RFC 4568: 10.3.2.1. SRTP Crypto Suite Registry and Registration The IANA has created a new subregistry for SRTP crypto suites under the SRTP transport of the SDP Security Descriptions. An IANA SRTP crypto suite registration MUST indicate the crypto suite name in accordance with the grammar for srtp-crypto-suite-ext defined in Section 9.2. The semantics of the SRTP crypto suite MUST be described in an RFC in accordance with the RFC 2434 Standards Action, including the semantics of the "inline" key-method and any special semantics of parameters. This may be a qualified downref for a future standards track document to register the crypto suit identifiers. But it should be considered now.
Pasi Eronen Former IESG member
(was Discuss)
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-03)
Unknown
I agree with the DISCUSS ballot position already provided by Alexey. In particular, Section 5 must be clarified. The SEED algorithm is not mandatory-to-implement for all RTP implementations. However, an RTP implementation that supports SEED, it must implement the modes listed in Section 5.
Tim Polk Former IESG member
(was No Record, Discuss)
No Objection
No Objection
()
Unknown