On 7/21/2011 2:50 AM, Mykyta Yevstifeyev wrote:
21.07.2011 8:20, Simon Wilkinson wrote
On 21 Jul 2011, at 06:00, Mykyta Yevstifeyev<[email protected]> wrote:
Reading this draft, I don't actually understand why you chose to publish it as
RFC.
We're using the Independent Submissions stream for afs3 documents. See RFC4846
for details of this stream, and it's purpose.
I've read RFC 4846 and have noticed you're using Independent Submissions
stream. Probably, the draft should be clearer regarding relationships with
currently deployed Internet protocols/technologies,
since your document "at the first glance" seems to be a bit irrelevant for the
RFC series. The counter conclusion may only be made by people who are involved in the AFS
development and other
contiguous technologies (whom I don't belong to), which makes the document not
as readable as desired. A good background placed in the Introduction is a good
way to resolve the issue.
Mykyta
The attempt to implement standards for the AFS protocols has been a mult-year
endeavor,
with discussions with the IETF and IESG and independent submission has been the
recommendation.
But as people come and go the same discussions are repeated, so progress has
been slow.
Following is a note sent to the editor on March 18, that may give you some
better insight
as to what we are trying to do. You can also find responses from the editor in
the
[email protected] archives. May 2011.
We now have one document up for review by the RFC editor as an independent
submission.
We expect that there will be some boiler plate text added to this document by
the editor,
and we will add it to the others.
-------- Original Message --------
Subject: [AFS3-std] AFS3 Standardization and Independent Submissions
Date: Fri, 18 Mar 2011 09:38:12 -0500
From: Douglas E. Engert <[email protected]>
To: [email protected], [email protected]
CC: Hartmut Reuter <[email protected]>
As you may have seen, there has been a group formed of developers, to
standardize
the AFS protocols. As one of the co-chairs, I am writing to you to get your
options on our process and how these drafts can be moved forward as Independent
Submissions.
A history of AFS can be found at: http://openafs.org
A number of independent interoperable implementations of AFS have been developed
over the years and for a number of reasons, using the IETF Independent
Submissions
track has been deemed to be the way to go.
The foundations of the process and the group can be found in:
http://www.ietf.org/id/draft-wilkinson-afs3-standardisation-01.txt
Many of the members of the group are current or former IETF WG chairs and
are familiar with the general IETF submission process, but not with the
Independent Submissions. So I am contacting you, the IS editor, to get
you option on the process and if we are doing what would be expected.
All of the drafts have -afs3- in the name.
This first draft has been submitted as Informational and has passed a last
call on the mailing list:
http://www.ietf.org/id/draft-brashear-afs3-pts-extended-names-09.txt
These have been submitted but and are being considered by the group:
http://www.ietf.org/id/draft-deason-afs3-getsizev2-02.txt
http://www.ietf.org/id/draft-deason-afs3-type-time-00.txt
http://www.ietf.org/id/draft-keiser-afs3-xdr-union-00.txt
http://www.ietf.org/id/draft-tkeiser-afs3-volser-tlv-04.txt
http://www.ietf.org/id/draft-wilkinson-afs3-bos-identities-00.txt
Our group is based on:
http://www.ietf.org/id/draft-wilkinson-afs3-standardisation-01.txt
So we would like to know if these look acceptable as Independent
Submissions and what we should be doing with the first one of these,
draft-brashear-afs3-pts-extended-names-09.
Thanks.
_______________________________________________
AFS3-standardization mailing list
[email protected]
http://lists.openafs.org/mailman/listinfo/afs3-standardization
--
Douglas E. Engert <[email protected]>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
_______________________________________________
AFS3-standardization mailing list
[email protected]
http://lists.openafs.org/mailman/listinfo/afs3-standardization
