> On 13 Aug 2022, at 00:35, John Levine wrote:
>
> It appears that Warren Kumari said:
>> -=-=-=-=-=-
>>
>> Warren’s meta-comment -[ Please read this ]-
>> -
>> I believe that there is still an open-mineshaft problem aro
On Kerberos, we need to note that one use case of Kerberos is Microsoft Active
Directory; MS AD is behind a number of name collisions that happened in the
2012 root zone expansion, including one string that will likely never show the
light of day in the root (.corp). So, this might be the tellt
e ICANN / IETF divide, so IETF shouldn't wade
>> into ICANN territory.
>
> We don't know what ICANN considers an attempt to "wade into ICANN territory,"
> and there's nothing the WG can do to resolve this question. Such questions
> are why we have liaisons, which the IAB administers for the IETF
Hi.
During a meeting today of ROW (https://regiops.net), the I-D on CDS
bootstrapping by using a DNSSEC-signed name at name server zone
(https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-bootstrapping/) was
discussed.
In that discussion, it was mentioned that the current draft only supp
> On 22 Jun 2022, at 00:07, John Levine wrote:
>
> It appears that said:
>> -=-=-=-=-=-
>>
>>
>> Hi.
>>
>> During a meeting today of ROW (https://regiops.net), the I-D on CDS
>> bootstrapping by using a DNSSEC-signed name at name server
>> zone
>> (https://datatracker.ietf.org/doc/draft-
