Update links to https, update bug trackers.

Author: wolenetz

index.html

@@ -8,11 +8,11 @@
     <script class="remove">
       (function() {
         var mpegContainerSpecDefinitions = {
-          'iso-11172-3': { fragment: 'http://www.iso.org/iso/catalogue_detail.htm?csnumber=22412', link_text: 'ISO/IEC 11172-3:1993', },
-          'iso-13818-3': { fragment: 'http://www.iso.org/iso/catalogue_detail.htm?csnumber=26797', link_text: 'ISO/IEC 13818-3:1998', },
-          'iso-14496-3': { fragment: 'http://www.iso.org/iso/catalogue_detail.htm?csnumber=53943', link_text: 'ISO/IEC 14496-3:2009', },
-          'id3v1': { fragment: 'http://id3.org/ID3v1', link_text: 'ID3v1', },
-          'id3v2': { fragment: 'http://id3.org/id3v2.3.0', link_text: 'ID3v2', },          
+          'iso-11172-3': { fragment: 'https://www.iso.org/iso/catalogue_detail.htm?csnumber=22412', link_text: 'ISO/IEC 11172-3:1993', },
+          'iso-13818-3': { fragment: 'https://www.iso.org/iso/catalogue_detail.htm?csnumber=26797', link_text: 'ISO/IEC 13818-3:1998', },
+          'iso-14496-3': { fragment: 'https://www.iso.org/iso/catalogue_detail.htm?csnumber=53943', link_text: 'ISO/IEC 14496-3:2009', },
+          'id3v1': { fragment: 'https://id3.org/ID3v1', link_text: 'ID3v1', },
+          'id3v2': { fragment: 'https://id3.org/id3v2.3.0', link_text: 'ID3v2', },
           'mpeg-mime-type': { fragment: '#mime-types', link_text: 'MIME-type', },
           'mpeg-mime-types': { fragment: '#mime-types', link_text: 'MIME-types', },
           'mpeg-audio-metadata-frames': { fragment: '#mpeg-metadata', link_text: 'Metadata Frames', },
@@ -27,7 +27,7 @@
       // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
       specStatus: "ED",
 
-      // the specification's short name, as in http://www.w3.org/TR/short-name/
+      // the specification's short name, as in https://www.w3.org/TR/short-name/
       shortName: "mse-byte-stream-format-mpeg-audio",
 
       // if there a publicly available Editor's Draft, this is the link
@@ -36,9 +36,9 @@
       // editors, add as many as you like
       // only "name" is required
       editors:  [
-        { name: "Dale Curtis", url: "", company: "Google Inc.", companyURL: "http://www.google.com/" },
-        { name: "Matthew Wolenetz", mailto: "[email protected]", url: "", company: "Google Inc.", companyURL: "http://www.google.com/", w3cid: "76912" },
-        { name: "Aaron Colwell (until April 2015)",  url: "", company: "Google Inc.", companyURL: "http://www.google.com/" },
+        { name: "Dale Curtis", url: "", company: "Google Inc.", companyURL: "https://www.google.com/" },
+        { name: "Matthew Wolenetz", mailto: "[email protected]", url: "", company: "Google Inc.", companyURL: "https://www.google.com/", w3cid: "76912" },
+        { name: "Aaron Colwell (until April 2015)",  url: "", company: "Google Inc.", companyURL: "https://www.google.com/" },
       ],
 
       mseDefGroupName: "mpeg-byte-stream-format",
@@ -47,7 +47,7 @@
       ],
 
       // name of the WG
-      group: "media", 
+      group: "media",
 
       scheme: "https",
 
@@ -95,7 +95,8 @@
     section>
 
     <section id="sotd">
-      <p>The working group maintains <a href="https://github.com/w3c/media-source/issues">a list of all bug reports that the editors have not yet tried to addressa>.p>
+      <p>The working group maintains <a href="https://github.com/w3c/mse-byte-stream-format-mpeg-audio/issues">a list of all bug reports that the editors have not yet tried to addressa>;
+         there may also be related open bugs in the [[MEDIA-SOURCE]] repository.p>
       <p>Implementors should be aware that this specification is not stable. <strong>Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways.strong> Vendors interested in implementing this specification before it eventually reaches the Candidate Recommendation stage should track the <a href="https://github.com/w3c/media-source">GitHub repositorya> and take part in the discussions.p>
     section>
 
@@ -110,7 +111,7 @@ MIME-types
       <p>This section specifies the MIME-types that may be passed to <a def-id="isTypeSupported">a> or <a def-id="addSourceBuffer">a> for byte streams that conform to this specification.p>
       <ul>
         <li>"audio/aac" for sequences of ADTS frames, as specified in <a def-id="iso-14496-3">a>.li>
-        <li>"audio/mpeg" for MPEG-1/2/2.5 Layer I/II/III streams, as specified in <a href="http://tools.ietf.org/html/rfc3003">RFC 3003a> [[!RFC3003]].li>
+        <li>"audio/mpeg" for MPEG-1/2/2.5 Layer I/II/III streams, as specified in [[!RFC3003]].li>
       ul>
       <p>The "codecs" MIME-type parameter MUST NOT be used with these MIME-types.p>
     section>
@@ -130,7 +131,7 @@ Metadata Frames
 
       <section id="icecast">
         <h3>Icecast headersh3>
-        <p>There is no normative spec for <a href="http://en.wikipedia.org/wiki/Icecast">Icecasta>/<a href="http://en.wikipedia.org/wiki/SHOUTcast">SHOUTcasta> headers, just <a href="http://forums.radiotoolbox.com/viewtopic.php?t=74">examplesa>. For the purpose of this specification, an <dfn>Icecast headerdfn> is defined as beginning with the 4 character sequence "ICY "(U+0049 I, U+0043 C, U+0059 Y, U+0020 SPACE) and ending with a pair of carriage-return line-feed sequences (U+000D CARRIAGE RETURN, U+000A LINE FEED, U+000D CARRIAGE RETURN, U+000A LINE FEED).p>
+        <p>There is no normative spec for <a href="https://en.wikipedia.org/wiki/Icecast">Icecasta>/<a href="https://en.wikipedia.org/wiki/SHOUTcast">SHOUTcasta> headers, just <a href="https://forums.radiotoolbox.com/viewtopic.php?t=74">examplesa>. For the purpose of this specification, an <dfn>Icecast headerdfn> is defined as beginning with the 4 character sequence "ICY "(U+0049 I, U+0043 C, U+0059 Y, U+0020 SPACE) and ending with a pair of carriage-return line-feed sequences (U+000D CARRIAGE RETURN, U+000A LINE FEED, U+000D CARRIAGE RETURN, U+000A LINE FEED).p>
         <p class="note">Icecast headers are allowed in the byte streams because some Icecast and SHOUTcast
           servers return a status line that looks like "ICY OK 200" instead of a standard HTTP status line.
           User-agent network stacks typically interpret this as an HTTP 0.9 response and include the