- From: Menachem Dodge via Datatracker <noreply@ietf.org>
- Date: Tue, 10 Oct 2023 04:26:39 -0700
- To: <ops-dir@ietf.org>
- Cc: draft-ietf-httpbis-alias-proxy-status.all@ietf.org, ietf-http-wg@w3.org, last-call@ietf.org
Reviewer: Menachem Dodge Review result: Has Nits Reviewer: Menachem Dodge Review result: Has Nits I have reviewed this document as part of the Ops area directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Ops area directors. Document editors and WG chairs should treat these comments just like any other last-call comments. Summary This document defines the next-hop-aliases HTTP Proxy-Status Parameter. NITS: 1. Abstract OLD --> This parameter carries the list of aliases and canonical names an intermediary received during DNS resolution as part establishing a connection to the next hop. NEW --> This parameter carries the list of aliases and canonical names an intermediary received during DNS resolution as part of establishing a connection to the next hop. 2. Section 2 OLD --> Note that while this example includes both the next-hop and next-hop-aliases parameters, next-hop-aliases can be included without including next-hop. NEW --> Note that while this example includes both the next-hop and next-hop-aliases parameters, next-hop-aliases can be included without including the next-hop. 3. Section 3 OLD --> Implementations ought to note that the full chain of names might not available in common DNS resolution APIs, such as getaddrinfo. NEW --> Implementations ought to note that the full chain of names might not be available in common DNS resolution APIs, such as getaddrinfo. Thank you kindly. Best Regards, Menachem Dodge
Received on Tuesday, 10 October 2023 11:26:45 UTC