IETF82, Taipei Wednesday, 11/16/2011 Notetaker: A. Jean Mahoney - mahoney@nostrum.com Note: Meeting scheduled for 9:00-11:30 (meeting slot split with BCFPBIS, ECRIT took 2nd half) ------------------------------------------------------------------------ 10 min * Agenda Bashing, Draft Status Update (Richard Barnes, Roger Marshall) Agenda bashing: Brian Rosen requested more time on alerting, less on additional data, more time on trustworthy Roger provided draft status. Brian Rosen reported that auth48 over soon, they said everything is fine. They wanted to reword the references to phonebcp, issues with loopback. Authors know we're waiting. ?? draft about to go to auth48 ------------------------------------------------------------------------ 5 min * Common Alerting Protocol (CAP) based Emergency Alerts using the Session Initiation Protocol (SIP) (Brian Rosen) http://datatracker.ietf.org/doc/draft-ietf-ecrit-data-only-ea/ Intention: Discuss open issues Brian Rosen presented. Proposal: allow CAP message and data in both INVITE and MESSAGE, make as similar as possible. Hadriel wanted to know the size (less than 1 kb?) and type of messages (a new MIME type?), and whether they were encrypted (ans: no). Hadriel wanted to know what happens if you strip the CAP message out? It's not pretty, but CAP is not essential. Hannes agreed that if it's a one shot message, use SIP MESSAGE. If there's a whole session with voice and other data, use INVITE and attach data. Hadriel had concerns about CAP making INVITEs brittle, thus risking people's lives in emergencies and wants the CAP sent only in MESSAGEs. Hannes recommended that Hadriel should review the document when it's updated. Brian said that INFO or UPDATE would also work. Hadriel - Could send MESSAGE in dialog. You need to send audio and data to the same place. Brian continued with the presentation: CAP goes in the body. Doesn't need a CID in the header. MUST send additional data, MAY add CAP payload. Need to deal with error handling. Brian felt that, with these updates and this discussion, the doc is close to ready. Draft ready before the end of the year. ------------------------------------------------------------------------ 5 min. * Trustworthy Location Information (Hannes Tschofenig) http://datatracker.ietf.org/doc/draft-ietf-ecrit-trustworthy-location/ Intention: Discuss open issues Current document written for wrong audience, need to explain to less-technical people. Does the group agree with re-focusing the target audience of the writeup? Brian Rosen has been frustrated with this work. Need to do this, but we need real recommendations in the doc in addition to explaining tradeoffs. Can't have perfection. Richard +1 Brian's comment, document needs next steps. This doc is a good place to describe it. Need to recommend best practices. Don't think making less technical is a good idea. ACTION: ==> Richard and Brian get together with Bernard and Hannes to determine where document is going. ------------------------------------------------------------------------ 30 min * Additional Data related to an Emergency Call (Brian Rosen) http://datatracker.ietf.org/doc/draft-ietf-ecrit-additional-data/ Intention: Discuss open issues Brian presented changes to the document. Hadriel had questions about where the XML was placed and how much data was included (variable, but could be a lot). ACTION ==> Add a section to the document to discuss fragmentation and stripping. ACTION ==> Randall will review the document ACTION ==> Have the NENA additional data wg comments brought back to the ecrit list. ------------------------------------------------------------------------ 5 min. * Extensions to the Emergency Services Architecture for dealing with Unauthenticated and Unauthorized Devices (Hannes Tschofenig) http://datatracker.ietf.org/doc/draft-ietf-ecrit-unauthenticated-access/ Intention: Discuss whether document is ready for WGLC There were questions about what the use cases were. ACTION ==> Hannes to send his questions, ask for feedback on the list. ------------------------------------------------------------------------ 30 min. * Public Safety Answering Point (PSAP) Callbacks (Hannes Tschofenig + Christer Holmberg) http://datatracker.ietf.org/doc/draft-ietf-ecrit-psap-callback/ Intention: Discuss open issues Christer presented. Discussion about how much the PSAP should be impacted versus impacting end points. Roger summarized: There needs to be requirements. There's not an agreement on what to do. Update the draft with normative requirements. Describe what is to happen. Hannes said that he wants consensus on solution and then add will add it back into the callback draft. Hadriel suggested taking the item to sipcore. ACTION ==> Continue discussion on the list [end]