It appears that Bryan Fields said:
>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 community start this?
T
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 be done? Could a par
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 commun
On 5/19/24 3:13 PM, David Conrad via NANOG wrote:
> When you say “ICANN” who, exactly, do you mean? ICANN the organization or
> ICANN the community? If the former, ICANN Org can’t do anything outside of
> ICANN community defined policy or process or risk all sorts of
> unpleasantness from interna
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 requests
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 requests to Verisign. The actual
database is maintained by the Root Zone Maintai
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, IANA
On Fri, May 17, 2024 at 6:53 PM John R. Levine wrote:
> On Fri, 17 May 2024, William Herrin wrote:
> > That said, ICANN generates the root zone including the servers
> > declared authoritative for the zone.
>
> Nope.
Verisign maintains them under contract to ICANN and NTIA and under
direction fro
> On May 18, 2024, at 03:53, John R. Levine wrote:
> On Fri, 17 May 2024, William Herrin wrote:
>> That said, ICANN generates the root zone including the servers
>> declared authoritative for the zone.
> Nope.
>
>> So they do have an ability to
>> say: nope, you've crossed the line to any of the
On Fri, 17 May 2024, William Herrin wrote:
That said, ICANN generates the root zone including the servers
declared authoritative for the zone.
Nope.
So they do have an ability to
say: nope, you've crossed the line to any of the root operators.
Very very nope.
ICANN as the IANA Functions Op
10 matches
Mail list logo
