24226 2014-01-07 19:29:17 +0000 Session Close may involve messaging 2014-01-07 20:47:22 +0000 1 1 1 Unclassified HTML WG Encrypted Media Extensions unspecified PC All RESOLVED WORKSFORME P2 normal --- 17199 1 watsonm adrianba ddorwin mike public-html-media public-html-bugzilla oldest_to_newest 98099 0 watsonm 2014-01-07 19:29:17 +0000 In order to support secure proof of key release, the Session Close algorithm should entertain the possibility that the session sends a message and receives a response. One possibility is that the Session Close algorithm may either transition directly to CLOSED state or may transition first to PENDING, sending a message, and then to CLOSED when the response is received. 98104 1 adrianba 2014-01-07 20:47:22 +0000 The session close algorithm runs when the session actually closes. Prior to that, the things that result in triggering the session close algorithm might cause messages to be passed and the state change to PENDING first. For example, the release() method says "or schedule other work that later causes the session to be closed." This other work might be firing a message event that sets the state to PENDING. Once the response is received, the session close algorithm will run.