In message <1251822081.3172.8887.ca...@shane-asus-laptop>, Shane Kerr writes:
> Mark,
>
> On Tue, 2009-09-01 at 11:52 +1000, Mark Andrews wrote:
> > If you deploy BCP 38 to the customer level TCP is a good enough
> > authenticator for updating a reverse zone via UPDATE.
>
> As I mentioned at the
On Tue, Sep 1, 2009 at 10:35 PM, Edward Lewis wrote:
> At 4:05 +0900 9/2/09, fujiw...@jprs.co.jp wrote:
>
>> Performance problem will be solved by better code and new hardware.
>>
>> In my opinion, "Dynamically Generate PTR When Queried" works well.
>
> I have to ask based on the experience I had w
On 9/1/09 11:55 AM, Doug Barton wrote:
When IPv6 forces use of positive reputations, reverse DNS
entries become superfluous.
I'm sorry, I have no idea what this is supposed to mean. Could you
elaborate?
We offer an email abuse tracking service that lists IPv4 addresses.
Defending this service
At 4:05 +0900 9/2/09, fujiw...@jprs.co.jp wrote:
Performance problem will be solved by better code and new hardware.
In my opinion, "Dynamically Generate PTR When Queried" works well.
I have to ask based on the experience I had with wildcards, how does
this work with:
1) Zone transfers?
2
> From: Mark Andrews
>4.4) draft-howard-isp-ip6rdns-00.txt
> [Alain Durand][15 min][10:30]
At the IETF meeting, I had comments, but could not comment about this topic.
Same topic was discussed in Japanese comunity this March
and then, I implemented prototype "On the Fly" DNS server.
On Tue, 1 Sep 2009, Paul Wouters wrote:
Deployment of IPv6 nameservers was very hard because most Registries
did not support receiving IPv6 information. In part because of the huge
market share at Registers that are OpenSRS resellers, and the lack of
support within OpenSRS. It took a while, but
Stephan Lagerholm wrote:
>> I was actually thinking along the lines of "what would it take to
>> actually populate a reverse zone of size /N?" where N would take
>> various flavors like 64, 60, 56, etc. as an interesting experiment.
>
> Doug,
> You will need 4 billion disks with a capacity of 400
Douglas Otis wrote:
> This issue is largely about email acceptance policies.
>
> Saying IPv6 reverse DNS is not considered a practical means to determine
> legitimate IP address use needs to be either stated or refuted.
Well, the draft seems focused on the idea of rDNS for ISPs who hand
out add
Hi,
Deployment of IPv6 nameservers was very hard because most Registries
did not support receiving IPv6 information. In part because of the huge
market share at Registers that are OpenSRS resellers, and the lack of
support within OpenSRS. It took a while, but we[*] finally managed to
convince Op
On 9/1/09 10:34 AM, Doug Barton wrote:
Shane Kerr wrote:
Perhaps it makes sense to have two documents:
1. A document which says "you won't be able to pre-populate in IPv6
reverse like you do in IPv4 - don't worry about it".
2. A document which says "if you want to provide
> I was actually thinking along the lines of "what would it take to
> actually populate a reverse zone of size /N?" where N would take
> various flavors like 64, 60, 56, etc. as an interesting experiment.
Doug,
You will need 4 billion disks with a capacity of 400 Gig each just to
get 100 bytes for
Mark Andrews wrote:
> In message <4a9c783e.8090...@dougbarton.us>, Doug Barton writes:
>> Mark Andrews wrote:
>>
>>> This was on the adgena for DNSOP at the last IETF 75. There was
>>> much discussion.
>> Sorry if I'm rehashing this unnecessarily. I did (an admittedly
>> cursory) search of my lis
Shane Kerr wrote:
> Perhaps it makes sense to have two documents:
>
> 1. A document which says "you won't be able to pre-populate in IPv6
> reverse like you do in IPv4 - don't worry about it".
> 2. A document which says "if you want to provide IPv6 reverse for
> some rea
Mark,
On Tue, 2009-09-01 at 11:52 +1000, Mark Andrews wrote:
> If you deploy BCP 38 to the customer level TCP is a good enough
> authenticator for updating a reverse zone via UPDATE.
As I mentioned at the IETF, this is simply not true. All because I let
someone on my network doesn't mean I want t
14 matches
Mail list logo
