RFC 8866 on SDP: Session Description Protocol
rfc-editor@rfc-editor.org Wed, 20 January 2021 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 96B903A0ABB; Tue, 19 Jan 2021 16:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 16ZI0NreCNap; Tue, 19 Jan 2021 16:22:27 -0800 (PST)
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 0B9963A0C35; Tue, 19 Jan 2021 16:22:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B869AF40786; Tue, 19 Jan 2021 16:21:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8866 on SDP: Session Description Protocol
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, mmusic@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210120002154.B869AF40786@rfc-editor.org>
Date: Tue, 19 Jan 2021 16:21:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/nhx95HkQE2zqExesZ0ZQXYRKuwo>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 20 Jan 2021 00:22:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8866
Title: SDP: Session Description Protocol
Author: A. Begen,
P. Kyzivat,
C. Perkins,
M. Handley
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: ali.begen@networked.media,
pkyzivat@alum.mit.edu,
csp@csperkins.org,
m.handley@cs.ucl.ac.uk
Pages: 57
Obsoletes: RFC 4566
I-D Tag: draft-ietf-mmusic-rfc4566bis-37.txt
URL: https://www.rfc-editor.org/info/rfc8866
DOI: 10.17487/RFC8866
This memo defines the Session Description Protocol (SDP). SDP is
intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation. This document obsoletes RFC 4566.
This document is a product of the Multiparty Multimedia Session Control 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