Draft: draft-ietf-sipping-overload-reqs-01
Reviewer: Brett Tate
Review Date: Jan 9, 2007
Review Deadline: Jan 23, 2007
Status: WGLC

Summary: Ready.  I look forward to seeing the solution which satisfies the requirements.

Comments:
REQ 13 nit: "of of".

REQ 22: Nice goal.  However depending upon how the two devices interact and are connected, it will likely be easy to deduce which device is overloaded or temporarily having issues unless able to potentially blame another device.  Additionally, a 503 is currently the only SIP response able to trigger target advancing per RFC 3263.  Does REQ 22 preclude sending a 503 or only preclude sending 503 containing load information decipherable by non desirable receivers?