IETF Logo Mail Archive

[TLS] Is there any interest in an RFC on how to do cross-organization mTLS?

Mark Robinson <mark@markrobinson.io> Mon, 09 September 2024 18:42 UTC

Return-Path: <mark@mrobinson.ca>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE4AC1CAE96 for <tls@ietfa.amsl.com>; Mon, 9 Sep 2024 11:42:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.855
X-Spam-Level:
X-Spam-Status: No, score=-4.855 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=markrobinson.io
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JEGZ-QNYFM9 for <tls@ietfa.amsl.com>; Mon, 9 Sep 2024 11:42:27 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28253C14CE4A for <tls@ietf.org>; Mon, 9 Sep 2024 11:42:26 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-5c3cdba33b0so5066510a12.1 for <tls@ietf.org>; Mon, 09 Sep 2024 11:42:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=markrobinson.io; s=google; t=1725907345; x=1726512145; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UYls1rVlTNwEiKWyg7qJgAIlzE6xJ6UWYlAgQWMnn2o=; b=VdY+2HGWaOhSuYRM3FeZQFWmC+00/QNtHEO8l6MMSgPktD0/GjzA5SnSuRE51cGqnX DUc5rVUz5p7Z6eutL+5pAOmUTaB0sALwjOEbtyUoraUBoEueE9PzH1iW7cYhmzM/9Cws u85PdTx6tzAmIjO0FAmiOauIDthJ6G9Y4gJCcgUCDwIVJjcQWETCrTP0GCMVtDSfAUBZ NcvzwdCAeFsMV58WL2h7P+wieHYbXoUtgPBhT2kqGCdN0TauGZXaPfDbZgjZfmJ+4sIL qo4F1HXzbCzhnOv7qMjCivYivTn0IORdyGagIs6f2vSgXZ4K17wdGbi6a7YrBmkrC4Ak HUVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725907345; x=1726512145; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UYls1rVlTNwEiKWyg7qJgAIlzE6xJ6UWYlAgQWMnn2o=; b=kpP5hnWzXgl88uUVHY8/yXCedsu5nFiPaxfvyBtnlXneT4q+VoBIfZMDH/nF9Lmhqt M87oWPjUsZViGaNCnZO2gjiq2Oidd3yUhTtgitF0ncor/54meN6pPHrFKGzeRLy0jD0+ DoGzS7BX3VKt2D5mesE9zWXB9eXAw6GRUUIGZsBl88KsRL/nswiyDd6YZeNTLYOLmq5R kmd5c21ZxVse+165irlLQQZPaq81JcyZ0XPKrVWOAfdeAJDzkmdlF8XYb6rJHdOGCmAi yzfwr2GmIq7ePQNAmP4FdnpTooAe1COzO4bRufMK2i06knIPD9wChUSog9L+RK81L9E2 esFw==
X-Gm-Message-State: AOJu0YxnJUMPI/OXASqt7Gk/KKEb/yh1MJgKf0JEqbX2BOji6aEaW9Jj ksNh5WjeulDnaJr1s9c5DxWws01UEmv91PX+dwZmx4ZvC9fwiO1FWX7a3TFy+SZqeW1rTJ1WhiM eaTChHGoeU7bNW35MEhIgbrgBCwfhGFHoHRJDTTcSZWXAOggT
X-Google-Smtp-Source: AGHT+IGsWhbX2Nx0rpNCXtBd6n7gyx+yIT8H/SvfZjwfDO8uRjVJMq47O8e5CnjS8PQL/ELbeTYzQJAcaUnAsu5Ai9k=
X-Received: by 2002:a05:6402:40c3:b0:5c2:5cc8:353f with SMTP id 4fb4d7f45d1cf-5c3dc7bd5ddmr9093457a12.22.1725907345169; Mon, 09 Sep 2024 11:42:25 -0700 (PDT)
MIME-Version: 1.0
From: Mark Robinson <mark@markrobinson.io>
Date: Mon, 09 Sep 2024 11:42:14 -0700
Message-ID: <CAHaGKyeSBGD4AAbnddiWtG7kEvh3Y6mbTyAgw485UfJZhFKXkw@mail.gmail.com>
To: tls@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003981510621b41e9e"
Message-ID-Hash: ZOHDW3KETMKZCC4TJIZ4BLVJW6ASFAVF
X-Message-ID-Hash: ZOHDW3KETMKZCC4TJIZ4BLVJW6ASFAVF
X-MailFrom: mark@mrobinson.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [TLS] Is there any interest in an RFC on how to do cross-organization mTLS?
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/prSrrPfChajSwT0RUgqxKrFoNMU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

I've been doing a lot of work lately to support organizations that do mTLS
between each other. The problem I've found is that there is a huge amount
of ignorance on TLS in general and mTLS in particular.

Would it be appropriate to write an RFC on how to make cross-organization
mTLS work reliably and at scale? Would this group/mailing list be the right
people to work with to make that happen?

Mark

v2.27.8 | Report a Bug | By Email | System Status