[Teas] RFC 10057 on A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces

rfc-editor@rfc-editor.org Wed, 18 November 2026 23:52 UTC

Received: by mx.ietf.org (Postfix) id CAC2547; Wed, 18 Nov 2026 23:52:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rfc-editor.org; s=mail; t=1795045953; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=NAtfpolPfaiHDTWb8SuzZ0DPmD+DfRxRrpxhE6cGgys=; b=BtBeI1su9k/Ll6yNMI4WwUk/VbSyMuDppWTQZtLvRHJfq5m2agbWLCltkFcE8L2VZVtN3s Guwj+i3mg4HQ0LipNpDBa1Lyi6dl14pJHjUHvNbXBbQhvZPh1z6b94TPryK/CgIE86LIAK FpPEaDnOf8J8Ee8J0UqZnihtiNyYzgw=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=rfc-editor@rfc-editor.org
Received: from celery-5795455977-22gr4 (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 99FCE13C232D2; Wed, 18 Nov 2026 15:52:32 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Wed, 18 Nov 2026 23:52:32 -0000
message-id: <179504595251.16.1186131134729338367@rfc-editor.org>
Message-ID-Hash: OTVJJA4LVYKHXUOV6WGJS5YLK2A6XG2H
X-Message-ID-Hash: OTVJJA4LVYKHXUOV6WGJS5YLK2A6XG2H
X-MailFrom: rfc-editor@rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-teas.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Teas] RFC 10057 on A YANG Data Model for Traffic Engineering Tunnels, Label Switched Paths, and Interfaces
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Z-ad8X0fb3pGUMaCxbjHBz9Xp34>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

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

        RFC 10057

        Title:      A YANG Data Model for Traffic Engineering Tunnels, 
                    Label Switched Paths, and Interfaces
        Author:     T. Saad,
                    R. Gandhi,
                    X. Liu,
                    V. P. Beeram,
                    I. Bryskin
        Status:     Proposed Standard
        Stream:     IETF
        Date:       November 2026
        Mailbox:    tsaad.net@gmail.com,
                    rgandhi@cisco.com,
                    xufeng.liu.ietf@gmail.com,
                    vbeeram@juniper.net
                    i_bryskin@yahoo.com
        Pages:      100


        I-D Tag:    draft-ietf-teas-yang-te-44

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

        DOI:        10.17487/RFC10057

This document defines a YANG data model for the provisioning and management of 
Traffic Engineering (TE) tunnels, Label Switched Paths (LSPs), and interfaces. 
The model covers data pertinent to TE tunnels, TE LSPs, and TE interfaces that are 
independent of any technology or data plane encapsulation. The model is divided into 
two YANG modules that address both device-specific and device-independent data, 
supporting configuration, operational state, Remote Procedure Calls (RPCs), 
and event notifications.

This document is a product of the Traffic Engineering Architecture and 
Signaling Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/

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