Skip to main content

References from draft-ietf-ace-key-groupcomm

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
draft-ietf-core-coap-pubsub A publish-subscribe architecture for the Constrained Application Protocol (CoAP)
References Referenced by
informatively references
draft-ietf-core-groupcomm-bis Group Communication for the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard informatively references
draft-ietf-core-oscore-groupcomm Group Object Security for Constrained RESTful Environments (Group OSCORE)
References Referenced by
Proposed Standard informatively references
draft-ietf-cose-cbor-encoded-cert CBOR Encoded X.509 Certificates (C509 Certificates)
References Referenced by
informatively references
draft-tiloca-core-oscore-discovery Discovery of OSCORE Groups with the CoRE Resource Directory
References Referenced by
informatively references
RFC 2093 Group Key Management Protocol (GKMP) Specification
References Referenced by
Experimental informatively references
RFC 2094 Group Key Management Protocol (GKMP) Architecture
References Referenced by
Experimental informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2627 Key Management for Multicast: Issues and Architectures
References Referenced by
Informational informatively references
RFC 3629 UTF-8, a transformation format of ISO 10646
References Referenced by
Internet Standard normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard informatively references
RFC 5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
References Referenced by
Proposed Standard informatively references
RFC 6690 Constrained RESTful Environments (CoRE) Link Format
References Referenced by
Proposed Standard normatively references
RFC 6749 The OAuth 2.0 Authorization Framework
References Referenced by
Proposed Standard normatively references
RFC 6838 Media Type Specifications and Registration Procedures
References Referenced by
Best Current Practice normatively references
RFC 7252 The Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7519 JSON Web Token (JWT)
References Referenced by
Proposed Standard informatively references
RFC 7641 Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard informatively references
RFC 7959 Block-Wise Transfers in the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard informatively references
RFC 7967 Constrained Application Protocol (CoAP) Option for No Server Response
References Referenced by
Informational normatively references Downref
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard informatively references
RFC 8392 CBOR Web Token (CWT)
References Referenced by
Proposed Standard informatively references
RFC 8610 Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
References Referenced by
Proposed Standard normatively references
RFC 8613 Object Security for Constrained RESTful Environments (OSCORE)
References Referenced by
Proposed Standard informatively references
RFC 8747 Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)
References Referenced by
Proposed Standard normatively references
RFC 8949 Concise Binary Object Representation (CBOR)
References Referenced by
Internet Standard normatively references
RFC 9052 CBOR Object Signing and Encryption (COSE): Structures and Process
References Referenced by
Internet Standard normatively references
RFC 9053 CBOR Object Signing and Encryption (COSE): Initial Algorithms
References Referenced by
Informational normatively references Downref
RFC 9200 Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
References Referenced by
Proposed Standard normatively references
RFC 9202 Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)
References Referenced by
Proposed Standard informatively references
RFC 9203 The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework
References Referenced by
Proposed Standard informatively references
RFC 9237 An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)
References Referenced by
Proposed Standard normatively references
RFC 9277 On Stable Storage for Items in Concise Binary Object Representation (CBOR)
References Referenced by
Proposed Standard informatively references
RFC 9290 Concise Problem Details for Constrained Application Protocol (CoAP) APIs
References Referenced by
Proposed Standard normatively references
RFC 9338 CBOR Object Signing and Encryption (COSE): Countersignatures
References Referenced by
Internet Standard normatively references
RFC 9431 Message Queuing Telemetry Transport (MQTT) and Transport Layer Security (TLS) Profile of Authentication and Authorization for Constrained Environments (ACE) Framework
References Referenced by
Proposed Standard informatively references