Re: [lamps] next steps for draft-ietf-lamps-rfc7030est-clarify-02.txt
Michael Richardson <mcr+ietf@sandelman.ca> Mon, 09 March 2020 20:34 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78E973A0CA5 for <spasm@ietfa.amsl.com>; Mon, 9 Mar 2020 13:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 EVxr9kQ4BGtJ for <spasm@ietfa.amsl.com>; Mon, 9 Mar 2020 13:34:07 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE9A63A0AA3 for <spasm@ietf.org>; Mon, 9 Mar 2020 13:34:07 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0B17E3818F for <spasm@ietf.org>; Mon, 9 Mar 2020 16:32:55 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4AD739F9 for <spasm@ietf.org>; Mon, 9 Mar 2020 16:34:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: LAMPS WG <spasm@ietf.org>
In-Reply-To: <FDDAE926-17BC-4F34-944F-D972F1B22EDC@vigilsec.com>
References: <158345858645.14723.3002052789783805901@ietfa.amsl.com> <901.1583459380@localhost> <FDDAE926-17BC-4F34-944F-D972F1B22EDC@vigilsec.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 09 Mar 2020 16:34:06 -0400
Message-ID: <25508.1583786046@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/laElDCzEtt_acWG4pQFoMovvbVY>
Subject: Re: [lamps] next steps for draft-ietf-lamps-rfc7030est-clarify-02.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 20:34:11 -0000
Russ Housley <housley@vigilsec.com> wrote:
> RFC 8713 references errata in the Informational References section.
Thank you, that's what I've done.
>> There are now two more errata filed since we started this process:
>> a) https://www.rfc-editor.org/errata/eid5904
>>
>> is dealt with in this update, as it's about Content-Transfer-Encoding.
>> Is Justin Crawford on this list? How can I reach out to this person?
>> Neither of his options fits what industry has actually implemented, which is
>> base64 encoded objects, without a Content-Transfer-Encoding.
>>
>> b) https://www.rfc-editor.org/errata/eid5926
>>
>> asks to have the Examples updates. I think that we could do that in this
>> document. I would prefer to take examples from deployed products, and I've
>> CC'ed some people who could probably generate that.
I propose to mark these errata as being dealt with by this update as well by
adding examples.
>> c) https://www.rfc-editor.org/errata/eid5779
>>
>> points out the extra <sp> before ";", which should be tolerated, but not
>> required. This could updated with (b) above, I think.
We could repeat the example and fix it.
--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
- [lamps] I-D Action: draft-ietf-lamps-rfc7030est-c… internet-drafts
- [lamps] next steps for draft-ietf-lamps-rfc7030es… Michael Richardson
- Re: [lamps] next steps for draft-ietf-lamps-rfc70… Russ Housley
- Re: [lamps] next steps for draft-ietf-lamps-rfc70… Michael Richardson
- Re: [lamps] next steps for draft-ietf-lamps-rfc70… Michael Richardson