Quoting John Levine on Wednesday May 01, 2024:
>
> We all know the people at IANA who run .INT. If we can't persuade them
> that this has becomes a problem that needs to be fixed, how urgent is
> it likely to be?
No persuasion necessary. There has been an ongoing project to update
the signing
Quoting John Levine on Saturday May 06, 2023:
> >The IANA Function Operator does so for all ccTLDs (which would imply all
> >TLDs).
>
> Indeed, but some of them are lame anyway. Here's today's report:
> ...
> There are 96 more that timed out but I can't tell whether they really aren't
> there
Quoting Masataka Ohta on Friday November 12, 2021:
>
> > The operational decisions relating to these things have already been
> > made, as I understand it -- the delegations no longer exist. Kim and
> > Amanda's document seems to have two purposes: (1) to document this
> > operational reality,
Colleagues,
I wanted to draw your attention to an Internet Draft we’ve developed,
its goal is to formally deprecate a number of historic “.int”
domains that were designated for Internet infrastructure purposes
decades ago and appear for all intents and purposes obsolete. After some
limited
Hi Mark,
Quoting Mark Andrews on Tuesday December 12, 2017:
>
> HOME.ARPA. SOAA.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2017121101
> 1800 900 604800 86400
> HOME.ARPA.NS A.ROOT-SERVERS.NET.
..
> HOME.ARPA. DNAME EMPTY.AS112.ARPA.
It is unclear to me how this avoids having
Quoting Stephane Bortzmeyer on Friday November 10, 2017:
>
> > I'll note that from a technical/mechanical perspective, ICANN's and
> > Verisign's root zone management systems already know how to deal
> > with delegations. A DNAME in the root would require an unknown level
> > of development by
Quoting Andrew Sullivan on Thursday April 30, 2015:
|
| Country is a loaded term. I don't have a better suggestion in mind but
| there are many instances where a ccTLD is a territory, etc. I don't mean
| to open a rathole, just point this out.
|
| If we changed this to say, A TLD that is
Hi Mark,
On 11/09/09 4:47 PM, Mark Andrews ma...@isc.org wrote:
Publish new DNSKEY, publish new DS, wait at least the max TTL of
the old DS/DNSSKEY TTLs. Remove old DS, remove old DNSKEY.
The same thing should be happening with ITAR. Publish new DNSKEY,
publish new DS, wait the
Hi Joao,
On 14/09/09 9:53 AM, joao damas j...@bondis.org wrote:
could the ITAR have a serial number that could be checked without
having to download and parse the whole file, to enable quick checks
from consumers of the ITAR information that would not overwhelm either
end of the
Hi Mark,
On 11/09/09 4:01 PM, Mark Andrews ma...@isc.org wrote:
IANA still has not provided timing guidance.
IANA can you please specifiy a maximum polling interval on this
page and inform the TLD's using ITAR of what it is. A minimum
polling interval would also be useful but is not
On 11/09/09 4:21 PM, Kim Davies kim.dav...@icann.org wrote:
Right now, since the initial activity populating the repository, there are
only a couple of ITAR change events per month, but we have no pattern as to
when they can occur.
Actually, I can be more specific:
2009-01-20 sign_zones
On 8/09/09 11:52 AM, Chris Thompson c...@cam.ac.uk wrote:
ISC supposedly get their data for TLDs from the IANA ITAR. That's certainly
up to date now at https://itar.iana.org/anchors/anchors.xml but it would be
more than interesting to know how long that has been the case. (As I recall,
PR
12 matches
Mail list logo