Charter updates based on side meeting

charter.md

@@ -1,12 +1,13 @@
-## HAPPY WG (Heuristics and Algorithms to Prioritize Protocol deploYment)
+## HAPPIE WG (Heuristics and Algorithms to Prioritize Protocol Initiation and Establishment)
 
 RFC 8305 defined “Happy Eyeballs Version 2”, which described a client algorithm 
 for asynchronous resolution of and connection attempts to different server IP 
-address options, aiming to improve IPv6 usage without adding risk due to 
-misconfigured networks or servers. The algorithm focused specifically on 
-optimizing TCP connection establishment. The name “happy eyeballs” itself refers
-to how a user’s eyeballs are happier when content loads more quickly because 
-they don’t need to wait for timeouts due to misconfigured deployments.
+address options, aiming to improve IPv6 usage without degrading connection
+establishment success rates due to misconfigured networks or servers. The
+algorithm focused specifically on optimizing TCP connection establishment.
+The name “happy eyeballs” itself refers to how a user’s eyeballs are happier
+when content loads more quickly because they don’t need to wait for timeouts
+due to misconfigured deployments.
 
 Since the publication of RFC 8305, several changes to common protocols and 
 server deployments have occurred that require a revision of the algorithm. Some 
@@ -17,17 +18,29 @@ of these include:
 - Introduction of Service Binding DNS resource records (SVCB and HTTPS RRs) that
   provide richer information about available services and record priorities
   and change the selection and sorting of addresses for Happy Eyeballs.
-- Preparations for the standardization of TLS Encrypted Client Hello.
+- Preparations for the standardization of TLS Encrypted Client Hello, which
+  can impact which servers a client is willing to connect to based on available
+  security properties.
 - Increased deployment and refinement of IPv6-only and IPv6-mostly networks.
 
-The HAPPY working group will deliver an updated version of the Happy Eyeballs 
+The HAPPIE working group will deliver an updated version of the Happy Eyeballs 
 algorithm that incorporates changes to account for these protocol developments.
-The algorithm should focus on deployed network scenarios and should be guided by
-data on user experience focused performance in those scenarios. The working 
-group can also document the impact of the Happy Eyeballs algorithm on the
-detection of misconfigured deployments and can document recommendations on how
-to report such cases that might otherwise be hidden due to automatic switching
-from one technology to another.
+The algorithm will focus on realistic network scenarios and should be guided by
+performance data measured in actual deployed networks. Although the algorithm
+needs to be applicable generically, platform-specific or deployment-specific
+considerations should be documented to help guide implementers. The algorithm
+should be described in a way that it has tunable input values that can reflect
+the preferences of a client implementation; defaults for these input values
+can be based on what the working group agrees ought to be the standard behavior
+(such as preferring IPv6 connections, preferring faster establishment times,
+etc.), but allow for variation.
+
+The working group will also document the impact of the Happy Eyeballs algorithm
+on the detection of misconfigured deployments, and may provide recommendations on
+how to report such cases that might otherwise be hidden due to automatic switching
+from one technology to another. Any recommended reporting mechanisms need to
+preserve user privacy, allow for accurate detection of broken deployments,
+and lead to some actionable result.
 
 The working group will focus on a connection establishment algorithm that
 runs on clients. The algorithm takes as input a fully-qualified domain name
@@ -39,12 +52,15 @@ working group deliverables.
 
 The rationale for having a working group for this work, instead of hosting it in
 V6OPS, is the increased cross-functional nature of the algorithm. As such, the 
-HAPPY working group will review its work with groups such as V6OPS, TSVWG, QUIC, 
+HAPPIE working group will review its work with groups such as V6OPS, TSVWG, QUIC, 
 HTTPBIS, DNSOP, and TLS.
 
 The working group’s core deliverables are:
 
-- Develop a standards-track document for Happy Eyeballs Version 3
-- Measure the effectiveness of the algorithm during development. This effort
+- Developing a standards-track document for Happy Eyeballs Version 3
+- Measuring the effectiveness of the algorithm during development. This effort
   does not necessarily need to lead to a published document, but should be
   captured in presentations, working group wikis, etc.
+- Producing a document that explains the impact of Happy Eyeballs on
+  detecting and measuring broken deployments, with recommendations on
+  how to report errors in a private, accurate, and actionable way.