IETF Logo Mail Archive

Re: [pkix] Simple Certificate Enrollment Protocol (SCEP)

"Max Pritikin (pritikin)" <pritikin@cisco.com> Wed, 12 November 2014 09:07 UTC

Return-Path: <pritikin@cisco.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF2F81A1B45 for <pkix@ietfa.amsl.com>; Wed, 12 Nov 2014 01:07:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level:
X-Spam-Status: No, score=-15.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 QDboPViOK-pi for <pkix@ietfa.amsl.com>; Wed, 12 Nov 2014 01:07:41 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27B3F1A1BB5 for <pkix@ietf.org>; Wed, 12 Nov 2014 01:07:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1145; q=dns/txt; s=iport; t=1415783261; x=1416992861; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=KGJfRLVIup1SixUchXOSlpJO5pYtlquPq9pGtwxMP34=; b=I7J14Ffr1x+6uZQZ5VnF+sE8M163DpYHZCZxpNtsIrgKaGNneqfEriyZ olqK+gFtM0Uq9J/zgyQlbAyqfdGVXboLmNxklGiICrvfid8JgZbMKtJ6k +zN5xCfM0jQ7ncSE11u+06taj7+8TI8Nq5UzFN42legKpt8QKTd7h7JaV Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFANkhY1StJV2U/2dsb2JhbABcDoMAVFnMIAqHTwKBGxYBAQEBAX2EAgEBAQMBAQEBawsFCwIBCA4KLicLJQEBBA4FiDgJDc1YAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSQYTMHgy2BHgWSOot3lmeDPEBtgksBAQE
X-IronPort-AV: E=Sophos;i="5.07,367,1413244800"; d="scan'208";a="95817920"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-5.cisco.com with ESMTP; 12 Nov 2014 09:07:40 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id sAC97e0a003147 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 12 Nov 2014 09:07:40 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.19]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Wed, 12 Nov 2014 03:07:40 -0600
From: "Max Pritikin (pritikin)" <pritikin@cisco.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Thread-Topic: [pkix] Simple Certificate Enrollment Protocol (SCEP)
Thread-Index: Ac/+VYvkGBrWCtIyTnqyZLG46sIQPwAApAGF
Date: Wed, 12 Nov 2014 09:07:39 +0000
Message-ID: <D3EA8D92-1779-42AD-84F2-46047C4ECF50@cisco.com>
References: <9A043F3CF02CD34C8E74AC1594475C739B9E6654@uxcn10-5.UoA.auckland.ac.nz>
In-Reply-To: <9A043F3CF02CD34C8E74AC1594475C739B9E6654@uxcn10-5.UoA.auckland.ac.nz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pkix/oUMwLpypIexlYu5su5gOJ-tmgwA
Cc: IETF PKIX <pkix@ietf.org>
Subject: Re: [pkix] Simple Certificate Enrollment Protocol (SCEP)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Nov 2014 09:07:43 -0000

Peter, as long as the scope is around identifying existing undocumented practices, and not adding new features, I could support getting the existing draft into shape for a Historic status RFC. 

- max

> On Nov 11, 2014, at 10:49 PM, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote:
> 
> "Max Pritikin (pritikin)" <pritikin@cisco.com> writes:
> 
>> A question: How is updating "half a billion SCEP devices” to a new version of
>> SCEP any different than updating them to EST or similar?
> 
> It's not a new version of SCEP (many implementations that I've done interop
> with already do AES, for example, even though the spec doesn't mention it),
> it's clarifying existing practice, noting possible problem areas (renewal is a
> big one, see the discussion on the JSCEP list a while back), etc.  For most
> existing implementations it'll mean no change, for future updates it's an
> option to choose more-likely-to-work option X instead of Y.
> 
> Peter.
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix

v2.23.0 | Report a Bug | By Email