[sipcore] RFC 8787 on Location Source Parameter for the SIP Geolocation Header Field
rfc-editor@rfc-editor.org Sun, 31 May 2020 20:59 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 759F53A0CD1; Sun, 31 May 2020 13:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NnCN_ErO_oSx; Sun, 31 May 2020 13:59:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDD853A0CCB; Sun, 31 May 2020 13:59:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C16FBF406F6; Sun, 31 May 2020 13:59:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, sipcore@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200531205918.C16FBF406F6@rfc-editor.org>
Date: Sun, 31 May 2020 13:59:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/KvFtXnaoJUaIwPA451UyCYapfg4>
Subject: [sipcore] RFC 8787 on Location Source Parameter for the SIP Geolocation Header Field
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 May 2020 20:59:37 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8787 Title: Location Source Parameter for the SIP Geolocation Header Field Author: J. Winterbottom, R. Jesske, B. Chatras, A. Hutton Status: Standards Track Stream: IETF Date: May 2020 Mailbox: a.james.winterbottom@gmail.com, r.jesske@telekom.de, bruno.chatras@orange.com, andrew.hutton@atos.net Pages: 8 Updates: RFC 6442 I-D Tag: draft-ietf-sipcore-locparam-06.txt URL: https://www.rfc-editor.org/info/rfc8787 DOI: 10.17487/RFC8787 There are some circumstances where a Geolocation header field may contain more than one locationValue. Knowing the identity of the node adding the locationValue allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the locationValues. This document defines the "loc-src" parameter so that the entity adding the locationValue to the Geolocation header field can identify itself using its hostname. This document updates RFC 6442. This document is a product of the Session Initiation Protocol Core 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/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