Re: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification"

2000-06-22 Thread Bob Hinden
The author of this draft's email address has changed. His new address is: [EMAIL PROTECTED] Bob At 01:35 PM 6/22/2000 -0700, Bob Hinden wrote: >I forgot to add that this document is now an IPng w.g. document. We >inherited it when the ION w.g. concluded. > >Bob > >At 01:26 PM 6/22/2000 -

Re: rfc2553bis comments

2000-06-22 Thread JINMEI Tatuya / $B?@L@C#:H(B
> On Sat, 17 Jun 2000 21:11:56 +0200, > Francis Dupont <[EMAIL PROTECTED]> said: > In your previous mail you wrote (after reformatting into text): >3) When multicast addresses are stored in a sockaddr_in6, how is the >scope id field Interpreted? > => I believe it should be an i

Re: W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification"

2000-06-22 Thread Bob Hinden
I forgot to add that this document is now an IPng w.g. document. We inherited it when the ION w.g. concluded. Bob At 01:26 PM 6/22/2000 -0700, Bob Hinden wrote: >This is a IPng working group last call for comments on advancing the >following document as a Proposed Standard: > > Title

W.G. Last Call on "Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification"

2000-06-22 Thread Bob Hinden
This is a IPng working group last call for comments on advancing the following document as a Proposed Standard: Title : Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification Author(s) : A. Conta Filename

RE: rfc2553bis comments

2000-06-22 Thread Tim Hartrick
Rich, Francis, > > To answer your question - yes, the bind() of a multicast address should > automatically join the group. So this is another reason to make > sin6_scope_id field be an interface id for multicast addresses of all > scopes. > I disagree with both of these things and generally

RE: rfc2553bis comments

2000-06-22 Thread Richard Draves
>> Another point en passant, should in this case a bind() > with a non-zero >> scope_id do an automatical IPV6_JOIN_GROUP? > >I don't follow this - you can't bind() a multicast address. > > => I can Winsock (or least, the MS implementation) doesn't allow this. I didn't know t

Re: IPv4 - IPv6 translation

2000-06-22 Thread ARIGA Seiji
On Thu, 22 Jun 2000 06:37:56 GMT, "Yuval Shaul" <[EMAIL PROTECTED]> wrote, : Does anybody know of anything (RFC, implementation, idea etc)about : converting IPv4 packets to IPv6 packets ? There are two implemented IPv4 - IPv6 translator using Socks. # It doesn't actually 'convert' packets, thoug

FW: rfc2553bis comments

2000-06-22 Thread Dave Thaler
I just got a bounce message from the first time, apologies if this is a duplicate. -Original Message- From: Dave Thaler Sent: Wednesday, June 21, 2000 5:44 PM To: Richard Draves; Francis Dupont Cc: [EMAIL PROTECTED] Subject: RE: rfc2553bis comments > > Another point en passant, should

Re: problems with privacy draft

2000-06-22 Thread Francis Dupont
In your previous mail you wrote: > I believe you can make your set of rules simpler if you introduce > a new lifetime (or condition if one needs something smarter than > a delay). I'll call it "regen lifetime" and when the regen lifetime > of an anonymous address expires then a new

Re: sin6_flowinfo and sendto/recvfrom

2000-06-22 Thread Francis Dupont
In your previous mail you wrote: My assumption was that recvfrom() and accept() should return sin6_flowinfo from the received packet, and connect() and sendto() should take sin6_flowinfo and put it into sent packets. For bind(), I'd say either error if sin6_flowinfo is non-zero,

Re: sin6_flowinfo and sendto/recvfrom

2000-06-22 Thread Francis Dupont
In your previous mail you wrote: >more questions (I could not find answer from my archive): >(4) what happens if we connect(2) with sin6_flowinfo filled? >my guess is that sin6_flowinfo sticks into pcb, and >will be attached to every packet we will sen

Re: rfc2553bis comments

2000-06-22 Thread Yves Legrandgerard
On 22-Jun-00 Francis Dupont wrote: > In your previous mail you wrote: > >> Another point en passant, should in this case a bind() with a non-zero >> scope_id do an automatical IPV6_JOIN_GROUP? > >I don't follow this - you can't bind() a multicast address. > > => I can and in

Re: rfc2553bis comments

2000-06-22 Thread Francis Dupont
In your previous mail you wrote: > Another point en passant, should in this case a bind() with a non-zero > scope_id do an automatical IPV6_JOIN_GROUP? I don't follow this - you can't bind() a multicast address. => I can and in fact I can bind() many sockets to the same multicas

Re: IPv4 - IPv6 translation

2000-06-22 Thread 이상훈
I think you should read RFC2765. - Original Message - From: "Yuval Shaul" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 22, 2000 3:37 PM Subject: IPv4 - IPv6 translation > Does anybody know of anything (RFC, implementation, idea etc)about > converting IPv4 packets to

RE: IPv4 - IPv6 translation

2000-06-22 Thread Brian Zill
Yuval Shaul asks: > > Does anybody know of anything (RFC, implementation, idea etc) > about converting IPv4 packets to IPv6 packets? Erik Nordmark and George Tsirtsis have written a couple of handy RFCs on this topic, see: RFC 2565, "Stateless IP/ICMP Translation Algorithm" RFC 2566, "Network Ad