From 4ac713e7acef137d5e1bf3def25b62b947b9a98c Mon Sep 17 00:00:00 2001 From: Tommy Pauly Date: Wed, 25 Oct 2023 08:49:59 -0700 Subject: [PATCH] Add reference to RFC3493 Closes #2667 --- draft-ietf-httpbis-alias-proxy-status.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-httpbis-alias-proxy-status.md b/draft-ietf-httpbis-alias-proxy-status.md index 5dc3e3d81..c859773eb 100644 --- a/draft-ietf-httpbis-alias-proxy-status.md +++ b/draft-ietf-httpbis-alias-proxy-status.md @@ -165,9 +165,9 @@ In order to include the `next-hop-aliases` parameter, a proxy needs to have acce of alias names and canonical names received in CNAME records. Implementations ought to note that the full chain of names might not be available in common DNS -resolution APIs, such as `getaddrinfo`. `getaddrinfo` does have an option for `AI_CANONNAME`, -but this will only return the last name in the chain (the canonical name), not the alias -names. +resolution APIs, such as `getaddrinfo`. `getaddrinfo` does have an option for `AI_CANONNAME` +({{Section 6.1 of ?RFC3493}}), but this will only return the last name in the chain +(the canonical name), not the alias names. An implementation MAY include incomplete information in the `next-hop-aliases` parameter to accommodate cases where it is unable to include the full chain, such as only including the canonical name if the implementation can only use `getaddrinfo` as described above.