[perpass] Fwd: RFC 7619 on The NULL Authentication Method in the Internet Key Exchange Protocol Version 2 (IKEv2)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 27 August 2015 12:24 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F9A1B2B58 for <perpass@ietfa.amsl.com>; Thu, 27 Aug 2015 05:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 D_TdyddrnMVd for <perpass@ietfa.amsl.com>; Thu, 27 Aug 2015 05:24:26 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F11E1B29F8 for <perpass@ietf.org>; Thu, 27 Aug 2015 05:24:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AFA34BE9C for <perpass@ietf.org>; Thu, 27 Aug 2015 13:24:24 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJ7kCG8GPK1E for <perpass@ietf.org>; Thu, 27 Aug 2015 13:24:24 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8514FBE98 for <perpass@ietf.org>; Thu, 27 Aug 2015 13:24:24 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1440678264; bh=WEZEogJGPShb0cfz9RZsvdLxG7+iRmTLBRuY7O8qLKQ=; h=Date:From:To:Subject:References:In-Reply-To:From; b=RAAP0NKZgoXcjJ/3ZSNJqj4Dcdn1u7AA+sA0sQh0jbIJ2kip0qD9hV9tMkQR7tfRx MhuVgOS82MVtUauMtWGMnDHKuBIKwazo9LbG/FTFTB8k+3soCQPFO0LF3lBFPt0qJS abkNetuNS8z9ZSOM/CWOQc3ArXvKyRvUffnlSLLo=
Message-ID: <55DF0178.2020301@cs.tcd.ie>
Date: Thu, 27 Aug 2015 13:24:24 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: perpass <perpass@ietf.org>
References: <20150827025452.1530D18046D@rfc-editor.org>
In-Reply-To: <20150827025452.1530D18046D@rfc-editor.org>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
X-Forwarded-Message-Id: <20150827025452.1530D18046D@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/py1WSq1hWOa5KPf8c3k7XSqkk58>
Subject: [perpass] Fwd: RFC 7619 on The NULL Authentication Method in the Internet Key Exchange Protocol Version 2 (IKEv2)
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2015 12:24:28 -0000

I think this was also initially suggested on this list, so
another loop closing ceremony is due :-)

Cheers,
S.

PS: I've not posted similarly on the DPRIVE RFC7626 as I
think starting DPRIVE was the loop closing for that, but
7626 is a fine thing as well.



-------- Forwarded Message --------
Subject: RFC 7619 on The NULL Authentication Method in the Internet Key
Exchange Protocol Version 2 (IKEv2)
Date: Wed, 26 Aug 2015 19:54:52 -0700 (PDT)
From: rfc-editor@rfc-editor.org
Reply-To: ietf@ietf.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: ipsec@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org

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


        RFC 7619

        Title:      The NULL Authentication Method in
                    the Internet Key Exchange Protocol Version
                    2 (IKEv2)
        Author:     V. Smyslov, P. Wouters
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2015
        Mailbox:    svan@elvis.ru,
                    pwouters@redhat.com
        Pages:      12
        Characters: 24593
        Updates:    RFC 4301

        I-D Tag:    draft-ietf-ipsecme-ikev2-null-auth-07.txt

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

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

This document specifies the NULL Authentication method and the
ID_NULL Identification Payload ID Type for Internet Key Exchange
Protocol version 2 (IKEv2).  This allows two IKE peers to establish
single-side authenticated or mutual unauthenticated IKE sessions for
those use cases where a peer is unwilling or unable to authenticate
or identify itself.  This ensures IKEv2 can be used for Opportunistic
Security (also known as Opportunistic Encryption) to defend against
Pervasive Monitoring attacks without the need to sacrifice anonymity.

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