IETF Logo Mail Archive

Re: [Rfced-future] Sectiion 4.3 on RPC Responsibilities (was: Re: Fwd: [I18ndir] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11_

"Salz, Rich" <rsalz@akamai.com> Tue, 08 March 2022 11:59 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C0C83A12DE for <rfced-future@ietfa.amsl.com>; Tue, 8 Mar 2022 03:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 SucJbDhKYMS2 for <rfced-future@ietfa.amsl.com>; Tue, 8 Mar 2022 03:59:44 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 244453A12DA for <rfced-future@iab.org>; Tue, 8 Mar 2022 03:59:43 -0800 (PST)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.1.2/8.16.1.2) with ESMTP id 228BmOLs006636; Tue, 8 Mar 2022 11:59:42 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=+qyTdtwBUdiQiXdoR9skoIlnYUjtZynhvktbdRyT0go=; b=UEom+vNhBD+r4aNwZsBCOpXNzaSb4TGGs8b91d8fV3e8J+jBJCRlZwaVfPPLphJeDuWs 5VKMrOfr+ByYq0GJFfy8brxsF+RR5uPQFRreGe4HFA7YLHCiyZ/ksALKoLe1iXgj02NI RSLZnXR3hhI7mkx/P2+Rj9FA0bT+xqaBdkOs4s6CzoVi4FjrMa7knKUwj7OOZ2lQxPPb RcY4QK+oKI0djhrSjxiln9mvTUaKiadsaos49b7scXjkJI/PMFUn5Zd9m1eXML1KFDry 6Y4NR2HbKBNOq/MZgUqaIOFZhKxtmIcMA/TLhtqQT8HipjxmUXQ6Ybe0BRQiZBp8U3zl 1w==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by mx0b-00190b01.pphosted.com (PPS) with ESMTPS id 3enqenct7p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 08 Mar 2022 11:59:41 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 228Bnc97030018; Tue, 8 Mar 2022 06:59:41 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint2.akamai.com with ESMTP id 3em4335bg9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 08 Mar 2022 06:59:41 -0500
Received: from USTX2EX-DAG1MB2.msg.corp.akamai.com (172.27.165.120) by usma1ex-dag4mb7.msg.corp.akamai.com (172.27.91.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.922.20; Tue, 8 Mar 2022 06:59:40 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.165.120) with Microsoft SMTP Server (TLS) id 15.0.1497.28; Tue, 8 Mar 2022 05:59:39 -0600
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.028; Tue, 8 Mar 2022 05:59:39 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
CC: "rfced-future@iab.org" <rfced-future@iab.org>
Thread-Topic: [Rfced-future] Sectiion 4.3 on RPC Responsibilities (was: Re: Fwd: [I18ndir] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11_
Thread-Index: AQHYLewB/q34Y69CgkKqjBmsx1mWqKyuCpoAgACJc4CAAFRiAIAAEzaAgAAD/QCAAU6lAIAABkGAgARn/ACAAE2SAIAAIlCAgABQfgA=
Date: Tue, 08 Mar 2022 11:59:39 +0000
Message-ID: <57E5B2BF-2FC0-4D2B-B71C-6D6E92F310FB@akamai.com>
References: <0DD984849353AF88D72E54B7@PSB> <7fd23143-dd24-295b-2912-32abc6e89579@lear.ch> <1CF8B6A11A07D3178C873256@PSB> <2dbdc67c-18a8-8c21-9f2b-7a8dc37d9860@stpeter.im> <2292F272F651D2E9C53B9075@PSB> <e9313719-8da1-ea05-b8d7-98485310d6b2@gmail.com> <a38e1bdf-36f1-79ea-cf37-8451cac0958f@stpeter.im> <7a2be7af-0cdf-6a30-985b-ba4f4bf24691@gmail.com> <F559CBFE-80A2-40C1-83A9-C93A7B9B8141@ietf.org> <ad01caaa-ad20-2287-389d-01ca4668cf8d@it.aoyama.ac.jp> <5a5d1dfb-3f89-17c2-5e87-ccc76ed19fbe@stpeter.im>
In-Reply-To: <5a5d1dfb-3f89-17c2-5e87-ccc76ed19fbe@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.58.22021501
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8E0EF9D37C58B245ACA1B3D5F296E122@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-03-08_03:2022-03-03, 2022-03-08 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 mlxscore=0 spamscore=0 bulkscore=0 mlxlogscore=886 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2203080062
X-Proofpoint-ORIG-GUID: qtJ7RdsAjr9gNt0ZV5RfaqgyytcHL7AY
X-Proofpoint-GUID: qtJ7RdsAjr9gNt0ZV5RfaqgyytcHL7AY
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.816,Hydra:6.0.425,FMLib:17.11.64.514 definitions=2022-03-08_03,2022-03-04_01,2022-02-23_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 mlxscore=0 bulkscore=0 priorityscore=1501 lowpriorityscore=0 phishscore=0 mlxlogscore=858 malwarescore=0 clxscore=1011 suspectscore=0 spamscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2203080063
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/MVCCAf4xbvd2KQkZYGxlKYGyH00>
Subject: Re: [Rfced-future] Sectiion 4.3 on RPC Responsibilities (was: Re: Fwd: [I18ndir] I18ndir last call review of draft-iab-rfcefdp-rfced-model-11_
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2022 11:59:49 -0000

>    I'm not a big fan of saying "or its successor" everywhere because the 
    point of specifying that a new RFC updates or obsoletes an old RFC is 
    that the reader should be able to follow the trail and find the new one.

Strongly agree.

Otherwise we could (and by this reasoning, should) add "or its successor" to almost every cross-reference.

v2.23.0 | Report a Bug | By Email