IETF Logo Mail Archive

[Emu] Re: Call for adoption: draft-dekok-emu-teapv2-03 (Ends 2026-05-26)

Peter Yee <peter@akayla.com> Tue, 12 May 2026 11:23 UTC

Return-Path: <peter@akayla.com>
X-Original-To: emu@mail2.ietf.org
Delivered-To: emu@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 7ACAEED0AC86; Tue, 12 May 2026 04:23:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778585013; bh=HvbsrdmhGN353qcU9GmlV7mL0qy8VyjUaC4BhFjxmLQ=; h=Date:Subject:From:To:CC:References:In-Reply-To; b=cQy86OLQm4tYiFrkWZDmFHq4knR2uY2Q7Cbv1jOqRY3G3xsuTjwLxaBu+iqJEoPqT Arj0d06r5nVMNV/5ScsAfVTe27z7eVfTaKK4jG+RRUTeQptOoy1Usevred6zG8EXyR ZrR1C1nP7lU067U5KJ1kjwfE64WlpFZeQwqgOCRI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=akayla.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ac7CW5vmqWlg; Tue, 12 May 2026 04:23:29 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 45171ED0AC7A; Tue, 12 May 2026 04:23:26 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 773891A0FA9; Tue, 12 May 2026 07:23:20 -0400 (EDT)
Received: from [10.100.21.214] (unknown [94.107.248.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id EB3511A1C45; Tue, 12 May 2026 07:23:19 -0400 (EDT)
User-Agent: Microsoft-MacOutlook/16.108.26050324
Date: Tue, 12 May 2026 13:23:16 +0200
From: Peter Yee <peter@akayla.com>
To: emu@ietf.org
Message-ID: <DE9246A5-B3AD-4C73-A5AC-D097B4FE049A@akayla.com>
Thread-Topic: [Emu] Call for adoption: draft-dekok-emu-teapv2-03 (Ends 2026-05-26)
References: <177858432222.788794.7686978637424095969@dt-datatracker-54557f87b8-lnrkh>
In-Reply-To: <177858432222.788794.7686978637424095969@dt-datatracker-54557f87b8-lnrkh>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akayla.com; h=date:subject:from:to:cc:message-id:references:in-reply-to:mime-version:content-type:content-transfer-encoding; s=pair-202402141610; bh=UiblRUyJhxXr5sYTLhVCq4bB8ut1YsXXCsQEz8X0r+0=; b=LPawdtn4IDdcINYHyk8Fb+0R30UVCVTFkejCtWL8L0jYRjhNOjTlMdMMfHpTAHwc5j9vC8QqMnVdFkaMBLIDOmxmuU9WRVq8tumV6VYnsycVNqTpBRrtEM1MTFKM+CqFg8VKGsvjjmOZiBzhY0+rWzC44VEPdVgSE5goI+Z4u6mwfLoCsjfOaAd6nzEhihmhi+TTHRqIRk8iWK2OCoJRZY3fszSMHQzWYnUt+SvCk/JiX4fx8MNc1QPzWOpxqoARFWHveXTiplEzge8yXXzQxkCFl/M80grn2HWUli3vDuUW06vkO7c66flvWxM798HxzYNe0wXLyuTUgBZ9jSfY3g==
X-Scanned-By: mailmunge 3.09
Message-ID-Hash: MIIRFHX5YNZMG25HDJKWL44MVCTO2IIP
X-Message-ID-Hash: MIIRFHX5YNZMG25HDJKWL44MVCTO2IIP
X-MailFrom: peter@akayla.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-emu.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: emu-chairs@ietf.org, draft-dekok-emu-teapv2@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Emu] Re: Call for adoption: draft-dekok-emu-teapv2-03 (Ends 2026-05-26)
List-Id: "EAP Methods Update (EMU)" <emu.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/j9Z1lZWLMY7ca87LyC3RkTGp4cs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Owner: <mailto:emu-owner@ietf.org>
List-Post: <mailto:emu@ietf.org>
List-Subscribe: <mailto:emu-join@ietf.org>
List-Unsubscribe: <mailto:emu-leave@ietf.org>

TEAP v1 was originally specified in RFC 7170. RFC 7170bis (RFC 9930) specifies
how TEAP v1 actually was implemented and fielded. Here's our next shot at
TEAP, TEAP v2, which specifies how TEAP ought to work, based on many
learnings from our experiences with TEAP v1.

As currently given, Alan's I-D is not written as a standalone document. The
expectation is that at some point it will incorporate the text from TEAP v1
that carries over to v2. 

If you would like to see this document adopted, please reply to the call for
adoption with your thoughts. Expressions of willingness to review the work
would also be appreciated. Of course, if you think there shouldn't be a TEAP
v2, you're welcome to say that too!

		-Peter and Joe

On 5/12/26, 1:12 PM, "Peter Yee via Datatracker" <noreply@ietf.org> wrote:

This message starts a emu WG Call for Adoption of:
draft-dekok-emu-teapv2-03

This Working Group Call for Adoption ends on 2026-05-26

Abstract:
This document defines the Tunnel Extensible Authentication Protocol
(TEAP) version 2. It addresses a number of security and
interoperability issues which were found during the publication of
TEAPv1 ([I-D.ietf-emu-rfc7170bis]).

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the emu WG. Comments to explain your preference are
greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-dekok-emu-teapv2/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-dekok-emu-teapv2-03.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-dekok-emu-teapv2-03

_______________________________________________
Emu mailing list -- emu@ietf.org <mailto:emu@ietf.org>
To unsubscribe send an email to emu-leave@ietf.org <mailto:emu-leave@ietf.org>

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