Hi, Jordi:
Thank for writing this draft, to tackle multi-domain setting issue, if my
understanding is correct,
what you propose is to add new functionality to ALTO server and extend ALTO
protocol. It is interesting topic,
I think it is also related to what PANRG and COINRG are doing.
1. First Computation of Bottleneck Substructures is computation intensive,
which might require in network computing support.
2. The multi-domain setting has been documented in ALTO deployment RFC, see
quoted text:
"
ALTO is inherently
designed for use in multi-domain environments. Most importantly,
ALTO is designed to enable deployments in which the ALTO server and
the ALTO client are not located within the same administrative
domain.
"
"
o Multiple administrative domains: The ALTO protocol is designed for
use cases where the ALTO server and client can be located in
different organizations or trust domains. ALTO assumes a loose
coupling between server and client. In addition, ALTO does not
assume that an ALTO client has any a priori knowledge about the
ALTO server and its supported features. An ALTO server can be
discovered automatically.
"
3. When you say the distributed protocol proposed in this document could be
used as a use
case to help drive the specifications of the inter-server communication
protocol discussed in [I-D.draft-zhang-alto-oam-yang],
I am not sure we should couple the distributed protocol you proposed with
server to server communication.
I think ALTO OAM is positioned to integrate various different tools to
capture network data, oam data, flow data, build network map and cost map.
Existing protocol can be used, such as routing protocol, OAM protocol,
IPFIX, do you want to propose to use ALTO to define such distribute protocol?
why BGP is not sufficient? Also distribute information across domain has a
big security concern, how do you address this?
4. Let's take a close look at PATH_METRIC_ANNOUNCEMENT, what packet format
looks like? what parameters are carried in PATH_METRIC_ANNOUNCEMENT?
5. When you say "ensures each domain's independent
convergence to the correct bottleneck substructure graph without the
need to know private flow and topology information from other
domains. " , I am wondering whether you use PATH_METRIC_ANNOUNCEMENT to
carry path metric information will expose some private flow and path
information?
Happy to discuss more in London during IETF week.
-Qin
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
