ISSUE-245

Do not require HTTPS URI for strong TLS protection

State:

CLOSED

Product:

Raised by:

Thomas Roessler

Opened on:

2010-04-09

Description:

In LC-2382 [1], it was noted that the definition of "strongly protected TLS connections" required use of an HTTPS URI. For detailed discussion, see [2].

The WG decided during its call on 2010-03-31 [3] to accept the proposal in [2].

1. http://www.w3.org/2006/02/lc-comments-tracker/39814/WD-wsc-ui-20100309/2382
2. http://lists.w3.org/Archives/Public/public-wsc-wg/2010Apr/0009.html
3. http://www.w3.org/2010/03/31-wsc-minutes.html

Related Actions Items:

No related actions

Related emails:

Fw: Transition Request: WSC user interface guidelines to proposed recommendation (from mzurko@us.ibm.com on 2010-05-12)
ISSUE-245 Do not require HTTPS URI for strong TLS protection (from mzurko@us.ibm.com on 2010-05-12)
Minutes WSC Apr 21 (from janv@opera.com on 2010-04-21)
Re: ISSUE-245: Do not require HTTPS URI for strong TLS protection (from mzurko@us.ibm.com on 2010-04-16)
Re: ISSUE-245: Do not require HTTPS URI for strong TLS protection (from tlr@w3.org on 2010-04-16)
Re: ISSUE-245: Do not require HTTPS URI for strong TLS protection (from mzurko@us.ibm.com on 2010-04-16)
Re: ISSUE-245: Do not require HTTPS URI for strong TLS protection (from mzurko@us.ibm.com on 2010-04-12)
ACTION-644: Summary of Last Call Comments (from tlr@w3.org on 2010-04-11)
Re: ISSUE-245: Do not require HTTPS URI for strong TLS protection (from steele@adobe.com on 2010-04-09)
Re: ISSUE-245: Do not require HTTPS URI for strong TLS protection (from tlr@w3.org on 2010-04-09)
Re: ISSUE-245: Do not require HTTPS URI for strong TLS protection (from ifette@google.com on 2010-04-09)
ISSUE-245: Do not require HTTPS URI for strong TLS protection (from sysbot+tracker@w3.org on 2010-04-09)

No additional notes.