Commit 5197f49a authored by Darshak Thakore's avatar Darshak Thakore

Script updating gh-pages. [ci skip]

parent 2dfe3a6b
......@@ -287,7 +287,7 @@ li, p {
<meta name="dct.creator" content="Thakore, D., Ed., Dang, N., and G. Hughes" />
<meta name="dct.identifier" content="urn:ietf:id:draft-dthakore-scte-urn-latest" />
<meta name="dct.issued" scheme="ISO8601" content="2016-3-21" />
<meta name="dct.issued" scheme="ISO8601" content="2016-3" />
<meta name="dct.abstract" content="This document describers the Namespace Identifier (NID) 'scte' for Uniform Resource Names (URNs) used to identify resources published by the Society of Cable Telecommunications Engineers (SCTE). SCTE specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the SCTE." />
<meta name="description" content="This document describers the Namespace Identifier (NID) 'scte' for Uniform Resource Names (URNs) used to identify resources published by the Society of Cable Telecommunications Engineers (SCTE). SCTE specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the SCTE." />
......@@ -311,7 +311,7 @@ li, p {
<td class="right">N. Dang</td>
</tr>
<tr>
<td class="left">Expires: September 22, 2016</td>
<td class="left">Expires: September 2, 2016</td>
<td class="right">SCTE</td>
</tr>
<tr>
......@@ -324,7 +324,7 @@ li, p {
</tr>
<tr>
<td class="left"></td>
<td class="right">March 21, 2016</td>
<td class="right">March 2016</td>
</tr>
......@@ -348,7 +348,7 @@ li, p {
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on September 22, 2016.</p>
<p>This Internet-Draft will expire on September 2, 2016.</p>
<h1 id="rfc.copyrightnotice">
<a href="#rfc.copyrightnotice">Copyright Notice</a>
</h1>
......@@ -484,7 +484,7 @@ li, p {
<p id="rfc.section.4.p.2">The use of URNs should also help specification authors to maintain different versions of URNs and dependencies between URNs across different versions of SCTE specifications if they so wish. </p>
<h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> Community Considerations</h1>
<p id="rfc.section.5.p.1">Participants involved in the development and usage of SCTE specifications and cable industry deployments will benefit from the publication of this namespace by providing consistent and reliable names for the XML namespaces, schema locations, and similar identifiers of physical data models published within SCTE specifications. </p>
<p id="rfc.section.5.p.2">The SCTE specifications are publicly available and are licensed to manufacturers on a nondiscriminatory basis. SCTE will maintain the corresponding specifications where the regustered resources are referenced or used. </p>
<p id="rfc.section.5.p.2">The SCTE specifications are publicly available and are licensed to manufacturers on a nondiscriminatory basis. SCTE will maintain the corresponding specifications where the registered resources are referenced or used. </p>
<h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a href="#IANA" id="IANA">IANA Considerations</a></h1>
<p id="rfc.section.6.p.1">This document adds a new entry ("scte") in the urn-namespaces registry. This is the defining document for the entry. The entry can be found in the <a href="#IANA-URN">Uniform Resource Names (URN) Namespaces</a> <cite title="NONE">[IANA-URN]</cite> Registry.</p>
<h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a href="#Security" id="Security">Security Considerations</a></h1>
......@@ -515,15 +515,15 @@ li, p {
</tr>
<tr>
<td class="reference">
<b id="RFC2629">[RFC2629]</b>
<b id="RFC3406">[RFC3406]</b>
</td>
<td class="top"><a>Rose, M.</a>, "<a href="http://tools.ietf.org/html/rfc2629">Writing I-Ds and RFCs using XML</a>", RFC 2629, DOI 10.17487/RFC2629, June 1999.</td>
<td class="top"><a>Daigle, L.</a>, <a>van Gulik, D.</a>, <a>Iannella, R.</a> and <a>P. Faltstrom</a>, "<a href="http://tools.ietf.org/html/rfc3406">Uniform Resource Names (URN) Namespace Definition Mechanisms</a>", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC3406">[RFC3406]</b>
<b id="RFC7749">[RFC7749]</b>
</td>
<td class="top"><a>Daigle, L.</a>, <a>van Gulik, D.</a>, <a>Iannella, R.</a> and <a>P. Faltstrom</a>, "<a href="http://tools.ietf.org/html/rfc3406">Uniform Resource Names (URN) Namespace Definition Mechanisms</a>", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002.</td>
<td class="top"><a>Reschke, J.</a>, "<a href="http://tools.ietf.org/html/rfc7749">The "xml2rfc" Version 2 Vocabulary</a>", RFC 7749, DOI 10.17487/RFC7749, February 2016.</td>
</tr>
</tbody>
</table>
......@@ -548,6 +548,12 @@ li, p {
</td>
<td class="top"><a>Cardona, E.</a>, <a>Channabasappa, S.</a> and <a>J-F. Mule</a>, "<a href="http://tools.ietf.org/html/rfc6289">A Uniform Resource Name (URN) Namespace for CableLabs</a>", RFC 6289, DOI 10.17487/RFC6289, June 2011.</td>
</tr>
<tr>
<td class="reference">
<b id="SANN">[SANN]</b>
</td>
<td class="top"><a>Society of Cable Telecommunications Engineers</a>, "<a>SCTE Assigned Name and Number Registry</a>"</td>
</tr>
</tbody>
</table>
<h1 id="rfc.authors">
......
......@@ -5,10 +5,10 @@
ART Area General Applications Working Group D. Thakore, Ed.
Internet-Draft CableLabs
Intended status: Informational N. Dang
Expires: September 22, 2016 SCTE
Expires: September 2, 2016 SCTE
G. Hughes
SeaChange
March 21, 2016
March 2016
A Uniform Resource Name (URN) Namespace for SCTE
......@@ -44,7 +44,7 @@ Status of This Memo
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 22, 2016.
This Internet-Draft will expire on September 2, 2016.
......@@ -53,7 +53,7 @@ Status of This Memo
Thakore, et al. Expires September 22, 2016 [Page 1]
Thakore, et al. Expires September 2, 2016 [Page 1]
Internet-Draft SCTE-URN March 2016
......@@ -109,7 +109,7 @@ Table of Contents
Thakore, et al. Expires September 22, 2016 [Page 2]
Thakore, et al. Expires September 2, 2016 [Page 2]
Internet-Draft SCTE-URN March 2016
......@@ -165,7 +165,7 @@ Internet-Draft SCTE-URN March 2016
Thakore, et al. Expires September 22, 2016 [Page 3]
Thakore, et al. Expires September 2, 2016 [Page 3]
Internet-Draft SCTE-URN March 2016
......@@ -221,7 +221,7 @@ Internet-Draft SCTE-URN March 2016
Thakore, et al. Expires September 22, 2016 [Page 4]
Thakore, et al. Expires September 2, 2016 [Page 4]
Internet-Draft SCTE-URN March 2016
......@@ -247,7 +247,7 @@ Internet-Draft SCTE-URN March 2016
The SCTE specifications are publicly available and are licensed to
manufacturers on a nondiscriminatory basis. SCTE will maintain the
corresponding specifications where the regustered resources are
corresponding specifications where the registered resources are
referenced or used.
6. IANA Considerations
......@@ -277,7 +277,7 @@ Internet-Draft SCTE-URN March 2016
Thakore, et al. Expires September 22, 2016 [Page 5]
Thakore, et al. Expires September 2, 2016 [Page 5]
Internet-Draft SCTE-URN March 2016
......@@ -296,15 +296,15 @@ Internet-Draft SCTE-URN March 2016
[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
May 1997, <http://www.rfc-editor.org/info/rfc2141>.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
DOI 10.17487/RFC2629, June 1999,
<http://www.rfc-editor.org/info/rfc2629>.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406,
October 2002, <http://www.rfc-editor.org/info/rfc3406>.
[RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary",
RFC 7749, DOI 10.17487/RFC7749, February 2016,
<http://www.rfc-editor.org/info/rfc7749>.
9.2. Informative References
[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for
......@@ -320,8 +320,24 @@ Internet-Draft SCTE-URN March 2016
DOI 10.17487/RFC6289, June 2011,
<http://www.rfc-editor.org/info/rfc6289>.
[SANN] Society of Cable Telecommunications Engineers, "SCTE
Assigned Name and Number Registry".
Authors' Addresses
Thakore, et al. Expires September 2, 2016 [Page 6]
Internet-Draft SCTE-URN March 2016
Darshak Thakore (editor)
CableLabs
858 Coal Creek Circle
......@@ -332,12 +348,6 @@ Authors' Addresses
URI: http://www.cablelabs.com
Thakore, et al. Expires September 22, 2016 [Page 6]
Internet-Draft SCTE-URN March 2016
Niem Dang
Society of Cable Telecommunications Engineers
140 Philips Road
......@@ -379,14 +389,4 @@ Internet-Draft SCTE-URN March 2016
Thakore, et al. Expires September 22, 2016 [Page 7]
Thakore, et al. Expires September 2, 2016 [Page 7]
......@@ -287,7 +287,7 @@ li, p {
<meta name="dct.creator" content="Thakore, D., Ed., Dang, N., and G. Hughes" />
<meta name="dct.identifier" content="urn:ietf:id:draft-dthakore-scte-urn-latest" />
<meta name="dct.issued" scheme="ISO8601" content="2016-3-21" />
<meta name="dct.issued" scheme="ISO8601" content="2016-3" />
<meta name="dct.abstract" content="This document describers the Namespace Identifier (NID) 'scte' for Uniform Resource Names (URNs) used to identify resources published by the Society of Cable Telecommunications Engineers (SCTE). SCTE specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the SCTE." />
<meta name="description" content="This document describers the Namespace Identifier (NID) 'scte' for Uniform Resource Names (URNs) used to identify resources published by the Society of Cable Telecommunications Engineers (SCTE). SCTE specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the SCTE." />
......@@ -311,7 +311,7 @@ li, p {
<td class="right">N. Dang</td>
</tr>
<tr>
<td class="left">Expires: September 22, 2016</td>
<td class="left">Expires: September 2, 2016</td>
<td class="right">SCTE</td>
</tr>
<tr>
......@@ -324,7 +324,7 @@ li, p {
</tr>
<tr>
<td class="left"></td>
<td class="right">March 21, 2016</td>
<td class="right">March 2016</td>
</tr>
......@@ -348,7 +348,7 @@ li, p {
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on September 22, 2016.</p>
<p>This Internet-Draft will expire on September 2, 2016.</p>
<h1 id="rfc.copyrightnotice">
<a href="#rfc.copyrightnotice">Copyright Notice</a>
</h1>
......@@ -484,7 +484,7 @@ li, p {
<p id="rfc.section.4.p.2">The use of URNs should also help specification authors to maintain different versions of URNs and dependencies between URNs across different versions of SCTE specifications if they so wish. </p>
<h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> Community Considerations</h1>
<p id="rfc.section.5.p.1">Participants involved in the development and usage of SCTE specifications and cable industry deployments will benefit from the publication of this namespace by providing consistent and reliable names for the XML namespaces, schema locations, and similar identifiers of physical data models published within SCTE specifications. </p>
<p id="rfc.section.5.p.2">The SCTE specifications are publicly available and are licensed to manufacturers on a nondiscriminatory basis. SCTE will maintain the corresponding specifications where the regustered resources are referenced or used. </p>
<p id="rfc.section.5.p.2">The SCTE specifications are publicly available and are licensed to manufacturers on a nondiscriminatory basis. SCTE will maintain the corresponding specifications where the registered resources are referenced or used. </p>
<h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a href="#IANA" id="IANA">IANA Considerations</a></h1>
<p id="rfc.section.6.p.1">This document adds a new entry ("scte") in the urn-namespaces registry. This is the defining document for the entry. The entry can be found in the <a href="#IANA-URN">Uniform Resource Names (URN) Namespaces</a> <cite title="NONE">[IANA-URN]</cite> Registry.</p>
<h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a href="#Security" id="Security">Security Considerations</a></h1>
......@@ -515,15 +515,15 @@ li, p {
</tr>
<tr>
<td class="reference">
<b id="RFC2629">[RFC2629]</b>
<b id="RFC3406">[RFC3406]</b>
</td>
<td class="top"><a>Rose, M.</a>, "<a href="http://tools.ietf.org/html/rfc2629">Writing I-Ds and RFCs using XML</a>", RFC 2629, DOI 10.17487/RFC2629, June 1999.</td>
<td class="top"><a>Daigle, L.</a>, <a>van Gulik, D.</a>, <a>Iannella, R.</a> and <a>P. Faltstrom</a>, "<a href="http://tools.ietf.org/html/rfc3406">Uniform Resource Names (URN) Namespace Definition Mechanisms</a>", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002.</td>
</tr>
<tr>
<td class="reference">
<b id="RFC3406">[RFC3406]</b>
<b id="RFC7749">[RFC7749]</b>
</td>
<td class="top"><a>Daigle, L.</a>, <a>van Gulik, D.</a>, <a>Iannella, R.</a> and <a>P. Faltstrom</a>, "<a href="http://tools.ietf.org/html/rfc3406">Uniform Resource Names (URN) Namespace Definition Mechanisms</a>", BCP 66, RFC 3406, DOI 10.17487/RFC3406, October 2002.</td>
<td class="top"><a>Reschke, J.</a>, "<a href="http://tools.ietf.org/html/rfc7749">The "xml2rfc" Version 2 Vocabulary</a>", RFC 7749, DOI 10.17487/RFC7749, February 2016.</td>
</tr>
</tbody>
</table>
......@@ -548,6 +548,12 @@ li, p {
</td>
<td class="top"><a>Cardona, E.</a>, <a>Channabasappa, S.</a> and <a>J-F. Mule</a>, "<a href="http://tools.ietf.org/html/rfc6289">A Uniform Resource Name (URN) Namespace for CableLabs</a>", RFC 6289, DOI 10.17487/RFC6289, June 2011.</td>
</tr>
<tr>
<td class="reference">
<b id="SANN">[SANN]</b>
</td>
<td class="top"><a>Society of Cable Telecommunications Engineers</a>, "<a>SCTE Assigned Name and Number Registry</a>"</td>
</tr>
</tbody>
</table>
<h1 id="rfc.authors">
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment