1 / 5

Alan Johnston <alan@sipstation> Joann McMillen <joanne@avaya>

Transporting User to User Call Control Information in SIP for ISDN Interworking draft-johnston-sipping-cc-uui-07. Alan Johnston <alan@sipstation.com> Joann McMillen <joanne@avaya.com>. Status. Reviewed by: Spencer Dawkins, Keith Drage, Vijay Gurbani, and Laura Liess Thank You!

mada
Télécharger la présentation

Alan Johnston <alan@sipstation> Joann McMillen <joanne@avaya>

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. Transporting User to User Call Control Information in SIP for ISDN Interworkingdraft-johnston-sipping-cc-uui-07 Alan Johnston <alan@sipstation.com> Joann McMillen <joanne@avaya.com> SIP WG IETF-74

  2. Status • Reviewed by: Spencer Dawkins, Keith Drage, Vijay Gurbani, and Laura Liess • Thank You! • Completed SIPPING WG LC on requirements • Requirements scoped to interworking with ISDN UUI service - not for general SIP user information exchange • Ready for mechanism discussion SIP WG IETF-74

  3. Recent Changes • Justified redirection requirement • Added ISUP Q.767 references • Clarified REQ-5: • REQ-5: The mechanism should not require processing entities to dereference a URL to retrieve the UUI information. • Clarified discussion on native SIP usage • Clarified security considerations SIP WG IETF-74

  4. Open Issue • Should UUI carry meta-data like we are defining for INFO? • Raised by Jonathan on list • Needed for INFO because INFO is used for more than just ISDN/ISUP interworking • We can avoid this by keeping the narrow focus of this header field and defining a new header field (User-Info?) for non-ISDN information which will need meta-data • ISDN UUI going to/from PSTN does not and can not be tagged with meta-data - to do so is a layer violation for this service SIP WG IETF-74

  5. Next Steps • Feedback on header field mechanism? SIP WG IETF-74

More Related