RFC 7690 on Close Encounters of the ICMP Type 2 Kind (Near Misses with ICMPv6 Packet Too Big (PTB))

rfc-editor@rfc-editor.org Fri, 22 January 2016 18:51 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2BAB1B2BE7; Fri, 22 Jan 2016 10:51:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 Wy6A2spuofSC; Fri, 22 Jan 2016 10:51:31 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6836A1AD36B; Fri, 22 Jan 2016 10:51:31 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0F208180206; Fri, 22 Jan 2016 10:50:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7690 on Close Encounters of the ICMP Type 2 Kind (Near Misses with ICMPv6 Packet Too Big (PTB))
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160122185013.0F208180206@rfc-editor.org>
Date: Fri, 22 Jan 2016 10:50:13 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/tWME50AZMkz__ph5m4Y3GPdM3dM>
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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, 22 Jan 2016 18:51:32 -0000

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

        
        RFC 7690

        Title:      Close Encounters of the ICMP Type 2 Kind 
                    (Near Misses with ICMPv6 Packet Too Big (PTB)) 
        Author:     M. Byerly,
                    M. Hite,
                    J. Jaeggli
        Status:     Informational
        Stream:     IETF
        Date:       January 2016
        Mailbox:    suckawha@gmail.com, 
                    mhite@hotmail.com, 
                    joelja@gmail.com
        Pages:      9
        Characters: 19061
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-pmtud-ecmp-problem-06.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7690

This document calls attention to the problem of delivering ICMPv6
type 2 "Packet Too Big" (PTB) messages to the intended destination
(typically the server) in ECMP load-balanced or anycast network
architectures.  It discusses operational mitigations that can be
employed to address this class of failures.

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/rfc.html

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