[Can] Addressing IESG comments on CAN charter so far

[Adrian Farrel <[e-mail]>]

Hi,

Martin Duke : Block : Cross-domain
Opinions from list : Not in immediate scope
Proposal :
OLD
The assumed model for the CAN WG is an overlay network, where a network
edge node makes a decision based on the metrics of interest, and then
steers the traffic to a node that serves a service instance, for example
using a tunnel. Architectures that require the underlay network to be
service-aware are out of scope.
NEW
The assumed model for the CAN WG is an overlay network, where a network
edge node makes a decision based on the metrics of interest, and then
steers the traffic to a node that serves a service instance, for example
using a tunnel. The CAN WG will initially focus on single domain models.
Architectures that require the underlay network to be service-aware
are out of scope.
END

===

Martin Duke : Comment : ALTO present tense wording
Opinions : Mailing list suggestion to clarify difference in scope wrt ALTO
Proposal : 
OLD
The IETF has done past work on exposing network conditions to endpoints
(notably ALTO) and load balancing/service selection at layers 4 and 7
(for example, related to the selection of SIP servers). Specific
characteristics that may distinguish CAN from other work include the
desire to integrate both network and compute conditions in the
optimization function, and the desire to operate that function on nodes
within the service provider's network, logically separated from service
operation.
NEW
The IETF is working on exposing network conditions to endpoints
(notably ALTO) and load balancing/service selection at layers 4 and 7
(for example, related to the selection of SIP servers). Specific
characteristics that may distinguish CAN from other work include the
desire to integrate both network and compute conditions in the
optimization function, and the desire to operate that function on nodes
within the service provider's network, logically separated from service
operation. Exposure of network and compute conditions to applications
is not in the scope of CAN.
END

===

Cheers,
Adrian