IETF Logo Mail Archive

Re: The RFC Acknowledgement

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 11 February 2013 23:32 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D68C021F8A99 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 15:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.537
X-Spam-Level:
X-Spam-Status: No, score=-3.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPXyVKWhe8w0 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 15:32:19 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 457FA21F8A61 for <ietf@ietf.org>; Mon, 11 Feb 2013 15:32:18 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id ez12so3785106wid.11 for <ietf@ietf.org>; Mon, 11 Feb 2013 15:32:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dddpy+MM0SoHMILrW1VSi++71JNSw0/4b0caAFOcpY0=; b=PJu/N6HnBNZ7XJef3tObrCM1Wx1oAbhm4lnmu2xcEwsw+75eZvoSuby9B3hsbodxQQ iiuQayAWzedPz56YmkiVCfBRZMQgBswJFuVKcqKcqY0aPMWYJUBZHgxtEyZCXX6TuWij 9Wd6KEMC2AWrRPvoLAloA2vj/Sqt/1RmHlUq55jRLBMqbeDSislEyIY9M1qFo9ggZg3l 5lP0PVkXYEs99GyYlRTS38Pahb7jmyxR0VbFtp5ym+cO4qOHvZD4h12VOueBTYrC4H9i 9KfFlqvhG8wfEerhZeAE6lWP7Pzzhl/OYzB70rvFSHAuuCZBEFAUVpVtdOsvuGk44a4N vOpQ==
MIME-Version: 1.0
X-Received: by 10.180.83.10 with SMTP id m10mr19079678wiy.5.1360625537392; Mon, 11 Feb 2013 15:32:17 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Mon, 11 Feb 2013 15:32:17 -0800 (PST)
In-Reply-To: <511978DD.8000804@bogus.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CADnDZ88eH+uYCP7+qnYQ_Tiq=W7xpq1SrB-TzZ-z0tFO=xvySA@mail.gmail.com> <511978DD.8000804@bogus.com>
Date: Tue, 12 Feb 2013 00:32:17 +0100
Message-ID: <CADnDZ8-9M_ye1Q7xi=ZjSkj3XNm9eOxviCn-=GJTNW8ZHZs=nQ@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 23:32:20 -0000

On 2/12/13, joel jaeggli <joelja@bogus.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,

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?

AB

v2.23.0 | Report a Bug | By Email