RFC 8159 on Keyed IPv6 Tunnel
rfc-editor@rfc-editor.org Sat, 06 May 2017 03:43 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 88CE5128D16 for <ietf-announce@ietfa.amsl.com>; Fri, 5 May 2017 20:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 mICG4NRhq6pG for <ietf-announce@ietfa.amsl.com>; Fri, 5 May 2017 20:43:56 -0700 (PDT)
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 01F9A128B91 for <ietf-announce@ietf.org>; Fri, 5 May 2017 20:43:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 64F26B80EB0; Fri, 5 May 2017 20:43:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8159 on Keyed IPv6 Tunnel
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
Message-Id: <20170506034350.64F26B80EB0@rfc-editor.org>
Date: Fri, 05 May 2017 20:43:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Ow5foxPZS1Ukn1Jyl2fJkd5e7nM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 06 May 2017 03:43:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8159
Title: Keyed IPv6 Tunnel
Author: M. Konstantynowicz, Ed.,
G. Heron, Ed.,
R. Schatzmayr,
W. Henderickx
Status: Standards Track
Stream: IETF
Date: May 2017
Mailbox: maciek@cisco.com,
giheron@cisco.com,
rainer.schatzmayr@telekom.de,
wim.henderickx@alcatel-lucent.com
Pages: 12
Characters: 27302
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l2tpext-keyed-ipv6-tunnel-07.txt
URL: https://www.rfc-editor.org/info/rfc8159
DOI: 10.17487/RFC8159
This document describes a tunnel encapsulation for Ethernet over IPv6
with a mandatory 64-bit cookie for connecting Layer 2 (L2) Ethernet
attachment circuits identified by IPv6 addresses. The encapsulation
is based on the Layer 2 Tunneling Protocol Version 3 (L2TPv3) over IP
and does not use the L2TPv3 control plane.
This document is a product of the Layer Two Tunneling Protocol Extensions 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
- RFC 8159 on Keyed IPv6 Tunnel rfc-editor