[rfc-dist] RFC 8585 on Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service

rfc-editor@rfc-editor.org Fri, 03 May 2019 03:14 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBD171200DE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 2 May 2019 20:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 konRf5yh5zQR for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 2 May 2019 20:14:37 -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 954AD120058 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 2 May 2019 20:14:37 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8EF48B824FC; Thu, 2 May 2019 20:14:23 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 41962B824FA; Thu, 2 May 2019 20:14:22 -0700 (PDT)
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: <20190503031422.41962B824FA@rfc-editor.org>
Date: Thu, 2 May 2019 20:14:22 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8585_on_Requirements_for_IPv6_Customer_?= =?utf-8?q?Edge_Routers_to_Support_IPv4-as-a-Service?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, v6ops@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8585

        Title:      Requirements for IPv6 Customer Edge 
                    Routers to Support IPv4-as-a-Service 
        Author:     J. Palet Martinez, 
                    H. M.-H. Liu,
                    M. Kawashima
        Status:     Informational
        Stream:     IETF
        Date:       May 2019
        Mailbox:    jordi.palet@theipv6company.com, 
                    hans.liu@dlinkcorp.com, 
                    kawashimam@vx.jp.nec.com
        Pages:      21
        Characters: 49405
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-transition-ipv4aas-15.txt

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

        DOI:        10.17487/RFC8585

This document specifies the IPv4 service continuity requirements for
IPv6 Customer Edge (CE) routers that are provided either by the
service provider or by vendors who sell through the retail market.

Specifically, this document extends the basic requirements for IPv6
CE routers as described in RFC 7084 to allow the provisioning of IPv6
transition services for the support of IPv4-as-a-Service (IPv4aaS) by
means of new transition mechanisms.  The document only covers
IPv4aaS, i.e., transition technologies for delivering IPv4 in
IPv6-only access networks.  IPv4aaS is necessary because there aren't
sufficient IPv4 addresses available for every possible customer/
device.  However, devices or applications in the customer Local Area
Networks (LANs) may be IPv4-only or IPv6-only and still need to
communicate with IPv4-only services on the Internet.

This document is a product of the IPv6 Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org