IETF 60 - San Diegodraft-ietf-sipping-kpml-041 KPML Updates Open Issues Eric Burger, Brooktrout Martin Dolly, AT&T

IETF 60 - San Diegodraft-ietf-sipping-kpml-042 Rev-04 Updates Editorial clean-up with comments from: Allison Mankin, Jonathan R., Silvano Brewster, Bert Culpepper, Rohan Mahy, and Cullen Jennings. Reference to and alignment with App-Interaction Add motivation per “Signaled Digits” Removed reference to use of http Removed section 10.3, Interactive Digit Collection Add GRUU text Remove "leg" Beefed up security considerations and reqts. Add 502 to kpml status References updated Remove "OR" expression Remove MSCML Add sustained rate or notification Expanded abstract Separate namespace for the kpml- request and kpml-response Clarification on DRegex syntax Clarification on digit buffering and security considerations

IETF 60 - San Diegodraft-ietf-sipping-kpml-043 Issue #1: Privacy of User Input Problem One application subscribes to digits to get a credit card #. With credit card #, “transfers” call. Don’t want next application to be able to “reach back” and get credit card #. Options So what, who cares? Do no quarantining (buffering of digits) – You can only get digits from the moment your SUBSCRIBE gets processed. Matter of Local Policy Flush buffer after dialog state change, offer/answer media change (reINVITE), or target refresh request

IETF 60 - San Diegodraft-ietf-sipping-kpml-044 Issue #2: Explanatory Content Problem draft-ietf-sipping- app-interaction- framework-02 contains copy of explanatory text from KPML-03 KPML-04 introduces additional motivating text Options Duplicate all of the text so people only have to look to one document Keep some overlap Keep all non-Normative text in app-interaction- framework; keep all Normative Protocol text in KPML

IETF 60 - San Diegodraft-ietf-sipping-kpml-045 Next Steps Full alignment with draft-ietf-sipping-app- interaction-framework-02 Incorporate additional comments –Better registration statements –Lots of Editorial changes NOTE: –With Exception of “Quarantine Reach Back”, there have been No Substantive Protocol Changes since -02