[Softwires] RFC 8026 on Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization Mechanism
rfc-editor@rfc-editor.org Wed, 16 November 2016 07:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E241295AB; Tue, 15 Nov 2016 23:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level:
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 dxJ-Hww_YgLl; Tue, 15 Nov 2016 23:00:02 -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 D20F8129694; Tue, 15 Nov 2016 22:59:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CBC7BB800CB; Tue, 15 Nov 2016 22:59:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161116065952.CBC7BB800CB@rfc-editor.org>
Date: Tue, 15 Nov 2016 22:59:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/CdkuqzzSv1nm_aCSf_EBxv7ekSw>
Cc: softwires@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [Softwires] RFC 8026 on Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization Mechanism
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2016 07:00:04 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8026
Title: Unified IPv4-in-IPv6 Softwire Customer Premises
Equipment (CPE): A DHCPv6-Based Prioritization
Mechanism
Author: M. Boucadair, I. Farrer
Status: Standards Track
Stream: IETF
Date: November 2016
Mailbox: mohamed.boucadair@orange.com,
ian.farrer@telekom.de
Pages: 11
Characters: 22857
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-softwire-unified-cpe-08.txt
URL: https://www.rfc-editor.org/info/rfc8026
DOI: http://dx.doi.org/10.17487/RFC8026
In IPv6-only provider networks, transporting IPv4 packets
encapsulated in IPv6 is a common solution to the problem of IPv4
service continuity. A number of differing functional approaches have
been developed for this, each having their own specific
characteristics. As these approaches share a similar functional
architecture and use the same data plane mechanisms, this memo
specifies a DHCPv6 option, whereby a single instance of Customer
Premises Equipment (CPE) can interwork with all of the standardized
and proposed approaches to providing encapsulated IPv4-in-IPv6
services by providing a prioritization mechanism.
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