The Pouzin Society RINA Standards What needs to

The Pouzin Society RINA Standards – What needs to be Standardized, and How Steve Bunch John Day

Overview • • • The Pouzin Society Standards and Interoperability RINA Standardization – How? Profiles and Tools Standards Body: Pouzin Society (PSOC) Operation of PSOC Summary 22 May 2018 RINA Standards 2

RINA Standards and Interoperability The Pouzin Society • Why do we want standards? Most DIFs are private – Interoperability, within a DIF and for common cases – Encourages wider availability and adoption • Avoids “Proprietary”, an anathema to many users – Share Experience and Intellectual Property (IPR) – Compatible tools and implementations (Wireshark…) – Stop Progress (wait, what? ) • Bob Metcalf on Ethernet at an early IEEE 802 meeting: “if we don’t stop improving this we’ll never be able to make any money” • Standards Problems that we all know about – Stop Progress (in a bad way) – Some participants will try to protect incumbents 22 May 2018 RINA Standards 3

RINA Standardization – How? The Pouzin Society • RINA is not like most familiar protocols – Not limited to defining everything at the bit/byte level with minutely documented policies and behaviors that can’t be changed – Standard Mechanisms are separated from optional Policies, and policies encapsulate the variation needed to optimize RINA implementations for their end purpose • “Interoperability” is within a DIF, among its members • To achieve interoperability, members of a particular DIF must – Correctly implement the Base RINA Mechanisms – Use the same set of Policies • But RINA doesn’t define a fixed set of Policies! – And not all DIFs have to use the same ones – So how do we “standardize” RINA? 22 May 2018 RINA Standards 4

Profiles and Tools The Pouzin Society • Base RINA specifications define mechanisms + slots for policies to be plugged into – CACEP, CDAP, EFCP, DIF, … – The base specs alone do NOT provide interoperability! • E. g. , encodings of protocol messages are defined by policy – When they use the same set of policies, implementations of each protocol are interoperable for that protocol • Profiles specify a particular set of policies – We define a complete set for use with each base specification – We define a complete set of those sets to define a DIF Profile • To ease building DIFs, tools can be used to select the set of policies and output a DIF Profile configuration for DIF members 22 May 2018 RINA Standards 5

(Simplified) Concept of the Policy “Store” EFCP CACEP CDAP BASE The Pouzin Society Policy Plugin Points Available Policies 22 May 2018 RINA Standards 6

Base and Profiles Relationship The Pouzin Society EFCP BASE CACEP BASE CDAP BASE Policy Plugin Points Profile Selection 22 May 2018 RINA Standards 7

Base and Profiles Relationship The Pouzin Society 22 May 2018 EFCP CACEP CDAP BASE RINA Standards Complete Protocol Definitions 8

DIF Profile The Pouzin Society • A “generic” DIF Profile can be defined – Lacking only authorization and specific App/Node configuration to operate, otherwise completely defined – Can be built into and provided with Operating Systems, or as a package – Optimized DIFs may need a new profile, or may be able to use an existing one with policy changes – We expect to need very few generic DIF Profiles • To go live with a DIF using a generic DIF Profile – Just add the authentication/configuration information (users, nodes, links with Qo. S, …) appropriate for the specific DIF 22 May 2018 RINA Standards 9

Base and Profiles Relationship The Pouzin Society EFCP BASE CDAP CACEP BASE Complete Protocol Definitions DIF PROFILE 22 May 2018 RINA Standards 10

Standardized DIF Profiles The Pouzin Society • We need at least a few widely-available generic DIF Profiles – e. g. , a DIF dynamically created by a DIF Allocator to connect Applications that don’t share a DIF – One to build in to widely-available OS distros • Tools will be used to configure Profiles, with the initial defaults corresponding to a known generic DIF Profile • We need a Standards Body to finalize a useful and minimal common default Profile set and facilitate creation of new ones when necessary – And we need standards for all the other good reasons previously cited – And we need to protect against the problems cited 22 May 2018 RINA Standards 11

