Agenda

Document status

Last meeting - Toronto, two meetings in a row!!!

Dual stack - no progress, no new version submitted

dane-sip

- discussed in London, mentioned in Toronto but author not present.
- not clear if there is interest.
- chair asked - who has use cases, no hands raised
- Jon - It's a Broccoli thing, no pain point
- chair - author can continue to work on it
- AD - if no one wants to do the work then let it drop
- Robert - comparison with dual stack not having energy is not valid
  - Simon Perreault said he could comment on the list
  - Mary, there are people who are interested but they aren't here

Paul is stepping down as chair

Robert

- draft-roach-sipcore-6665-clarification-00
  - limited number of people have read it
- refer-clarifications
- refer-explicit-subscription
- Recent list discussions
  - No argument about what use means.
- further qualify "creates and implicit subscription" in refer-clarifications
  - Allen - leave it as it is
  - More tightly tie the references together
  - Adam - need all three to be published together

Plan for the 2 refer drafts
- Adoption call on list
- Ready to issue -00s
- 3-4 weeks from pubreq
- Christer would like to adopt all three at the same time

Plan for 6665 clarifications
- Adam read draft to the room

Call for adaption of all three drafts
- Consensus to adapt all three
- Robert will drop -00 for the 2 refer drafts with changes
- Need the consensus call to go to the list for 6665-clarifications
- Goal is for WG last call happening before Dallas

------

SIP Authorization framework use cases - Rifaat

- Auth framework components
  - Authentication
  - Authorization

Jon Peterson - clarification on authorization

Much discussion on WebRTC use case
- Request for Christer to write a draft that explains IMS authentication model to provide clarity for the use case.

Jon expressed concern that there are already lots of things that overlap with authentication and authorization.
Much discussion in general, no decisions reached

------

Key derivation - Rifaat

Eric - What problem is being solved
Rifaat - Find something better then Digest
Cullen - Most commercial deployments do not relay on low entropy passwords
Eric - Proposed solution does not address all of the use cases and identified digest issues
Eric - Challenged that replay is a fundamental problem