RFC 9063 on Host Identity Protocol Architecture

rfc-editor@rfc-editor.org Thu, 15 July 2021 19:46 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 C0D553A0CC5; Thu, 15 Jul 2021 12:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id huLU3CTJKPiz; Thu, 15 Jul 2021 12:46:23 -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 738DF3A0D25; Thu, 15 Jul 2021 12:46:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F16E4F40722; Thu, 15 Jul 2021 12:46:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwNjMgb24gSG9zdCBJZGVudGl0eSBQcm90b2NvbCBBcmNoaXRlY3R1cmU=?=
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: <20210715194611.F16E4F40722@rfc-editor.org>
Date: Thu, 15 Jul 2021 12:46:11 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-y-ix0elHKOdiR4ZYnLIsk8F680>
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:46:36 -0000

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

        RFC 9063

        Title:      Host Identity Protocol Architecture 
        Author:     R. Moskowitz, Ed.,
                    M. Komu
        Status:     Informational
        Stream:     IETF
        Date:       July 2021
        Mailbox:    rgm@labs.htt-consult.com,
        Pages:      41
        Obsoletes:  RFC 4423

        I-D Tag:    draft-ietf-hip-rfc4423-bis-20.txt

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

        DOI:        10.17487/RFC9063

This memo describes the Host Identity (HI) namespace, which provides
a cryptographic namespace to applications, and the associated
protocol layer, the Host Identity Protocol, located between the
internetworking and transport layers, that supports end-host
mobility, multihoming, and NAT traversal. Herein are presented the
basics of the current namespaces, their strengths and weaknesses, and
how a HI namespace will add completeness to them. The roles of the HI
namespace in the protocols are defined. 

This document obsoletes RFC 4423 and addresses the concerns raised by
the IESG, particularly that of crypto agility. The Security
Considerations section also describes measures against flooding
attacks, usage of identities in access control lists, weaker types of
identifiers, and trust on first use. This document incorporates
lessons learned from the implementations of RFC 7401 and goes further
to explain how HIP works as a secure signaling channel.

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

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