Re: "Deprecate"
t.p. <daedulus@btconnect.com> Thu, 29 August 2013 15:36 UTC
Return-Path: <daedulus@btconnect.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 9F34221E809F for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 08:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level:
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 cHxI3pfSKUKF for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 08:36:46 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id D933011E8118 for <ietf@ietf.org>; Thu, 29 Aug 2013 08:36:36 -0700 (PDT)
Received: from mail138-ch1-R.bigfish.com (10.43.68.239) by CH1EHSOBE020.bigfish.com (10.43.70.77) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Aug 2013 15:36:28 +0000
Received: from mail138-ch1 (localhost [127.0.0.1]) by mail138-ch1-R.bigfish.com (Postfix) with ESMTP id 27ADD380230; Thu, 29 Aug 2013 15:36:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah186068h1954cbh8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail138-ch1 (localhost.localdomain [127.0.0.1]) by mail138-ch1 (MessageSwitch) id 1377790586694944_2642; Thu, 29 Aug 2013 15:36:26 +0000 (UTC)
Received: from CH1EHSMHS043.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.229]) by mail138-ch1.bigfish.com (Postfix) with ESMTP id 9BFD5220041; Thu, 29 Aug 2013 15:36:26 +0000 (UTC)
Received: from AMSPRD0711HT004.eurprd07.prod.outlook.com (157.56.250.181) by CH1EHSMHS043.bigfish.com (10.43.69.252) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 29 Aug 2013 15:36:25 +0000
Received: from DBXPRD0611HT001.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.242.14.165) with Microsoft SMTP Server (TLS) id 14.16.353.4; Thu, 29 Aug 2013 15:36:23 +0000
Message-ID: <012e01cea4cd$66fb01a0$4001a8c0@gateway.2wire.net>
From: "t.p." <daedulus@btconnect.com>
To: adrian@olddog.co.uk, 'Michelle Cotton' <michelle.cotton@icann.org>, 'ietf' <ietf@ietf.org>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBD0A61@GLKXM0002V.GREENLNK.net> <CE44ADE0.E6DD3%michelle.cotton@icann.org> <077801cea4ca$5ca1cde0$15e569a0$@olddog.co.uk>
Subject: Re: "Deprecate"
Date: Thu, 29 Aug 2013 16:35:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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: Thu, 29 Aug 2013 15:36:56 -0000
---- Original Message ----- From: "Adrian Farrel" <adrian@olddog.co.uk> To: "'Michelle Cotton'" <michelle.cotton@icann.org>; "'Dearlove, Christopher (UK)'" <chris.dearlove@baesystems.com>; "'t.p.'" <daedulus@btconnect.com>; "'ietf'" <ietf@ietf.org> Sent: Thursday, August 29, 2013 4:13 PM Subject: RE: "Deprecate" > That would be great. > > Should 4020bis have a gating normative reference on 5226bis? Tricky; it would mean we are approving 4020bis without knowing what it means, until 5226bis is approved. Tom Petch > > Adrian > > > -----Original Message----- > > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of > > Michelle Cotton > > Sent: 29 August 2013 15:53 > > To: Dearlove, Christopher (UK); t.p.; ietf > > Subject: Re: "Deprecate" > > > > We are working on 5226bis right now and have a plans to discuss the term > > in there. > > > > --Michelle Cotton > > > > Michelle Cotton > > Manager, IANA Services > > ICANN > > > > > > > > On 8/29/13 5:22 AM, "Dearlove, Christopher (UK)" > > <chris.dearlove@baesystems.com> wrote: > > > > >It's definitely an ISO term, I see it used for features of C++. > > > > > >There's then discussion even there of what it means. It is, I think, > > >meant to be used for "we don't think you should use this, there's > > >something better, and this is a warning that it may get removed in a > > >future version". In the case of computer languages there is an additional > > >possibility of "your compiler may emit a warning if you persist in using > > >it". > > > > > >But the only major feature (export) removed in the last C++ version went > > >straight from "part of the standard, but only one compiler ever > > >implemented it, and thus found out it was a bad realisation of an idea" > > >to removed, with no intermediate deprecated stage. And other features > > >just hang around deprecated. So it really doesn't guarantee anything in > > >that instance, neither than if deprecated will go, not if not deprecated > > >won't go. > > > > > >-- > > >Christopher Dearlove > > >Senior Principal Engineer, Communications Group > > >Communications, Networks and Image Analysis Capability > > >BAE Systems Advanced Technology Centre > > >West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK > > >Tel: +44 1245 242194 | Fax: +44 1245 242124 > > >chris.dearlove@baesystems.com | http://www.baesystems.com > > > > > >BAE Systems (Operations) Limited > > >Registered Office: Warwick House, PO Box 87, Farnborough Aerospace > > >Centre, Farnborough, Hants, GU14 6YU, UK > > >Registered in England & Wales No: 1996687 > > > > > > > > >-----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" > > > > > >----------------------! WARNING ! ---------------------- > > >This message originates from outside our organisation, > > >either from an external partner or from the internet. > > >Keep this in mind if you answer this message. > > >Follow the 'Report Suspicious Emails' link on IT matters > > >for instructions on reporting suspicious email messages. > > >-------------------------------------------------------- > > > > > >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 > > >> -------------------------------------------------------------------- > > >> > > > > > > > > > > > >************************************************************* > > ******* > > >This email and any attachments are confidential to the intended > > >recipient and may also be privileged. If you are not the intended > > >recipient please delete it from your system and notify the sender. > > >You should not copy it or use it for any purpose nor disclose or > > >distribute its contents to any other person. > > >************************************************************* > > ******* > > > > >
- "Deprecate" t.p.
- RE: "Deprecate" Adrian Farrel
- RE: "Deprecate" Dearlove, Christopher (UK)
- Re: "Deprecate" Michelle Cotton
- RE: "Deprecate" Adrian Farrel
- Re: "Deprecate" t.p.
- RE: "Deprecate" Dearlove, Christopher (UK)
- Re: "Deprecate" t.p.