diff --git a/draft-sheffer-wimse-s2s-protocol.html b/draft-sheffer-wimse-s2s-protocol.html new file mode 100644 index 0000000..4be0ad1 --- /dev/null +++ b/draft-sheffer-wimse-s2s-protocol.html @@ -0,0 +1,1239 @@ + + + + + + +WIMSE Service to Service Authentication + + + + + + + + + + + + + + + + + + + + + + + + +
Internet-DraftWIMSE S2S AuthMay 2024
ShefferExpires 24 November 2024[Page]
+
+
+
+
Workgroup:
+
Workload Identity in Multi System Environments
+
Internet-Draft:
+
draft-sheffer-wimse-s2s-protocol-latest
+
Published:
+
+ +
+
Intended Status:
+
Standards Track
+
Expires:
+
+
Author:
+
+
+
Y. Sheffer
+
Intuit
+
+
+
+
+

WIMSE Service to Service Authentication

+
+

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://yaronf.github.io/wimse-s2s/draft-sheffer-wimse-s2s-protocol.html. + Status information for this document may be found at https://datatracker.ietf.org/doc/draft-sheffer-wimse-s2s-protocol/.

+

+ Discussion of this document takes place on the + Workload Identity in Multi System Environments Working Group mailing list (mailto:wimse@ietf.org), + which is archived at https://mailarchive.ietf.org/arch/browse/wimse/. + Subscribe at https://www.ietf.org/mailman/listinfo/wimse/.

+

Source for this draft and an issue tracker can be found at + https://github.com/yaronf/wimse-s2s.

+
+
+
+

+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 24 November 2024.

+
+
+ +
+
+ ▲

+Table of Contents +

+ +
+
+
+
+

+1. Introduction +

+

TODO 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. Security Considerations +

+

TODO Security

+
+
+
+
+

+4. IANA Considerations +

+

This document has no IANA actions.

+
+
+
+
+

+5. 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.

+
+
+
+
+

+Author's Address +

+
+
Yaron Sheffer
+
Intuit
+ +
+
+
+ + + diff --git a/draft-sheffer-wimse-s2s-protocol.txt b/draft-sheffer-wimse-s2s-protocol.txt new file mode 100644 index 0000000..3601d23 --- /dev/null +++ b/draft-sheffer-wimse-s2s-protocol.txt @@ -0,0 +1,116 @@ + + + + +Workload Identity in Multi System Environments Y. Sheffer +Internet-Draft Intuit +Intended status: Standards Track 23 May 2024 +Expires: 24 November 2024 + + + WIMSE Service to Service Authentication + draft-sheffer-wimse-s2s-protocol-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://yaronf.github.io/wimse-s2s/draft-sheffer-wimse-s2s- + protocol.html. Status information for this document may be found at + https://datatracker.ietf.org/doc/draft-sheffer-wimse-s2s-protocol/. + + Discussion of this document takes place on the Workload Identity in + Multi System Environments Working Group mailing list + (mailto:wimse@ietf.org), which is archived at + https://mailarchive.ietf.org/arch/browse/wimse/. Subscribe at + https://www.ietf.org/mailman/listinfo/wimse/. + + Source for this draft and an issue tracker can be found at + https://github.com/yaronf/wimse-s2s. + +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 24 November 2024. + +Copyright Notice + + Copyright (c) 2024 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. Security Considerations + 4. IANA Considerations + 5. Normative References + Acknowledgments + Author's Address + +1. Introduction + + TODO 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. Security Considerations + + TODO Security + +4. IANA Considerations + + This document has no IANA actions. + +5. 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. + +Author's Address + + Yaron Sheffer + Intuit + Email: yaronf.ietf@gmail.com diff --git a/index.html b/index.html index e69de29..4c9a21f 100644 --- a/index.html +++ b/index.html @@ -0,0 +1,48 @@ + + + + yaronf/wimse-s2s main preview + + + + +

Editor's drafts for main branch of yaronf/wimse-s2s

+

View saved issues, or the latest GitHub issues and pull requests in the repo.

+ + + + + + + + +
WIMSE S2S Authplain textdatatrackerdiff with last submission
+ + +