[rfc-dist] RFC 9268 on IPv6 Minimum Path MTU Hop-by-Hop Option

rfc-editor@rfc-editor.org Tue, 30 August 2022 04:41 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D31C1522D2; Mon, 29 Aug 2022 21:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sulUWIR713jW; Mon, 29 Aug 2022 21:41:35 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A871DC1522D4; Mon, 29 Aug 2022 21:41:35 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5964AC88BF; Mon, 29 Aug 2022 21:41:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: [rfc-dist] RFC 9268 on IPv6 Minimum Path MTU Hop-by-Hop Option
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: <20220830044135.5964AC88BF@rfcpa.amsl.com>
Date: Mon, 29 Aug 2022 21:41:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/c17KNTb0gWIfk6wAmmwdmzY9Sks>
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2022 04:41:39 -0000

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

        
        RFC 9268

        Title:      IPv6 Minimum Path MTU Hop-by-Hop Option 
        Author:     B. Hinden,
                    G. Fairhurst
        Status:     Experimental
        Stream:     IETF
        Date:       August 2022
        Mailbox:    bob.hinden@gmail.com,
                    gorry@erg.abdn.ac.uk
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-mtu-option-15.txt

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

        DOI:        10.17487/RFC9268

This document specifies a new IPv6 Hop-by-Hop Option that is used to
record the Minimum Path MTU (PMTU) along the forward path between a
source host to a destination host. The recorded value can then be
communicated back to the source using the return Path MTU field in
the Option.

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


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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