-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, all,
Nicolas Williams wrote:
> On Fri, Jan 15, 2010 at 10:51:39AM -0600, Wesley Leggette wrote:
>>>> When we are ready to submit something (it would be a submission which
>>>> documents what we have currently implemented) is there a working group that
>>>> would be appropriate, or should we just submit an I-D directly?
>>> It's always easiest to submit an individual I-D first, then see where to
>>> place it, AFAICT.
>> Then we will do that for now, taking into account your other suggestions.
>
> The process roughly goes like this:
>
> - Submit some individual submission Internet-Drafts (e.g.,
> draft-leggette-my-distributed-storage-protocol-00).
- - figure out whether that doc should be handled in an existing WG
- this can happen by review, or by making a brief presentation
on one of the area meetings at the next IETF
BoFs can be useful if the result suggests significant effort is needed
(new WG or substantial recharter of existing WG), but this intermediate
step is useful in getting feedback.
Joe
>
> - Request a BoF meeting at the next IETF meeting.
>
> The goal of the BoF should be to determine IETF interest in your
> proposals. Possible outcomes of a BoF include:
>
> - a second BoF is needed;
>
> - there's no interest in chartering a WG or re-chartering an
> existing one; you will be able to try again once more, and you
> will still be able to proceed with the individual submission
> track;
>
> (There's the possibility in this case that the IESG will
> ultimately oppose standards-track publication, in which case
> you'll end up with informational or experimental RFCs, or perhaps
> you'd abandon the effort.)
>
> - a WG will be chartered to host the work;
>
> - an existing WG will be re-chartered to host the work.
>
> It will help to have an introductory I-D. Do disclose mind IPR
> dislosure rules. Do familiarize yourself with the IETF standards
> process.
>
> Nico
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAktRWMoACgkQE5f5cImnZrtB3gCfY44D5CkxSEzMMmsPPus19DSe
X7UAn2Xx3RYzeJ6PqP5M0WO3GQ3mSrYj
=IB/u
-----END PGP SIGNATURE-----
