-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jeff,
Jeffrey Hutzelman wrote: | I think at this point that we've had sufficient discussion that it is | appropriate to begin putting together a concrete, self-contained | proposal which does not depend on prior mail or other conversations. I am writing such a document. My current draft has a bunch of motivation for doing all this in the first place, but if it's not viewed as important (perhaps because there's consensus there), I can just send the rest, which resembles an IETF RFC, as requested. I will re-review RFC 2119. I have been trying to get point feedback so what is proposed in the draft reflects intuitions of people I know have ideas and usually share them--not short circuit the opportunity for others to comment. My document is far along. Given this feedback, I guess there is no harm in just sending my intuitions and letting the discussion proceed from there. | | ----- | | Now, I'll go ahead and add a couple of my own comments on the approaches | I see being described, which you may want to take into account when | preparing your draft. Your feedback is helpful. Matt - -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIIJ3EJiSUUSaRdSURCOhLAJ0YwRu9/Ol/P1efWv+VdAZ3/wyUkACePbfu 09bg4uyl0JQkMfdKdCqI18A= =3lZ7 -----END PGP SIGNATURE----- _______________________________________________ AFS3-standardization mailing list [email protected] http://michigan-openafs-lists.central.org/mailman/listinfo/afs3-standardization
