On Tue, Aug 28, 2012 at 08:19:08PM +0200, "\"Martin v. L?wis\""
<mar...@v.loewis.de> wrote:
> Am 28.08.12 19:15, schrieb Oleg Broytman:
> >> The RFC database itself has expiration dates on specifications,
> >> namely on I-D documents (internet drafts). The expire 6 months
> >> after their initial publication, unless renewed.
> >
> > Does that expiration mean something?
>
> It's explained in RFC 2026. An internet draft is not an internet
> standard, it may get changed at any time. An I-D which is expired
> and still used has the same relevance as a proprietary standard;
> it has nothing to do with the internet standards process.
>
> Whether this has any practical consequence depends on the market,
> of course. Customers that insist on standards compliance will look
> for RFC compliance, but typically not for I-D compliance. If the
> field of standardization is of relevance for such users, they will
> eventually ask for an RFC to be issued, which then may or may not
> be compatible with a long-standing proprietary standard.
I see. Thank you!
Oleg.
--
Oleg Broytman http://phdru.name/ p...@phdru.name
Programmers don't die, they just GOSUB without RETURN.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
