RFC 8705 Quiz (EN)

**Judgment point:** Separate the role of OAuth mTLS binding from nearby security functions and policy decisions. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: authenticating the resource owner or end user only because a client certificate exists is not the central purpose of RFC 8705. It can be nearby work, but it is not the decision this RFC primarily supports. - B: authenticating OAuth clients with mutual TLS and binding access tokens to certificate material is the reason this RFC belongs in the review path. It drives checks on inputs, validation, and boundaries. - C: making bearer-token replay impossible when resource servers skip certificate matching is outside the RFC boundary. Higher-layer policy and adjacent protocol responsibilities still need separate text.

**Judgment point:** OAuth mTLS binding is a building block. Acceptance conditions, authorization, and deployment exceptions must still be explicit. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: accepted client certificate authorities, subject constraints, and token audience policy is not decided by the RFC alone. The relying application must say what success means. - B: Skipping local acceptance policy can accept a valid object in the wrong context. That crosses the RFC boundary. - C: verify that the presented client certificate matches the certificate binding in the access token is a boundary the implementation review must preserve. Source and scope mistakes cause false acceptance. - D: An RFC citation can be necessary, but deployment configuration, keys, trust, and failure handling are not automatic.

**Judgment point:** A profile is the contract that makes use of OAuth mTLS binding consistent across implementations. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: If input bytes and context are free-form, implementations verify different values. - B: Human-readable text is useful for explanation, but it is unstable as a validation input. Locale and wording changes break it. - C: issue tokens with certificate confirmation data and define how the TLS client certificate reaches the resource server is required. Clear producer rules let verifiers evaluate the same object under the same assumptions.

**Judgment point:** Interoperability failures appear when the same wire data receives different processing meanings. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: checking the token but not checking the current TLS client certificate against the token binding shifts the validation target or meaning. Implementations can then disagree about success. - B: Limiting BCP 14 words to real requirements reduces ambiguity rather than creating it. - C: Documenting unsupported-extension behavior reduces implementation divergence.

**Judgment point:** OAuth mTLS binding needs validation against its defined inputs and scope, not just its delivery path. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: HTTPS protects transport, but it does not replace validation of OAuth mTLS binding. - B: verify that the presented client certificate matches the certificate binding in the access token is the central step. It separates well-formed input from acceptable input. - C: A filename or path can be a routing hint, but it is not enough as identity or security proof.

**Judgment point:** A specification can define processing rules while still leaving acceptance policy outside the mechanism. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: client certificate authentication methods and certificate-bound access token confirmation data is part of the mechanism RFC 8705 addresses directly. It is not the policy layer. - B: accepted client certificate authorities, subject constraints, and token audience policy is an application or deployment acceptance condition. - C: Well-formed syntax and algorithm processing belong to the RFC-defined side. The meaning of success still needs policy. - D: how revocation or certificate rotation affects existing tokens is local policy. It should be written for the deployment and threat model.

**Judgment point:** A security review looks for false-acceptance paths, not just whether the mechanism is present. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: Performance can matter, but caching does not replace a security property. - B: A recent library helps, but local policy, inputs, and threat model still need review. - C: terminating TLS at a proxy without preserving trustworthy client-certificate information to the resource server is the central failure mode. Attackers exploit this kind of context or trust shift.

**Judgment point:** Adjacent specifications are usually safer to read as layered responsibilities, not automatic replacements. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: RFC 7800 defines confirmation-key semantics, while RFC 8705 applies certificate binding in OAuth deployments preserves the responsibility split. - B: Obsoletion is explicit in RFC metadata and text. Nearby concepts do not automatically replace one another. - C: OAuth mTLS binding matters in protocol composition reviews. Treating it as unrelated hides boundaries.

**Judgment point:** Review questions should show whether implementers can reproduce the same success and failure boundary. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: Naming inputs, context, validation rules, and rejection behavior directly reduces implementation differences. - B: An RFC number does not define local semantics by itself. A profile or policy must fill the gap. - C: Treating unknown values as success can accept extensions or attacker input incorrectly. - D: when a confidential OAuth client or resource request must be constrained to a client certificate is a real review setting. Fixing success conditions there reduces misuse.

**Judgment point:** Validation failure is a signal to stop using that input as evidence for the decision. **Related keywords:** - **mutual TLS**: TLS with client-certificate authentication - **certificate-bound token**: Token tied to certificate material - **cnf**: Confirmation claim **Options:** - A: Downgrading to a warning creates fail-open behavior. Attacker-controlled input can enter the success path. - B: Treating the result as unusable for that decision is safe. If fallback exists, it needs explicit policy. - C: Authorization is important, but it does not automatically repair broken validation input.