iana well known uri registryiana well known uri registry

201-255: Reserved for vendor private use. expert. A Registry for Well-Known Tokens This document creates the '"about" URI Tokens' registry. 200-249: Intended for Abstract and Resource Model Extension Messages. Registration Template; 7.1.2. You switched accounts on another tab or window. Specification Required (Expert: Ari Kernen), Expert Review (Expert: Dave Thaler (primary), Dan Romascanu (secondary)), Specification Required (Expert: Dave Thaler (primary), Dan Romascanu (secondary)), Expert Review (Expert: Uma Chunduri, Jeff Tantsura), Expert Review (Expert: Les Ginsberg, Chris Hopps), Specification Required or IESG Approval (Expert: Pascal Thubert, Mohit Sethi). References; 8.1. are coordinated with the expert. A set of conventions by which a Dublin Core metadata description set can be can be represented within an (X)HTML Web page using (X)HTML elements and attributes. RFC 5785: Defining Well-Known Uniform Resource Identifiers (URIs) provisional registration date field update: First Come First Served. Search IETF mail list archives. Introduction [ RFC5785] defines a path prefix, "/.well-known", that can be used by well-known URIs. delegated to the COSE Key Type Parameters registry. Well-known URIs are registered on the advice of one or more Designated Experts (appointed by the IESG or their delegate), with a Specification Required (using terminology from ). (Expert: Carsten Bormann, Christian Amsss). For the purpose of providing services to unknown callers, a service contact . DCCP: Eddie Kohler and Yoshifumi Nishida), First Come First Served with a permanent, stable, and publically accessible document, Specification Required (Expert: Flemming Andreasen), Specification Required (Expert: Christer Holmberg), Specification Required (Expert: Stephan Wenger), Specification Required (Expert: Bo Burman), REGISTRY OBSOLETED - No further registrations accepted, Specification Required (Expert: Magnus Westerlund), Specification Required (Expert: Adam Roach). "; intended for private use: First Come First Served. Integer values in the range -65536 to -1: used for key parameters specific to a single algorithm "): First Come First Served. 1000-2999: Standards Action, Specification Required or IESG Review. 194-199: Specification Required or Expert Review. "spice") and a file extension of ".json", resulting in a full path Modifications do not require IANA considerations This section contains considerations for IANA. Integer values between 0 and 255: Standards Action With Expert Review. It also contains an IANA registry for URI suffixes to be used with this path prefix for forming well-known URIs. Specification Required (Expert: Gorry Fairhurst), IESG Approval with Specification Required, Specification Required (Expert: Vijay Gurbani), Specification Required (Expert: Mark Nottingham), Specification Required (Expert: Dale Worley), Expert Review and RFC Required (Expert: Primary: Simon Perreault; Backups: Cyrus Daboo, Peter Saint-Andre). 0-255, 512-65535: Specification Required. Internet Assigned Numbers Authority Well-Known URIs Created 2010-01-20 Last Updated 2023-05-31 Available Formats [IMG] XML [IMG] HTML [IMG] Plain text Registry included below Well-Known URIs Well-Known URIs Registration Procedure(s) Specification Required Expert(s) Mark Nottingham Reference [RFC8615] Note New link relations, along with changes to existing relations, can be requested using . protocol-registries/well-known-uris: Registry for Well Known URIs - GitHub Values are assigned relative to the respective Client-type. IANA Considerations The "Well-Known URIs" registry should be updated with the following additional values (using the template from [RFC8615]): * URI suffix: probing.txt * Change controller: IETF * Specification document(s): this document * Status: permanent 9. RFCs must be reviewed by an expert. IANA does not assign. The reason that this resource is located at a well-known URI is that Issuers are defined by an origin name in TokenChallenge structures; see Section 2.1 of [AUTHSCHEME]. 3-30: IETF Review (IETF RFC publication). References 9.1. This process is described in Section 3. of RFC 5646. Guidance for RFC Authors - Internet Assigned Numbers Authority The "host-meta.json" documents obtained from the same host using the HTTP and If your reference is from an Open Source project, community or commerical group, a request can be made once your document becomes public, but anticipatory requests are discouraged, and may be refused or delayed. 128-240: Some recognized assignments below, others Reserved. This page seems problematic; it essentially duplicates the IANA well-known URI registry, thereby both introducing opportunities for errors/mismatches, and subsuming the function of the public registry. (Expert: Marc Petit-Huguenin (primary), Cullen Jennings (secondary)), Specification Required (Expert: Marc Petit-Huguenin (primary), Cullen Jennings (secondary)), Expert Review (Expert: Keyur Patel (Primary), John G. Scudder (Secondary)), RFC Required (Standards Track or Experimental), Standards Action or Specification Required (Expert: Unassigned), Specification Required (Expert: David Waltermire, Stephen Banghart). Are you sure you want to create this branch? Service Name and Transport Protocol Port Number Registry Curate this topic . Under vendor namespace: First Come First Served. Re: [OPSEC] [IANA #1274499] expert review for draft-ietf-opsec-probe-attribution (well-known-uris) https://developers.google.com/amp/cache/update-cache, https://github.com/Vroo/well-known-uri-appspecific/blob/main/well-known-uri-for-application-specific-purposes.txt, http://www.bacnet.org/Addenda/Add-135-2012am-ppr3-draft-17_chair_approved.pdf, https://github.com/google/digitalassetlinks/blob/master/well-known/specification.md, https://github.com/google/digitalassetlinks/blob/master/well-known/details.md, https://www.iana.org/assignments/brski-parameters/brski-parameters.xhtml#brski-well-known-uris, https://w3c.github.io/webappsec-change-password-url/#the-change-password-well-known-uri, Common Security Advisory Framework Version 2.0, OASIS Standard, https://www.w3.org/TR/tabular-data-model/#default-locations-and-site-wide-location-configuration, https://identity.foundation/.well-known/resources/did-configuration, http://www.w3.org/TR/tracking-dnt/#status-resource, https://globalprivacycontrol.github.io/gpc-spec/, https://github.com/Automattic/hosting-provider, status-change-http-experiments-to-historic, https://spec.matrix.org/latest/client-server-api/#well-known-uri, https://spec.matrix.org/latest/server-server-api/#getwell-knownmatrixserver, OpenID_Foundation_Artifact_Binding_Working_Group, http://openid.net/specs/openid-connect-discovery-1_0.html, https://docs.oasis-open-projects.org/oslc-op/core/v3.0/ps01/oslc-core.html, Section 3.2.2.4.6 of version 1.3.8 of the CA/Browser Forums Baseline Requirements Certificate Policy for the Issuance and Management of Publicly-Trusted Certificates (Baseline Requirements), https://cabforum.org/baseline-requirements-documents/, http://www.openarchives.org/rs/resourcesync, https://www.threadgroup.org/support#specifications, The "tor-relay" Well-Known Resource Identifier, https://buettner.github.io/private-prefetch-proxy/traffic-advice.html, https://journallist.net/reference-document-for-trust-txt-specifications, https://www.w3.org/TR/wot-discovery/#introduction-well-known, mailto:d6035904-6d06-4ef2-861b-81090738b440&email.cynthia.re, [OpenID_Foundation_Artifact_Binding_Working_Group], http://www.w3.org/2011/tracking-protection/. Expert Review (Expert: Carlos Pignataro (primary), Ignacio Goyret (secondary)), (Expert: Carlos Pignataro (primary), Ignacio Goyret (secondary)), Specification Required (Expert: Carlos Pignataro (primary), Ignacio Goyret (secondary)), Expert Review (Expert: John Bradley, Joni Brennan, Leif Johansson, Lucy Lynch). Initial Registry Contents 7.2. Well-Known URI Registry; 7.3.1. Integer values 256 to 65535: Specification Required. 250-255: Reserved for vendor private use. OpenID RISC Profile of IETF Security Events 1.0 Specification Required (Expert: Andy Newton, Scott Hollenbeck), Expert Review (Expert: Andy Newton, Scott Hollenbeck), Specification Required (Expert: Chuck Lever (primary), Tom Talpey (secondary)), Expert Review (Expert: Tristan Richardson), Expert Review (Expert: Tristan Richardson, John Levine), First Come First Served or Standards Action. Protocol parameter registries represent the authoritative record of many of the codes and numbers contained in a variety of Internet protocols. (Expert: Donald Eastlake (primary), Sue Hares (secondary)), RFC Required (single value) or IETF Review (single or multiple values), Expert Review (Expert: Yoav Nir, Rich Salz, Nick Sullivan), (Expert: Yoav Nir, Rich Salz, Nick Sullivan), Specification Required (Expert: Yoav Nir, Rich Salz, Nick Sullivan). Integer values less than -65536: Private Use. Updated Registration Instructions; 7.3. Specification Required (Expert: Andreas Huelsing, Stefan-Lukas Gazdag), (Expert: Robert Moskowitz, Jeff Ahrenholz), Specification Required (Expert: Christopher Wood, Richard Barnes), Specification Required (Expert: Rifaat Shekh-Yusef, Yutaka Oiwa), Expert Review (Expert: Rifaat Shekh-Yusef, Yutaka Oiwa), RFC Required or Specification Required (Expert: James Manger), Specification Required for Permanent registrations, Well-Known URI Registry. name starts wth "vnd. A profile URI to request or signal compacted JSON-LD . This is one of the available formats of the Interface Types (ifType) and Tunnel Types (tunnelType) registries. This registry requires a stable reference for a specification document. Re: [OPSEC] [IANA #1274499] expert review for draft-ietf-opsec-probe No namespace specified: Expert Review and RFC Required. . 2023-05-31 Available Formats XML HTML Plain text Registry included below Well-Known URIs Well-Known URIs Registration Procedure(s) Specification Required Expert(s) Mark Nottingham Reference [RFC8615] Note New link relations, along with changes to existing relations, can be requested 0x20000000-0x3EFFFFFF: First Come First Served. values 31 * N + 27 (for integer values of N): Reserved. 1-127: Standards Action or non standards-track It also contains an IANA registry for URI suffixes to be used with this path prefix for forming well-known URIs. Expert Review (Expert: Andy Bierman (primary), Jrgen Schnwlder (secondary)), Expert Review (Expert: Ira McDonald, Michael Sweet). Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. e- Reserved for Experiments, First Come First Served Uniform Resource Identifier (URI) Schemes - Internet Assigned Numbers A well-known URI for publishing ECHConfigList values. 8388608-16777213: First Come First Served with specification. The Well-Known URI Registry This specification updates the registration procedures for the "Well- Known URI" registry, first defined in ; see Section 3.1. Expert Review (Expert: Jamal Hadi Salim, Joel Halpern). The registry entries consist of three fields: Token, Description, and Reference. IANA also oversees the approval process for new proposed top-level domains for ICANN. For Private Enterprise Number (PEN) registration (prefix 1.3.6.1.4.1), see . requests for more than one value: Expert Review. Updated Registration Instructions . registry iana iana-registry well-known-uri Updated May 4, 2021; protocol-registries / link-relations Star 24. 0-8191: Standards Action or non standards-track www.iana.org/assignments/well-known-uris/. In [ RFC5785 ], this mechanism is specifically defined for the "http" and "https" URI schemes (now defined in [ RFC7230 ]). Specification Required (Expert: Donald Eastlake, Alexey Melnikov), Specification Required (Expert: Christian Hopps, Lou Berger, Dean Bogdanovic). (Expert: Carsten Bormann, Jaime Jimnez, Christian Amsss), (Expert: Carsten Bormann, Jaime Jimenez, Christian Amsss), Expert Review (Expert: Francesca Palombini, Gran Selander, Christian Amsss), Expert Review (Expert: Carsten Bormann, Jaime Jimnez, Christian Amsss), Specification Required (Expert: Thomas Fossati, Carsten Bormann), Specification Required (Expert: Kevin Ma, Ben Niven-Jenkins), Specification Required (Expert: Kevin Ma), Specification Required (Expert: Kevin Ma, Nir Sopher), Specification Required (Expert: Phil Sorber), Standards Track or IESG-Approved Experimental RFC, Specification Required (Expert: Mike West), Specification Required (Expert: Dave Oran, Hitoshi Asaeda), Expert Review (Expert: Sri Gundavelli, Li Xue), Specification Required (Expert: Sri Gundavelli, Li Xue), Specification Required (Expert: Roni Even, Simon Pietro Romano), Expert Review (Expert: Roni Even, Simon Pietro Romano), Expert Review and RFC Required (Expert: Tero Kivinen). 16384 and higher Private Use (Shall start with x-) (Expert: Rolf Sonneveld, Andrew Findlay), Specification Required (Expert: Rolf Sonneveld, Andrew Findlay), x- Private Use AODV Message Types (for messages sent to port 654), Applicable Exchange Core (APEX) Endpoint Applications, Internet Draft draft-ietf-alto-performance-metrics-28, ACE Authorization Server Request Creation Hints, OAuth Token Introspection Response CBOR Mappings, Internet Draft draft-ietf-acme-authority-token-09, ACME Directory Metadata Auto-Renewal Fields, Auto-Submitted header field optional parameters, http://www.icann.org/en/resources/policy/global-addressing, BMP Initiation and Peer Up Information TLVs, BMP Peer Flags for Loc-RIB Instance Peer Type 3, BMP Peer Flags for Peer Types 0 through 2, BGP Graceful Restart Flags for Address Family, BGP Non-Transitive Extended Community Types, Generic Transitive Extended Community Part 2 Sub-Types, Generic Transitive Extended Community Part 3 Sub-Types, Generic Transitive Extended Community Sub-Types, Layer2 Info Extended Community Control Flags Bit Vector, Non-Transitive Four-Octet AS-Specific Extended Community Sub-Types, Non-Transitive IPv4-Address-Specific Extended Community Sub-Types, Non-Transitive IPv6-Address-Specific Extended Community Types, Non-Transitive Opaque Extended Community Sub-Types, Non-Transitive Two-Octet AS-Specific Extended Community Sub-Types, P-Multicast Service Interface (PMSI) Tunnel Attribute Flags, P-Multicast Service Interface Tunnel (PMSI Tunnel) Tunnel Types, Transitive Four-Octet AS-Specific Extended Community Sub-Types, Transitive IPv4-Address-Specific Extended Community Sub-Types, Transitive IPv6-Address-Specific Extended Community Types, Transitive Opaque Extended Community Sub-Types, Transitive Two-Octet AS-Specific Extended Community Sub-Types, BGP Tunnel Encapsulation Attribute Sub-TLVs, BGP Tunnel Encapsulation Attribute Tunnel Types, Flags Field of NVGRE Encapsulation Sub-TLVs, Flags Field of VXLAN Encapsulation Sub-TLVs, Internet Draft draft-ietf-idr-rfc7752bis-16, BGP-LS Well-Known Instance-IDs (OBSOLETE), Internet Draft draft-ietf-idr-bgpls-srv6-ext-14, BPSec BIB-HMAC-SHA2 Integrity Scope Flags, Bundle Protocol TCP Convergence-Layer Message Types, Bundle Protocol TCP Convergence-Layer REFUSE_BUNDLE Reason Codes, Bundle Protocol TCP Convergence-Layer SHUTDOWN Reason Codes, Bundle Protocol TCP Convergence-Layer Version 4 Message Types, Bundle Protocol TCP Convergence-Layer Version 4 MSG_REJECT Reason Codes, Bundle Protocol TCP Convergence-Layer Version 4 SESS_TERM Reason Codes, Bundle Protocol TCP Convergence-Layer Version 4 Session Extension Types, Bundle Protocol TCP Convergence-Layer Version 4 Transfer Extension Types, Bundle Protocol TCP Convergence-Layer Version 4 XFER_REFUSE Reason Codes, Bundle Protocol TCP Convergence-Layer Version Numbers, Ciphersuite Parameters and Results Type Registry, Experimental Mobility Protocol Subtype Registry, Layer 2 Access Technology Identifier Registry, Internet Draft draft-ietf-lamps-cmp-updates-23, Cisco SLA Protocol Address Family Registry, Cisco SLA Protocol Authenticator Modes Registry, Cisco SLA Protocol Measurement-Type Registry, Cisco SLA Protocol Version Number Registry, COPS-PR Object S-Num, S-Types, and Error-Codes, M-Types, Reason Sub-Codes, and Error Sub-codes, R-Types, Reason-Codes, Report-Types, Decision Object Command-Codes/Flags, and Error-Codes, Receiver Proxy Control Policy Element (P-Type 0x07) Control-Value field, Interface Description (if=) Link Target Attribute Values, Resource Type (rt=) Link Target Attribute Values, Context Transfer Protocol Authorization Token Calculation Algorithms, Cryptographic Suites for IKEv1, IKEv2, and IPsec, Data Link Switching Protocol Sender Capability Codes, Differentiated Services Field Codepoints (DSCP), DOTS Signal Channel Conflict Status Codes, Internet Draft draft-ietf-dnsop-dns-catalog-zones-09, Internet Draft draft-ietf-dnsop-svcb-https-12, Underscored and Globally Scoped DNS Node Names, DNS KEY Record Diffie-Hellman Prime Lengths, DNS KEY Record Diffie-Hellman Well-Known Prime/Generator Pairs, _domainkey DNS TXT Record Tag Specifications, Authorized Third-Party Signature (ATPS) Tag Registry, Authentication Suboption (value 8) - Algorithm identifier values, Authentication Suboption (value 8) - Protocol identifier values, Authentication Suboption (value 8) - Replay Detection Method (RDM) identifier values, CableLabs Client Configuration Option Ticket Control Mask Bit Definitions, DHCP Cablelabs Client Configuration Option Type 122 Sub-Option Codes, DHCP Options Permitted in the RADIUS DHCPv4-Options Attribute, Internet Draft draft-ietf-opsawg-add-encrypted-dns-12, IEEE 802.21 Service Type (MoS DHCPv4 Address and FQDN Sub-Options), NetWare/IP Option Type 63 Sub-Option Codes, RADIUS Attributes Permitted in RADIUS Attributes Sub-option, DHCPv6 Options Permitted in the RADIUS DHCPv6-Options Attribute, IEEE 802.21 Service Type (MoS DHCPv6 Address and FQDN Sub-Options), Option Codes Permitted in the S46 Priority Option, Options Permitted in the Relay-Supplied Options Option, RADIUS Attributes Permitted in DHCPv6 RADIUS Option, Internet Draft draft-ietf-homenet-naming-architecture-dhc-options-24, Queue Parameter Sub-Data Item Type Values, Dynamic Source Routing (DSR) Protocol Options, Dynamic Source Routing (DSR) Protocol Route Error Types, User Specific Root Keys (USRK) Key Labels, Attribute Types (Non-Skippable Attributes 0-127), Attribute Types (Skippable Attributes 128-255), EAP-AKA' AT_KDF Key Derivation Function Values, EAP-FAST (value 43) Error-TLV (value 5) Error-Codes, EAP-FAST (value 43) Request-Action TLV (value 19) Action Codes, EAP-FAST Server-Trusted-Root Credential Format Types, TEAP Identity-Type TLV (value 2) Registry, TEAP PAC TLV (value 11) PAC Attribute Type Codes, TEAP PAC TLV (value 11) PAC-Type Type Codes, TEAP Request-Action TLV (value 8) Registry, TEAP Trusted-Server-Root TLV (value 17) Credential-Format Codes, EAP-EKE Keyed Message Digest (MAC) Registry, Extensions for the Extensible Provisioning Protocol (EPP), Logical Functional Block (LFB) Class Names and Class Identifiers, NSIS Signaling Layer Protocol (NSLP) Identifiers, Ethernet Sender TSpec TLVs/Ethernet Flowspec TLVs, Generalized SCSI (Switching Capability Specific Information) TLV Types, Geolocation Policy Location Profile Names, PIDF-LO Civic Address Considerations Registry, XML Namespaces for 'provided-by' elements for use with PIDF-LO objects, Global Navigation Satellite System (GNSS) Types, Types for Subfields of WSON Resource Block Information Registry, HTTP Mutual Authentication Host Validation Methods, Hash Algorithms for HTTP Digest Authentication, Hypertext Transfer Protocol (HTTP) Field Name Registry, Internet Draft draft-ietf-httpapi-rfc7807bis-07, https://www.iana.org/assignments/power-state-sets, IANA Link Layer Discovery Protocol (LLDP) TLV Subtypes, Internet Draft draft-ietf-ippm-ioam-conf-state-10, Structured Cybersecurity Information (SCI) Specifications, Instant Messaging SRV Protocol Label Registry, Internet Draft draft-ietf-lsr-rfc8919bis-04, Path Computation Element (PCE) Capability Flags, PCE Discovery (PCED) Sub-TLV Type Indicators, Internet - Xerox Network System (XNS) Protocol Mappings, ICMP Extension Object Classes and Class Sub-types, Address Registration Option Status Values, Certificate option (Type 16) Cert Type field, IPv6 Neighbor Discovery Prefix Information Option Flags, Option-Code for Handover Assist Information Option (Type 29), Option-Code for Mobile Node Identifier Option (Type 30), Trust Anchor option (Type 15) Name Type field, Additional Exchanges Defined-- XCHG values, Encryption Algorithm Class Values (Value 1), IKEv2 Configuration Payload Attribute Types, IKEv2 Notification IPCOMP Transform IDs (Value 16387), IKEv2 Notify Message Types - Status Types, IKEv2 Post-quantum Preshared Key ID Types, IMAP URLAUTH Access Identifiers and Prefixes, IMAP URLAUTH Authorization Mechanism Registry, Allocations made from the Current Recovered IPv4 Pool, IANA IPv4 Special-Purpose Address Registry, IPv6 Anycast Subnet-Router Anycast Address, IANA IPv6 Special-Purpose Address Registry, Destination Options and Hop-by-Hop Options, Internet Protocol Version 6 Address Space, iSCSI Task Management Function Response Codes, AD-HOC Block I (224.0.2.0 - 224.0.255.255), AD-HOC Block II (224.3.0.0-224.4.255.255 (224.3/16, 224.4/16)), AD-HOC Block III (233.252.0.0-233.255.255.255 (233.252/14)), DIS Transient Groups 224.252.0.0-224.255.255.255 (224.252/14)), Internetwork Control Block (224.0.1.0 - 224.0.1.255 (224.0.1/24)), Local Network Control Block (224.0.0.0 - 224.0.0.255 (224.0.0/24)), Relative Addresses used with Scoped Multicast Addresses, RESERVED (224.1.0.0-224.1.255.255 (224.1/16)), RESERVED (224.5.0.0-224.251.255.255 (251 /16s)), RESERVED (225.0.0.0-231.255.255.255 (7 /8s)), SDP/SAP Block (224.2.0.0-224.2.255.255 (224.2/16)), Source-Specific Multicast Block (232.0.0.0-232.255.255.255 (232/8)), Unicast-Prefix-based IPv4 Multicast Addresses, Unicast-based (Including SSM) Multicast Group IDs, https://www.iana.org/assignments/perm-mcast-groupids, Constrained Join Protocol (CoJP) Key Usage, Constrained Join Protocol (CoJP) Parameters, Constrained Join Protocol (CoJP) Unsupported Configuration Codes, IS-IS Application Identifiers for Generic Information TLV, IS-IS Bit Values for Prefix Attribute Flags Sub-TLV, IS-IS Group Address Type Codes for GADDR-TLV, IS-IS Sub-Sub-TLV Codepoints for Application-Specific Link Attributes, IS-IS Sub-Sub-TLVs for Flexible Algorithm Definition Sub-TLV, IS-IS Sub-Sub-TLVs for Flood Reflection Discovery Sub-TLV, IS-IS Sub-Sub-TLVs for SRv6 Capabilities Sub-TLV, IS-IS Sub-TLVs for Application-Specific SRLG TLV, IS-IS Sub-TLVs for IS-IS Router CAPABILITY TLV, IS-IS Sub-TLVs for Segment Identifier/Label Binding TLVs, IS-IS Sub-TLVs for TLVs Advertising Neighbor Information, IS-IS Sub-TLVs for TLVs Advertising Prefix Reachability, JSON Web Encryption Compression Algorithms, JSON Web Signature and Encryption Algorithms, JSON Web Signature and Encryption Header Parameters, PASSporT Resource Priority Header (rph) Types, Personal Assertion Token (PASSporT) Extensions, Kerberos V GSS-API Mechanism Extension Types, Kerberos V GSS-API Token Type Identifiers, Forwarding Equivalence Class (FEC) Type Name Space, LDP MP Opaque Value Element extended type, Directory of language tag applications - OBSOLETE, Language Subtag Registry - Registration Templates, ATM Alarm Status AVP (Attribute Type 88) Values, Message Type AVP (Attribute Type 0) Values, PPP Disconnect Cause Code (Attribute Type 46) Values, Proxy Authen Type AVP (Attribute Type 29) Values, Result Code AVP (Attribute Type 1) Values, Service Category AVP (Attribute Type 42) Flag Field, VCCV Capability AVP (Attribute Type 96) Values, Internet Directory Numbers (iso.org.dod.internet.directory [1.3.6.1.1. RFC 6694: The "about" URI Scheme - RFC Editor RFC 8615: Well-Known Uniform Resource Identifiers (URIs) A tag already exists with the provided branch name. SCTP: Michael Tuexen name doesn't start with "vnd. (Expert: Klaus Hartke (primary), Carsten Bormann (secondary), Jaime Jimenez (secondary), Alexander Pelov (secondary)), (Expert: Klaus Hartke (primary), Alexander Pelov (secondary)), Expert Review (Expert: Thomas Fossati, Carsten Bormann). 16384-32767: Private or Experimental Use. RFC or peer-reviewed permanent and readily available reference. Key length of one: Specification Required. documentation of the use being registered as specified in