Subject: [cuss] Review of draft-ietf-cuss-sip-uui

From: "DOLLY, MARTIN C" <[email-masked]>
Date: Tue, 10 Jan 2012 15:32:07 +0000

Greetings,

I was asked by chairs of this WG to review 
draft-ietf-cuss-sip-uui. 

Below are my comments, build on Shida's comments posted on 11/29/2011

The concept of "escaping" needs to be added to Section 4 Normative Definition, and an illustrative example would be helpful.

UUI can be communicated between an UE and an Application Server acting as a B2BUA, as meets the UAC-UAS requirement, so I believe a statement explicitly stating that should be added to the overview.

Complex call center communications can have multiple (3-4) redirections/referrals, so a multiple redirection/referral example would be helpful.

Is it possible to have multiple UUI headers, either with the same data content encoded differently or with different data content?

What is an intermediary, if it is not a proxy?

Terminology: the document has UUIs being communicated between UACs and UASs and between endpoints, which is it?

Considering the same data content could be encoded differently, does this result in multiple UUI packages? And if so, could they be defined in the same RFC?

Regards,

Martin Dolly
Lead Member Technical Staff
Core & Government/Regulatory Standards
AT&T Services, Inc.
[email-masked]
+1-609-903-3360