RFC 8890 Quiz (EN)

The Internet is for End Users

0 / 0

References (URLs)

Q1: What is the central review lens of RFC 8890

Multiple Choice
**Judgment point:** RFC 8890 adds a review lens. It asks whether choices serve the people and organizations ultimately affected by the Internet. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: Operator simplicity can matter, but it is not automatically the controlling interest. - B: The end-user effect and conflict analysis are the heart of this RFC. - C: The RFC does not ban intermediaries or providers; it asks designers to evaluate their effect on end users.

Q2: Which statements fit the RFC 8890 view of end users. Select all that apply

Multi-Select
**Judgment point:** The end-user concept is broader than a login account or a browser session. It is about who ultimately benefits or is harmed. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: This matches the broad end-user lens used for standards review. - B: Operators and end users can overlap, but they often have different incentives. - C: Conflicting incentives are exactly why the RFC asks for explicit end-user analysis. - D: End users appear in many contexts, not only web browsers.

Q3: A protocol adds a new gateway service. What should a reviewer ask first under RFC 8890

Multiple Choice
**Judgment point:** The first question is not whether the component is fashionable or convenient. It is what effect it has on end users. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: Provider cost can be relevant, but it is incomplete without user impact. - B: A market category does not demonstrate user benefit or protection. - C: Help, harm, and agency put the review on the end-user effect rather than provider narrative.

Q4: When does provider convenience become a design concern under RFC 8890

Multiple Choice
**Judgment point:** The RFC does not reject operational convenience. It rejects treating provider convenience as enough when users carry the downside. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: Hidden cost, reduced choice, and new risk are concrete user-impact concerns. - B: Fewer configuration files may help operations, but the user effect still has to be evaluated. - C: The point is to handle conflict, not to wait for perfect alignment.

Q5: Which review flow best applies the end-user lens

Multiple Choice
End-user review flow.
Stakeholders Conflict identified End-user impact Justified trade-off
**Judgment point:** A defensible standards argument makes the trade-off visible before the mechanism is treated as acceptable. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: A note written after the decision can miss the actual conflict. - B: This sequence makes stakeholder conflict and end-user impact part of the decision. - C: Technical elegance does not by itself show benefit or reduced harm for users.

Q6: Which statements are careful uses of RFC 8890. Select all that apply

Multi-Select
**Judgment point:** RFC 8890 improves review quality. It does not remove the need for evidence, security review, privacy review, and technical constraints. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: Requests matter, but standards still need feasibility, interoperability, and harm analysis. - B: Explicit analysis of benefit, harm, agency, and conflict is the intended use. - C: End-user analysis complements security and privacy review; it does not replace them. - D: Trade-offs can be acceptable when they are visible, justified, and revisited as needed.

Q7: How should a reviewer treat agents, gateways, or intermediaries that act on a user’s behalf

Multiple Choice
**Judgment point:** Intermediaries can help users, but they can also concentrate control or hide decisions. The review should inspect incentives. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: Assuming perfect representation hides conflicts of interest. - B: Control points outside the endpoint can strongly affect users. - C: Incentives, defaults, and control points are concrete ways to test whether the component serves users.

Q8: What is the right stance when privacy, safety, usability, and interoperability pull in different directions

Multiple Choice
**Judgment point:** User interests are not always simple. A good review explains why one trade-off is acceptable under the expected conditions. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: This keeps the trade-off visible and reviewable. - B: Implementation ease is not neutral when it changes user risk or choice. - C: Subjective difficulty is a reason to write the analysis more clearly, not to omit it.

Q9: Which text belongs in an RFC 8890-informed design review. Select all that apply

Multi-Select
**Judgment point:** A review that only asserts benefit is hard to evaluate. The reader needs affected parties, evidence, and change triggers. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: Naming affected users and protected interests makes the review concrete. - B: Operator cost may matter, but it is not the only factor in this framework. - C: A broad benefit claim without evidence is not useful review text. - D: Explaining trade-offs and revisit conditions makes the decision auditable.

Q10: If end-user impact is uncertain, what should the specification do

Multiple Choice
**Judgment point:** Uncertainty is normal. The important part is to keep it visible and actionable rather than hiding it. **Related keywords:** - **end user** : Human or organization that ultimately uses or is affected by the Internet - **agency** : Ability to understand and influence outcomes - **trade-off** : Design choice where interests conflict **Options:** - A: Overclaiming turns uncertainty into an unsupported assertion. - B: This gives readers a concrete way to monitor whether the design remains acceptable. - C: Deleting the concern prevents later reviewers from knowing what to watch.