Voglio sapere a riguardo di…

Federal Register / Vol. 86, No. 151 / Tuesday, August 10, 2021 / Rules and Regulations which encrypts data to hide information from electronic observers on the internet. NAESB also deleted all references to the Secure Sockets Layer protocol in the standards.
14. Concerning identification key lengths, the Sandia Surety Assessment recommended that Rivest-ShamirAdelman keys 15 must be no shorter than 2048 bits, Elliptic Curve Digital Signature Algorithm keys 16 must be no shorter than 224 bits, Hash 17 algorithms should be from the Secure Hash Algorithm SHA2 18 or SHA3
families, and acceptable Advanced Encryption Standard key lengths range from 128, to 192, to 256. The Sandia Surety Assessment recommended that, in general, implementors use the largest feasible key length consistent with implementation of current business processes. In response, NAESB deleted Standard 4.3.83 to remove legacy support references and maintain a minimum encryption strength of 128
bits. Further, NAESB revised existing Standards 10.2.34 and 10.3.15 to delete a proprietary Pretty Good Privacy PGP 19-related hyperlink and to accommodate license-free OpenPGP, respectively. NAESB also adopted a new Standard 10.2.39 to specify that OpenPGP should be used to create public and private keys for privacy and digital signature applications.
15. Further, NAESB revised existing Standards 4.3.60, 4.3.84, 10.3.4, and 10.3.16 to specify HTTPS, which is an encrypted version of HTTP, whenever a secure communication is required to protect information in transit and support overall privacy needs.

jbell on DSKJLSW7X2PROD with RULES

b. Modifications in Response to Industry Requests 16. The following section describes standards development efforts undertaken by NAESB in response to industry requests or through the normal course of WGQ activities that resulted in modifications to the Nomination Related Standards, Quadrant EDM
1.2 and recommends support for Transport Layer Security Version 1.3 by the year 2024.
15 Rivest-Shamir-Adelman is a public key infrastructure algorithm composed of a public component and a private component that is typically installed on a recognized Certificate Authority.
16 Elliptic Curve Digital Signature Algorithm public keys generate an encrypted signature to validate data.
17 A Hash is a cryptology technique used for digital signatures in which a series of numbers that may represent, for example, a password, an image, a document, or an executable file is used to generate a cryptographic hash i.e., a large number.
18 SHA2 is a set of cryptographic hash functions.
19 PGP is a proprietary i.e., an organization must pay to use it encryption program developed to enhance the confidentiality and integrity of data.

VerDate Sep<11>2014

16:06 Aug 09, 2021

Jkt 253001

Related Standards, and an effort that impacted multiple sets of standards.
NAESB made corresponding revisions, where appropriate, to the related data sets and technical implementation as part of the standards development effort.
i. Nomination Related Standards 17. NAESB revised existing Standards 1.3.27, 1.4.1, and 1.4.2 to add a new data element Capacity Block ID to allow a Service Requester to determine which primary point rights of the contract their segmented nomination 20
is using and eliminate an existing manual business process from the TSP
to automate the business process.
ii. Quadrant Electronic Delivery Mechanism Related Standards 18. NAESB developed two new standards, Standard 4.3.107 to establish a standard data retention period for retrieval of Operationally Available data from the Informational Postings website, and Standard 4.3.108, to establish a standard data retention period for retrieval of Notices for the subcategories of Critical, Non-Critical, and Planned Service Outage from the Informational Postings website.
iii. Revisions Impacting Multiple Standards 19. NAESB revised multiple standards 21 and data sets 22 to remove references to the term gigacalories and add the term gigajoules, as the standard quantity for nominations, confirmations, and scheduling in Mexico.
iv. Other Material in NAESBs Report 20. NAESB revised multiple data sets which impacted technical implementation documentation only.
21. Further, NAESB revised its optional model contracts and corresponding Mexican and Canadian Addendums to reflect a standard digital representation of natural gas trade events. NAESB states that these revisions are intended to capitalize on smart contracts and distributed ledger technologies.
20 In order for a Service Requester to have control over its segmented nominations, the Transportation Service Provider TSP will require a Capacity Block ID to be submitted with each nomination line item specifying a Transaction Type of Segmented.
21 NAESB WGQ Version 3.2 Standards 1.3.14, 1.3.15, 1.3.82, and 3.3.3.
22 NAESB WGQ Version 3.2 Standards 0.4.1
through 0.4.3, 1.4.1, 1.4.3 through 1.4.6, 2.4.1, 2.4.6, 2.4.17, 3.4.1, 3.4.2, and 5.4.24 through 5.4.26.

PO 00000

Frm 00005

Fmt 4700

Sfmt 4700

43593

B. NAESBs Process 22. NAESB used its consensus procedures to develop and approve the WGQ Version 3.2 Standards. As the Commission found in Order No. 587, the adoption of consensus standards is appropriate, because the consensus process helps ensure the reasonableness of the standards by requiring that the standards draw support from a broad spectrum of industry participants representing all segments of the industry. Moreover, since the industry itself must conduct business under these standards, the Commissions regulations should reflect those standards that have the widest possible support. In section 12d of the National Technology Transfer and Advancement Act of 1995 NTT&AA,23 Congress affirmatively requires federal agencies to use technical standards developed by voluntary consensus standards organizations, like NAESB, as means to carry out policy objectives or activities determined by the agencies unless an agency determines that the use of such standards would be inconsistent with applicable law or otherwise impractical.
C. Adoption of Version 3.2 of the Standards 23. In the Version 3.2 NOPR, the Commission proposed to incorporate by reference, in its regulations, Version 3.2
of the NAESB WGQ consensus business practice standards, with the exception of NAESBs standards specifying the terms of optional model contracts and the eTariff-related standards.24 None of the commenters opposed the Commissions proposal to incorporate by reference the NAESB WGQ Version 3.2 business practice standards as proposed in the Version 3.2 NOPR.25
24. After a review of the comments filed in response to the Version 3.2
NOPR, and because the revisions made by NAESB in this version of the standards are designed to enhance the natural gas industries system and software security measures and to clarify the processing of certain business transactions, we amend Part 284 of the Commissions regulations to incorporate by reference the NAESB WGQ Version 3.2 business practice standards, with the exceptions as explained in the Version 3.2 NOPR of the optional model contracts and the eTariff-related standards.
23 Public Law 104113, 12d, 110 Stat. 775
1996.
24 Version 3.2 NOPR, 174 FERC 61,103 at n.1 &
P 19.
25 NAESBs clarifying comments regarding revised existing Standards 4.3.60 and 10.3.16 are discussed separately in section II above.

E:FRFM10AUR1.SGM

10AUR1