RFC 8675 on A YANG Data Model for Tunnel Interface Types
rfc-editor@rfc-editor.org Sun, 17 November 2019 09:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F377F12008D; Sun, 17 Nov 2019 01:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 Fltpg2vF3326; Sun, 17 Nov 2019 01:00:29 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42FB312007A; Sun, 17 Nov 2019 01:00:29 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0598CF406D2; Sun, 17 Nov 2019 01:00:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8675 on A YANG Data Model for Tunnel Interface Types
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, softwires@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20191117090018.0598CF406D2@rfc-editor.org>
Date: Sun, 17 Nov 2019 01:00:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nYUX8TDVd27EMhQTmeLkXY5q4lA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Nov 2019 09:00:31 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8675
Title: A YANG Data Model for
Tunnel Interface Types
Author: M. Boucadair,
I. Farrer,
R. Asati
Status: Standards Track
Stream: IETF
Date: November 2019
Mailbox: mohamed.boucadair@orange.com,
ian.farrer@telekom.de,
rajiva@cisco.com
Pages: 16
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-softwire-iftunnel-07.txt
URL: https://www.rfc-editor.org/info/rfc8675
DOI: 10.17487/RFC8675
This document specifies the initial version of a YANG module
"iana-tunnel-type", which contains a collection of IANA-maintained
YANG identities used as interface types for tunnel interfaces. The
module reflects the "tunnelType" registry maintained by IANA. The
latest revision of this YANG module can be obtained from the IANA
website.
Tunnel type values are not directly added to the Tunnel Interface
Types YANG module; they must instead be added to the "tunnelType"
IANA registry. Once a new tunnel type registration is made by IANA
for a new tunneling scheme or even an existing one that is not
already listed in the current registry (e.g., LISP, NSH), IANA will
update the Tunnel Interface Types YANG module accordingly.
Some of the IETF-defined tunneling techniques are not listed in the
current IANA registry. It is not the intent of this document to
update the existing IANA registry with a comprehensive list of tunnel
technologies. Registrants must follow the IETF registration procedure
for interface types whenever a new tunnel type is needed.
This document is a product of the Softwires Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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