Draft:  draft-ietf-sipping-sbc-funcs-01.txt
Reviewer:  Francois Audet
Review Date:  20 March 2007
Review Deadline: 16 March 2007
Status:  Post-WGLC

Summary: Almost Ready.

Document is in good shape.

Note: additional comments are embedded in a word document sent to the mailing list. 

The one semi-technical comment is the one that clarifies that in 
the access scenario topology, the SBC may be hosted either on
the Access network or on the Operator network.

There is one thing that is missing from the document, and that I haven't 
addressed in the Word document. There should be a section called
"Breaking transparency and integrity" or something along those lines. 
It should cover the following:

- There needs to be some discussion about SBCs modifying SIP headers
  that are not meant to be modified by proxies, or modify ANYHING in 
  the SDP or any other attached MIME body and how it will break RFC 4474 
  unless the Authentication Service is provided by the SBC itself (i.e., 
  because RFC 4474 includes an integrity check that protects headers that 
  are not meant to be modified and any MIME body including the SDP). 
  RFC 4474 should be added in normative references.
 

I think it is very crucial to add a section on this topic.