Protocol Action: 'A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 06 May 2004 17:27 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04422 for <ietf-announce-archive@ietf.org>; Thu, 6 May 2004 13:27:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLmeE-0006CL-Nd for ietf-announce-archive@ietf.org; Thu, 06 May 2004 13:27:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLmbq-0005Kt-00 for ietf-announce-archive@ietf.org; Thu, 06 May 2004 13:24:34 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLmaM-0004jo-00 for ietf-announce-archive@ietf.org; Thu, 06 May 2004 13:23:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLm5P-0000AI-Ms; Thu, 06 May 2004 12:51:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLkQ6-0004VK-QN for ietf-announce@optimus.ietf.org; Thu, 06 May 2004 11:04:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18838 for <ietf-announce@ietf.org>; Thu, 6 May 2004 11:04:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLkQ4-0007Tg-0R for ietf-announce@ietf.org; Thu, 06 May 2004 11:04:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLkP4-000712-00 for ietf-announce@ietf.org; Thu, 06 May 2004 11:03:15 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLkO9-0006Y2-00; Thu, 06 May 2004 11:02:17 -0400
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BLkMM-0002Xm-Rc; Thu, 06 May 2004 11:00:26 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, mmusic mailing list <mmusic@ietf.org>, mmusic chair <jo@acm.org>, mmusic chair <csp@csperkins.org>
Subject: Protocol Action: 'A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)' to Proposed Standard
Message-Id: <E1BLkMM-0002Xm-Rc@optimus.ietf.org>
Date: Thu, 06 May 2004 11:00:26 -0400
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'A Transport Independent Bandwidth Modifier for the Session Description 
   Protocol (SDP) '
   <draft-ietf-mmusic-sdp-bwparam-06.txt> as a Proposed Standard

This document is the product of the Multiparty Multimedia Session Control 
Working Group. 

The IESG contact persons are Jon Peterson and Allison Mankin.

Technical Summary
 
Although the Session Description Protocol (SDP) already has a "bandwidth" 
parameter(the b= line) to characterize the amount of bandwidth a particular 
session will require, it is difficult for the receiver of an SDP message to 
know what values the creator of SDP used to factor the overhead into the 
total session bandwidth value. This becomes especially problematic in the 
presence of middleboxes that convert between IPv4 and IPv6. The use of 
session header compression (such as cRTP) on a per-hop basis at the sender 
side can also confuse recipients of SDP, since the assessment of total 
bandwidth on the sender side will assume header compression that probably 
isn't available at the receiver side. Similar problems exist for calculating 
RTCP bandwidth.

Accordingly, this document defines a Transport Independent Application 
Specific Maximum (TIAS) bandwidith modifier that can appear in the b= line o
SDP, and a new attribute, "maxrate", that is correlated with SDP media (m=) 
lines. Together, these two parameters enable recipients of SDP to make a muc
more exact and universal assessment of the bandwidth that a session will 
require.
 
Working Group Summary
 
This MMUSIC Working Group supported the advancement of this specification.
 
Protocol Quality
 
This document has been reviewed for the IESG by Jon Peterson.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce