[email protected] is an RT queue, so I would appreciate your
_not_ sending mail to it and the mailing list at the same time. Doing so
results in a new, pointless ticket every time someone responds to the
mailing list post.
--On Thursday, March 12, 2009 06:08:29 PM +0100 Hartmut Reuter
<[email protected]> wrote:
Derrick Brashear had already promised several times to integrate this
code into the normal OpenAFS code base. To help make that happen I am
now trying to register the extensions to the RPC interface.
... which has been going poorly, because I've been lame about answering.
Looking through my lists of requests, I don't see any conflicts, so you can
consider these assigned.
I did find some indication that some of these procedures may have had
previous, lower numbers; if those are still in use or were ever deployed
outside your organization, we should reserve them as well to avoid
potential conflicts. Similarly, I'd appreciate your sending a separate
message to [email protected] listing the gaps and other "old"
numbers, so we can avoid assigning those for conflicting purposes.
Regarding the new services on pots 7011 and 7012, to record those I'll need
(via separate email to [email protected]) the service numbers and
other information such as is found in the "AFS Application Services" table
at <http://grand.central.org/numbers/rxservice.html>. You should also
register the UDP port numbers with IANA. Note that these numbers are
already listed in the port-numbers table with other uses.
-- Jeff
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
