IETF Logo Mail Archive

"Updates: RFC xxx" - what does it actually mean ?

Flemming Andreasen <fandreas@cisco.com> Mon, 29 August 2016 19:22 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07E4E12D825 for <wgchairs@ietfa.amsl.com>; Mon, 29 Aug 2016 12:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level:
X-Spam-Status: No, score=-15.069 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Qg6jZDxEvEz for <wgchairs@ietfa.amsl.com>; Mon, 29 Aug 2016 12:22:26 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8A8812D82B for <wgchairs@ietf.org>; Mon, 29 Aug 2016 12:22:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=375; q=dns/txt; s=iport; t=1472498545; x=1473708145; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=L49/4zhUGzs8dNAxEJc43DHZc2WzMLmVVB/cPFbr/pc=; b=haF71jObSgZ/BVutw+f0SHg+apL4IEfOP00QR0F9519IY1knmAJ1NSDN DI/AvvIyFZl30nfGp/VschT7tg1Wdnqi9os+hHRZlZzZPFSyzM5U2/Wqh inN/3o1IF57Vky2zcz4iMyQDC0XEfJ7c7tqpLocnl+TNhe5Ztzyh/GR9C g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CoBADyisRX/5hdJa1cGgEBAQECAQEBAYMpAQEBAQEegQGxSYRUhGOHejwQAQIBAQEBAQEBXhwLhQsVdgImAl8NCAEBiDyeXI9lj0kBAQEHAiWBA4UrgXiKF4JaAQSZT4khggmDJF2BVwGIA4V6kD01H4Q4IIcAAQEB
X-IronPort-AV: E=Sophos;i="5.30,252,1470700800"; d="scan'208";a="316692729"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Aug 2016 19:22:25 +0000
Received: from [10.98.149.203] (bxb-fandreas-88110.cisco.com [10.98.149.203]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u7TJMOn7012769 for <wgchairs@ietf.org>; Mon, 29 Aug 2016 19:22:24 GMT
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
From: Flemming Andreasen <fandreas@cisco.com>
Subject: "Updates: RFC xxx" - what does it actually mean ?
Message-ID: <f552a1b8-33ea-db70-ba3a-17b0009cadcc@cisco.com>
Date: Mon, 29 Aug 2016 15:22:24 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/7MPUBoUGo_1Bcr1EhwNHdf2RGV8>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 19:22:31 -0000

Greetings

Let's say I have "RFC X", and I then publish "RFC Y", which includes 
"Updates: RFC X" on its title page.

1) In order for me to be compliant with RFC X, MUST I now also be 
compliant with RFC Y ?

2) If yes, what if RFC Y introduced a non-backwards compatible change to 
RFC X ?

3) Is the answer to 1) documented somewhere ?

Thanks

-- Flemming

v2.23.0 | Report a Bug | By Email