IETF Logo Mail Archive

Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice

"HANSEN, TONY L" <tony@att.com> Mon, 06 June 2016 10:18 UTC

Return-Path: <tony@att.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 82E5512D5B9 for <ietf@ietfa.amsl.com>; Mon, 6 Jun 2016 03:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.58
X-Spam-Level:
X-Spam-Status: No, score=-1.58 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no autolearn_force=no
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 cd1MuRebxqAi for <ietf@ietfa.amsl.com>; Mon, 6 Jun 2016 03:18:54 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B849A12B022 for <ietf@ietf.org>; Mon, 6 Jun 2016 03:18:54 -0700 (PDT)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u56AELcj039789 for <ietf@ietf.org>; Mon, 6 Jun 2016 06:18:54 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by mx0a-00191d01.pphosted.com with ESMTP id 23d4970q68-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 06 Jun 2016 06:18:54 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u56AIr7Y021285 for <ietf@ietf.org>; Mon, 6 Jun 2016 06:18:53 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u56AIo6u021245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Mon, 6 Jun 2016 06:18:51 -0400
Received: from MISOUT7MSGHUBAB.ITServices.sbc.com (MISOUT7MSGHUBAB.itservices.sbc.com [130.9.129.146]) by mlpi409.sfdc.sbc.com (RSA Interceptor) for <ietf@ietf.org>; Mon, 6 Jun 2016 10:18:45 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.125]) by MISOUT7MSGHUBAB.ITServices.sbc.com ([130.9.129.146]) with mapi id 14.03.0294.000; Mon, 6 Jun 2016 06:18:45 -0400
From: "HANSEN, TONY L" <tony@att.com>
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
Thread-Topic: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
Thread-Index: AQHRvcgWzK3cXInOa0yDaJhN6H/zK5/YXmQAgAAKooCAABGLgIAALgYAgAAKuACAATX2AIABsk+AgAAJKICAAJlSAA==
Date: Mon, 06 Jun 2016 10:18:44 +0000
Message-ID: <469534D3-00B3-4295-B710-4B88B04D18A1@att.com>
References: <20160419141640.31545.54742.idtracker@ietfa.amsl.com> <575185A2.70908@cs.tcd.ie> <EDA3CD0D-BDCA-4AC6-AA67-318670080338@sobco.com> <CAC4RtVBngkPc-yQ8P0qyvwsG9L4qjDMDPZ5xwa4gR84=ov4iUg@mail.gmail.com> <CAF4+nEHzvVOq_1L2ukX-OcPGkVFgR2OOD5puLMBJGif3a=Hzaw@mail.gmail.com> <CAC4RtVC6sKnYQS3mOay8-rSLQ0+U5mYGVhBbSSD=0xNX6dt2ng@mail.gmail.com> <5751D5E8.6030803@cs.tcd.ie> <CALaySJ+3jorRopPKNHjy19fo1v1=dZEHarMJ1-gB89vNbkFxaw@mail.gmail.com> <5751ED8B.4020508@isi.edu> <9b7a1b04-f767-517a-bd84-28c030695dfc@gmail.com> <57521D24.40700@cs.tcd.ie> <CAC4RtVBMA42Ke_m6ked9GtUTdGSdg-Jjxp5ibiWBDdG+p2y-2w@mail.gmail.com> <57548D7B.5020702@isi.edu> <CALaySJL_aUv751Z9xdSWib4vbnqK-ymzg7gLWqk8+Q1uo_MYRA@mail.gmail.com>
In-Reply-To: <CALaySJL_aUv751Z9xdSWib4vbnqK-ymzg7gLWqk8+Q1uo_MYRA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.110.240.243]
Content-Type: text/plain; charset="utf-8"
Content-ID: <830191D729D23D45B0C241DF21EEBC94@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-06-06_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1606060125
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M251_RhOfDkzbE_rtrb9_StxFt4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 06 Jun 2016 10:18:55 -0000

On 6/5/16, 5:10 PM, "ietf on behalf of Barry Leiba" <ietf-bounces@ietf.org on behalf of barryleiba@computer.org> wrote:
>
>Yes, as you say (and as I say), the point is to do what's right.  I
>contend that in most cases, the right thing is to update the reference
>*when we produce a more current reference*.  If we have not done that,
>then we should not do that.
>
>And also as you say (and as I say), we always want to leave
>flexibility to use our heads and do the right thing.  That's why I'm
>very happy to move away from the "in no case" phrase, to something
>such as "in most cases."  I pretty much *always* want to allow people
>to make sensible judgments, and not to stand behind firm, inflexible
>rules.

Phwew!

I think there is consensus on this: The authors are expected to do the right thing. In most cases, but not all, the right thing to do is to update a reference when the previous reference is obsoleted. One size does not fit all.

Barry, do you have updated text to capture the outcome of this long thread?

	Tony Hansen

v2.23.0 | Report a Bug | By Email