[Sipping] draft-ietf-sipping-media-policy-dataset: Bandwidth directionality
"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 07 March 2011 22:13 UTC
Return-Path: <dworley@avaya.com>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C13D3A6820 for <sipping@core3.amsl.com>; Mon, 7 Mar 2011 14:13:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level:
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=-0.554, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_18=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p13Nl+qluCj7 for <sipping@core3.amsl.com>; Mon, 7 Mar 2011 14:13:27 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 6A0FA3A67B4 for <sipping@ietf.org>; Mon, 7 Mar 2011 14:13:27 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHfndE2HCzI1/2dsb2JhbACmV3SkYAKZXYViBIUcinE
X-IronPort-AV: E=Sophos;i="4.62,279,1297054800"; d="scan'208";a="62298077"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 07 Mar 2011 17:14:41 -0500
X-IronPort-AV: E=Sophos;i="4.62,279,1297054800"; d="scan'208";a="612705341"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Mar 2011 17:14:40 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Mon, 7 Mar 2011 17:14:40 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "sipping@ietf.org" <sipping@ietf.org>
Date: Mon, 07 Mar 2011 17:11:00 -0500
Thread-Topic: draft-ietf-sipping-media-policy-dataset: Bandwidth directionality
Thread-Index: AQHL3RUNafBx19X2g0mVkymy0YZjuQ==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C1555@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Sipping] draft-ietf-sipping-media-policy-dataset: Bandwidth directionality
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 22:13:28 -0000
One problem I'm noticing is that the session-policy XML allows specifying the bandwidth in each direction, but SDP does not (as far as I can tell). How should we resolve this? Should we define directional bandwidth modifiers in SDP? Or should we restrict bandwidth in a stream based on the directionality attributes of the stream? That is, if the sending bandwidth is limited to 10,000 and the receiving bandwidth is limited to 100,000, then an a=sendrecv stream would be have b=10000 but an a=recv stream would have b=100000. Dale
- [Sipping] draft-ietf-sipping-media-policy-dataset… Worley, Dale R (Dale)
- Re: [Sipping] draft-ietf-sipping-media-policy-dat… Worley, Dale R (Dale)