RINA Standards – The Pouzin Society (PSOC) • • • The Pouzin Society Marketing and Education Base Standards Certification of Implementations The (Policy+) Store Intellectual Property • NB: Pouzin Society is evolving, we will use the web site to keep people informed 22 May 2018 RINA Standards 12

PSOC Marketing and Education The Pouzin Society • Web site: pouzinsociety. org • Outreach – Workshops and conferences – Publicity and outreach • Repositories – Official: Standards, announcements, etc. – Contributed (e. g. , tools, papers, wiki) 22 May 2018 RINA Standards 13

Creating RINA Standards The Pouzin Society • PSOC will be the forum for the open process – Base Specs (these are intended to change little) – Policy Specs for policies used in compliant DIF Profiles – Compliant DIF Profile Specs – Compliance Process/Artifacts (e. g. , interop tests, acceptance criteria, workshops, connectathons, …) • PSOC members will define what it means to be a “Compliant Implementation” of a DIF Profile – Mainly, it’s interoperability – but probably a bit more – Other conformance certifications (e. g. , policies) TBD 22 May 2018 RINA Standards 14

Compliant Implementations The Pouzin Society • Compliance is about interoperability, and the specs help drive that • Multiple ways have been used to confirm “Compliance” – “Connectathons”, “Unplugfests”, etc. , where implementers gather to test against each other (many cellular standards, Bluetooth, etc. ) (NB: under NDA, often pre-release products) – Compatibility with or derivation from Reference implementations (early UNIX, Android, many protocols) – Test suites (POSIX, X/Open, protocol testing frameworks) – Static and Dynamic code analysis tools, verification tools • Creating test suites and reference implementations is typically done by members (perhaps their own tests), or via their membership fees (via contractors or paying a member) • Bluetooth SIG and USB SIG have been poster children of ways that work (and some things that don’t work), we can learn from them 22 May 2018 RINA Standards 15

PSOC (Policy+) Store The Pouzin Society • Policies, Tools, Services, … for purchase, or referral to vendors • There are no Product Differentiators in the Base Standards (other than RINA itself) • Product differentiation is in implementations and in Policies – And support, maintenance, and other add-ons • Competition is in Policies, and the Store can be used to sell them to add value to DIFs – E. g. , optimized routing algorithms, authentication algorithms, encryption algorithms, DIF-optimized protocol encoding • Vast majority of DIFs are private, no requirement for agreements across those, other than for convenience – Can be useful: software reuse, debugging tools, support 22 May 2018 RINA Standards 16

Proposed PSOC IPR Rules (The Part about “Sharing IPR”) The Pouzin Society • Compliant Implementations get to use PSOC-owned Trademarks, and rights to use PSOC-copyrighted documents and code – It is not anticipated that PSOC would own any Essential IPR, that is, IPR needed to create a Compliant Implementation • Member IPR owners, as a condition of membership, agree to grant Compliant Implementations a right to use their “Essential IPR” needed by other members in any Compliant Implementation (many industry SIGs use this model, lawyers have seen it before) – Usage by members is fee-free for PSOC-Certified Compliant Implementations (e. g. , via non-assert as most industry SIGs use) – All other owner rights over Essential IPR are unaffected • Policy implementations using IPR that is not Essential IPR to RINA can be made available by vendors in the “PSOC Store”, they do not have to be made available for free 22 May 2018 RINA Standards 17

Summary The Pouzin Society • RINA, despite its generality, allows standardization to ensure interoperability of implementations – Profiles are used to define a specific set of policies to use for compliance testing and for interoperability • Pouzin Society (PSOC) will be the SDO for RINA • PSOC will manage the certification of Compliant Implementations and use of Trademarks/Copyrights – These will be royalty-free to members and users • Added-value Policies and other RINA-related products such as tools can be sold through the PSOC Store • PSOC will go live as the RINA SDO at some point – announcement on the website: pouzinsociety. org • Questions and Discussion 22 May 2018 RINA Standards 18