Oops. Missed a (significant) word.
On May 19, 2024, at 3:02 PM, David Conrad via NANOG wrote:
> On May 19, 2024, at 1:12 PM, Bryan Fields wrote:
>> Suppose the community wanted to change this or make a formal policy on root
>> server hosting requirements. Where would this
On May 19, 2024, at 1:12 PM, Bryan Fields wrote:
> Suppose the community wanted to change this or make a formal policy on root
> server hosting requirements. Where would this be done? Could a party submit
> a proposal to ICANN via the policy development process? If not where should
> the
John,
On May 19, 2024, at 12:53 PM, John R. Levine wrote:
> On Sun, 19 May 2024, David Conrad wrote:
>>> They provide this to Verisign, the Root Zone Maintainer, who create the
>>> root zone and distribute it to the root server operators.
>>
>> Technically, IANA provides database change
On May 17, 2024, at 10:14 PM, Bill Woodcock wrote:
>> On May 18, 2024, at 02:30, William Herrin wrote:
>> So Cogent operates a root server because they bought PSI who ran a
>> root server and ICANN has never chosen to throw down the gauntlet.
>
> As John said, ICANN has nothing to do with who
John,
On May 17, 2024, at 6:53 PM, John R. Levine wrote:
> ICANN as the IANA Functions Operator maintains the database of TLD info.
Sort of.
> They provide this to Verisign, the Root Zone Maintainer, who create the
> root zone and distribute it to the root server operators.
Technically,
5 matches
Mail list logo
