RFC 9028 on Native NAT Traversal Mode for the Host Identity Protocol

rfc-editor@rfc-editor.org Thu, 15 July 2021 19:45 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 1B22E3A0D01; Thu, 15 Jul 2021 12:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id WupsUGV_9dmT; Thu, 15 Jul 2021 12:45:41 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 534723A0CD4; Thu, 15 Jul 2021 12:45:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CCA41F40721; Thu, 15 Jul 2021 12:45:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwMjggb24gTmF0aXZlIE5BVCBUcmF2ZXJzYWwgTW9kZSBmb3IgdGhlIEhvc3QgSWRlbnRpdHkgUHJvdG9jb2w=?=
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, hipsec@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210715194535.CCA41F40721@rfc-editor.org>
Date: Thu, 15 Jul 2021 12:45:35 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dCPrxuPBVl_uNwa0qnmbBFkfr78>
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: Thu, 15 Jul 2021 19:45:51 -0000

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

        RFC 9028

        Title:      Native NAT Traversal Mode for 
                    the Host Identity Protocol 
        Author:     A. Keränen,
                    J. Melén,
                    M. Komu, Ed.
        Status:     Experimental
        Stream:     IETF
        Date:       July 2021
        Mailbox:    ari.keranen@ericsson.com,
        Pages:      55
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hip-native-nat-traversal-33.txt

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

        DOI:        10.17487/RFC9028

This document specifies a new Network Address Translator (NAT)
traversal mode for the Host Identity Protocol (HIP). The new mode is
based on the Interactive Connectivity Establishment (ICE) methodology
and UDP encapsulation of data and signaling traffic. The main
difference from the previously specified modes is the use of HIP
messages instead of ICE for all NAT traversal procedures due to the
kernel-space dependencies of HIP.

This document is a product of the Host Identity Protocol 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

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