On Thu, 29 Jul 2004 17:53:30 +1000,
Nick 'Sharkey' Moore [EMAIL PROTECTED] said:
Our time in the WG is limited, but I'll try and work out some way of
gauging the WGs feelings about these issues.
To save time, here is a summary of my opinion on the substantial
request to optimistic DAD.
1.
On 2004-08-03, JINMEI Tatuya / [EMAIL PROTECTED]@C#:H wrote:
To save time, here is a summary of my opinion on the substantial
request to optimistic DAD.
Thanks Jinmei. I think we're not that far apart in our
opinions after all :-)
Finally, I admit some of the above points may be
Hi,
I'd like for the WG to consider one addition / spelling out for
2461bis in section 7.2.2 on address resolution:
If no Neighbor Advertisement is received after MAX_MULTICAST_SOLICIT
solicitations, address resolution has failed. The sender MUST return
ICMP destination unreachable
Hi, I try to implement the simple ipv6 intranet
among the pcs within the same network.
So I use the link local address starting with fe80::
The environment is the following
PC1 - WinXP SP1
PC2 - Win2003Server with Port Filtering(TCP)
Symptom
Both PC can ping6 to itself.
But when those pc try
Russ's third point is:
I believe that the 1st paragraph of section 8.4 needs further explanation.
A security association is identified by a triple consisting of a Security
Parameter Index (SPI), an IP Destination Address, and a security protocol
identifier (either AH or ESP). So, manual
You need to specify the scope identifier in addition to the link local address. The
ipconfig command will document addresses in the format:
IP Address. . . . . . . . . . . . : fe80::204:23ff:fe4a:f8c7%7
The indicator %7 is the scope identifier of your link (your system may use a
different
Dear All,
ETSI Plugtests(tm) Service is organizing its 5th IPv6 Interoperability
Event. The event will be held from 11th - 15th October 2004 at the
Sofitel of Cannes-Mandelieu French Riviera !
Registration is available at:
www.etsi.org/plugtests/IPv6.htm
Deadline to register is 24 September
Hello Bill,
This should be fixed. We were working on providing .dmg file
which would make that old file uncessary.
thanks,
Jibin
On Sun, 1 Aug 2004, David Murray wrote:
Forwarded Message
Date: Sunday, August 01, 2004 8:40 AM -0700
From: Bill Manning [EMAIL
The ICMP indication of local address resolution failure SHOULD be
treated as a hard error [RFC1122].
(the language is a bit wishy-washy because I don't want all the
address unreachable ICMP messages to be treated like this, just the
ones which the host in question generated
On Tue, 3 Aug 2004, Erik Nordmark wrote:
Two comments:
1. The term local address resolution isn't defined so I doubt the
above text suggestion clearly communicates what you want to say.
Right. Maybe just remove local then, making it a bit more ambiguous
but more accurate? :-)
The
But if ND resulution fails, is it probable that it's going to be fixed
any time soon? If the app just aborts if net connectivity is down,
the user can try again soon? At least to me, timely notification of a
serious network error that's blocking my access is a good thing.
If the (wireless)
On Tue, 3 Aug 2004, Erik Nordmark wrote:
[...]
Making anything a hard error seems to imply that TCP would immediately
give up, whether the connection was already established or in the process
of being established.
Unfortunately, yes.
But that is not such a big problem as I see it. Remember,
But that is not such a big problem as I see it. Remember, for
sessions that are already established, this only happens through the
NUD process. By default, that's 30 seconds, or until you want to
actually communicate (e.g., quiet SSH sessions would not be reset) if
the implementations
Hello,
Thanks for the comment, and sorry for not responding sooner.
On Mon, 26 Jul 2004 10:40:09 -0700,
Barany, Pete [EMAIL PROTECTED] said:
I noticed in Section 5.4.2 Sending Neighbor Solicitation Messages that
MLD (RFC 2710) is referenced (and correctly so). Subsequently,
MLD-snooping
Hi Takeo Shibata,
As we know an IPv6 node can have many interfaces and many IPv6 address at the same
time.
The ping6 command though Windows XP, ping fe80::x%7 , %7 means interface index
So as the same way in linux, the Ping6 command should be ping6 -I eth0
fe80::xx ,
Hi Takeo,
You can do one of the following on linux
you can do
ping6 -I interface_name destn
(or)
ping6 destn%interface_name
For Example:
ping6 -i eth0 fe80:: (or) ping6 fe80::%eth0
assuming the interface you are using is eth0.
Cheers
Suresh
On Tue, 3 Aug 2004, Takeo Shibata
(B
(B
(BHi ALL
(B
(BThank you very much for HELP.
(BI understand that
(BFor Windows, the interface name specified by
(B%IFNAME
(BFor Linux, it is specified followed by -I
(Boption.
(B
(BBut thank you for your helps.!
(B
(BTak
17 matches
Mail list logo
