📄 draft-ietf-simple-interdomain-scaling-analysis-00 - problem statement for sip-simple.htm
字号:
(A15) NOTIFY terminated......................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-40">40</A>
(A16) Number of sign-out messages.....................1,600,000
(A17) Total messages between domains.................70,400,000
(A18) Total number of messages / second...................2,444
(A19) Total number of bytes / second on the wire.........1968KB
<SPAN class=grey>Houri, et al. Expires August 30, 2007 [Page 13]</SPAN>
<A id=page-14 href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-14" name=page-14><SPAN class=break> </SPAN></A>
<SPAN class=grey>Internet-Draft Problem Statement for SIP/SIMPLE February 2007</SPAN>
Figure 3: Widely distributed inter-domain with no optimizations
(A01) Subscription lifetime (hours)...........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-8">8</A>
(A02) Presence state changes / hour...........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-3">3</A>
(A03) Subscription refresh interval / hour....................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-1">1</A>
(A04) Total federated presentities per watcher...............<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-20">20</A>
(A05) Number of dialogs to maintain per watcher...............<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-1">1</A>
(A06) Number of watchers in a federated presence domain..20,000
(A07) Initial SUBSCRIBE/200 per watcher.......................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A08) Initial NOTIFY/200 per watcher..........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A09) Total initial messages.............................80,000
(A10) NOTIFY/200 per watched presentity.....................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-960">960</A>
(A11) SUBSCRIBE/200 refreshes................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-16">16</A>
(A12) NOTIFY/200 due to subscribe refresh.....................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-0">0</A>
(A13) Number of steady state messages................19,520,000
(A14) SUBSCRIBE termination...................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A15) NOTIFY terminated.......................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A16) Number of sign-out messages........................80,000
(A17) Total messages between domains.................39,360,000
(A18) Total number of messages / second...................1,367
(A19) Total number of bytes / second on the wire..........571KB
Figure 4: Widely distributed inter-domain with optimizations
<SPAN class=h4><A name=section-3.6.2>3.6.2</A>. Associated inter-domain presence</SPAN>
In this type of environment, the domain is a collection of associated
users such as an enterprise. Here, federation is once again very
common. However, there is also a strong association between some
users in the deployment. These associations make it somewhat more
likely that users in that domain will be watchers of the same
presentity. This can occur because of business relationships (e.g.
two co-workers on a project federating with a partner company).
Common characteristics of this deployment are:
o Federated subscriptions are large minority or small majority of
subscription traffic
o Individual users are likely to subscribe to multiple users in any
one domain, especially their own
<SPAN class=grey>Houri, et al. Expires August 30, 2007 [Page 14]</SPAN>
<A id=page-15 href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-15" name=page-15><SPAN class=break> </SPAN></A>
<SPAN class=grey>Internet-Draft Problem Statement for SIP/SIMPLE February 2007</SPAN>
o The intersection of users in the deployment watching the same
presentities increases
This federation type has traffic rates similar to the previous
examples but with different levels of association of the users.
<SPAN class=h4><A name=section-3.6.3>3.6.3</A>. Very large network peering</SPAN>
In this environment, two or more very large networks create a peering
relationship allowing their users to subscribe to presence in the
other domains. Where as the number of users in other deployment
types ranges from hundreds to several hundred thousand, these large
networks host up to hundreds of millions of users. Examples of these
networks are large wireless carriers and consumer IM networks.
Common characteristics of this deployment are:
o As users become accustomed to network boundaries disappearing,
federated subscriptions become as common as subscriptions within
the same domain
o Individual users are highly likely to want to see presence of
multiple presentities in the peer network
o The intersection of users in the deployment watching the same
presentities is very high (i.e., two or more users in network A
are extremely likely to be watching a same user in network B)
o Status changes increase greatly due to typical observed consumer
behavior
The first table below provides the calculations without optimizations
the second table provides the calculations with optimizations. Even
though the optimizations help a lot (almost cut the number of
messages by half), the numbers are still very high. Note also that
the bandwidth required is very high (almost 1GB per second).
<SPAN class=grey>Houri, et al. Expires August 30, 2007 [Page 15]</SPAN>
<A id=page-16 href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-16" name=page-16><SPAN class=break> </SPAN></A>
<SPAN class=grey>Internet-Draft Problem Statement for SIP/SIMPLE February 2007</SPAN>
(A01) Subscription lifetime (hours)..............................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-8">8</A>
(A02) Presence state changes / hour..............................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-6">6</A>
(A03) Subscription refresh interval / hour.......................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-1">1</A>
(A04) Total federated presentities per watcher..................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-10">10</A>
(A05) Number of dialogs to maintain per watcher.................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-10">10</A>
(A06) Number of watchers in a federated presence domain.10,000,000
(A07) Initial SUBSCRIBE/200 per watcher.........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-20">20</A>
(A08) Initial NOTIFY/200 per watcher............................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-20">20</A>
(A09) Total initial messages...........................400,000,000
(A10) NOTIFY/200 per watched presentity........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-960">960</A>
(A11) SUBSCRIBE/200 refreshes..................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-160">160</A>
(A12) NOTIFY/200 due to subscribe refresh......................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-160">160</A>
(A13) Number of steady state messages...............12,800,000,000
(A14) SUBSCRIBE termination.....................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-20">20</A>
(A15) NOTIFY terminated.........................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-20">20</A>
(A16) Number of sign-out messages....................4,000,000,000
(A17) Total messages between domains................27,200,000,000
(A18) Total number of messages / second....................944,444
(A19) Total number of bytes / second on the wire.........880,555KB
Figure 5: Very large network peering with no optimizations
<SPAN class=grey>Houri, et al. Expires August 30, 2007 [Page 16]</SPAN>
<A id=page-17 href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-17" name=page-17><SPAN class=break> </SPAN></A>
<SPAN class=grey>Internet-Draft Problem Statement for SIP/SIMPLE February 2007</SPAN>
(A01) Subscription lifetime (hours)..............................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-8">8</A>
(A02) Presence state changes / hour..............................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-6">6</A>
(A03) Subscription refresh interval / hour.......................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-1">1</A>
(A04) Total federated presentities per watcher..................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-10">10</A>
(A05) Number of dialogs to maintain per watcher..................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-1">1</A>
(A06) Number of watchers in a federated presence domain.10,000,000
(A07) Initial SUBSCRIBE/200 per watcher..........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A08) Initial NOTIFY/200 per watcher.............................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A09) Total initial messages............................40,000,000
(A10) NOTIFY/200 per watched presentity........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-960">960</A>
(A11) SUBSCRIBE/200 refreshes...................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-16">16</A>
(A12) NOTIFY/200 due to subscribe refresh........................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-0">0</A>
(A13) Number of steady state messages................9,760,000,000
(A14) SUBSCRIBE termination......................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A15) NOTIFY terminated..........................................<A href="http://tools.ietf.org/html/draft-ietf-simple-interdomain-scaling-analysis-00#page-2">2</A>
(A16) Number of sign-out messages.......................40,000,000
(A17) Total messages between domains................19,680,000,000
(A18) Total number of messages / second....................683,333
(A19) Total number of bytes / second on the wire.........545,833KB
Figure 6: Very large network peering with optimizations
<SPAN class=h4><A name=section-3.6.4>3.6.4</A>. Intra-domain peering</SPAN>
Within a particular domain, multiple presence infrastructures are
deployed with users split between the two. This scenario is unique
in that federated messages do not pass outside the administrative
domain's network. The two infrastructures peer directly inside the
domain. A common example of this is an enterprise IT system with
multiple independent vendor presence solutions deployed(e.g., a
presence solution for desktop messaging deployed alongside a presence
solution for IP telephony).
Common characteristics of this deployment are
o The difference between subscriptions to presentities in one system
vs. the other are completely arbitrary. Any one presentity is as
likely to be homed on one infrastructure as the other
o Active users are almost guaranteed of subscribing to many use⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -