RFC 9711 Quiz (EN)

**Judgment point:** Separate the role of Entity Attestation Token from nearby security functions and policy decisions. **Related keywords:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **Options:** - A: making every relying party trust an entity without verifier policy is not the central purpose of RFC 9711. It can be nearby work, but it is not the decision this RFC primarily supports. - B: carrying attested claims about an entity so a relying party can evaluate trust in that entity is the reason this RFC belongs in the review path. It drives checks on inputs, validation, and boundaries. - C: replacing the RATS architecture roles of Attester, Verifier, and Relying Party is outside the RFC boundary. Higher-layer policy and adjacent protocol responsibilities still need separate text.

**Judgment point:** Entity Attestation Token is a building block. Acceptance conditions, authorization, and deployment exceptions must still be explicit. **Related keywords:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **Options:** - A: which claims, issuers, appraisal rules, and relying-party decisions are acceptable 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: validate the token protection, freshness, issuer, intended use, and claim meanings before deriving trust 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 Entity Attestation Token consistent across implementations. **Related keywords:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **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: include claims that describe the entity and state, and bind them to freshness evidence required by the profile 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:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **Options:** - A: accepting an EAT because it is signed while ignoring nonce, freshness, issuer, and appraisal policy 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:** Entity Attestation Token needs validation against its defined inputs and scope, not just its delivery path. **Related keywords:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **Options:** - A: HTTPS protects transport, but it does not replace validation of Entity Attestation Token. - B: validate the token protection, freshness, issuer, intended use, and claim meanings before deriving trust 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:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **Options:** - A: EAT claims, nonce or freshness data, JWT or CWT container choice, and attestation-oriented claim semantics is part of the mechanism RFC 9711 addresses directly. It is not the policy layer. - B: which claims, issuers, appraisal rules, and relying-party decisions are acceptable 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 Evidence and Attestation Results map to the local trust decision 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:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **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: treating stale or context-free attestation claims as current authorization evidence 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:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **Options:** - A: RFC 9334 defines RATS roles, while RFC 9711 defines a token format for attestation-oriented claims preserves the responsibility split. - B: Obsoletion is explicit in RFC metadata and text. Nearby concepts do not automatically replace one another. - C: Entity Attestation Token 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:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **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 service needs evidence about a device, workload, or component state before granting trust 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:** - **EAT**: Attestation claims token - **freshness**: Protection against stale evidence - **Relying Party**: Party using attestation results **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.