Skip to main content

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

Yes

Lars Eggert
(Magnus Westerlund)

No Objection

(Chris Newman)
(Cullen Jennings)
(Dan Romascanu)
(Jari Arkko)
(Jon Peterson)
(Lisa Dusseault)
(Mark Townsley)
(Pasi Eronen)
(Ron Bonica)
(Ross Callon)
(Russ Housley)

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

Lars Eggert Yes

(Magnus Westerlund; former steering group member) (was No Objection) Yes

Yes ()

                            

(Chris Newman; former steering group member) No Objection

No Objection ()

                            

(Cullen Jennings; former steering group member) No Objection

No Objection ()

                            

(Dan Romascanu; former steering group member) No Objection

No Objection ()

                            

(Jari Arkko; former steering group member) No Objection

No Objection ()

                            

(Jon Peterson; former steering group member) No Objection

No Objection ()

                            

(Lisa Dusseault; former steering group member) No Objection

No Objection ()

                            

(Mark Townsley; former steering group member) No Objection

No Objection ()

                            

(Pasi Eronen; former steering group member) No Objection

No Objection ()

                            

(Ron Bonica; former steering group member) No Objection

No Objection ()

                            

(Ross Callon; former steering group member) No Objection

No Objection ()

                            

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection ()

                            

(Tim Polk; former steering group member) No Objection

No Objection (2008-05-22)
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.