Telechat Review of draft-ietf-cuss-sip-uui-reqs-

Request Review of draft-ietf-cuss-sip-uui-reqs
Requested rev. no specific revision (document currently at 09)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2011-11-01
Requested 2011-11-01
Authors Alan Johnston, Laura Liess
Draft last updated 2011-11-01
Completed reviews Genart Telechat review of -?? by Ben Campbell
Genart Telechat review of -?? by Ben Campbell
Assignment Reviewer Ben Campbell
State Completed
Review review-ietf-cuss-sip-uui-reqs-genart-telechat-campbell-2011-11-01
Review completed: 2011-11-01


I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-cuss-sip-uui-reqs-07
Reviewer: Ben Campbell
Review Date: 2011-01-01
IESG Telechat date: 2011-01-03


This version is basically ready for publication as an informational RFC. Alan responded to two of my comments with perfectly reasonable explanations (see quoted text below.) In both cases, I think the requirements would be more clear if the clarifications were included in the draft text:

>> -- REQ-12: 
>> What degree of certainty is required here? (i.e. strong identity?) If implied by the SIP dialog, does that impact expectations on what sort of authn must happen at the SIP layer?
> This is not meant to imply strong identity.  And since UUI data can appear in a response, there aren't really any strong methods available with SIP.   The UUI mechanism does not introduce stronger authorization requirements for SIP, but instead the mechanism needs to be able to utilize existing SIP approaches.
>> -- REQ 13:
>> I'm not sure I understand how this interacts with the ability for intermediaries to remove UUI. Should this be detectable by the endpoints? Or is that ability limited to the hop-by-hop case, or require no integrity protection?
> Yes, there are tradeoffs between this requirement and requirement REQ-9.  Hop-by-hop protection is one way to resolve this interaction.