1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential Conveying Policy URI in Call-info purpose Hisham Khartabil Aki Niemi SIP WG IETF 59, Seoul

2 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential Conveying a Session Policy URI in SIP draft-khartabil-sip-policy-uri-call-info-purpose-00 Some participants in a conference need to know the conference policy URI Some participants are not able to subscribe to the conference state event package to get such information Proposal in this draft is to use the Call-info header in SIP with a purpose of “policy-uri”

3 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential Issues 1: policy-uri “policy-uri” as a purpose is too general. Suggestion to make it specific for conference policy “conf-policy-uri” Proposal: change to “conf-policy-uri” or “conf-policy”

4 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential Issue 2: To IANA or not to IANA It was also discovered that there was no IANA registry set up for the “purpose" parameter in the Call-info header of SIP. This document sets up the IANA registry. Some controversy over that. Should we or should we not set up the IANA registry? RFC3261 says: “ Additional tokens can be registered using IANA and the procedures in Section 27. ” Proposal: Go ahead and set up the IANA registry