[OpenAFS-devel] Re: IPv6 strawman plan: Re: Moving Forwards

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1A9C66855F1B3E44956ABFAE
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 9/10/2012 11:36 AM, Andrew Deason wrote:
> On Mon, 10 Sep 2012 01:19:40 -0400
> Jeffrey Altman <jaltman@your-file-system.com> wrote:
>=20
>> 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.
>=20
> 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.




--------------enig1A9C66855F1B3E44956ABFAE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJQTgzBAAoJENxm1CNJffh4uNUIAIfvN3k+4K6rJXmoIBKeJvah
uVbLvKPFknqz8vnke+faNWYxOK50Z7VEn7kaQz9yNUs3anoz4yVBAww11L060uCl
KCnc+7/HsP4IbMjQZgF6Htnkym0HaZYtZ1WOb2gQzvsfiqSfDIzLdg714FxNYaaz
FAJFyuYzAtdxOs8ayw85jRihPAfoqkmQMeL8zXSQ0CeyLsTuO910Op4dMTyE1ovh
cjhadEHGmFUMGdBxzagc0ZgbsjRjlKL9Evuudy2kIUHYDh61Q+v2fAp3NOg/6nZL
lZ+Q44Shhj1WVYmV0yv+N/64ugdlo77rTNKmLse9MO3X1K7J1Pio5cc2gGY+ngE=
=Kvq/
-----END PGP SIGNATURE-----

--------------enig1A9C66855F1B3E44956ABFAE--