IPv6 BCP?!

[J D Falk]

Are you guys really trying to define a BCP for IPv6 DNSBLs?  How can it
possibly be a Best Current/Common Practice when there aren't any IPv6 DNSBLs
yet?

Proposal: finish defining existing practice as previously agreed, and split
out IPv6 into a more theoretical document.

--
J.D. Falk
Return Path

Work with me!
http://www.returnpath.net/careers/


_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[Dave Crocker-2]

J.D. Falk wrote:
> Are you guys really trying to define a BCP for IPv6 DNSBLs?  How can it
> possibly be a Best Current/Common Practice when there aren't any IPv6 DNSBLs
> yet?


AND...

Why should an IPv6 BL be different from an IPv4 one, except for the format of
the addresses?

d/


--

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[John Levine-2]

>Are you guys really trying to define a BCP for IPv6 DNSBLs?

Nope.  We're just trying to define the format of bits on the wire
so when people build them, they'll interoperate.  This argument is
about my DNSBL spec, not Chris' BCP.

R's,
John
_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[John Levine-2]

>Why should an IPv6 BL be different from an IPv4 one, except for the
>format of the addresses?

Um, are there any differences I've inadvertently introduced in the
current draft?  We've fended off attempts to make the values anything
other than A and TXT.  There's an open question about what the test
addresses should be, but I'm trying to figure out what the never
routable addresses analogous to 127/0 are.

R's,
John

_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[J D Falk]

On 04/08/2008 10:05, "John Levine" <asrg@...> wrote:

>> Are you guys really trying to define a BCP for IPv6 DNSBLs?
>
> Nope.  We're just trying to define the format of bits on the wire
> so when people build them, they'll interoperate.  This argument is
> about my DNSBL spec, not Chris' BCP.

Ah, okay, whew.  But even so, wouldn't it make more sense to do some
research into IPv6 DNSBLs before defining how they'll work?  Or if not,
wouldn't it make more sense to get the current spec published before adding
something uncertain & controversial?

--
J.D. Falk
Return Path

Work with me!
http://www.returnpath.net/careers/

_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[Dave Crocker-2]

John Levine wrote:
>> Why should an IPv6 BL be different from an IPv4 one, except for the
>> format of the addresses?
>
> Um, are there any differences I've inadvertently introduced in the
> current draft?  We've fended off attempts to make the values anything
> other than A and TXT.  There's an open question about what the test
> addresses should be, but I'm trying to figure out what the never
> routable addresses analogous to 127/0 are.


Any reason not to simply add AAAA records to the mix and be done with it?

d/

--

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[David Nicol]

On Mon, Aug 4, 2008 at 1:39 PM, Dave Crocker <dhc@...> wrote:
>
> Any reason not to simply add AAAA records to the mix and be done with it?

IIRC it's that the current 6->4 mapping is supposed to eventually go
away, and the test address mappings SHOULD survive that event.
_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[Frank Ellermann-3]

J.D. Falk wrote:
 
> wouldn't it make more sense to do some research into IPv6
> DNSBLs before defining how they'll work?

The only question that has to be answered is which IPv6 can
be the sacrifice maiden for an always listed test address.

Now after somebody got me to see that ::FFFF:127.0.0.2 is
not simple enough there is still the original proposal ::2,
and the new proposal in the meeting to use an IPv6 example
address.

Similar there was a s/test/invalid/ proposal for RHSBLs.

IMO it is perfect when a "proposed standard" proposes an
answer to a simple question.  There is no huge installed
base with different ideas (wrt IPv6), or with better ideas
(wrt RHSBLs).

It's not really "controversial", it would be only nice to
hear from some IPv6 experts that ::2 is okay as sacrifice.

I.e. that nobody would ever want to list or not list that
IP for "real".  Outside of a toy DNSBL with say "odd IPs",
where ::2 or 127.0.0.2 don't qualify as "odd enough".

 Frank

_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[Tony Hansen]

::2 is reserved for IETF use. This seems like it could be a perfectly
valid such use to be defined for it.

        Tony Hansen
        tony@...

Frank Ellermann wrote:
>
> It's not really "controversial", it would be only nice to
> hear from some IPv6 experts that ::2 is okay as sacrifice.
>
> I.e. that nobody would ever want to list or not list that
> IP for "real".  Outside of a toy DNSBL with say "odd IPs",
> where ::2 or 127.0.0.2 don't qualify as "odd enough".

_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[John Levine-2]

> Ah, okay, whew.  But even so, wouldn't it make more sense to do some
> research into IPv6 DNSBLs before defining how they'll work?  Or if
> not, wouldn't it make more sense to get the current spec published
> before adding something uncertain & controversial?

For the most part, the way that v6 DNSBLs will work is obvious, just
use the v6 rDNS naming rather than v4 rDNS naming.  The only parts
that aren't obvious are arbitrary, notably the test addresses.  Since
they're arbitrary, it makes sense to me to define them now so that
when people start building v6 DNSBLs they interoperate.

R's,
John


_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg

[Frank Ellermann-3]

Tony Hansen wrote:

> ::2 is reserved for IETF use. This seems like it could
> be a perfectly valid such use to be defined for it.

Nice, then s/test/invalid/ was the last technical point,
anything else is wordsmithing and maybe adding BCP 91 or
similar in the references.

 Frank

_______________________________________________
Asrg mailing list
Asrg@...
https://www.ietf.org/mailman/listinfo/asrg