Re: [art] [Technical Errata Reported] RFC7505 (6895)

John C Klensin <john-ietf@jck.com> Fri, 25 March 2022 22:31 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9061D3A0FAF for <art@ietfa.amsl.com>; Fri, 25 Mar 2022 15:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 NjbsjS8iYNrn for <art@ietfa.amsl.com>; Fri, 25 Mar 2022 15:31:06 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEC0B3A0EF9 for <art@ietf.org>; Fri, 25 Mar 2022 15:31:05 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1nXsSL-000ECx-Jg; Fri, 25 Mar 2022 18:30:53 -0400
Date: Fri, 25 Mar 2022 18:30:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Chris Smiley <csmiley@amsl.com>
cc: standards@taugh.com, mx0dot@yahoo.com, "Murray S. Kucherawy" <superuser@gmail.com>, Francesca Palombini <francesca.palombini@ericsson.com>, art@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Message-ID: <24B13CF9E3FEEAA5F22219D6@PSB>
In-Reply-To: <409C3E7D-AD56-497C-8866-7A01F5B99422@amsl.com>
References: <20220325190002.A18F03BAA5@rfc-editor.org> <409C3E7D-AD56-497C-8866-7A01F5B99422@amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/6SvQ_QDtQYf-D73l7tXhkEo6UB8>
Subject: Re: [art] [Technical Errata Reported] RFC7505 (6895)
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2022 22:31:21 -0000

Chris and others,

Thank you.
However, may I suggest that you hold off on circulating
possibly-suspicious messages like this, especially to large
lists like art@ietf.org, until the determination has been made
as to whether they need consideration and/or technical
evaluation or are just junk/noise?  

To the degree to which the intent of the original author was to
introduce noise into our systems and possibly impede our efforts
to do serious work, the broad circulation of the report aided in
that effort.

best,
   john


--On Friday, March 25, 2022 14:21 -0700 Chris Smiley
<csmiley@amsl.com> wrote:

> 
> Greetings,
> 
> FYI - this report has been deleted as junk.
> 
> Thank you.
> 
> RFC Editor/cs
> 
> 
>> On Mar 25, 2022, at 12:00 PM, RFC Errata System
>> <rfc-editor@rfc-editor.org> wrote:
>> 
>> The following errata report has been submitted for RFC7505,
>> "A "Null MX" No Service Resource Record for Domains That
>> Accept No Mail".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid6895
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Jesus Alvarado <mannyman4208@gmail.com>
>> 
>> Section: 7505
>> 
>> Original Text
>> -------------
>> 8.1 firmware oh and I forgot that I do have a couple of admin
>> breaking part to recover.
>> 
>> Corrected Text
>> --------------
>> I have 3 different ones that I can re encode in to but
>> haven't got a to do paperwork from Symantec contracts from
>> 2015 that worked through 2012 problems from 2013.
>> 
>> Notes
>> -----
>> 13 std ters.. of Trojans layers still knowing how to work
>> through and did part of the clean forge come back
>> 
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary,
>> please use "Reply All" to discuss whether it should be
>> verified or rejected. When a decision is reached, the
>> verifying party   can log in to change the status and edit
>> the report, if necessary. 
>> 
>> --------------------------------------
>> RFC7505 (draft-ietf-appsawg-nullmx-10)
>> --------------------------------------
>> Title               : A "Null MX" No Service Resource Record
>> for Domains That Accept No Mail Publication Date    : June
>> 2015
>> Author(s)           : J. Levine, M. Delany
>> Category            : PROPOSED STANDARD
>> Source              : ART Area General Application Working
>> Group Area                : Applications and Real-Time
>> Stream              : IETF
>> Verifying Party     : IESG
>> 
> 
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art