This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] v6 ns/glue naming bcp
- Previous message (by thread): [dns-wg] v6 ns/glue naming bcp
- Next message (by thread): [dns-wg] v6 ns/glue naming bcp
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Patrik Fältström
paf at cisco.com
Sat Sep 6 14:00:37 CEST 2003
On 6 sep 2003, at 12.56, Jeroen Massar wrote: >> (The pix blocks it in some configuration modes I can add before you >> all >> say _T_H_E__P_I_X_...) > > Haha, hmm people where indeed complaining about PIX's at RIPE46 :) > Btw, when is a PIX going to do IPv6, I once heared "March 2003" > but I queried a university where they wanted to do IPv6 but due > to policy stuff were not allowed as their PIX didn't filter IPv6 > that it still did not support it :( The pix is like all "firewall software" there to "protect" stupid things behind it. So, to some degree it should only allow the minimal possible things (512 byte DNS packets, no extensions to SMTP etc). But, the problem _I_ see with the pix is that one only have the choice of being so rigid regarding the standards, OR to open the port(s) completely. As you understand, this is something I am trying to change, but it is hard, because firewall people are extremely conservative. paf
- Previous message (by thread): [dns-wg] v6 ns/glue naming bcp
- Next message (by thread): [dns-wg] v6 ns/glue naming bcp
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]