IETF90 ECRIT This file contains the posted agenda followed by the meeting notes. 17:30-18:30 GMT, Thursday, July 24, 2014 Toronto ========================================================================= Note taker: Christer Holmberg Blue sheets handed out. Note Well presented. 5 min * Agenda Bashing, Draft Status Update (Chairs) Chairs: Marc Linsner, Roger Marshall Presentation slot requested by Ludwig Seitz to present use cases and get wg feedback on: draft-seitz-ace-usecases-01 Additional time given for the Additional-data draft by dropping off car-crash and ecall draft presentations (same presenter, Randall Gellens) ========================================================================= Original ECRIT Agenda - 17:30-18:30 GMT, Afternoon Session III, Thursday, July 24, 2014 Toronto 5 min * Agenda Bashing, Draft Status Update (Chairs) 10 min * Additional Data related to an Emergency Call (Randy) http://www.ietf.org/id/draft-ietf-ecrit-additional-data-22.txt 5 min * Common Alerting Protocol (CAP) based Data-Only Emergency Alerts using the Session Initiation Protocol (Brian) http://www.ietf.org/id/draft-ietf-ecrit-data-only-ea-07.txt 10 min * Internet Protocol-based In-Vehicle Emergency Calls (Randy) http://www.ietf.org/id/draft-ietf-ecrit-car-crash-00.txt 10 min * Next-Generation Pan-European eCall (Randy) http://www.ietf.org/id/draft-ietf-ecrit-ecall-00.txt 5 min * A LoST extension to support return of complete and similar location info (Brian) http://www.ietf.org/id/draft-marshall-ecrit-similar-location-03.txt 10 min * A Routing Request Extension for the HELD Protocol (James) http://www.ietf.org/id/draft-winterbottom-ecrit-priv-loc-04 5 min * Discussion ========================================================================= Topic: Additional data: Draft: draft-ietf-ecrit-additional-data-22 Presenter: Randall Gellens ISSUE: As IMSI has been added to device identifier types, associated privacy issues need to be described in the security considerations. OUTCOME: Text regarding privacy issues associated with IMSI delivery will be added. ISSUE: Does device classification registry in section 3.3.1 need an entry for soft client on unknown device type? OUTCOME: Yes (Soft client running on a computer does not know on what type of computer it is running) ISSUE: Service providers without NENA/EENA IDs. Do providers need to be identified and globally unique? OUTCOME: Service providers do need to be unique. ISSUE: Type Of Data Provider is unclear OUTCOME: Will be renamed TypeOfProvider ISSUE: Does a Data Provider Contact, given as a telephone number, have to be in E.164 format? OUTCOME: Data Provider Contact URI can be generic SIP URI and when telephone number, MUST be E.164. ISSUE: Suggestion to add a new element in Owner/Subscriber block to indicate source of data. OUTCOME: The suggested was not accepted. It was indicated that the document is not restricted to emergency calls. It was indicated that a UE may not be aware that it is making an emergency call (but the network will detect the call as an emergency call), in which case a UE will not provide additional data. It was determined that additional text is needed to cover the privacy issues associated with the additional data, and that the data should only be provided for emergency calls. The chairs indicated that a new WGLC is not needed, but that the community needs to review such text. ========================================================================= Topic: Data-Only Emergency Calls Draft: draft-ietf-ecrit-data-only-ea-08 Presenter: Brian Rosen The author requested WGLC for the draft. It was indicated that the terminology needs to be double checked, as “call” often implies the presence of conversational media. ========================================================================= Topic: A LoST extension to support return of complete and similar location info Draft: draft-marshall-ecrit-similar-location-03 Presenter: Roger Marshall ISSUE: There was a request to adopt the draft as a WG document. OUTCOME: There was WG consensus to adopt the draft. ========================================================================= Topic: A Routing Extension for HELD Draft: draft-winterbottom-ecrit-priv-loc-04 Presenter: Laura Liess ISSUE: It was suggested to extend HELD, by adopting draft-winterbottom-ecrit-priv-loc, in order to solve the problem presented. OUTCOME: Some people did not agree to the statements made, and the suggested was to solve the problem. Additional discussions need to take place on the mailing list. ========================================================================= Topic: Feedback for ACE Use Cases Draft: draft-seitz-ace-usecases-01 Presenter: Ludwig Seitz The ECRIT community was requested to provide feedback, and real-lire use-cases.