[Sipping] Draft SIPPING minutes, 2nd Session

[[e-mail]]

SIPPING WG Meeting

Thursday, July 17, 2003,  1300-1500

AKA v2 was pointed out and drawn attention to. WG does not need to review document.

1300 Open Issues from Application Interaction Design Team
=========================================================
Jonathan Rosenberg

Status:
- submitted new documents below.
- Design teams considered itself done. Only 1 issue remaining
- Question remaining is if WG is interesting in adopting this work
- Changes from previous revision presented (see slides)

No comments on the mike for adopting this work

Voting:
- rough consensus to adopt the work as WG items.


draft-rosenberg-sipping-app-interaction-framework-00
draft-jennings-sip-app-info-01
----------------------------------------------------
Jonathan Rosenberg

Open issue: KPML DTMF reporting
- INFO: INFO is only for within dialogs
- NOTIFY: implicit subscriptions has issues
- Explicit subscription: GRUU and authorisation problem
- HTTP: not returning a script in proposed issues
- New method: what does this buy us?
- MESSAGE: least harmful solution. It is the proposed solution for now.

Discussion:
- Most mike speakers were advocating a new method. Jonathan has reservation (semantics)
- Another proposal was presented suggesting content-disposition with MESSAGE.
- Implicit subscription is really bad, from REFER experience. Jonathan asks to explicitly list the  problems with implicit subscriptions and we can figure out which ones apply/don't apply to this  problem.
- implicit subscription might may cause flood of proposals to use other methods with it. We don't want  to have to go through the exercise of going through  the pros and cons every time someone wants to use  implicit subscriptions.
- no consensus, take it to the list.

draft-burger-sipping-kpml-02 
----------------------------------------------------
Eric Burger

- Issues and resolutions presented (see slides)
- No comments, questions or suggestions
- Will be sent to AD for consideration

1320 Discussion of Media-related Issues 
=========================================================

draft-camarillo-sipping-early-media-02.txt
----------------------------------------------------
- Presented by Gonzalo
- Missed the dead line, so it wasn't submitted
- no issues discussed

draft-mahy-sipping-tones-00.txt
----------------------------------------------------
Rohan Mahy

- Presented background and proposal (put it in the body)
- trying to reduce early media occurrence
- using explicit tones can convey country specific tones
- Rohan asks if this is interesting to the working group.

Discussion:
- no concrete support from comments on the mike
- speaker asks for comments on the mailing list regarding support of this work.
draft-burger-sipping-netann-06 

1350 Discussion of Event Filtering and Throttling 
=========================================================
Aki Niemi

draft-niemi-sipping-event-throttle-reqs-02.txt 
----------------------------------------------------
- presenter clarified how is this different than filtering and partial notification.
- presented the model behind the requirements

Open issues/ discussion:
- need to elaborate on use cases. Proposal is not to do so
- might be worth mentioning the buffer behaviour
- move to WG item
- Rough consensus to take this as a WG item


1400 Discussion of DPNSS to SIP interworking 
=========================================================
Ranjith Mukundan

draft-mukundan-sipping-dpnss-02.txt 
----------------------------------------------------
- presented what is dpnss, why dpnss is needed and how its complementary to QSIG/SIP.
- MIME type as a proposal

Issues/Discussion:

- Some scepticism on the usefulness of this work.
- Do we have the expertise to review it. Is this the right place to take on this work
- A show of hands was asked  showing interest in this topic: One hand went up in the room
- About 4 people raised their hand claiming expertise in dpnss
- DPNSS to sip translation: no interest in the group
- WG item? Conclusion was a no. Authors can proceed with it as individual work

1410 Discussion of End-to-middle Security 
=========================================================
Kumiko Ono

draft-ono-sipping-end2middle-security-00.txt
----------------------------------------------------
- presented why this type of security is needed, using use cases. 

Issues/Discussion:
- Any interest from WG?
- middle to end and end to middle: just the inverse of each other. Others suggest that they are  complementary.
- too early as a wg item.
- A hum was taken on interest in this topic. The hum showed interest.
- A hum was taken on interest of having the requirements taken as WG item. The hum showed interest.

1435 Discussion on Phone-related Status and Presence 
=========================================================
Jonathan Rosenberg

draft-rosenberg-peterson-simple-pidf-phone
----------------------------------------------------
- Presented what is it. Asked people to take a look at it.

Discussion:
- maybe presence is not the right thing to do for this
- this is tide to dialog state. Answer is that you don't want both, but you definitely need presence.  the worry is that you have to subscribe to both event packages. Answer is that different things need  different packages
- A hum was taken on interest in this topic. The hum showed interest.
- Propose to produce use cases to motivate this work. Agreed.
- Might be an issue if this is a sipping or simple work. We can decide later


1450 Discussion of Diagnostics in SIP 
========================================================
Alan Johnston

draft-johnston-sipping-rtcp-summary-00.txt
----------------------------------------------------

- Delivery of RTCP summery reports to 3rd parties
- 3 possibilities: 1 RTCP to multiple locations, 2 SIP header in BYE, 3 Event package

Discussion:
- this is interesting and needed, although the proposed mechanisms were not well received.
- why not use some snmp mechanisms?
- RMON WG is working on such things already. Advice to take a look at the work being done there.
- Need evaluate RMON work. Alan will do that. 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP