AUTOSAR   Adaptive Platform References

AUTOSAR 21-11 Adaptive Platform, Reference, Terms and word count

https://qiita.com/kaizen_nagoya/items/623047c3fdeb0a97cf44

Referenceを抜き書き。

|No.|title|doc|update|RFC/ISO/IEC/IEEE/ITU|qiita|
|:----|:----|:----|:----|:----|:----|
|1|Advanced Encryption Standard (AES) Key Wrap Algorithm https://tools.ietf.org/html/rfc3394|883| |3394|17|
|2|Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm https://tools.ietf.org/html/rfc5649|883| |5649|17|
|3|Agile Software Development: Principles, Patterns, and Practices|982| | |37|
|4|Algirdas Avizienis, Jean-Claude Laprie, Brian Randell, and Carl Landwehr, ’Basic Concepts and Taxonomy of Dependable and Secure Computing’, IEEE Transactions on Dependable and Secure Computing, Vol. 1, No. 1, January-March 2004 https://www.nasa.gov/pdf/636745main_day_3-algirdas_avizienis.pdf|721| | |21|
|5|API standards for Open Systems http://www.opengroup.org/austin/papers/wp-apis.txt|885| | |38|
|6|ATAMSM: Method for Architecture Evaluation, https://resources.sei.cmu.edu/asset_files/TechnicalReport/2000_005_001_13706.pdf|982| | |37|
|7|AUTOSAR Introduction, https://www.autosar.org/fileadmin/ABOUT/AUTOSAR_Introduction.pdf|885| | |38|
|8|AUTOSAR Specifications in general|930| | |32|
|9|Bjarne Stroustrup, Herb Sutter, C++ Core Guidelines, 2017. https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines|839| | |36|
|10|Bjarne Stroustrup, The C++ Programming Language, Fourth Edition, ISBN: 978-0-321-56384-2, Addison-Wesley, 2013.https://www.stroustrup.com/4th.html|839| | |36|
|11|BSI: Functionality Classes and Evaluation Methodology for Deterministic Random Number Generators (AIS), https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Zertifizierung/Interpretationen/AIS_20_Functionality_Classes_Evaluation_Methodology_DRNG_e.pdf?__blob=publicationFile|883| | |17|
|12|C++ Core Guidelines https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md|714| | |13|
|13|Camel case, https://en.wikipedia.org/wiki/CamelCase|714| | |12|
|14|ChaCha20-Poly1305 Cipher Suites for Transport Layer Security (TLS) https://rfc-editor.org/rfc/rfc7905.txt|883| |7905|17|
|15|Code-Pointer Integrity https://www.usenix.org/conference/osdi14/technical-sessions/presentation/kuznetsov|881| | |15|
|16|Conservative use of noexcept in the Library, http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3279.pdf|714| | |12|
|17|Copying and Comparing: Problems and Solutions, http://dx.doi.org/10.1007/3-540-45102-1_11|846| | |23|
|18|Cpp Styleguide, https://google.github.io/styleguide/cppguide.html#Type_Names|714| | |12|
|19|cppreferenc http://cppreference.com, online reference for the C and C++ languages and standard libraries, 2017|839| | |36|
|20|Data Distribution Service (DDS), Version 1.4, http://www.omg.org/spec/DDS/1.4|713| | |53|
|21|Data Integrity Pattern, http://en.wikipedia.org/wiki/Data_integrity|885| | |38|
|22|DDS Consolidated XML Syntax, Version 1.0, https://www.omg.org/spec/DDS-XML|713| | |53|
|23|DDS Interoperability Wire Protocol, Version 2.2, http://www.omg.org/spec/DDSI-RTPS/2.2|717| | |27|
|24|DDS Security, Version 1.1, https://www.omg.org/spec/DDS-SECURITY/1.1|713| | |53|
|25|Design guidelines for using parallel processing technologies on Adaptive Platform, AUTOSAR_EXP_ParallelProcessingGuidelines|885| | |38|
|26|Diagnostic Extract Template, AUTOSAR_TPS_DiagnosticExtractTemplate|709| | |10|
|27|Dynamic Memory Allocation and Fragmentation https://www.researchgate.net/publication/295010953_Dynamic_Memory_Allocation_and_Fragmentation|983| | |4|
|28|Dynamic Memory Allocation on Real-Time Linux https://static.lwn.net/images/conf/rtlws-2011/proc/Jianping.pdf|983| | |40|
|29|E2E Protocol Specification, AUTOSAR_PRS_E2EProtocol|706| | |14|
|30|Elliptic Curve Cryptography, https://www.secg.org/sec1-v2.pdf|883| | |17|
|31|Explanation of Adaptive Platform Design, AUTOSAR_EXP_PlatformDesign|721| | |21|
|32|Explanation of Adaptive Platform Software Architectural Decisions, AUTOSAR_EXP_SWArchitecturalDecisions|706| | |14|
|33|Explanation of ara::com API, AUTOSAR_EXP_ARAComAPI|713| | |53|
|34|Explanation of Safety Overview, AUTOSAR_EXP_SafetyOverview|706| | |14|
|35|Explanation of Sensor Interfaces, AUTOSAR_EXP_SensorInterfaces|911| | |47|
|36|Explanations of Adaptive Platform Design, AUTOSAR_EXP_PlatformDesign.pdf.|929| | |11|
|37|Extensible and Dynamic Topic Types for DDS, Version 1.2, https://www.omg.org/spec/DDS-XTypes/1.2|717| | |27|
|38|Financial institution encryption of wholesale financial messages: X9.23|883| | |17|
|39|Functional Cluster Shortnames, AUTOSAR_TR_FunctionalClusterShortnames|714| | |12|
|40|General Requirements specific to Adaptive Platform, AUTOSAR_RS_General|717| | |27|
|41|General Specification of Basic Software Modules, AUTOSAR_SWS_BSWGeneral|851| | |30|
|42|Generic Structure Template, AUTOSAR_TPS_GenericStructureTemplate|713| | |53|
|43|Glossary AUTOSAR_TR_Glossary https://www.autosar.org/fileadmin/user_upload/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf|709| | |10|
|44|Google C++ Style Guide, Google, 2017. https://google.github.io/styleguide/cppguide.html|839| | |36|
|45|Guide for Internet Standards Writers https://tools.ietf.org/html/rfc2360|883| |2360|17|
|46|Guide to the Software Engineering Body of Knowledge, Version 3.0, 　http://www.swebok.org|982| | |37|
|47|Guidelines for the use of the C++14 language in critical and safety-related systems, AUTOSAR_RS_CPP14Guidelines|881| | |15|
|48|Guidelines for using Adaptive Platform interfaces, AUTOSAR_EXP_AdaptivePlatformInterfacesGuidelines|721| | |21|
|49|High Integrity C++ (HIC++) v4.0, https://www.perforce.com/resources/qac/high-integrity-cpp-coding-standard|714| | |12|
|50|HMAC: Keyed-Hashing for Message Authentication https://tools.ietf.org/html/rfc2104|883| |2104|17|
|51|IEC 61508-3, Functional safety of electrical/electronic/programmable electronic|839| |61508-3|36|
|52|IEEE P1363: A Standard for RSA, Diffie-Hellman, and Elliptic-Curve Cryptography (Abstract)|883| |1363|17|
|53|IEEE Standard for Information Technology- Standardized Application Environment Profile (AEP)-POSIX Realtime and Embedded Application Support https://standards.ieee.org/findstds/standard/1003.13-2003.html|713| |1003.13|53|
|54|Information technology – Universal Coded Character Set (UCS), http://www.iso.org|713| | |53|
|55|Integration of DDS Security, AUTOSAR_TR_DDSSecurityIntegration|717| | |27|
|56|Interface Definition Language (IDL), Version 4.2, https://www.omg.org/spec/IDL/4.2|717| | |27|
|57|Internationalization Updates to RFC 5280 https://tools.ietf.org/html/rfc8399|883| |8399|17|
|58|Internationalized Email Addresses in X.509 Certificates https://tools.ietf.org/html/rfc8398|883| |8398|17|
|59|Internet X.509 Certificate Request Message Format https://tools.ietf.org/html/rfc2511|883| |2511|17|
|60|Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile https://datatracker.ietf.org/doc/html/rfc3280|883| |3280|17|
|61|Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF) https://tools.ietf.org/html/rfc4211|883| |4211|17|
|62|ISO 23150 Road vehicles–Data communication between sensors and data fusion unit for automated driving functions–Logical interface|911| |23150|47|
|63|ISO 26262-6, Road vehicles - Functional safety - Part 6: Product development at the software level, International Organization for Standardization, 2011.|839| |26262-6|36|
|64|ISO 26262-7, Road vehicles - Functional safety - Part 7:, International Organization for Standardization, 2011.|839| |26262-7|36|
|65|ISO 26262-8, Road vehicles - Functional safety - Part 8: Supporting processes, International Organization for Standardization, 2011.|839| |26262-8|36|
|66|ISO 26262:2018 (all parts) – Road vehicles – Functional Safety http://www.iso.org|706| |26262|14|
|67|ISO 42010:2011 – Systems and software engineering – Architecture description http://www.iso.org|982| |42010|37|
|68|ISO IEC 9797-3:2011 Amd 1:2020(en) Information technology - Security techniques - Message Authentication Codes (MAC), http://www.iso.org|883| |9797|17|
|69|ISO/IEC 11889-1:2015 Information technology - Trusted platform module library - Part 1: Architecture http://www.iso.org|883| |11889|17|
|70|ISO/IEC 14882:2003, The C++ Standard Incorporating Technical Corrigendum 1, International Organization for Standardization, 2003.|839| |14882|36|
|71|ISO/IEC 14882:2011, Information technology – Programming languages – C++, http://www.iso.org|717| |14882|27|
|72|ISO/IEC 14882:2014, Information technology – Programming languages – C++ http://www.iso.org|903| |14882|9|
|73|ISO/IEC 9796-2:2010 Information technology - Security techniques - Digital signature schemes giving message recovery - Part 2: Integer factorization based mechanisms, http://www.iso.org|883| |9796|17|
|74|ISO/IEC C++ 2003 Language DDS PSM, Version 1.0, https://www.omg.org/spec/DDS-PSM-Cxx/1.0|717| | |27|
|75|Joint Strike Fighter Air Vehicle C++ Coding Standards for the System Development and Demonstration Program, Document Number 2RDU00001 Rev C, Lockheed Martin Corporation, 2005.|839| | |36|
|76|Joshua Bloch, Effective Java, Second Edition, ISBN: 978-0321356680, AddisonWesley, 2008|839| | |36|
|77|Jump-oriented Programming: A New Class of Code-reuse Attack|881| | |15|
|78|Keying and Authentication for Routing Protocols (KARP) Design Guidelines https://tools.ietf.org/html/rfc6518|883| |6518|17|
|79|Layered Software Architecture, AUTOSAR_EXP_LayeredSoftwareArchitecture|709| | |10|
|80|Log and Trace Protocol Specification with protocol version "1", AUTOSAR_PRS_LogAndTraceProtocol from Release R20-11|853| | |28|
|81|Log and Trace Protocol Specification with protocol version "2", AUTOSAR_PRS_LogAndTraceProtocol from Release R21-11|853| | |28|
|82|Log and Trace Protocol Specification, AUTOSAR_PRS_LogAndTraceProtocol|713| | |53|
|83|Main Requirements, AUTOSAR_RS_Main|706| | |14|
|84|Mapping mixed-criticality applications on multi-core architectures https://doi.org/10.7873/DATE.2014.111|885| | |38|
|85|Meta Model, AUTOSAR_MMOD_MetaModel|994| | |35|
|86|Methodology for Adaptive Platform, AUTOSAR_TR_AdaptiveMethodology|706| | |14|
|87|Methodology for Classic Platform, AUTOSAR_TR_Methodology|709| | |10|
|88|Middleware for Real-time and Embedded Systems, http://doi.acm.org/10.1145/508448.508472|717| | |27|
|89|MISRA C++:2008 Guidelines for the use of the C++ language in critical systems, The Motor Industry Software Reliability Association, 2008.|839| | |36|
|90|N3857: Improvements to std::future and Related APIs https://isocpp.org/files/papers/N3857.pdf|903| | |9|
|91|N4659: Working Draft, Standard for ProgrammingLanguage C++ http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/n4659.pdf|903| | |9|
|92|N4820: Working Draft, Standard for Programming Language C++ http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2019/n4820.pdf|903| | |9|
|93|New directions in cryptography https://ieeexplore.ieee.org/document/1055638|883| | |17|
|94|On the Expressiveness of Return-into-libc Attacks|881| | |15|
|95|OpenBSD-3.3 announcement, public release of WˆX, http://www.openbsd.org/33.html|881| | |15|
|96|Patterns, Frameworks, and Middleware: Their Synergistic Relationships, http://dl.acm.org/citation.cfm?id=776816.776917|717| | |27|
|97|Patterns, Frameworks, and Middleware: Their Synergistic Relationships, http://dl.acm.org/citation.cfm?id=776816.776917|846| | |23|
|98|PKCS #10: Certification Request Syntax Specification Version 1.7 https://tools.ietf.org/html/rfc2986|883| |2986|17|
|99|PKCS #12: Personal Information Exchange Syntax v1.1 https://tools.ietf.org/html/rfc7292|883| |7298|17|
|100|PKCS #5: Password-Based Cryptography Specification Version 2.0 https://rfc-editor.org/rfc/rfc2898.txt|883| |2898|17|
|101|PKCS #5: Password-Based Cryptography Specification Version 2.1 https://rfc-editor.org/rfc/rfc8018.txt|883| |8018|17|
|102|PKCS #7: Cryptographic Message Syntax Version 1.5 https://rfc-editor.org/rfc/rfc2315.txt|883| |2315|17|
|103|Public Key Cryptography for the Financial Services Industry Key Agreement and Key Stransport Using Elliptic Curve Cryptography https://webstore.ansi.org/preview-pages/ASCX9/preview_ANSI+X9.63-2011+(R2017).pdf|883| | |17|
|104|Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2 https://rfc-editor.org/rfc/rfc5208.txt|883| |5208|17|
|105|Recommendation for Key Derivation Using Pseudorandom Functions (Revised) https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-108.pdf|883| | |17|
|106|Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar3.pdf|883| | |17|
|107|Reference Model for Service Oriented Architecture 1.0, https://www.oasis-open.org/committees/download.php/19679/soa-rm-cs.pdf|713| | |53|
|108|Requirements of State Management, AUTOSAR_RS_StateManagement|720| | |22|
|109|Requirements on Automated Driving Interfaces, AUTOSAR_RS_AutomatedDrivingInterfaces functions–Logical interface|912| | |49|
|110|Requirements on AUTOSAR Features, AUTOSAR_RS_Features|889| | |25|
|111|Requirements on AUTOSAR Network Management, AUTOSAR_RS_NetworkManagement|898| | |46|
|112|Requirements on Communication Management, AUTOSAR_RS_CommunicationManagement|717| | |27|
|113|Requirements on Diagnostics, AUTOSAR_RS_Diagnostics|723| | |6|
|114|Requirements on E2E, AUTOSAR_RS_E2E|716| | |26|
|115|Requirements on Execution Management, AUTOSAR_RS_ExecutionManagement|718| | |31|
|116|Requirements on Health Monitoring, AUTOSAR_RS_HealthMonitoring|706| | |14|
|117|Requirements on Identity and Access Management, AUTOSAR_RS_IdentityAndAccessManagement|706| | |14|
|118|Requirements on Log and Trace, AUTOSAR_RS_LogAndTrace|853| | |28|
|119|Requirements on Methodology for Classic and Adaptive Platform, AUTOSAR_RS_Methodology|709| | |10|
|120|Requirements on Operating System Interface, AUTOSAR_RS_OperatingSystemInterface|719| | |33|
|121|Requirements on Persistency, AUTOSAR_RS_Persistency|853| | |24|
|122|Requirements on Platform Health Management, AUTOSAR_RS_PlatformHealthManagement|706| | |14|
|123|Requirements on Platform Health Management, AUTOSAR_RS_PlatformHealthManagement|851| | |30|
|124|Requirements on Security Management for Adaptive Platform, AUTOSAR_RS_SecurityManagement|883| | |17|
|125|Requirements on Time Synchronization, AUTOSAR_RS_TimeSync|880| | |55|
|126|Requirements on Timing Extensions, AUTOSAR_RS_TimingExtensions|968| | |52|
|127|Requirements on Update and Configuration Management, AUTOSAR_RS_UpdateAndConfigurationManagement|888| | |43|
|128|REST: Architectural Styles and the Design of Network-based Software Architectures|876| | |34|
|129|RFC 1951, DEFLATE Compressed Data Format Specification version 1.3 https://www.rfc-editor.org/rfc/rfc1951.txt|876| |1951|34|
|130|RFC 1952, GZIP file format specification version 4.3 https://www.rfc-editor.org/rfc/rfc1952.txt|876| |1952|34|
|131|RFC 2616, Hypertext Transfer Protocol – HTTP/1.1 https://www.rfc-editor.org/rfc/rfc2616.txt|876| |2616|34|
|132|RFC 3602 The AES-CBC Cipher Algorithm and Its Use with IPsec https://www.rfc-editor.org/rfc/rfc3602.txt|930| |3602|32|
|133|RFC 3986, Uniform Resource Identifier (URI): Generic Syntax https://www.rfc-editor.org/rfc/rfc3986.txt|876| |3986|34|
|134|RFC 4106 The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP) https://www.rfc-editor.org/rfc/rfc4106.txt|930| |4106|32|
|135|RFC 4122, A Universally Unique IDentifier (UUID) URN Namespace https://www.rfc-editor.org/rfc/rfc4122.txt|876| |4122|34|
|136|RFC 4301 Security Architecture for the Internet Protocol https://www.rfc-editor.org/rfc/rfc4301.txt|930| |4301|32|
|137|RFC 4302  IP Authentication Header  https://datatracker.ietf.org/doc/html/rfc4302|930| |4302|32|
|138|RFC 4303 IP Encapsulating Security Payload (ESP) https://datatracker.ietf.org/doc/html/rfc4303|930| |4303|32|
|139|RFC 4309, https://tools.ietf.org/html/RFC4309 Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)|930| |4309|32|
|140|RFC 4494  The AES-CMAC-96 Algorithm and Its Use with Ipsec https://datatracker.ietf.org/doc/html/rfc4494|930| |4494|32|
|141|RFC 4543  The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH https://datatracker.ietf.org/doc/html/rfc4543|930| |4543|32|
|142|RFC 4868 Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with Ipsec https://datatracker.ietf.org/doc/html/rfc4868|930| |4868|32|
|143|RFC 5903 Three-Way Handshake for IS-IS Point-to-Point Adjacencies https://datatracker.ietf.org/doc/html/rfc5303|930| |5903|32|
|144|RFC 6379 Suite B Cryptographic Suites for Ipsec https://datatracker.ietf.org/doc/html/rfc6379|930| |6379|32|
|145|RFC 7159, The JavaScript Object Notation (JSON) Data Interchange Format|876| |7159|34|
|146|RFC 7296 Internet Key Exchange Protocol Version 2 (IKEv2)  https://datatracker.ietf.org/doc/html/rfc7296|930| |7296|32|
|147|RFC 7427 Signature Authentication in the Internet Key Exchange Version 2 (IKEv2) https://datatracker.ietf.org/doc/html/rfc4427|930| |7427|32|
|148|RFC4304    Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI)  for Internet Security Association and Key Management Protocol (ISAKMP) https://datatracker.ietf.org/doc/html/rfc4304|930| |4304|32|
|149|Road vehicles – Diagnostic communication over Internet Protocol (DoIP) – Part 2: Network and transport layer requirements and services, http://www.iso.org|723| | |6|
|150|Road vehicles – Diagnostic communication over Internet Protocol (DoIP), http://www.iso.org|713| | |53|
|151|Road vehicles – Diagnostics on Controller Area Networks (CAN) – Part2: Network layer services|723| | |6|
|152|RPC over DDS, Version 1.0, https://www.omg.org/spec/DDS-RPC/1.0|713| | |53|
|153|S/MIME Version 2 Message Specification https://tools.ietf.org/html/rfc2311|883| |2311|17|
|154|Safety Requirements for AUTOSAR Adaptive Platform and AUTOSAR Classic Platform, AUTOSAR_RS_Safety|706| | |14|
|155|safety-related systems – Annex C, Overview of techniques and measures for achieving software safety integrity, International Electrotechnical Commission, 2010|839| | |36|
|156|Scott Meyers, Effective Modern C++, ISBN: 978-1-491-90399-5, O’Reilly, 2015.|839| | |36|
|157|Security Extract Template, AUTOSAR_TPS_SecurityExtractTemplate|713| | |53|
|158|Serialization and Unserialization, https://isocpp.org/wiki/faq/serialization|846| | |23|
|159|site holding a number of web pages for groups producing open standards, 2017 http://open-std.org, |839| | |36|
|160|Smashing The Stack For Fun And Profit, http://phrack.org/issues/49/14.html|881| | |15|
|161|Software Component Template, AUTOSAR_TPS_SoftwareComponentTemplate|709| | |10|
|162|Software Engineering Institute CERT C++ Coding Standard, Software Engineering Institute Division at Carnegie Mellon University, 2016.|839| | |36|
|163|Software Process Engineering Meta-Model Specification, http://www.omg.org/spec/SPEM/2.0/|709| | |10|
|164|SoK: Eternal War in Memory https://people.eecs.berkeley.edu/~dawnsong/papers/Oakland13-SoK-CR.pdf|881| | |15|
|165|SOME/IP Protocol Specification, AUTOSAR_PRS_SOMEIPProtocol|713| | |53|
|166|SOME/IP Service Discovery Protocol Specification, AUTOSAR_PRS_SOMEIPServiceDiscoveryProtocol|713| | |53|
|167|Specification of Abstract Platform, AUTOSAR_TPS_AbstractPlatformSpecification|709| | |10|
|168|Specification of Adaptive Platform Core|717| | |27|
|169|Specification of Communication Management, AUTOSAR_SWS_CommunicationManagement|706| | |14|
|170|Specification of Crypto Interface, AUTOSAR_SWS_CryptoInterface|885| | |38|
|171|Specification of Cryptography, AUTOSAR_SWS_Cryptography|713| | |53|
|172|Specification of Diagnostic Communication Manager, AUTOSAR_SWS_DiagnosticCommunicationManager|885| | |38|
|173|Specification of Diagnostic Log and Trace, AUTOSAR_SWS_DiagnosticLogAndTrace|885| | |38|
|174|Specification of Diagnostics, AUTOSAR_SWS_Diagnostics|713| | |53|
|175|Specification of ECU State Manager, AUTOSAR_SWS_ECUStateManager|885| | |38|
|176|Specification of Execution Management, AUTOSAR_SWS_ExecutionManagement|706| | |14|
|177|Specification of Health Monitoring, AUTOSAR_ASWS_HealthMonitoring|706| | |14|
|178|Specification of Identity and Access Management, AUTOSAR_SWS_IdentityAndAccessManagement|706| | |14|
|179|Specification of Language Binding for modeled AP data types, AUTOSAR_SWS_LanguageBindingForModeledAPdatatypes|717| | |27|
|180|Specification of Log and Trace, AUTOSAR_SWS_LogAndTrace|723| | |6|
|181|Specification of Manifest, AUTOSAR_TPS_ManifestSpecification|930| | |32|
|182|Specification of Network Management Interface, AUTOSAR_SWS_NetworkManagementInterface|885| | |38|
|183|Specification of Network Management, AUTOSAR_SWS_NetworkManagement|908| | |44|
|184|Specification of Operating System Interface, AUTOSAR_SWS_OperatingSystemInterface|885| | |38|
|185|Specification of Persistency, AUTOSAR_SWS_Persistency|713| | |53|
|186|Specification of Platform Health Management , AUTOSAR_SWS_PlatformHealthManagement|888| | |43|
|187|Specification of Platform Types for Adaptive Platform, AUTOSAR_SWS_AdaptivePlatformTypes|706| | |14|
|188|Specification of Platform Types, AUTOSAR_SWS_PlatformTypes|717| | |27|
|189|Specification of RTE Software, AUTOSAR_SWS_RTE|846| | |23|
|190|Specification of Secure Onboard Communication Protocol , AUTOSAR_PRS_SecOcProtocol|717| | |27|
|191|Specification of Secure Onboard Communication, AUTOSAR_SWS_SecureOnboardCommunication|713| | |53|
|192|Specification of Socket Adaptor, AUTOSAR_SWS_SocketAdaptor|717| | |27|
|193|Specification of State Management, AUTOSAR_SWS_StateManagement|721| | |21|
|194|Specification of SW-C End-to-End Communication Protection Library, AUTOSAR_SWS_E2ELibrary|713| | |53|
|195|Specification of Synchronized Time-Base Manager, AUTOSAR_SWS_SynchronizedTimeBaseManager|880| | |55|
|196|Specification of the AUTOSAR Network Management Protocol, AUTOSAR_PRS_NetworkManagementProtocol|898| | |46|
|197|Specification of Time Synchronization over Ethernet, AUTOSAR_SWS_TimeSyncOverEthernet|880| | |55|
|198|Specification of Time Synchronization, AUTOSAR_SWS_TimeSynchronization|713| | |53|
|199|Specification of Update and Configuration Management, AUTOSAR_SWS_UpdateAndConfigurationManagement|853| | |24|
|200|stack overflow http://stackoverflow.com, community of programmers, 2017|839| | |36|
|201|Standard for Information Technology–Portable Operating System Interface (POSIX(R)) Base Specifications, Issue 7 http://pubs.opengroup.org/onlinepubs/9699919799/|903| | |9|
|202|Standard Template Library, https://en.wikipedia.org/wiki/Standard_Template_Library|714| | |12|
|203|Standardization Template, AUTOSAR_TPS_StandardizationTemplate|889| | |25|
|204|System Template, AUTOSAR_TPS_SystemTemplate|709| | |10|
|205|The 4+1 View Model of Architecture https://www.cs.ubc.ca/~gregor/teaching/papers/4+1view-architecture.pdf|706| | |14|
|206|The application/pkcs10 Media Type https://tools.ietf.org/html/rfc5967|883| |5967|17|
|207|The Geometry of Innocent Flesh on the Bone: Return-into-libc without Function Calls (on the x86) (CRL) Profile https://rfc-editor.org/rfc/rfc5280.txt|881| | |15|
|208|The Memory Fragmentation Problem: Solved? https://doi.org/10.1145/286860.286864|983| | |40|
|209|The SPARC Architectural Manual, Version 8, http://sparc.org/wp-content/uploads/2014/01/v8.pdf.gz|881| | |15|
|210|The Transport Layer Security (TLS) Multiple Certificate Status Request Extension https://tools.ietf.org/html/rfc6961|883| |6961|17|
|211|The Transport Layer Security (TLS) Protocol Version 1.3 https://tools.ietf.org/html/rfc8446|883| |8446|17|
|212|Time Synchronization Protocol Specification, AUTOSAR_PRS_TimeSyncProtocol|880| | |55|
|213|TLSF: a new dynamic memory allocator for real-time systems https://doi.org/10.1109/EMRTS.2004.1311009|983| | |40|
|214|Transport Layer Security (TLS) Extensions: Extension Definitions https://tools.ietf.org/html/rfc6066|883| |6066|17|
|215|TRIVIUM Specifications http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.59.9030|883| | |17|
|216|Unified diagnostic services (UDS) - Part 2: Session layer services (Release 2013-03), http://www.iso.org|723| | |6|
|217|Unified diagnostic services (UDS) – Part 1: Application layer (Release 2020-02) http://www.iso.org|723| | |6|
|218|Unified diagnostic services (UDS) – Part 1: Specification and requirements (Release 2013-03) http://www.iso.org|723| | |6|
|219|Updated Security Considerations the MD5 Message-Digest and the HMAC-MD5 Algorithms, https://tools.ietf.org/html/rfc6151|883| |6151|17|
|220|Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS), 2002, https://rfc-editor.org/rfc/rfc3278.txt|883| |3278|17|
|221|Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS), 2010 https://rfc-editor.org/rfc/rfc5753.txt|883| |5753|17|
|222|Using Advanced Encryption Standard Counter Mode (AES-CTR) with the Internet, Key Exchange version 02 (IKEv2) Protocol https://rfc-editor.org/rfc/rfc5930.txt|883| |5930|17|
|223|UTF-16, an encoding of ISO 10646, http://www.ietf.org/rfc/rfc2781.txt|717| |2781|27|
|224|UTF-8, a transformation format of ISO 10646, http://www.ietf.org/rfc/rfc3629.txt|717| |3629|27|
|225|Utilization of Crypto Services, AUTOSAR_EXP_UtilizationOfCryptoServices|885| | |38|
|226|ValueOrError and ValueOrNone types http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0786r1.pdf|903| | |9|
|227|Virtual Functional Bus, AUTOSAR_EXP_VFB|885| | |38|
|228|X.501 : Information technology - Open Systems Interconnection - The Directory: Models https://www.itu.int/rec/T-REC-X.501|883| | |17|
|229|X.509 https://www.itu.int/rec/T-REC-X.509/en|883| | |17|
|230|X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP https://rfc-editor.org/rfc/rfc6960.txt|883| |6960|17|
|231|X.680 : Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation https://www.itu.int/rec/T-REC-X.680|883| | |17|
|232|X.682 : Information technology - Abstract Syntax Notation One (ASN.1): Constraint specification https://www.itu.int/rec/T-REC-X.682|883| | |17|
|233|X.683 : Information technology - Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications https://www.itu.int/rec/T-REC-X.683|883| | |17|
|234|X.690 : Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) https://www.itu.int/rec/T-REC-X.690|883| | |17|

RFCで文書名がないものは文書名を追記。
URLがないものを現在順次追記中。
DOCおよびQiitaは、一つだけ記載。