assisted installer follow-up

This is a follow-up change to openshift#376 with some placeholders for
discussion items that were not resolved before the previous PR merged.

Signed-off-by: Doug Hellmann <[email protected]>

Author: dhellmann

enhancements/installer/connected-assisted-installer.md

@@ -184,6 +184,8 @@ the installer or to the cluster, so I can adapt my existing admin
 processes and infrastructure management tools instead of replacing
 them.
 
+There was some question about whether this story was relevant.
+
 #### Story 4
 
 As a cluster hardware administrator, I want to enable power control
@@ -209,6 +211,16 @@ that approach cannot be supported, users can proceed by providing an
 extra host (4 hosts to build a 3 node cluster, 6 hosts to build a 5
 node cluster, etc.).
 
+There was a question about how the agent is secured:
+
+Could you add some specifics notes on the security for this design?
+There are a lot of attack vectors in remote installation and auto-join
+systems, but maybe there are details I’m missing that make this model
+secure. Would be helpful to have them explicitly noted.
+
+This part of the change should be replaced with those details, when
+ready.
+
 ## Design Details
 
 ### Test Plan
@@ -307,7 +319,7 @@ The idea is to find the best form of an argument why this enhancement should _no
 
 ## Alternatives
 
-The telco/edge bare metal team is working on support for automating
+The bare metal IPI team is working on support for automating
 virtual media and dropping the need for a separate provisioning
 network. Using the results will still require the user to understand
 how to tell the installer the BMC type and credentials and to ensure