[MMUSIC] RFC 8859 on A Framework for Session Description Protocol (SDP) Attributes When Multiplexing
rfc-editor@rfc-editor.org Tue, 19 January 2021 00:46 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 6BF053A0DEB;
Mon, 18 Jan 2021 16:46:29 -0800 (PST)
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 QsYDYW2I-6Rf; Mon, 18 Jan 2021 16:46: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 CA2E53A0D3F;
Mon, 18 Jan 2021 16:46:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30)
id 63194F407A9; Mon, 18 Jan 2021 16:46:12 -0800 (PST)
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, mmusic@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210119004612.63194F407A9@rfc-editor.org>
Date: Mon, 18 Jan 2021 16:46:12 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ucw0jKu2_0hvQ5jyiFGZvb7Ov4E>
Subject: [MMUSIC] =?utf-8?q?RFC_8859_on_A_Framework_for_Session_Descripti?=
=?utf-8?q?on_Protocol_=28SDP=29_Attributes_When_Multiplexing?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>,
<mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>,
<mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 00:46:33 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8859
Title: A Framework for Session Description
Protocol (SDP) Attributes When Multiplexing
Author: S. Nandakumar
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: snandaku@cisco.com
Pages: 82
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mmusic-sdp-mux-attributes-19.txt
URL: https://www.rfc-editor.org/info/rfc8859
DOI: 10.17487/RFC8859
The purpose of this specification is to provide a framework for
analyzing the multiplexing characteristics of Session Description
Protocol (SDP) attributes when SDP is used to negotiate the usage of
a single 5-tuple for sending and receiving media associated with
multiple media descriptions.
This specification also categorizes the existing SDP attributes based
on the framework described herein.
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