Mention WebRTC in bug-triage-labels.md.

net/docs/bug-triage-labels.md

 # Chrome Network Bug Triage : Components and labels
 
 ## Some network component caveats
 
 **UI>Browser>Downloads**
 : Despite the name, this covers all issues related to downloading a file except
   saving entire pages (which is **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.
@@ skipping 66 matching lines @@
 
 **Blink>Network>FetchAPI**
 : Generic issues with the Fetch API - missing request or response
   headers, multiple headers, etc.  These will often run into issues in certain
   corner cases (Cross origin / CORS, proxy, whatever).  Attach all components that
   seem appropriate.
 
 **Blink>Network>XHR**
 : Generic issues with sync/async XHR requests.
 
+**Blink>WebRTC>Network**
+: Anything WebRTC-related does not use the net stack and should go here.
+
 **Services>Sync**
 : Sharing data/tabs/history/passwords/etc between machines not working.
 
 **Services>Chromoting**
 
 **Platform>Extensions**
 : Issues extensions loading / not loading / hanging.
 
 **Platform>Extensions>API**
 : Issues with network related extension APIs should have this component.
@@ skipping 36 matching lines @@
   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 components.
 
 ## Common labels
 
 **Type-Bug-Security**
 : Security related bug (Allows for code execution from remote site, allows
   crossing security boundaries, unchecked array bounds, etc) should be tagged
   with this label.