Hi, all.
In article [EMAIL PROTECTED] (at Wed, 05 Jul 2000 20:40:07 +0900),
[EMAIL PROTECTED] says:
Are you trying to change 2553 to use socklen_t for all the arguments,
or are you trying to correct glibc? If the latter, the mailing list
is a wrong place to ask.
As there is no change between RFC2553 and 2553bis on this particular
"getnameinfo argument" issue, RFC2553 is the correct specification
to look at for this particular issue.
Please try to convince glibc guys, quoting the above if necessary.
I've raised an official
As there is no change between RFC2553 and 2553bis on this particular
"getnameinfo argument" issue, RFC2553 is the correct specification
to look at for this particular issue.
Please try to convince glibc guys, quoting the above if necessary.
I've raised an official
Hi, I need some information about the possibility to support IP directly
over SDH, without passing through ATM.
Have you some titles of articles and other references for helping me?
Thanks in advance
xubo
E-mail:[EMAIL PROTECTED]
I have a different question in the same context. Assume two nodes
node A and node B on the same link. If node A (malicious) does
not do *DAD* and sends out a packet with node B's address as source
address to B, B should drop the packet. But this is not mentioned
in the spec anywhere. It
In your previous mail you wrote:
The question has to do with NA NS where the destination address (== the
target address) is tentative.
= I have an incredibly simple answer: our code doesn't receive packets
to a tentative address!
Ideally one should not recieve packets
We have an
idea of what to use it for.
I'm currently writing a draft about
traffic engineering in ipv6 like I said to you Bob.
A draft proposal is finished quite soon and the
intention is to see if there is some interest to use the flowlabel for traffic
engineering and If you would like to
I have a different question in the same context. Assume two nodes
node A and node B on the same link. If node A (malicious) does
not do *DAD* and sends out a packet with node B's address as source
address to B, B should drop the packet. But this is not mentioned
in the spec anywhere. It
