Merge pull request #50 from tfpauly/tfpauly-patch-2

Clarify out-of-scope

charter.md

@@ -29,10 +29,13 @@ 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 working group will focus on connection establishment where the client knows 
-a hostname and needs to establish a connection to a server IP address using a 
-particular network. Algorithms for more general aspects of connection 
-establishment attempts across multiple networks, etc, are out of scope.
+The working group will focus on a connection establishment algorithm that
+runs on clients. The algorithm takes as input a fully-qualified domain name
+(FQDN), and results in a single established connection to a single server IP
+address on a single network. While the algorithm could apply to scenarios with
+multiple networks to choose between or to use simultaneously, or could deal
+with pools of multiple connections, such scenarios are out of scope for the
+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