RE: "Deprecate"

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 29 August 2013 12:22 UTC

Return-Path: <adrian@olddog.co.uk>
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 78D6221E808F for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 05:22:47 -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=[AWL=-0.000, 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 8paTwtIlQgHg for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 05:22:22 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id D5A6C21E8094 for <ietf@ietf.org>; Thu, 29 Aug 2013 05:22:21 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TCMHAq006872; Thu, 29 Aug 2013 13:22:17 +0100
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [10.12.10.176]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TCMHaI006865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Aug 2013 13:22:17 +0100
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TCMHrL020013; Thu, 29 Aug 2013 13:22:17 +0100
Received: from 950129200 ([50.95.132.233]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TCMEE8019976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 29 Aug 2013 13:22:15 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'t.p.'" <daedulus@btconnect.com>, 'ietf' <ietf@ietf.org>
References: <001301cea4ae$ccde2b60$4001a8c0@gateway.2wire.net>
In-Reply-To: <001301cea4ae$ccde2b60$4001a8c0@gateway.2wire.net>
Subject: RE: "Deprecate"
Date: Thu, 29 Aug 2013 13:22:13 +0100
Message-ID: <071401cea4b2$66250840$326f18c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJgXz2YP9EIHcOzrUDi8tDD5n58r5iIpglg
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 29 Aug 2013 12:22:47 -0000

Tom,

Not a complete answer but look in RFC 4020 (especially 3.3) and
draft-cotton-rfc4020bis (currently in IETF last call).

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t.p.
> Sent: 29 August 2013 12:56
> To: ietf
> Subject: "Deprecate"
> 
> I recently saw 'deprecate' used in an IANA Considerations and turned to
> "IANA Considerations" [RFC5226] to see how it was defined only to find
> no mention of it there.  I am used to the term from SMI, as quoted
> below, but that seems not quite right, in that a deprecated IANA entry
> never disappears, as in
> http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-
> number
> s-5
> 
> Are there other, perhaps better definitions of the term 'deprecated' in
> use outside SMI (and yes, I know about praying nuns!)?
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Fred Baker (fred)" <fred@cisco.com>
> To: "IPv6 Maintanence" <ipv6@ietf.org>
> Sent: Monday, July 29, 2013 3:32 PM
> Subject: "Deprecate"
> 
> 
> > At the mike a moment ago, I referred to an existing formal definition
> of "deprecate". For the record, the reference is to RFC 1158, which
> reads:
> >
> > 3.1.  Deprecated Objects
> >
> >    In order to better prepare implementors for future changes in the
> >    MIB, a new term "deprecated" may be used when describing an object.
> >    A deprecated object in the MIB is one which must be supported, but
> >    one which will most likely be removed from the next version of the
> >    MIB (e.g., MIB-III).
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >