IETF Logo Mail Archive

Re: [Curdle] [kitten] I-D Action: draft-ietf-curdle-des-des-des-die-die-die-03.txt

Jeffrey Altman <jaltman@secure-endpoints.com> Wed, 21 June 2017 19:39 UTC

Return-Path: <prvs=13456c59c6=jaltman@secure-endpoints.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70FA01241FC for <curdle@ietfa.amsl.com>; Wed, 21 Jun 2017 12:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=secure-endpoints.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 eeGJ_5Z0c4qn for <curdle@ietfa.amsl.com>; Wed, 21 Jun 2017 12:39:05 -0700 (PDT)
Received: from sequoia-grove.secure-endpoints.com (sequoia-grove.ad.secure-endpoints.com [208.125.0.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 039A5129412 for <curdle@ietf.org>; Wed, 21 Jun 2017 12:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/relaxed; d=secure-endpoints.com; s=MDaemon; t=1498073922; x=1498678722; i=jaltman@secure-endpoints.com; q=dns/txt; h=VBR-Info:Subject:To: References:From:Openpgp:Organization:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type; bh=EutfDKLijbA71MVk2jRWYU wXArnZCv+guRJje3U/QYk=; b=Rltd6TNpT4nFjoSu00aMEesRC5M64vmsr9AlYN 0zg/r4ZGQhUejLgXU8EYwq/RmbYgGVi3YP8T7TUCzPkqtThfRp0husVIk65jMm0/ ZZnOo7CE+M2mYfVXmZ5xQot89Pf9Jr6FCWt7234EGOowJ5QkXXfZ34Aik9UpiBv5 /Qjkw=
X-MDAV-Result: clean
X-MDAV-Processed: sequoia-grove.secure-endpoints.com, Wed, 21 Jun 2017 15:38:42 -0400
X-Spam-Processed: sequoia-grove.secure-endpoints.com, Wed, 21 Jun 2017 15:38:42 -0400
Received: from [IPv6:2001:470:1f07:f77:7174:9244:a061:80d1] by secure-endpoints.com (IPv6:2001:470:1f07:f77:28d9:68fb:855d:c2a5) (MDaemon PRO v17.0.2) with ESMTPSA id md50001371673.msg; Wed, 21 Jun 2017 15:38:40 -0400
VBR-Info: md=secure-endpoints.com; mc=all; mv=vbr.emailcertification.org;
X-MDRemoteIP: 2001:470:1f07:f77:7174:9244:a061:80d1
X-MDHelo: [IPv6:2001:470:1f07:f77:7174:9244:a061:80d1]
X-MDArrival-Date: Wed, 21 Jun 2017 15:38:40 -0400
X-Authenticated-Sender: jaltman@secure-endpoints.com
X-Return-Path: prvs=13456c59c6=jaltman@secure-endpoints.com
X-Envelope-From: jaltman@secure-endpoints.com
X-MDaemon-Deliver-To: curdle@ietf.org
X-CAV-Result: clean
To: kitten@ietf.org, curdle@ietf.org
References: <20170621034615.GH39245@kduck.kaduk.org> <20170621094935.AF6161A6BF@ld9781.wdf.sap.corp> <20170621174558.GK39245@kduck.kaduk.org>
From: Jeffrey Altman <jaltman@secure-endpoints.com>
Openpgp: id=FA444AF197F449B24CF3E699F77A735592B69A04; url=https://pgp.mit.edu
Organization: Secure Endpoints Inc.
Message-ID: <ad1f3a3b-6116-cae4-855d-0b61964af770@secure-endpoints.com>
Date: Wed, 21 Jun 2017 15:38:36 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <20170621174558.GK39245@kduck.kaduk.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040206090204090807030301"
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/-I6HDifwdHE2leVi5wq6d--eMew>
Subject: Re: [Curdle] [kitten] I-D Action: draft-ietf-curdle-des-des-des-die-die-die-03.txt
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jun 2017 19:39:07 -0000

On 6/21/2017 1:45 PM, Benjamin Kaduk wrote:
> It sounds like you are asking for the addition of some text along
> the lines of:
> 
>   Software support is only a bare minimum requirement for deprecating
>   RC4 enctypes; there may be additional logistical considerations
>   involved such as provisioning AES keys for all principals and
>   updating software configuration to enable AES and disable deprecated
>   encryption types.
> 
> Is that something you are asking for?
> 
> Thanks,

In my opinion, such text is inappropriate for an RFC.  The deprecation
of the encryption type is a protocol action.  The RFC is not guidance
for system administrators.  Such guidance should come from the protocol
implementations.

As such I believe the addition of text similar to the above is
unnecessary for publication.

Jeffrey Altman

v2.23.0 | Report a Bug | By Email