89:
51:
with the session, performing congestion control by adjusting the set of joined channels associated with the session in response to detected congestion, and using the packets to reliably reconstruct objects. All information flow in an ALC session is in the form of data packets sent by a single sender to channels that receivers join to receive data.
54:
ALC does specify the
Session Description needed by receivers before they join a session, but the mechanisms by which receivers obtain this required information is outside the scope of ALC. An application that uses ALC may require that receivers report statistics on their reception experience back to
50:
The sender side of ALC consists of generating packets based on objects to be delivered within the session and sending the appropriately formatted packets at the appropriate rates to the channels associated with the session. The receiver side of ALC consists of joining appropriate channels associated
46:
Because ALC is focused on reliable content delivery, the goal is to deliver objects as quickly as possible to each receiver while at the same time remaining network friendly to competing traffic. Thus, the congestion control used in conjunction with ALC should strive to maximize use of available
42:
as the underlying network service. Massive scalability in this context means the number of concurrent receivers for an object is potentially in the millions, the aggregate size of objects to be delivered in a session ranges from hundreds of kilobytes to hundreds of gigabytes, each receiver can
55:
the sender, but the mechanisms by which receivers report back statistics is outside the scope of ALC. In general, ALC is designed to be a minimal protocol instantiation that provides reliable content delivery without unnecessary limitations to the scalability of the basic protocol.
43:
initiate reception of an object asynchronously, the reception rate of each receiver in the session is the maximum fair bandwidth available between that receiver and the sender, and all of this can be supported using a single sender.
126:
47:
bandwidth between receivers and the sender while at the same time backing off aggressively in the face of competing traffic.
69:
27:
for content delivery in a reliable, massively scalable, multiple-rate, and congestion-controlled manner. Specified in
145:
119:
150:
112:
88:
24:
96:
74:
139:
28:
38:
The protocol is specifically designed to provide massive scalability using IP
39:
32:
64:
100:
120:
8:
127:
113:
65:Tampere University of Technology MAD/TUT
7:
85:
83:
95:This Internet-related article is a
99:. You can help Knowledge (XXG) by
14:
87:
1:
17:Asynchronous Layered Coding
167:
82:
35:proposed standard.
146:Internet protocols
108:
107:
25:Internet protocol
158:
129:
122:
115:
91:
84:
166:
165:
161:
160:
159:
157:
156:
155:
136:
135:
134:
133:
80:
61:
59:Implementations
12:
11:
5:
164:
162:
154:
153:
151:Internet stubs
148:
138:
137:
132:
131:
124:
117:
109:
106:
105:
92:
78:
77:
72:
67:
60:
57:
13:
10:
9:
6:
4:
3:
2:
163:
152:
149:
147:
144:
143:
141:
130:
125:
123:
118:
116:
111:
110:
104:
102:
98:
93:
90:
86:
81:
76:
73:
71:
68:
66:
63:
62:
58:
56:
52:
48:
44:
41:
36:
34:
30:
26:
22:
18:
101:expanding it
94:
79:
70:TZI Papageno
53:
49:
45:
37:
20:
16:
15:
31:, it is an
140:Categories
40:multicast
29:RFC 5775
23:) is an
75:INRIA
97:stub
33:IETF
21:ALC
142::
128:e
121:t
114:v
103:.
19:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
