diff --git a/draft-vesco-vcauthtls.html b/draft-vesco-vcauthtls.html new file mode 100644 index 0000000..4312a1d --- /dev/null +++ b/draft-vesco-vcauthtls.html @@ -0,0 +1,1462 @@ + + + + + + +TODO - Your title + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Internet-DraftTODO - AbbreviationNovember 2023
Vesco, et al.Expires 12 May 2024[Page]
+
+
+
+
Workgroup:
+
Network Working Group
+
Internet-Draft:
+
draft-vesco-vcauthtls-latest
+
Published:
+
+ +
+
Intended Status:
+
Informational
+
Expires:
+
+
Authors:
+
+
+
A. Vesco
+
LINKS Foundation
+
+
+
L. Perugini
+
LINKS Foundation
+
+
+
N. Tuveri
+
Tampere University
+
+
+
+
+

TODO - Your title

+
+

Abstract

+

TODO Abstract

+
+
+

+About This Document +

+

This note is to be removed before publishing as an RFC.

+

+ The latest revision of this draft can be found at https://Cybersecurity-LINKS.github.io/draft-vesco-perugini-tls-ssi/draft-vesco-perugini-tuveri-tls-ssi.html. + Status information for this document may be found at https://datatracker.ietf.org/doc/draft-vesco-vcauthtls/.

+

Source for this draft and an issue tracker can be found at + https://github.com/Cybersecurity-LINKS/draft-vesco-perugini-tls-ssi.

+
+
+
+

+Status of This Memo +

+

+ This Internet-Draft is submitted in full conformance with the + provisions of BCP 78 and BCP 79.

+

+ Internet-Drafts are working documents of the Internet Engineering Task + Force (IETF). Note that other groups may also distribute working + documents as Internet-Drafts. The list of current Internet-Drafts is + at https://datatracker.ietf.org/drafts/current/.

+

+ Internet-Drafts are draft documents valid for a maximum of six months + and may be updated, replaced, or obsoleted by other documents at any + time. It is inappropriate to use Internet-Drafts as reference + material or to cite them other than as "work in progress."

+

+ This Internet-Draft will expire on 12 May 2024.

+
+
+ +
+
+ ▲

+Table of Contents +

+ +
+
+
+
+

+1. Introduction +

+
+
+
+
+

+2. Conventions and Definitions +

+

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", +"MAY", and "OPTIONAL" in this document are to be interpreted as +described in BCP 14 [RFC2119] [RFC8174] when, and only when, they +appear in all capitals, as shown here.

+
+
+
+
+

+3. Structure of the FOOBAR Extensions +

+ +
+
+

+3.2. foobar1 +

+
+
+
+
+

+3.3. foobar2 +

+
+
+
+
+
+
+

+4. Possibly the new Messages +

+
+
+
+
+

+5. TLS Client and Server Handshake Behavior +

+
+
+

+5.1. ClientHello +

+
+
+ +
+
+

+5.3. Certificate +

+
+
+ +
+
+
+
+

+6. An alternative Design / Design Consideration +

+
+
+
+
+

+7. Examples +

+ + + +
+
+

+7.4. TLS Client Uses Certificate and Server Uses VP +

+

it happens when the server does not send ssi_paramters extension in certificate request or it does but the client does not have a DID in the list of supported DLT (i.e. DID Methods) by the server

+
+
+
+
+

+7.5. Fallback to Traditional Handshake +

+

server ignores ssi_parameters extension in the clientHello

+
+
+
+
+

+7.6. Empty intersection of Client and Server DID Methods +

+

HelloRetryRequest + foobar extension +server replies with the list of its DID Methods, this implies that the server has a DID stored in each of the DLT of the listed DID Methods.

+
+
+
+
+

+7.7. TLS Server Enforces SSI Server Authentication +

+

server enforces SSI client authentication (no fall back bu enforce SSI to the client)

+

HelloRetryRequest

+
+
+
+
+
+
+

+8. Security Considerations +

+

TODO Security

+
+
+
+
+

+9. IANA Considerations +

+

This document has no IANA actions.

+
+
+
+
+

+10. Normative References +

+
+
[RFC2119]
+
+Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/rfc/rfc2119>.
+
+
[RFC8174]
+
+Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.
+
+
+
+
+
+
+

+Acknowledgments +

+

TODO acknowledge.

+
+
+
+
+

+Authors' Addresses +

