IETF Logo Mail Archive

Re: [Sipping] draft-ietf-sipping-media-policy-dataset: Bandwidth limitations

"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 10 May 2011 19:57 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipping@ietfa.amsl.com
Delivered-To: sipping@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 907B0E0711 for <sipping@ietfa.amsl.com>; Tue, 10 May 2011 12:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.021
X-Spam-Level:
X-Spam-Status: No, score=-100.021 tagged_above=-999 required=5 tests=[AWL=-2.422, BAYES_00=-2.599, GB_SUMOF=5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gO4qW9h6NsZh for <sipping@ietfa.amsl.com>; Tue, 10 May 2011 12:57:18 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 53DAAE06AE for <sipping@ietf.org>; Tue, 10 May 2011 12:57:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHmXyU2HCzI1/2dsb2JhbACmC3erSwKbfoYPBJQ0ijY
X-IronPort-AV: E=Sophos;i="4.64,347,1301889600"; d="scan'208";a="187755413"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 10 May 2011 15:57:16 -0400
X-IronPort-AV: E=Sophos;i="4.64,347,1301889600"; d="scan'208";a="650060469"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 May 2011 15:57:16 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 10 May 2011 15:57:15 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, "sipping@ietf.org" <sipping@ietf.org>
Date: Tue, 10 May 2011 15:54:27 -0400
Thread-Topic: draft-ietf-sipping-media-policy-dataset: Bandwidth limitations
Thread-Index: AQHMDn78Hk6A5FQJT0WMWQEIG2PSDJSGeyWD
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22246BD47A@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B22246BD46F@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22246BD46F@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: Re: [Sipping] draft-ietf-sipping-media-policy-dataset: Bandwidth limitations
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 10 May 2011 19:57:19 -0000

I see commented-out text about these bandwidth descriptions:

    The <max-bw-ti> Element

      The <max-bw-ti> element defined as the <max-bw>
      element with the following exceptions.
      
      The given bandwidth limit is transport independent and
      therefore does not include include the bandwidth needed for
      lower-layer transport and network protocols (e.g., UDP and
      IP).

      The bandwidth limit is given in bits per second (i.e., not in 
      kilobits per second).

      The <max-bw-ti> element MAY have the following
      attribute (see <xref target="sec_attributes" />): pprate.  

   The maxprate attribute

      The <max-bw-ti> element has an optional attribute
      'maxprate'. The "maxprate" value is the maximum packet rate
      calculated over all the declared media streams.  If this can't
      be measured (stored media) or estimated (live), the sum of all
      media level values provides a ceiling value.

      All other attributes and merging rules are defined as for the 
      <max-bw> element.

Do people think these data are significant, or can they be safely omitted from
the media-policy-dataset?

Dale

v2.23.0 | Report a Bug | By Email