> > > A.41. Section 10.1 expiration definition > > I think that it would be a good idea to say that a Node should wait a random > time after the expiration time before retrieving the file again from the > configuration server to not crash it and to let ConfigUpdate do its job. >
Makes sense. I'm going to add the text The peer SHOULD retrieve a new copy of the configuration at a randomly selected time that is before the expiration time. I'm not all that happy with that text it someone wants to suggest something better. It does not tell the implementors what range to select the time over but it's not clear we have to be that specific. > A.42. Section 10.1 client-permitted definition > > I have no idea how an overlay can enforce this. All nodes starts as clients, > so > how an overlay is supposed to know the difference between a real client and a > client that yet had to do the steps required to become a peer? > Agree. Changed to If it is set to "FALSE" then nodes are not allowed to remain clients after the initial join. There is currently no way for the overlay to enforce this. _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
