RFC 5705 Quiz (EN)

**Judgment point:** Separate the role of TLS exporter from nearby security functions and policy decisions. **Related keywords:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **Options:** - A: exporting TLS private keys to the application layer is not the central purpose of RFC 5705. It can be nearby work, but it is not the decision this RFC primarily supports. - B: deriving application-specific keying material from an established TLS connection is the reason this RFC belongs in the review path. It drives checks on inputs, validation, and boundaries. - C: assigning authorization meaning to every byte derived from TLS is outside the RFC boundary. Higher-layer policy and adjacent protocol responsibilities still need separate text.

**Judgment point:** TLS exporter is a building block. Acceptance conditions, authorization, and deployment exceptions must still be explicit. **Related keywords:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **Options:** - A: what the exported bytes authorize, identify, or bind in the application protocol 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: check that both peers use the same label, context, length, and connection before comparing derived bytes 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 TLS exporter consistent across implementations. **Related keywords:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **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: define a collision-resistant exporter label and context string for the application purpose 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:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **Options:** - A: comparing exporter bytes that were derived with a different label, context, or connection 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:** TLS exporter needs validation against its defined inputs and scope, not just its delivery path. **Related keywords:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **Options:** - A: HTTPS protects transport, but it does not replace validation of TLS exporter. - B: check that both peers use the same label, context, length, and connection before comparing derived bytes 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:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **Options:** - A: exporter label, context value, output length, and TLS connection secrets is part of the mechanism RFC 5705 addresses directly. It is not the policy layer. - B: what the exported bytes authorize, identify, or bind in the application protocol 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 exporter output is encoded and transported 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:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **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: reusing a generic label across different protocol purposes or omitting context where separation is needed 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:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **Options:** - A: RFC 5705 defines exporters for older TLS usage, and later TLS 1.3 channel binding work builds on exporter ideas preserves the responsibility split. - B: Obsoletion is explicit in RFC metadata and text. Nearby concepts do not automatically replace one another. - C: TLS exporter 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:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **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 an application proof or key confirmation value must be tied to the TLS session 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:** - **exporter label**: A name that separates exporter uses - **context**: Extra separation input - **keying material**: Bytes derived from TLS secrets **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.