[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Fwd: I-D ACTION:draft-lear-multi6-things-to-think-about-00.txt]
Hi,
i think this draft will be useful
I have some additional questions for your consideration:
- Is the multi-homing solution IPv6 only or can it also be used with IPv4?
I know this is multi6, but it is probably interesting to know if the
solution can be applied to IPv4
- Does your solution applies to all type of sites?, for instance is your
solution suitable for very small sites? (does it requires an expert
administrator o very powerful equipment) is your solution siutable for very
large sites?
- About incremental deployment, i think that there are different ideas about
what incremental deployment means. So perhaps we could ask more specific
question (in addition) like:
- Does your solution imposes changes outside the multi-homed site?
- what do you need to change in the mh site? in particular if
you plug in a non upgraded IPv6 node, does it work properly? can it
communicate outside the mhsite? does it obtain multi-homing benefits?
- Does your solution requires some global infrastructure to start
working? like a new global DNS like system, or it allows two upgraded nodes
to communicate with each other without any additional infrastructure
- If your solution preserves established communications, does it introduces
overhead? additional data? additional processing in the nodes? How does your
solution distributes the overhead? does it imposes additional overhead on a
per communication basis or a per node basis? does it imposes extra overhead
to all communications? does it imposes additional overhead for those
communications that don't suffer an outage along its path? does it only
imposes overhead after the outage?
- Impact od DNS, does you solution will impose an additional significant
stress to the DNS system? like how much more DNS queries are expected
Regards, marcelo
> -----Mensaje original-----
> De: owner-multi6@ops.ietf.org [mailto:owner-multi6@ops.ietf.org]En
> nombre de Brian E Carpenter
> Enviado el: martes, 16 de diciembre de 2003 9:27
> Para: Multi6
> Asunto: [Fwd: I-D ACTION:draft-lear-multi6-things-to-think-about-00.txt]
>
>
> fyi
>
> -------- Original Message --------
> Subject: I-D ACTION:draft-lear-multi6-things-to-think-about-00.txt
> Date: Mon, 15 Dec 2003 15:29:00 -0500
> From: Internet-Drafts@ietf.org
> Reply-To: Internet-Drafts@ietf.org
> To: IETF-Announce: ;
>
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
>
>
> Title : Things MULTI6 Developers should think about
> Author(s) : E. Lear
> Filename : draft-lear-multi6-things-to-think-about-00.txt
> Pages : 12
> Date : 2003-12-15
>
> This document specifies a set of questions that authors should be
> prepared to answer as part of a solution to multihoming with IPv6.
> The questions do not assume that multihoming is the only problem of
> interest, nor do they demand a more general solution either.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-lear-multi6-things-to-th
ink-about-00.txt
To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-lear-multi6-things-to-think-about-00.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv@ietf.org.
In the body type:
"FILE /internet-drafts/draft-lear-multi6-things-to-think-about-00.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.