[Gnso-ppsai-pdp-wg] FW: Re: Fwd: What is content and what isn't

Michele Neylon - Blacknight michele at blacknight.com
Thu Oct 30 19:09:47 UTC 2014

>From Eric ..

Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Domains
http://www.blacknight.press/ - get all our latest media releases & coverage
Intl. +353 (0) 59  9183072
Direct Dial: +353 (0)59 9183090
Social: http://mneylon.social
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845

From: Eric Brunner-Williams [mailto:ebw at abenaki.wabanaki.net]
Sent: Thursday, October 30, 2014 7:08 PM
To: Michele Neylon - Blacknight
Subject: Fwd: Re: [Gnso-ppsai-pdp-wg] Fwd: What is content and what isn't


Again please. Thanks in advance.


-------- Original Message --------

Re: [Gnso-ppsai-pdp-wg] Fwd: What is content and what isn't


Thu, 30 Oct 2014 07:12:57 -0700


Eric Brunner-Williams <ebw at abenaki.wabanaki.net><mailto:ebw at abenaki.wabanaki.net>


gnso-ppsai-pdp-wg at icann.org<mailto:gnso-ppsai-pdp-wg at icann.org>


My note of earlier today, which Michele was kind enough to forward, covered only two of the points I hoped to make -- a difference between what we know when we look at a string, whether or not it resolves (registrations, or blocks, without associated resource records), and what we know when we resolve a domain name (without necessarily pointing a browser at the domain name). Then there is "content", that is, something that happens when we take the next step after discovering, via the resolution process, the underlying resources, and actually use those resources. This last part is what I expect many here mean by "content".

My point is that there is something between "string" and "content", and there are useful analytical steps for distinct interests for each of "string", "resolved resource records" and "resources".

Again, thank you all for your patience,

I don't know if this will go to the list -- I haven't been active since January.

I suggest that the terminal label in a dot-terminated sequence of labels, aka "the domain name", e.g., "example" in example.com<http://example.com>, and the resources associated with a dot-terminated sequence of labels, differ.

The former may be discovered by several means, e.g., string search through bulk access, random poking on whois, payload in transport protocol data, etc.

The later may only be discovered by resolution -- that is -- resources disclosed by the dns, or by direct access to the resources, usually hosts.

Restated, as I'm sure everyone is aware, names, infringing or not, are not the same as resources, malign or not, associated with the names via the dns.

What I suggest, because I don't think everyone agrees on what "content" might mean, is that the two flavors Steve referred to during yesterday's call:

Abuse comes in two flavors:  abuse that derives from registration of the domain name itself, and abuse that derives from how the domain name is used.

really are quite different, and that "content" as I suspect most here intend does _not_ include properties of resource records that would interest, even alarm, network operators (nominally included in the ISPCP within the GNSO). Examples of non-"content" resource record properties of interest or alarm are correlations of A records (hosts), of NS records (nameservers) with blocks of addresses or nameservers previously known to be ... interesting or alarming, as well as the TTL (time to live) value of resource records (enabling FastFlux and friends).

In lieu of "content", perhaps the clunkier but less vague term of "resolved resources" could be used. Then we would know when we are discussing a static property of a string (well, one likely to last a year or so in the current common registration model) or the dynamic properties of resolution of a FQDN.

Thank for your patience,


Gnso-ppsai-pdp-wg mailing list

Gnso-ppsai-pdp-wg at icann.org<mailto:Gnso-ppsai-pdp-wg at icann.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-ppsai-pdp-wg/attachments/20141030/8f31e696/attachment.html>

More information about the Gnso-ppsai-pdp-wg mailing list