New Non-WG Mailing List: Lurk -- Limited Use of Remote Keys

IETF Secretariat <> Sat, 16 January 2016 00:54 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 2E38E1B34A0; Fri, 15 Jan 2016 16:54:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <>
To: IETF Announcement List <>
Subject: New Non-WG Mailing List: Lurk -- Limited Use of Remote Keys
X-Test-IDTracker: no
X-IETF-IDTracker: 6.12.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Fri, 15 Jan 2016 16:54:44 -0800
Archived-At: <>
Cc: <>, stephen.farrell@cs.tcd.iedaniel.migault,
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 16 Jan 2016 00:54:44 -0000

A new IETF non-working group email list has been created.

List address:
To subscribe:


Communication protocols like IPsec, SSH or TLS provide means to authenticate the remote peer. Authentication is based the proof of ownership of a private key. Currently most trust models assume the private key is associated and owned by the peer. In addition, the remote peer is both responsible of the hosted content and for the network delivery. Although these assumptions were largely true in the past, today, the deployment of service on the current Internet largely relies on multiple distributed instances of the service. Similarly, the delivery of popular content often splits the roles of providing the content and delivering the content. In such architectures, the application, - like a web browser - expects to authenticate a content provider while authenticating the node delivering the content. In this case, the confusion mostly results from using a secure transport layer to authenticate application layer content. There may be a BoF at IETF95 to discuss this topic.

For additional information, please contact the list administrators.