> -----Original Message----- > From: Anima [mailto:[email protected]] On Behalf Of Sheng Jiang > Sent: 03 May 2016 04:03 > To: Brian E Carpenter <[email protected]>; Anima WG > <[email protected]> > Subject: Re: [Anima] Proposed change to GRASP > [...] > One question: does this new namespace also need to be managed by IANA > or there could be other mechanism to manage it so that the uniqueness > could be guaranteed?
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... Michael _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
