RFC 7949 on OSPFv3 over IPv4 for IPv6 Transition
rfc-editor@rfc-editor.org Wed, 10 August 2016 16:13 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 8925312D739; Wed, 10 Aug 2016 09:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.869
X-Spam-Level:
X-Spam-Status: No, score=-103.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=unavailable 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 cKIqvSDm1p1E; Wed, 10 Aug 2016 09:13:28 -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 A848812D6AE; Wed, 10 Aug 2016 09:06:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9077BB80FCE; Wed, 10 Aug 2016 09:06:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7949 on OSPFv3 over IPv4 for IPv6 Transition
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160810160603.9077BB80FCE@rfc-editor.org>
Date: Wed, 10 Aug 2016 09:06:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/DilsyruiYaFgEnJJLJ2gnCAd5lo>
Cc: drafts-update-ref@iana.org, ospf@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Wed, 10 Aug 2016 16:13:29 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7949
Title: OSPFv3 over IPv4 for IPv6 Transition
Author: I. Chen, A. Lindem, R. Atkinson
Status: Standards Track
Stream: IETF
Date: August 2016
Mailbox: ichen@kuatrotech.com,
acee@cisco.com,
rja.lists@gmail.com
Pages: 11
Characters: 25554
Updates: RFC 5838
I-D Tag: draft-ietf-ospf-transition-to-ospfv3-12.txt
URL: https://www.rfc-editor.org/info/rfc7949
DOI: http://dx.doi.org/10.17487/RFC7949
This document defines a mechanism to use IPv4 to transport OSPFv3
packets. Using OSPFv3 over IPv4 with the existing OSPFv3 Address
Family extension can simplify transition from an OSPFv2 IPv4-only
routing domain to an OSPFv3 dual-stack routing domain. This document
updates RFC 5838 to support virtual links in the IPv4 unicast address
family when using OSPFv3 over IPv4.
This document is a product of the Open Shortest Path First IGP 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