publication of various forms of contact. The intended
purpose is to provide a faster means of reliable contact for
professionals, cyber-defense of domains.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require
reuse (even though
it was junk info) to track and enumerate election information operations.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 8
deployed in a meaningful way to get
access to this data. Hence this proposal, which I harbor no illusions is a
second-best to an independent third party making this available in a way usable
by systems in a programmatic fashion. The best way just isn’t going to happen.
—
John Bambenek
On July 1st
have
to compromise two separate systems. What is best is independent third-party
verification but we don’t get that and we won’t. So, here we are.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license
Yes, bifurcation of whois is a problem. I’d rather it all be in one place, but
that door was closed and not by me.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa
.
Reputation and contact-ability intersect in this use case in my mind.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 8, 2019, at 17:14, Patrick Mevzek
Below
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 8, 2019, at 20:01, Paul Wouters wrote:
> On Mon, 8 Jul 2019, John Bambenek wr
Below
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 9, 2019, at 05:09, Vittorio Bertola
wrote:
>
>> Il 9 luglio 2019 00:01 John
Below
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 9, 2019, at 08:32, Jim Reid wrote:
>> On 8 Jul 2019, at 22:38, John Ba
Below
On 7/9/19 9:25 AM, Joe Abley wrote:
> On 9 Jul 2019, at 10:07, John Bambenek
> wrote:
>
>> On Jul 9, 2019, at 08:32, Jim Reid wrote:
>>
>>> 2. These policy problems are out of scope for the IETF. It deals with
>>> technical and operational matter
Below
On 7/9/19 9:28 AM, Ted Lemon wrote:
> On Jul 9, 2019, at 10:07 AM, John Bambenek
> <mailto:jcb=40bambenekconsulting@dmarc.ietf.org>> wrote:
>> But ICANN won’t allow such a system with meaningful data, so here we
>> are.
>
> The question you should be
> Hello everyone,
>
> Jim Reid wrote:
>
> > BTW, whois was originally intended to provide a way to publish
> > out-of-band contact data so the domain holder could be
> > contacted whenever their DNS or email was broken. Putting this
> > info in the DNS would defeat that.
>
> Implementation details
This might be worthy discussing
> in the draft.
>
>
> Rubens
>
>
>
>
>> Em 8 de jul de 2019, à(s) 18:38:000, John Bambenek
>> > <mailto:jcb=40bambenekconsulting@dmarc.ietf.org>> escreveu:
>>
>> All-
>>
>> In response to
This is true with DKIM today which uses a label.
On 7/9/19 10:05 AM, Jim Reid wrote:
>
>> On 9 Jul 2019, at 15:50, John Bambenek
>> wrote:
>>
>> I'm not married to any name, I chose WHOIS for historical reasons. We can
>> call it _hamsandwich if it buil
Below
On 7/9/19 10:07 AM, Joe Abley wrote:
> Hi John,
>
> On 9 Jul 2019, at 10:36, John Bambenek wrote:
>
>> If the proposal is to create a standard by which to put contact
>> information into DNS records, what venue would you suggest?
> I think that the protocol as
> Hi :-)
>
> John Bambenek wrote:
> >> That said, I agree it cannot solve GDPR or other policy concerns.
>
> > Why? GDPR applies to IP addresses, that doesn't impact DNS yet.
>
> You appear to have confused IP with P(I)I: personally identifying
> infor
Not intended to debate, per se.
On 7/9/19 10:21 AM, Ted Lemon wrote:
> As far as I can tell, you are deflecting my serious concerns rather
> than responding to them. I’m asking you to describe an actual
> situation where the information you want us to publish would (a) be
> published and (b) /ac
> Hello,
>
> John Bambenek
> wrote:
> >> All whois data is PII, in the case where people register
> >> individual details, as opposed to organizational roles. I think
> >> you may need to do a bit more research on this topic, you seem to
> >> have m
On 7/9/19 11:00 AM, Ted Lemon wrote:
> On Jul 9, 2019, at 11:41 AM, John Bambenek
> <mailto:jcb=40bambenekconsulting@dmarc.ietf.org>> wrote:
>> You assume I'm going to create a huge database, I am not. I would
>> envision doing something like if you send
On 7/9/19 10:27 AM, Jim Reid wrote:
>> John Bambenek wrote:
>>
>>> Why? GDPR applies to IP addresses that, doesn't impact DNS yet.
> GDPR applies to *any* data which identifies a living European citizen.
>
> If you think it only applies to IP addresses you ar
On 7/9/19 11:09 AM, Ted Lemon wrote:
> On Jul 9, 2019, at 12:03 PM, John Bambenek
> <mailto:jcb=40bambenekconsulting@dmarc.ietf.org>> wrote:
>> I cannot coerce anything. I represent nothing that represents even a
>> molecule of the network to coerce or enforce
Yes, I can do that.
On 7/9/19 11:12 AM, Paul Wouters wrote:
> On Tue, 9 Jul 2019, John Bambenek wrote:
>
>> On 7/9/19 11:00 AM, Ted Lemon wrote:
>> On Jul 9, 2019, at 11:41 AM, John Bambenek
>> wrote:
>> You assume I'm going to create a
I generally agree with this and have no problem deferring to an effort
to create a dictionary of registration data elements and agreed upon
definitions.
I gave serious thought to just making the current proposal have one
contact class, I kept several more for consistency with the legacy
system, bu
; Il 9 luglio 2019 16:36 John Bambenek
>> ha scritto:
>>
>>> I agree with pretty much everything else Jim said, but really this seems
>>> like the core issue: this seems like a proposal in the wrong venue.
>> If the proposal is to create a standard by which t
> John Bambenek
> wrote:
>
> > But is the risk to self-identification as present when
> > role-based accounts could be used as opposed to PII? I guess
> > I'm not understanding the risks of people accidentally
> > disclosing what they don't intend to.
&
there be one created?
On 7/9/19 1:21 PM, Ted Lemon wrote:
> On Jul 9, 2019, at 2:04 PM, John Bambenek
> <mailto:jcb=40bambenekconsulting@dmarc.ietf.org>> wrote:
>> Can't this be mitigated by any number of forms of user education?
>
> The evidence is crystal cl
Below
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 9, 2019, at 15:51, Jim Reid wrote:
>> On 9 Jul 2019, at 17:43, John Ba
Below
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 9, 2019, at 16:21, Brian Dickson wrote:
>
>
>> On Tue, Jul 9, 2019 at
it. Why should this service be special in that
regard?
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 9, 2019, at 09:46, Paul Vixie wrote
Below.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 9, 2019, at 19:13, Paul Vixie wrote:
>> On Tuesday, 9 July 2019 21:56:49 UT
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
On Jul 9, 2019, at 19:41, Paul Vixie wrote:
>
>
> John Bambenek wrote on 2019-07
to contact a domain owner for
something that doesn’t exist (aside of domain renewal spam or trying to buy the
domain).
Am I missing something?
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
support free form text fields so
can support this with no additional work. The idea here was to develop
something using services people already run with functionality that already
exists. The only “new” here is a standard way to structure the information.
—
John Bambenek
On July 1st, 2019, my DGA
This is my understanding as well as the approach and legal assumption I used in
creating this draft.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com for details
disclosure and allow role-based info. That’s not the only approach.
It just seemed logical to me to tackle it that way.
—
John Bambenek
On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license
which means commercial use will require a license. Contact
sa...@bambenekconsulting.com
And the existing system is not consistently formatted, this would create
a parseable and consistent standard.
And would bypass GDPR concerns by registries.
On 7/10/19 3:14 PM, David Conrad wrote:
> Philip,
>
> On Jul 10, 2019, at 6:24 AM, Philip Homburg
> mailto:pch-dnso...@u-1.phicoh.com>> wrote
36 matches
Mail list logo
