On 9/10/2012 11:36 AM, Andrew Deason wrote: > On Mon, 10 Sep 2012 01:19:40 -0400 > Jeffrey Altman <[email protected]> wrote: > >> While you may fork the code base, you may not fork the AFS3 wire >> protocols. If you decide to implement your own extensions to AFS3 you >> must follow the rules of the AFS3 standardization and RPC registration >> processes. If you choose not to follow those rules, then you must >> implement your own wire protocol that will not interfere with AFS3 >> clients and servers. > > Aside from what Simon said, anyone can just request RPC code points > without explanation of what they are. If Troy wants to request 50 > 'private' points from each relevant package and make his own protocol, I > have a hard time seeing the trouble with that.
Requesting RPC code points would be following the standardization and registration process.
signature.asc
Description: OpenPGP digital signature
