RFC 1958 (Internet Architectural Principles) Quiz

Q1: How should the principles in RFC 1958 be used?

Multiple Choice

A. As an invariant formal model that no later design may revise B. As normative wire requirements for claiming protocol conformance C. As a snapshot of useful guidance to apply with engineering evidence and changing conditions

**Explanation:** A: the document says it is not a formal or invariant reference model. B: RFC 1958 is Informational and does not define a protocol wire format. C: it records guidelines, while treating constant change and feedback from real implementations as fundamental.

Q2: Which summary matches RFC 1958's high-level view of Internet architecture?

Multiple Choice

A. The goal is connectivity, the tool is IP, and intelligence is primarily end to end B. The goal is one application, the tool is a proprietary gateway, and intelligence is hidden in transit nodes C. The goal is centralized control, the tool is manual configuration, and endpoints remain passive

**Explanation:** A: RFC 1958 presents global connectivity as the goal and IP plus end-to-end intelligence as the architectural means. B: connectivity is more valuable than any one application, and proprietary semantic gateways fragment it. C: the Internet evolves without one central owner, and manual state should be minimized.

Q3: A network link performs error detection, but an application must know whether an entire object arrived intact. Where does the final integrity check belong?

Multiple Choice

A. Only in the first transit router, because lower-layer checks make endpoint checks redundant B. At the endpoints, while lower-layer checks may still provide a performance enhancement C. In a global registry that observes every packet from every application

**Explanation:** A: any network path can still fail beyond one link, and the router lacks complete application knowledge. B: only the endpoints can fully verify the end-to-end function; lower layers may supply useful incomplete checks. C: centralized observation is neither necessary nor sufficient for application correctness.

Q4: Which properties should network-maintained state have under RFC 1958? Select all that apply.

Multi-Select

A. Adaptive procedures should derive and repair it as topology or activity changes B. Every end-to-end session record should be manually configured in permanent storage C. Its volume and manually configured portion should be minimized D. Losing it should cause no more than a temporary denial of service when connectivity remains

**Explanation:** A: Adaptive procedures let the network reconstruct state after topology or activity changes. B: Permanent per-session configuration violates the guidance and makes the network a fragile owner of endpoint communication state. C: Minimizing state and manual configuration reduces operational and recovery dependencies. D: Recoverable state limits its loss to temporary disruption when connectivity still exists.

Q5: Two protocol proposals have persuasive architecture documents, but neither has interoperating implementations. What is still missing?

Multiple Choice

A. A single organization with authority to turn off competing designs B. More manually selected options before implementation begins C. Engineering feedback from multiple instances of running code

**Explanation:** A: the Internet has no single owner and evolves through cooperation. B: options increase ambiguity and implementation burden. C: RFC 1958 values rough consensus and running code, and says real implementation feedback outweighs architectural principle alone.

Q6: A new protocol works only when all peers have similar CPU, memory, bandwidth, and application timing. Which RFC 1958 concern is most direct?

Multiple Choice

A. Heterogeneity is inevitable and must be supported by design B. All hardware media must expose the same native address format C. One application type should determine Internet-layer behavior

**Explanation:** A: Internet protocols must accommodate large differences in hosts, links, and applications. B: the Internet layer is deliberately independent of hardware media and addressing. C: the architecture supports many application protocols rather than optimizing the common layer for one.

Q7: A design introduces a second incompatible mechanism that solves the same problem as a deployed mechanism, with no demonstrated technical advantage. What is the preferred review outcome?

Multiple Choice

A. Standardize both so every implementation must support permanent dual behavior B. Reuse the successful solution unless a good technical reason justifies the new one C. Select the new mechanism solely because it has more parameters

**Explanation:** A: duplication creates interoperability and maintenance cost. B: RFC 1958 advises choosing one solution and reusing successful prior work unless technical improvement justifies change. C: parameter count is not technical value, and unnecessary options should be avoided.

Q8: Which decisions reflect RFC 1958's general design guidance? Select all that apply.

Multi-Select

A. Keep separable functions modular B. Prefer a simple, almost complete solution now over waiting indefinitely for perfection C. Add manual configuration choices for every conceivable deployment difference D. Consider scale, performance, and cost together with functionality

**Explanation:** A: Modular boundaries contain responsibilities when functions can remain separate. B: A simple, useful solution now can produce implementation feedback that an indefinitely delayed perfect design cannot. C: RFC 1958 recommends avoiding options and parameters where possible and negotiating necessary ones dynamically instead of relying on manual configuration. D: A functional design that does not scale or is too costly is not an adequate Internet design.

Q9: Routing startup requires a DNS lookup, but reaching the DNS server requires routing to be operational. How does RFC 1958 classify this design?

Multiple Choice

A. A desirable form of fate sharing because both services fail together B. A harmless optimization because DNS names are easier to read C. A circular dependency that must be removed

**Explanation:** A: fate sharing keeps communication state with the endpoints; it does not justify startup deadlock. B: readability does not remove the bootstrap failure. C: RFC 1958 uses routing depending on DNS as its explicit circular-dependency example.

Q10: An Agent-to-Agent service relies on a private carrier link, so endpoints perform no integrity or peer-authentication check. Which review conclusion follows RFC 1958?

Multiple Choice

The carrier may protect traffic on its segment, but the application needs assurance about the complete path and the peer agent.

A. Carrier protection can be defense in depth, but endpoints still need the end-to-end checks required by their threat model B. A private segment automatically authenticates the application-level agent and its authority C. The application should move all identity state into transit routers

**Explanation:** A: RFC 1958 assigns confidentiality and authentication responsibility to end users and says endpoints should not depend on carrier confidentiality or integrity. B: link or carrier trust does not establish application identity or authorization. C: moving endpoint identity state into the network increases coupling and weakens fate sharing.

RFC 1958 Quiz

Internet architecture as evolving guidance

References (URLs)

Q1: How should the principles in RFC 1958 be used?

Q2: Which summary matches RFC 1958's high-level view of Internet architecture?

Q3: A network link performs error detection, but an application must know whether an entire object arrived intact. Where does the final integrity check belong?

Q4: Which properties should network-maintained state have under RFC 1958? Select all that apply.

Q5: Two protocol proposals have persuasive architecture documents, but neither has interoperating implementations. What is still missing?

Q6: A new protocol works only when all peers have similar CPU, memory, bandwidth, and application timing. Which RFC 1958 concern is most direct?

Q7: A design introduces a second incompatible mechanism that solves the same problem as a deployed mechanism, with no demonstrated technical advantage. What is the preferred review outcome?

Q8: Which decisions reflect RFC 1958's general design guidance? Select all that apply.

Q9: Routing startup requires a DNS lookup, but reaching the DNS server requires routing to be operational. How does RFC 1958 classify this design?

Q10: An Agent-to-Agent service relies on a private carrier link, so endpoints perform no integrity or peer-authentication check. Which review conclusion follows RFC 1958?