W3C home > Mailing lists > Public > public-council@w3.org > February 2017

HTTPS in Local Network Community Group Launched

From: <public-council@w3.org>
Date: Mon, 06 Feb 2017 02:48:29 +0000
To: "Tomoyuki Shimizu" <tomoyuki.labs@gmail.com>,"Daisuke Ajitomi" <daisuke.ajitomi@toshiba.co.jp>,"Yoshiro Yoneya" <yoshiro.yoneya@jprs.co.jp>,"Junichi Hashimoto" <ju-hashimoto@kddi.com>,"Tatsuya Igarashi" <Tatsuya.Igarashi@jp.sony.com>,Cc: public-council@w3.org
Message-Id: <E1caZLx-0005Kw-NN@maia.w3.org>
With your support, the HTTPS in Local Network Community Group has been launched:

This group was originally proposed on 2017-02-03
by Tomoyuki Shimizu. The following people supported its
      Tomoyuki Shimizu
      Daisuke Ajitomi
      Yoshiro Yoneya
      Junichi Hashimoto
      Tatsuya Igarashi
To join the group, please use:

Please note that supporting a group is different from joining
a group. Supporters must also enroll if they wish to participate.

The HTTPS in Local Network Community Group (CG) explores the manner of
secure communication between browsers and server-capable devices in
local network such as set-top boxes, network attached storages, etc. We
propose that this Community Group clarify requirements for browsers and
devices in issuing valid certificates and establishment of HTTPS and
WebSocket connections over TLS and incubate relevant specifications of
APIs and/or network protocols.

This work has four primary purposes:

 Improve security and privacy of communication between browsers and
server-capable devices. 
 Enable web applications in secure contexts to communicate with
server-capable devices in local network via XMLHttpRequest, Fetch API,
and WebSocket. 
 Enable service discovery mechanisms to advertise existence of
TLS-enabled server-capable devices. 
 Encourage adoption and implementation of the specification by browser
vendors and device manufacturers. 

Given wider support and adequate stability, we plan to migrate the
generated in this Community Group to an appropriate standards track, for

example the IETF Standards Track or a W3C Working Group, for further
contributions and formal standardization.

Thank you,

W3C Community Development Team
Received on Monday, 6 February 2017 02:49:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:18 UTC