[Emu] RFC 9191 on Handling Large Certificates and Long Certificate Chains in TLS-Based EAP Methods

rfc-editor@rfc-editor.org Wed, 16 February 2022 02:43 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8895A3A14AC; Tue, 15 Feb 2022 18:43:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-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 bqpaP5hPDLa8; Tue, 15 Feb 2022 18:43:15 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E4043A144D; Tue, 15 Feb 2022 18:42:48 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 2EF594C1D3; Tue, 15 Feb 2022 18:42:48 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, emu@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20220216024248.2EF594C1D3@rfc-editor.org>
Date: Tue, 15 Feb 2022 18:42:48 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/QNEwcQ0Fwq7ORQT4Bo-oP1TEJXk>
Subject: [Emu] =?utf-8?q?RFC_9191_on_Handling_Large_Certificates_and_Long?= =?utf-8?q?_Certificate_Chains_in_TLS-Based_EAP_Methods?=
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2022 02:43:28 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9191

        Title:      Handling Large Certificates and Long 
                    Certificate Chains in TLS-Based EAP Methods 
        Author:     M. Sethi,
                    J. Preuß Mattsson,
                    S. Turner
        Status:     Informational
        Stream:     IETF
        Date:       February 2022
        Mailbox:    mohit@iki.fi,
                    john.mattsson@ericsson.com,
                    sean@sn3rd.com
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-emu-eaptlscert-08.txt

        URL:        https://www.rfc-editor.org/info/rfc9191

        DOI:        10.17487/RFC9191

The Extensible Authentication Protocol (EAP), defined in RFC 3748,
provides a standard mechanism for support of multiple authentication
methods. EAP-TLS and other TLS-based EAP methods are widely deployed
and used for network access authentication. Large certificates and
long certificate chains combined with authenticators that drop an EAP
session after only 40 - 50 round trips is a major deployment problem.
This document looks at this problem in detail and describes the
potential solutions available.

This document is a product of the EAP Method Update Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC