| 1 |
<pre>Network Working Group E. Lear |
| 2 |
Request for Comments: 4219 Cisco Systems |
| 3 |
Category: Informational October 2005 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Things Multihoming in IPv6 (MULTI6) Developers Should Think About</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 (2005). |
| 17 |
|
| 18 |
Abstract |
| 19 |
|
| 20 |
This document specifies a set of questions that authors should be |
| 21 |
prepared to answer as part of a solution to multihoming with IPv6. |
| 22 |
The questions do not assume that multihoming is the only problem of |
| 23 |
interest, nor do they demand a more general solution. |
| 24 |
|
| 25 |
Table of Contents |
| 26 |
|
| 27 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 28 |
<a href="#section-1.1">1.1</a>. Reading this Document ......................................<a href="#page-3">3</a> |
| 29 |
<a href="#section-2">2</a>. On the Wire Behavior ............................................<a href="#page-4">4</a> |
| 30 |
<a href="#section-2.1">2.1</a>. How will your solution solve the multihoming problem? ......<a href="#page-4">4</a> |
| 31 |
<a href="#section-2.2">2.2</a>. At what layer is your solution applied, and how? ...........<a href="#page-4">4</a> |
| 32 |
<a href="#section-2.3">2.3</a>. Why is the layer you chose the correct one? ................<a href="#page-4">4</a> |
| 33 |
<a href="#section-2.4">2.4</a>. Does your solution address mobility? .......................<a href="#page-4">4</a> |
| 34 |
<a href="#section-2.5">2.5</a>. Does your solution expand the size of an IP packet? ........<a href="#page-4">4</a> |
| 35 |
<a href="#section-2.6">2.6</a>. Will your solution add additional latency? .................<a href="#page-4">4</a> |
| 36 |
2.7. Can multihoming capabilities be negotiated |
| 37 |
end-to-end during a ........................................<a href="#page-4">4</a> |
| 38 |
<a href="#section-2.8">2.8</a>. Do you change the way fragmenting is handled? ..............<a href="#page-5">5</a> |
| 39 |
<a href="#section-2.9">2.9</a>. Are there any layer 2 implications to your proposal? .......<a href="#page-5">5</a> |
| 40 |
<a href="#section-3">3</a>. Identifiers and Locators ........................................<a href="#page-5">5</a> |
| 41 |
<a href="#section-3.1">3.1</a>. Uniqueness .................................................<a href="#page-5">5</a> |
| 42 |
3.2. Does your solution provide for a split between |
| 43 |
identifiers and ............................................<a href="#page-5">5</a> |
| 44 |
3.3. What is the lifetime of a binding from an |
| 45 |
identifier to a locator? ...................................<a href="#page-5">5</a> |
| 46 |
<a href="#section-3.4">3.4</a>. How is the binding updated? ................................<a href="#page-5">5</a> |
| 47 |
<a href="#section-3.5">3.5</a>. How does a host know its identity? .........................<a href="#page-5">5</a> |
| 48 |
<a href="#section-3.6">3.6</a>. Can a host have multiple identifiers? ......................<a href="#page-5">5</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Lear Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 55 |
|
| 56 |
|
| 57 |
3.7. If you have separate locators and identifiers, how |
| 58 |
will they be ...............................................<a href="#page-5">5</a> |
| 59 |
3.8. Does your solution create an alternate "DNS-like" |
| 60 |
service? ...................................................<a href="#page-5">5</a> |
| 61 |
<a href="#section-3.9">3.9</a>. Please describe authentication/authorization ...............<a href="#page-6">6</a> |
| 62 |
<a href="#section-3.10">3.10</a>. Is your mechanism hierarchical? ...........................<a href="#page-6">6</a> |
| 63 |
<a href="#section-3.11">3.11</a>. Middlebox interactions ....................................<a href="#page-6">6</a> |
| 64 |
<a href="#section-3.12">3.12</a>. Are there any implications for scoped addressing? .........<a href="#page-6">6</a> |
| 65 |
<a href="#section-4">4</a>. Routing System Interactions .....................................<a href="#page-6">6</a> |
| 66 |
<a href="#section-4.1">4.1</a>. Does your solution change existing aggregation methods? ....<a href="#page-6">6</a> |
| 67 |
<a href="#section-4.2">4.2</a>. Does the solution solve traffic engineering requirements? ..7 |
| 68 |
4.3. Does the solution offer ways for the site to manage |
| 69 |
its traffic ................................................<a href="#page-7">7</a> |
| 70 |
4.4. If you introduce any new name spaces, do they |
| 71 |
require aggregation? .......................................<a href="#page-7">7</a> |
| 72 |
4.5. Does your solution interact with Autonomous System |
| 73 |
numbering? .................................................<a href="#page-7">7</a> |
| 74 |
<a href="#section-4.6">4.6</a>. Are there any changes to ICMP error semantics? .............<a href="#page-7">7</a> |
| 75 |
<a href="#section-5">5</a>. Name Service Interactions .......................................<a href="#page-7">7</a> |
| 76 |
<a href="#section-5.1">5.1</a>. Please explain the relationship of your solution to DNS ....<a href="#page-7">7</a> |
| 77 |
<a href="#section-5.2">5.2</a>. Please explain interactions with "2-faced" DNS .............<a href="#page-7">7</a> |
| 78 |
<a href="#section-5.3">5.3</a>. Does your solution require centralized registration? .......<a href="#page-8">8</a> |
| 79 |
<a href="#section-5.4">5.4</a>. Have you checked for DNS circular dependencies? ............<a href="#page-8">8</a> |
| 80 |
<a href="#section-5.5">5.5</a>. What if a DNS server itself is multihomed? .................<a href="#page-8">8</a> |
| 81 |
<a href="#section-5.6">5.6</a>. What additional load will be placed on DNS servers? ........<a href="#page-8">8</a> |
| 82 |
<a href="#section-5.7">5.7</a>. Any upstream provider support required? ....................<a href="#page-8">8</a> |
| 83 |
<a href="#section-5.8">5.8</a>. How do you debug connectivity? .............................<a href="#page-8">8</a> |
| 84 |
<a href="#section-6">6</a>. Application Concerns and Backward Compatibility .................<a href="#page-8">8</a> |
| 85 |
<a href="#section-6.1">6.1</a>. What application/API changes are needed? ...................<a href="#page-8">8</a> |
| 86 |
6.2. Is this solution backward compatible with "old" IP |
| 87 |
version 6? .................................................<a href="#page-9">9</a> |
| 88 |
<a href="#section-6.3">6.3</a>. Is your solution backward compatible with IPv4? ............<a href="#page-9">9</a> |
| 89 |
<a href="#section-6.4">6.4</a>. Can IPv4 devices take advantage of this solution? ..........<a href="#page-9">9</a> |
| 90 |
6.5. What is the impact of your solution on different |
| 91 |
types of sites? ............................................<a href="#page-9">9</a> |
| 92 |
<a href="#section-6.6">6.6</a>. How will your solution interact with other middleboxes? ...<a href="#page-10">10</a> |
| 93 |
<a href="#section-6.7">6.7</a>. Referrals .................................................<a href="#page-10">10</a> |
| 94 |
<a href="#section-6.8">6.8</a>. Demonstrate use with a real life complex application ......<a href="#page-10">10</a> |
| 95 |
<a href="#section-7">7</a>. Legal Concerns .................................................<a href="#page-10">10</a> |
| 96 |
<a href="#section-8">8</a>. Security Considerations ........................................<a href="#page-10">10</a> |
| 97 |
<a href="#section-9">9</a>. Acknowledgements ...............................................<a href="#page-11">11</a> |
| 98 |
<a href="#section-10">10</a>. References ....................................................<a href="#page-11">11</a> |
| 99 |
<a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-11">11</a> |
| 100 |
<a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-11">11</a> |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Lear Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
At the time of this writing there are quite a number of proposed |
| 116 |
solutions to the problem of multihoming within IPv6, and related |
| 117 |
problems such as the locator/identifier split. |
| 118 |
|
| 119 |
This document contains several sets of questions that attempt to |
| 120 |
focus these solutions on operational problems. This document does |
| 121 |
not suggest methods to solve the problem. Rather, we simply want to |
| 122 |
ensure that while solving a problem the medicine is not worse than |
| 123 |
the cure. We focus on practical operational problems that both |
| 124 |
single-homed and multihomed deployments may face. |
| 125 |
|
| 126 |
It is the hope of the author that perhaps the authors of other |
| 127 |
proposed solutions will use this document to identify gaps in their |
| 128 |
solutions, and cooperate to close those gaps. |
| 129 |
|
| 130 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Reading this Document</span> |
| 131 |
|
| 132 |
The questions are organized along the following lines: |
| 133 |
|
| 134 |
o changes to on the wire behavior; |
| 135 |
o routing system interactions; |
| 136 |
o identifier/mapping split; |
| 137 |
o application concerns and backward compatibility; |
| 138 |
o name service interactions; |
| 139 |
o legal concerns; and |
| 140 |
o security considerations. |
| 141 |
|
| 142 |
In reality many questions cut across all of these concerns. For |
| 143 |
instance, the identifier / locator split has substantial application |
| 144 |
implications, and every area has security considerations. |
| 145 |
|
| 146 |
Unless it is blatantly obvious, each question contains some reasoning |
| 147 |
as to why it is being asked. It is envisioned that no solution will |
| 148 |
answer every question with completeness, but that there will be |
| 149 |
tradeoffs to be made. The answers by the various designers of |
| 150 |
solutions will hopefully shed some light on which tradeoffs we as a |
| 151 |
community wish to make. |
| 152 |
|
| 153 |
It would seem silly for people who have written detailed answers to |
| 154 |
these questions to have to repeat the exercise. Therefore, a simple |
| 155 |
reference to existing documents will suffice, so long as the answer |
| 156 |
is complete. If it is not complete, then feel free to reference it |
| 157 |
and add what text is necessary to make the answer complete. |
| 158 |
|
| 159 |
This document presumes a familiarity with <a href="./rfc3582">RFC 3582</a> [<a href="#ref-2" title=""Goals for IPv6 Site- Multihoming Architectures"">2</a>], and does not |
| 160 |
attempt to repeat the requirements work gathered there. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Lear Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. On the Wire Behavior</span> |
| 170 |
|
| 171 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. How will your solution solve the multihoming problem?</span> |
| 172 |
|
| 173 |
Please scope the problem you are attempting to solve and what you are |
| 174 |
not attempting to solve. |
| 175 |
|
| 176 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. At what layer is your solution applied, and how?</span> |
| 177 |
|
| 178 |
Is it applied in every packet? If so, what fields are used? |
| 179 |
|
| 180 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Why is the layer you chose the correct one?</span> |
| 181 |
|
| 182 |
Each layer has its benefits and tradeoffs. For instance, transport |
| 183 |
layer solutions would require that EVERY transport be modified, while |
| 184 |
IP layer solutions may entail expansion of the packet or a change to |
| 185 |
the pseudo-header (thus requiring changes to the transport layer). |
| 186 |
|
| 187 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Does your solution address mobility?</span> |
| 188 |
|
| 189 |
If so, how are rendezvous handled? Can your solution handle both |
| 190 |
locators changing at the same time? If so, please explain. Should |
| 191 |
it? If not, how will your solution interact with MOBILEIP-V6 [<a href="#ref-3" title=""Mobility Support in IPv6"">3</a>] |
| 192 |
(MIPv6) |
| 193 |
|
| 194 |
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Does your solution expand the size of an IP packet?</span> |
| 195 |
|
| 196 |
Expanding the size of an IP packet may cause excessive fragmentation |
| 197 |
in some circumstances. |
| 198 |
|
| 199 |
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Will your solution add additional latency?</span> |
| 200 |
|
| 201 |
Latency is an important factor in many applications, including voice. |
| 202 |
Any substantial amount of additional latency, including session |
| 203 |
initiation would be highly undesirable. |
| 204 |
|
| 205 |
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Can multihoming capabilities be negotiated end-to-end during a</span> |
| 206 |
<span class="h3"> connection?</span> |
| 207 |
|
| 208 |
If the proposal introduces additional overhead, can the information |
| 209 |
be somehow piggybacked on messages that are already used? This would |
| 210 |
be useful in order to keep connection setup constant. Please also |
| 211 |
indicate any drawbacks that might apply due to this piggybacking. |
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Lear Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Do you change the way fragmenting is handled?</span> |
| 226 |
|
| 227 |
If you use a shim approach, do you fragment above or below the shim? |
| 228 |
How are fragments identified, so that they can be reassembled? If |
| 229 |
you use any additional names, do they need to be associated with |
| 230 |
fragments? If not, why not? If so, how will that happen? |
| 231 |
|
| 232 |
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Are there any layer 2 implications to your proposal?</span> |
| 233 |
|
| 234 |
While IPv6 has a simplified approach to layer 2, perhaps you |
| 235 |
unsimplified it. If so, please provide details. |
| 236 |
|
| 237 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Identifiers and Locators</span> |
| 238 |
|
| 239 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Uniqueness</span> |
| 240 |
|
| 241 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Does your solution provide for a split between identifiers and</span> |
| 242 |
<span class="h3"> locators?</span> |
| 243 |
|
| 244 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. What is the lifetime of a binding from an identifier to a locator?</span> |
| 245 |
|
| 246 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. How is the binding updated?</span> |
| 247 |
|
| 248 |
Will transport connections remain up when new paths become available |
| 249 |
or when old ones become unavailable? How does the end node discover |
| 250 |
these events? |
| 251 |
|
| 252 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. How does a host know its identity?</span> |
| 253 |
|
| 254 |
If you are establishing a new identity, how does the host learn it? |
| 255 |
|
| 256 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Can a host have multiple identifiers?</span> |
| 257 |
|
| 258 |
If so, how does an application choose an identity? |
| 259 |
|
| 260 |
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. If you have separate locators and identifiers, how will they be</span> |
| 261 |
<span class="h3"> mapped?</span> |
| 262 |
|
| 263 |
Does the mapping work in both directions? How would someone |
| 264 |
debugging a network determine which end stations are involved? |
| 265 |
|
| 266 |
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Does your solution create an alternate "DNS-like" service?</span> |
| 267 |
|
| 268 |
If you use mechanisms other than DNS, first, why was DNS not |
| 269 |
appropriate? Also, how will this other mechanism interact with DNS? |
| 270 |
What are its scaling properties? |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Lear Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. Please describe authentication/authorization</span> |
| 282 |
|
| 283 |
How are bindings authenticated and authorized. What technology do |
| 284 |
you build on for this mechanism? |
| 285 |
|
| 286 |
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. Is your mechanism hierarchical?</span> |
| 287 |
|
| 288 |
Please describe the hierarchical breakdown. |
| 289 |
|
| 290 |
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. Middlebox interactions</span> |
| 291 |
|
| 292 |
What are the implications for firewalls? What are the interactions |
| 293 |
with Network Address Translation (NAT)? What are the interactions |
| 294 |
with web caches? What complications are introduced with your |
| 295 |
solution? For instance, are there implication for ingress filters? |
| 296 |
If so, what are they? |
| 297 |
|
| 298 |
When considering this question, there are really two issues. First, |
| 299 |
will middleboxes impede your solution by rewriting headers in some |
| 300 |
way, as NATs do for IP addresses, and web caches do at higher layers? |
| 301 |
Second, is there a way in which middleboxes are actually part of your |
| 302 |
solution? In particular, are they required? This would be the case, |
| 303 |
for example, with Generalized Structure Element (GSE) (8+8). |
| 304 |
|
| 305 |
<span class="h3"><a class="selflink" id="section-3.12" href="#section-3.12">3.12</a>. Are there any implications for scoped addressing?</span> |
| 306 |
|
| 307 |
Please see <a href="./rfc3513">RFC 3513</a> [<a href="#ref-1" title=""Internet Protocol Version 6 (IPv6) Addressing Architecture"">1</a>]. How does your mechanism interact with |
| 308 |
multicast? |
| 309 |
|
| 310 |
How does your solution interact with link-local addressing |
| 311 |
|
| 312 |
How does your solution interact with Son-Of-Sitelocal (whatever that |
| 313 |
will be)? |
| 314 |
|
| 315 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Routing System Interactions</span> |
| 316 |
|
| 317 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Does your solution change existing aggregation methods?</span> |
| 318 |
|
| 319 |
Routing on the Internet scales today because hosts and networks can |
| 320 |
be aggregated into a relatively small number of entries. Does your |
| 321 |
solution change the way in which route aggregation occurs? |
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Lear Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Does the solution solve traffic engineering requirements?</span> |
| 338 |
|
| 339 |
One of the significant goals of IPv4 multihoming solutions has been |
| 340 |
the ability to perform traffic engineering based on appropriately |
| 341 |
adjusting the BGP advertisements. If the prefixes used by such sites |
| 342 |
was be aggregated (particularly beyond the site"s border), the site"s |
| 343 |
ability to perform traffic engineering would be diminished. |
| 344 |
|
| 345 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Does the solution offer ways for the site to manage its traffic</span> |
| 346 |
<span class="h3"> flows?</span> |
| 347 |
|
| 348 |
If so, how? Is this controllable on a per-host basis, or on a |
| 349 |
per-site basis? |
| 350 |
|
| 351 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. If you introduce any new name spaces, do they require aggregation?</span> |
| 352 |
|
| 353 |
Is it desirable or required that, in order to scale distribution of |
| 354 |
any mapping information, an aggregation method be introduced? |
| 355 |
|
| 356 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Does your solution interact with Autonomous System numbering?</span> |
| 357 |
|
| 358 |
If your solution involves address prefixes distributed using BGP4+, |
| 359 |
does it interact with the use of AS numbers and, if so, how? Will it |
| 360 |
require additional AS numbers? |
| 361 |
|
| 362 |
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. Are there any changes to ICMP error semantics?</span> |
| 363 |
|
| 364 |
Do you create new codes? If so, why and what do they mean? Will a |
| 365 |
host that is not aware of your scheme see them? |
| 366 |
|
| 367 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Name Service Interactions</span> |
| 368 |
|
| 369 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Please explain the relationship of your solution to DNS</span> |
| 370 |
|
| 371 |
If your solution uses new names for identifiers, please explain what |
| 372 |
mappings are defined, and how they are performed? |
| 373 |
|
| 374 |
If there are any additional administrative requirements, such as new |
| 375 |
zones or RR types to manage, please explain them as well. |
| 376 |
|
| 377 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Please explain interactions with "2-faced" DNS</span> |
| 378 |
|
| 379 |
2-faced DNS is used so that hosts behind a NAT get one address for |
| 380 |
internal hosts, while hosts outside the NAT get another. Similar |
| 381 |
mechanisms are used for application layer gateways, such as SOCKS |
| 382 |
[<a href="#ref-5" title=""A SOCKS-based IPv6/IPv4 Gateway Mechanism"">5</a>]. |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Lear Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Does your solution require centralized registration?</span> |
| 394 |
|
| 395 |
For instance, if you are using the DNS, what will be the top level |
| 396 |
domain, and how will the name space distribute through it? |
| 397 |
|
| 398 |
Also, how will the centralized registration be managed? |
| 399 |
|
| 400 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Have you checked for DNS circular dependencies?</span> |
| 401 |
|
| 402 |
If you are using the DNS in your solution, is it required for |
| 403 |
connectivity? What happens if the DNS fails? Can communication |
| 404 |
between the DNS resolver and the server make use of your solution? |
| 405 |
What about between the application and the resolver? |
| 406 |
|
| 407 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. What if a DNS server itself is multihomed?</span> |
| 408 |
|
| 409 |
If a link fails or a service is dropped, how will it impact DNS? |
| 410 |
Again, are there any dependency loops? Perhaps diagram out your |
| 411 |
dependencies to make sure. |
| 412 |
|
| 413 |
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. What additional load will be placed on DNS servers?</span> |
| 414 |
|
| 415 |
Can the load be distributed? Remember that DNS is optimized for READ |
| 416 |
operations. |
| 417 |
|
| 418 |
<span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. Any upstream provider support required?</span> |
| 419 |
|
| 420 |
If so, please describe. For instance, currently reverse mappings are |
| 421 |
delegated down from upstream providers. How would this work with |
| 422 |
your solution? |
| 423 |
|
| 424 |
<span class="h3"><a class="selflink" id="section-5.8" href="#section-5.8">5.8</a>. How do you debug connectivity?</span> |
| 425 |
|
| 426 |
How would tools like ping and traceroute need to be enhanced? What |
| 427 |
additional tools would prove useful or necessary? For instance, if |
| 428 |
there is an id/locator split, can one ping an identifier? If so, |
| 429 |
what gets returned? |
| 430 |
|
| 431 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Application Concerns and Backward Compatibility</span> |
| 432 |
|
| 433 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. What application/API changes are needed?</span> |
| 434 |
|
| 435 |
Will old code work with the new mechanism? For instance, what about |
| 436 |
code that uses gethostbyname()? |
| 437 |
|
| 438 |
Will getaddrinfo() need to change? |
| 439 |
|
| 440 |
What about other API calls? |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Lear Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 447 |
|
| 448 |
|
| 449 |
There are several possible approaches. For instance, a multihoming |
| 450 |
service could attempt to require no changes to the API, in which case |
| 451 |
it is possible that IP addresses might become opaque blobs that work |
| 452 |
with the API, but might break operational assumptions that |
| 453 |
applications make about addresses. Consider the case of a web server |
| 454 |
that wants to log IP addresses. How will it accomplish this task? |
| 455 |
|
| 456 |
Another approach is to have some sort of compatibility library for |
| 457 |
legacy applications, but also provide a richer calling interface for |
| 458 |
transparency. |
| 459 |
|
| 460 |
Yet another approach would be to only provide the new functionality |
| 461 |
to those applications that make use of a new calling interface. |
| 462 |
|
| 463 |
One useful exercise would be to provide code fragments that |
| 464 |
demonstrate any API changes. |
| 465 |
|
| 466 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Is this solution backward compatible with "old" IP version 6?</span> |
| 467 |
|
| 468 |
Can it be deployed incrementally? Please describe how. |
| 469 |
|
| 470 |
Does your solution impose requirements on non-multihomed/non-mobile |
| 471 |
hosts? |
| 472 |
|
| 473 |
What happens if someone plugs in a normal IPv6 node? |
| 474 |
|
| 475 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Is your solution backward compatible with IPv4?</span> |
| 476 |
|
| 477 |
How will your mechanism interact with 6to4 gateways and IPv4 hosts? |
| 478 |
|
| 479 |
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Can IPv4 devices take advantage of this solution?</span> |
| 480 |
|
| 481 |
Can the same mechanism somehow be used on the existing network? N.B. |
| 482 |
this is NOT a primary consideration, but perhaps a side benefit of a |
| 483 |
particular solution. |
| 484 |
|
| 485 |
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. What is the impact of your solution on different types of sites?</span> |
| 486 |
|
| 487 |
What will the impact of your solution be on the following types of |
| 488 |
systems? |
| 489 |
|
| 490 |
o single homed sites |
| 491 |
o small multihomed sites |
| 492 |
o large multihomed sites |
| 493 |
o ad-hoc sites |
| 494 |
o short lived connections (think aggregator wireless ISPs) |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Lear Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 503 |
|
| 504 |
|
| 505 |
In particular, consider ongoing administration, renumbering events, |
| 506 |
and mobile work forces. |
| 507 |
|
| 508 |
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. How will your solution interact with other middleboxes?</span> |
| 509 |
|
| 510 |
<span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. Referrals</span> |
| 511 |
|
| 512 |
How will your solution handle referrals, such as those within FTP or |
| 513 |
various conferencing or other peer to peer systems? |
| 514 |
|
| 515 |
Referrals exist within various other protocols, such as so-called |
| 516 |
"peer to peer" applications. Note that referrals might suffer three |
| 517 |
types of failure: |
| 518 |
|
| 519 |
firewall and NAT - Is there failure just as what FTP active mode |
| 520 |
experiences today with relatively simple firewalls? |
| 521 |
time-based - Is there something ephemeral about the nature of the |
| 522 |
solution that might cause a referral (such as a URL) to fail over |
| 523 |
time, more so than what we have today? |
| 524 |
location-based - If the binding varies based on where the parties are |
| 525 |
in the network, and if one moves, will they no longer be able to |
| 526 |
find each other? |
| 527 |
|
| 528 |
<span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. Demonstrate use with a real life complex application</span> |
| 529 |
|
| 530 |
Provide a detailed walk-through of SIP + Real Time Streaming Protocol |
| 531 |
(SIP+RTSP) when one or several of the peers are multihomed. How does |
| 532 |
your analysis change when encrypted RTSP is used or when SIP with |
| 533 |
S/MIME end-to-end (e2e) signalling is used? |
| 534 |
|
| 535 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Legal Concerns</span> |
| 536 |
|
| 537 |
Are you introducing a namespace that might involve mnemonics? Doing |
| 538 |
so might introduce trademark concerns. If so, how do you plan to |
| 539 |
address such concerns? |
| 540 |
|
| 541 |
Are there any organizations required to manage a new name space? If |
| 542 |
so, please describe what they are and how the method will scale. |
| 543 |
|
| 544 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 545 |
|
| 546 |
How secure should a multi6 solution be? This is a reasonable |
| 547 |
question for each solution to answer. The author opines that the |
| 548 |
worst case should be no worse than what we have today. For example, |
| 549 |
would a multi6 solution open up a host, on either end of a |
| 550 |
communication, to a time-based attack? Any such risks should be |
| 551 |
clearly stated by the authors. Considerable time should be spent on |
| 552 |
threat analysis. Please see [<a href="#ref-4" title=""Threats Relating to IPv6 Multihoming Solutions"">4</a>] for more details. |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Lear Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 559 |
|
| 560 |
|
| 561 |
As IP addresses can often be tied to individuals, are there any |
| 562 |
auditing or privacy concerns introduced by your solution? |
| 563 |
|
| 564 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span> |
| 565 |
|
| 566 |
The author wishes to acknowledge everyone in the multi6 group and |
| 567 |
elsewhere that is putting forward proposals. It is easy to ask |
| 568 |
questions like the ones found in this document. It is quite a bit |
| 569 |
harder to develop running code to answer them. Marcelo Bagnulo, Kurt |
| 570 |
Erik Lindqvist, Joe Touch, Patrik Faltstrom, Brian Carpenter, and |
| 571 |
Iljitsch van Beijnum provided input to this document. |
| 572 |
|
| 573 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span> |
| 574 |
|
| 575 |
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span> |
| 576 |
|
| 577 |
[<a id="ref-1">1</a>] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6) |
| 578 |
Addressing Architecture", <a href="./rfc3513">RFC 3513</a>, April 2003. |
| 579 |
|
| 580 |
[<a id="ref-2">2</a>] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site- |
| 581 |
Multihoming Architectures", <a href="./rfc3582">RFC 3582</a>, August 2003. |
| 582 |
|
| 583 |
[<a id="ref-3">3</a>] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in |
| 584 |
IPv6", <a href="./rfc3775">RFC 3775</a>, June 2004. |
| 585 |
|
| 586 |
[<a id="ref-4">4</a>] Nordmark, E., "Threats Relating to IPv6 Multihoming Solutions", |
| 587 |
<a href="./rfc4218">RFC 4218</a>, October 2005. |
| 588 |
|
| 589 |
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span> |
| 590 |
|
| 591 |
[<a id="ref-5">5</a>] Kitamura, H., "A SOCKS-based IPv6/IPv4 Gateway Mechanism", |
| 592 |
<a href="./rfc3089">RFC 3089</a>, April 2001. |
| 593 |
|
| 594 |
Author's Address |
| 595 |
|
| 596 |
Eliot Lear |
| 597 |
Cisco Systems GmbH |
| 598 |
Glatt-com, 2nd Floor |
| 599 |
CH-8301 Glattzentrum ZH |
| 600 |
Switzerland |
| 601 |
|
| 602 |
EMail: [email protected] |
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Lear Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc4219">RFC 4219</a> MULTI6 Solution Questionnaire October 2005</span> |
| 615 |
|
| 616 |
|
| 617 |
Full Copyright Statement |
| 618 |
|
| 619 |
Copyright (C) The Internet Society (2005). |
| 620 |
|
| 621 |
This document is subject to the rights, licenses and restrictions |
| 622 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 623 |
retain all their rights. |
| 624 |
|
| 625 |
This document and the information contained herein are provided on an |
| 626 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 627 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 628 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 629 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 630 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 631 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 632 |
|
| 633 |
Intellectual Property |
| 634 |
|
| 635 |
The IETF takes no position regarding the validity or scope of any |
| 636 |
Intellectual Property Rights or other rights that might be claimed to |
| 637 |
pertain to the implementation or use of the technology described in |
| 638 |
this document or the extent to which any license under such rights |
| 639 |
might or might not be available; nor does it represent that it has |
| 640 |
made any independent effort to identify any such rights. Information |
| 641 |
on the procedures with respect to rights in RFC documents can be |
| 642 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 643 |
|
| 644 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 645 |
assurances of licenses to be made available, or the result of an |
| 646 |
attempt made to obtain a general license or permission for the use of |
| 647 |
such proprietary rights by implementers or users of this |
| 648 |
specification can be obtained from the IETF on-line IPR repository at |
| 649 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 650 |
|
| 651 |
The IETF invites any interested party to bring to its attention any |
| 652 |
copyrights, patents or patent applications, or other proprietary |
| 653 |
rights that may cover technology that may be required to implement |
| 654 |
this standard. Please address the information to the IETF at ietf- |
| 655 |
[email protected]. |
| 656 |
|
| 657 |
Acknowledgement |
| 658 |
|
| 659 |
Funding for the RFC Editor function is currently provided by the |
| 660 |
Internet Society. |
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
Lear Informational [Page 12] |
| 669 |
</pre> |