But Gigi, perhaps I see this all as attributes for a domain (although it is perhaps more about the scope of number of interconnectivity in that domain, but I see HEAnet (the Irish NREN) also also only as connecting a lot of domains (of our clients and some international ones) and not really end-systems). For me a GOLE is just a domain (with certain attributes and values). All the best, Victor Gigi Karmous-Edwards wrote:I think another key difference is that a GOLE has a high concentration of cross-border fibers which includes those that interconnects to other GOLEs. In my opinion distinguishing a GOLE from a domain is useful for path computation. Also, we rarely find termination (compute, instrument, etc. ) points within GOLEs. Therefore, their function is to primarily interconnect to other domains and GOLEs. Thanks, Gigi Victor Reijs (work) wrote:Hello Freek and Erik-Jan, Freek Dijkstra wrote:The only distinction between a GOLE and an other domain is that a GOLE is it's policy: a GOLE is "open" and will thus not define a policy on its own (it may enforce the policy of connected domains, though).But if 'policy' is an attribute of a domain, then that is even no difference (at least looking at the abstract level). Correct? All the best, Victor _______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg