IETF Logo Mail Archive

Re: [art] Against BCP 190

S Moonesamy <sm+ietf@elandsys.com> Sat, 13 July 2019 13:30 UTC

Return-Path: <sm@elandsys.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 433A81202BA for <art@ietfa.amsl.com>; Sat, 13 Jul 2019 06:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=yvC3CGii; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=JJnTlwqO
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 xWkLIPExyhnQ for <art@ietfa.amsl.com>; Sat, 13 Jul 2019 06:30:04 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F6A1200FA for <art@ietf.org>; Sat, 13 Jul 2019 06:30:03 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.189.240]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id x6DDTmBN006967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Jul 2019 06:29:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1563024601; x=1563111001; bh=GLqrx7Ji31diWCzImdpehLLt6+pAE6DO853RUYY3TZ0=; h=Date:To:From:Subject:In-Reply-To:References; b=yvC3CGiiNCJoGjvmoE+zrsnWT+OV1lo2HHJ8oYFzeYfeMpzaRxp0j1MFrsuEsKs7i QHCc6uDMAEmNO5JX3E/hFf8XbQYfyBHPGxmWrdHEbsLt/AJwONCwQyo1C81U8IvdAG 5SPbWHsZCoWX0jzQbGe2vYCinZpBYeZW2GiQicDI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1563024601; x=1563111001; i=@elandsys.com; bh=GLqrx7Ji31diWCzImdpehLLt6+pAE6DO853RUYY3TZ0=; h=Date:To:From:Subject:In-Reply-To:References; b=JJnTlwqO9Krekir9ntTVV3Me2ie888snv8rmBjS1BoWR+1yGZEQQlyjenJfthLVEq HPwAjmEIfkV/Sbd3sAz5jn3bb70GS71bebVIwl9KG6zejfcoDYwmIdvMVYcC4MJ71c f+jCdzobgPUxU1MwlcVdTz7WF70WeTsZcwatWMKE=
Message-Id: <6.2.5.6.2.20190713054207.0bbd9b58@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 13 Jul 2019 06:29:30 -0700
To: Rob Stradling <rob@sectigo.com>, art@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <791b33b8-4696-f69c-aca3-8838b2caafd8@sectigo.com>
References: <791b33b8-4696-f69c-aca3-8838b2caafd8@sectigo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/afpbOO1tnFv6rD7b9PW8aMzAs5s>
Subject: Re: [art] Against BCP 190
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: Sat, 13 Jul 2019 13:30:05 -0000

Hi Rob,

The short answer for your request to change RFC 7320 is to consider 
the example at 
https://mailarchive.ietf.org/arch/msg/art/vcUQD4V6PlTMbzfW_89JhvhJEF0

The ACME erratum which you referred to violates the rules set by the 
IESG for processing of errata.  I took a quick look at 
draft-ietf-trans-rfc6962-bis.  It is not aligned with the Working 
Group Charter.  One of the "DISCUSS" is about information disclosure; 
it is currently not addressed in the draft.

If the Working Group is against RFC 7320, it could submit a draft to 
change it.  I suggest considering the time it could take to get that 
through the IETF process.

Regards,
S. Moonesamy

v2.27.8 | Report a Bug | By Email | System Status