RFC 7378 on Trustworthy Location

rfc-editor@rfc-editor.org Thu, 18 December 2014 03:59 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 51C241A014D; Wed, 17 Dec 2014 19:59:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 09SDIR4LgtU2; Wed, 17 Dec 2014 19:59:52 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 63EFD1A014C; Wed, 17 Dec 2014 19:59:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D141D181243; Wed, 17 Dec 2014 19:59:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7378 on Trustworthy Location
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141218035930.D141D181243@rfc-editor.org>
Date: Wed, 17 Dec 2014 19:59:30 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/WXgmInqbN_zbPhCF26UZtt-_qT4
Cc: drafts-update-ref@iana.org, ecrit@ietf.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: Thu, 18 Dec 2014 03:59:54 -0000

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

        
        RFC 7378

        Title:      Trustworthy Location 
        Author:     H. Tschofenig, H. Schulzrinne,
                    B. Aboba, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       December 2014
        Mailbox:    Hannes.Tschofenig@gmx.net, 
                    hgs@cs.columbia.edu, 
                    Bernard_Aboba@hotmail.com
        Pages:      31
        Characters: 75402
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ecrit-trustworthy-location-14.txt

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

The trustworthiness of location information is critically important
for some location-based applications, such as emergency calling or
roadside assistance.

This document describes threats to conveying location, particularly
for emergency calls, and describes techniques that improve the
reliability and security of location information.  It also provides
guidelines for assessing the trustworthiness of location information.

This document is a product of the Emergency Context Resolution with Internet Technologies 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
  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