[urn] URN registration request for SCTE
Gary Hughes <ghughes1138@gmail.com> Tue, 20 August 2019 16:17 UTC
Return-Path: <ghughes1138@gmail.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB90120105 for <urn@ietfa.amsl.com>; Tue, 20 Aug 2019 09:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ez8jKn4R6HOs for <urn@ietfa.amsl.com>; Tue, 20 Aug 2019 09:17:40 -0700 (PDT)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C92B012082C for <urn@ietf.org>; Tue, 20 Aug 2019 09:17:39 -0700 (PDT)
Received: by mail-ed1-x533.google.com with SMTP id p28so6961300edi.3 for <urn@ietf.org>; Tue, 20 Aug 2019 09:17:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=XoxZIFQ7nkFJ82dCFM2XQZVRyYM3C49C7XWstec0gSI=; b=bftAIbqPPu+79G888NQnzVIj4hhmcyD2fGwwrp5UDPKF5OCWnaN1RJwgtrbAz3d15+ 3RBR95JZoX5E5Joaq6FPB/pMhfTCCZeYjBdahh9Z6Sea1Bol/Rc8zoMTwMeyaPGuQWS9 bLXezuUrEizPYbSjjXvVnnSuY9yzrBHp4H2lrrKK56Xl8UmaLvaIUFaITKybOHeNoKAp ysPKM2nuNgIhQU0hffHwM13XCnCwiXpKhXBJFjGaV4kuMes01qNarHNoS2F5hmhDEV3b 0lVpDUt0dTNKqdp8IN1xh3ogTvWSnfTj4L/yKlyc7gdhUYo2JTeeK425y/pxYLy9zdwF Y2zA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=XoxZIFQ7nkFJ82dCFM2XQZVRyYM3C49C7XWstec0gSI=; b=U6/80dg6eyGSI2IHoPM6N+HGsTV8PUKadE5IcLtMzB5aePenaCvwIK/r2TzmzJ42jA 5LX1MsYPZf9h4cNKz36Eoh1r7ljwpp46f0clNwsNrw8D/3JO0Edn0mA2C7I4X0BOCFga nLaXHuPVO2Y/ydhjKg7jq7vUFxoNzXAtBYN6cMXLDogOrfC77DS/00Lfy8hoB2cVqoAi svYMREVZJDOIFGV2lKZIRSlHLvueJPKq2JkJQcHCp2DbgKFaewIcv2tejvo2Hx7u+z5g 5yyQlmiC5hPc29HKOyMybRvoGpSDf7IgALUNM34M7/bZynARub19abT4j9X0SXcY7shI pqeg==
X-Gm-Message-State: APjAAAWu6u1ZMKbiyLge6DcfVTbBUD1JjnKjPHiexjlvYtD5My4rH3Tu 1jvJlIqa43pyUntSZfIkQ16WcvVPS6ffmZ5aXH0AbZirJ18=
X-Google-Smtp-Source: APXvYqw8MA2dS84XT5H/gHGtEqjSb+VfUdZjhMQSponazkuZeSTCD1IDEEAxWOrSudbiiPfwD1Y8ah7mmiCOpY82ySs=
X-Received: by 2002:a50:b875:: with SMTP id k50mr31990168ede.232.1566317857652; Tue, 20 Aug 2019 09:17:37 -0700 (PDT)
MIME-Version: 1.0
From: Gary Hughes <ghughes1138@gmail.com>
Date: Tue, 20 Aug 2019 12:17:26 -0400
Message-ID: <CAMDWyD+nMDEf8+YdNW6i5rGzRUC4Pur1rj6ghm4pbugLsXJqrA@mail.gmail.com>
To: urn@ietf.org
Cc: Paul Woidke <paul.woidke@icloud.com>, Dean Stoneback <dstoneback@scte.org>
Content-Type: multipart/alternative; boundary="00000000000082c2a105908ecb36"
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/-elz2RLUevSGUXsQwYhugZmG9e8>
Subject: [urn] URN registration request for SCTE
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2019 16:26:42 -0000
The Society of Cable Telecommunications Engineers (SCTE), an ANSI-accredited SDO, is requesting fast track registration for the 'scte' namespace identifier. The completed template follows. regards, Gary Hughes ========================================================= IETF URN Registration for SCTE *Namespace Identifier*: scte *Version*: 1 *Date*:*.* 2019-08-19 *Registrant*: The Society of Cable Telecommunications Engineers (SCTE) standards program is an ANSI-accredited Standards Development Organization 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. Name: Society of Cable Telecommunications Engineers 140 Philips Road, Exton, PA 19341-1318, USA Designated contact: Role: Manager, Standards Email: standards@scte.org *Purpose*:*.* Occasionally, SCTE specification efforts require identifiers in a managed namespace so that they are unique and persistent. To ensure that the uniqueness is absolute, the registration of a specific Uniform Resource Name (URN) Namespace Identifier (NID) for use by SCTE is being specified in RFC8141, in full conformance with the NID registration process specified in RFC8141 [RFC8141] When SCTE specifications require the use of data models, URN Namespaces are key constructs to manage the definitions of those data models reliably with persistence and uniqueness. 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. *Syntax*: The Namespace Specific String (NSS) of all URNs that use the "scte" NID will have the following structure: urn:scte:{SCTEresource}:{ResourceSpecificString} where the "SCTEresource" is a US-ASCII string that conforms to the URN syntax requirements of [RFC8141]. SCTE publishes information regarding the registered resources in the corresponding SCTE standards. The “SCTEresource” may be used to identify the SCTE standard or the project which defined the URN. The “ResourceSpecificString” specifies the name and optionally the edition (year) of the standard that first defined the URN. For example: urn:scte:dash:essential-event:2015 Event essentiality, first defined in the 2015 edition of the SCTE DASH specifications urn:scte:scte35:2013:xml XML representation of SCTE 35 commands, first defined in the 2013 edition of ANSI/SCTE 35 Published SCTE standards are freely downloadable from the SCTE web site at: https://www.scte.org/SCTE/Standards/Download_SCTE_Standards.aspx. *Assignment**: * 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 ( https://www.scte.org/SCTE/Standards/SCTE_Assigned_Names_and_Numbers_specification.aspx) and updated as needed. The SANN specification will only document URNs defined in SCTE standards. *Security and Privacy*: There are no additional security considerations other than those normally associated with the use and resolution of URNs in general, which are described in [RFC8141]. *Interoperability**: * SCTE standards are referenced by other SDOs and industry groups. Formally registering the “scte” NID will help ensure that collisions do not occur. *Resolution*: The namespace is not listed with a resolution discovery system; this is not applicable for this URN registration. *Documentation*: The SCTE Assigned Names and Numbers [SANN] specification will describe the use of “scte” namespace and procedures for requesting assignment of new resources and values in that namespace. This will be available at https://www.scte.org/SCTE/Standards/SCTE_Assigned_Names_and_Numbers_specification.aspx *Additional Information*: 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. 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. *Revision Information*: This application is a revision and resubmission of draft-dthakore-scte-urn-00
- [urn] URN registration request for SCTE Gary Hughes
- Re: [urn] URN registration request for SCTE Dale R. Worley
- Re: [urn] URN registration request for SCTE Hakala, Juha E
- Re: [urn] URN registration request for SCTE lars.svensson
- Re: [urn] URN registration request for SCTE Gary Hughes
- Re: [urn] URN registration request for SCTE Gary Hughes
- Re: [urn] URN registration request for SCTE lars.svensson