Add new labels to net bug triage docs.

net/docs/bug-triage-labels.txt

 Some network label caveats
 * Cr-UI-Browser-Downloads:  Despite the name, this covers all issues related to
     downloading a file except saving entire pages (Which is Cr-Blink-SavePage),
     not just UI issues.  Most downloads bugs will have the word "download" or
     "save as" in the description. Issues with the HTTP server for the Chrome
     binaries are not downloads bugs.
 * Cr-UI-Browser-SafeBrowsing:  Bugs that have to do with the process by which a
     URL or file is determined to be dangerous based on our databases, or the
     resulting interstitials. Determination of danger based purely on
     content-type or file extension belongs in Cr-UI-Browser-Downloads, not
     SafeBrowsing.
 * Cr-Internals-Network-SSL:  This includes issues that should be also tagged as
     Cr-Security-UX (certificate error pages or other security interstitials,
     omnibox indicators that a page is secure), and more general SSL issues.  If
     you see requests that die in the SSL negotiation phase, in particular, this
     is often the correct label.
 * Cr-Internals-Network-DataProxy:  Flywheel / the Data Reduction Proxy.  Issues
-    require “Reduce Data Usage” be turned on.  Proxy url is
+    require "Reduce Data Usage" be turned on.  Proxy url is
     https://proxy.googlezip.net:443, with compress.googlezip.net:80 as a
     fallback.  Currently Android and iOS only.
 * Cr-Internals-Network-Cache:  The cache is the layer that handles most range
     request logic (Though range requests may also be issued by the PDF plugin,
     XHRs, or other components).
 * Cr-Internals-Network-SPDY:  Covers HTTP2 as well.
 * Cr-Internals-Network-HTTP:  Typically not used.  Unclear what it covers, and
     there's no specific HTTP owner.
 * Cr-Internals-Network-Logging:  Covers about:net-internals, about:net-export as
     well as the what's sent to the NetLog.
-* Connectivity issues (ERR_NETWORK_CHANGED, system always thinking it's offline)
-    don't have a label.  There should be assigned to pauljensen@chromium.org.
-    TODO(mmenke):  Should we add a label?
-* SDCH issues should go to rdsmith@chromium.org.
-    TODO(mmenke):  Should we add a label?
+* Cr-Internals-Network-Connectivity:  Issues related to switching between
+    networks, ERR_NETWORK_CHANGED, Chrome thinking it's online when it's not /
+    navigator.onLine inaccuracies, etc.
+* Cr-Internals-Network-Filters:  Covers SDCH and gzip issues.
+    ERR_CONTENT_DECODING_FAILED indicates a problem at this layer, and bugs here
+    can also cause response body corruption.
 
 
 Common non-network label reference.  Bugs in these areas often receive the
 Cr-Internals-Network label, though they fall largely outside the purview of the
 network stack team:
 * Cr-Blink-Forms:  Issues submitting forms, forms having weird data, forms
     sending the wrong method, etc.
 * Cr-Blink-Loader:  Cross origin issues are sometimes loader related.  Blink
     also has an in-memory cache, and when it's used, requests don't appear in
     about:net-internals.  Requests for the same URL are also often merged there
@@ skipping 33 matching lines @@
 * Cr-Blink-SecurityFeature:  CORS / Cross origin issues.  Main frame
     cross-origin navigation issues are often actually Cr-UI-Browser-Navigation
     issues.
 * Cr-Privacy:  Privacy related bug (History, cookies discoverable by an entity
     that shouldn't be able to do so, incognito state being saved in memory or on
     disk beyond the lifetime of incognito tabs, etc).  Generally used in
     conjunction with other labels.
 * Type-Bug-Security:  Security related bug (Allows for code execution from
     remote site, allows crossing security boundaries, unchecked array bounds,
     etc).