IETF Logo Mail Archive

RE: New Version Notification for: draft-baryun-rfc2119-update-00.txt

"Adrian Farrel" <afarrel@juniper.net> Thu, 02 August 2012 15:38 UTC

Return-Path: <afarrel@juniper.net>
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 3809521F869F for <ietf@ietfa.amsl.com>; Thu, 2 Aug 2012 08:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wv5XkiE1nHk for <ietf@ietfa.amsl.com>; Thu, 2 Aug 2012 08:38:56 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 7704621F869E for <ietf@ietf.org>; Thu, 2 Aug 2012 08:38:56 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q72Fcnrv031773; Thu, 2 Aug 2012 16:38:49 +0100
Received: from 950129200 (dhcp-3167.meeting.ietf.org [130.129.49.103]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q72Fcgfb031696 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Aug 2012 16:38:45 +0100
From: Adrian Farrel <afarrel@juniper.net>
To: 'joel jaeggli' <joelja@bogus.com>, 'Scott Brim' <scott.brim@gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com> <501A8B5B.2070609@bogus.com>
In-Reply-To: <501A8B5B.2070609@bogus.com>
Subject: RE: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Date: Thu, 02 Aug 2012 16:38:40 +0100
Message-ID: <011201cd70c4$e81abde0$b85039a0$@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLw+3MjyVCsgx/3v7ilGpHvBIxheAJ4IDYAAngh6QwBuKimbQKXHalqlLWRm9A=
Content-Language: en-gb
X-Mailman-Approved-At: Fri, 03 Aug 2012 08:48:43 -0700
Cc: 'Barry Leiba' <barryleiba@computer.org>, 'ietf' <ietf@ietf.org>, 'Abdussalam Baryun' <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: afarrel@juniper.net
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: Thu, 02 Aug 2012 15:38:57 -0000

> A Change to the interpretation of normative language does not
> retroactively apply to existing documents.

Shucks! Really?

I was hoping I could automatically change the behavior of deployed routers by
updating the meaning of some words in published RFCs. You mean I can't do that?

A

v2.23.0 | Report a Bug | By Email