+
+
Andrea Vesco
+
LINKS Foundation
+ +
+
+
Leonardo Perugini
+
LINKS Foundation
+ +
+
+
Nicola Tuveri
+
Tampere University
+ +
+
+
+ + + diff --git a/draft-vesco-vcauthtls.txt b/draft-vesco-vcauthtls.txt new file mode 100644 index 0000000..e6ac2c9 --- /dev/null +++ b/draft-vesco-vcauthtls.txt @@ -0,0 +1,193 @@ + + + + +Network Working Group A. Vesco +Internet-Draft L. Perugini +Intended status: Informational LINKS Foundation +Expires: 12 May 2024 N. Tuveri + Tampere University + 9 November 2023 + + + TODO - Your title + draft-vesco-vcauthtls-latest + +Abstract + + TODO Abstract + +About This Document + + This note is to be removed before publishing as an RFC. + + The latest revision of this draft can be found at + https://Cybersecurity-LINKS.github.io/draft-vesco-perugini-tls-ssi/ + draft-vesco-perugini-tuveri-tls-ssi.html. Status information for + this document may be found at https://datatracker.ietf.org/doc/draft- + vesco-vcauthtls/. + + Source for this draft and an issue tracker can be found at + https://github.com/Cybersecurity-LINKS/draft-vesco-perugini-tls-ssi. + +Status of This Memo + + This Internet-Draft is submitted in full conformance with the + provisions of BCP 78 and BCP 79. + + Internet-Drafts are working documents of the Internet Engineering + Task Force (IETF). Note that other groups may also distribute + working documents as Internet-Drafts. The list of current Internet- + Drafts is at https://datatracker.ietf.org/drafts/current/. + + Internet-Drafts are draft documents valid for a maximum of six months + and may be updated, replaced, or obsoleted by other documents at any + time. It is inappropriate to use Internet-Drafts as reference + material or to cite them other than as "work in progress." + + This Internet-Draft will expire on 12 May 2024. + +Copyright Notice + + Copyright (c) 2023 IETF Trust and the persons identified as the + document authors. All rights reserved. + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents (https://trustee.ietf.org/ + license-info) in effect on the date of publication of this document. + Please review these documents carefully, as they describe your rights + and restrictions with respect to this document. Code Components + extracted from this document must include Revised BSD License text as + described in Section 4.e of the Trust Legal Provisions and are + provided without warranty as described in the Revised BSD License. + +Table of Contents + + 1. Introduction + 2. Conventions and Definitions + 3. Structure of the FOOBAR Extensions + 3.1. ssi_parameters + 3.2. foobar1 + 3.3. foobar2 + 4. Possibly the new Messages + 5. TLS Client and Server Handshake Behavior + 5.1. ClientHello + 5.2. CertificateRequest + 5.3. Certificate + 5.4. CertificateVerify + 6. An alternative Design / Design Consideration + 7. Examples + 7.1. TLS Server Uses a VP + 7.2. TLS Client and Server Use VPs + 7.3. TLS Client Uses VP and Server Uses Certificate + 7.4. TLS Client Uses Certificate and Server Uses VP + 7.5. Fallback to Traditional Handshake + 7.6. Empty intersection of Client and Server DID Methods + 7.7. TLS Server Enforces SSI Server Authentication + 8. Security Considerations + 9. IANA Considerations + 10. Normative References + Acknowledgments + Authors' Addresses + +1. Introduction + +2. Conventions and Definitions + + The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", + "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and + "OPTIONAL" in this document are to be interpreted as described in + BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all + capitals, as shown here. + +3. Structure of the FOOBAR Extensions + +3.1. ssi_parameters + +3.2. foobar1 + +3.3. foobar2 + +4. Possibly the new Messages + +5. TLS Client and Server Handshake Behavior + +5.1. ClientHello + +5.2. CertificateRequest + +5.3. Certificate + +5.4. CertificateVerify + +6. An alternative Design / Design Consideration + +7. Examples + +7.1. TLS Server Uses a VP + +7.2. TLS Client and Server Use VPs + +7.3. TLS Client Uses VP and Server Uses Certificate + +7.4. TLS Client Uses Certificate and Server Uses VP + + it happens when the server does not send ssi_paramters extension in + certificate request or it does but the client does not have a DID in + the list of supported DLT (i.e. DID Methods) by the server + +7.5. Fallback to Traditional Handshake + + server ignores ssi_parameters extension in the clientHello + +7.6. Empty intersection of Client and Server DID Methods + + HelloRetryRequest + foobar extension server replies with the list of + its DID Methods, this implies that the server has a DID stored in + each of the DLT of the listed DID Methods. + +7.7. TLS Server Enforces SSI Server Authentication + + server enforces SSI client authentication (no fall back bu enforce + SSI to the client) + + HelloRetryRequest + +8. Security Considerations + + TODO Security + +9. IANA Considerations + + This document has no IANA actions. + +10. Normative References + + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . + + [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, + May 2017, . + +Acknowledgments + + TODO acknowledge. + +Authors' Addresses + + Andrea Vesco + LINKS Foundation + Email: andrea.vesco@linksfoundation.com + + + Leonardo Perugini + LINKS Foundation + Email: leonardo.perugini@linksfoundation.com + + + Nicola Tuveri + Tampere University + Email: nic.tuv@gmail.com diff --git a/index.html b/index.html index dfa8f8e..3136eb0 100644 --- a/index.html +++ b/index.html @@ -23,6 +23,13 @@

Editor's drafts for main branch of diff with last submission + + TODO - Abbreviation + plain text + datatracker + diff with last submission + +