Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt

Doesn’t http/https already include an authentication framework for clients?

-MSK

From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf Of Patrick Vande Walle
Sent: Tuesday, May 01, 2012 5:49 AM
To: Dave Piscitello; John Levine
Cc: weirds@ietf.org
Subject: Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt

-1.

While I can see the usefulness of such an information in specific criminal investigations, I think the registry or registrar could provide this information out of band to the relevant law enforcement authorities, when asked properly.

As mentioned already, IP addresses are considered as personal data under some jurisdictions.

If anything, this thread also shows the need to come up with an authentication framework. It is not just a nice to have option, but should be an integral part of the deliverables.

Patrick Vande Walle

Dave Piscitello <dave.piscitello@icann.org<mailto:dave.piscitello@icann.org>> a écrit :

+1

In a searchable world, sometimes all you have is the IP of the name server that's resolving the malicious/harmful domain. So asking "what other domains host zone files at this IP?", "who registered those domains?", and "what registrar is sponsoring the registrations?" are all useful crumbs that often help you identify names used by in a campaign, or the registrant names used in association with a criminal enterprise.

On Apr 30, 2012, at 10:46 PM, John Levine wrote:

>> I find the notion of asking a domain registrar for information about an
>> IP address to be confusing.  Is the user expecting to know who they
>> should contact about that IP address, are they expecting to find all the
>> possible mappings of labels to that IP address , or are they expecting
>> to have the domain query service perform a reverse l

 ookup

for them?
>
> For a name registry or registrar, I'd be thrilled to get a list of
> name servers they know about that resolve to that IP.  A common bad
> guy trick is to register a bunch of names, stick them all on the same
> servers, but use a different subdomain name for each one, e.g. foo.biz<http://foo.biz>
> has name server ns1.foo.biz<http://ns1.foo.biz> and bar.biz<http://bar.biz> has ns1.bar.biz<http://ns1.bar.biz> , but they're
> really the same IP.
>
> R's,
> John
>

________________________________

> weirds mailing list
> weirds@ietf.org<mailto:weirds@ietf.org>
> https://www.ietf.org/mailman/listinfo/weirds

________________________________

weirds mailing list
weirds@ietf.org<mailto:weirds@ietf.org>
https://www.ietf.org/mailman/listinfo/weirds

--
Envoyé de mon téléphone. Excusez la brièveté.