| 1 |
<pre>Network Working Group G. Armitage |
| 2 |
Request for Comments: 2269 Lucent Technologies |
| 3 |
Category: Informational January 1998 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Using the MARS Model in non-ATM NBMA Networks</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. It does |
| 11 |
not specify an Internet standard of any kind. Distribution of this |
| 12 |
memo is unlimited. |
| 13 |
|
| 14 |
Copyright Notice |
| 15 |
|
| 16 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 17 |
|
| 18 |
Abstract |
| 19 |
|
| 20 |
Initially developed for IP over ATM, the <a href="./rfc2022">RFC 2022</a> (MARS) model is |
| 21 |
also applicable to other NBMA networks that provide the equivalent of |
| 22 |
switched, point to multipoint connections. This short document is |
| 23 |
intended to state the obvious equivalences, and explain the less |
| 24 |
obvious implications. No changes to the MARS model per se are |
| 25 |
suggested or required. <a href="./rfc2022">RFC 2022</a> is not required over NBMA networks |
| 26 |
that offer Ethernet-like group addressing functionality. |
| 27 |
|
| 28 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 29 |
|
| 30 |
Most network layer models, like the one described in STD 5, <a href="./rfc1112">RFC 1112</a> |
| 31 |
[<a href="#ref-1" title=""Host Extensions for IP Multicasting"">1</a>] for IP multicasting, assume sources may send their packets to an |
| 32 |
abstract 'multicast group addresses'. Link layer support for such an |
| 33 |
abstraction is assumed to exist, and is provided by technologies such |
| 34 |
as Ethernet. |
| 35 |
|
| 36 |
Some NBMA networks (e.g. ATM using UNI3.0 or UNI3.1 signaling [<a href="#ref-4" title=""ATM User-Network Interface Specification Version 3.0"">4</a>,<a href="#ref-5" title=""ATM User Network Interface (UNI) Specification Version 3.1"">5</a>]) |
| 37 |
do not support a multicast (or group) address abstraction. In these |
| 38 |
environments multicasting is typically supported through point to |
| 39 |
multipoint calls (or emulated with multiple point to point calls). |
| 40 |
The MARS model (<a href="./rfc2022">RFC 2022</a>) [<a href="#ref-2" title=""Support for Multicast over UNI 3.0/3.1 based ATM Networks."">2</a>] was originally developed by the IP over |
| 41 |
ATM working group, and so uses ATM-centric descriptive language. For |
| 42 |
completeness this memo explains how <a href="./rfc2022">RFC 2022</a> can be applied to other |
| 43 |
NBMA technologies. |
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Armitage Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2269">RFC 2269</a> MARS Model in non-ATM NBMA Networks January 1998</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. <a href="./rfc2022">RFC 2022</a>'s basic assumptions.</span> |
| 58 |
|
| 59 |
Section 3 of [<a href="#ref-2" title=""Support for Multicast over UNI 3.0/3.1 based ATM Networks."">2</a>] describes the basic assumptions that the MARS model |
| 60 |
makes about the services available from the link layer network (using |
| 61 |
ATM as the specific case). In summary these are: |
| 62 |
|
| 63 |
The ATM model broadly describes an 'AAL User' as any entity that |
| 64 |
establishes and manages VCs and underlying AAL services to |
| 65 |
exchange data. An IP over ATM interface is a form of 'AAL User' |
| 66 |
|
| 67 |
The most fundamental limitations of UNI 3.0/3.1's multicast |
| 68 |
support are: |
| 69 |
|
| 70 |
Only point to multipoint, unidirectional VCs may be |
| 71 |
established. |
| 72 |
|
| 73 |
Only the root (source) node of a given VC may add or remove |
| 74 |
leaf nodes. |
| 75 |
|
| 76 |
Leaf nodes are identified by their unicast ATM addresses. |
| 77 |
|
| 78 |
Given this point to multipoint call service, the MARS document goes |
| 79 |
on to describe two architectures for emulating multipoint to |
| 80 |
multipoint IP multicasting - the VC Mesh, and the Multicast Server. |
| 81 |
In either case it was assumed that IP/ATM interfaces (whether in |
| 82 |
routers or hosts) are allowed to originate and manage outgoing point |
| 83 |
to multipoint calls without network operator intervention or manual |
| 84 |
provisioning. |
| 85 |
|
| 86 |
The MARS document also specifies that AAL5 be used for all SVCs, |
| 87 |
implying a requirement that the underlying link service supports the |
| 88 |
atomic exchange of PDUs. |
| 89 |
|
| 90 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Generalising the MARS model.</span> |
| 91 |
|
| 92 |
Any NBMA service that offers an equivalent to (or superset of) the |
| 93 |
ATM point to multipoint call service can use the MARS model directly. |
| 94 |
It must be possible to transmit atomic data units bi-directionally |
| 95 |
with point to point calls, and unidirectionally (from root to leaves) |
| 96 |
on point to multipoint calls. |
| 97 |
|
| 98 |
A MARS is an entity known by its NBMA address. |
| 99 |
|
| 100 |
A MARS Client is an entity known by its NBMA address. |
| 101 |
|
| 102 |
An MCS (where needed) is an entity known by its NBMA address. |
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Armitage Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2269">RFC 2269</a> MARS Model in non-ATM NBMA Networks January 1998</span> |
| 111 |
|
| 112 |
|
| 113 |
The MARS control messages defined in sections <a href="#section-4">4</a> onwards of the MARS |
| 114 |
document are shown carrying ATM addresses. Using different mar$afn |
| 115 |
(Address Family) values in the fixed header of MARS control messages |
| 116 |
allows MARS entities to indicate they are carrying other types of |
| 117 |
NBMA addresses (as done in NHRP [<a href="#ref-3" title=""NBMA Next Hop Resolution Protocol (NHRP)"">3</a>]). As for NHRP, the |
| 118 |
interpretation of the 'sub-address' fields shall be in the context of |
| 119 |
the address family selected (which means it will often simply be |
| 120 |
null). |
| 121 |
|
| 122 |
In all cases where {IP, ATM.1, ATM.2, ...} mappings are referred to, |
| 123 |
they may be interpreted as {IP, NBMA.1, NBMA.2, ...} in the context |
| 124 |
of whatever NBMA network you are deploying MARS. |
| 125 |
|
| 126 |
The MARS Cluster is defined in [<a href="#ref-2" title=""Support for Multicast over UNI 3.0/3.1 based ATM Networks."">2</a>] as: |
| 127 |
|
| 128 |
The set of ATM interfaces chosing to participate in direct ATM |
| 129 |
connections to achieve multicasting of AAL_SDUs between |
| 130 |
themselves. |
| 131 |
|
| 132 |
It is trivial to observe that the cluster definition is independent |
| 133 |
of the underlying link layer technology. A revised definition |
| 134 |
becomes: |
| 135 |
|
| 136 |
The set of NBMA interfaces chosing to participate in direct NBMA |
| 137 |
connections to achieve multicasting of packets between themselves. |
| 138 |
|
| 139 |
The term 'Cluster Member' continues to refer to an endpoint that is |
| 140 |
currently using a specific MARS for multicast support. The potential |
| 141 |
scope of a cluster may be the entire membership of a LIS, while the |
| 142 |
actual scope of a cluster depends on which LIS members are actually |
| 143 |
registered with the cluster's MARS at any given time. |
| 144 |
|
| 145 |
Section 3.4 of [<a href="#ref-2" title=""Support for Multicast over UNI 3.0/3.1 based ATM Networks."">2</a>] provided a set of mneumonics for the signalling |
| 146 |
functions available to AAL Users. These mneumonics are then used in |
| 147 |
the remainder of [<a href="#ref-2" title=""Support for Multicast over UNI 3.0/3.1 based ATM Networks."">2</a>] to indicate link layer events to which MARS |
| 148 |
entities might react. Recast from the perspective of an NBMA based |
| 149 |
MARS entity, the descriptions would now read: |
| 150 |
|
| 151 |
The following generic signalling functions are presumed to be |
| 152 |
available to local MARS entities: |
| 153 |
|
| 154 |
L_CALL_RQ Establish a pt-pt call to a specific endpoint. |
| 155 |
L_MULTI_RQ Establish pt-mpt call to a specific endpoint. |
| 156 |
L_MULTI_ADD Add new leaf node to previously established pt-mpt |
| 157 |
call. |
| 158 |
L_MULTI_DROP Remove specific leaf node from established pt-mpt |
| 159 |
call. |
| 160 |
L_RELEASE Release pt-pt call, or all Leaves of a pt-mpt call. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Armitage Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2269">RFC 2269</a> MARS Model in non-ATM NBMA Networks January 1998</span> |
| 167 |
|
| 168 |
|
| 169 |
The signalling exchanges and local information passed between MARS |
| 170 |
entity and NBMA signalling entity with these functions are outside |
| 171 |
the scope of this document. |
| 172 |
|
| 173 |
The following indications are assumed to be available to MARS |
| 174 |
entities, generated by by the local NBMA signalling entity: |
| 175 |
|
| 176 |
L_ACK Succesful completion of a local request. |
| 177 |
L_REMOTE_CALL A new call has been established to the MARS |
| 178 |
entity. |
| 179 |
ERR_L_RQFAILED A remote NBMA endpoint rejected an L_CALL_RQ, |
| 180 |
L_MULTI_RQ, or L_MULTI_ADD. |
| 181 |
ERR_L_DROP A remote NBMA endpoint dropped off an existing |
| 182 |
call. |
| 183 |
ERR_L_RELEASE An existing call was terminated. |
| 184 |
|
| 185 |
The signalling exchanges and local information passed between MARS |
| 186 |
entity and NBMA signalling entity with these functions are outside |
| 187 |
the scope of this document. |
| 188 |
|
| 189 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Open Issues.</span> |
| 190 |
|
| 191 |
The trade offs between VC Mesh and Multicast Server modes may look |
| 192 |
quite different for each NBMA technology. This will be especially |
| 193 |
true in the area of VC (or equivalent) resource consumption in the |
| 194 |
NICs of hosts, routers, and endpoints supporting MARSs or MCSs. The |
| 195 |
use of VC mesh mode is most vulnerable to NBMA technologies that are |
| 196 |
signalling intensive or resource challenged. |
| 197 |
|
| 198 |
Sizing of Clusters (and hence LISes) will also be affected by a given |
| 199 |
NBMA network's ability to support lots of pt-mpt calls. |
| 200 |
Additionally, you cannot have more members in a cluster than you can |
| 201 |
have leaf nodes on a pt-mpt call, without hacking the MARS model [<a href="#ref-6" title=""Issues affecting MARS Cluster Size"">6</a>]. |
| 202 |
|
| 203 |
On going developments in server synchronisation protocols for |
| 204 |
distributed <a href="./rfc2022">RFC 2022</a> implementations are expected to be applicable to |
| 205 |
non-ATM NBMA networks. |
| 206 |
|
| 207 |
Quality of service considerations are outside the scope of this |
| 208 |
document. They will be very specific to each NBMA technology's |
| 209 |
capabilities. Related work is being pursued outside the ION Working |
| 210 |
Group. |
| 211 |
|
| 212 |
If the NBMA network offers some sort of native multipoint to |
| 213 |
multipoint service then use of the MARS model may not be optimal. |
| 214 |
Such situations require further analysis. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Armitage Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2269">RFC 2269</a> MARS Model in non-ATM NBMA Networks January 1998</span> |
| 223 |
|
| 224 |
|
| 225 |
Security Considerations |
| 226 |
|
| 227 |
This memo is informational, and specifies no protocol for deployment. |
| 228 |
No specific non-ATM NBMA network technologies or security |
| 229 |
characteristics are discussed. Should enhancements to security be |
| 230 |
required, they shall be added as an extension to the base |
| 231 |
architecture in <a href="./rfc2022">RFC 2022</a>, or described in documents explicitly |
| 232 |
proposing use of <a href="./rfc2022">RFC 2022</a> over specific NBMA technologies. |
| 233 |
|
| 234 |
Acknowledgments |
| 235 |
|
| 236 |
This memo was substantially developed while the author was with Bell |
| 237 |
Communications Research (Bellcore). |
| 238 |
|
| 239 |
Author's Address |
| 240 |
|
| 241 |
Grenville Armitage |
| 242 |
Bell Laboratories, Lucent Technologies. |
| 243 |
101 Crawfords Corner Rd, |
| 244 |
Holmdel, NJ, 07733 |
| 245 |
USA |
| 246 |
|
| 247 |
EMail: [email protected] |
| 248 |
|
| 249 |
References |
| 250 |
|
| 251 |
[<a id="ref-1">1</a>] Deering, S., "Host Extensions for IP Multicasting", STD 5, <a href="./rfc1112">RFC</a> |
| 252 |
<a href="./rfc1112">1112</a>, Stanford University, August 1989. |
| 253 |
|
| 254 |
[<a id="ref-2">2</a>] Armitage, G., "Support for Multicast over UNI 3.0/3.1 based ATM |
| 255 |
Networks.", <a href="./rfc2022">RFC 2022</a>, November 1996. |
| 256 |
|
| 257 |
[<a id="ref-3">3</a>] Luciani, J., et. al., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22NBMA+Next+Hop+Resolution+Protocol+%28NHRP%29%22'>"NBMA Next Hop Resolution Protocol (NHRP)"</a>, |
| 258 |
Work in Progress. |
| 259 |
|
| 260 |
[<a id="ref-4">4</a>] ATM Forum, "ATM User-Network Interface Specification Version |
| 261 |
3.0", Englewood Cliffs, NJ: Prentice Hall, September 1993. |
| 262 |
|
| 263 |
[<a id="ref-5">5</a>] ATM Forum, "ATM User Network Interface (UNI) Specification |
| 264 |
Version 3.1", ISBN 0-13-393828-X, Prentice Hall, Englewood Cliffs, |
| 265 |
NJ, June 1995. |
| 266 |
|
| 267 |
[<a id="ref-6">6</a>] Armitage, G., "Issues affecting MARS Cluster Size", <a href="./rfc2121">RFC 2121</a>, |
| 268 |
March 1997. |
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Armitage Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2269">RFC 2269</a> MARS Model in non-ATM NBMA Networks January 1998</span> |
| 279 |
|
| 280 |
|
| 281 |
Full Copyright Statement |
| 282 |
|
| 283 |
Copyright (C) The Internet Society (1998). All Rights Reserved. |
| 284 |
|
| 285 |
This document and translations of it may be copied and furnished to |
| 286 |
others, and derivative works that comment on or otherwise explain it |
| 287 |
or assist in its implementation may be prepared, copied, published |
| 288 |
and distributed, in whole or in part, without restriction of any |
| 289 |
kind, provided that the above copyright notice and this paragraph are |
| 290 |
included on all such copies and derivative works. However, this |
| 291 |
document itself may not be modified in any way, such as by removing |
| 292 |
the copyright notice or references to the Internet Society or other |
| 293 |
Internet organizations, except as needed for the purpose of |
| 294 |
developing Internet standards in which case the procedures for |
| 295 |
copyrights defined in the Internet Standards process must be |
| 296 |
followed, or as required to translate it into languages other than |
| 297 |
English. |
| 298 |
|
| 299 |
The limited permissions granted above are perpetual and will not be |
| 300 |
revoked by the Internet Society or its successors or assigns. |
| 301 |
|
| 302 |
This document and the information contained herein is provided on an |
| 303 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 304 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 305 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 306 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 307 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
Armitage Informational [Page 6] |
| 333 |
</pre> |