Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 587472 Deprecate and remove NPN
Starred by 6 users Project Member Reported by davidben@chromium.org, Feb 17 2016 Back to list
Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Status: ----
Launch-Test: ----
Launch-UI: ----



Sign in to add a comment
(See http://www.chromium.org/blink#launch-process for an overview)

OWP launch-tracking version of issue #526713.

Change description:
NPN was the TLS extension used to negotiate SPDY (and, in transition, HTTP/2). During the standardization process, NPN was replaced with ALPN, published as RFC 7301 in July 2014. We intend to remove NPN at the same time as the SPDY removal.

Changes to API surface:
We'll no longer offer the NPN extension as part of TLS handshakes. Sites using NPN to negotiate SPDY or HTTP/2 will fall back to HTTP/1.1 at a loss in performance but not functionality.

Links:
Public standards discussion: https://tools.ietf.org/html/draft-agl-tls-nextprotoneg-04

Support in other browsers:
Internet Explorer:
Firefox:
Safari:

*Make sure to fill in any labels with a -?, including all OSes this change
affects. Feel free to leave other labels at the defaults.

 
Summary: Deprecate and remove NPN (was: Deprecate NPN)
Comment 2 by b...@chromium.org, Jun 28 2016
Blockedon: 624096
Comment 3 by b...@chromium.org, Jul 11 2016
Blockedon: -624096
Status: Fixed
NPN functionality is disabled, concluding this launch bug.  Issue 526713 tracks further effort to clean up NPN-related, now dead, code.
Sign in to add a comment