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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The media-policy-dataset provides 3 different bandwidth limitations:

max-bw
max-session-bw
max-stream-bw

Comparing the description of these (section 7.3 et seq.) with the description of
the b= line in SDP (RFC 4566 section 5.8) turns up a lot of ambiguity in the
definitions.

It seems to me to be clear that the max-stream-bw number corresponds to the "b=AS:..." line
in an SDP media description -- the bandwidth used by one direction of one media
stream.

The max-session-bw seems to correspond to the "b=AS:..." line in the *session* description,
the total bandwidth used (in one direction) by the whole session.

The max-bw number is less clear.  It seems to be intended to limit the total bandwidth used
by an agent (across all of the sessions it participates in).  As such, it can't be translated to
an SDP attribute.

Conversely, the "b=CT:..." line in an SDP session description seems to be intended to
describe the total bandwidth used by a "conference" (whatever that is).  It's not clear
what the significance of that is exactly, since the agent in question may not be the conference
focus, and indeed, the session may not be part of a "conference".

Thoughts?

Dale
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP


[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux