Minutes of the SIPPING WG Session at IETF 71 ============================================ Minutes edited by Gonzalo Camarillo Based on notes by Keith Drage and Bruce Lowekamp Meeting chaired by Gonzalo Camarillo and Mary Barnes Slides presented included in the proceedings Tuesday, March 10th, 1740-1950 ------------------------------ Topic: Agenda Bash Discussions led by: Chairs The chairs presented the status of the WG. An ad-hoc meeting on SIP extensibility, which was supposed to be held from 10 pm to midnight, had been announced on the list. The chairs asked the room whether or not people wanted to participate in the ad-hoc given that it was an important topic but the only available slot was late in the evening. There was equal support to hold the meeting as to cancel it. Consequently, since there was not clear consensus to hold the ad-hoc meeting, it was cancelled. The chairs informed the room that the following draft was going to be sent to the SIP WG so that the SIP WG works on a solution for its requirements: draft-holmberg-sipping-199-04.txt. Last time this draft was presented there was agreement that there was a need for a solution to, at least, meet the requirements listed in the draft. Additionally, some people said they might study whether meeting further requirements (e.g., resolving HERFP) was reasonable. Nobody on the list or in the room had spoken up since then. Therefore, this draft is sent to the SIP WG as is, without incorporating any further requirements. Topic: Updates to Asserted Identity Discussion led by: John Elwell Relevant documents: draft-ietf-sipping-update-pai-00.txt John presented the changes incorporated since the last revision of the draft (which was not a WG item). John discussed the following open issues: Open issue 1: Whether to allow P-Asserted-Identity in a REGISTER request, between an edge proxy that authenticates the UA and a registrar. The feedback in the room was in favour of allowing this. Open issue 2: Whether to allow P-Asserted-Identity in any mid-dialog request (including PRACK, INFO, BYE, etc.) rather than just UPDATE. Several people spoke against allowing general use in all requests, as it was not the general intent of the original draft. This conclusion was to only allow it in UPDATE. Open issue 3: Are there any use cases that justify the use of P-Preferred-Identity in an UPDATE request? There was no consensus than this is useful. Unless there are further discussion on list, this will not be included in the draft. Open issue 4: Should we be precise (at least in the normative section) as to the conditions under which a proxy may assert an identity in the response? This issue needs more discussions on the list. The chairs had asked on the list whether the applicability statement in RFC 3325 still holds or the draft intends to update it somehow. The applicability statement will not be updated. Topic: User Agent Profile Datasets Discussion led by: Sam Ganesan Relevant documents: draft-ietf-sipping-profile-datasets-00.txt The chairs noted that this draft is important because it is a dependency of the session policies framework (which is a chartered item as well). The invisible attribute and the exclude mechanism need more discussions on the list. Topic: Extension to the ua-profile Event Package to Support the Application Profile Type Discussion led by: Sumanth Channabasappa Relevant documents: draft-channabasappa-sipping-app-profile-type-02.txt Sam requested the WG to consider accepting this draft as a WG item. Sam noted that specifications being developed in other standards bodies, such as OMA and TISPAN, are considering the 'application' profile type (or equivalents). This draft will standardize the 'application' profile type and its associated requirements. Only half dozen people indicated they had read the draft. The chairs asked for more discussion on the mailing list before proceeding. Topic: What is a Session Initiation Protocol (SIP) Trunk Anyway? Discussion led by: Jonathan Rosenberg Relevant documents: draft-rosenberg-sipping-siptrunk-00.txt Jonathan clarified that a SIP trunk is not a trunk used to sip water as in the figure below: _,-'`````--.___..----.,'__`---..__ ,'' ,' `.`. `. ,'' / ` ) \ // | / \ // : :