RFC 8781 on Discovering PREF64 in Router Advertisements

rfc-editor@rfc-editor.org Fri, 24 April 2020 18:37 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 86C863A0437; Fri, 24 Apr 2020 11:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7qKcVv6Uo5SD; Fri, 24 Apr 2020 11:37:50 -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 DCA2A3A041E; Fri, 24 Apr 2020 11:37:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4AD4CF406C3; Fri, 24 Apr 2020 11:37:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3ODEgb24gRGlzY292ZXJpbmcgUFJFRjY0IGluIFJvdXRlciBBZHZlcnRpc2VtZW50cw==?=
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, ipv6@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200424183742.4AD4CF406C3@rfc-editor.org>
Date: Fri, 24 Apr 2020 11:37:42 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/P0a8B8LgHwpEvZRW48N79B7Uleg>
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: Fri, 24 Apr 2020 18:37:54 -0000

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

        
        RFC 8781

        Title:      Discovering PREF64 in Router Advertisements 
        Author:     L. Colitti,
                    J. Linkova
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2020
        Mailbox:    lorenzo@google.com, 
                    furry@google.com
        Pages:      10
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-ra-pref64-09.txt

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

        DOI:        10.17487/RFC8781

This document specifies a Neighbor Discovery option to be used in
Router Advertisements (RAs) to communicate prefixes of Network
Address and Protocol Translation from IPv6 clients to IPv4 servers
(NAT64) to hosts.

This document is a product of the IPv6 Maintenance 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