Many said to me before as you do RFC don't change, it is already known
in any org that documents don't change when published. Even author's
drafts in IETF don't change but are updated by new versions or new
names, this is progress of doc process in IETF. The RFCs can be
rewritten and obsolete the old RFC, so no more use of the old one, we
use the new one for progress.
My understanding is that the RFC-ideas and RFC-effects in the
Internet may change. The RFC-document is just a reference, what is
important is its specification usefulness and the reputation to be
used (some RFCs are not used). Therefore, in my point of view the
value of any RFC may change in future, but the number of RFC and
publications never changes,
AB
++
On 2/12/13, joel jaeggli <joelja(_at_)bogus(_dot_)com> wrote:
On 2/11/13 3:32 PM, Abdussalam Baryun wrote:
On 2/12/13, joel jaeggli <joelja(_at_)bogus(_dot_)com> wrote:
Do you mean that IETF is producing what it does not own, or IETF has
no right to edit/amend a document that it is publishing? I
misunderstand your point,
Once an RFC number is issued and the document published, the content of
that RFC never changes.
See RFC 2200 section 2
I agree, but still IETF can update or obsolete any document,
A consensus driven working group process can be used by IETF
participants to produce a new RFC which updates or obsoletes an existing
document. The existing document does not change.
ftp://ftp.ietf.org/rfc/rfc822.txt looks the same as in 1982.
The question ment to be:
Do you mean that IETF is producing what it does not own, or IETF has
no right to edit/amend a document that will be published?
Authors grant rights under the terms of the provisions in force at the
time of publication. Not some unspecified set of rules in the future. So
variously none, 1310, 1602, 2026, 3978, 4748 and the IETF Trust
Licensing Policy.
AB