RFC 7383 on Internet Key Exchange Protocol Version 2 (IKEv2) Message Fragmentation

rfc-editor@rfc-editor.org Fri, 07 November 2014 01:32 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 5B2B51ACE5D; Thu, 6 Nov 2014 17:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.496
X-Spam-Level:
X-Spam-Status: No, score=-107.496 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, 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 0hfLlPRCyJRl; Thu, 6 Nov 2014 17:31:59 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 285C01ACE4D; Thu, 6 Nov 2014 17:31:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DDD2E181C99; Thu, 6 Nov 2014 17:31:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7383 on Internet Key Exchange Protocol Version 2 (IKEv2) Message Fragmentation
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141107013143.DDD2E181C99@rfc-editor.org>
Date: Thu, 06 Nov 2014 17:31:43 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/5xVjsENkyfCqLYkyGHYwu_pB5FU
Cc: ipsec@ietf.org, drafts-update-ref@iana.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: <http://www.ietf.org/mail-archive/web/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, 07 Nov 2014 01:32:04 -0000

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

        
        RFC 7383

        Title:      Internet Key Exchange Protocol Version 
                    2 (IKEv2) Message Fragmentation 
        Author:     V. Smyslov
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2014
        Mailbox:    svan@elvis.ru
        Pages:      20
        Characters: 47354
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipsecme-ikev2-fragmentation-10.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7383.txt

This document describes a way to avoid IP fragmentation of large
Internet Key Exchange Protocol version 2 (IKEv2) messages.  This
allows IKEv2 messages to traverse network devices that do not allow
IP fragments to pass through.

This document is a product of the IP Security Maintenance and Extensions 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/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