pem-dev
[Top] [All Lists]

Re: why is MOSS not yet an RFC?

1995-09-21 10:54:00
The IESG's Protocol Action announcement for MOSS and security multiparts is 
now
2-1/2 months old, and yet neither of these documents has been published as an
RFC.  It hasn't taken nearly this long for other recent standards, I think.

Incorrect. The process is in fact quite variable in length. I've seen documents
take anywhere from a week to eight months, and different documents can take
very different amounts of time even during the same period. If memory serves
the editorial process for MIME took something on the order of four months. The
SMTP extensions, on the other hand, took only a couple of weeks. Same document
area, lots of authors in common, roughly the same period in time, etc. Mac-MIME
took a LONG time -- eight months or so. Go figure.

I'm not a mind reader, but it seems obvious from inspection that one of the
things the RFC Editors does is group similar standards together. I suspect,
without the slightest shred of proof mind you, that the RFC Editor is putting
together a group of either security or email-related standards to come out in
one batch.

Does anyone know what the problem is?  I'd hate to think that it has anything 
to
do with this S/MIME business ...

I doubt that it has anything to do with S/MIME. The RFC Editors brief is
an editorial one, not a technical one. And if there had been an editorial
problem I suspect the authors would have been contact by now...

                                Ned 

<Prev in Thread] Current Thread [Next in Thread>