[OpenAFS-devel] IPv6 Status

Tue, 28 Feb 2012 11:57:00 -0500

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
    <title></title>
  </head>
  <body bgcolor=3D"#ffffff" text=3D"#000000">
    The proper forum for discussing protocol changes is
    <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:afs3-standardiza=
tion@openafs.org">afs3-standardization@openafs.org</a>.=C2=A0=C2=A0=C2=A0=
 OpenAFS cannot accept or deploy
    any protocol changes that have not been approved by that group.<br>
    <br>
    Additional responses inline....<br>
    <br>
    On 2/28/2012 11:22 AM, Troy Benjegerdes wrote:
    <blockquote cite=3D"mid:20120228162213.GG8686@excalibur.hozed.org"
      type=3D"cite">
      <pre wrap=3D"">If this is *not* a huge concern for the AFS communit=
y, then we might
as well all start working on AFS to Dropbop migration plans.
</pre>
    </blockquote>
    Concern does not equal resource availability and Dropbox is not an
    alternative to AFS.=C2=A0 If you have the money to pay Dropbox, then =
you
    should start writing checks today to someone in the AFS community to
    move the things you want forward.<br>
    <br>
    <blockquote cite=3D"mid:20120228162213.GG8686@excalibur.hozed.org"
      type=3D"cite">
      <pre wrap=3D"">If someone is sitting on a pile of code, or even a c=
ontract to do=20
some IPv6 work, it would be nice to make a public timeline of when
it will be available.
</pre>
    </blockquote>
    <br>
    Your File System committed to implement IPv6 as part of the DoE
    grant but as with much of the work, the money didn't complete as
    much of the work as was hoped.=C2=A0 The primary cause was that we fo=
und
    that somewhere between 35% and 50% of our time was spent fixing
    issues that were introduced into the OpenAFS code tree.=C2=A0=C2=A0 I=
t was
    impossible to develop substantial systems on a moving target with
    the limited resources available to us.<br>
    <br>
    Your File System still wants to implement IPv6 and give it to the
    OpenAFS community but there is at present no funding for that work
    and our internal priorities are elsewhere.<br>
    <br>
    <blockquote cite=3D"mid:20120228162213.GG8686@excalibur.hozed.org"
      type=3D"cite">
      <pre wrap=3D"">
It's not going to help the community any if three different implementatio=
ns
magically appear in December 2012 that haven't been tested outside of the=

site that's been developing them.
</pre>
    </blockquote>
    <br>
    That is unlikely to happen.=C2=A0 RPCs need to be allocated by the
    registrars and OpenAFS will not accept code that is not standardized
    by afs3-standardization.=C2=A0 Organizations could develop the work
    internally and not tell anyone about it but then they are not part
    of this community.<br>
    <br>
    <blockquote cite=3D"mid:20120228162213.GG8686@excalibur.hozed.org"
      type=3D"cite">
      <pre wrap=3D"">
If nothing else, can we at least get all the RPCs and APIs changes
defined and documented?
</pre>
    </blockquote>
    <br>
    Doing so is 80% of the work.<br>
    <br>
    <br>
  </body>
</html>


--------------enig052473F3DBDFCA9058A6FBAB
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)

iQEcBAEBAgAGBQJPTQdeAAoJENxm1CNJffh48u0H/1hzoZCYFVghZ/P8A0Sba3ay
prbGLiIUtH6blEGmwXtaPPpwup4d7ni7q1guLT/PyxIIK+70/DflSEPdtghu83Oj
fVRKJaSTAwEK83IgTf4//JEx5F2vU8kcCFSGKYpBsStNDknPcXF0x7Mm4ZMjmxmE
cXJl61ag2Bi5CuAD2qYqCBDxtRw1u31FapeKDa5KxznHumUhvvzBbyX2YikobO+a
ujR2AVudOTM6W5PwxNfVEj1yQqS5PoTZfQuQHMzwucWx++uiQ8AVju2ac5WE3tXi
ik1Sll8cAA5W/fJHvMT7IWPapa7oWjr/iJ83p6GK7TM5NbehXkiTDX4/oEoQ/QY=
=L+BB
-----END PGP SIGNATURE-----

--------------enig052473F3DBDFCA9058A6FBAB--