DOCSLIB.ORG

CSIP) Conformance Test Procedures Sunspec Test Procedures

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Status: Approved Version: 1.2 SunSpec Common Smart Inverter Profile (CSIP) Conformance Test Procedures SunSpec Test Procedures Abstract This document provides conformance test procedures for compliance with the requirements specified in the Common Smart Inverter Profile. SunSpec CSIP Conformance Test Procedures 1 SunSpec Alliance Copyright © SunSpec Alliance 2019. All Rights Reserved. All other copyrights and trademarks are the property of their respective owners. License Agreement and Copyright Notice This document and the information contained herein is provided on an "AS IS" basis and the SunSpec Alliance DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. This document may be used, copied, and furnished to others, without restrictions of any kind, provided that this document itself may not be modified in anyway, except as needed by the SunSpec Technical Committee and as governed by the SunSpec IPR Policy. The complete policy of the SunSpec Alliance can be found at SunSpec Alliance. Prepared by the SunSpec Alliance 4040 Moorpark Avenue, Suite 110 Website: SunSpec Alliance San Jose, CA 95117 Email: [email protected] SunSpec CSIP Conformance Test Procedures 2 SunSpec Alliance Revision History Version Date Comments 0.9 01-31-2018 Draft version Incorporates community review comments and 1.0 05-31-2018 corrects typographical and cross-reference errors 1.2 07-24-2019 Moved test requirements tracking to a single section. Removed test prerequisite sections. Removed requirement for testing with HTTP. Changed the Server [S], Client [C] terminology to Server [S], Client [C], Test Server [TS], Test Client [TC]. Removed redundant tests: CORE-007, CORE- 008, CORE-020. Updated test criteria to clarify which system types for which each test is applicable and the role of each test element. SunSpec CSIP Conformance Test Procedures 3 SunSpec Alliance About the SunSpec Alliance The SunSpec Alliance is a trade alliance of developers, manufacturers, operators, and service providers together pursuing open information standards for the distributed energy industry. SunSpec standards address most operational aspects of PV, storage, and other distributed energy power plants on the smart grid, including residential, commercial, and utility-scale systems, thus reducing cost, promoting innovation, and accelerating industry growth. Over 100 organizations are members of the SunSpec Alliance, including global leaders from Asia, Europe, and North America. Membership is open to corporations, nonprofits, and individuals. For more information about the SunSpec Alliance, or to download SunSpec specifications at no charge, visit sunspec.org. About the SunSpec Specification Process SunSpec Alliance specifications are initiated by SunSpec members to establish an industry standard for mutual benefit. Any SunSpec member can propose a technical work item. Given sufficient interest and time to participate, and barring significant objections, a workgroup is formed, and its charter is approved by the board of directors. The workgroup meets regularly to advance the agenda of the team. The output of the workgroup is generally in the form of a SunSpec Interoperability Specification. These documents are considered to be normative, meaning there is a matter of conformance required to support interoperability. The revision and associated process of managing these documents is tightly controlled. Other documents are informative, or make some recommendation with regard to best practices, but are not a matter of conformance. Informative documents can be revised more freely and more frequently to improve the quality and quantity of information provided. SunSpec Interoperability Specifications follow a lifecycle pattern of: DRAFT, TEST, APPROVED, and SUPERSEDED. For more information or to download a SunSpec Alliance specification, go to https://sunspec.org/about-sunspec-specifications/. Acknowledgements The following contributed to this specification: Bob Fox, SunSpec Alliance Gene Hartsell, SunSpec Alliance Steve Kang, QualityLogic, Inc. Gordon Lum, Kitu Systems, Inc. James Mater, QualityLogic, Inc. Tom Tansy, SunSpec Alliance SunSpec CSIP Conformance Test Procedures 4 SunSpec Alliance Contents 1 Introduction .................................................................................................................................................................... 9 1.1 Purpose .................................................................................................................................... 9 1.2 Scope and Applicability ............................................................................................................ 9 1.3 Overview .................................................................................................................................. 9 1.3.1 Client-server Model ......................................................................................................... 9 1.3.2 CSIP Client-server Framework ...................................................................................... 10 1.4 References ............................................................................................................................. 10 2 Nomenclature ............................................................................................................................................................... 11 2.1 Terms ..................................................................................................................................... 11 2.2 Acronyms and Abbreviations ................................................................................................. 11 3 Testing Overview ......................................................................................................................................................... 12 3.1 IEEE 2030.5 Test Scope ........................................................................................................ 12 3.2 Testing Assumptions and Notation ............................................................................................... 13 3.2.1 General Communication and Payload Requirements .................................................... 13 3.2.2 Mandatory Conformance Requirements for All Tests.................................................... 13 3.2.3 Server [S] ...................................................................................................................... 16 3.2.4 Test Server [TS] ............................................................................................................ 16 3.2.5 Client [C] ....................................................................................................................... 17 3.2.6 Test Client [TC] ............................................................................................................. 17 3.2.7 Equipment Under Test .................................................................................................. 17 3.3 Format of Test Description .................................................................................................... 18 4 Profile Test Conformance ....................................................................................................................................... 19 5 Communication Fundamentals Tests ............................................................................................................... 21 COMM-001 - Basic Discovery (xmDNS/DNS-SD) ................................................................................ 22 COMM-002 - Basic Discovery (Out-of-Band) [C, A, S] ........................................................................ 24 COMM-003 - Basic Security [C,A,S] .................................................................................................... 25 COMM-004 - Advanced Security [C, A, S]........................................................................................... 26 6 Core Function Set Tests .......................................................................................................................................... 29 CORE-001 - HTTP Request [S] ........................................................................................................... 30 CORE-002 - HTTP Response [C, A, S] ................................................................................................ 32 CORE-003 - Polling Interaction [C, A] ................................................................................................ 34 CORE-004 - List Handling [S] ............................................................................................................. 36 CORE-005 - Basic Time [C, A, S] ........................................................................................................ 40 CORE-006 - Advanced Time [C, A, S] ................................................................................................. 42 SunSpec CSIP Conformance Test Procedures 5 SunSpec Alliance CORE-009 - Advanced End Device [C, A, S] ....................................................................................... 44 CORE-010 - Function Set Assignments [C, A, S] ................................................................................ 46 CORE-011 - Advanced Function Set Assignments [C, A, S]...............................................................
Recommended publications
  • Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers

    Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers

    Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers Elastic Load Balancing: Application Load Balancers Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Elastic Load Balancing Application Load Balancers Table of Contents What is an Application Load Balancer? .................................................................................................. 1 Application Load Balancer components ......................................................................................... 1 Application Load Balancer overview ............................................................................................. 2 Benefits of migrating from a Classic Load Balancer ........................................................................ 2 Related services ......................................................................................................................... 3 Pricing ...................................................................................................................................... 3 Getting started .................................................................................................................................
  • Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers

    Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers

    Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers Elastic Load Balancing: Application Load Balancers Elastic Load Balancing Application Load Balancers Table of Contents What is an Application Load Balancer? .................................................................................................. 1 Application Load Balancer components ......................................................................................... 1 Application Load Balancer overview ............................................................................................. 2 Benefits of migrating from a Classic Load Balancer ........................................................................ 2 Related services ......................................................................................................................... 3 Pricing ...................................................................................................................................... 3 Getting started .................................................................................................................................. 4 Before you begin ....................................................................................................................... 4 Step 1: Configure your target group ............................................................................................. 4 Step 2: Choose a load balancer type ...........................................................................................
  • Requests Documentation Release 2.26.0

    Requests Documentation Release 2.26.0

    Requests Documentation Release 2.26.0 Kenneth Reitz Sep 21, 2021 Contents 1 Beloved Features 3 2 The User Guide 5 2.1 Installation of Requests.........................................5 2.2 Quickstart................................................6 2.3 Advanced Usage............................................. 15 2.4 Authentication.............................................. 30 3 The Community Guide 33 3.1 Recommended Packages and Extensions................................ 33 3.2 Frequently Asked Questions....................................... 34 3.3 Integrations................................................ 35 3.4 Articles & Talks............................................. 35 3.5 Support.................................................. 36 3.6 Vulnerability Disclosure......................................... 36 3.7 Release Process and Rules........................................ 38 3.8 Community Updates........................................... 38 3.9 Release History.............................................. 39 4 The API Documentation / Guide 71 4.1 Developer Interface........................................... 71 5 The Contributor Guide 93 5.1 Contributor’s Guide........................................... 93 5.2 Authors.................................................. 96 Python Module Index 103 Index 105 i ii Requests Documentation, Release 2.26.0 Release v2.26.0. (Installation) Requests is an elegant and simple HTTP library for Python, built for human beings. Behold, the power of Requests: >>>r= requests.get ('https://api.github.com/user',
  • Pulse Secure Virtual Traffic Manager: Trafficscript Guide, V19.3

    Pulse Secure Virtual Traffic Manager: Trafficscript Guide, V19.3

    Pulse Secure Virtual Traffic Manager: TrafficScript Guide Supporting Pulse Secure Virtual Traffic Manager 19.3 Product Release 19.3 Published 15 October, 2019 Document Version 1.0 Pulse Secure Virtual Traffic Manager: TrafficScript Guide Pulse Secure, LLC 2700 Zanker Road, Suite 200 San Jose CA 95134 www.pulsesecure.net © 2019 by Pulse Secure, LLC. All rights reserved. Pulse Secure and the Pulse Secure logo are trademarks of Pulse Secure, LLC in the United States. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Pulse Secure, LLC assumes no responsibility for any inaccuracies in this document. Pulse Secure, LLC reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Pulse Secure Virtual Traffic Manager: TrafficScript Guide The information in this document is current as of the date on the title page. END USER LICENSE AGREEMENT The Pulse Secure product that is the subject of this technical documentation consists of (or is intended for use with) Pulse Secure software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at http://www.pulsesecure.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. © 2019 Pulse Secure, LLC. Pulse Secure Virtual Traffic Manager: TrafficScript Guide Contents PREFACE . 1 DOCUMENT CONVENTIONS . 1 TEXT FORMATTING CONVENTIONS . 1 COMMAND SYNTAX CONVENTIONS . 1 NOTES AND WARNINGS. 2 REQUESTING TECHNICAL SUPPORT . 2 SELF-HELP ONLINE TOOLS AND RESOURCES. 2 OPENING A CASE WITH PSGSC . 3 INTRODUCTION.
  • Web Tracking: Mechanisms, Implications, and Defenses Tomasz Bujlow, Member, IEEE, Valentín Carela-Español, Josep Solé-Pareta, and Pere Barlet-Ros

    Web Tracking: Mechanisms, Implications, and Defenses Tomasz Bujlow, Member, IEEE, Valentín Carela-Español, Josep Solé-Pareta, and Pere Barlet-Ros

    ARXIV.ORG DIGITAL LIBRARY 1 Web Tracking: Mechanisms, Implications, and Defenses Tomasz Bujlow, Member, IEEE, Valentín Carela-Español, Josep Solé-Pareta, and Pere Barlet-Ros Abstract—This articles surveys the existing literature on the of ads [1], [2], price discrimination [3], [4], assessing our methods currently used by web services to track the user online as health and mental condition [5], [6], or assessing financial well as their purposes, implications, and possible user’s defenses. credibility [7]–[9]. Apart from that, the data can be accessed A significant majority of reviewed articles and web resources are from years 2012 – 2014. Privacy seems to be the Achilles’ by government agencies and identity thieves. Some affiliate heel of today’s web. Web services make continuous efforts to programs (e.g., pay-per-sale [10]) require tracking to follow obtain as much information as they can about the things we the user from the website where the advertisement is placed search, the sites we visit, the people with who we contact, to the website where the actual purchase is made [11]. and the products we buy. Tracking is usually performed for Personal information in the web can be voluntarily given commercial purposes. We present 5 main groups of methods used for user tracking, which are based on sessions, client by the user (e.g., by filling web forms) or it can be collected storage, client cache, fingerprinting, or yet other approaches. indirectly without their knowledge through the analysis of the A special focus is placed on mechanisms that use web caches, IP headers, HTTP requests, queries in search engines, or even operational caches, and fingerprinting, as they are usually very by using JavaScript and Flash programs embedded in web rich in terms of using various creative methodologies.
  • 5G; 5G System; Access and Mobility Management Services; Stage 3 (3GPP TS 29.518 Version 15.0.0 Release 15)

    5G; 5G System; Access and Mobility Management Services; Stage 3 (3GPP TS 29.518 Version 15.0.0 Release 15)

    ETSI TS 129 518 V15.0.0 (2018-09) TECHNICAL SPECIFICATION 5G; 5G System; Access and Mobility Management Services; Stage 3 (3GPP TS 29.518 version 15.0.0 Release 15) 3GPP TS 29.518 version 15.0.0 Release 15 1 ETSI TS 129 518 V15.0.0 (2018-09) Reference RTS/TSGC-0429518vf00 Keywords 5G ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.
  • Towards an Ontology of HTTP Interactions Mathieu Lirzin, Béatrice Markhoff

    Towards an Ontology of HTTP Interactions Mathieu Lirzin, Béatrice Markhoff

    Towards an ontology of HTTP interactions Mathieu Lirzin, Béatrice Markhoff To cite this version: Mathieu Lirzin, Béatrice Markhoff. Towards an ontology of HTTP interactions. [Research Report] Université de Tours - LIFAT. 2020. hal-02901879 HAL Id: hal-02901879 https://hal.archives-ouvertes.fr/hal-02901879 Submitted on 17 Jul 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Towards an ontology of HTTP interactions Mathieu Lirzin1;2[0000−0002−8366−1861] and B´eatriceMarkhoff2[0000−0002−5171−8499] 1 N´er´eide,8 rue des d´eport´es,37000 Tours, France [email protected] 2 LIFAT EA 6300, Universit´ede Tours, Tours, France [email protected] Abstract. Enterprise information systems have adopted Web-based foun- dations for exchanges between heterogeneous programmes. These programs provide and consume via Web APIs some resources identified by URIs, whose representations are transmitted via HTTP. Furthermore HTTP re- mains at the heart of all Web developments (Semantic Web, linked data, IoT...). Thus, situations where a program must be able to reason about HTTP interactions (request-response) are multiplying. This requires an explicit formal specification of a shared conceptualization of those inter- actions.
  • X41 D-SEC Gmbh Dennewartstr

    X41 D-SEC Gmbh Dennewartstr

    Browser Security White PAPER Final PAPER 2017-09-19 Markus VERVIER, Michele Orrù, Berend-Jan WEVER, Eric Sesterhenn X41 D-SEC GmbH Dennewartstr. 25-27 D-52068 Aachen Amtsgericht Aachen: HRB19989 Browser Security White PAPER Revision History Revision Date Change Editor 1 2017-04-18 Initial Document E. Sesterhenn 2 2017-04-28 Phase 1 M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 3 2017-05-19 Phase 2 M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 4 2017-05-25 Phase 3 M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 5 2017-06-05 First DrAFT M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 6 2017-06-26 Second DrAFT M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 7 2017-07-24 Final DrAFT M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 8 2017-08-25 Final PAPER M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 9 2017-09-19 Public Release M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER X41 D-SEC GmbH PAGE 1 OF 196 Contents 1 ExECUTIVE Summary 7 2 Methodology 10 3 Introduction 12 3.1 Google Chrome . 13 3.2 Microsoft Edge . 14 3.3 Microsoft Internet Explorer (IE) . 16 4 Attack Surface 18 4.1 Supported Standards . 18 4.1.1 WEB TECHNOLOGIES . 18 5 Organizational Security Aspects 21 5.1 Bug Bounties . 21 5.1.1 Google Chrome . 21 5.1.2 Microsoft Edge . 22 5.1.3 Internet Explorer . 22 5.2 Exploit Pricing . 22 5.2.1 ZERODIUM . 23 5.2.2 Pwn2Own .
  • Httpclient-Tutorial.Pdf

    Httpclient-Tutorial.Pdf

    HttpClient Tutorial Oleg Kalnichevski Jonathan Moore Jilles van Gurp Preface .................................................................................................................................... iv 1. HttpClient scope .......................................................................................................... iv 2. What HttpClient is NOT .............................................................................................. iv 1. Fundamentals ....................................................................................................................... 1 1.1. Request execution ...................................................................................................... 1 1.1.1. HTTP request .................................................................................................. 1 1.1.2. HTTP response ............................................................................................... 2 1.1.3. Working with message headers ........................................................................ 2 1.1.4. HTTP entity .................................................................................................... 3 1.1.5. Ensuring release of low level resources ............................................................ 5 1.1.6. Consuming entity content ................................................................................ 6 1.1.7. Producing entity content .................................................................................. 6 1.1.8. Response
  • Fortiadc Server Load Balance Script Deployment Guide

    Fortiadc Server Load Balance Script Deployment Guide

    FortiADC Server Load Balance Script Deployment Guide VERSION 5.2.0 FORTINET DOCUMENT LIBRARY http://docs.fortinet.com FORTINET VIDEO GUIDE http://video.fortinet.com FORTINET BLOG https://blog.fortinet.com CUSTOMER SERVICE & SUPPORT https://support.fortinet.com FORTIGATE COOKBOOK http://cookbook.fortinet.com FORTINET TRAINING SERVICES http://www.fortinet.com/training FORTIGUARD CENTER http://www.fortiguard.com END USER LICENSE AGREEMENT http://www.fortinet.com/doc/legal/EULA.pdf FEEDBACK Email: [email protected] Friday, December 28, 2018 FortiADC Link Load Balance Deployment Guide First Edition TABLE OF CONTENTS TABLE OF CONTENTS 3 Configuration Overview 4 Deployment –Content Routes Based on URI String 9 Introduction FortiADC SLB supports Lua scripts to perform actions that are not currently supported by the built-in feature set. Scripts enable you to use predefined script commands and variables to manipulate the HTTP request/response or select a content route. The multi-script support feature enables you to use multiple scripts by setting their sequence of execution. Here are FortiADC's predefined scripts and commands that you can copy and customize in the GUI/Server Load Balance/Scripting page. Configuration Overview The script used in the SLB/VS configuration that is triggered when the associated virtual server receives an HTTP request or response. Then, it does the programmed action. The events in which you can create them are shown as below: Event name Description RULE_INIT The event is used to initialize global or static variables used within a script. It is triggered when a script is added or modified, or when the device starts up, or when the software is restarted.
  • Identity Provider (IDP) Technical Specifications Version 1.3

    Identity Provider (IDP) Technical Specifications Version 1.3

    Identity & Authorization Management (I.AM) Identity Provider (IDP) Technical specifications Version 1.3 This document is provided to you free of charge by the eHealth platform Willebroekkaai 38 – 1000 Brussel 38, Quai de Willebroeck – 1000 Bruxelles All are free to circulate this document with reference to the URL source. Table of contents Table of contents .................................................................................................................................................... 2 1. Document management ........................................................................................................................ 4 1.1 Document history ................................................................................................................................... 4 2. Introduction ........................................................................................................................................... 5 2.1 Goal of the service ................................................................................................................................. 5 2.2 Identity ................................................................................................................................................... 5 2.3 Trust ....................................................................................................................................................... 6 2.3.1 Web SSO ................................................................................................................................................
  • Security Analysis of Real-Life Openid Connect Implementations

    Security Analysis of Real-Life Openid Connect Implementations

    Single Sign-On Security: Security Analysis of real-life OpenID Connect Implementations Lauritz Holtmann Master’s Thesis – September 30, 2020. Chair for Network and Data Security. Supervisor: Dr.-Ing. Christian Mainka Advisor: Prof. Dr. Jörg Schwenk Advisor: Dr.-Ing. Vladislav Mladenov Abstract OpenID Connect 1.0 is an authentication protocol that extends the OAuth 2.0 Au- thorization Framework. A typical OpenID Connect 1.0 setup involves three parties: an End-User who wants to sign-in at a service, the OpenID Provider that authenti- cates the End-User and a Relying Party that provides a service to the End-User. Im- plementing Single Sign-On protocols like OpenID Connect enables Service Providers to delegate authorization and authentication tasks to a dedicated third party. This decentralized scenario comes with flexibility for implementing entities and usability benefits for End-Users but also introduces new challenges regarding secure andre- liable authentication mechanisms. In this thesis, three novel variants of attacks on OpenID Connect implementations and two attacks on the OpenID Connect speci- fication are presented. Besides these novel attacks, four Identity Provider andfive Service Provider implementations are evaluated against a set of previously known attacks and requirements resulting from the specification and current security best practices. During the execution of the analysis, NodeJS implementations of the Identity Provider and Service Provider parts of the OpenID Connect specification were created, which are also introduced in this thesis. Finally, common vulnerability patterns observed within the set of OpenID Connect implementations are derived and recommendations for additions to the OpenID Connect security considerations are given.