Re: IETF RFCs

----- "paola dimaio" <paola.dimaio@gmail.com> wrote:
> unless someone has objection on placing efforts towards some level of
> compliance with IETF RFC's  (so far we have two people in favour)
> 
> and since you seem familiar with it, would you give us some input
> on how to go about it?

Well, there's a standard 'standards-track' procedure for actually creating
an RFC standard, which can be found under Publication Process at 

   http://rfc-editor.org/

Style Guide is probably also useful.

But the most important issue is mindset: RFCs are commonly created by and
for implementors: they're tight enough specs that a prospective implementor
has a decent hope of sitting down the just the RFC, and turning out code
that will work in the Real World.

More is here:

  http://rfc-editor.org/rfcfaq.html

and it can be helpful to read a few RFCs, to get a feel for things.

RFC 2822 specifies Internet email, RFC 1036 Usenet messages, RFCs 2045&6
the MIME encapsulation format, etc...

Exactly how this mindset would apply best to EIIFs work, I'm not yet entirely
sure since, embarrassingly enough, I *still* haven't read the draft.

Happily, I have a few hours free this afternoon.  :-)

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra@baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274

             Those who cast the vote decide nothing.
             Those who count the vote decide everything.
               -- (Josef Stalin)