TCP Friendly Rate Control (TFRC): Protocol Specification
RFC 5348

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

Lars Eggert Yes

(Magnus Westerlund) (was No Objection) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Ross Callon) No Objection

(Lisa Dusseault) No Objection

(Pasi Eronen) No Objection

(Russ Housley) (was Discuss) No Objection

(Cullen Jennings) No Objection

(Chris Newman) No Objection

(Jon Peterson) No Objection

(Tim Polk) No Objection

Comment (2008-05-22)
No email
send info
I support Russ's discuss on the importance of a change summary.  Having diffed the
RFC and the ID, this appears to be a very significant revision covering many issues.
The change summary will help ensure readers find the appropriate changes.

It would be nice if the security considerations section was updated with some examples.
The document punts most security issues  to the "specific transport protocol and its
authentication mechanisms" and that is probably appropriate.  However, I would assume
that the details have been worked out for TCP since publication of 3448, and that
references to those solutions could easily be included.  That would be helpful in my opinion.

(Dan Romascanu) No Objection

(Mark Townsley) No Objection