http listen mode (Roman's DISCUSS)

[boucadair]

** Section 5.4.3. It appears that there is an http-auth-client for both http
and https. Is this suggesting that it is possible to have authenticated users
over unencrypted HTTP. How does that work securely? Is this related to
Section 8’s “The ietf-alto supports an HTTP listen mode to cover cases where
the ALTO server stack does not handle the TLS termination itself, but is
handled by a separate component.” If so, what is the residual risk of this
approach?

[boucadair]

see also #27

[boucadair]

Also from Éric V:

Section 5.3.1.1

As I am trusting the SEC ADs' reviews, I will not ballot a blocking
DISCUSS,
please remove all HTTP (as opposed to HTTPS) in the text and in the
data model
itself. Or is "http" used instead of "https" ? But, then why is there
a "tls"

[Med] The WG had some cycles on this specific point (https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues/27). This http-listen is echoing what is in https://datatracker.ietf.org/doc/draft-ietf-netconf-restconf-client-server/:

• The "transport" choice node enables either the HTTP or HTTPS
  transports to be configured, with each option enabled by a
  "feature" statement. The HTTP option is provided to support cases
  where a TLS-terminator is deployed in front of the RESTCONF-
  server.

EV: A variation of the text at the bottom about http vs. https would be nice in section 5.3.1.1

[boucadair]

From Zahed:

Also supporting Roman's discuss. It is very important that we record
under what circumstances ALTO servers are configured to use HTTP
instead of HTTPS.