The problem is Brian - that there is this underlying assumption with the
entire IETF service model that says that people are responsible for
maintaining their own alignment with IETF standards - and so at some point
they decide they have spent enough and they stop spending to participate.
Personally its an amazingly arrogant assumption that the world is going to
continue paying the IETF, whether through the donation of engineering
services to the WG's or by subsidizing attendance and/or a standards program
initiative or their freezing a product at some level which stops tracking
new IETF changes. Either way for innovation and tracking its new standards
as such this is the problem, and believing that the current model does not
need wholesale change documents how naive the IETF management model is IMHO.
If there was a Copyright Issue such that people were forced to stay in
compliance with the IETF then this would not be an issue. At least at the
Standards Tracking levels; but this is the point behind Brand Control - and
you folks have lost it.
It (Brand Control for the IETF) is not hiding - its standing right in front
of you too - all you have to do is take control of the Copyright, work out
some better process for sharing and interacting with the ITU, ANSI, ETSI and
a couple of others like WIPO, and create some simple method of versioning
that is tied to the copyrights.
----- Original Message -----
From: "Brian E Carpenter" <brc(_at_)zurich(_dot_)ibm(_dot_)com>
To: "Eliot Lear" <lear(_at_)cisco(_dot_)com>
Cc: "Paul E. Jones" <paulej(_at_)packetizer(_dot_)com>;
<dcrocker(_at_)bbiw(_dot_)net>;
<ietf(_at_)ietf(_dot_)org>
Sent: Sunday, August 13, 2006 11:56 PM
Subject: Re: RFC 4612 - historic status
Eliot Lear wrote:
Paul E. Jones wrote:
I wonder how customers might react to seeing new gateway hardware
produced
utilizing "historic" RFCs. What does that mean?
It means that one standards body has decided to cite a specification
that has been deprecated by another.
It would have been better, imho, if ITU had decided to cite the
non-deprecated
image/* MIME types, but that is not a decision the IETF can control.
Brian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf