1 / 13

Problem Statement and Requirements for SIP Call Control UUI draft-ietf-cuss-sip-uui-reqs-00

Problem Statement and Requirements for SIP Call Control UUI draft-ietf-cuss-sip-uui-reqs-00. Alan Johnston <alan.b.johnston@gmail.com> Joanne McMillen <c.joanne.mcmillen@gmail.com> Laura Liess <laura.liess.dt@gmail.com>. Recent Changes.

vilina
Download Presentation

Problem Statement and Requirements for SIP Call Control UUI draft-ietf-cuss-sip-uui-reqs-00

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Problem Statement and Requirements for SIP Call Control UUIdraft-ietf-cuss-sip-uui-reqs-00 Alan Johnston <alan.b.johnston@gmail.com> Joanne McMillen <c.joanne.mcmillen@gmail.com> Laura Liess <laura.liess.dt@gmail.com> CUSS WG IETF-79

  2. Recent Changes • draft-johnston-cuss-sip-uui-reqs-00 was adopted by WG and used as basis for this document • Editorial edits from Keith incorporated • Removed Figure 5 Not Recommended Call Flow - may move to mechanism document • Edits to REQ-2, REQ-4, REQ-7, REQ-8, and REQ-9 • Added new REQ-10, REQ-11, and REQ-12 • Rewrite of Security Considerations • Two Open Issues identified in document CUSS WG IETF-79

  3. REQ-2 • Changed to: • REQ-2: The mechanism will allow UAs to insert and receive UUI data in SIP dialog terminating requests and responses. CUSS WG IETF-79

  4. REQ-4 • Changed to: • REQ-4: The mechanism will allow UUI to be able to survive proxy retargeting or any other form of redirection of the request. CUSS WG IETF-79

  5. REQ-7 • Changed to: • REQ-7: The mechanism will support interworking with call control related DSS1 information elements or QSIG information elements or ISUP parameters. CUSS WG IETF-79

  6. REQ-8 • Changed to: • REQ-8: The mechanism will allow the inserter of UUI to be sure that the UAS understands the call control UUI mechanism. This could be useful in ensuring that a request destined for the PSTN is routed to a gateway that supports the ISDN UUI service. This mechanism is related to REQ-10. CUSS WG IETF-79

  7. REQ-9 • Changed to: • REQ-9: The mechanism will allow proxies to remove a particular type of UUI information from a request or response. • Removed: • or to block requests based on the presence of a particular type of UUI CUSS WG IETF-79

  8. New REQ-10 • REQ-10: The mechanism will provide the ability for a UA to discover which types or application usages of UUI another UA understands or supports • OPEN ISSUE: For the ISDN Service, is there value in extending this down the protocol discriminator, which is the first octet of the ISDN UUI information? CUSS WG IETF-79

  9. New REQ-11 • REQ-11: The solution MUST provide a mechanism of transporting at least 128 octets of user data and a one octet protocol discriminator, i.e. 129 octets in total. CUSS WG IETF-79

  10. New REQ-12 • REQ-12: The recipient of UUI MUST be able to determine the entity that inserted the UUI. It is acceptable that this is performed implicitly where it is known that there is only one other end UA involved in the dialog. Where that does not exist, some other mechanism will need to be provided. CUSS WG IETF-79

  11. OPEN ISSUE in REQ-6 • REQ-6: The mechanism will minimize reliance on SIP extensions or uncommon SIP behavior. • OPEN ISSUE: Does this requirement need to be reworked, or does it not provide any useful value? CUSS WG IETF-79

  12. New Security Considerations UUI information can contain sensitive information. UUI transported over SIP may need integrity protection, confidentiality, and the ability to determine the identity of the source of the UUI. Since the security requirements and key management of the UUI information are likely to be quite different from the SIP signaling transport, applications using this mechanism to transport information requiring confidentiality will likely perform their own encryption at the application layer before being passed to SIP for transport. CUSS WG IETF-79

  13. Next Steps • Confirm decisions on list • WGLC soon? CUSS WG IETF-79

More Related