IETF Logo Mail Archive

Re: [Svt] I'd like to see SVT move forward

Stefan Santesson <stefan@aaa-sec.com> Mon, 08 February 2021 09:14 UTC

Return-Path: <stefan@aaa-sec.com>
X-Original-To: svt@ietfa.amsl.com
Delivered-To: svt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 703B23A14F2 for <svt@ietfa.amsl.com>; Mon, 8 Feb 2021 01:14:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 BAKpZvSyWMxV for <svt@ietfa.amsl.com>; Mon, 8 Feb 2021 01:14:08 -0800 (PST)
Received: from smtp.outgoing.loopia.se (smtp.outgoing.loopia.se [93.188.3.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9E4E3A14F7 for <svt@ietf.org>; Mon, 8 Feb 2021 01:14:06 -0800 (PST)
Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id C5EA01A98006 for <svt@ietf.org>; Mon, 8 Feb 2021 10:02:18 +0100 (CET)
Received: from s645.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id A5F0B2E29DF1; Mon, 8 Feb 2021 10:02:18 +0100 (CET)
Received: from s476.loopia.se (unknown [172.22.191.5]) by s645.loopia.se (Postfix) with ESMTP id 8A74C1579F86; Mon, 8 Feb 2021 10:02:18 +0100 (CET)
X-Virus-Scanned: amavisd-new at amavis.loopia.se
Received: from s630.loopia.se ([172.22.191.5]) by s476.loopia.se (s476.loopia.se [172.22.190.16]) (amavisd-new, port 10024) with LMTP id BVuR1pqXUJWY; Mon, 8 Feb 2021 10:02:17 +0100 (CET)
X-Loopia-Auth: user
X-Loopia-User: mailstore2@aaa-sec.com
X-Loopia-Originating-IP: 85.235.7.89
Received: from [192.168.2.50] (gw.aaa-sec.ideon.se [85.235.7.89]) (Authenticated sender: mailstore2@aaa-sec.com) by s630.loopia.se (Postfix) with ESMTPSA id 1B4FF13B935F; Mon, 8 Feb 2021 10:02:17 +0100 (CET)
User-Agent: Microsoft-MacOutlook/16.44.20121301
Date: Mon, 08 Feb 2021 10:02:16 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: Russ Housley <housley@vigilsec.com>, "svt@ietf.org" <svt@ietf.org>
Message-ID: <08F4D2AF-C980-4008-A442-17ACF7FF379F@aaa-sec.com>
Thread-Topic: [Svt] I'd like to see SVT move forward
References: <C46A471B-7C1B-42E8-95DD-9FE0140E59C0@vigilsec.com>
In-Reply-To: <C46A471B-7C1B-42E8-95DD-9FE0140E59C0@vigilsec.com>
Mime-version: 1.0
Content-type: multipart/mixed; boundary="B_3695623337_750553634"
Archived-At: <https://mailarchive.ietf.org/arch/msg/svt/Jo1sQmdgfo3nicsL-xXT_LjQ0Rs>
Subject: Re: [Svt] I'd like to see SVT move forward
X-BeenThere: svt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Signature Validation Tokens <svt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/svt>, <mailto:svt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/svt/>
List-Post: <mailto:svt@ietf.org>
List-Help: <mailto:svt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/svt>, <mailto:svt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2021 09:14:12 -0000

Russ,

 

Thank you for this reminder.

I would like to update on the implementation progress of the current version (1.0) of these specifications.

 

Attached you find a signed XML and PDF document, with and without an SVT.

 

These documents were signed using the eduSign signing service at: https://edusign.sunet.se/open/login

The SVT was issued by the eduSign validation service: https://validator.edusign.sunet.se

 

Anyone can upload, validate and get successfully validated documents extended with an SVT.

 

Documents extended with an SVT can be archived and validated at any time in the future based on the SVT as long as the validator trust the SVT signing key and the algorithms used to sign the SVT.

 

At this point we see no problems with the specifications and the profiles for PDF and XML.

 

We have now got a green light to implement this as a national service for the public sector government agencies in Sweden.

Any feedback on these specifications would therefore be very valuable.

 

I would like to also repeat that there are more resources available at our GitHub page: https://github.com/swedenconnect/IETF-SVT

Including a youtube presentation video: https://youtu.be/IEJBmHJklHY

 

 

Stefan Santesson 

 

From: Svt <svt-bounces@ietf.org> on behalf of Russ Housley <housley@vigilsec.com>
Date: Thursday, 4 February 2021 at 20:47
To: "svt@ietf.org" <svt@ietf.org>
Subject: [Svt] I'd like to see SVT move forward

 

In October 2020, Stefan approached me about working with him on the SVT documents.  I said that the information that was perviously presented had not convinced me that this was needed.  That lead to a dialog about the digitally signed documents in archives.  The examples that Stefan used were the Swedish Agency for Digital Government (DIGG) and eduSign.  Further discussion of these use chases convinced me that there was value to this approach.  These were included in the SECDISPATCH slides at IETF 109:

 

                https://datatracker.ietf.org/meeting/109/materials/slides-109-secdispatch-draft-santesson-svt-00

 

I am not saying that the specifications are finished.  Rather, I am saying let's talk about them.  Has anyone on this list found things in the documents to praise or criticize?

 

Russ

 

-- Svt mailing list Svt@ietf.org https://www.ietf.org/mailman/listinfo/svt

v2.23.0 | Report a Bug | By Email