Skip to main content

References from draft-ietf-scim-api

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
BCP 14
References Referenced by
normatively references
BCP 18
References Referenced by
informatively references
BCP 195
References Referenced by
informatively references
draft-ietf-httpauth-basicauth-update The 'Basic' HTTP Authentication Scheme
References Referenced by
Proposed Standard informatively references
draft-ietf-oauth-assertions Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants
References Referenced by
Proposed Standard informatively references
draft-ietf-oauth-pop-architecture OAuth 2.0 Proof-of-Possession (PoP) Security Architecture
References Referenced by
Informational informatively references
draft-ietf-precis-framework PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
References Referenced by
Proposed Standard informatively references
draft-ietf-precis-saslprepbis Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
References Referenced by
Proposed Standard normatively references
draft-ietf-scim-core-schema System for Cross-domain Identity Management: Core Schema
References Referenced by
Proposed Standard normatively references
draft-nottingham-uri-get-off-my-lawn Standardising Structure in URIs
References Referenced by
informatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice informatively references
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by
Draft Standard informatively references
RFC 3553 An IETF URN Sub-namespace for Registered Protocol Parameters
References Referenced by
Best Current Practice 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 normatively references
RFC 4627 The application/json Media Type for JavaScript Object Notation (JSON)
References Referenced by
Informational informatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by
Proposed Standard normatively references
RFC 5789 PATCH Method for HTTP
References Referenced by
Proposed Standard normatively references
RFC 6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
References Referenced by
Proposed Standard normatively references
RFC 6265 HTTP State Management Mechanism
References Referenced by
Proposed Standard informatively references
RFC 6749 The OAuth 2.0 Authorization Framework
References Referenced by
Proposed Standard normatively references
RFC 6750 The OAuth 2.0 Authorization Framework: Bearer Token Usage
References Referenced by
Proposed Standard normatively references
RFC 6819 OAuth 2.0 Threat Model and Security Considerations
References Referenced by
Informational informatively references
RFC 6902 JavaScript Object Notation (JSON) Patch
References Referenced by
Proposed Standard informatively references
RFC 7159 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Proposed Standard normatively references
RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by
Proposed Standard normatively references
RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by
Proposed Standard normatively references
RFC 7232 Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
References Referenced by
Proposed Standard normatively references
RFC 7233 Hypertext Transfer Protocol (HTTP/1.1): Range Requests
References Referenced by
Proposed Standard normatively references
RFC 7235 Hypertext Transfer Protocol (HTTP/1.1): Authentication
References Referenced by
Proposed Standard normatively references
RFC 7486 HTTP Origin-Bound Authentication (HOBA)
References Referenced by
Experimental informatively references
RFC 7525 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by
Best Current Practice informatively references
RFC 7538 The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
References Referenced by
Proposed Standard normatively references
STD 63
References Referenced by
normatively references
STD 66
References Referenced by
normatively references
STD 68
References Referenced by
normatively references