Re: draft-ietf-sipping-media-policy-dataset: Bandwidth limitations
"Worley, Dale R (Dale)" <[email protected]> Tue, 10 May 2011 15:54:27 -0400
| Newsgroups | gmane.ietf.sipping |
|---|---|
| Message-ID | <CD5674C3CD99574EBA7432465FC13C1B22246BD47A@DC-US1MBEX4.global.avaya.com> |
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
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email protected] for questions on current sip
Use [email protected] for new developments of core SIP