RFC 8262 on Content-ID Header Field in the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Thu, 26 October 2017 00:22 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2832E13F4F1; Wed, 25 Oct 2017 17:22:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 S-SSArORY4Hg; Wed, 25 Oct 2017 17:22:20 -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 95EAB13968C; Wed, 25 Oct 2017 17:22:20 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DF193B80DE1; Wed, 25 Oct 2017 17:22:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8262 on Content-ID Header Field in the Session Initiation Protocol (SIP)
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
Message-Id: <20171026002216.DF193B80DE1@rfc-editor.org>
Date: Wed, 25 Oct 2017 17:22:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/xFIeVBP3E3V6hf9MBltWP9CoMy0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Oct 2017 00:22:22 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8262
Title: Content-ID Header Field in the
Session Initiation Protocol (SIP)
Author: C. Holmberg,
I. Sedlacek
Status: Standards Track
Stream: IETF
Date: October 2017
Mailbox: christer.holmberg@ericsson.com,
ivo.sedlacek@ericsson.com
Pages: 14
Characters: 26427
Updates: RFC 5621, RFC 5368, RFC 6442
I-D Tag: draft-ietf-sipcore-content-id-10.txt
URL: https://www.rfc-editor.org/info/rfc8262
DOI: 10.17487/RFC8262
This document specifies the Content-ID header field for usage in the
Session Initiation Protocol (SIP). This document also updates RFC
5621, which only allows a Content-ID URL to reference a body part
that is part of a multipart message-body. This update enables a
Content-ID URL to reference a complete message-body and metadata
provided by some additional SIP header fields.
This document updates RFC 5368 and RFC 6442 by clarifying their usage
of the SIP Content-ID header field.
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