Paul Wouters has entered the following ballot position for
draft-ietf-dnsop-dnssec-bcp-05: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
http
Roman Danyliw has entered the following ballot position for
draft-ietf-dnsop-dnssec-bcp-05: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
On OCT17@11:53, Paul Wouters wrote:
> On Mon, 17 Oct 2022, Eliot Lear wrote:
>
> > Let's please leave Internet lawyering to lawyers. If people want a
> > legal opinion on this draft, the IETF does have resources for that.
>
> But it is to the core of the ICANN / IETF divide, so IETF shouldn't wa
Dear WG,
The DNSOP WG chairs welcome feedback on the draft
draft-homburg-add-codcp, Control Options For DNS Client Proxies
(https://datatracker.ietf.org/doc/draft-homburg-add-codcp/).
The draft was submitted to the ADD WG for discussion and review, but the
WG chairs and the int area AD consi
On Sun, Oct 16, 2022 at 8:03 AM Suzanne Woolf wrote:
> Dear Colleagues,
>
>
> The chairs have gotten a couple of requests, off-list and on, for a WGLC
> on draft-ietf-dnsop-alt-tld.
>
> We’ve reviewed the current draft closely and have some concerns that we
> feel need to be resolved before any e
Dear WG,
This is a Call for Agenda Items for the IETF 115 in London, UK.
DNSOP WG is scheduled on Tuesday, 8 November at 09:30-11:30 (GMT/UTC).
(See for IETF 115 agenda https://datatracker.ietf.org/meeting/115/agenda)
Please email the chairs with your requests. *Or*
drop us a pull request
While we're talking about this draft, I would like to suggest that the
draft discuss the interpretation of URIs containing ".alt" hostnames. I
have great difficulty understanding what "https://example.foo.alt/"; means
... but most of the interest in alternative naming systems seems to be
based on
Speaking only for myself (and definitely not for my employer, GoDaddy)...
On Sun, Oct 16, 2022 at 11:45 PM Eliot Lear wrote:
>
> On 17.10.22 04:20, Paul Wouters wrote:
>
> > Basically, .alt is what IETF recommends you should not do, and we
> > should not keep
> > a registry of entries within it.
On Mon, 17 Oct 2022, Suzanne Woolf wrote:
One could advance the 6761bis proposal document first, which would
remove these non-compliance items as those would be no longer needed
(as the bis document proposal removes it as these were not consistently
required in the past). Alternatively, ignoring
John Scudder has entered the following ballot position for
draft-ietf-dnsop-dnssec-bcp-05: Yes
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
https://
On Mon, Oct 17, 2022 at 7:12 AM Joe Abley wrote:
>
> My goal is certainly not to put any brakes on if the effect of that is to
> make things move more slowly. I apologise if that's what I have done in
> suggesting to Brian that semantic-free labels do not fit the problem space.
>
>
And I, in retu
On Sun, Oct 16, 2022 at 7:20 PM, Paul Wouters wrote:
> On Sun, 16 Oct 2022, Suzanne Woolf wrote:
>
> 1. As far as I can tell, this draft does not comply with RFC 6761. This is
> a problem for two reasons.
>
> One could advance the 6761bis proposal document first, which would remove
> these non-co
On Sun, Oct 16, 2022 at 11:44 PM, Eliot Lear wrote:
> Hi Paul!
>
> Good conversation! I hope we can discuss some of this "in person"
> (whatever that means these days) at IETF 115.
>
> On 17.10.22 04:20, Paul Wouters wrote:
>
> On Sun, 16 Oct 2022, Suzanne Woolf wrote:
>
> 1. As far as I can tel
Hi Joe,
> -Original Message-
> From: Joe Abley
> Sent: 16 October 2022 20:30
> To: Brian Dickson
> Cc: Eliot Lear ; Rob Wilton (rwilton) ;
> Suzanne Woolf ; dnsop@ietf.org; DNSOP-Chairs Chairs
>
> Subject: Re: [DNSOP] Possible alt-tld last call?
>
> Op 16 okt. 2022 om 15:03 heeft Brian
Dear colleagues,
I work for the Internet Society but this is emphatically not the position of
the Internet Society.
On Sun, Oct 16, 2022 at 03:03:10PM +, Suzanne Woolf wrote:
2. Having the IETF maintain a registry of pseudo-SLDs concerns me on the basis
that having the IETF “recognize” (
On Mon, 17 Oct 2022, Eliot Lear wrote:
Let's please leave Internet lawyering to lawyers. If people want a legal
opinion on this draft, the IETF does have resources for that.
But it is to the core of the ICANN / IETF divide, so IETF shouldn't wade
into ICANN territory.
We cannot assume that D
Hi,
> On Oct 16, 2022, at 10:20 PM, Paul Wouters wrote:
>
> On Sun, 16 Oct 2022, Suzanne Woolf wrote:
>
> > 1. As far as I can tell, this draft does not comply with RFC 6761. This is
> > a problem for two reasons.
>
> One could advance the 6761bis proposal document first, which would
> remov
On 17.10.22 17:16, Paul Wouters wrote:
But does the IETF, when running a FCFS registry, want to take the legal
liability of your adjudicating?
Again, Paul, if you want to ask counsel for advice and have them provide
it here, great. Otherwise we end up Internet-lawyering, which is also
whe
On Mon, 17 Oct 2022, Independent Submissions Editor (Eliot Lear) wrote:
On 17.10.22 12:37, Vittorio Bertola wrote:
Well, I'm just waiting for the request to register amazon.alt.
(or xxx.alt, or ru[ssia].alt, or .alt, which some
people will do just for fun)
Unless, of course, you mean that
> On 17 Oct 2022, at 15:12, Joe Abley wrote:
>
> Since it's not clear, my favoured approach to this entire subject is to do
> whatever is the quickest way to resolve the conversation so that this working
> group can get on with work that, in my opinion, no disrespect intended, is
> less poin
On 17 Oct 2022, at 10:06, Martin Schanzenbach wrote:
> Technically, GNS celebrated its 10th birthday in 2022 ;)
:-)
> But back to business: You cannot think both that alternative name systems are
> fleeting trends and at the same time are a serious threat to DNS namespace
> consistency.
> That
On OCT17@07:11, Joe Abley wrote:
> On Oct 16, 2022, at 23:03, Christian Huitema wrote:
>
> > The main problem with "giraffe.org" and similar is that the subdomains are
> > leased, not owned. A glitch in the renewal, and they are grabbed by some
> > domain catcher and redirected to "my sexy gira
> On 17 Oct 2022, at 13:00, Independent Submissions Editor (Eliot Lear)
> wrote:
>
> I don't want to adjudicate names, but I have no problem adjudicating naming
> systems, including transparent attempts to get vanity names. Since none of
> those are naming systems, they would all get the of
Hi Vittorio,
On 17.10.22 12:37, Vittorio Bertola wrote:
Well, I'm just waiting for the request to register amazon.alt.
(or xxx.alt, or ru[ssia].alt, or .alt, which some people
will do just for fun)
Unless, of course, you mean that the ISE will adjudicate trademarks, define which strings
are
Hello, Roni!
The old algorithms GOST R 34.11-94, GOST R 34.10-2001 and GOST R
34.11-2001 are considered obsolete. They are now replaced with GOST R
34.10-2012 (digital signature) and GOST R 34.11-2012 (hash function).
Basically, the use of GOST algorithms in DNSSEC remains the same as
describ
On Oct 16, 2022, at 23:03, Christian Huitema wrote:
> The main problem with "giraffe.org" and similar is that the subdomains are
> leased, not owned. A glitch in the renewal, and they are grabbed by some
> domain catcher and redirected to "my sexy giraffe" or some such.
On the face of it that
> Il 17/10/2022 08:44 CEST Eliot Lear ha scritto:
>
> Let's please leave Internet lawyering to lawyers. If people want a
> legal opinion on this draft, the IETF does have resources for that.
>
> [...]
>
> No matter what we say in the ALT draft, someone could burden the IETF
> with a new dra
Robert Wilton has entered the following ballot position for
draft-ietf-dnsop-dnssec-bcp-05: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
28 matches
Mail list logo
