IETF Logo Mail Archive

Re: [rfc-i] ****SPAM**** Re: 3rd party SDO cross-referencing of IETF work (was: Re: Chair/datatracker tracking expired WG documents ?)

"Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org> Fri, 25 March 2022 12:22 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A6403A128E for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 25 Mar 2022 05:22:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1648210952; bh=HmKvqkICAaGaVUAXnyMN9eEneUqdlDrVxGYo06r9sl0=; h=To:Date:References:In-Reply-To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:Cc:From; b=GRMp7wiDpL5jaQrZzRrcK1g/5EImgF0XxPdPJpO4ImfK8LCsRDddpcVY+NNkRs9Os C7iFXbTxUZlbM3DH8MRQofIKO8NSP3+aI6mRMFf7DGj4izLleXeIj/ObcfZNDPDRVy fwVdrKWczmwaLIcJlHi+oqTjWgeI9/tpd2TzrV+8=
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C103A1241; Fri, 25 Mar 2022 05:22:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1648210948; bh=HmKvqkICAaGaVUAXnyMN9eEneUqdlDrVxGYo06r9sl0=; h=From:To:Date:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc; b=zJMXn6HiYJkQDOE0oJBRCmXKUQoJY1zSi6uQgVvFGOuWMJE3rC8gcc8A54lo1tBHO EXz0xLQ9I+/ip2TvlfntXZiNzRAEUFv+UjWCIWPVeC+Bm7cuqw0Pp+sFrPqAUOSWFB k7pP/IIFNCmp0xatY0yKdF6JZKPW0Zci+nxOVqaE=
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 685753A123E for <rfc-interest@ietfa.amsl.com>; Fri, 25 Mar 2022 05:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.109 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_HI=-5, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Hh4O5p3y1U4k for <rfc-interest@ietfa.amsl.com>; Fri, 25 Mar 2022 05:22:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C83583A1068 for <rfc-interest@ietfa.amsl.com>; Fri, 25 Mar 2022 05:22:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix) id 566A020EB46; Fri, 25 Mar 2022 05:22:11 -0700 (PDT)
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 558DC15EE85 for <rfc-interest@rfc-editor.org>; Fri, 25 Mar 2022 05:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDPGziTTqa1m for <rfc-interest@rfc-editor.org>; Fri, 25 Mar 2022 05:22:07 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) by rfc-editor.org (Postfix) with ESMTPS id BA3813BAA5 for <rfc-interest@rfc-editor.org>; Fri, 25 Mar 2022 05:22:07 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.1.2/8.16.1.2) with ESMTP id 22PBMjUl007701; Fri, 25 Mar 2022 12:21:46 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=ffPMIAKMcDh27B4e6SbmdqVktuds8+7Xa2UiNLuuWYA=; b=nJPDrYZmtcEcDGewns05QFhZHKk9MpXxX/0TLEpxDzybd3XG7NKi0Dqfq9tEMoJbl1Up VP5R78miHl3Y4eYduqW845aqJkK6qx5v+Z538UFJM3Bm6xUo4L8vBc4oeu3c4l/JWRdl cRdXW2KEeQDxBZSP64ovdhumn/wfc57sWUgaEODi8/A4T1vskVnnARtjyeFUGkDgIdih f9/NO1bzU+rtIg6A2jnipHtZ7Zg8s9pcR/LQcKZRhOeAMTn/fp7E0NjrIeAyWvHkZ/qd 9wuAIcq+WzduIaIc09eiLIiA/EJRJsyRQZmkTl9OeWiC9j4vrpjkLsbxyyVovwAcqBMR Xw==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by m0050093.ppops.net-00190b01. (PPS) with ESMTPS id 3f0814ad30-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 25 Mar 2022 12:21:45 +0000
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 22PCK4tm002787; Fri, 25 Mar 2022 08:21:44 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 3ewagy9pq0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 25 Mar 2022 08:21:44 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag4mb8.msg.corp.akamai.com (172.27.91.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.986.5; Fri, 25 Mar 2022 08:21:43 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Fri, 25 Mar 2022 08:21:43 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.033; Fri, 25 Mar 2022 08:21:43 -0400
To: 'Toerless Eckert' <tte@cs.fau.de>, "Joel M. Halpern" <jmh@joelhalpern.com>
Thread-Topic: [rfc-i] ****SPAM**** Re: 3rd party SDO cross-referencing of IETF work (was: Re: Chair/datatracker tracking expired WG documents ?)
Thread-Index: AQHYQDfUComjlE9H+E610K9BjoBDp6zQQ/qA///BWoA=
Date: Fri, 25 Mar 2022 12:21:43 +0000
Message-ID: <9C68473E-4C39-4EFA-ACBF-7968676DDEB8@akamai.com>
References: <Yj2d4DJMFWJOxoZa@faui48e.informatik.uni-erlangen.de> <317196df-3363-36c9-2421-02d9e229f664@joelhalpern.com> <Yj2wI/nc+gzbIBMF@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <Yj2wI/nc+gzbIBMF@faui48e.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.59.22031300
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-ID: <544E0EFE6DBEAE458C09486A910690EE@akamai.com>
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.850 definitions=2022-03-25_02:2022-03-24, 2022-03-25 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 mlxlogscore=887 bulkscore=0 mlxscore=0 spamscore=0 malwarescore=0 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2203250069
X-Proofpoint-GUID: SDwfG7Ih8Jte8JIqLxRu8x7LGQESq2f_
X-Proofpoint-ORIG-GUID: SDwfG7Ih8Jte8JIqLxRu8x7LGQESq2f_
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.850,Hydra:6.0.425,FMLib:17.11.64.514 definitions=2022-03-25_02,2022-03-24_01,2022-02-23_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 clxscore=1011 mlxscore=0 mlxlogscore=860 spamscore=0 lowpriorityscore=0 adultscore=0 priorityscore=1501 suspectscore=0 malwarescore=0 bulkscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2203250069
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/HKpfrIkRH3gnbLR2e7VD5ZlElcA>
Subject: Re: [rfc-i] ****SPAM**** Re: 3rd party SDO cross-referencing of IETF work (was: Re: Chair/datatracker tracking expired WG documents ?)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>
X-Original-From: "Salz, Rich" <rsalz@akamai.com>
From: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>

This could be useful information to know. Does the liaison program not handle it?

>   But of course, if an external SDO does choose to ignore our recommendation
    and is actually referrring to a draft in a published spec, then i still would
    rather like to know about it via such an explicit tracking mechanism than
    not to know about it.

A potential problem is that, unless people (who, that's also a problem) are diligent about following up and discouraging such use, then it is very easy for the misbehaving SDO to say "but you never complained so we assumed it's okay."


_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest

v2.8.7 | Report a Bug | By Email