Minutes for INSIPID virtual #1 interim meeting ============================================== 25th June 2012: 9:00 - 11:00 Pacific US time -------------------------------------------- Chairs: Keith Drage Gonzalo Salgueiro Present: Keith Drage Gonzalo Salgueiro Adam Roach Gonzalo Camarillo James Polk Parthasarathi Ravindran Paul Kyzivat Salvatore Loreto Andy Hutton Sandeep Sharma Dan Romascamu Peter Dawes Hadriel Kaplan Alan Ford Paul Jones Alan Johnson Laura Leiss 1) Agenda bash, notetakers, etc ------------------------------------ Andy Hutton volunteered to take notes. Agenda Bash. -- No bashing. Session ID and Trouble Shooting - Peter Dawes ---------------------------------------------- Proposing a new requirement which is to be able to mark the session identifier as being for troubleshooting. Question - What do you mean by marking, Answer - Need to mark the session-id as being for the purpose of troubleshooting. Paul K suggested that the troubleshooting indication might not be associated with the session id at all. No further clarification questions. 2) Scope of requirements / use cases document -------------------------------------------------- Session Initiation Protocol (SIP) Header Parameter for Debugging ---------------------------------------------------------------- draft-dawes-dispatch-debug-00 Peter Dawes https://datatracker.ietf.org/doc/draft-dawes-dispatch-debug Proposing a new requirement which is to be able to mark the session identifier as being for troubleshooting. Question - What do you mean by marking, Answer - Need to mark the session-id as being for the purpose of troubleshooting. Paul K suggested that the troubleshooting indication might not be associated with the session id at all. No further clarification questions. Session Initiation Protocol (SIP) Extension for logging and debugging ---------------------------------------------------------------------- draft-kaithal-dispatch-sip-log-information-00 Parthasarathi Ravindran (on behalf of Adarsh Kaithal / Sandeep K S) https://datatracker.ietf.org/doc/draft-kaithal-dispatch-sip-log-information/ Request is to consider "Log-me" logging requirement as a usecase for INSIPID. Question from Peter Dawes - Many entities could include this is some checking needed to prevent misuse of the header. - Answer from Partha, We are just defining building blocks. Paul K - The issue of misuse does need to be dealt with but is probably not hard. Adam - Do we really need to tackle the issue of logging or is that a different but related problem that should be done elsewhere. Paul K - A possible candidate place for defining a mechanism to turn logging on would be SIPCLF. Question raised as to whether we did a reason in the protocol as to why session-id is included. Others - Would require a change to SIPCLF charter so would have to take to dispatch if we wanted this to be done elsewhere. A lot of discussion in whether the log me service should be dealt with within INSIPID. Conclusion: Consensus is that any mechanism to control logging should go to DISPATCH. There did seem to be the assumption that the session-id is fit for the purpose of correlating logged information. A Session Identifier for the Session Initiation Protocol (SIP) (ANNEX A ONLY) ------------------------------------------------------------------------------ draft-kaplan-dispatch-session-id-03 Hadriel Kaplan http://tools.ietf.org/html/draft-kaplan-dispatch-session-id-03 No discussion. Keith asked question regarding whether we need use cases and requirements seems to be consensus that we do need these. Should the requirements & use cases be a separate document to the solution. Seems to be consensus that it should be two separate documents. Keith, chairs will discuss creating a new milestone for the requirements draft. 3) Discussion of individual requirements --------------------------------------------- Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks draft-jones-ipmc-session-id-reqts-01 Paul Jones / James Polk / Parthasarathi Ravindran / Laura Liess / Roland Jesske / Salvatore Loreto / Hadriel Kaplan https://datatracker.ietf.org/doc/draft-jones-ipmc-session-id-reqts/ REQ1: OK REQ2: Debate about whether the use of the word "Session" within the text is correct or whether it relates to dialogs and/or transactions. "Identify" changed to "correlate". Out of this came new requirement to be able to correlate non-dialog creating transactions. Text was edited on-line. REQ3: Needs some rewording to make it clear that some entity other than the conference focus can correlate the sessions. REQ4: Paul K - We need some stronger wording to explain why it is needed. Keith - Reword all the requirements so they start with "The solution must...". REQ5: Question - What is the subscriber ID? - Seems to come from the mobile world. Restructure the sentence as agreed online. Also add requirement to not reveal the user. REQ6: Laura explained why it might be difficult to meet REQ6 4) Next steps --------------------------------- Next Interims to be on the 25th of June and 10th of July.