Re: [Secdispatch] addressing Content-Type-Encoding errata on EST / RFC7030

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 18 July 2019 17:49 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F59120AD4 for <secdispatch@ietfa.amsl.com>; Thu, 18 Jul 2019 10:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 MrgR7E3DhtkS for <secdispatch@ietfa.amsl.com>; Thu, 18 Jul 2019 10:49:00 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id A7EC2120ADC for <secdispatch@ietf.org>; Thu, 18 Jul 2019 10:49:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1563472139; d=isode.com; s=june2016; i=@isode.com; bh=ZzhlWsXGPE+PIkvYdod4PkvVUwFXw2zYyknrWdPEw00=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=vgVtcDWNdrgr/14Du99CL3xtFdeqcnvDsCAPQOIO0k83kW7gewlEp3C80k+nArmxPDvSrq 3VGqMk5rrhNE+9MjSJhzpL5TNOkg481V9c1aYWi382F2OtxAaGzWdvh1axv64xRFcpqQ7K VZDYc0eFemZJLiqGijP9YLESGfaBO4I=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <XTCxCgAW87AG@statler.isode.com>; Thu, 18 Jul 2019 18:48:59 +0100
To: Michael Richardson <mcr+ietf@sandelman.ca>, secdispatch@ietf.org
Cc: Daniel Harkins <dharkins@lounge.org>
References: <6535.1560786935@dooku.sandelman.ca> <10505.1560789112@dooku.sandelman.ca> <12718.1560790704@dooku.sandelman.ca> <040a01d5263c$6c51efa0$44f5cee0$@augustcellars.com> <16160.1560951514@localhost> <57b7caef-e814-947b-c705-6e02c35e2cd3@sandelman.ca>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <ea07d17b-7bef-a00c-68ee-98d711407665@isode.com>
Date: Thu, 18 Jul 2019 18:48:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0
In-Reply-To: <57b7caef-e814-947b-c705-6e02c35e2cd3@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/x9f_CDnXgpGnXEaC1125MQmnGDY>
Subject: Re: [Secdispatch] addressing Content-Type-Encoding errata on EST / RFC7030
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2019 17:49:03 -0000

Hi Michael,

On 16/07/2019 16:36, Michael Richardson wrote:
> On 2019-06-19 9:38 a.m., Michael Richardson wrote:
>>
>> Dear secdispatch Chairs,
>>
>> I have written draft-richardson-lamps-rfc7030est-clarify-02 to deal with
>> the errata:
>>     https://www.rfc-editor.org/errata/eid5107
>>
>> it turns out that deployed code prevents us from having a signal that
>> would let us remove the needless base64 encoding, but at least we can
>> remove the deprecated CTE header which was not being used anyway.
>
> Hi secdispatch, I don't think that I really need any in-person time 
> next week on this.  I'm just looking for guidance on where/how such a 
> document should proceed.  AD-sponsor? LAMPS? Something else?

I think I was the ART AD who spotted the problem, so arguably it is my 
fault :-). We should talk in Montreal. I think AD-sponsored would be Ok 
if changes are constrained.

Best Regards,

Alexey


> The base64/Content-Type-Encoding situation definitely caused a lot of 
> confusion for the BRSKI inter-operation testing that has occurred in 
> the past few months.
>
>>
>> I believe that we can deal with:
>>      https://www.rfc-editor.org/errata/eid4384
>>      https://www.rfc-editor.org/errata/eid5108
>>
>> in this document as well, although I haven't yet done that.  The 
>> result would
>> be a standards track document that Updates RFC7030.
>
> There is an additional errata of a completely editorial from July 13.
> I don't really speak enough ASN.1 to know if the ASN.1 errata is valid.
>
> I'm told that Dan Harkins has other reasons to re-open RFC7030, and 
> while I think we could satisfy the PS->IS step via interoperation and 
> deployment experience, I'm not burning to do that work.
>
>>
>> As an aside, I think that the errata needs to move from reported to 
>> accepted.
>>