This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24226 - Session Close may involve messaging
Summary: Session Close may involve messaging
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
Depends on:
Blocks: 17199
  Show dependency treegraph
Reported: 2014-01-07 19:29 UTC by Mark Watson
Modified: 2014-01-07 20:47 UTC (History)
3 users (show)

See Also:


Description Mark Watson 2014-01-07 19:29:17 UTC
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.
Comment 1 Adrian Bateman [MSFT] 2014-01-07 20:47:22 UTC
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.