Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem)

2002-09-22 Thread itojun
> Yes, and I know why the restriction is in RFC 1884 and it > is a reasonable restriction. I don't think so, IP source address is easy to forge and it does not add any meaning protection. DNSSEC is the only way if you want trusted responsees. therefore, i agr

Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem)

2002-09-22 Thread Jun-ichiro itojun Hagino
> Yes, and I know why the restriction is in RFC 1884 and it > is a reasonable restriction. I don't think so, IP source address is easy to forge and it does not add any meaning protection. DNSSEC is the only way if you want trusted responsees. therefore, i agr

Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6anycast response problem)

2002-09-22 Thread JINMEI Tatuya / 神明達哉
> On Mon, 23 Sep 2002 12:54:35 +0900, > Jun-ichiro itojun Hagino <[EMAIL PROTECTED]> said: >> Yes, and I know why the restriction is in RFC 1884 and it >> is a reasonable restriction. > I don't think so, IP source address is easy to forge and it does not > add any meaning pr

Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem)

2002-09-22 Thread Jun-ichiro itojun Hagino
>>> Yes, and I know why the restriction is in RFC 1884 and it >>> is a reasonable restriction. >> I don't think so, IP source address is easy to forge and it does not >> add any meaning protection. DNSSEC is the only way if you want trusted >> responsees. therefore, i agree with e

Re: RES_INSECURE and CHECK_SRVR_ADDR in resolver functions (IPv6 anycast response problem)

2002-09-22 Thread Mark . Andrews
> > Yes, and I know why the restriction is in RFC 1884 and it > > is a reasonable restriction. > > I don't think so, Are you saying we should source packets from the anycast address? If not you should quote better. > IP source address is easy to forge and it