Commit 676ec361 authored by Darshak Thakore's avatar Darshak Thakore

updated TBD sections from text provided by Niem

parent e70f6496
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!DOCTYPE rfc SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/rfc2629.dtd" [
<!ENTITY RFC1737 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1737.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC4234 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4234.xml">
......@@ -128,7 +128,22 @@
<uri>http://www.scte.org</uri>
</address>
</author>
<author fullname="Gary Hughes" initials="G." surname="Hughes">
<organization abbrev="SeaChange">SeaChange International Inc.</organization>
<address>
<postal>
<street>50 Nagog Park</street>
<city>Acton</city>
<region>MA</region>
<code>01720</code>
<country>US</country>
</postal>
<email>gary.hughes@schange.com</email>
<uri>http://www.schange.com</uri>
</address>
</author>
<date month="March" year="2016"/>
<!-- month="March" is no longer necessary
note also, day="30" is optional -->
......@@ -174,7 +189,12 @@
<middle>
<section anchor="intro" title="Introduction">
<t>TO-BE-FILLED-BY-NIEM - need a paragraph on what SCTE is</t>
<t>The SCTE standards program is an ANSI-accredited forum for the development
of technical specifications supporting cable telecommunications.
SCTE standards work includes: data and telephony over cable;
application platform development; digital video; emergency alert systems;
network monitoring systems; cables, connectors and amplifiers;
construction and maintenance practices; energy management, and more.</t>
<t>Occasionally, SCTE specification efforts require identifiers in a
managed namespace so that they are unique and persistent. To ensure that
......@@ -214,7 +234,7 @@
Designated contact
<list>
<t>Role: Manager, Standards</t>
<t>Email: TO-BE-FILLED-BY-NIEM</t>
<t>Email: TBD</t>
</list>
</t>
</list>
......@@ -236,9 +256,10 @@
</t>
<t>
SCTE maintains a naming authority, ??? TO-BE-FILLED-BY-NIEM
that will manage the assignment of "SCTEresources" and the specific registration
values assigned for each resource class.
SCTE will maintain a naming authority, the SCTE Assigned Names and Numbers [SANN]
specification, that will contain the assignment of SCTE resource classes and the
specific registration values assigned for each resource class. This specification
will be published on the SCTE Standards Program website.
</t>
</list>
</t>
......@@ -247,8 +268,8 @@
Relevant ancillary documentation:
<list>
<t>
SCTE publishes information regarding the registered resources in the ????
TO-BE-FILLED-BY-NIEM
SCTE publishes information regarding the registered resources in the corresponding
SCTE standards.
</t>
</list>
</t>
......@@ -273,8 +294,8 @@
Identifier persistence considerations:
<list>
<t>
SCTE will update the ??? TO-BE-FILLED-BY-NIEM to document the registered resources
that use the "scte" NID.
SCTE will update the SCTE Assigned Names and Numbers specification to document the
registered resources that use the "scte" NID.
</t>
</list>
</t>
......@@ -342,10 +363,11 @@
<t>
The following example represents a hypothetical URL that could be assigned by SCTE.
<vspace/>
urn:scte:??? TO-BE-FILLED-BY-NIEM
urn:scte:dash:2015
</t>
<t>
This example defines the URN to be used for ??? TO-BE-FILLED-BY-NIEM
This example defines the URN to be used for for ANSI/SCTE 214-1 2015 “MPEG DASH for
IP-Based Cable Services Part 1: MPD Constraints and Extensions”
</t>
</section>
......
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