STD 87, RFC 8201 on Path MTU Discovery for IP version 6

rfc-editor@rfc-editor.org Fri, 14 July 2017 17:38 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2532213146D; Fri, 14 Jul 2017 10:38:04 -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 UXKZro3wTMy2; Fri, 14 Jul 2017 10:38:00 -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 8EE98131600; Fri, 14 Jul 2017 10:38:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0702BB80D46; Fri, 14 Jul 2017 10:37:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 87, RFC 8201 on Path MTU Discovery for IP version 6
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
Message-Id: <20170714173757.0702BB80D46@rfc-editor.org>
Date: Fri, 14 Jul 2017 10:37:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pF7u90EAaJ0F96lGwZivW8PAgPU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 17:38:04 -0000

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

        STD 87        
        RFC 8201

        Title:      Path MTU Discovery for IP 
                    version 6 
        Author:     J. McCann, 
                    S. Deering,
                    J. Mogul,
                    R. Hinden, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2017
        Mailbox:    bob.hinden@gmail.com
        Pages:      19
        Characters: 42751
        Obsoletes:  RFC 1981
        See Also:   STD 87

        I-D Tag:    draft-ietf-6man-rfc1981bis-08.txt

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

        DOI:        10.17487/RFC8201

This document describes Path MTU Discovery (PMTUD) for IP version 6.
It is largely derived from RFC 1191, which describes Path MTU
Discovery for IP version 4.  It obsoletes RFC 1981.

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

This is now an Internet 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