>We need some "common point" to start with. When a node comes up and >hasn't established any AN neighborship, it needs to know which port number >to use. > >For the bootstrap case, intuitively, that ASA port number should be well >known. However, that doesn't help with other ASAs. >Maybe there should be a common port for general negotiation, from which >we then derive the other port numbers dynamically? > >The way I see it right now, on every node there will be a "management ASA", >or "meta ASA", which must be on every node, and is used for controlling the >other ASAs. We could define a port number for that with IANA, and have all >other ports negotiated dynamically. Now Stuart would probably say we >should use mDNS for such a purpose...
I agree the need for a management ASA. But I am not sure it needs a fixed port number. Dynamic port number could work well for management ASA, too. The "discovery ASA", if there will be one, needs a fixed port number. However, it could just use the GRASP port number, I guess. Or you mean a management ASA includes discovery function to discover ASAs on other node? Sheng >Michael _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
