Integrity Transform Carrying Roll-Over Counter for the Secure Real-time Transport Protocol (SRTP)
RFC 4771

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

(Russ Housley) Yes

(Jari Arkko) No Objection

(Ross Callon) No Objection

(Brian Carpenter) No Objection

(Lars Eggert) No Objection

(Bill Fenner) No Objection

(Ted Hardie) No Objection

(Sam Hartman) No Objection

Comment (2006-09-13 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
It's unfortunate that this integrity transform needs to be coupled to
a choice of hash.  That means that in the future we'll end up with a
lot of integrity transforms if we need new hashes.  However that seems
like the best design tradeoff available to us.

(Cullen Jennings) (was Discuss) No Objection

(David Kessens) No Objection

(Jon Peterson) No Objection

(Dan Romascanu) No Objection

Comment (2006-09-10 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The write-up mentions that 'The RoC is carried in every rth packet, which is bandwidth-sensitive'. I cannot find any mention in the document about this issue. Is there any impact on the applications or network operation, like an increase in bandwidth consumption to care about, or is this only about consuming a number of bits in the header to carry the RoC?

Magnus Westerlund (was Discuss) No Objection