Re: [DNSOP] Last Call: (The .onion Special-Use Domain Name) to Proposed Standard

2015-08-11 Thread Sam Hartman
> "Darcy" == Darcy Kevin (FCA) writes: Darcy>In retrospect, the definition of the Darcy> €œhttp€ and Darcy> €œhttps€ schemes (i.e. RFC 7230) should Darcy> have probably enumerated clearly which name registries were Darcy> acceptable for those schemes, so that the fo

Re: [DNSOP] Re: Last Call: draft-ietf-dnsop-reflectors-are-evil (Preventing Use of Recursive Nameservers in Reflector Attacks) to BCP

2007-10-03 Thread Sam Hartman
> "Joao" == Joao Damas <[EMAIL PROTECTED]> writes: Joao> It does indeed as Stephane pointed out. Opening up your Joao> resolver so you can server roaming users, without further Joao> protection, is, at best, naive. I'd appreciate it if you took Paul's comments a lot more seriousl

Re: [DNSOP] Re: [secdir] secdir review of draft-ietf-dnsop-reflectors-are-evil-04.txt (fwd)

2007-10-03 Thread Sam Hartman
If other related risks reduce the value of that fix,then the cost may not be justified. So, to the extent that Dean is trying to encourage that sort of analysis here, I think it is very good. At this time, I make no comment on the rest of his messag

[DNSOP] Re: Last Call: draft-ietf-dnsop-reflectors-are-evil (Preventing Use of Recursive Nameservers in Reflector Attacks) to BCP

2007-10-03 Thread Sam Hartman
> "Stephane" == Stephane Bortzmeyer <[EMAIL PROTECTED]> writes: Stephane> But suggesting ORNS (Open Recursive Name Servers) for Stephane> the solution to this issue is, indeed, a bad idea (do Stephane> note I did not say the N word), for the reasons Stephane> explained in draf